Cutover
A cutover runbook that shows whether go-live is on time, step by step.
Every runbook step has planned and actual times, an owner and a backup, and the step it depends on. Variance shows when a step finishes late, and a delayed step flags the steps that follow it.
A go or no-go step cannot be marked complete until someone signs it off. Load the runbook from an Excel template and rehearse it in a cutover dry run test cycle.
Cutover
A timed runbook with owners, predecessors and go or no-go sign-off.
What the module covers
Planned against actual
Record actual times as each step finishes. Variance and downstream impact update as you go.
Owners and backups
Each step names who does it and who covers, because cutover weekends are long.
Go or no-go with sign-off
Decision points in the runbook need a named sign-off before they count as done.
Built from your template
Import the runbook from Excel, or generate a starting plan and adjust it to your programme.
In the app, this module is these workspace tabs:
- Cutover
How a programme uses it
Write the runbook
Import the steps with owners, backups and durations, then set each step's predecessor.
Rehearse it
Run a dry run as a test cycle and record actual timings against the plan.
Run the weekend
Record actual times live. The team sees variance and the next go or no-go point in one place.
Where it helps most
Client-side PMOs
Run the cutover from one runbook that everyone on the bridge call can see.
CommandCC for client-side PMOsCIOs and programme directors
Know before the go or no-go call how far the cutover is from plan, and why.
CommandCC for CIOs and programme directors
Cutover: common questions
Can we rehearse the cutover in CommandCC?
Yes. Testing has a cutover dry run cycle, and the runbook records actual against planned times, so each rehearsal shows where time is lost.
What happens at a go or no-go point?
The step needs a named sign-off before it is complete, so the decision and the person who made it are recorded in the runbook.
See this module with your programme in mind.
Tell us which application you are implementing and where the programme is today. We will show you how this module would hold your work.