An opening is an important event. It gives a project a visible result and the institution a point at which to recognise the work involved. I do not want to diminish that achievement. I do want the operating account to survive it. A new area may be available for its intended purpose while some maintenance responsibilities still rely on project personnel, temporary support or knowledge that has not reached the receiving team. The opening milestone does not answer who will sustain the place after those arrangements change.
That question can become difficult precisely because the project has already been declared successful. A request for further support expense may sound like an attempt to reopen a completed decision. Receiving managers may be reluctant to identify limitations if doing so appears to challenge the achievement of colleagues who delivered the project. I want those concerns discussed as part of the operating transition, with enough precision to distinguish unfinished ownership from a general allegation that the project has failed.
Completion has more than one meaning
Construction, installation, technical acceptance and readiness for particular activities can each have their own evidence and responsible decision-makers. Enduring maintenance ownership is connected to those matters but is not identical to them. The organisation needs to know who will arrange support, maintain the relevant records, recognise when a specialist decision is needed and carry unresolved questions forward. Those responsibilities should not be inferred solely from the fact that the area has opened.
In our 2023 expansion review, we identified thirty-six maintenance and support responsibilities that required an enduring arrangement. Twenty-seven had an agreed receiving owner and the relevant support account. Nine still depended on transitional arrangements. The distinction allowed us to discuss a specific operating requirement. It did not negate the project’s completed milestones, and it did not allow the COO to replace technical acceptance or independent quality decisions with a broad judgement that the area was ready.
The tension lay in who should absorb the remaining work. Some project colleagues believed that the receiving organisation should take it on immediately. Receiving managers pointed to missing knowledge, records or support conditions. Both positions contained a legitimate concern. A project cannot remain permanently responsible for ordinary operations, but an operating team cannot acquire capability merely by being named as the owner. The useful discussion was what each of the nine responsibilities still required and which evidence would support a complete transfer.
I supported a CNY 4.7 million temporary-support allocation while that work proceeded. It was additional expense after a substantial capital programme, and it deserved challenge. The case for it was not that every request from the receiving team had to be funded. It was that the identified responsibilities needed a credible arrangement while their enduring conditions were resolved. The allocation gave management a way to examine the transition instead of allowing an incomplete handover to become an unpriced assumption inside the operating plan.
Temporary support should retain an exit condition
A temporary arrangement can quietly become permanent if nobody knows what would allow it to end. It can also be ended too early if the project date is treated as sufficient reason to withdraw it. I want a defined responsibility, a receiving owner and a practical account of the condition that remains. The condition may concern knowledge, records, access to specialist support or another requirement identified by the appropriate participants. Its resolution needs evidence rather than a new label in the project report.
During the reporting period, six of the nine transitional responsibilities moved to their agreed enduring arrangement. Three remained under temporary support. Those numbers describe responsibility transitions, not thirty-six pieces of equipment or nine technical defects. The CNY 4.7 million was an approved allocation, not a claim that the entire amount had been spent. Keeping those definitions visible mattered because a broad completion statement could easily make the result appear larger and more final than the underlying account.
The receiving owner should participate before the final handover discussion. Someone who will sustain the arrangement can often identify a practical dependency that is not prominent in the project plan. That input should be specific enough to act on. An indefinite request for more preparation is no more useful than an unsupported declaration that the team must accept responsibility now. The participants need a shared view of what is required, who can provide it and how the institution will decide that the arrangement is adequate.
Temporary support must also preserve the relevant boundaries of authority. A provider helping the receiving team does not acquire unrestricted control over the area, and an operating manager does not become a substitute for independent specialist approval. The responsibilities should be connected clearly so the transition does not create a gap or two conflicting assumptions about who decides. My role is to make that operating account coherent, including when the honest answer is that a particular responsibility remains transitional for longer than management hoped.
Bring the receiving organisation into the project earlier
The best correction would have been to begin the ownership discussion earlier. By the time an opening is imminent, the organisation has fewer options for addressing missing preparation without expense or delay. The project team may already be moving to another assignment, and receiving managers may be trying to absorb new work alongside their existing responsibilities. An earlier discussion makes the sustaining arrangement part of the project’s purpose rather than an additional burden discovered after the visible delivery is complete.
That does not require operating managers to take over every project decision. Their contribution should concern the responsibilities they will inherit and the conditions needed to exercise them. Project specialists retain their expertise, and technical acceptance retains its own process. The aim is a more complete relationship between building the area and sustaining it. A clear boundary can improve cooperation because each participant understands which question they are being asked to answer rather than feeling responsible for the whole project without a clear boundary.
The board-facing account should preserve the same distinctions. Directors should be able to understand the milestone achieved, the responsibilities transferred and the transitional work that remains. A temporary-support cost can then be examined alongside its purpose and exit conditions. Reporting only the opening would omit an important operating limitation; reporting only the open transition items could obscure substantial work already delivered. A balanced account makes both visible without forcing every part of the project into one completion percentage.
My lesson is that an enduring owner is part of the operating result, not an administrative detail to settle after the celebration. The three responsibilities still under support mattered because real work would depend on them after the project team had gone. I would rather preserve that unfinished account than gain a cleaner completion statement by letting it disappear. A project’s visible milestone deserves recognition. Its continuing usefulness deserves an equally serious conversation about the people, knowledge and support that will sustain it.