There is no golden standard for programme reporting, and asking for one is usually a sign that something upstream is broken. When executives ask for better reporting, they are mostly asking the wrong function to solve the wrong problem. Better reporting cannot close a governance gap, because a report only changes outcomes when someone holds the decision right, the habit and the forum to act on it.
The request arrives when the old report stopped mattering
The pattern is familiar. A programme drifts. A board member says the reporting is not good enough. Someone commissions a new dashboard, a redesigned RAG scheme, a consolidated template with more tabs.
Three months later, the report looks far more professional. The same decisions are still waiting.
The report was never the bottleneck. Nobody in the room had the right, the habit or the forum to act on what it already said. A better-looking version of an unread document is still unread.
The request is understandable. Reporting is the one lever an executive can pull without confronting anyone. Asking for a new dashboard feels like action, costs nothing politically and hands the discomfort to someone further down the organisation. Asking who should have decided last quarter’s open issue, and why they did not, is a much harder conversation. So the organisation has the easier one, repeatedly.
The causal chain runs in one direction
Reporting sits at the end of a chain, not the start. Governance defines which decisions exist and who takes them. Those decisions define what information is needed, and when. Only then does it make sense to ask what a report should contain.
Run the chain backwards and you get the familiar result: ever more data, collected at real cost to the people doing the work, and not one additional decision taken. Teams spend days populating fields that nobody reads, because nobody ever said which decision those fields were meant to feed.
Before changing any report, three questions settle most of the argument. Which decision does this report feed? Who takes that decision, and in which forum? What would they do differently with different information?
If nobody can answer the first, the report is not the problem. If nobody can answer the second, the problem is governance. And when the honest answer to the third is “nothing”, the report can probably stop.
A report that no forum can act on is not information. It is decoration with a distribution list.
Large engineering programmes make the mistake expensive
The pattern is costly anywhere, but large capital programmes multiply it. Several parties each bring their own reporting standard. The main contractor reports against its contract, the owner against its budget, each shareholder against its own investment process. Every format is legitimate on its own terms.
The instinct is to consolidate them into a single master report. What comes out is volume, not clarity: a document thick enough to cover every stakeholder and thin on anything a decision-maker can use. Across engagements like this, the consolidated pack tends to grow every quarter, and the list of open decisions grows with it.
Timing makes it worse. The contractor reports monthly, the board meets quarterly, and each shareholder runs its own calendar. By the time a consolidated view reaches the forum that could act on it, the window for the decision has often closed. Somebody then asks for faster reporting, which repeats the original mistake one level down.
The reporting is not failing in those programmes. It is faithfully describing a governance structure in which nobody has agreed which forum decides what. No template can resolve that, because it is not a formatting question.
The cost lands on the people doing the work
Every report has a production cost, and almost nobody measures it. Project managers chase updates, controllers reconcile figures between formats, and someone spends the last two days of every month assembling the pack. That time comes straight out of delivery.
When the report feeds a real decision, the cost is worth paying. When it does not, the organisation is paying its most capable people to document a standstill. Teams notice this long before leadership does. Updates get thinner, numbers get copied forward, and the report drifts further from reality while looking more complete than ever.
One question exposes the problem quickly. How many decisions did last quarter’s reporting pack actually trigger? If the answer is close to zero, the pack is not a reporting asset. It is a governance cost hiding in a reporting budget.
Change a decision right, and the report changes itself
The fix starts with the forum, not the format. Decide what the steering forum actually decides, which is rarely what its name suggests, and the information it needs becomes obvious. Then name the escalations that must reach it, the thresholds that trigger them and the time it has to respond.
Once that is settled, the report almost writes itself. It usually gets shorter, because most of what it carried was there to cover the absence of a decision rather than to inform one. The measures sharpen too. A steering forum needs to know whether the strategy is moving, which is a different question from whether the business is running: the difference between key results and KPIs.
None of this means reporting standards do not matter. Consistent definitions, reliable data and a stable format all help. They help a governance system that already works. They cannot substitute for one that does not.
Five habits keep reporting downstream of governance
Avoiding the trap does not take a reporting project. It takes a few habits that put decisions first and keep them there:
- Write the decision list before touching the template. Before any reporting change, list the decisions the forum must take in the next two cycles. If the list is empty, the problem is not the report.
- No forum, no report. Every recurring report gets a named forum and a named decision owner. A report that cannot name either goes to a working tool, not to the steering pack.
- Lead with decisions, show status by exception. Open with the decisions needed this cycle, the options and the deadline for each. Status appears only where something has crossed an agreed threshold.
- Put a clock on escalations. Agree how long the forum has to respond, and report unanswered escalations as exactly that. An escalation without a deadline is a note for the file.
- Audit the yield every quarter. Count the decisions each section of the pack triggered. Cut what triggered none, and the pack will shrink towards what the forum actually uses.
Fix the forum, and the report will follow. Fix the report, and the forum will still not decide.