The scope clause is the deal
Everything else in a contract - price, liability, termination - allocates risk around one central question: what is actually being delivered? The scope of work, or subject matter, clause answers it. When that clause is vague, the rest of the contract is allocating risk around a hole.
This is why "deliver the solution", "provide the services", or "complete the project" define nothing. They are placeholders where the scope should be, and they push the real argument to the moment something goes wrong.
TCS v DBS: when hundreds of pages weren't enough
In Tata Consultancy Services Ltd v Disclosure and Barring Service [2024] EWHC 1185 (TCC), a major UK government IT modernisation contract ended in an eight-week trial with the parties claiming more than GBP 200 million between them. Constable J rejected almost all of it: TCS recovered a few million, DBS a little less, and after set-off DBS paid TCS just under GBP 5 million - a fraction of what either side had claimed.
Scope was central to it. TCS said its responsibility was limited to application software; DBS said TCS had to deliver a working end-to-end system - both readings plausible, both supported by the contract. The case turned on more than scope alone, with delay causation, notice and condition-precedent requirements, acceptance, and quality all in issue, but the unclear allocation of scope, responsibility, performance standards, and acceptance and remedy mechanics ran through it. Sophisticated parties and a long document are no protection when the core questions are left unclear.
Effort or result: where most scope disputes start
There is a fundamental difference between promising to try and promising to achieve. "The consultant will use reasonable skill and care to improve the systems" is an obligation of means - a promise of competent effort, with no breach if the systems do not improve despite proper work. "The consultant will deliver a system processing 10,000 transactions per hour by 31 December" is an obligation of result - if the target is missed, how hard anyone tried is irrelevant.
Most scope disputes begin here: the supplier thinks it promised effort, the client thinks it was promised an outcome, and the wording supported both. Decide which you are giving or taking for each obligation, because the risk allocation is completely different. This has its own guide below.
Acceptance: the standard and the procedure
Defining the work is only half the job; you also have to define when it is done. Vague standards like "acceptable to the Client" or "meets industry standards" just defer the fight - acceptable to whom, measured how? Replace them with measurable criteria: a throughput, an error rate, a test protocol that either passes or fails.
And the procedure matters as much as the standard. How acceptance is documented, who approves, what happens on rejection, and what notice unlocks a remedy can decide whether a genuine defect is actually claimable. Both have their own guide below.
How to write a scope clause that holds
Say what is in and what is out, in concrete terms. Specify the deliverables, the performance standard for each, and whether each obligation is one of effort or of result. Define acceptance by measurable criteria and a documented procedure, and tie remedies to that procedure. Then read the scope clause against the rest of the contract for consistency.
The discipline is the same one that runs through interpretation: a court will hold you to what the contract measurably says, not to what you assumed the other side had signed up to deliver.
Use at the desk
Practical checklist
- Define scope in concrete terms - state what is included and what is excluded; avoid "deliver the solution" placeholders.
- For each obligation, decide whether it is one of effort (reasonable skill and care) or of result (a specified outcome), and draft accordingly.
- Replace vague standards ("acceptable", "industry standard") with measurable acceptance criteria.
- Specify the acceptance procedure: documentation, approver, timeline, rejection, rounds of correction, and remedies.
- Tie remedies to the acceptance procedure, and follow it - a notice or report requirement can be a condition precedent to your claim.
- Read the scope clause against the rest of the contract for consistency before signing.
This guide is informational only and is not legal advice. It does not replace advice from licensed counsel on the facts of a specific transaction.
Product demo
Use the guide for context. Use Veqtor for the Word documents.
Watch Claude compare negotiation drafts and create a separate Word document with proposed tracked changes.
See Veqtor work with Word redlines