Key takeaway
A permitted user and a person able to enforce a contract term are different entries. Review beneficiaries and change rights before assuming only the signers matter.
The group-user clause leaves a second question open
A proposed license permits the buyer’s subsidiaries to use an agreed dataset. The commercial team records the buyer as the only customer, then assumes it can later amend the arrangement with that buyer alone. That assumption needs its own contract review: who, if anyone, has an enforceable third-party right?
Under section 1 of the Contracts (Rights of Third Parties) Act 1999, a nonparty can enforce a term through the Act where the contract expressly permits it, or within the statutory benefit route and its qualifications. The person must be expressly identified by name, class or description. The contract’s proper construction and relevant terms matter. This is an English-law review of an ordinary commercial license, not a rule that every person who benefits automatically gets enforcement rights.
Complete the beneficiary map before selecting wording
Hypothetical example: Fictional Archive Ltd negotiates with Buyer Ltd. A draft permits use by Buyer Ltd’s named operating subsidiaries. Its service promise benefits those users, while another clause appears to exclude statutory third-party enforcement. No agreement has been executed and no affiliate has received records.
The completed issue map below deliberately separates access scope from contract enforcement. The owner can take this finite set of issues to the contract drafter instead of declaring all affiliates either parties or strangers. A row marked unresolved is a useful decision when the terms point in different directions.
| Entity or class | Use permission in draft | Enforcement issue |
|---|---|---|
| Buyer Ltd | Proposed contracting customer | Party rights under the actual contract |
| Named operating subsidiaries | Included as proposed authorised users | Reconcile benefit wording with the exclusion clause |
| Future group members | Definition not settled | Clarify class description and scope before relying on it |
| Unrelated recipient | Not included | No use permission established by this example |
Variation may require a separate consent review
Section 2 addresses rescission and variation where a third party has a section 1 right. It identifies circumstances involving communicated assent, known reliance or reasonably foreseeable actual reliance. It also permits express contractual arrangements concerning variation without third-party consent or specified consent circumstances.
Accordingly, the project owner should not treat a buyer’s signature on a change note as the whole review. The legal reviewer needs the third-party-rights provision, variation clause, identification of affected persons and relevant assent or reliance facts. Those facts cannot be reconstructed from a CRM field saying one customer.
In the illustration, the proposed remedy is to resolve the drafting before granting use. If rights later exist, a narrower license amendment might affect a beneficiary’s entitlement even when the named buyer agrees. This article does not decide whether statutory consent is required in a real transaction or whether a court could dispense with it.
Record the clause that changes the answer
Attach the exact authorised-user definition, benefit promise, third-party exclusion or permission and variation language to each reviewed entity class. Distinguish a statement that someone may use a product from a statement that the person may enforce a promise. If the parties intentionally exclude the statutory route, have the reviewer check the actual words and any other relevant legal routes.
The Act contains exceptions, and not every document associated with a company is an ordinary commercial license within the same analysis. Section 6 covers specified categories, including certain constitutional and employment arrangements and carriage contracts. Do not lift this worksheet into one of those settings without a new applicability review.
Nothing in the worksheet adds a person to the data-permission map. Even an enforceable contractual promise cannot, by itself, supply the licensor’s missing rights to another party’s personal information or confidential content.
Give the commercial owner a bounded next step
For the fictional draft, hold the unresolved affiliate expansion and ask the contract drafter to align use, beneficiary and variation provisions. Preserve what was changed and which definition was reviewed. After that review, the business owner can decide whether the commercial scope is still acceptable.
The offer-comparison worksheet can keep the proposed group scope visible, while rights review captures underlying source restrictions. VOID’s permissioned introduction does not create beneficiary rights or authorise affiliate delivery. The practical gain is a clearer question about who can insist on which promise, before wider use or later amendments make that question harder.
Use this review agenda with your legal and privacy advisers. Requirements depend on the records, jurisdictions and intended use.