Seven reasons why projects quietly run over time and budget

Projects going over budget and completed late are a major problem for construction. Image: Adobe Stock

A project always starts with good intentions, including a decent plan and a team that genuinely cares and believes it will be different this time. Eventually, little things start to creep in, such as a decision getting delayed because someone is ‘just waiting on XYZ’ for final sign-off or moving forward on a working assumption to avoid stopping the clock.

On the surface, everything looks fine and nobody panics because nothing looks catastrophic yet, which is exactly how overruns happen and money goes down the drain: slowly, in the gaps between what was planned versus what the team are actually doing.

I’ve spent the better part of thirty years in the trenches of complex property and construction programmes, and more often than not, I am the person who gets a call only after the project has already started its downward spiral. When you spend that much time performing rescue missions, you begin to notice the same red flags waving.

The green dashboard trap

There is a particular kind of comfort that comes from a tidy spreadsheet, yet a green status frequently becomes a convenient habit rather than a true reflection of what is happening on site. We have all seen instances where early warning signs get dismissed as ‘manageable’ and risks are politely ‘monitored’ while everyone just hopes the next reporting period will magically look better. The trouble is that optimism does not buy you time; it simply borrows it, and by the time the reporting finally matches what the team has been feeling for weeks, the easy fixes are usually gone.

Progressing on guesswork

When approvals lag or design calls get hesitant, the site does not just stand still, as the overheads are far too high to let the wheels stop spinning. People keep moving and building based on what they think is most likely or what they have seen work on a similar job before. While this keeps the site looking busy, it also acts as a factory for rework, which is the ultimate silent killer because it shows up as lost productivity and a programme that feels suffocating for reasons no one can quite explain.

Rushing the handover to site

Mobilisation is where you actually set the rules of the road, defining who decides what, how information moves, and what ‘done’ actually looks like. If you treat this stage like a box-ticking formality, you will pay for it for months, as once a team gets used to vague ownership and fuzzy decision routes, it is nearly impossible to put the toothpaste back in the tube.

Ian Rogers is the CEO and founder of construction consultancy Procync. Image: Procync

Too many voices, no decision-makers

Having a lot of people at the table is not automatically a problem, but not having a final decision maker in the room with the right level of authority to shut down discussions is a problem, and its where the trouble really starts. You notice it most when a problem starts bouncing between departments, with everyone involved only taking half-responsibility, or when the whole team is stuck in limbo waiting for a final sign-off that never actually shows up. In that kind of culture, nobody really says ‘no’; they just delay things politely, and those polite delays are what eventually kill your margin.

Tracking the wrong kind of busy

A project can be a hive of activity and still be completely stuck in the mud. If you are just measuring progress by how many reports get filed rather than whether you are actually tackling the risks and getting rid of the unknowns, you are asking for trouble. It allows slippage to hide in plain sight for weeks, and by the time anyone admits there is a problem, the chance of actually fixing it is usually long gone.

The risk register gets ghosted

Nearly every team kicks things off with a solid risk workshop, yet as soon as the real pressure of delivery starts mounting, that risk register usually goes out the window classed as a mindless admin task, usually performed once a month just to satisfy a requirement in head office. Those risks end up sitting there with the same stagnant mitigations for months on end until the inevitable happens and everyone acts surprised, despite the fact that the warning signs have been right there in the report since the second week of the job.

Blaming the tech for people problems

While sequencing, design quality and buildability certainly matter, the majority of overruns are driven by human friction, such as misaligned priorities, unspoken tensions or different interpretations of success. If you do not fix the relationship between the teams, no amount of technical solutions will stick, and you will just be treating the symptoms while the underlying issues continue to fester elsewhere.

Projects do not usually run over time and budget because of one giant mistake, but rather because several small issues were allowed to live on the job unchecked. The only real safeguard is early clarity and honesty, which includes clear ownership, making the hard calls when they need to be made and reporting the truth while there is still room to change the outcome.

Ian Rogers is the CEO and founder of leading construction consultancy Procync, known for solving complex project challenges and delivering smarter, dispute-free outcomes across the built environment.