Two projects compete for the same team. One has a louder sponsor, while the other loses part of its purpose if it finishes after a seasonal decision window. Cost of delay is a way to describe the consequence of delivering later. Use it to expose timing sensitivity, with assumptions and limitations visible.
APM links benefits with portfolio prioritisation. The approach below is an illustrative business decision aid, not a validated financial forecast or a universal project-ranking formula.
Photo by Vitaly Gariev on Unsplash.
Define what later actually changes
Identify the period being compared and the result that would be delayed. Consequences may include continuing manual effort, a missed operating window, deferred capacity or an effect on clients. Some can be estimated credibly; others should remain a qualitative explanation.
Do not turn every proposed benefit into guaranteed revenue. Clarify whether demand exists, whether the business can use released capacity and whether another dependency controls the result.
Use a delay-consequence note
For each option, record:
Deliverable and proposed delay interval.
Benefit or obligation affected by that interval.
Evidence supporting the consequence.
Range, scenario or qualitative limitation.
Dependencies that could change the result.
Non-financial impacts and specialist advice needed.
Decision authority and date.
Keep consequential legal or commercial obligations separate from speculative benefit estimates. Their interpretation belongs with the relevant owners.
A hypothetical sequencing choice
A business is choosing between improving an internal reporting process and preparing a seasonal service offer. The reporting project could reduce recurring effort once adopted. The service offer depends on an external booking window after which its immediate value may reduce.
The sponsor compares a short sequencing delay to each, using actual evidence where available. It might still choose reporting first if the seasonal offer lacks a credible operating route or demand basis. A fixed window is relevant information, not automatic proof that the project deserves priority.
No revenue figures are needed to show the distinction. If the business does use numbers, label the assumptions and have the appropriate finance owner assess them.
Check for double counting and false precision
Do not count the same staff time as cash saving, extra capacity and additional revenue without explaining which outcome is achievable and how. Avoid a spreadsheet result with decimal precision when its inputs are broad guesses.
Sensitivity is often the useful question: which assumption would reverse the choice? If a small change flips the recommendation, the next action may be obtaining evidence rather than committing the team.
Make the trade-off visible afterwards
Record why the sequence was chosen and what would trigger review. Tell the owners of displaced work what the decision means. Revisit the basis when timing, scope or demand changes.
The small-team planning guide connects timing choices to delivery. For the connected task, read Who Owns Project Benefits After Delivery Is Complete?. If project sequence depends on confident numbers nobody can explain, discuss your project requirements.
