When the Scope and the Contract Data disagree
NEC4 has no order of precedence between documents. When the Scope and the Contract Data say different things, the cost of resolving it is usually assessed in the bidder's favour.
By J M Bryant, Founder. November 2026. 4-minute read.
Every experienced NEC bid team reads the Scope and the Contract Data side by side, looking for the places where they disagree. It is one of the most reliable sources of margin in a tender pack, and one of the easiest for a client to remove before issue.
Why it matters more under NEC4
Many standard forms set an order of precedence: if two documents conflict, one wins. The NEC4 Engineering and Construction Contract deliberately does not. Instead, when the Project Manager or the Contractor notices an ambiguity or inconsistency, the Project Manager gives an instruction resolving it. If that instruction changes the Scope, it is a compensation event.
The contract then goes further. Where the instruction resolves an ambiguity or inconsistency in Scope the Client provided, the change is assessed as if the Prices and Completion Date were for the interpretation most favourable to the Contractor. In plain terms: if your documents can be read two ways, you pay for the more expensive one.
What it looks like in practice
The conflicts we see most often are simple. Contract Data names the Client as the applicant for a utility connection while the Scope makes it the Contractor's job. Contract Data sets a completion date that the Scope's phasing cannot meet. Secondary options are selected in the Contract Data, but the Scope is written as if they were not, or the reverse.
None of these need bad faith on anyone's side. They come from documents written by different people at different times, often with a template carried over from the last scheme.
How a bidder uses it
A bidder has three choices: price the risk, qualify the bid, or say nothing and wait. The third is usually the most profitable. The cheaper reading goes into the price, and the difference comes back later as a compensation event, assessed on the favourable interpretation.
What to check before issue
- Read Contract Data part one and the Scope together, clause by clause, for every obligation that names a Party.
- Check that each selected secondary option is reflected in the Scope and the pricing document.
- Confirm dates, sections and key dates match the Scope's phasing.
- Make sure anything carried over from a previous scheme still applies to this one.
Each of these is a drafting correction before issue. After award, each is a compensation event.