Privity and Contract Terms

Privity of contract is the common law rule that only a party to a contract can sue or be sued upon it. A contract, on this view, is a private arrangement between the people who made it — nobody standing outside that relationship, however much they might benefit from or be harmed by it, has standing to enforce it.

Two nineteenth- and early twentieth-century decisions cemented the rule. In Tweddle v Atkinson (1861) 1 B&S 393, the fathers of a bride and groom agreed with each other that each would pay the young husband a sum of money. When one father died without paying, the husband — the person the whole arrangement was designed to benefit — sued the deceased father's estate. He lost. He was not a party to the agreement between the two fathers, so he had no right to enforce it, however obviously it had been made for his benefit.

Half a century later, the House of Lords entrenched the same principle at the highest level in Dunlop Pneumatic Tyre Co Ltd v Selfridge & Co Ltd [1915] AC 847. Dunlop sold tyres to a dealer on terms that the dealer would not resell below a fixed price, and would extract the same promise from anyone it resold to. Selfridge, who bought from that dealer, broke the price-maintenance promise. Dunlop sued — and lost, because Dunlop was not a party to the contract between the dealer and Selfridge. The House of Lords confirmed, in ringing terms, that only a party to a contract can sue on it.

Privity is intimately bound up with another doctrine you already know: consideration must move from the promisee. If you cannot show you gave something in exchange for the promise, you are, almost by definition, a stranger to the bargain — and the rule that consideration must move from the promisee is really the same insight expressed from the other direction. The two doctrines reinforce each other: a stranger to the consideration is a stranger to the contract.

Definition: Privity of contract — only a person who is a party to a contract may sue or be sued on it; a person cannot acquire rights, or incur liabilities, under a contract to which he is not a party.

Why should a trainee solicitor care about a Victorian rule? Because clients constantly try to arrange their affairs so that someone outside the paper contract gets a benefit from it — a wedding gift arrangement, a building contract that is meant to benefit future purchasers of the building, an insurance policy meant to protect a family member. Privity is the trap that can silently defeat all of these unless one of its exceptions or the modern statutory scheme applies.

Long before Parliament intervened, the courts and commercial practice had already carved out four established routes around the privity wall.

• Agency. Where an agent contracts on behalf of a principal, the agency relationship allows the agent to create contractual rights and obligations that arise directly between the principal and the third party — the agent effectively drops out of the picture, and privity is never really breached because the "real" contracting party was the principal all along.
• Assignment. A contracting party can transfer the benefit of a contract to a third party by assignment, and critically this can be done without needing the original promisor's consent. The assignee steps into the assignor's shoes to enforce the right (though the burden of a contract cannot be assigned in the same way).
• Trust of a promise. Equity permits a beneficiary to enforce a contractual promise made for his benefit where the promisee holds the benefit of that promise on trust for him. Because the promisee-as-trustee is suing (or is compellable to sue) for the beneficiary, the beneficiary effectively obtains an indirect right of enforcement without being a party in the strict sense.
• Collateral contract. Courts will sometimes find a separate, second contract running alongside the main one — a collateral contract between the promisor and the third party — which, being a genuine contract in its own right (with its own consideration), simply bypasses privity restrictions rather than breaking them.

These devices are useful, but they are narrow, fact-dependent, and often artificial. By the late twentieth century, the Law Commission concluded that English law needed a general statutory mechanism — and Parliament obliged.

Source: Houses of Parliament in 2022 by Terry Ott from Washington, DC Metro Area, United States of America, CC BY 2.0.

The Contracts (Rights of Third Parties) Act 1999 ("CRTPA 1999") creates a statutory exception to the common law doctrine of privity. It does not abolish privity — the common law rule and its old exceptions survive untouched — but it gives third parties a freestanding statutory right to enforce contractual terms in defined circumstances. This is now the primary route SQE1 candidates are expected to apply in problem scenarios, so know the sections cold.

Section 1: When can a third party enforce a term?

Section 1(1)(a) — a third party may enforce a term where the contract expressly provides that he may.

Section 1(1)(b) — a third party may enforce a term that purports to confer a benefit on him.

Limb (a) is the easy case: the parties have written "X shall be entitled to enforce clause 5" into the contract. Limb (b) is broader and more litigated: it catches terms that were never drafted with third-party enforcement explicitly in mind but which, on their face, are for the third party's benefit — think of a building contract clause promising quality of work to "the purchaser and any subsequent owner."

Limb (b) is deliberately reined in by section 1(2), which disapplies it where the contract, properly construed, shows that the parties did not intend the term to be enforceable by the third party. So a benefit that is merely incidental — the third party happens to gain from the arrangement but the parties never meant to hand him an enforceable right — falls outside the Act.

Section 1(3) then imposes an identification requirement: the third party must be expressly identified in the contract by name, as a member of a class, or by description. This can be satisfied loosely — "the tenants of the building" or "any future purchaser" will do — but the third party must be identifiable from the contract's own terms. Helpfully for commercial planning, the third party need not be in existence when the contract is entered into: a company not yet incorporated, or a child not yet born, can still be the intended beneficiary of a term.

Section 2: Locking in the third party's right

Once a third party has an enforceable right, can the original two contracting parties simply agree between themselves to tear it up? Section 2 says: not freely. The parties are restricted from rescinding or varying the contract to remove a crystallised third-party right without that third party's consent, once the right has "crystallised."

Section 2(1) tells you exactly when crystallisation happens — the third party's right becomes protected from unilateral variation once:

1. he has communicated his assent to the term to the promisor, or
2. the promisor knows that the third party has relied on the term, or
3. the promisor could reasonably have foreseen that the third party would rely on it, and reliance has in fact occurred.

Think of this as the Act's equivalent of reliance-based estoppel: the contracting parties keep full freedom to vary or cancel the third-party benefit right up until the third party does something (or the promisor should have anticipated something) that makes it unfair to snatch the benefit away.

Sections 3–5: Fighting fair, and not paying twice

Giving a stranger a right to sue would be a poor bargain for the promisor if it also meant losing every defence he would otherwise have had. Section 3 prevents this: it allows the promisor to raise against the third party any defence or set-off that would have been available against the promisee had the promisee been the one suing. The third party inherits the claim on the same footing the promisee would have stood.

Section 4 preserves the promisee's own, entirely separate right to enforce the contractual term — the Act adds a new claimant, it does not remove the old one. Both the promisee and the third party may, in principle, have a live right to enforce the very same term.

That duplication creates an obvious risk: what if the promisor is forced to pay the promisee for the third party's loss, and then the third party sues too? Section 5 protects the promisor from double liability, ensuring he is not made to pay out twice, to both the promisee and the third party, for what is really the same loss.

Section 6: What the Act does not touch

Section 6 carves out several categories where the statutory scheme simply does not apply, mostly because other legal regimes already handle third-party interests in these areas:

• contracts on a bill of exchange, promissory note, or other negotiable instrument;
• a company's articles of association, which do not create enforceable third-party rights under the Act for non-members;
• contracts of employment, which a third party cannot use the Act to enforce against an employee;
• contracts for the international carriage of goods, where third-party enforcement is excluded for most rights, other than exclusion or limitation clauses (which third parties, such as subcontractors named in a Himalaya clause, may still rely on).

Finally, remember that the whole scheme is opt-out: contracting parties may expressly exclude the operation of the CRTPA 1999 by including a term to that effect — many commercial contracts routinely do exactly this, precisely to avoid the uncertainty of section 1(1)(b) claims from unintended beneficiaries.

Privity and the 1999 Act answer the question who can enforce a term. The rest of this topic answers a different but equally exam-favourite question: what counts as a term at all, and how seriously does the law treat it?

Express terms and the parol evidence rule

An express term is one the parties have actually agreed — whether orally, in writing, or through some combination of both. Where a contract has been reduced to writing, the parol evidence rule presumes that the written document contains the whole of the agreed terms, and in principle excludes extrinsic evidence offered to add to, vary, or contradict it. In practice this presumption is riddled with exceptions (evidence of a genuinely separate collateral contract, proof of a trade custom, evidence that the writing was never intended to be the entire agreement, rectification claims, and so on) — but as a starting presumption for SQE1 purposes, treat the written document as prima facie complete.

Implied terms: four different routes in

Not everything a contract requires is written down. An implied term is one not expressly stated by the parties but nonetheless treated as forming part of the contract. Terms can be implied into a contract in four distinct ways, and SQE1 problem questions frequently hinge on spotting which route applies:

Implied in fact. Courts imply terms in fact only where necessary to make sense of what the parties actually agreed, using two classic tests:

Under the business efficacy test from The Moorcock (1889) 14 PD 64, a term will be implied in fact where necessary to give the contract commercial effectiveness — without it, the contract simply wouldn't work as a piece of business.

Under the officious bystander test from Shirlaw v Southern Foundries (1926) Ltd [1939] 2 KB 206, a term will be implied where it is so obvious that, had an officious bystander suggested it while the parties were negotiating, both would have testily agreed "of course" — it goes without saying.

Implied by custom. A term implied by custom incorporates an established local or trade custom into the contract — unless that custom is inconsistent with the contract's own express terms, in which case the express terms win.

Implied in law. Distinct from implication in fact, a term implied in law is imposed by the courts as a matter of policy onto a recognised category of relationship — employer-employee, landlord-tenant, and similar established relationships — regardless of what these particular parties actually intended. The court is not asking "what would these parties have agreed?" but "what does this type of relationship require as a matter of law?"

Source: Half-timbered tudor buildings, High Holborn by Iridescenti, CC BY-SA 3.0.

Implied by statute. Parliament has implied specific terms into specific categories of contract, and the sale-of-goods and supply-of-services statutes are exam staples:

Conditions, warranties, and the innominate middle ground

Once you know a term exists, the next question a solicitor must answer for a client facing a breach is: what remedy does this breach actually give me? That depends on the term's legal status.

A condition is a term that goes to the root of the contract; its breach entitles the innocent party to terminate the contract and claim damages. In Poussard v Spiers and Pond (1876) 1 QBD 410, an actress's obligation to perform from the opening night of an opera was held to be a condition — missing the opening undermined the whole point of engaging her, so the producers were entitled to terminate and hire a replacement.

A warranty, by contrast, is a minor term not central to the contract's main purpose; its breach entitles the innocent party only to damages, with no right to terminate. In Bettini v Gye (1876) 1 QBD 183, a singer's obligation to attend rehearsals before a performance was held to be merely a warranty — missing a few days of rehearsal was a nuisance, not something that struck at the heart of the engagement.

Note that the label a contract attaches to a term — even calling it expressly "a condition" — is not conclusive of its true legal classification. Courts look past the label to the term's real significance in the contract.

The strict condition/warranty split proved too rigid for terms whose breach could range from trivial to catastrophic depending on circumstances — a single clause breached in a minor way one day and a devastating way the next. The Court of Appeal's answer was the innominate term, established in Hong Kong Fir Shipping Co Ltd v Kawasaki Kisen Kaisha Ltd [1962] 2 QB 26. An innominate term is one whose classification as a condition or warranty is not fixed in advance but depends on the seriousness of the consequences flowing from its breach in the actual event.

Under the Hong Kong Fir test, breach of an innominate term is treated as if it were breach of a condition — giving a right to terminate — only where the breach deprives the innocent party of substantially the whole benefit intended under the contract. A less serious breach of the same term leaves the innocent party with a damages claim only.

For a client asking "can I walk away from this contract?", these three categories — condition, warranty, innominate term — are the analytical spine of the answer, and Hong Kong Fir is the case to reach for whenever the term's classification is not settled in advance by statute or clear authority.

Even once you know a term is part of the contract and know its status, you still have to work out what it means. English courts interpret contractual terms objectively: the question is not what either party subjectively intended, but what meaning the language would convey to a reasonable person equipped with the parties' background knowledge at the time of contracting.

Source: Junction of Colmore Row and Bennetts Hill, Birmingham - DSC08808 by Rept0n1x, CC BY-SA 3.0.

Two further interpretive tools matter for SQE1:

• The contra proferentem rule construes an ambiguous term against the party who drafted it, or who is seeking to rely on it — historically deployed with particular force against parties trying to rely on exclusion and limitation clauses they themselves inserted.
• An entire agreement clause states that the written contract constitutes the complete agreement between the parties, and excludes reliance on prior negotiations or representations. It functions as the parties' own contractual reinforcement of the parol evidence presumption, closing off arguments that some earlier draft, email, or conversation added extra terms.

A client dispute rarely announces which doctrine governs it. A subcontractor's defective work harms a building's eventual purchaser: is that purchaser a stranger under Tweddle and Dunlop, or does section 1(1)(b) of the CRTPA 1999 hand her an enforceable right because the warranty of quality purports to benefit her? A supplier misses a delivery date: is that clause a condition, a warranty, or an innominate term whose status depends on how badly the delay actually hurt the buyer, à la Hong Kong Fir? A written contract omits something the client swears was agreed: does the parol evidence rule, or an entire agreement clause, shut the argument down — or does an implied term under The Moorcock or a statute like the Sale of Goods Act 1979 fill the gap regardless?

Every one of these questions is really the same skill applied to different facts: identify who can sue, on what term, with what remedy. Master that sequence, and privity, third-party rights, and the taxonomy of contractual terms stop being a list of separate rules to memorise and become a single, coherent method for answering the client's question — what can I actually do about this?