A project report can be full of progress photographs and still fail to answer the director's central question: what will it take to finish?
Expenditure to date is part of that answer. The remaining work, unresolved scope, outstanding decisions and delivery constraints are the rest. Without them, management may be looking at a detailed account of activity while the expected final outcome remains unclear.
The report should give the owner a current forecast, explain the movement since the previous forecast and identify the decisions that can still influence the result. That is the basis on which directors can intervene usefully.
Keep authority, forecast and cash separate
The approved budget records the authorised financial baseline. The forecast expresses the current expectation of the total cost. Cash paid shows the payments made. These figures should be connected, but they should not be used interchangeably.
A low payment total may reflect delayed invoicing or payment terms rather than low project cost. A forecast above the budget may include a risk exposure that has not been authorised. A proposed change may need to be visible without being represented as an approved instruction.
The report should make these distinctions explicit. Directors then know whether they are being asked to approve expenditure, recognise a forecast movement or resolve uncertainty about scope.
Build the forecast from the remaining work
For each significant package, establish the cost incurred on the agreed reporting basis and the cost still expected to complete it. Reconcile orders and contracts so that amounts already included in incurred cost are not added again as remaining commitments.
As a numerical illustration, recorded costs of $140,000 plus an estimated $135,000 still to complete produce a forecast of $275,000. Against an approved budget of $250,000, that is a $25,000 adverse variance. If the $135,000 already includes the unpaid balance of relevant orders, adding those orders again would overstate the forecast.
The calculation is straightforward. The quality lies in the estimate of what remains.
Ask the delivery team to identify remaining quantities, expected rates, procurement status and the assumptions governing completion. Compare the estimate with physical progress and the latest programme. A package reported as nearly complete should not retain an unexplained large remaining allowance; equally, substantial unresolved work should not disappear behind a high completion percentage.
GAO's cost and schedule guides are useful references for maintaining an estimate against a defined scope and programme. The owner's report should apply those disciplines at a level proportionate to the project.
Explain the movement since last month
A forecast is more informative when management can see why it changed. Separate approved scope changes, revised quantities or rates, programme effects and newly identified exposure.
This prevents the current total from becoming a number that is repeatedly overwritten without a clear history. It also allows the owner to distinguish deterioration in the original work from an intentional increase in the project scope.
Contingency needs similar care. State what it covers and how it is being managed. Do not include the same risk in a package estimate and again in a general allowance. When a risk becomes an identified cost, explain the transfer and the remaining exposure.
A single expected figure may need a supporting range where major uncertainty remains. The range should arise from identifiable assumptions. It should not be used to obscure a known overrun or imply a level of statistical confidence that has not been established.
Turn unresolved issues into a decision schedule
“Awaiting client approval” is an incomplete report. Identify the decision, the recommendation, the information available, the person authorised to decide and the latest date that avoids a stated consequence.
This should include owner selections, access decisions, scope changes and acceptance matters. A delayed decision can affect procurement well before it appears to affect installation, so the required date should follow the actual dependency.
Recovery proposals also require evidence. Additional labour, revised sequencing or expedited deliveries should show how they address the constraint, what they cost and what conditions must hold. Moving the finish date in a programme is not evidence that recovery is achievable.
The report should close with the expected route to handover. Outstanding testing, documentation, commissioning and defects can govern the date on which the asset becomes usable even after the visible construction is largely complete.
Directors should leave the review understanding the expected final cost, the credible completion position and the decisions they must make. The report's purpose is to preserve their ability to act while there is still time to affect the outcome.