Checkory
Licence grant with sublicence boxes for affiliates and end users

How to Review a Right to Sublicence Affiliates and End Users

Label a software sublicence as granted, banned, or consent-gated, name affiliates and end users, and write what happens when the master ends.

•9 min read•Article
💡

Key takeaway in 30 seconds

Knowing how to review a right to sublicense to affiliates and end users means labelling the clause granted, banned, or consent-gated. Name affiliates, hosts, and true end users, and shut resellers. Cap the grant, ban a further sublicence, and write the ending if the master licence ends. Then add that carve-out, or walk.

Lyle’s Friday job is the affiliate and end-user sublicence review on Clause 4.2. The risk is an open “any person” grant that never names the Irish affiliate, the host, or true end users. Label the clause, list recipients, cap further grants, and write the ending. Then add a carve-out, or walk. Do it on the file you will actually sign, and keep one log.

September 2026. England and Wales. Lyle is Ops at a 19-person UK SaaS and the licensee. The packet — licence, order form, and schedules — is Friday’s file set. Clause 4.2 lets Licensee grant sublicences to any person. No recipient list, consent gate, further-grant ban, flow-down, copy, or liability line. Silence if the master ends. AE Slack says not to narrow it.

An open grant is not tidy cover for one affiliate and your customers. Silence on termination does not reliably switch those permissions off. Patents Act 1977 s.30(4)(a) (checked 2026-09-30) allows a patent sub-licence only to the extent the licence provides. That is patent colour, not the copyright rule here. On copyright software, VLM [2013] EWHC 228 (Ch) is the caution: a sub-licence survived where the grant was wide enough. CMS (2013, updated 2026) says to write automatic termination into the head licence and the sub-licence.

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

Read Clause 4.2 as one of three labels: granted, banned, or consent-gated. “Any person” is a grant, not a named affiliate right. A total ban blocks the Irish affiliate and Lyle’s end users. Silence is not a grant.

Do: write the label in the margin before you argue scope. Don’t: treat AE’s “already covered” line as the label. IP Draughts on making sublicensing express (2011) (checked 2026-09-30): state whether sublicensing is permitted rather than hope a court implies it. If the fight is only “Customer and its Affiliates may use” the seats, that is a different hunt. Open how to review affiliate and group-company usage rights and leave this page. In practice, Lyle stays here because Clause 4.2 is a downstream grant.

Comparison table of granted, banned, and consent-gated sublicence labels
Comparison table of granted, banned, and consent-gated sublicence labels
💡

Typical mistake

AE sells “open is better” while Clause 4.2 sublicences the software to any person — log the missing recipient list, not the Slack line

What to allow: affiliates, hosts, and true end users?

Name three classes and stop. Affiliates, hosts who run the module for you, and true end users. A reseller is not on that list. “Any person” fails on the first read.

Do: define affiliate, and end the sublicence if that status ends. A host may run the module for Lyle, with no resale right. End users sit on terms no weaker than the master. Don’t: leave “any person.” Law Insider affiliate sublicence samples (2026) (checked 2026-09-30): affiliates only, and the licensee stays liable. Law Insider sublicensing-scope samples (2026) use a ladder: affiliates free, service contractors on notice with no sale right, others only with consent. Simply-docs sub-licensing template (UK template, checked 2026-09-30) limits agent sub-licences to services. For example, Lyle’s host is a contractor, not a reseller.

Workflow diagram for reviewing a sublicence to affiliates and end users
Workflow diagram for reviewing a sublicence to affiliates and end users

How do you keep a sublicence inside the master grant?

A sublicence cannot exceed the master grant. Object code, field, territory, term, and the user cap travel down. The cap counts Lyle and every sublicensee together. No further sub-sublicence unless the master says so.

Do: add “no greater than the rights granted in this licence” and “the sublicensee shall not grant a further sublicence.” Don’t: assume a customer of your customer is still a true end user. Vaquill licence-grant dials (checked 2026-09-30): end users on terms no weaker than the master, affiliates only for consistent use. The common pattern is no further-grant ban. Clause 4.2 has none.

Checklist board for keeping a sublicence inside the master grant
Checklist board for keeping a sublicence inside the master grant

Review flow-down, the copy, and who stays liable?

Three controls travel together. Flow the restrictions. Send the licensor a copy. Say the licensee remains liable. A sublicence does not relieve Lyle.

Do: flow confidentiality, the user cap, the further-grant ban, and termination. Require a copy within a stated number of days. Redact price, not the grant. Don’t: accept “they will follow our terms” with no clause. Law Insider sublicense-rights samples (2026) (checked 2026-09-30): copies to the licensor, head terms, and the licensee stays responsible. Law Insider client-sublicence samples (2026) treat a sublicensee’s failure as the licensee’s act, and still add up the usage cap. IP Draughts on sublicensing drafting (2011) (checked 2026-09-30): a sublicence to affiliates is cleaner than folding them into “Licensee.” No general right to appoint a subcontractor. For example, name the host.

When to write what happens if the master licence ends?

Write the ending. Do not infer it. Each sublicence should end when the master ends, and the sublicence should say so. A direct licence for end users is a separate bargain.

Do: say the sub-licence ends if the head licence ends. Don’t: tell Finance that cancellation automatically cuts every end user. VLM shows the opposite when authority was wide. Pinsent Masons on VLM (2013) (checked 2026-09-30): on those facts, the sub-licensor’s insolvency did not end use. CDPA 1988 s.92 (checked 2026-09-30) defines an exclusive copyright licence in writing, signed for the owner. It is not a sublicence code. In practice, write the ending into Clause 4.2.

When do you add an affiliate and end-user carve-out, or walk?

Add the carve-out when “any person” becomes the affiliate, the host, and true end users. Walk if the vendor keeps “any person” or will not write the ending. A total ban is also a walk if the product cannot ship.

Success bar: one log and one pause sentence, Clause 4.2 versus “don’t narrow it.” Path: label, name recipients, cap further grants, flow-down, copy, liability, write the ending, then carve-out or walk. Upload the same file to document analysis. That is a first-pass: a machine pass that marks clauses. Verify every High flag: a high-severity item a human still opens. Escalate to counsel: a qualified lawyer.

Lyle’s sublicence log

CheckLyle’s paperAction
B63 fenced?This is a downstream grantStay on the sublicence.
Label?Granted to any personNot a named carve-out
Recipients named?No listAffiliate, host, end users
Further grant banned?SilentBan sub-sublicensing
Flow-down, copy, liability?All three missingWrite all three
Master-end outcome?SilentSublicences end with the master.
DecisionAE: don’t narrow itCarve-out, or walk.

Hunt

1

Freeze the packet

Grant, affiliate definition, seat cap, hosting schedule, termination. Search sublicen, affiliate, end user, reseller, and further.

2

Label the sentence

Granted, banned, or consent-gated. Silence is not a grant. Group seat use is a different page.

3

Name eligible recipients

Affiliates, a host for your benefit with no resale right, and true end users. Shut resellers.

4

Cap scope and further grants

No wider than the master. Add up the user cap. No further sublicence unless the master says so.

5

Flow down, copy, and liability

Put the restrictions in the sublicence. Copy it to the licensor. The licensee stays liable.

6

Write the master-end outcome

Each sublicence ends with the master, and it says so. Do not infer that from silence.

7

Carve out or walk

Replace “any person” or walk. Pause Friday if AE says not to narrow an open grant.

Frequently asked questions

Do group companies need a sublicence?▼
Yes if they are not parties and the grant names only Licensee. Seat-use wording is a different checklist.
Is a hosting provider a sublicensee?▼
Name the host as a contractor if it runs the software for you. Do not call it “any person,” and do not let it grant onwards.
Do sublicences survive termination of the master licence?▼
Only if this paper says so. Silence is the risk. VLM shows a software sub-licence can survive a wide grant. Write that each sublicence ends with the master.
Can the sublicence be wider than our licence?▼
No. Keep field, territory, term, and the user cap inside the master grant. Count seats across you and every sublicensee.
May an end user sublicense again?▼
Not by default. Ban a further sublicence unless the master expressly allows that second grant.
Who is liable if an affiliate breaches?▼
You, if the paper says the licensee remains liable for sublicensee acts. Without that sentence, the path to you is an argument, not a clause.

Next steps

Fill the log on Clause 4.2 before Friday. For a machine pass on the same file, use document analysis. A human still opens the recipient list and the ending.

What to do next

Sources

Read also

Related guides

Updated: September 30, 2026