Boardroom Data vs Site Reality: Why Construction Reports Stay Green
Construction project reporting hides problems because people learn that bad news gets punished, so each layer softens it before passing it up. By the time a site risk reaches the board, it has been edited to green. The fix is cultural, not software: treat a red as a request for support, and get site problems to the board in 72 hours, not 30 days.
Last reviewed: November 2026
Walk into most construction boardrooms today and you’ll see colourful dashboards full of green lights, good safety statistics and healthy projected margins. The directors look at those screens and feel in control.
Back on site, the project manager is staring at a late steel delivery, a trade partner who hasn’t turned up and a quality issue that’s about to eat 3 weeks of the programme.
None of that is on the dashboard yet.
Every construction board believes it has visibility of its projects. The monthly reports come in. The programme is updated. The commercial position is reviewed. RAG statuses are discussed, actions are noted, and everyone moves on feeling informed.
But here’s what most boards don’t see: the gap between what those reports say and what’s actually happening on site. Not because the data is fabricated. Because it’s been filtered, softened and shaped by people who’ve learned that delivering bad news has consequences.
That gap is one of the most dangerous patterns in construction project reporting. Decisions get made on information that’s weeks out of date, commercially optimistic and carefully framed to avoid difficult conversations. And by the time the truth surfaces, the cost of fixing it has multiplied.
Why does construction reporting hide problems?
Nobody sets out to mislead the board. What happens is more subtle than that. A site manager flags a risk in a weekly report. The project director softens it before it goes up. The operations director summarises it as “being managed”. By the time it reaches the board, a genuine programme risk has become a green RAG with a footnote.
How a red becomes green
Nobody lied. Every step just made it a little more comfortable.
This doesn’t happen because people are dishonest. It happens because the culture punishes honesty. When a project manager raises a problem and the response is blame, pressure or a demand to “just sort it out”, the lesson is clear: keep it to yourself. Fix it quietly. Only escalate when you’ve run out of options.
The research says the same. In a study of failing IT projects, people’s reluctance to report bad news was shaped by two things: how much damage they thought staying silent would do, and how much wrongdoing they had seen around the project (Smith, Keil and Depledge, Journal of Management Information Systems, 2001). Different industry. Same human behaviour.
Over time, site teams learn to tell the board what it wants to hear rather than what it needs to hear. The boardroom data looks clean. The site reality is anything but.
Why is the dashboard always green?
The reason is cultural. If a project manager knows that a red light will earn a trip to head office for a grilling, they will find a way to keep that light green for as long as possible. Sound familiar?
You don’t need a better algorithm. Good data is 20% tech and 80% people. When site teams trust that the numbers will be used to help them, not punish them, the data becomes honest. And honest data is the only kind that can save your margin.
Where is the commercial blind spot?
Nowhere is the gap more dangerous than in commercial reporting. Construction projects are complex commercial environments with hundreds of moving parts, and the temptation to present an optimistic position is enormous.
Cost to complete forecasts that assume everything goes to plan. Variations logged but not yet agreed, counted as income. Risk allowances that shrink every month because nobody wants to be the one who says the project might lose money.
By the time the board sees the real commercial position, it’s often too late to influence it. The margin has already gone. The only discussion left is how to explain it to the client and how to limit the damage.
This isn’t a process failure. It’s a culture failure. If your commercial teams believe a realistic position will bring criticism rather than support, they’ll present an optimistic one. Every time.
What is the difference between lagging and leading indicators?
Most construction KPIs are lagging. They tell you what happened last month:
- last month’s spend;
- last month’s safety incidents;
- last month’s progress against the master programme.
They’re fine for the annual report. They’re useless for intervention. In my experience the commercial report lands around the 20th of the following month. If that’s when you find out a project is in the red, you’ve missed the window to fix it.
Leading indicators tell you what is happening now, and what’s about to go wrong. Three matter most:
- Workface readiness. Are the materials and information there before the gang arrives?
- Constraint resolution. Are roadblocks being cleared as fast as they appear?
- Team sentiment. Does the site team feel in control of the programme, or under the pump?
None of those fits neatly in a monthly report. All of them predict the margin.
How fast should a site problem reach the board?
I’ve sat on both sides of this table. I’ve been the one on site trying to make the numbers look acceptable. And I’ve been the one building a national dashboard to track performance across hundreds of millions of pounds of work.
The secret to a dashboard that works isn’t better software. It’s closing what I call the intervention gap: the time between a problem appearing on site and the person who can fix it knowing about it. My rule is that a site problem should reach the board in 72 hours.
Not 30 days.
In one business I worked in, we cut the time it took a site problem to reach the leadership team from 60 days to 3, over 18 months. Not with new software. With a process where a flagged issue was in front of the right decision-maker within 24 hours and closed out within 72. When people saw that raising a problem got them help that week, they raised more of them, earlier.
That is the shift from reporting to a live loop: data that tells you what is happening now, while there is still time to act on it.
What does the board never hear?
Ask any experienced site manager what they wish the board understood about their project. You’ll hear things that never make it into a monthly report. The trade partner who’s consistently underperforming but hasn’t been formally challenged because the QS doesn’t want to trigger a dispute. The design issue that’s been parked for weeks because nobody wants to admit it wasn’t caught earlier. The team member who’s struggling but hasn’t been supported because everyone’s too busy firefighting.
These aren’t minor operational details. They’re the leading indicators of project failure. But they live in conversations, site walks and team dynamics, not in dashboards and programme updates. A board that relies only on formal reporting is making decisions with one eye closed.
How do you build a culture of honest reporting?
Closing the gap starts with leadership behaviour, not better systems. If the board reacts to bad news with blame, it will keep getting filtered reports. If it reacts with curiosity and support, it starts getting the truth.
“A red light is a request for support. Not a mark of failure.”
That means changing how project reviews work. Instead of interrogating project managers about why something is amber, ask what support they need. Instead of demanding a recovery plan on the spot, make space for an honest view of what’s realistic. Instead of measuring leaders on whether their projects look good on paper, measure them on whether problems get surfaced and addressed early.
The businesses that close the gap are the ones where flagging a risk is rewarded, not punished. Where commercial honesty is valued over commercial optimism. Where the board actively looks for the information that challenges the formal reports. Call it a black box culture: every failure is reported, studied and fixed, not hidden.
This is culture work. It needs sustained effort from the top, reinforced until honest reporting is the norm rather than the exception.
Seeing what’s really there
At Constructing Culture, we help construction businesses close the gap between what the board sees and what’s actually happening on site. That means working with leadership teams on the behaviours, systems and culture that make honest reporting safe and expected.
If you’re a director and you suspect your board isn’t getting the full picture, or you know it isn’t, book a conversation. The cost of not knowing is always higher than the cost of finding out.
The bottom line: if your dashboard says green and your gut says red, the dashboard is the one that’s been edited.
Questions people ask
Why do construction RAG reports stay green until it’s too late?
Because each layer of reporting softens bad news on its way up, so a real programme risk reaches the board as a green status with a footnote.
What is the difference between lagging and leading indicators in construction?
Lagging indicators report what already happened, such as last month’s spend or progress. Leading indicators predict what will happen, such as whether materials and information are ready before a gang starts.
Which leading indicators should a construction board track?
Workface readiness, how fast constraints are being cleared, and how the site team feels about the programme.
How quickly should site problems reach the board?
Within 72 hours, not at the next monthly report, by which point the margin is often already gone. That is Andy Pritchard’s rule from running multi-project programmes.
Sources
- Smith, H. J., Keil, M. and Depledge, G. (2001), “Keeping mum as the project goes under: toward an explanatory model”, Journal of Management Information Systems 18(2), 189 to 227 (abstract). A study of IT projects.
Andy Pritchard MCIOB
CIOB Gold Medal, Construction Manager of the Year 2019. Founder of Constructing Culture and author of Going for Gold. About Andy →