The premium template for the messy reality of ERP cutover — the days before, the cutover weekend itself, the hypercare period that always overruns, and the steady-state handover that finally closes it. Built for transformation directors, programme managers, and ops sponsors who have been burned by hypercare that never ended.

💎 Hypercare is not a phase — it's a contract.

The single most expensive mistake on an ERP cutover isn't a botched data migration. It's hypercare with no named exit criteria. The business keeps the warranty open, the programme team can't demobilise, the integrator keeps billing, and the new platform never feels owned.

This pack fixes that. Every measurable exit criterion is named, evidenced, and signed off — before steady-state begins.

Why this exists — the 2026 context

The ERP buying spree of 2020-2022 is now hitting delayed go-lives across Q3-Q4 2026. PwC's 2026 Operations Survey found 89% of digital transformations underdeliver against business case. Boards have stopped accepting hypercare as a fuzzy "few weeks of extra support." They are now asking transformation leads to commit to named, measurable exit criteria before the programme can be demobilised.

SaaS deployment management platforms start at £20,000+ per cutover. For a single mid-market ERP go-live, that's not credible. Notion is the credible scaffold.

Who this is for

💡 Use this if you are…

• A Transformation Director running a cutover programme and the steerco is asking for hypercare exit criteria

• A Programme Manager trying to get integrator partners off the project so internal teams can own the platform

• A Head of Ops / VP Ops sponsoring an ERP cutover and you've been through one before that never properly ended

• A PMO Lead standing up a cutover for the first time and you need a credible runbook before the cutover weekend

How to use this pack

1. Pre-cutover (T-12 to T-1 weeks) — Build the Cutover Plan database. Every deployable activity, owner, time-box, dependencies, dry-run result, go/no-go gate. Run two dry-runs minimum.
2. Cutover Window (T-0) — Switch to the Cutover Window Runbook. Hour-by-hour task list owned by the cutover lead. One pane of glass for the cutover weekend.
3. Stabilisation (T+1 to T+7 days) — The first week post-go-live. Triage everything into the Hypercare Issue database. Don't fix in production yet — log, classify, prioritise.
4. Hypercare (T+1 week to exit) — Burn down the issue log against the Hypercare Exit Criteria. These are the named contract — measurable, evidenced, signed.
5. Exit Criteria sign-off — When every criterion is GREEN and held for the required window, sponsor, IT lead, and integrator co-sign the exit gate.
6. Steady-state Handover — The Steady-state Handover Pack transfers ownership: RACI to BAU, support model to service desk, escalation map to the new owners.