TUPE Transfer Pack (Incoming Employer)
TUPE transfers go wrong when the receiving employer guesses. Due diligence gaps, missed consultation steps, unlawful harmonisation attempts: each one is a liability. This gives you the structure, the documents, and the guidance to do it properly.
Customised to you
All documents pre-filled with both company names, transfer date, and your specific details.
Due diligence built in
ELI request templates and due diligence checklists so you know what to ask for and when.
Presentation decks included
Employee briefing decks ready to present. Not just documents, the tools to communicate properly.
HR FAQ on harmonisation
What you can and cannot do post-transfer. The guide that stops you making expensive mistakes.
What's included (22 documents)
Word documents
- How to Use This Pack (step-by-step guide)
- Leaders' Guidance (due diligence, ELI custom and practice verification, ETO reasons, commercial indemnities, integration)
- HR FAQ: What You Can and Can't Do Post-Transfer
- Due Diligence Checklist
- Employee Liability Information Request Letter
- Measures Letter to Transferor
- Welcome Letter with Measures Explanation
- Consultation Invite to Employee Representatives
- Individual Consultation Meeting Record
- Employee FAQ: What TUPE Means For You
- Post-Transfer Welcome Letter
- Post-Transfer Terms Comparison
- Terms Harmonisation Letter
- ETO Reason Change Notification
- Objection to Transfer Acknowledgement
- Day-One Integration Checklist
Excel spreadsheets
- ELI Due Diligence Template (pre-transfer)
- ELI Transfer Template (comprehensive)
PowerPoint presentations
- TUPE Project Plan (timeline deck)
- Welcome & Introduction (employee briefing)
- What TUPE Means For You (employee rights deck)
- 🔒 Secure payment via Stripe
- ✓ Written by a Chartered FCIPD professional
- ⬇ Instant download after customisation
Need someone to run the whole thing?
If you need someone to manage the transfer end to end, run the consultation, or provide interim HR leadership during a complex transition, I do that too. Every TUPE is different, so this is a conversation, not a checkout.