What should the command centre know at all times?
The command centre is the coordination point for a live transition. It does not execute every activity; it maintains operational control, understands deviation, coordinates teams, manages decisions and protects the outcome.
- What has completed and what is running?
- What should have started and what is overdue?
- What is blocked or on the critical path?
- Which validations and approvals are outstanding?
- What decisions are required and by when?
- What is the current completion forecast?
- Is contingency or rollback still possible?
Command centre roles
The operating model may include a cutover manager and deputy, programme manager, workstream and technical leads, business leads, decision authority, communications and scribe or governance support. The precise structure depends on programme risk and scale.
Publish responsibilities, deputies, escalation routes and decision authority before the event.
The operating rhythm
Combine continuous exception monitoring with scheduled checkpoints for forecast, risk and decisions. The appropriate frequency changes with the phase and risk; arbitrary meetings can distract teams from execution.
Every checkpoint should have a clear purpose, current evidence and accountable actions.
Management by exception
A command centre should not spend its time reading hundreds of completed activities aloud. Direct attention towards deviation.
- Critical blockers
- Critical overdue activities
- Forecast threats
- Dependency failures
- Validation failures
- Approval delays
- Emerging risks
One operational truth, multiple views
Executives need outcome, major exceptions, forecast and decisions. Programme managers need workstream health, dependencies, schedule and exceptions. Cutover managers need activity-level sequencing, blockers, overdue tasks, validations and approvals.
Provide role-oriented views from one event record rather than asking each audience to maintain a tracker.
Decision management
A decision record should state the decision required, options, evidence, authority, deadline, outcome and conditions. Decisions should remain connected to the activities, risks and readiness evidence that prompted them.
Silence or a meeting vote without defined authority is not a controlled decision.
Communications
Status updates should be factual, timestamped and audience-appropriate. State what changed, current impact, action, owner and next update. Avoid stale percentages and unqualified colour labels.
Communications must not become a competing execution system.
Command centre anti-patterns
Common failure modes create delay or obscure the real state.
- Managing execution through conference-call narration
- Multiple competing trackers
- Manually consolidating status
- Reporting stale percentages
- Unclear decision authority
- Hiding blockers to preserve green status
- Uncontrolled plan changes
Command centre checklist
Confirm the control environment before go-live.
- Approved baseline identified
- Roles and deputies briefed
- Operational dashboards available
- Critical dependencies visible
- Escalation thresholds agreed
- Decision authority and deadlines recorded
- Communications templates prepared
- Contingency state visible
- Audit trail operating
- Handover to hypercare defined
Give management live operational truth
CutoverCenter Live Mission Control provides role-oriented views of progress, blockers, overdue work, validation, approval, workstream health and management attention.