Cutover dress rehearsal: a walkthrough

A cutover dress rehearsal is the full cutover sequence, executed end-to-end against a production-like environment, with the actual cutover team, at the actual time of day. It runs one week before the production cutover and exists to surface every coordination, communication, and decision-making failure mode the technical rehearsals cannot catch.

It is the most comprehensive of the four rehearsal types and — if you run only one rehearsal — the one you cannot skip.

Definition

A cutover dress rehearsal is a time-boxed, end-to-end execution of the cutover plan against a production-equivalent non-production environment. It includes every activity that the real cutover will include: pre-cutover freeze procedures, the cutover window itself, business sign-off, the go-live moment, and at least one full rollback. The actual cutover team executes it, on the actual schedule, with the actual war-room setup.

When the dress rehearsal happens

T-7 days. One week before the production cutover.

That timing is deliberate:

• Late enough that the runbook, integrations, and team state are representative of production
• Early enough that there is still a week to close the action list

A dress rehearsal at T-3 is too late — there is no time to act on what it surfaces. A dress rehearsal at T-14 is too early — the environment and the team will both have drifted by the time of the real cutover.

For high-risk programs, schedule a second dress rehearsal at T-3 explicitly to confirm that the T-7 action list has closed.

What’s in scope vs the mock cutover

The dress rehearsal differs from the mock cutover at T-14 in three significant ways:

1. Scope. Mock = technical phases only. Dress rehearsal = end-to-end, including communications, freeze procedures, business sign-off, go-live, and rollback.
2. Duration. Mock = half a day to one day. Dress rehearsal = matches the production cutover window (8h–72h).
3. Participants. Mock = technical streams. Dress rehearsal = all streams plus the executive sponsor for the readiness review.

The two rehearsals are complementary, not redundant. The mock catches technical bugs early and cheaply. The dress rehearsal catches everything else.

The dress rehearsal runbook

Pre-rehearsal (T-9 to T-8)

1. Confirm environment readiness. The non-production environment must match production in data volume, integration endpoints, authentication, and network topology. Document every divergence — those are the gaps the rehearsal will not catch.
2. Refresh the environment from a recent production snapshot. Stale data hides failure modes. The starting point must reflect what the real cutover will encounter.
3. Lock the participant list. Every owner from the cutover plan must be present and executing their own activities. No delegation upward. Junior staff on the production rota execute the rehearsal.
4. Schedule on the real clock. If the production cutover starts Saturday 23:00, the dress rehearsal starts Saturday 23:00 the previous week. Cognitive load at 03:00 is materially different from cognitive load at 14:00.
5. Stage the war room. Same Slack channel structure, same video bridge, same shared timeline document, same on-call rotation that will run the real cutover.
6. Brief the executive sponsor separately. They observe the readiness review at T-1 and the post-rehearsal debrief — they do not sit in the war room during execution. Stream leads modify their behavior when senior leadership is watching, which defeats the purpose of the rehearsal.

Execution day (T-7)

The dress rehearsal executes the full cutover plan, in order, on the production clock. At a high level:

1. T-1 readiness review (simulated). Run the formal go/no-go meeting with the executive sponsor. Record a decision. This rehearses the meeting itself — which is often where real cutovers slip.
2. Open the cutover window. Stand up the war room. Confirm staffing. Send the kickoff communication to stakeholders.
3. Lock the source system. Same procedure as production. Time-stamp the start and end.
4. Take the backup snapshot. Verify the backup completes and is restorable. If verification fails, this is the most important action item from the rehearsal.
5. Execute the data migration. End to end, at production-equivalent volumes. The longest single phase. Measure elapsed time precisely.
6. Validate row counts and checksums. Use the production validation scripts.
7. Run smoke tests. Use the production smoke-test suite.
8. Business validation. Key users execute critical workflows on the target system. Time-stamp how long this actually takes — it is consistently underestimated.
9. Cut DNS / load-balancer / integrations. Execute the cutover to target.
10. Go-live announcement. Send the go-live communication to end users.
11. Open the target to users. This is the go-live moment.
12. Post-cutover validation. Simulate the first hours of production. Reconcile any final discrepancies.
13. Exercise the rollback. At some point during the rehearsal — ideally at the rollback trigger point of a planned failure scenario — execute a full rollback to the source system. The rollback path is the rarer one and the higher-risk one.

Throughout: time-stamp every task start, every task end, every decision point. Capture deviations in a debrief log structured across five categories — time variance, new risks, sequence issues, decision quality, communication failures.

Post-rehearsal debrief (T-6)

1. Run the debrief within 24 hours. Memory degrades fast. Same room, same participants.
2. Walk through the debrief log. Each observation gets categorized and prioritized.
3. Produce the action list. Every action has an owner and a due date — typically T-3 or T-1, certainly before T-0.
4. Update the runbook live. Every deviation from the plan becomes an edit. New steps, corrected timings, additional rollback triggers.
5. Report status to the executive sponsor. Brief them on the action list and the confidence level for go-live.

Action list closure (T-6 to T-1)

Every action item from the dress rehearsal must close before T-0, or the cutover slips. The cutover lead reviews status at every daily stand-up. Actions that will not close are escalated, not absorbed.

What only the dress rehearsal catches

The dress rehearsal exists because four categories of failure mode do not surface in any other rehearsal type:

Coordination failures. Two streams that each work correctly on their own but fail when they need to hand off. The mock cutover doesn’t catch these because it is technical-only; the dress rehearsal does because every stream is in the war room.

Communication chain issues. Stakeholder updates that arrive too late, too early, with wrong information, or to the wrong audience. These only surface when the comms procedure is actually exercised end-to-end.

Rollback procedure. Most rollbacks fail not because the technical steps don’t work but because the team has never executed them under pressure. Decisions about when to roll back are harder than the rollback itself. The dress rehearsal rehearses both.

Decision quality under fatigue. The cutover lead makes 30+ go/no-go calls during a typical cutover window, many past midnight. Practicing those calls in a low-stakes rehearsal measurably improves the real ones.

What to measure

Five numbers from the dress rehearsal directly determine whether the production cutover is ready:

Metric	Why it matters
Total elapsed time	Does the plan fit in the production window with ≥30% buffer?
Time-to-recover from a forced failure	If something fails at 03:00, how long does the team need?
Time to business sign-off	Consistently underestimated; can extend the window by hours
Rollback execution time	How long from rollback decision to source-system operational?
Communication latency	How long from event to stakeholder notification?

If total elapsed time exceeds the production window without buffer, the cutover plan or the window has to change. Do not proceed on the assumption that it will be faster in production.

Common mistakes specific to dress rehearsals

Compressing the timeline. “We don’t need to run for the full 56 hours — we’ve already done the technical part in the mock.” Wrong. The dress rehearsal is rehearsing the coordination, communication, and decision-quality dimensions, all of which require the full duration.

Letting senior leadership sit in the war room. Stream leads behave differently when observed by their executive sponsor. The rehearsal is supposed to expose the team’s actual decision-making, which requires a safe space to make mistakes. Brief leadership in the debrief.

Skipping the rollback rehearsal. Most dress rehearsals execute the happy path and stop at go-live. The rollback path then enters the production cutover untested. At least one rehearsal must rehearse the rollback — and the dress rehearsal is the right one.

Treating action items as optional. If an action from the dress rehearsal will not close before T-0, the production cutover should slip. Programs that override this principle are the same programs that ship cutover incidents.

Using a small dataset. “We refreshed last month — the data is roughly the same.” It is not. Refresh from a recent snapshot. Data patterns drift, and the patterns that drift the most are the ones that cause production incidents.

When to schedule a second dress rehearsal

For high-risk programs, schedule a second dress rehearsal at T-3, with explicit scope: validate that the action list from the T-7 rehearsal has closed. The T-3 rehearsal can be shorter and more targeted — it does not need to repeat the full 56 hours. It needs to confirm the specific items that were red.

If the T-7 rehearsal surfaced fewer than five action items, the T-3 rehearsal is optional. If it surfaced more than ten, it is mandatory.

After the dress rehearsal: closing the loop

The action list from the dress rehearsal is the most important artifact of the entire program. It is the difference between a cutover that goes well and one that does not.

• Every action has an owner and a date — before T-0.
• The cutover lead reviews status at every daily stand-up between T-6 and T-1.
• Actions that will not close before T-0 are escalated, not ignored.
• The T-1 readiness review explicitly validates that every action has closed.

If the readiness review at T-1 reveals open actions, the cutover lead has two options: pull them in by T-0, or recommend the executive sponsor delay the cutover. There is not a third option.

Generate your cutover plan

The cutover plan template generator produces a phased plan with dress rehearsal scheduled at T-7 and the readiness review at T-1, with action-list tracking baked in.

Related

• Cutover rehearsal: the complete guide — the pillar, with the full taxonomy of rehearsals
• Mock cutover: an explainer — the T-14 technical-phase rehearsal
• Dry run migration: a complete how-to — rehearsing the data move at production scale
• Cutover phases breakdown — where the dress rehearsal sits in the six-phase model
• Cutover vs go-live — where the go-live moment fits inside the cutover window