Timing a rollback drill before the campaign freeze

Campaign freezes compress decision time. Teams often schedule application audits after feature work is “done,” which leaves little room to rehearse a rollback with production-like traffic.

Drill while the canary still means something

A rollback drill run only in an empty staging environment proves the script parses. It does not prove abort criteria under load. When we audit applications ahead of freezes, we ask whether the last drill used a canary percentage close to what marketing traffic will look like on launch day.

Put the drill on the same calendar as the audit

If findings are due fourteen days before go-live, the drill should finish before evidence week ends. Otherwise the register can only say “rollback unproven,” which is accurate but late. Release leads who book both together avoid that awkward gap.

Name who may abort

Drills that succeed technically still fail organisationally when nobody on the night rota has authority to stop promotion. We list missing abort authority as a distinct finding from a broken script.

For a narrower look at a single path, see our deployment path review.