Limbo Is Not a Status: A Governance Triage for Dormant UK Initiatives

Every organisation has two portfolios. The first is visible: the projects on the delivery plan, the budgets in the approved column and the milestones reported to the board. The second is harder to see. It consists of initiatives that were paused for a sensible reason and never resumed; pilots that ran out of sponsor attention; business cases that survived a change of director; systems bought but not implemented; restructures announced and quietly deferred. None of this work is live. Very little of it has been formally closed. It occupies the space between.

That space is not neutral. Dormant work continues to shape decisions, consume governance capacity and complicate the planning cycle. The purpose of a triage is not to shame teams for past hesitation. It is to replace an accumulating ambiguity with a set of explicit choices: kill, revive or archive.

The shadow portfolio and its carrying cost

Paused work is often treated as costless because it is not spending at the same rate as active delivery. That is a misreading. Dormant initiatives continue to absorb governance attention, reporting effort and senior management headspace. They appear in risk registers, programme boards and budget conversations. They require status updates that say little and take time to prepare. They hold onto reserved funding, software licences, contractor options and room on delivery roadmaps.

The cost is rarely a single large invoice. It is a series of small, recurring charges against management capacity. A portfolio of twenty dormant initiatives, each absorbing two hours of governance and reporting time a month at a loaded rate of £90 per hour, carries a direct cost of £43,200 a year before any reserved budget is considered. Add the opportunity cost of the decisions those hours displace, and the figure becomes harder to defend.

There are familiar symptoms. Status reports describe an initiative as nearly restarted. The same dependencies are cited quarter after quarter but never tested. The original benefits case has not been revisited since approval. No single person can say who owns the next decision. The work appears on no delivery plan, yet it cannot be removed from the risk register because nobody is certain it has ended.

Why closure is avoided

Closure is often avoided for understandable reasons. Sunk cost creates reluctance to write off effort. A former sponsor may regard the initiative as part of their legacy. Teams worry that closing work will be read as failure rather than as discipline. There may be genuine uncertainty about contractual obligations or customer commitments. And there is always the hope that a quieter quarter will create the capacity to restart.

Hope is not a governance mechanism. A pause without an expiry date, a named decision owner and a restart test is not a pause. It is an unresolved commitment.

A triage in three passes

The first pass is inventory. Assemble a list of every initiative that is neither on the active delivery plan nor formally closed. Sources include PMO records, budget lines, board minutes, risk registers, procurement records and handover notes from departing managers. The list should include internal projects, customer-facing change and technology work. Assign one accountable owner to the triage itself, not a committee.

The second pass is a short test. Five questions are usually enough:

• Is the original outcome still relevant to the current strategy?
• Is there a named sponsor with the capacity to carry the work?
• What is the true restart cost, including re-mobilisation, re-procurement and lost momentum?
• What obligations remain, whether contractual, regulatory or customer-facing?
• What would happen if the initiative were closed today?

The third pass is a disposition. Revive means a dated decision, funded capacity and an accountable sponsor. Kill means an explicit closure note, release of reserved budget and a short record of what was learned. Archive means the work is retained as an asset with defined trigger conditions and a review date, but removed from routine reporting. Archive is not a softer word for abandonment. It is a decision with an audit trail.

Quantifying what the portfolio is holding

A useful carrying-cost estimate does not require perfect data. Multiply governance hours by a loaded hourly rate. Add reporting time, reserved budget, minimum contract charges and the value of senior attention. Include the cost of any licences or subscriptions maintained for work that is not running. Present the total as a range and state the assumptions. The aim is not accounting precision; it is to make visible a cost that has become normalised.

This figure is particularly useful before the next planning cycle. It changes the conversation from whether dormant work should be reviewed to what the organisation would rather fund with the same capacity.

Making the triage stick

A one-off clean-up will not hold unless portfolio reporting changes. Dormant should become a formal status, distinct from active, on hold and closed. A pause should require a restart decision date and a named owner. A quarterly review of dormant initiatives should be short, decision-focused and chaired by someone with authority to close work. Planning gates should require the dormant list to be cleared or explicitly carried forward, not simply inherited.

None of this requires a large programme. It requires a register, a small set of tests and the willingness to record decisions that have been avoided. The most expensive initiatives are not always the ones that are running. Sometimes they are the ones that nobody has been willing to end.

Limbo is not a status. It is an absence of decision. The triage restores the decision, and with it a clearer view of what the organisation is actually choosing to carry.