Cover photo: Dallas Penner / Unsplash. Illustrative photograph, not a client project.
Define the service entering operation
The technical release can be complete while the service desk has no escalation route, the weekend shift has not practised the new process and the business owner is still expecting the project team to handle exceptions.
An operational readiness checklist brings that evidence into one decision. It covers the people, procedures, technology and external dependencies needed to operate a changed service. It should say what is ready, what remains open and who has authority to accept the remaining risk.
This is programme-wide transition into operation. It is broader than accepting an AI supplier’s deliverables or transferring code and accounts when a software agency leaves. Start by naming the service boundary: users, locations, operating hours, transaction types and what remains on the old process.
Agree readiness criteria while there is time to meet them
The Local Government Association’s transition guidance covers organisational and technical readiness, rollback, clear responsibilities and operational knowledge. It is a useful UK local-government reference, not a UAE regulatory checklist. The example criteria below are a working method to tailor with your service owners.
| Area | Evidence to request | Who accepts it |
|---|---|---|
| People | Named shift cover and completed role practice | Operations lead |
| Procedures | Approved normal and exception paths | Process owner |
| Support | Exercised incident and escalation route | Service owner |
| Data | Reconciliation against agreed tolerances | Data owner |
| Cutover | Rehearsed sequence with stop points | Cutover lead |
| Recovery | Tested recovery route and limits | Accountable service owner |
| Communications | Approved messages and support contacts | Business-change lead |
Specify the scope and version of each piece of evidence. A rehearsal of last month’s process may not prove readiness for this week’s change. Set criteria before reviewing the result; otherwise a failed test has an unfortunate habit of becoming an accepted exception.
Rehearse an exception, not only the happy path
Imagine a fictional case-management rollout across a head office and two regional teams. The new process works for an ordinary case, but a missing reference number sends the user into a queue nobody monitors.
A useful rehearsal follows that case from intake to resolution. The receiving team must identify the exception, route it to the correct person, record the action and tell the user what happens next. Include an unavailable approver or a support handoff outside head-office hours. These tests reveal operating gaps that a successful software demonstration will not.
Record observed results and defects rather than “training complete”. Attendance proves someone attended. It does not prove the shift can complete the work. Where the test uses simulated data, say so and record what cannot be inferred about production volumes, integrations or access.
Make the go/no-go record explicit
Set the decision time, chair and quorum in advance. The record should identify the release scope, evidence reviewed, unmet criteria, decision and conditions. Name who accepted each residual risk, within their authority, and when it must be reviewed.
A suggested rule is to withhold approval if a mandatory safety, legal, security or continuity condition is unmet. For lesser defects, the accountable owner may consider a bounded workaround with a named operator and expiry. Do not average a critical failure into an otherwise high readiness score.
In the fictional rollout, an unowned exception queue is a no-go for the affected process. A documented workaround with trained cover might support a limited release, but only if the service owner accepts its capacity and risks. The checklist records that reasoning; it cannot authorise it.
A conditional go needs conditions someone will actually check. Record what happens if they expire, fail or stop being true.
Separate rollback from wishing the change away
Work backwards from the last point at which reversal is safe. A backup may restore software and data without reversing messages already sent, transactions already completed or manual actions already taken. Record these irreversible effects and how reconciliation would work.
The cutover runbook needs ordered steps, owners, timings, evidence and stop points. Give one person authority to pause execution and identify who decides whether to resume, roll back or use the continuity procedure. Confirm the receiving teams are available at those times, including suppliers in other time zones.
After launch, use a defined stabilisation period with named cover, issue triage and service measures. Exit enhanced support only when agreed conditions are met, such as manageable incident volume, accepted ownership and closure or transfer of outstanding defects. Avoid an arbitrary Friday handover that leaves nobody accountable on Monday.
Use the worksheet to assemble evidence and record the decision. Keep the detailed runbook, confidential incidents and sensitive customer data in your own controlled systems; the CSV only needs their references.
Practical questions
Who should make the final go-live decision?
The person or forum with delegated authority for that service and release. The project team supplies evidence and a recommendation. The operational owner must be involved because the decision creates responsibilities that continue after delivery.
Can we launch with open defects?
Sometimes, where the authorised owner accepts a clearly bounded residual risk and a workable control exists. Identify the affected users, consequences, owner and expiry. An unmet mandatory condition must not disappear inside an aggregate readiness score.
What if a release cannot be rolled back?
Say so before the decision. Assess staged rollout, pause points, continuity arrangements and forward recovery. Reconcile effects already created. A plan that requires reversal of an irreversible action is not a recovery plan.
Use the worksheet
Download the editable worksheet (CSV) ↓
Open the CSV in your spreadsheet application, replace the illustrative entries and add rows for your programme. It contains plain values, no formulas or macros. Keep evidence references in the sheet and sensitive supporting material in your own controlled systems. Nothing is submitted through this download.
Reviewed 8 November 2026. Examples, figures and working methods are illustrative editorial material, not measured client results, professional certification or a substitute for your organisation’s required approvals.

