Privity of Contract and Third-Party Rights in the UK

Privity of contract sounds technical, but it causes very practical problems for founders and SMEs. A common mistake is assuming a group company, investor, subcontractor or end customer can enforce a contract they did not sign. Another is relying on a verbal assurance that a third party will be protected, only to find the written terms say otherwise. A third mistake is copying contract wording from overseas material and missing the UK rules that can let some non-parties enforce terms.

If you are about to sign a supply agreement, SaaS contract, services deal or business sale document, this matters.

The question is simple: who gets rights under the contract, and who carries the risk if something goes wrong? The answer is not always limited to the named signatories. UK law still starts from privity, but there are important exceptions, especially under the Contracts (Rights of Third Parties) Act 1999. This guide explains what privity of contract means, when third parties can benefit, what to check before you sign, and where businesses commonly get caught out.

Overview

Privity of contract generally means only the parties to a contract can enforce it or be bound by it. In the UK, that starting point is modified by statute and by certain legal structures, so a third party may sometimes have enforceable rights even if they did not sign.

The practical issue for businesses is not just the legal theory. It is whether your contract clearly says who can claim, who is protected, and whether any third-party rights are intended or excluded.

• Privity usually limits enforcement to the contracting parties.
• The Contracts (Rights of Third Parties) Act 1999 can let a non-party enforce a term in some cases.
• Third-party rights can be created expressly, or they may arise where the contract purports to confer a benefit on an identified person or class.
• Many commercial contracts exclude third-party rights on purpose, but that exclusion must be drafted clearly.
• Related issues often appear in group company arrangements, subcontracting, warranties, indemnities, limitation clauses and customer supply chains.
• Before you sign, check whether anyone outside the named parties is supposed to rely on the deal, receive protection, or have a direct claim.

What Privity of Contract Means For UK Businesses

Privity of contract means your agreement usually creates rights and obligations only between the parties who entered into it. If your business signs a contract with a supplier, a third party will not automatically be able to sue under that contract just because they benefit from it.

That basic rule matters because many business relationships involve more than two people or companies. A founder may negotiate on behalf of a company being formed. A parent company may want affiliate companies to use software under one master agreement. A customer may expect an end user, installer or project owner to rely on warranties. This is where founders often get caught.

The traditional rule

Under the traditional common law position, a person who is not a party to the contract cannot enforce it. That person also generally cannot be made liable under it, although related legal doctrines may still create obligations in other ways.

For example, if Company A hires Company B to provide IT services for a client project, the client usually cannot sue Company B under that contract just because the services were intended to help them. The client may have other claims depending on the facts, but privity means the contract itself is not automatically theirs to enforce.

The UK statutory exception

The main statutory exception in the UK is the Contracts (Rights of Third Parties) Act 1999. This law can allow a third party to enforce a contractual term if one of two routes applies.

• The contract expressly says the third party may enforce the term.
• The term purports to confer a benefit on the third party, and the contract does not show that the parties did not intend the term to be enforceable by that third party.

The third party must also be identified in the contract by name, as a member of a class, or by description. They do not need to exist when the contract is made, which can be useful where rights are intended for future group entities, future owners of goods, or defined categories of users.

Why this matters in day-to-day commercial contracts

For SMEs, this issue often appears in ordinary commercial documents, not just major corporate deals. Before you sign a contract, ask who is expected to rely on it in practice.

Common examples include:

• a parent company negotiating services that affiliates will actually use
• a customer asking for warranties to extend to its group companies, end clients or funders
• a subcontracting chain where the end customer wants direct protection
• software terms that refer to authorised users, contractors or associated entities
• professional services contracts where directors, employees or consultants want the benefit of liability exclusions

If the contract is silent, assumptions can become expensive. One side may think the benefit flows through the commercial arrangement. The other may assume only the named legal entity can claim anything.

Privity is not the whole story

Privity does not mean third parties are always irrelevant. Rights or protections can also be created through collateral warranties, agency arrangements, trusts, assignments, novations, guarantees and indemnities. Those mechanisms work differently, and the drafting matters.

For instance, if a building contractor gives a collateral warranty to a tenant or funder, that third party may have direct contractual rights even though they are not part of the main building contract. Likewise, if contractual rights are validly assigned, the assignee may enforce them. None of that removes the need to understand privity. It just means businesses should not stop at the headline rule.

What about burden as opposed to benefit?

A third party may sometimes be given a benefit under a contract, but the burden of the contract does not usually transfer to them simply because they received that benefit. This distinction matters when businesses try to give non-parties rights without making it clear who pays, who performs and who carries the risk.

For example, a software provider might agree that affiliate companies can use a platform. That does not automatically mean each affiliate is directly liable for fees or indemnities unless the contract structure makes that clear. If you want a non-signatory to have obligations, you usually need a cleaner mechanism, such as making them a party, requiring accession, or using a separate undertaking.

Legal Issues To Check Before You Sign

Before you sign a contract, identify every person or entity that is expected to benefit from it or rely on it. If that list extends beyond the named parties, the drafting needs closer attention.

1. Is any third party supposed to enforce a term?

If the commercial deal assumes someone outside the signature block can bring a claim, say so expressly. Do not rely on general wording if the right is important.

Think about whether the third party should be able to enforce:

• payment obligations
• service levels or delivery standards
• warranties about goods, software or services
• confidentiality obligations
• indemnities
• limitation of liability clauses that are intended to protect personnel or affiliates

Clear wording reduces the chance of later argument about whether a benefit was merely commercial, or legally enforceable.

2. Should third-party rights be excluded?

Many contracts deliberately exclude the operation of the Contracts (Rights of Third Parties) Act 1999. That is common where the parties want a closed set of rights and do not want outsiders claiming under the agreement.

An exclusion can help in supplier and customer contracts where each side wants certainty about who can sue. It can also avoid accidental rights arising for affiliates, end users or subcontractors mentioned elsewhere in the document.

Still, an automatic exclusion is not always the right move. If directors, employees or group companies are meant to rely on a specific protection, excluding all third-party rights may defeat that intention.

3. Who is identified, and how clearly?

The 1999 Act requires the third party to be identified by name, class or description. Vague language can create uncertainty, especially in group structures or layered projects.

Before you accept the provider's standard terms, check whether third parties are described clearly enough. If the clause refers to affiliates, personnel, subcontractors, clients or authorised users, the definitions should be workable and consistent throughout the agreement.

4. Can the parties later vary or cancel the term?

Where a third party has rights under the 1999 Act, the original parties may not always be free to vary or rescind the term without that third party's consent once certain conditions are met. That can affect settlement discussions, contract changes and renegotiations.

This matters in long-term supply, technology and outsourcing arrangements. A clause that looked commercially harmless at signing can reduce flexibility later.

5. Are there better tools than third-party rights?

Sometimes a direct third-party right is the best answer. Often it is not. The practical alternative depends on the deal structure.

Options may include:

• making the relevant entity a party from the outset
• using an accession process for future entities
• granting a collateral warranty
• using a guarantee from a parent company
• assigning rights where that is legally and commercially appropriate
• using agency language if one entity is truly contracting on behalf of another

Each option carries different consequences for liability, control and administration.

6. Do limitation and exclusion clauses protect the people you think they protect?

This is a frequent drafting trap. A contract may cap liability for the supplier, but what about its directors, employees, consultants or subcontractors? If a claim is brought against an individual or related entity, the protection may not automatically extend to them.

Some contracts use third-party rights so those people can rely on exclusions or limitations directly. Others use separate wording designed to protect them. Either way, the point should be checked rather than assumed.

7. Does the contract match the real commercial chain?

Privity problems often reflect a mismatch between the legal paper and the real-world arrangement. Before you spend money on setup, implementation or procurement, map who is actually doing what.

Ask questions such as:

• Who receives the services or goods in practice?
• Who suffers the loss if something fails?
• Who is expected to make a claim?
• Who is giving promises, and who is relying on them?
• Are there group companies, landlords, funders, franchisees, channel partners or end clients involved?

If the contract only captures part of that picture, privity issues are likely.

Common Mistakes With Privity of Contract

The main mistake is treating privity as either absolute or irrelevant. In the UK, neither approach is safe. Businesses need to know when third-party rights are excluded, when they may arise, and whether another structure would fit the deal better.

Assuming a commercial beneficiary has legal rights

Founders often say, “the contract is for our client” or “our sister company will use it too”, and assume that is enough. It is not. A third party may benefit in a commercial sense without having a legal right to enforce the contract.

This is particularly common in agency-style arrangements, reseller models and group procurement.

Excluding third-party rights without reading the rest of the contract

Many precedents contain a standard exclusion of the 1999 Act. That clause may be fine, but it needs to be consistent with the rest of the agreement.

If the contract elsewhere says employees can enforce confidentiality protections, or affiliates may rely on a licence, a blanket exclusion can create contradiction or remove intended rights. Internal inconsistency is where disputes start.

Giving benefits to a class that is too broad or unclear

Wording like “associated persons” or “those connected with the customer” may sound flexible, but it can be uncertain in practice. Poorly defined classes create room for arguments about who qualifies and what they can claim.

That uncertainty can be costly in a dispute and awkward in negotiations with insurers, funders or acquirers who want a clean risk position.

Trying to impose obligations on non-signatories

Businesses sometimes try to give a third party rights while also expecting them to accept contractual burdens, without making them a party. That usually does not work neatly.

If an affiliate, end user or subcontractor needs to comply with material obligations, consider whether they should sign up directly, enter a separate agreement, or be added through a proper accession mechanism.

Relying on verbal promises about who is covered

Before you rely on a verbal promise that “everyone in the group is protected” or “your client can enforce this too”, read the operative clauses. Contract law disputes often come down to the written terms, not the negotiating assumptions.

If a right matters enough to shape price, risk or insurance, it should be spelt out.

Using overseas templates without UK review

This topic is especially vulnerable to cross-border drafting problems. A contract based on Australian, US or other overseas wording may deal with third-party rights differently, or assume a different legal background.

UK businesses should make sure their agreements reflect UK law and the way the 1999 Act interacts with the rest of the contract.

Forgetting future changes in group structure

A startup may sign a contract in one entity, then reorganise, create new subsidiaries or bring in investors. If affiliate use or benefit matters, the agreement should anticipate that possibility.

Otherwise, the business may later discover that the company using the service, receiving the goods or suffering the loss has no direct rights at all.

FAQs

Can a third party enforce a contract in the UK?

Sometimes, yes. The usual rule is that only the parties can enforce a contract, but the Contracts (Rights of Third Parties) Act 1999 can allow a non-party to enforce a term if the contract says so expressly, or if the term purports to benefit them and the contract does not show the parties meant to exclude enforcement.

Do I need to exclude third-party rights in every contract?

No. Many businesses do exclude them, but not every deal should. If a group company, employee, subcontractor or end client is meant to have direct protection or enforcement rights, a blanket exclusion may be the wrong choice.

Can a person who benefits from the contract also be bound by it if they did not sign?

Usually not automatically. A third party may be able to enforce a benefit in some situations, but contractual burdens do not generally transfer to them just because they received that benefit. If you want them to have obligations, use a structure that creates direct commitments.

What is the difference between assignment and third-party rights?

Assignment transfers existing contractual rights from one party to another, subject to the contract and the law. Third-party rights under the 1999 Act let a non-party enforce a term without becoming an original contracting party. They are different tools and should not be treated as interchangeable.

Why does privity matter in supplier and SaaS contracts?

It matters because the business using the service, the affiliates accessing it, or the people relying on liability protections may not be the same as the named customer or supplier. If the contract does not reflect the real user and risk chain, the wrong entity may end up with no claim or no protection.

Key Takeaways

• Privity of contract usually means only the contracting parties can enforce the agreement or be bound by it.
• In the UK, the Contracts (Rights of Third Parties) Act 1999 can create enforceable rights for non-parties in some cases.
• Before you sign, check whether any affiliate, employee, subcontractor, end client or other third party is supposed to benefit from or rely on the contract.
• Do not assume a commercial beneficiary has legal rights, or that a non-signatory can be made liable without proper drafting.
• Exclusions of third-party rights should be deliberate and consistent with the rest of the agreement.
• Where third-party involvement is central to the deal, alternatives such as accession, collateral warranties, guarantees, assignment or direct contracting may work better.

If you want help with third-party rights clauses, supplier and SaaS contract drafting, warranties and indemnities, or limitation of liability terms, you can reach us on 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.