Construction projects rarely go wrong in one dramatic moment.
There is usually no single meeting where the team consciously chooses the wrong route, no obvious decision that can immediately be identified as the point of failure. More often, problems accumulate quietly. An assumption remains untested. A decision is delayed. Scope develops faster than the budget. Design information arrives out of sequence. A programme date is protected long after the basis for achieving it has changed.
By the time the project is visibly under pressure, the causes may be months old.
This is one of the most difficult realities of project delivery. The issues that dominate at construction stage are often symptoms rather than root causes. Cost overruns, delay, disputes and repeated change are highly visible. The decisions and gaps that created them are much less so.
Understanding where projects really go wrong means looking earlier.
Projects go wrong when assumptions become facts
Every project begins with incomplete information. That is normal.
Early budgets rely on assumptions. Programmes are developed before every dependency is known. Existing buildings cannot always be fully investigated. Specialist equipment information may still be developing. Client requirements can evolve as the business case becomes clearer.
The problem is not the existence of assumptions. It is when they stop being recognised as assumptions.
A provisional scope becomes the basis of a cost plan. An indicative programme date is communicated as a commitment. A design team progresses on the basis that an existing service has sufficient capacity. A procurement strategy assumes information will be available by a particular date.
If those assumptions are not recorded, tested and revisited, they become embedded in the project.
When reality eventually differs, the project describes the outcome as a change. Commercially, however, the exposure existed from the beginning.
Good project governance makes assumptions visible. It identifies what needs confirmed, who owns the action and when the answer is required. That sounds simple, but it is one of the clearest differences between projects that actively manage uncertainty and those that merely report it later.
Projects go wrong when the brief is still moving but the programme is not
A project programme is often approved early and then treated as a fixed reference point.
The brief, however, may continue to evolve.
Stakeholders add requirements. Operational teams refine how spaces need to work. Surveys identify constraints. Design coordination exposes interfaces. Funding conditions change. None of this is unusual, particularly on complex education, healthcare, care, industrial or public estate projects.
The risk arises when the programme does not respond.
Teams are asked to absorb additional scope within the same design period. Procurement dates remain fixed even though information maturity has changed. Construction start dates are protected because they have been communicated upwards, rather than because the project remains ready.
Eventually, the pressure appears somewhere else. Design quality suffers. Tender information contains gaps. Contractors price risk. Decisions are pushed into the construction phase.
A realistic programme is not a sign of weak project management. It is a control tool.
If the brief changes, the programme impact should be understood and discussed. The client may still decide to protect the target date, but that should be an informed decision with the consequences visible.
Projects go wrong when cost plans are mistaken for cost certainty
A detailed cost plan can create a strong sense of control.
It has work packages, quantities, rates, allowances and contingencies. The total is precise. That does not necessarily mean the project is commercially certain.
Cost certainty depends on the quality of the information behind the numbers.
If scope is unclear, surveys are incomplete, design interfaces are unresolved or the programme is unrealistic, the cost plan is carrying uncertainty whether the spreadsheet shows it or not.
Quantity Surveying should therefore do more than measure and price. The commercial adviser needs to challenge the basis of the project.
What is excluded? Which allowances depend on further information? How mature is the design? Are operational constraints reflected? Does the procurement route match the current level of definition? What risks could materially change the position?
The most useful cost advice does not simply tell a client what the project is expected to cost. It explains what needs to happen for that expectation to remain credible.
Projects get into difficulty when a number is protected after the assumptions supporting it have changed.
Projects go wrong in the gaps between disciplines
Many project failures do not sit neatly within one consultant’s scope.
A design decision may be technically appropriate but create a significant cost or programme consequence. A procurement decision may transfer responsibility without resolving an information gap. A building condition issue may affect design, phasing and temporary works. A late compliance concern may require coordination across several packages.
These issues live between disciplines.
If Quantity Surveying, Project Management, Building Surveying and Principal Designer services operate as separate reporting lines, the client can become responsible for identifying the connections. On straightforward projects, that may be manageable. On complex projects, it creates risk.
Integrated consultancy should provide challenge across those boundaries.
If the Building Surveyor identifies uncertainty in the existing asset, the cost and programme implications should be tested. If the Project Manager proposes a compressed procurement period, the team should understand whether the design and commercial information will be ready. If design risk is emerging, Principal Designer input should influence decisions while options remain open.
The Whole House approach is valuable because project problems rarely respect appointment boundaries.
Projects go wrong when nobody owns the decision
Projects can have experienced teams, detailed reports and regular meetings while still struggling to make decisions.
The issue is often unclear authority.
A design question is discussed by several stakeholders but no individual has responsibility for approval. An operational requirement is raised but the route for changing the brief is unclear. A commercial risk is reported repeatedly without a decision on mitigation.
The project remains busy, but the issue remains open.
Unresolved decisions create programme risk. Design teams either wait or proceed on assumptions. Cost plans retain allowances. Procurement information becomes qualified. Contractors identify uncertainty and respond commercially.
Good governance should make decision ownership explicit.
Who provides the recommendation? Who needs to be consulted? Who approves? By what date? What is the impact if the decision is not made?
This does not require a complex governance structure. In many cases, simpler governance is more effective. The objective is to create a clear route from issue to decision.
A risk without an owner is usually a future problem.
Projects go wrong when stakeholder engagement happens at the wrong time
Late stakeholder input is one of the most common sources of avoidable change.
The end user sees the developed design and identifies an operational issue. The estates team raises a maintenance concern after equipment has been specified. A senior stakeholder joins the project and questions an assumption that shaped the brief months earlier.
The feedback may be entirely valid.
The problem is timing.
Construction projects become less flexible as they progress. A requirement that can be incorporated easily during briefing may have significant cost and programme implications after tender or once work is under way.
Stakeholder management should therefore be connected to project decision points.
Who needs to influence the brief? Who needs to review design before an option is closed? Which operational teams hold information the consultants do not? When does client approval become critical to the programme?
More engagement is not automatically better. Earlier, better structured engagement usually is.
Projects go wrong when risk registers become reporting tools
Most significant projects have a risk register. That does not mean risk is being managed.
A risk can appear in every monthly report and still become an issue exactly as predicted.
The difference lies in action.
If a survey is required to reduce uncertainty, has it been instructed? If a long-lead item threatens the programme, has the procurement strategy changed? If stakeholder approval is critical, is the decision date visible? If an existing building condition could affect scope, has the budget been tested against credible scenarios?
Risk management should change what the project team does.
Registers are useful because they create visibility and accountability. They become ineffective when the process is reduced to changing scores, rewriting descriptions and carrying the same actions from one meeting to the next.
The strongest project teams are willing to escalate risk early, particularly when the mitigation requires a client decision.
Bad news does not become better because it is reported later.
Projects go wrong when procurement is used to solve uncertainty
There is often pressure to move into procurement as quickly as possible.
Tendering feels like progress. It creates a market price and moves the project closer to site. But procurement cannot compensate for an unclear project.
If scope is immature, surveys are incomplete or design responsibilities are poorly defined, the market will respond to that uncertainty.
Contractors may include risk allowances. They may qualify their tender. Competition can become difficult to compare because bidders make different assumptions. Issues may re-emerge as change during delivery.
The procurement route should reflect project maturity and risk appetite.
In some cases, early contractor involvement may help resolve buildability, logistics or specialist interfaces. In others, further design development before tender may provide better value. Frameworks can offer speed and compliant access to the market, but the individual project still needs a clear commercial strategy.
Starting procurement earlier does not always mean finishing the project earlier.
Sometimes the fastest route to successful delivery is to resolve the difficult questions before asking the market to price them.
Projects go wrong when the existing asset is underestimated
Refurbishment and estate projects introduce a particular type of risk because the project is working with an asset that already has a history.
Drawings may be incomplete. Previous alterations may not be recorded. Concealed conditions can only be understood through targeted investigation or opening-up works. Services may have been adapted over decades.
Assuming the existing building will behave as expected is rarely a robust strategy.
Building Surveying should inform project development early enough for condition risk to influence scope, cost and programme. The objective is not to survey every element without limit. Investigation should be proportionate to the decisions being made.
Where uncertainty remains, it should be visible.
This is particularly important across public estate, education, healthcare, care and historic building projects, where live operational environments can make unexpected work significantly more disruptive.
Existing buildings will always retain some uncertainty. Projects go wrong when that uncertainty is ignored rather than managed.
Projects go wrong when teams protect the plan instead of the outcome
There is a point on some projects where maintaining the original plan becomes more important than questioning whether it is still the right plan.
A target date has been published. A budget has been approved. A procurement route has been selected. Considerable effort has already been invested.
Changing direction can feel like failure.
But project control is not about defending earlier decisions regardless of new information. It is about protecting the client’s outcome.
If the evidence changes, the project should be capable of responding.
That might mean revisiting scope, changing sequence, undertaking further investigation or adjusting procurement. These decisions can be uncomfortable, particularly where senior stakeholders expect certainty.
The role of an experienced consultant is to provide clear advice at those moments.
Clients need to understand the implications of continuing as well as the implications of change. Sometimes the right recommendation is to protect the existing plan. Sometimes it is to pause and resolve an issue before the project carries it further.
Professional challenge is most valuable before a problem becomes unavoidable.
The warning signs are usually there
Most troubled projects provide warning signs.
Decisions remain open longer than planned. The same risks appear in consecutive reports. Design information dates move while procurement milestones remain fixed. Cost plans carry increasing allowances. Stakeholders raise requirements that were not captured in the brief. The project team spends more time explaining variance than resolving its cause.
Individually, none of these automatically means a project will fail.
Together, they can indicate that project controls are describing pressure rather than controlling it.
This is where joined-up advice matters. A programme concern should trigger a commercial discussion. A condition risk should be tested against design and delivery. A stakeholder issue should be connected to decision ownership. A design risk should be considered before the relevant option is closed.
Whole House thinking brings Quantity Surveying, Project Management, Building Surveying and Principal Designer perspectives around the same project risks.
The value is not in producing four separate views. It is in reaching a clearer decision.
Projects rarely fail at the point we notice
When a project is delayed or over budget, attention naturally turns to the visible problem.
The contractor is behind programme. The cost report shows change. A design package is late. A stakeholder has challenged the scope.
Those issues need managed, but the more important question is how the project reached that position.
Often, the root cause sits earlier. An assumption was not tested. A decision had no owner. The programme did not respond to a changing brief. Risk was reported but not reduced. Procurement began before the project was ready.
Better project outcomes do not come from eliminating uncertainty. Construction is too complex for that.
They come from identifying uncertainty earlier, connecting the right disciplines and making difficult decisions while the project still has options.
That is where projects are protected.
And it is usually long before the point where anyone says the project has gone wrong.