ANSWER
What belongs in a rollback checklist before cutover?
Reviewed .
A rollback checklist before cutover defines the return trigger, who can invoke it, data state, maximum recovery time, communication, dependencies and proof that the legacy operation can still resume. A document alone is not a ready plan: the return must be rehearsed, access must work and the decision must have an owner.
Step by step
- Define objective rollback triggers and the authority that can invoke them without ambiguous escalation.
- Record restore point, synchronization, reconciliation and treatment of in-flight transactions.
- Confirm legacy access, infrastructure, staff and vendor availability during the window.
- Test the return in a representative environment and measure RTO, accepted loss and manual steps.
- Attach evidence, contacts, communication, go/no-go and validity to the Evidence Pack.
How an agent does this
In AgenticosCore, Brake stops the new execution while rollback follows the approved process plan. Cutover remains blocked until the rehearsal and evidence are recorded in Trail.
Frequently asked questions
Are Brake and rollback the same?
No. Brake stops the new execution. Rollback restores the previous operation and reconciles state, which can require additional steps.
When does a rollback plan expire?
When access, data, dependencies, staff or architecture change. Validity must be explicit and reviewed before each cutover.
Primary sources
- Contingency Planning Guide for Federal Information Systems — NIST
- Retiring service components securely — UK Government Security