Board reporting on capital projects is structurally optimistic. This is not usually dishonesty. It is the predictable result of asking a delivery team to report on its own performance, in a format that rewards steadiness, to an audience that has neither the time nor the technical grounding to interrogate the detail.
The reports are accurate in what they say. The risk sits in what the format does not require them to say.
Why status reporting drifts
Three mechanisms push project reporting toward the reassuring.
The first is aggregation. A program reported at summary level averages away the item in trouble. Ninety percent complete across ten workstreams conceals one workstream at forty.
The second is the reporting cycle itself. A team that reports monthly must produce a defensible position monthly. Problems that are being worked on are rarely escalated while there is still a chance of solving them quietly, which means the board learns about them last.
The third is the absence of a counterfactual. A report says the project is on schedule. It does not say against which schedule, or how many times that schedule has been rebaselined.
The questions worth asking
What has changed since the last report, and why? Not the status — the delta. A project whose reported position never moves is either genuinely stable or not being measured. The follow-up matters more than the answer: what caused the change, and was it foreseen?
How many times has the baseline been reset? A program reported as on schedule against its fourth baseline is not on schedule. Ask for the original approved dates alongside the current ones, on the same page.
What is the cost-to-complete, and how was it derived? This is the single most useful question a director can ask, and the answer distinguishes real reporting from arithmetic. Cost-to-complete built from the remaining scope, the current market, and the known change position is a forecast. Cost-to-complete calculated as original budget minus spend to date is a subtraction, and it will hold right up until it does not.
Which decisions are open, and who owns each one? Every open decision is a cost that has not yet been incurred. A project with a long list of unowned decisions is accumulating liability quietly.
Does the contingency still match the risk? Contingency is drawn down over time. Risk should fall faster. Where contingency has been consumed but the risk register has not shrunk, the project is under-provisioned and the reporting has not caught up.
A project that has spent half its contingency and retired none of its risk is in worse shape than one that has overspent and closed out its exposures.
What independent review adds
Internal reporting cannot fully solve this, because the people best placed to see the problems are the same people accountable for them. That is not a criticism of any individual. It is a structural conflict, and it is the reason lenders commission independent monitors as a matter of course.
An independent read does three things internal reporting cannot. It establishes a single agreed account of the project where several competing accounts exist. It tests the cost-to-complete against evidence rather than against the budget. And it gives the board a view that carries no career consequence for the person delivering it.
Setting the standard
The most useful thing a board can do is set the reporting standard early, while the project is still going well.
Require the original baseline on every schedule page. Require cost-to-complete with its derivation attached. Require the open decision list with named owners and dates. Require contingency drawdown shown against risk closure.
None of this is burdensome when the project is healthy. All of it is resisted when the project is not — and the resistance is itself the signal.
