TUPE Explained for FM Managers Who Didn't Study Law (But Have to Live With It)

You're three weeks into mobilisation planning. Staffing schedules are drafted, the RAMS are being reviewed, and the client is already asking for a dashboard update. Then someone in the contracts team says: 'Has anyone actually looked at the TUPE obligations yet?' The room goes quiet.

TUPE is one of the most consequential areas of employment law for FM contract managers — and one of the most consistently left until it becomes urgent. This article won't turn you into an employment lawyer. It will make sure you know what you're dealing with, when it applies, and where the real exposure sits.

TUPE — the Transfer of Undertakings (Protection of Employment) Regulations 2006 — protects employees when the organisation or service they work for changes hands. In plain terms: if you take over a contract, you inherit the workforce. Their contracts, their continuity of service, their terms — all of it moves with them.

This applies across England, Scotland, and Wales, whether or not the parties intend it to. It applies to incoming providers, outgoing providers, and clients insourcing a service.

There are two legal triggers, and both are routine in FM. The first is a business transfer — where an economic entity transfers to a new owner while retaining its identity. The second — and far more common in FM — is a service provision change (SPC). Under Regulation 3 of the TUPE Regulations, an SPC covers three scenarios: outsourcing (a client stops doing something in-house and hands it to a contractor), retendering (a new contractor takes over from the incumbent), and insourcing (a client brings a previously outsourced service back in-house).

A cleaning contract retendered to a new provider, a security service outsourced for the first time, a TFM mobilisation replacing a bundle of single-service contracts — all almost certainly trigger TUPE. The legislation — not the contract — determines whether it applies. You cannot contract your way out of it.

Under Regulation 4, the incoming provider inherits: contracts of employment (salary, hours, holiday entitlement, and all other contractual terms); continuous service (an employee with eight years at the incumbent arrives with eight years of service); all liabilities (outstanding grievances, disciplinary matters, tribunal claims, and historic failures of the outgoing employer); and collective agreements (any trade union recognition and collectively bargained terms in force at transfer).

That liability point is critical. Incoming FM providers inherit not just the staff but the legal and contractual history attached to them. Warranties and indemnities can allocate that risk contractually — but they don't make the underlying liability disappear.

Before any TUPE transfer, the transferor (outgoing provider) must provide Employee Liability Information (ELI) to the incoming provider. Under Regulation 11, this must be delivered no less than 28 days before the transfer date and must include: identity and age of each transferring employee; written particulars of employment; details of any disciplinary or grievance procedures taken in the previous two years; details of any current or anticipated tribunal claims; and details of any collective agreements that will remain in effect post-transfer.

ELI is your workforce baseline for mobilisation. You cannot build a credible cost model or onboarding plan without it. Late or incomplete ELI is one of the most common mobilisation failures in FM — and while the outgoing provider bears the legal exposure, you are left with the operational gap.

Both outgoing and incoming providers have a duty to inform and consult affected employees — or their representatives — before transfer. Under Regulation 13, this covers all employees who may be affected, not just those directly transferring. The information provided must include the fact and date of the transfer, the legal and economic implications for staff, and any measures either party envisages taking.

That last word is where FM managers most often get it wrong. In TUPE law, 'measures' covers any proposed change to how work is organised — rotas, reporting lines, management structures, uniforms, site arrangements. If you plan to change it, you must disclose it. Not disclosing a planned change to avoid early resistance is a compliance failure, not a tactical decision.

A defensible process requires genuine dialogue, written records of what was communicated and when, and documented responses to employee representatives. Failure to consult is one of the most direct routes to workforce disengagement at the point of transfer.

Under Regulation 7, any dismissal where the sole or principal reason is the TUPE transfer itself is automatically unfair. This applies before and after the transfer, and it applies to both outgoing and incoming providers.

The only permitted exception is an ETO reason — economic, technical, or organisational — that entails genuine changes in the workforce. Redundancy can qualify, but only where there is a real reduction in workforce need. It does not cover situations where the incoming provider simply does not want to retain certain staff.

An FM provider who dismisses transferred staff without a genuine, documented ETO rationale is sitting on an unfair dismissal claim. TUPE-connected dismissal is not a theoretical risk; it is a live tribunal liability that mobilisation teams need to plan around — not discover after the fact.

TUPE is not an HR checklist item. In FM contract transitions, it shapes workforce costs, onboarding timelines, legal exposure, and operational readiness from day one. The FM managers who handle it well treat it as a mobilisation workstream in its own right — planned from contract award, not raised in the final weeks before go-live.