Deployment Rollback Window

A practical example

Example: you ship a new lead-scoring formula. For the first hour you can revert and records keep their old scores.

Once the nightly batch rescores the database under the new formula, reverting the code leaves every record carrying the new scores — the window has closed.

What to evaluate before investing

• Ask vendors whether automation changes can be scheduled or staged, so mutating steps run only after verification.
• Ask whether the platform logs prior values when a change mutates records, which partially reopens the window.
• Ask how the vendor recommends verifying changes before they touch production data.

Limitations and tradeoffs

Defining the window forces faster verification, but it cannot be extended by intent alone; only pre-mutation logging or staged rollouts genuinely preserve the ability to restore prior state.