Delay usually produces another plan. Milestones move, reporting changes and a recovery lead presents a new completion date. That plan may improve delivery, but it does not answer whether the remaining programme deserves funding.
Treat continuation as a fresh investment. Compare the cash, staff time and disruption still required with the value available today. The original budget describes history. It sets no floor for future spending.
What the delay revealed
A missed date may expose an execution problem inside an otherwise sound case. It can also reveal a vague product, an infeasible integration or a vendor dependency that nobody priced. Sometimes the business cannot absorb the process change. Calling every one of these a delivery delay conceals the decision in front of management.
The benefit can decay while the team works. Customers adopt another process, a commercial window closes or expected savings are assigned elsewhere. The chosen architecture may now cost more to maintain than the system it would replace. Recalculate the remaining spend and the remaining benefit from the same date.
- Scope: compare the current backlog with the product that received approval.
- Evidence: record what delivery has shown about demand and feasibility.
- Cost: include transition work, support and the management time still required.
- Benefit: recalculate the expected result on the revised launch date.
- Alternatives: price a narrower build, a purchase and continued use of the current process.
- Exit: identify contracts, roles and dependencies that make a change expensive.
Sunk cost and usable work
Past spending gives no basis for another release. The programme may still have produced assets worth keeping: cleaned data, a proven integration, reusable components or a team with a sharper understanding of the domain. Price those assets into each option now under consideration.
A narrower service might keep the completed integration and discard the rest of the scope. A purchased platform could use the cleaned data. Closing the programme may release specialists for another commitment. The recovery value differs across those choices and should appear beside their transition costs.
Options for the next commitment
- Continue the current scope under the revised cost and schedule.
- Fund one milestone that resolves the largest open technical question.
- Narrow the product around the benefit with the strongest evidence.
- Rebuild the investment case around a different delivery plan.
- Pause until a named customer, vendor or operating condition is secured.
- Close the work and manage the contractual, technical and staffing exit.
Put transition cost beside every option. Closure can trigger contract payments and migration work. Continuation can extend duplicate systems and scarce staffing. Both belong in the comparison.
Controls for another release
A date provides a forecast, not a spending control. The continuation record should fix the funded scope and assign each dependency. It should also name the evidence required for the next release, such as an accepted integration, a cost ceiling or signed operational ownership.
Report against those conditions. A rising ticket count can coexist with a deteriorating economic case. The decision owner needs the cost to reach the next gate, the evidence gathered since approval and any movement in the expected benefit.
Independent Continuation Review
An Independent Continuation Review compares the approved initiative with the programme now requesting money. It checks the original conditions, evidence gathered during delivery and changes in scope, then prices the options still available. Programme management stays with the client team.
The opinion may support another release, a smaller scope or an exit. A six-month extension that depends on one unresolved integration should identify the owner, test date and spending cap for that dependency before work resumes.