Why are disputes so common in construction? A job can start before the design is complete, involve input from several parties whose work depends on one another and change considerably before it finishes. Decisions often have to be made while work is under way, with significant amounts of money at stake for everyone involved.
Every dispute has its own facts, but in our experience it is often similar themes that come up across very different projects.
Recognising these patterns gives employers, contractors and subcontractors a chance to deal with problems before they turn into costly disputes.
Getting the contract basics right
A contract can be detailed and still leave the parties with different views about what the price includes. An employer may expect the contractor to adapt a design around existing services. The contractor may have priced on the assumption that those services can be reused. The difference can remain hidden until a survey shows that some of the services need replacing.
The problem can lie in the documents themselves. A tender qualification may never make it into the signed agreement, two documents may point in different directions, or the parties may include an allowance without saying what happens if the cost exceeds it. It can also arise because a party understood what it had priced but did not appreciate that the contract placed a wider risk on it.
Before signing, identify the assumptions that would materially affect the price or programme if they proved wrong. Check who carries each risk, whether the relevant qualifications are incorporated and which document takes priority if the terms conflict. If the extent of a risk cannot yet be established, agree how the parties will deal with it when more information becomes available.
Using the contract as the rulebook
The contract sets out what each party is expected to do when something changes or goes wrong. It gives the parties a common process for raising an issue, recording what has happened and reaching a decision. Problems arise when that process gives way to informal arrangements, particularly if each side has a different understanding of what has been agreed.
Take a delay that everyone knows about. The contractor may discuss it at progress meetings without giving the notice the contract requires. The employer’s team may know that work is being held up but leave the effect on completion unassessed. Months later, the parties can find themselves arguing about notice, entitlement and the effect of the delay at a time when the original sequence of events is harder to establish.
The same can happen with change and payment. A site team may agree a different way of doing the work without making clear whether it has been instructed. The parties may discuss a valuation and still let a payment notice deadline pass. These departures can generate disputes of their own and make the underlying issues harder to resolve. The parties are left reconstructing what was asked for, what was agreed and when.
Both parties have a part to play in making the agreed process work. When a delay is notified or a change is raised, check what the contract requires each side to do next. One party may need to give particulars or keep records, while the other may need to issue an instruction, ask for further information or make an assessment within a set time. If the parties disagree, dealing with the issue through that process helps establish what remains in dispute and why. For a main contractor, that means dealing with issues raised by its subcontractors under their own terms, even while the corresponding issue is still being discussed with the employer.
Helping teams understand the contract they are using
People quite reasonably draw on what has worked on previous jobs. Difficulties arise when a process becomes familiar enough that nobody checks whether it applies to the current contract. Even projects using the same standard form can have different amendments, notice periods or people authorised to issue instructions. The terms of a subcontract can also differ from those of the main contract on the same project.
Clients sometimes ask us what sounds like a straightforward question. Does this count as a variation? Was that email enough to give notice? The answer is often “It depends”. The wording of the agreed terms, how the courts have interpreted similar provisions and the facts of the particular issue can all affect the answer. A site request that could be dealt with by one person on the last job may need formal confirmation from someone else on this one.
Practical training should use the contract the team is actually working under. Take a likely situation, such as a client asking for a different layout, and follow it through with the site and commercial teams. Who can instruct it? Who needs to know before the work proceeds? Who deals with the effect on time and cost? Walking through a real situation helps people understand when they can act and when they need to involve someone else.
Dealing with changes as the scope develops
On many construction projects, the scope at completion differs from what the parties started with. Some design decisions may still be open when work begins because waiting for every detail would delay the start. The client’s needs may evolve. Work may need to change to meet regulatory requirements or because the design of one trade has to be coordinated with another. Some of these developments are foreseeable in principle, even when nobody can say at tender stage exactly what they will involve.
Disputes often start when the technical decision gets made and the commercial question is left open. For example, resolving a clash between a duct and a structural beam may be straightforward on site. The parties can still disagree later about whether rerouting was part of the design coordination already allowed for or a change to the agreed requirements, and whether it affected other work.
When deciding how to proceed, establish why the work needs to change and identify which parts of the agreed scope or design responsibility are affected. If the parties need to proceed before they can assess the effect on cost or time, confirm what has been authorised and what remains to be decided. A short record made at that point can prevent a practical decision on site from being remembered later as an agreement on who would pay.
When claims and assessments become adversarial
Construction disputes can involve complex questions and substantial financial exposure on both sides. A party that expects its claims to be reduced may build in room to negotiate. An assessor accustomed to overstated claims may approach the next submission expecting to cut it back. Each response reinforces the other.
Both sides can end up spending time on the weakest items while well supported parts of the claim go unresolved. Industry habits are hard to change, but the parties can deal with individual items on their merits. A claimant can show how it reached its figures and identify any estimates. An assessor can explain the reasons for reducing or rejecting particular items. Agreeing the parts that can be resolved helps focus time and cost on the issues that genuinely need a decision.
Communicating before positions harden
Project teams often talk regularly and still avoid putting important matters in writing. A subcontractor may worry that a notice will be taken as a sign of confrontation or affect its prospects of future work. The team receiving it may prefer to deal with things informally to keep the relationship working. The difficulty is that a conversation can leave one party thinking it has raised a contractual issue and the other thinking it has heard a routine progress update.
A notice can give the other party an opportunity to act while there are still options. If access is going to be late, for example, early notification may give the project team time to change the sequence or make another area available. The parties can give the required notice and carry on discussing how best to deal with the problem. When a decision is made, a short confirmation of what was agreed and what remains open helps everyone proceed on the same basis.
Keeping records and dealing with issues as they arise
Many of the issues we are asked to advise on come to us months after the event. Sometimes both parties have made real efforts to reach agreement and have come to an impasse. On other projects, getting the work done has taken priority, or the parties have deliberately left the commercial issues until the end of the job.
This approach generally makes the facts harder to establish which in turn makes disputes harder to resolve. Even where there are plenty of emails or site records, they may be of limited help if they do not show the required information or they are being looked at by different people as teams change and issues evolve. That uncertainty can make it harder for both sides to assess the strength of their positions and reach agreement.
There are also contractual requirements to consider which may mean the issue has to be dealt with within a certain timeframe, as noted earlier. It is generally better to deal with the issues as they arise and capture the consequences as you go – whether that is time and or money. That is not just true of the claiming party but also the assessor who has to respond to those claims.
If discussions have stalled, identify what is preventing a decision and consider whether someone else with authority to resolve it should be involved. That may help the parties settle the issue while there is still time to do something about it.
How CCC can help
An early review can help identify the actual disagreement, assess the contractual position and focus effort on the evidence or action most likely to make a difference.
CCC advises employers, contractors and subcontractors on contract terms, project administration and construction claims. Contact us for a free initial one-hour consultation to discuss your position and the practical options available.


