Excel is excellent at planning
Excel is flexible, familiar, fast, portable and capable of modelling large cutover plans. Its filtering, formulas, bulk editing and offline availability make it a sensible starting point for many programmes.
The problem is not Excel. The problem is asking one artefact to serve simultaneously as plan, workflow engine, execution console, approval system, audit trail and management dashboard.
- Familiar to stakeholders
- Fast modelling and bulk editing
- Powerful sorting, filtering and formulas
- Portable exchange format
- Useful offline planning capability
1. Concurrent execution
During go-live, multiple teams update work simultaneously. Shared workbooks can support collaboration, but programmes must still manage copies, conflicting edits, locks, connectivity and clarity about the authoritative state.
The operational question is whether every participant can update safely without fragmenting the record.
2. Who is allowed to do what?
Live execution may require different permissions for executor, validator, approver, manager and viewer. Worksheet protection can limit editing, but role-aware workflow and project-scoped authority often require more explicit controls.
Governance should prevent an executor from independently approving controlled work while allowing ordinary confirmation tasks to complete without invented bureaucracy.
3. Dependencies become operational
During planning, a dependency is a relationship. During execution it becomes a control: may this activity start yet? A live system can evaluate predecessor state and explain why work is not ready.
In a workbook, teams may need additional coordination to prevent successors starting from stale status.
4. Planned status and runtime status diverge
Consider a task planned for 22:00 to 22:30. Its predecessor finishes at 22:41, it starts at 22:43, completes at 23:06 and remains pending validation until 23:14. The organisation needs both the original baseline and this runtime truth.
Overwriting planned fields removes variance history; adding more columns increases coordination. A governed runtime should preserve the baseline and record events separately.
5. Validation and approval become workflow
Changing a cell to Complete is not equivalent to governed acceptance. Where required, an executor submits, a validator checks the result and an approver records authority and rationale.
The workflow must also handle rejection, correction and resubmission without losing history.
6. Evidence and checklists
Activities may require screenshots, reconciliations, log references, test results or signed checklists. A live control environment can bind that evidence to the activity and acceptance event, with access governed appropriately.
7. Management reporting becomes manual
During live cutover, management asks what is running, late or blocked; which workstream is delaying the forecast; and what needs a decision. If answering requires extracts, reconciliation and manually prepared slides, the management view is already behind execution.
Role-oriented dashboards should derive from the same current events, with clear definitions and timestamps.
8. Audit history and version control
A controlled event history records who changed status, submitted evidence, validated, approved or changed the plan. Version governance preserves what was approved for rehearsal or go-live and why it evolved.
File history helps recover documents, but it is not automatically an activity-level governance record.
9. Rehearsal learning
Rehearsal findings should connect back to affected activities, dependencies and durations. Controlled plan evolution makes it possible to show how evidence changed the next baseline rather than relying on a separate lessons log.
Do not replace Excel. Give it an operational boundary.
Keep Excel where it is strong: discovery, modelling, review, bulk editing and governed exchange. Move the approved baseline into an environment designed for concurrent execution, permissions, evidence, dependencies, decisions and live reporting.
CutoverCenter supports governed Excel import and export so teams can retain familiar planning workflows without asking the workbook to become the command system.
When is Excel probably enough?
A workbook may be sufficient for a small, low-risk transition with few participants, simple dependencies, limited governance and no need for live management reporting. As scale, concurrency, regulatory evidence or business consequence increases, assess whether additional operational control is proportionate.
The choice should follow risk and operating needs, not a blanket technology rule.
Keep familiar planning and add execution control
CutoverCenter provides a governed boundary between flexible planning and live enterprise execution.