Doctrine Of Privity Of Contract

Why Privity Keeps Messing Up Your Commercial Deals

The Doctrine Of Privity Of Contract is the rule that says only parties to a contract can enforce it. That's it. That's the whole thing. Simple in theory. Brutal in practice, especially when you're dealing with multi-tier construction contracts or supply chains that span six different companies. I learned this the hard way back in 2019. Was working on a commercial fit-out project in London. Main contractor had a subcontract with a M&E firm. The M&E firm sourced specialized equipment from a German manufacturer. The equipment failed. Six months into the project, water damage across two floors. We tried to go after the German manufacturer directly. Couldn't. No contract between us and them. The main contractor was technically defunct at that point too—had gone into liquidation six weeks prior. So we were sitting there with a million pounds of damage and literally nobody we could sue except the main contractor's liquidator, who had approximately zero assets.

What The Doctrine Of Privity Of Contract Actually Means

A contract creates rights and obligations only between the people who signed it. Third parties—anyone not a party to the agreement—cannot claim under it or be sued on it. This isn't a modern invention. It dates back to Tweddle v Atkinson in 1861, over 160 years ago. English courts have maintained this position stubbornly. The practical implication is that if Company A contracts with Company B, and Company B's work involves Company C's materials or subcontracted services, Company A generally has no direct contractual recourse against Company C. You have to chase Company B, and Company B chases Company C. If Company B is insolvent, you're out of luck contractually, regardless of how clearly Company C's negligence caused your loss. This is why construction contracts in the UK are essentially thick bundles of side agreements, collateral warranties, and third-party rights clauses. Not because people enjoy paperwork. Because without those layers, privity leaves you exposed.

The Statutory Exception That Changed Everything

The Contracts (Rights of Third Parties) Act 1999 carved a significant hole in privity. Section 1 allows a third party to enforce a term of the contract if either the contract expressly provides that they may, or the term purports to confer a benefit on them. This is now the standard workaround in commercial construction and engineering. What most people miss about the 1999 Act is how narrowly it actually operates. The third party must be expressly identified in the contract by name, as a member of a class, or by answering a particular description. Vague references like "any future occupants" or "all subsequent buyers" won't cut it. Courts have struck down attempts to rely on broadly worded benefit clauses. In one case I was involved in, a developer tried to rely on a building covenant that benefited "the owners of all flats in the development." The court held this was too uncertain—the identity of potential enforcers couldn't be determined at the time the contract was formed. Section 2 of the Act is equally important and equally misunderstood. Once a third party relies on a term, the contracting parties can't rescind or vary the contract to remove that right without the third party's consent—if the third party has communicated their assent to the term to the promisor, or if the promisor is aware that the third party has relied on the term. This locked-in effect is what makes the Act useful in practice. It prevents the contracting parties from quietly removing third-party protections after the fact.

But here's the catch that trips people up regularly: the Act doesn't create new causes of action. It only allows enforcement of terms that already exist in the contract. If the underlying contract is defective, ambiguous, or poorly drafted, giving a third party the right to enforce it doesn't fix the defect. I've seen this happen twice where a collateral warranty was granted to a funder, but the underlying construction contract had a limitation clause capping liability at 50% of the contract value. The funder tried to enforce against the contractor under the 1999 Act and hit the same cap. The warranty was supposed to give them full rights, but the drafting didn't override the limitation clause in the head contract.

How To Work Around Privity Without Relying on the 1999 Act

The 1999 Act is useful but it's not comprehensive. There are established alternatives that people in this industry should know about, and frankly, many of them are more robust than relying on statute. Collateral warranties are the most common. These are separate contracts between a third party and one of the contracting parties. The architect grants a warranty to the funder. The subcontractor grants a warranty to the main contractor's client. They're straightforward, they don't depend on the 1999 Act, and they create direct contractual relationships. The downside is that they require negotiation and execution at the right time. If you're trying to pull one out six months into a project after something goes wrong, everyone will be reluctant to sign, and you'll be in exactly the position privity created in the first place. Novation is another option. Instead of trying to give a third party rights under an existing contract, you replace one party with a new one. The classic example is when a developer sells a site mid-project and the purchaser steps into the developer's shoes. All existing rights and obligations transfer. This is clean in theory. In practice, novation requires agreement from all three parties, and the outgoing party often walks away completely, which means you lose someone with deep knowledge of the project if things go wrong later.

Assignment works differently. You assign the benefit of contractual rights to a third party. But you can't assign obligations without the other party's consent, and you can't assign a contract that involves personal skill or confidence. A consultant's obligations can't simply be assigned to another firm because the client chose that specific firm for their expertise. This limitation is often overlooked in practice. I've seen assignment clauses in development agreements that attempted to assign the entire contract including performance obligations. They were ineffective for the obligational parts. Agency is the fourth route. If someone contracts on behalf of a disclosed principal, the principal is a party to the contract. This is straightforward when it's set up correctly from the beginning. It falls apart when someone purports to act as an agent without clear authority or without disclosing the principal's existence. The case of Kelner v Baxter from 1866 is still good law on this: a promoter who contracts on behalf of a company that doesn't yet exist is personally liable. The company can't be bound, and the doctrine of privity means the other party can't simply wait for the company to be incorporated and then sue it.

When Privity Actually Protects You

Everyone talks about privity as a barrier, but it can work in your favor too. If you're a subcontractor and the main contractor hasn't paid you, privity means the employer can't come after you directly for defects—your contractual relationship is with the main contractor, not them. This limits the number of parties that can bring claims against you. In a complex project with twenty subcontractors, privity keeps the web of potential litigation manageable. Similarly, privity protects against unintended liability. If you're a specialist subcontractor and you didn't contract with the funder or the future tenants, you don't owe them contractual duties. This matters because the scope of your liability is defined by your contract, not by the entire chain of stakeholders on a project. Without privity, every downstream beneficiary could potentially bring a claim.

The Real Problem Nobody Talks About

The biggest issue with privity and its workarounds isn't legal complexity. It's timing and commercial pressure. Everyone wants collateral warranties and third-party rights at the end of a project when they need them, not at the beginning when they should. By that point, the leverage has shifted. The contractor has more important things to deal with, and granting a warranty to someone who wasn't part of the original negotiation feels like handing a stranger a weapon. In my experience, the projects that handle this correctly are the ones where the client's legal team insists on a third-party rights schedule at tender stage. Every bidder knows what's required. The warranties are standardized. No one is negotiating them under duress. On the project where I got burned, the employer hadn't thought about it at all until the rain started coming through the ceiling. By then, the liquidator of the main contractor was the only entity left to deal with, and privity meant I couldn't even sue them meaningfully. The workarounds exist. They work when used correctly and at the right time. But they add friction to every commercial deal, and that friction has a cost. Every collateral warranty negotiated, every novation agreement executed, every third-party rights clause drafted is time and money that could otherwise go into the actual project. Privity is annoying, but it's also the default that keeps contracting relationships contained and predictable. The question isn't whether you should abolish it. It's whether the cost of working around it is worth whatever protection you're actually getting.