Close the programme and keep the unfinished obligations owned

The library has reopened. Staff can use the new rooms, the contractor has handed over the keys, and the programme team is preparing to leave. A ventilation warranty claim remains open. One supplier invoice is disputed. The promised improvement in room availability will not be assessed until the next operating quarter.

These unfinished items need somewhere to go when the programme closes. A closure report that merely lists them can leave operations with responsibilities it has never accepted and no funding or access to resolve them.

Decide what closure means for this programme

Separate the decision to close the programme from acceptance of the delivered service and from later benefit evaluation. They can occur at different times and involve different authorities. Use the operational handover guide for the wider transition; this article concentrates on the obligations that remain after the temporary team leaves.

The UK government's GovS 002 standard includes transfer of continuing responsibilities as part of closure. It also expects decisions and outstanding matters to be handled through appropriate governance. That is guidance for its government context, not a universal private-sector closing rule. GovS 002, closing a programme or project

For the fictional library, the closure authority needs to know which obligations can transfer now, which require a decision and which prevent the proposed closure scope. The scheduled last day of the team cannot answer those questions.

Build an accepted obligation register

Start with the actual remaining work, including commitments held outside the project tracker. Check contracts, unresolved incidents, financial exceptions, records access and planned benefits reviews with the people responsible for those areas.

These are proposed assignments for the example. A person's name in a spreadsheet is not their acceptance. Ask the receiving owner to confirm that the obligation is understood and that the required authority, capacity and resources are available. Retain the acceptance and any conditions beside the obligation.

The warranty case illustrates why this matters. Facilities may understand the defect but lack the contractor correspondence. Procurement may hold the correspondence but have no instruction to continue the claim. Transferring both documents to a shared folder does not settle who is allowed to agree the remedy.

Resolve an unaccepted transfer before dissolving its owner

Suppose the facilities manager declines the claim because the proposed investigation requires a specialist budget that was never transferred. The programme has an unresolved governance decision. It should not mark the item complete or assume that the facilities team will absorb the work later.

Bring the gap to the authority that can fund or change the arrangement. Possible decisions include transferring a funded obligation, retaining a small temporary capability, or changing the proposed closure scope. Record what remains open, who now owns it and the evidence that will allow the next decision.

Ending enhanced launch support is another distinct event. A service may leave hypercare while a programme still has commercial obligations. Conversely, a programme may close after transferring an accepted support arrangement. Neither event should be used as a shortcut for the other's decision.

Preserve a route back to the evidence

After closure, the receiving owner should be able to reconstruct why an item exists without asking a former team member to search an old laptop. Retain the relevant decision, source record, current state and next due action in the approved record system. Apply the organization's actual access and retention rules; closure does not authorize keeping every personal record indefinitely.

Test the handover using one unfinished item. Can the new owner find the latest contractor response, identify the decision they are authorized to make and locate the funding or escalation route? Record any missing access before the temporary account or support arrangement disappears.

For the library's benefits review, preserve uncertainty as well as the target. The benefit-realization article explains why a delivered room cannot prove an improvement in service availability. The receiving service owner needs the measurement and decision responsibility, not a prefilled claim of success.

The closing record should state the decision taken, its effective scope and the destination of each accepted continuing obligation. When someone opens the warranty case a month later, the organization should still have an owner who can act.

The library programme and obligation register are illustrative. Primary guidance was checked on 25 October 2026.