Lesson 4 of 5
Running the command center
11 min
During the cutover window, the command center (sometimes called the war room) is where the cutover is run: where status is known, issues are decided and the clock is watched. It may be a physical room, a virtual bridge, or both. Its job is to make sure that, at any moment, someone can answer three questions: where are we against the plan, what is blocking us, and who decides?
Who is in the command center
Rhythm: checkpoints and calls
Run the window on a fixed rhythm. Short checkpoint calls at set times, for example every four hours and at each milestone, review status against plan, new issues and decisions needed. Between calls, workstreams update a shared status board as each task starts and ends, so nobody has to ask for status. Shift handovers follow a written template: tasks in progress, open issues, decisions taken and anything the next shift must watch.
- Fri 18:00Kick-off callLegacy locked; backup confirmed; roster and bridge checked
- Every 4 hoursCheckpoint callsStatus against plan, float remaining, issues, decisions
- Sat 18:00Go/no-go 1Data loaded and reconciled; finance balances signed
- Sun 14:00Go/no-go 2Verification passed; decision to release the business
- Mon 06:00Business releaseUsers unlocked; hypercare starts; command center hands over
The status board
The status board is the single source of truth during the window. It shows each task with planned and actual times, its status, the critical path and the float remaining. Keep it simple enough to read at a glance: a task that is late on the critical path should be obvious within seconds. If verification test runs are recorded in a test management tool such as a dedicated test plan in SAP Cloud ALM, link to it so the decision group sees verification status without asking.
Issues, escalation and decisions
Every issue in the window goes into one issue log with a time, an owner, its impact on the critical path and its status. The cutover manager decides what he can within agreed limits; anything that threatens a go/no-go criterion or the window goes to the decision group immediately, not at the next checkpoint.
- Does the issue affect a critical path task?No → owner fixes it; note it in the log · Yes → next question
- Can it be resolved within the remaining float?Yes → cutover manager approves the fix and adjusts the plan · No → next question
- Does it threaten a go/no-go criterion or the window?Yes → convene the decision group now with options · No → cutover manager decides and informs at next checkpoint
Keep a separate decision log: every decision, who took it, when, on what evidence, and any conditions. After go-live, auditors and steering committees ask why a step was skipped or a difference accepted. The decision log answers in a minute.
Communication
Plan messages in advance and put them in the runbook: to executives at each go/no-go point, to users before the freeze and at release, to customers and suppliers if shipments or orders are affected, and to the support desk at release. Pre-written templates mean that at 02:00 the communications lead only fills in times and outcomes.
| Audience | When | Content |
|---|---|---|
| Executive sponsor | Each go/no-go point | Decision, evidence summary, conditions, next checkpoint |
| All users | Freeze, release | What is locked, when to start, where to get help |
| Customers and suppliers | Before freeze, if affected | Order and shipment cut-off times, contact points |
| Hypercare desk | Release | Known issues, workarounds, priority rules |
Contoso's communication plan for the cutover window.
What would you do?
At 02:00 on Saturday, the business partner load fails halfway. The data lead thinks a fix will take three hours; float is four hours. The next checkpoint is at 06:00. What should Luis do?
- The command center makes position, blockers and decision rights clear at every moment.
- Run on a fixed rhythm of checkpoint calls, a live status board and written shift handovers.
- One issue log, one decision log, and escalation rules tied to float and go/no-go criteria.
- Pre-plan communications to executives, users, partners and the support desk.
Check your understanding · not graded
Lesson check
1. What is the main job of the command center during cutover?
2. Why keep a decision log separate from the issue log?
3. When should an issue go to the decision group?
4. What should a shift handover cover?