top of page
Search

TUPE, Mobilisation and Day 1 Readiness: What Every FM Lead Needs to Coordinate

TUPE mobilisation Day 1 readiness coordination for FM leads

It is week ten of mobilisation. The HR team has just finished TUPE consultation. The mobilisation lead has just discovered that three roles marked for transfer are now subject to ETO dismissal — a decision made two weeks ago that nobody thought to communicate across workstreams. The induction programme is already written. The cost model is already approved. The Day 1 roster does not reflect the workforce that is actually transferring.

This is not a hypothetical. It is one of the most common failure modes in FM contract mobilisations — and it happens because TUPE and mobilisation are typically treated as separate tracks, owned by different teams, measured by different milestones, and managed by people who are barely speaking to each other.

The employment lawyer worries about TUPE 2006 regulations — consultation timelines, ELI obligations, measures disclosure. The mobilisation lead worries about Day 1 readiness — headcount in place, systems live, compliance certificates held, service delivery confirmed. Nobody is joining the dots. And at week ten, it collides.

Why TUPE and Mobilisation Are Interdependent Workstreams

The GOV.UK TUPE guide makes clear that TUPE transfers carry over employment contracts, liabilities, and continuity of service. But what it does not tell you is that every milestone in the TUPE process has a direct operational consequence for the mobilisation programme.

TUPE is not just a legal compliance exercise. It is the mechanism by which your workforce arrives. The DCS Group's analysis of TUPE in facilities management identifies employee liability information, consultation, and measures disclosure as the three areas most likely to cause downstream operational disruption — not because of legal failures, but because operational teams do not know to act on them.

The NEC Contracts Practice Note on FM and TUPE reinforces this: in FM contracts, TUPE is not a one-off event at transfer date — it is a continuous thread running through the entire mobilisation lifecycle. Every TUPE decision shapes the operational picture. Every operational decision creates a TUPE risk.

The 5 Coordination Points Where TUPE and Mobilisation Must Align

1. ELI receipt → workforce cost model finalised

The Employee Liability Information pack from the outgoing employer is the foundation of your cost model. Until ELI is received and verified, your assumptions about salary, hours, terms, and entitlements are estimates. Do not finalise the workforce cost model until ELI is in hand, reconciled, and challenged where necessary.

2. TUPE consultation close → induction planning can begin

You cannot finalise induction content, team structures, or Day 1 briefings until consultation has formally closed. Induction materials that reference operational changes not yet disclosed to transferring employees create legal exposure and destroy trust on day one. Consultation close is the green light for induction planning — not before.

3. Transfer date confirmed → payroll and IT provisioning locked

Once the legal transfer date is confirmed, IT and payroll provisioning can be locked. This includes system access, email creation, badge provisioning, and CAFM configuration. Any slippage in transfer date confirmation cascades directly into IT readiness, and IT unreadiness cascades into Day 1 failures that are visible to the client.

4. Measures disclosed → operational changes can be scheduled

Measures under TUPE — changes to terms, working practices, or operational structures — cannot be communicated informally before formal disclosure. Once disclosed, they can be scheduled into the operational change plan. The sequencing matters: premature communication of operational changes before formal TUPE disclosure is a legal liability.

5. ETO decisions made → organisation design confirmed

Where an economic, technical, or organisational (ETO) reason for dismissal or variation exists, those decisions must be made before organisation design is finalised. Headcount planning built on an incomplete picture of ETO outcomes will unravel. The organisational chart for Day 1 should not be signed off until ETO decisions are resolved.

What Day 1 Readiness Actually Requires from the TUPE Workstream

Day 1 readiness is usually defined in operational terms: systems live, staff inducted, compliance in place, client briefed. But Day 1 readiness also has a TUPE dimension that is often invisible until it fails.

It requires confirmed headcount — not estimated headcount. It requires disclosed measures — not planned measures. It requires completed consultation — not ongoing consultation. And it requires a workforce that has been told what is changing, when it is changing, and what it means for them.

Day 1 operational confidence is only achievable when the TUPE workstream has delivered its outputs in the right sequence, at the right time, with full visibility to the mobilisation team.

The RACI for a Joint TUPE/Mobilisation Governance Structure

A joint governance structure requires clearly defined ownership across both workstreams. The following RACI covers the critical intersection points:

  • ELI receipt and reconciliation — Responsible: TUPE/HR Lead | Accountable: Mobilisation Director | Consulted: Finance, Ops Lead | Informed: Client-Side HR

  • TUPE consultation management — Responsible: TUPE/HR Lead | Accountable: Mobilisation Director | Consulted: Employment Solicitor | Informed: Mobilisation Manager

  • Transfer date confirmation — Responsible: Mobilisation Manager | Accountable: Mobilisation Director | Consulted: TUPE/HR Lead, Client | Informed: All workstream leads

  • Measures disclosure — Responsible: TUPE/HR Lead | Accountable: Mobilisation Director | Consulted: Employment Solicitor | Informed: Mobilisation Manager

  • ETO decisions — Responsible: TUPE/HR Lead, Legal | Accountable: Mobilisation Director | Consulted: Finance | Informed: All workstream leads

  • Induction planning — Responsible: Mobilisation Manager | Accountable: Mobilisation Director | Consulted: TUPE/HR Lead | Informed: Training Lead

  • IT provisioning — Responsible: Technical Lead | Accountable: Mobilisation Manager | Consulted: HR Lead | Informed: All

  • Payroll setup — Responsible: Finance/HR | Accountable: Mobilisation Manager | Consulted: TUPE/HR Lead | Informed: All

The Three Most Common Coordination Failures — and How to Prevent Them

1. ELI received but not actioned operationally

ELI lands in the HR inbox and is treated as a legal document. Nobody routes it to finance for cost model reconciliation or to the mobilisation lead for headcount planning. Fix: ELI receipt triggers a mandatory three-way review — HR, Finance, Mobilisation — within 48 hours.

2. Consultation closes with no handoff to mobilisation

Consultation is managed entirely by HR and the employment solicitor. When it closes, nobody tells the mobilisation team. Induction planning is delayed by two weeks while people work out who owns next steps. Fix: Consultation close is a formal programme milestone with a defined handoff briefing to the mobilisation workstream.

3. Operational changes communicated before measures are disclosed

Operational leads brief their teams on upcoming changes before TUPE measures have been formally disclosed. Employees raise grievances. Legal exposure increases. Fix: Any communication about post-transfer operational arrangements must be cleared by the TUPE/HR Lead before issue.

Develop Your Capability

If you are managing TUPE and mobilisation simultaneously, the following MCFM Global Academy courses will sharpen your capability across both workstreams:

Sources

 
 
 

Comments

Rated 0 out of 5 stars.
No ratings yet
Add a rating
bottom of page