Capital Discipline
How to keep the value case live after approval
A business case supports approval. A live value case keeps the approved intent connected to current assumptions, forecasts, evidence and decisions after approval.
Wovex
•

A business case helps an organisation decide whether to proceed. A live value case helps it keep reviewing whether the intended value still makes sense as delivery, evidence and circumstances change.
The live value case does not replace the approved business case. It keeps the original intent connected to the current position: assumptions, ownership, baselines, forecasts, actuals, variance, confidence and decisions.
Approval should begin an ongoing value-management cycle, not turn the rationale into a historic document.
Why value logic often goes stale after approval
A great deal of effort often goes into gaining approval. The case for change is developed, options are assessed, benefits are described and decision-makers agree to proceed.
Then delivery reporting takes over.
Meanwhile:
assumptions change;
forecasts move;
owners change roles;
dependencies become clearer;
evidence arrives;
scope and timing are adjusted; and
decisions alter the route to value.
When those changes are not connected back to the approved intent, the organisation may still be managing delivery, but it is no longer actively managing the same value case it approved.
The original document remains important. The problem is treating it as the only view of the value case.
Business case and live value case: related but different jobs
Instrument | Primary job | Typical point of emphasis |
|---|---|---|
Business case | Support an approval or investment decision | Rationale, options, expected costs, benefits, risks, affordability and delivery arrangements |
Live value case | Support continuing review after approval | Current expectations, ownership, evidence, variance, confidence, decisions and changes from the approved position |
The two should be traceably connected. A live value case should show where the current view came from and how it has changed. It should not silently overwrite the approved position, because that removes the comparison leaders need.
The minimum information a live value case should preserve
A proportionate live value case normally needs seven connected elements.
1. Approved intent
What problem or opportunity justified the investment? What value was expected, for whom and over what period?
Preserve the approved position as a reference point. This gives later reviews something stable to compare with.
2. Outcomes and benefits
State the changes that should result from the initiative and why they matter. Keep outputs, outcomes and benefits distinguishable so that completion of work is not mistaken for value.
3. Accountable ownership
Record who is responsible for enabling, monitoring and responding to the expected value. A name in a field is not enough if the person lacks authority, information or an active review role.
4. Measures and reference points
Connect each material benefit to suitable evidence. Include the baseline, current forecast, target and relevant tolerances where these genuinely support decisions.
5. Assumptions and dependencies
Make visible the conditions on which the value case depends. Examples might include adoption, policy decisions, partner behaviour, data quality, operational capacity or complementary initiatives.
6. Evidence, variance and confidence
Show what the current evidence says, how it differs from expectation and how confident the organisation should be in the interpretation. Do not hide uncertainty behind a confident summary.
7. Decisions and rationale
Record material decisions, who made them, what evidence was available and why the decision was reasonable at the time. This keeps the value case connected to action rather than turning it into a passive register.
A practical method for keeping the value case live
The method below can fit an existing monthly, quarterly or stage-gate rhythm. The frequency should reflect the scale, uncertainty and decision needs of the investment.
Step 1: Preserve the approved position
Keep the approved benefits, assumptions, forecasts and decision context as a dated reference. Do not overwrite them when the current view changes.
Step 2: Update the current forecast
Ask whether the latest expected value, timing and confidence have moved. Explain the reason for material change rather than simply replacing the number.
Step 3: Review assumptions, dependencies and ownership
Identify which conditions have strengthened, weakened or become irrelevant. Confirm that the accountable owner still has the authority and information needed to act.
Step 4: Add current evidence
Bring together the most decision-relevant evidence. This may include quantitative measures, operational observations, stakeholder feedback, adoption signals and qualitative explanation.
Evidence should be proportionate. Collecting everything can be as unhelpful as collecting nothing.
Step 5: Explain variance and confidence
Compare actuals and forecasts with the relevant baseline, target or approved expectation. Explain what changed, why it matters and what is still uncertain.
Step 6: Make and record the decision
Decide whether to continue, correct, accelerate, reshape, pause, stop, collect more evidence or accept the current position. Record the owner, rationale and next review point.
Step 7: Create a dated snapshot
Preserve the current position so that future reviewers can see what was known and decided at that point. The live case should evolve without erasing its history.
Illustrative scenario: a service transformation changes direction
This is an illustrative scenario, not a customer case study.
A service transformation is approved on the expectation that a new operating model will reduce avoidable contact, improve response times and lower the cost of handling each case.
Six months into delivery, the technical work is progressing, but a policy change increases the complexity of the cases entering the service. The original cost forecast is no longer realistic. Early evidence also shows that one customer group needs more support than expected.
A static business case would leave the approved assumptions unchanged while the delivery team reports progress against milestones.
A live value case would:
preserve the original approved expectation;
record the policy change and its effect on the assumptions;
update the forecast and confidence level;
distinguish the value impact for different customer groups;
identify the decision to redesign part of the operating model; and
record when the new evidence will be reviewed.
The purpose is not to make the original case look right. It is to give leaders a current, traceable basis for deciding whether and how the investment should continue.
A useful review rhythm
A live value case should be reviewed when the organisation can use the result. Useful triggers include:
a scheduled value or portfolio review;
a material forecast change;
a breached tolerance;
a change in strategy, scope or external context;
a major delivery decision;
new evidence that changes confidence; or
a change in accountable ownership.
The review should be light enough to sustain and strong enough to support the decision. High-risk or novel investments may need more frequent evidence and deeper challenge. Stable, lower-risk benefits may need less.
Common failure modes
Updating the forecast without preserving the original
This makes it difficult to explain how expectations changed. Keep both the approved and current positions.
Treating every change as a failure
Forecasts should respond to evidence. A well-explained downward revision may demonstrate stronger management than an unchanged but unrealistic promise.
Maintaining a register with no decision rhythm
A register can preserve information, but it does not create ownership or action by itself. Connect it to named reviews and decisions.
Assigning ownership without authority
An owner who cannot influence adoption, operations, resources or decisions may only be a reporter. Confirm what the owner can actually do.
Collecting evidence after the decision point
Evidence is most useful when it arrives in time to shape a choice. Design the collection rhythm around known review and decision needs.
Live-value-case review checklist
Use this short checklist in an existing governance meeting:
What value was approved?
What is the current forecast, and what has moved?
Which assumptions or dependencies have changed?
What does the latest evidence show?
How confident are we, and why?
Who owns the response?
What decision is required now?
What should be preserved for the next review?
What a live value case cannot guarantee
Keeping the value case live does not guarantee benefits, prove causality or make a decision automatically correct. It does not remove uncertainty or replace formal business-case, finance, risk or delivery governance.
It does improve the organisation’s ability to see how the rationale is changing, make decisions using current evidence and explain those decisions later.
The value case must stay live after approval because the conditions that create value do not freeze when permission is granted.
Continue with practical guidance in the Wovex Knowledge Base.