Ian Rogers is the CEO and visionary founder of leading construction consultancy Procync – known for solving complex project challenges and delivering smarter, dispute-free outcomes across the built environment. In this guest article, he looks at why projects can initially appear to be ‘green’… right up until they don’t.
If you have ever delivered a live construction project, you will recognise the pattern. Everything reads green on paper and the update goes out like it always does. Then you step onto site and it’s obvious the job’s under strain, even if nobody’s calling it that. That disconnect is where problems usually begin.
Projects rarely unravel because of one catastrophic mistake. It is almost never a single decision that blows the programme apart. More often, it is a build-up of smaller calls that felt reasonable at the time. A drawing that is not fully coordinated but works moves ahead anyway. A design query that gets answered verbally so the team can keep going. A package that proceeds on the assumption approval will land next week. None of it feels dramatic. It just feels like keeping momentum, and let’s be honest momentum matters.
Stopping a site is expensive and nobody wants to be the person responsible for slowing things down. So, work continues, assumptions get made. Minor clashes are ‘sorted’ on the ground. Small bits of rework are absorbed without too much noise. From a reporting perspective, the job can still look fine.
Dashboards only show what they are designed to track; milestones met, labour levels holding, procurement broadly aligned and costs within tolerance. What they do not capture particularly well is friction. They do not measure hesitation around decisions, or how often a team is building around incomplete information. They do not show how much effort is going into workarounds rather than clean delivery. You can be green and still be building risk into the programme.
One of the more common patterns is assumption creep. Work advances based on what is likely rather than what is confirmed. Interfaces between trades are agreed informally but not fully stress tested. A detail that should have been locked down is left slightly open-ended. Each one seems manageable, but collectively they begin tightening the job in ways that do not immediately show up on the critical path.
There is also the human side. Few people escalate early unless they have to. Risks are described as ‘under control’. Issues are ‘being monitored’. It sounds sensible, and often it is, but when reporting language softens while pressure on site increases, the dashboard starts lagging reality. By the time the status shifts from green to amber, the strain has usually been there for weeks.
Another giveaway is when busyness gets mistaken for progress. The site is actives, deliveries are arriving, meetings are happening; everyone is working hard. Yet key decisions are drifting, ownership across certain interfaces is blurred, and the programme feels tighter than it did a month ago. Activity gives comfort, but it does not guarantee control.
Interpretation of green
None of this suggests dashboards are pointless, in fact they are essential. The problem is not the tool, but how green is interpreted. If green simply means ‘nothing has failed yet’, it offers false reassurance. A genuinely stable job is one where uncertainties are reducing, decisions are landing when they should, and the critical path is being actively protected rather than assumed to be intact.
Projects do not suddenly turn red. They stay green longer than they should, until the underlying pressure finally forces its way into the numbers. By then, recovery is rarely clean or cheap. The only real safeguard is honest reporting early, while there is still room to adjust course rather than react to the damage.
