Definitions decide more than you think
A defined term is not housekeeping. It can decide whether you own the software or only licensed it, whether you can terminate for breach or must accept reasonable remediation, and whether an indemnity covers a self-reported regulatory issue or only a customer complaint. The words you choose in the definitions schedule set the risk allocation of the whole deal.
Recitals do quieter work, but they are not decoration either. They can colour how an ambiguous clause is read, and in the right circumstances they can lock a party into a stated fact by way of estoppel.
How English courts interpret what you wrote
Interpretation under English law follows a settled framework set out by the Supreme Court in Wood v Capita Insurance Services Ltd [2017] UKSC 24. The court asks what a reasonable person with all the background knowledge available to the parties would have understood the words to mean, treating interpretation as a single, iterative exercise.
Two tools sit inside that exercise: textual analysis (the words actually used) and contextual analysis (the commercial setting). They are complementary, not rival philosophies. The more sophisticated and professionally drafted the contract, the more weight the words themselves carry.
Courts will not fix a bad bargain
The hard lesson from Wood v Capita is that it is not the court's job to improve the deal you made. A clause working out badly for one side is not a reason to depart from its natural meaning, and a vague phrase may simply be a negotiated compromise the parties could not make more precise.
In Wood v Capita itself, a professionally drafted indemnity covering losses arising out of claims or complaints registered with the regulator did not extend to a compensation scheme the buyer reached after self-reporting. The claim failed on the words used. Sophisticated parties get the contract they wrote.
Where definitions go wrong
Most definition disputes trace back to a handful of recurring failures: mixing the exhaustive means with the non-exhaustive includes; relying on including but not limited to, which courts can still read restrictively; circular definitions that point at each other; and undefined qualitative words like reasonable, material, or promptly that guarantee an argument later. Each has its own guide below.
A defined term never stands alone. The court reads it against the whole contract, so a definition that works in isolation but contradicts an operative clause will fail.
Where recitals go wrong, and right
Recitals can explain an ambiguous operative clause, but they generally cannot override a clear one. What they can do is record a fact so definitely that a party is estopped from later denying it. The line is drawn by how clearly the recital is expressed: a plain statement of fact can bind, while loose background narrative usually will not.
The practical discipline is the same for both definitions and recitals: say exactly what you mean, check it against the rest of the contract, and assume a court will hold you to the words rather than the intention behind them.
Use at the desk
Practical checklist
- Treat the definitions schedule as risk allocation, not housekeeping - check each term against the operative clauses.
- Assume a court will apply the natural meaning of your words; it will not improve a bad bargain (Wood v Capita [2017] UKSC 24).
- Choose means (exhaustive) or includes (non-exhaustive) for each definition - never both.
- Do not rely on including but not limited to to expand a list; courts can still read it restrictively.
- Remove circular definitions - define each term independently.
- Replace vague qualifiers (reasonable, material, promptly) with thresholds, concrete steps, or measurable timeframes.
- Make recitals accurate statements of fact, and keep operative obligations in the operative clauses.
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