The 1999 Act routes

The Contracts (Rights of Third Parties) Act 1999 lets a third party enforce a term in two ways: section 1(1)(a), where the contract expressly provides that it may; and section 1(1)(b), where the term purports to confer a benefit on it, unless on a proper construction the parties did not intend the term to be enforceable by the third party (section 1(2)). The third party must be identified by name, class or description but need not exist when the contract is made (section 1(3)).

Two further provisions matter. Section 2 restricts variation or rescission once the third party has assented or relied (or reliance was foreseeable and has occurred), unless the contract disapplies that protection. Sections 3 and 5 preserve the promisor's defences and prevent double recovery. The default commercial practice has been to exclude the Act and then carve in specifically identified beneficiaries - because the section 1(1)(b) presumption can capture beneficiaries the parties did not intend, and section 2 can fetter their freedom to vary.

DEFRA v PCSU strengthened the presumption

Secretary of State for the Department for Environment, Food and Rural Affairs v Public and Commercial Services Union [2024] UKSC 41 strengthened the section 1(1)(b) presumption considerably. The Supreme Court held that sections 1(1)(b) and 1(3) create a strong but rebuttable presumption that a term purporting to confer a benefit on an expressly identified third party is enforceable by that party, and that the party resisting enforcement must establish a positive common intention that the term not be enforceable.

The point is not that an express, clear exclusion of the Act is ineffective - it remains effective. It is that silence, ambiguity, or poor coordination between a general exclusion and any carve-outs is now more likely to leave the section 1(1)(b) presumption intact. Parties who do not want third parties enforcing a benefit need to say so clearly.

Use section 1(1)(a) for security agents and the like

Where a non-party is meant to enforce specific terms, the safer route is express section 1(1)(a) wording rather than reliance on an uncertain section 1(1)(b) 'benefit' analysis. HNW Lending Ltd v Lawrence [2025] EWHC 908 (Ch) - the first decision to interpret the scope of section 1(1)(a) - upheld a security agent's right to enforce because the loan agreement expressly provided that, although not a party, the agent could take the benefit of and specifically enforce the agreement under the Act. The court held that section 1(1)(a) enables enforcement where the contract expressly so provides, even without a benefit being conferred.

The drafting lesson is to anchor security-agent (and similar) enforcement rights in express section 1(1)(a) language. Common cases for carving in third-party rights include group-company exclusions and limitations, lender or security-agent enforcement, software-licence benefits flowing to customer affiliates and sub-licensees, guarantor reliance on the principal contract's limitation provisions, and additional insureds.

The cross-border angle

Civil-law systems reach third-party-rights questions through their own domestic doctrines. German law has the Vertrag zugunsten Dritter (sections 328 to 335 of the BGB), conceptually similar to section 1 of the 1999 Act but not requiring an exclusion to opt out - the parties' intention is the test. French law has the stipulation pour autrui (Articles 1205 to 1209 of the Code civil), under which the third party acquires a direct right from the date of acceptance.

The cross-border risk is that an English-law contract that is silent - and so leaves the section 1(1)(b) presumption intact - may simultaneously be analysed by a German or French court as creating a direct beneficiary right under that system's own doctrine. An English-law drafting silence can therefore generate parallel third-party arguments in different forums, which is a further reason to address third-party rights expressly rather than leave them to the default.

Use at the desk

Practical checklist

  • Decide deliberately: exclude the 1999 Act, then carve in the specific third parties you intend.
  • After DEFRA v PCSU, make any exclusion express and clear - silence may leave the section 1(1)(b) presumption intact.
  • Name the beneficiaries (or class) and identify the precise clauses each may enforce.
  • Anchor security-agent and similar rights in express section 1(1)(a) wording (HNW Lending v Lawrence).
  • Contract out of section 2 if you want to retain freedom to vary or rescind without third-party consent.
  • In a cross-border deal, remember civil-law doctrines may confer direct beneficiary rights regardless of the Act.

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

Continue reading

Pillar guideBoilerplate clausesBoilerplate clauses

How the boilerplate clauses - entire agreement, NOM, notices, waiver, severability and third-party rights - actually operate under English law, and what changes in a cross-border deal.

5 min readThird-party rightsParties to a contractThe Contracts (Rights of Third Parties) Act 1999

How non-parties can enforce your contract, why the 2024 Supreme Court ruling strengthened the presumption, and the exclusion clause you need.

4 min readGroup liabilityParties to a contractIs a parent company liable for its subsidiary?

Why separate legal personality means no automatic liability, what Vedanta and Okpabi changed, and why you need a parent guarantee.

4 min readCross-borderBoilerplate clausesEnglish law as the only connection

When English law is the only connection, the boilerplate must survive the enforcement forum - Rome I Articles 3, 9 and 21, the purely-domestic carve-out, and New York Convention Article V(2)(b).

5 min read