1
Describe the change, timing, affected services, implementation plan, validation method, and rollback trigger
Describe the change, timing, affected services, implementation plan, validation method, and rollback trigger.
Flagship use case · Operations & Resilience
Change Readiness Analyzer
Assess change risk with mandatory control gates, conditional N/A handling, assessment history, and CAB-ready outputs.
App v2.0.0Site v6.2.0Local by default
Interface preview
Working application structure
This representative capture shows the application shell and primary workspace. Actual results depend on the information entered and the workflow completed.
Desktop viewport · representative interface stateOpen live application →
Visible methodAssumptions and record logic remain reviewable.
Local-first postureData handling is stated in the application.
Portable outputExports support review and continuity.
Explicit boundariesLimitations are part of the product evidence.
User and problem
Where the tool fits
Designed for: Change managers, CAB participants, service owners, technical leads, and implementation coordinators.
Problem addressed: Change reviews can become subjective when risk factors, mandatory controls, rollback readiness, and decision evidence are not evaluated consistently.
Core workflow
From input to decision-ready output
Frame→Structure→Analyze→Export
2
Score seven weighted risk factors and mark each control Complete, Pending, or N/A
Score seven weighted risk factors and mark each control Complete, Pending, or N/A.
3
Review the calculated readiness state and generate a CAB decision brief with conditions and open gaps
Review the calculated readiness state and generate a CAB decision brief with conditions and open gaps.
Method
Transparent calculation and record logic
The methodology is intentionally visible so users can challenge the assumptions and validate the result against authoritative evidence.
How the application works
- Normalizes weighted factor scores to a 0–100 risk score. Familiarity, rollback confidence, and resource coverage are inverse-risk factors.
- Excludes controls marked N/A from the completion denominator but never treats mandatory incomplete controls as ready.
- Classifies readiness as Ready, Conditional, or Not ready using risk thresholds, control completion, and mandatory-gate status.
Illustrative output
Risk score: 47 / 100 Controls complete: 82% Readiness: Conditional Decision: Approve with conditions
Boundaries
What the result does not prove
- The scoring model is a governance aid, not a substitute for technical testing or organizational approval.
- Weights and thresholds are fixed in this version and may not match every risk framework.
- A Complete control is a user assertion; the tool does not independently verify evidence.
Working data remains local to this browser unless the application explicitly describes an external request or the user exports a file. Browser storage can be lost when data is cleared or the device changes.