Poor project reporting rarely looks like a major problem at first. The pack is produced, status updates circulate and governance meetings go ahead.
The weakness becomes apparent when senior leaders need to act and the information is late, inconsistent or difficult to trust. Time is spent establishing the position rather than deciding what to do about it.
The cost extends beyond producing the report: delayed intervention, weaker investment decisions and delivery capacity lost to repeated requests and reconciliation.
Most delivery problems are easier to deal with when they are identified early. When a milestone slips, a dependency moves, or an assumption changes, early visibility gives teams more scope to adjust the plan before the impact spreads.
However, if updates are inconsistent, or information has to be manually reconciled, senior leaders may not see an issue requiring their intervention until the opportunity to contain it has passed.
An example we have experienced recently with a Brighter PMO Practice client illustrates the point.
A transformation programme was reporting green, with expenditure below forecast and its go-live date unchanged. On the surface, there was little reason for leadership to intervene. However, a delayed supplier deliverable had pushed back testing, and the specialists needed to recover the position were already committed to another programme. The financial forecast still assumed the original completion date, and the apparent underspend was not a saving; it was work that had not yet happened.
Our PMO team connected the workstream plans, resource commitments and cost forecast, exposing a recovery plan that depended on capacity the organisation did not have. We brought the resulting choices into governance: reprioritise specialist resources, reduce the scope of the initial release or move the implementation date and recognise the additional cost. Leadership could then make an informed decision before supplier extensions and conflicting resource commitments became unavoidable.
The problem was not a lack of information; it was the absence of a joined-up view.
The longer it takes for an issue requiring leadership intervention to reach the right decision-maker, the more likely it is that a manageable delivery problem becomes an expensive recovery exercise.
The same reporting weaknesses also consume leadership time. A governance meeting should help senior leaders make decisions, but when delivery information does not fit together, discussion becomes an exercise in establishing the facts.
For example, the project lead may have one view of delivery, finance has another, and the PMO pack has been produced using information submitted several days earlier.
Questions about spend, milestones or risk then turn into discussions about where the number originated or whether a date has changed.
Senior leaders spend time checking information that should have been reconciled before the meeting, while decisions are pushed back until the facts can be confirmed.
The reporting process should give leaders a consistent view of what has changed, where intervention is required and which decisions need to be made. If the meeting is used to establish rather than act on the facts, the process around it needs attention.
The impact becomes more serious when the same reporting problems sit across several programmes.
Portfolio decisions depend on being able to compare delivery, cost, risk and resource demand across different projects. When programmes apply inconsistent status criteria, report without clear approved baselines, or assess risk inconsistently, meaningful comparison becomes difficult.
Senior leaders then have to prioritise programmes without a reliable basis for comparison, affecting decisions about where additional resources should be allocated and which work needs intervention.
The risk is not simply that a struggling programme receives too little attention. It is that leaders commit funding and scarce resources elsewhere without a reliable understanding of the trade-offs across the portfolio.
Once senior leaders lose confidence in the reporting pack, they start looking for information elsewhere.
Programme leads are then asked for separate updates, finance builds another view and individual workstreams create their own trackers for senior stakeholders. As a result, the organisation is left with parallel reporting processes covering the same portfolio.
The PMO now has more information to reconcile, while programme teams spend additional time answering the same questions in different formats.
There is also the cost of producing the report to consider. For many PMOs, updates are still chased manually, spreadsheets are copied into presentations and the same information is reworked for different audiences.
While the final pack may look polished, experienced PMO teams have spent a large part of the reporting cycle assembling it.
If several people are spending days producing a governance pack each month, the cost is already significant. Programme teams are also contributing time through repeated updates, duplicated requests and different reporting formats. That is capacity that could be better used to analyse delivery, challenge assumptions or resolve issues earlier.
The problem is not the time spent validating and interpreting information. It is the time lost rebuilding it before that work can begin.
Start with the decisions leaders need to make, then work backwards to the information required. The PMO can then look at how that information is produced, where duplication exists and who owns the quality of each update.
Reporting definitions should be clear enough for programmes to work consistently. Agree the criteria behind status ratings, reporting cut-off dates and escalation thresholds, and make material changes to milestones, costs and assumptions visible.
The PMO should then test whether the reported position is supported by the evidence and connect the implications across delivery, cost, capacity and dependencies. Where a decision is needed, the report should make the options, consequences and timing clear.
Use source systems and automation to reduce repetitive preparation where possible, but not as a substitute for clear ownership and informed challenge.
The aim is straightforward: provide leaders with reliable information early enough for them to act on it.
Brighter Consultancy’s PMO Practice works with organisations to improve how PMOs operate, strengthening the reporting, governance and portfolio processes that support delivery. We help teams establish clear reporting standards, strengthen the challenge behind the numbers and turn project information into insight leaders can act on.
If your project reporting is taking too long to produce, creating multiple versions of the truth or failing to surface issues early enough, speak to our PMO Practice about strengthening reporting, governance and delivery confidence.