operra
Releases

How to write a rollback plan that actually gets used

Operra Guides · 5 minute read

Almost every team says they have a rollback plan. Far fewer have one they would actually use at 11pm when a release is going wrong. The difference is not the steps. It is deciding, in advance and in daylight, when to roll back and who makes the call.

1. Name one decision owner

During an incident, everyone has an opinion and nobody wants to be the one who undoes the release. Name one person who calls the rollback. Everyone else gives information; that person decides.

2. Agree triggers with numbers

Vague triggers like "if things go badly" lead to waiting too long. Write triggers your monitoring can actually show:

TriggerExample threshold
Error rate on a key serviceAbove 2% for 10 minutes
Critical user journey failsLogin or payment fails in smoke testing
Performance degradesResponse time over 3 seconds for 15 minutes
Data integrity issueAny data loss or corruption found

Adjust the numbers to your product. The point is that they are agreed before the release, not argued during it.

3. Set a decision deadline

Teams under pressure keep trying "one more fix". Set the latest time you will decide, for example 60 minutes after deployment. Also note the point of no return: the step after which rolling back means restoring from backup, such as a database migration.

4. Write the steps like a recipe

Each step needs an action, an owner, an estimated time and how you will check it worked. A typical sequence:

  1. Announce the rollback in the release channel.
  2. Turn on a maintenance page if customers are affected.
  3. Redeploy the previous version.
  4. Revert database and configuration changes.
  5. Run smoke tests.
  6. Turn off the maintenance page and monitor closely.

5. Protect the data

Most rollback pain comes from data, not code. Before release, confirm backups are taken and a restore has actually been tested. Decide what happens to data customers create after the release if you roll back.

6. Plan the messages

Know in advance who tells whom: internal stakeholders, customers through your status page or email, and the support team with workaround notes.

7. Learn from it

A rollback is not a failure; an unplanned, slow rollback is. Log every rollback, hold a short root cause review within three working days, and agree what must change before trying again.

Get the Release Go/No-Go Kit

A ready-to-use checklist with an automatic GO / NO-GO decision, a release calendar, rollback plan, change request form and release notes template. Word and Excel.

See what's inside