Disputes usually develop in stages
Construction disputes rarely arrive without warning. They usually develop through unresolved instructions, late information, disputed variations, access constraints, programme slippage or correspondence that is increasingly written for a future tribunal rather than the project team.
By the time a detailed claim is submitted, the parties may already have invested in competing narratives. Internal reports have been written, financial provisions made and senior stakeholders briefed. Negotiation is then harder because changing position can be perceived as admitting error.
Early negotiation is therefore not a soft alternative to contract administration. It is a project-control discipline: identify the issue, preserve rights, establish the facts and create a realistic route to decision before cost and delay compound.
1. Preserve contractual rights while opening dialogue
A common mistake is to treat negotiation and contractual compliance as alternatives. They are not. A party can engage constructively while still issuing the notices, particulars and programme information required by the contract.
Early discussions should not create uncertainty about whether rights have been waived. Project teams should understand the relevant notice provisions, time bars, authority limits and document requirements before entering substantive negotiations. Where appropriate, correspondence can record that discussions are intended to resolve the issue without prejudicing contractual rights.
Talk early—but do not allow an informal conversation to become a substitute for a notice the contract requires.
2. Agree the problem before arguing the answer
Negotiations often fail because the parties begin with money or responsibility before agreeing what actually happened. A more productive sequence is to establish a short, neutral issue statement: the instruction given, the information outstanding, the activity affected, the decision required and the date by which that decision matters.
This does not require agreement on liability. It requires enough common ground to stop the discussion moving between different versions of the problem. A jointly reviewed chronology, marked-up programme extract or decision log can be more useful than another lengthy position letter.
3. Use an early-escalation discipline
Project teams should have an internal expectation that emerging issues are discussed promptly—often within 24 to 48 hours—rather than left to mature through email. That is a management target, not a universal contractual period.
The important point is speed. The people closest to the work should identify the issue quickly; the project leads should determine whether it can be resolved operationally; and unresolved matters should move to an agreed escalation level before they affect critical work or substantial cost.
4. Separate facts, entitlement and commercial resolution
A useful negotiation separates three questions. First, what are the contemporaneous facts? Second, what is each party's contractual position? Third, is there a commercially sensible resolution even if entitlement remains disputed? Mixing these questions too early creates confusion.
For example, the parties may agree that late information affected a work sequence but disagree on whether the contractor mitigated properly or whether the delay was critical. That partial agreement is still valuable. It narrows the dispute and identifies the analysis needed for the remaining issues.
5. Use neutral, technically accurate language
Words such as breach, default and failure may be contractually relevant, but they can also trigger defensive reactions when used before the facts are settled. Early issue meetings are usually more productive when the language is precise and operational: design release, access constraint, sequencing effect, information requirement, programme impact and mitigation option.
Neutral language is not an attempt to hide responsibility. It is a way of keeping the discussion focused long enough to determine responsibility properly.
6. Put decision-makers in the room
Negotiation cannot succeed if everyone present lacks authority. Before the meeting, confirm who can agree a valuation, approve a programme change, commit resources, accept a reservation of rights or recommend settlement.
The parties should also arrive with the information required to decide: the current programme, relevant contract extracts, contemporaneous records, cost build-up, mitigation options and a clear statement of what approval is sought. A meeting without authority or data becomes another source of delay.
7. Document shared understanding—not just the final number
A useful negotiation record should distinguish matters agreed, matters not agreed, assumptions, required actions, owners and dates. It should also record whether any agreement is interim, subject to substantiation or intended as a full and final resolution of a defined issue.
Poorly drafted minutes can create a second dispute about the first negotiation. Circulate the record promptly and invite corrections within a stated period.
8. Use neutral assistance before the dispute becomes institutionalised
An independent adviser does not need to act as a formal mediator. A short neutral review of programme impact, valuation, records or contractual process can help the parties understand where their positions are strong, where evidence is missing and what issues are genuinely worth contesting.
Early neutral input is particularly useful where project relationships remain workable but the technical issue has become too complex or politically sensitive for the project team to resolve alone.
What good early negotiation looks like
- Contractual notices and records continue to be maintained.
- The issue is stated neutrally and supported by contemporaneous information.
- The right people attend with genuine authority to decide or recommend.
- Operational mitigation is considered separately from final entitlement.
- Agreements, reservations and outstanding actions are recorded clearly.
- Escalation occurs before the issue affects critical work or substantial cost.
Final thoughts
The choice is not between collaboration and protecting contractual rights. Well-managed projects do both. They communicate early, comply with the contract, test the evidence and give decision-makers enough information to reach a commercial outcome.
Once a claim is fully developed, negotiation may still succeed, but it will usually be slower, more positional and more expensive. The most effective negotiators create room for resolution before the project team has become committed to a dispute.