1
Build the change package
Describe the business reason, affected systems, implementation approach, validation, communication and rollback before approval.
- Link the tickets, problems and assets that explain impact.
- Declare outage and freeze-exception requirements explicitly.
- Use readiness gaps to improve the package before CAB review.
2
Review and schedule
CAB readiness and approvals make missing information visible. Use the calendar to inspect surrounding work before committing to a window.
- Assign the appropriate approver.
- Resolve readiness gaps rather than treating the score as decoration.
- Check conflicting or adjacent changes.
3
Execute and validate
Move the change through start, validation and completion actions. If validation fails, record the outcome and use rollback when required.
- Start only when the approved window and prerequisites are satisfied.
- Record validation passed or failed with useful evidence.
- Complete, cancel or roll back through explicit actions so history stays trustworthy.