The Signed Business Case Is a Starting Gun, Not a Finish Line

There is a particular moment in UK project delivery when a business case stops being a working document and becomes an artefact. It is signed, minuted and filed. The delivery team moves on. The assumptions that underpinned the case — costs, benefits, timelines, operational capacity — are left to age quietly in a shared drive.

This is not a failure of diligence at approval. It is a failure of routine after approval. The signed business case is treated as evidence that the right questions were asked, when it is better understood as a snapshot of what was believed at a particular point in time. Delivery then proceeds against a document that no one is actively testing.

The consequence is familiar. Commercial decisions are made against stale figures. Operational teams plan for benefits that have shifted shape. Delivery teams manage scope that no longer matches the original rationale. No single decision looks unreasonable, but the join between commercial, operational and delivery thinking weakens month by month.

The answer is not another governance committee. It is a lightweight live-case routine that keeps the original case honest without turning it into a bureaucratic burden.

The filing-cabinet problem

Most business cases are written to secure approval. That is their immediate purpose, and they are often good at it. They present a compelling case, summarise costs and benefits, and address the questions that approvers are likely to ask. Once approval is granted, the document has served its primary function.

The problem is that the assumptions inside it have not stopped moving. Supplier rates change. Operational volumes differ from forecast. Recruitment takes longer than planned. Regulatory requirements shift. Benefits that looked achievable in year one now depend on a dependency that has slipped. None of this means the original case was wrong. It means the case is now a historical record rather than a live instrument.

In UK organisations, this gap is often filled by informal recollection. Someone remembers that the benefits case assumed a particular level of take-up. Someone else believes the cost envelope included a contingency that has since been used. The delivery team works with the version of the case that exists in conversation, not the version that was approved.

That is a fragile basis for decision-making. It is also avoidable.

A live case is not a new committee

The phrase 'keeping the business case alive' can sound like an invitation to create a standing group with a terms of reference and a quarterly reporting line. That is precisely what it should not mean.

A live-case routine is a small set of practices that sit inside existing delivery governance. It does not need a new board. It does not need a separate paper cycle. It needs a named owner, a short list of assumptions that matter, and a rhythm for checking whether those assumptions still hold.

The test of whether the routine is working is simple: can a delivery lead, a finance business partner and an operational manager each explain, without digging through files, which assumptions are currently under pressure and what is being done about them? If the answer is yes, the routine is doing its job. If the answer requires a meeting to establish, it is too heavy or too detached.

Owned assumptions, trigger points and evidence checks

The core of the live case is a short assumption register. Not every assumption in the original document — only the ones that would change a decision if they proved false. In practice, that is usually a handful: the cost of a key resource, the volume of demand, the availability of a critical dependency, the timing of a benefit, the operational capacity to absorb change.

Each assumption should have a named owner. Not a team name. A person who is accountable for monitoring it and speaking up when it moves. The owner does not need to be senior. They need to be close enough to the evidence to notice change.

Each assumption should also have a trigger point. This is the threshold at which the assumption is no longer safe to leave unexamined. For example: if supplier day rates rise by more than a stated percentage, or if demand falls below a stated volume for two consecutive months, or if a key recruitment milestone slips by more than four weeks. Trigger points turn vague concern into a specific prompt for review.

Finally, each assumption should have an evidence check. This is the lightest part of the routine: a periodic look at whether the evidence still supports the assumption. It might be a monthly glance at actuals against forecast, a quarterly conversation with a supplier, or a review of operational data. The evidence check should be proportionate to the risk. Not every assumption needs a dashboard.

Keeping the routine light

The most common objection to this kind of routine is that it will become another meeting. The way to prevent that is to attach it to forums that already exist. A delivery board can review the assumption register as a standing item. A finance business partner can check the cost assumptions as part of regular budget monitoring. An operational lead can confirm demand assumptions in an existing performance conversation.

The live case does not need its own agenda. It needs a home in the agendas that already exist.

A second objection is that the original business case is too long or too technical to revisit. This is where the assumption register earns its keep. It extracts the small number of things that matter and leaves the rest of the document as reference material. The register becomes the working摘要 of the case — not a summary of its prose, but a summary of its live risks.

A third objection is that no one has time. In practice, the time required is modest: perhaps an hour a month to maintain the register, plus the cost of acting when a trigger point is reached. The alternative — discovering eighteen months into delivery that the commercial case has quietly evaporated — is more expensive.

Joining up commercial, operational and delivery decisions

The deeper value of the live-case routine is not compliance. It is coherence. When assumptions are owned and visible, commercial decisions can be tested against delivery reality. Operational teams can see which benefits depend on their capacity. Delivery teams can understand why a cost envelope is shaped the way it is. The conversation shifts from 'the business case says' to 'the business case assumed, and here is what we now know'.

That shift matters in UK organisations where business cases often cross organisational boundaries. A local authority case may depend on partner capacity. An NHS trust case may depend on recruitment that sits with a regional body. A private sector case may depend on a supplier relationship managed by a different function. A live case makes those dependencies explicit and gives them a routine home.

None of this requires a new governance layer. It requires a modest discipline: treat the signed business case as a starting gun rather than a finish line. Keep the assumptions owned. Set trigger points. Check the evidence. Let the case evolve as delivery teaches you more.

The document on the shelf will not tell you when it has become out of date. A live routine will.