A large proportion of variation disputes are not about change at all. They are about whether something was in the original scope, with each party reading the same documents and arriving honestly at a different answer. Establishing who carries that ambiguity is central to a contractual entitlement review.
The instinct is to argue about what was intended. The contract is usually more interested in what was written and in which document governs, which is a narrower and more answerable question.
Where scope ambiguity comes from
Incomplete design at tender, which is normal rather than exceptional. A contractor prices what is shown and makes assumptions about what is not.
Documents prepared by different people at different times, which describe the same work in inconsistent terms without anybody reconciling them.
And performance requirements sitting alongside prescriptive descriptions, where meeting one does not necessarily satisfy the other.
None of these is unusual. What varies is whether the contract deals with them clearly, and whether anybody looked at how it does so before the argument started.
The questions the contract asks
Which documents form the contract, and in what order of priority. Most contracts answer this expressly, and the answer frequently decides the argument.
What the contractor was required to include, which on design and build is usually broader than on a traditional form.
And what the contract says about errors, discrepancies and ambiguities, since many forms contain a specific mechanism for dealing with them.
Those three provisions, read together, usually produce an answer without anybody needing to establish what was in anybody’s mind.
Qualifications and assumptions at tender
Where a contractor qualified its price, the qualification may have become part of the contract or may have been excluded by the conditions. Which of those happened is a matter of what the contract documents say.
Qualifications recorded only in a covering letter, or discussed at interview and not written into the contract, frequently turn out to carry less weight than the contractor expected.
This is why tender qualifications deserve attention at signature rather than at dispute. The time to establish whether an assumption is part of the bargain is before the bargain is concluded.
Design and build changes the question
Under design and build the contractor usually takes responsibility for satisfying the employer’s requirements, which means a gap between the requirements and the proposals is frequently the contractor’s problem.
That allocation is the point of the procurement route rather than an unfairness in it. Where the employer wanted certainty of price, the corollary is that the contractor carries the detail.
What varies is how far the contract goes. Some amendments extend that responsibility further; others preserve areas where the employer carries the risk of its own documents.
Reading which version you have is the whole exercise, and it is a different exercise on every project.
Measurement contracts behave differently
Where the contract is based on a bill of quantities, errors in the quantities are usually dealt with by a specific mechanism rather than by argument about scope.
That mechanism generally favours the contractor, since the bill was prepared by or for the employer, but the detail depends on the form and on any amendments.
The practical consequence is that the same factual situation can produce quite different outcomes depending on how the works were procured.
What evidence actually helps
The contract documents themselves, in the order of priority the contract sets. Tender correspondence where it has been incorporated. And the instructions issued afterwards, which frequently resolve the question one way or the other.
What helps less is recollection of meetings, assurances given informally, and arguments about what a reasonable contractor would have assumed, however genuinely those assumptions were held at the time.
Those things are not irrelevant, but they are secondary to the documents, and claims built primarily on them tend to struggle. The further a position depends on what somebody remembers, the weaker it gets as time passes.
Dealing with it during the works
Raise it when it appears rather than when it is priced. A discrepancy notified at the time is a question to be resolved; the same discrepancy raised in the final account is a claim to be resisted, and it is received quite differently.
Use the contract mechanism if there is one. Many forms require a contractor to notify discrepancies and require the contract administrator to issue an instruction resolving them, which produces a decision rather than an argument.
And record the resolution. An agreement reached on site about what the scope includes is worth very little if it exists only in two people’s memories, both of which will be tested later.
A short written confirmation of what was agreed, sent the same week, is usually enough and takes minutes to produce.
Pricing the gap at tender
A contractor pricing incomplete information has three choices: include an allowance, qualify the price, or assume the gap will be resolved by instruction. Each carries a different risk.
Including an allowance is the safest and the least competitive, which is why it is the least used. Qualifying is effective only if the qualification becomes part of the contract.
Assuming resolution by instruction is the common approach and it depends entirely on the procurement route. On design and build that assumption is frequently wrong, which is where a large proportion of these disputes originate.
Where it ends up
Unresolved scope questions accumulate into the final account, which is the worst place to deal with them because everything is being argued at once and the people involved have moved on.
Dealing with them as they arise is ordinary contract administration, and it is what cost control and variations work is for.
Where they have accumulated and the account has stopped moving, the position is better addressed as a whole through final account dispute review than item by item through correspondence.
Not sure whether the contract gives you a route?
A contractual entitlement review tests whether the contract gives a right to additional payment or time for what happened, before anybody argues about what it is worth.