← Back to the blog

Blog

Project Handover: Who Owns Operations Afterwards?

A project handover is only complete when operations can genuinely take responsibility. A GPM article from 5 October 2026 describes a gap that keeps recurring: the closure report names a person, but the mandate, deputy, budget, support channel and measures behind that name are missing.

This goes beyond documentation hygiene. PMI’s Benefits Realization Management Framework draws an explicit line between delivery and sustaining benefits. As a project moves into business as usual, accountable owners should keep tracking actions and outcomes. The UK Government Digital Service takes a similar line: readiness criteria agreed early, plus a clear go/no-go decision by the senior responsible owner.

Formal accountability is not operational readiness

A steering committee should ask for evidence in five areas:

  • Ownership: A named person takes on the permanent task, backed by a deputy and decision authority.
  • Rules: The new process is binding and covers change rights and exception paths.
  • Budget: Running costs, residual work and external support sit under an assigned cost centre.
  • Support channel: Questions and non-standard cases must not flow back to a project team that no longer exists.
  • Measurement: Adoption, deviations and benefits continue to be tracked after go-live against agreed metrics.

In software projects, I often see technical acceptance worked out in more detail than the first four weeks of operations. Test and UAT triage function as long as the project is staffed. Afterwards, there may be no owner to prioritise, no budget for residual defects and no decision log for exceptions. The risk has not gone away; it has simply moved to a different organisational address.

Hypercare belongs in the project plan

The initial support period should not be treated as informal help after closure. Give it a duration, a budget, an escalation route and measurable exit criteria. A practical criterion might be that critical defects stay below the agreed threshold for four weeks, that every open exception has an owner and a due date, and that operations confirm acceptance.

None of this means blocking closure indefinitely. Open items can be consciously accepted, but they must remain visible, time-bound and assigned to a body that still exists once the steering committee has dissolved.

What project sponsors should do now

Add a binding “handover to operations” section to the project charter and the closure checklist. Ask for evidence of authority, cover, budget, support and measurement, not names alone. Before approval, walk through one real exception: who decides, who pays and where is the decision recorded?

Whether the project can deliver is not the real question. What counts is whether operations can act tomorrow without the project team.

← Back to the blog