How to Review TUPE Clauses in a UK Outsourcing Agreement

Reeve, Ops at a 23-person UK B2B services firm, is about to treat “TUPE shall not apply” as a skip-the-staff-process sticker. Finance wants Friday. The hidden risk is a waiver with no ELI date. Knowing how to review tupe clauses in a uk outsourcing agreement is a 25-minute hunt: test whether a service provision change actually bites, lock Employee Liability Information 28 days before, split entry from exit, freeze dumps, then allocate, demand ELI, or walk to employment counsel.

September 2026. English law; exclusive courts of England and Wales. The packet — the exact file set that will be signed — is the customer MSA (master services agreement — the frame contract vendors hang order forms on) plus Schedule 7, an exhibit — attached schedule or appendix. Four people only work that helpdesk.

Schedule 7: “The parties agree that the Transfer of Undertakings (Protection of Employment) Regulations 2006 shall not apply to this Agreement.” No list, no 28-day date, clause 19.4 dumps all employment liabilities on the supplier, silent holiday, no freeze, no exit. AE Slack: “Don’t poke HR.” Friday is booked.

Writing “TUPE shall not apply” does not stop a service provision change — and on a first-generation outsource Reeve’s firm is the transferor who must give Employee Liability Information. TUPE 2006 reg 18 applies ERA 1996 s.203: you cannot contract out for the staff. Pinsent Masons: indemnities only reallocate money; claims still run against the incoming employer. ACAS (23 February 2026): no minimum grouping size. Colour, not a verdict.

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

What does TUPE actually bite — business transfer or service-provision change?

Circle Schedule 7. A waiver that TUPE shall not apply is not a fact test. Log an organised grouping situated in Great Britain whose principal purpose is this client’s work, activities after go-live fundamentally the same, not goods-only, not a short-term event — or “sticker only — fail.” Do not write a verdict.

Do: run the reg 3 limbs on these four people who only work that desk. Don’t: treat the sticker as a skip. GOV.UK colour: a cleaner whose employer outsources cleaning is likely protected; an ad-hoc courier pool is not. For example, four dedicated helpdesk people is grouping colour, not a finding. Escalate employment counsel — a qualified lawyer, not the chatbot.

When is Employee Liability Information due, and who pays for bad data?

On a first-generation outsource Reeve’s firm is the transferor and must give Employee Liability Information not less than 28 days before the transfer. Circle: no date, no list. Log who produces the pack, the 28-day date, and who pays if it is late or wrong — or “silent ELI — fail.”

Do: date the pack and add an indemnity for late or inaccurate ELI. Don’t: sign a go-live inside 28 days with an empty file. Reg 11 is the 28-day duty. ACAS ELI: compensation could be at least £500 per employee if the pack is late, wrong, or not updated. Reg 12(5): not less than £500 per employee unless just and equitable to award less. In practice, a contractual sum for bad ELI is a factor — silence is not a plan.

How do you split entry indemnities from exit / second-generation?

Circle “Supplier shall be responsible for all employment liabilities.” One dump is not an allocation. Split entry (pre-transfer claims, holiday pay, consultation failure, woodwork) from exit, where today’s supplier becomes transferor on a retender.

Do: name those entry heads; mirror them on exit with a duty to give ELI to a successor. Don’t: accept clause 19.4 as covering in and out. Trethowans (2 September 2026): transferee wants pre-transfer protection; transferor wants post-transfer. GOV.UK: holiday entitlement transfers. Silence means the incoming employer still owes the employee. Occupational pensions (reg 10) are a watch-item.

Why does a freeze stop last-minute term changes, headcount dumps, and bonus spikes?

Circle the missing freeze. Dumping a fifth person in week 12, or paying a leaving bonus, is how the grouping and the cost move. Demand no new hires, no material T&C or bonus changes, and no dismissals without consent once a transfer is likely — or “no freeze — fail.”

Do: freeze from the date a transfer is likely. Don’t: tidy terms “because we outsourced.” Reg 4(4): a variation is void if the sole or principal reason is the transfer — that protects employees, not the commercial fight. Davenport (29 July 2026): transfer-connected dismissals are treated as automatically unfair. Escalate; do not invent a dismiss-window.

Is this staff transfer, not IR35 status, and not a named key-person swap?

These four people are employees whose contracts may transfer by operation of law. That is not IR35 status on a PSC statement of work, and it is not a named-lead swap on a professional-services agreement. Stay on the organised grouping.

If the fight is substitution, control, mutuality, or a status determination statement, that is a different hunt: IR35 substitution, control, and mutuality review. If the fight is named-lead notice, approval, or overlap, that is a different hunt: key-person replacement notice review. Return to Schedule 7.

When to allocate, demand ELI, or walk to employment counsel

Allocate means redline the waiver, write a working assumption that SPC may apply, date ELI 28 days before, split entry from exit, and freeze. Demand the pack now. Walk to employment counsel — do not sign Friday — if waiver, silent ELI, one-line dump, no freeze, and no exit remain.

Success bar: a one-page log plus one Friday pause sentence. The sticker is not that sentence. Workflow: SPC vs business transfer → ELI 28 days + who pays → entry vs exit → freeze → not B38 / not B78 → allocate / demand ELI / walk to employment counsel. Upload the same PDF to document analysis for a first-pass — first machine pass extracting clauses before a human reads every page. A human still opens Schedule 7. Verify every High flag — high-severity item a named human still opens.