Protection of Employment Regulations 2006 TUPE: A Guide

You usually find out a TUPE transfer is happening after the commercial decision has already been made.

A business unit is being sold. A cleaning, field service, payroll, or IT support contract is moving to another provider. The board wants a low-risk handover. Managers want certainty. Employees want straight answers. HR is left holding the detail, the timetable, and much of the legal exposure.

That’s where understanding TUPE moves from theory to daily practice. TUPE isn’t just an employment law topic for lawyers. It shapes who transfers, what data must be shared, how consultation is handled, whether dismissals are lawful, and how smoothly the new employer can absorb people into its HR systems without creating avoidable claims.

In practice, the organisations that handle TUPE well do three things early. They identify whether TUPE applies. They control the consultation and data process tightly. They use technology to create a clean audit trail instead of relying on scattered spreadsheets, inboxes, and late-night document chasing.

What is TUPE and When Does It Apply?

TUPE stands for the Transfer of Undertakings (Protection of Employment) Regulations 2006. The regulations were enacted as Statutory Instrument 2006/246 and came into force on 6 April 2006, replacing the original 1981 regulations. Their core purpose is clear. When a relevant transfer happens, employees don’t lose their employment because the business or service changes hands. Their contracts transfer automatically to the new employer with unchanged terms and conditions.

The easiest way to explain TUPE is as a relay race. The baton is the employment relationship. One employer passes it to another, but the runner receiving it can’t decide to swap the baton for a different one halfway through. The job, the contract, and the continuity move across with the transfer where TUPE applies.

The two situations HR directors see most often

Most HR teams encounter TUPE in two broad scenarios.

• Business transfer. A business, part of a business, or an organised economic activity moves from one employer to another.
• Service provision change. A client outsources a service, brings it back in-house, or moves the service from one contractor to another.

A business transfer often arises in a sale, merger, acquisition, or carve-out. If a trading division is sold and employees are assigned to that part of the undertaking, TUPE may apply.

A service provision change is often where the practical arguments start. Common examples include facilities management, cleaning, catering, customer service, logistics support, and field-based operational teams. A company might outsource a service for the first time, end an outsourcing arrangement and bring the work back internally, or retender and appoint a new provider.

What counts in the real world

HR directors usually get into trouble when they focus on labels rather than the underlying facts. Calling something a “new contract” doesn’t stop TUPE applying if the work, the organised grouping of employees, and the responsibility for carrying it out have effectively moved.

That’s also why status and working arrangements matter. Before a transfer, it helps to sense-check whether the people said to be “outside scope” really are outside scope. Questions around worker status, substitution clauses, and the actual working relationship can become highly relevant, and Stewart Accounting Services employment status insights are a useful reminder that contractual wording on its own won’t always decide the point.

TUPE analysis starts with the operating model, not the org chart.

Practical examples

A few examples make the trigger points clearer:

• A manufacturer sells one operating division. The employees dedicated to that division may transfer with it.
• A housing provider changes cleaning contractor. The organised team delivering that service may move to the incoming contractor.
• A professional services firm brings payroll back in-house. Employees assigned to the outsourced payroll service may transfer back.
• A group reorganises internally. Internal reshuffles can be more complex, and you need to examine whether there is a relevant legal transfer between employers rather than assuming TUPE automatically applies.

The first job in any TUPE project is to make an evidence-based call on scope. If that step is rushed, every step after it becomes harder.

Employee Rights and Employer Obligations Under TUPE

A TUPE transfer changes the legal employer, but it does not wipe the slate clean for the people who move across. Under Regulation 4(2), the incoming employer takes over the employment relationship with its rights, duties, and liabilities intact. For an HR Director, that means the transfer is not an onboarding exercise. It is a risk transfer, a records transfer, and a management test all at once.

What transfers with the employee

The practical effect is wider than salary and job title. The transferee usually inherits the contractual position the employee had immediately before transfer, along with liabilities connected to that employment.

That often includes:

• Pay and contractual allowances
• Accrued holiday and holiday arrangements
• Continuity of service
• Hours, place of work, notice terms, and other express contractual terms
• Live grievances, disciplinary history, and employment claims linked to the transferring employment

HR teams often focus first on the visible data points. Basic pay, start date, reporting line. The bigger exposure usually sits in the background. Missing variation letters, inconsistent allowances, unresolved absence cases, or a manager who has handled performance badly for months can all become the transferee’s problem after day one.

That is why document quality matters. If records are scattered across shared drives, inboxes, and local spreadsheets, the legal position becomes harder to assess and much harder to defend. In practice, a well-structured Microsoft 365 environment helps reduce that risk. Dynamics 365 can give HR one auditable employee record, track inherited terms, and flag exceptions before they become post-transfer disputes.

The duty is not passive

The incoming employer cannot assume that liability only attaches to matters it knew about. A cautious transferee tests the data it receives, identifies gaps early, and pushes for clarification while there is still time to act.

I usually advise clients to separate inherited issues into three categories:

1. Terms that must be honoured immediately, such as pay, hours, and continuity
2. People risks that need active management, such as grievances, long-term sickness, disciplinaries, or protected disclosures
3. Contract areas that may need legal review, such as mobility clauses, commission structures, restrictive covenants, or collective terms

That triage helps HR decide what needs operational action, what needs legal input, and what can be monitored.

Dismissal protection is stronger than many managers assume

Under Regulation 7(1), a dismissal will usually be automatically unfair if the reason is the transfer itself, unless there is an economic, technical, or organisational reason involving changes in the workforce. The point is simple. A transfer is not a free opportunity to remove awkward roles, tidy up legacy teams, or impose a preferred structure without proper justification.

The pressure usually comes from commercial integration plans. Leaders want one pay model, one set of processes, one structure. That may be commercially sensible, but TUPE asks a different question. What is the underlying reason for the proposed change, and can the employer show that it is not solely transfer-driven harmonisation?

What an ETO reason looks like in practice

An ETO reason needs more than a preference for administrative consistency. In real terms, the employer should be able to show:

• a genuine business reason
• a change affecting the workforce, such as numbers, functions, or structure
• a fair process, with proper consultation and individual consideration where required

HR discipline makes the difference between a defensible decision and an expensive one. If managers are discussing redundancies, relocations, or exits around the transfer date, every rationale, meeting note, and approval trail needs to line up. Basic process errors still matter. So do notice obligations. If your team is reviewing post-transfer dismissals or agreed exits, keep the practical points in this guide to notices of termination in view.

Contract changes after transfer

This is another area where businesses get caught. A term is not safe to change on the mere basis that both employers agree it would be cleaner. Changes connected to the transfer are heavily restricted, and harmonisation for convenience is a common source of claims.

Sometimes there is a real operational case for change. Sometimes there is not. The mistake is treating all inherited differences as anomalies that HR should iron out quickly. In a TUPE context, difference is often lawful. Forced uniformity may not be.

A sensible approach is to document:

• the proposed change
• the business reason for it
• whether the reason is connected to the transfer
• the alternatives considered
• who was consulted, when, and what was discussed
• why the employer believes the process and outcome are fair

Those records should sit in one place, not across email chains and personal notes. Within Dynamics 365 and the wider Microsoft 365 stack, HR can log consultation activity, retain version-controlled letters, restrict access to sensitive case files, and preserve an audit trail if the decision is challenged later.

In TUPE work, good judgment matters. Good records matter just as much.

The TUPE Transfer Timeline and Consultation Process

A TUPE transfer rarely fails because the HR team didn’t know the rules existed. It fails because the process runs late, ownership is blurred, or key information arrives in fragments.

The practical way to manage TUPE is to treat it as a structured workstream with clear deadlines, named owners, and one central record of what was issued, to whom, and when.

The consultation duty

Both transferor and transferee have duties around informing and, where measures are proposed, consulting appropriate representatives of affected employees. That obligation shouldn’t be left until the commercial terms are finalised. By the time leaders feel “ready” to talk, the window for meaningful consultation is often already narrowing.

The quality of consultation matters as much as the fact of it. Employees and representatives need clear information about the transfer, the likely timing, the reasons for it, and any measures envisaged.

Consultation works best when HR can explain the change in plain English. If managers can’t describe the transfer clearly, employees won’t trust the process.

Employee Liability Information and the hard deadline

One of the most important operational requirements is Employee Liability Information, often shortened to ELI. The current employer must provide ELI at least 28 days before the transfer date.

That information typically covers the identity of transferring employees, their terms and conditions, and details of claims, grievances, disciplinary matters, and other relevant employment issues. If ELI is incomplete, late, or disorganised, the incoming employer starts blind.

A surprising number of transfers drift into avoidable risk because HR teams collect payroll data in one file, contractual terms in another, sickness and case data in emails, and consultation notes somewhere in SharePoint or on local drives. The issue isn’t lack of effort. It’s lack of process control.

A working timeline HR can actually use

What a robust consultation process looks like

The organisations that handle this well usually follow a disciplined sequence:

• Map the affected population early. Don’t forget employees on family leave, sick leave, secondment, or long-term absence.
• Decide who the representatives are. If no suitable representatives exist, elections may be needed.
• Prepare one agreed narrative. Mixed messages from leadership, HR, and line managers create distrust quickly.
• Separate legal points from operational promises. Managers should never improvise on pay, location, or role changes.
• Track every communication. Dates, recipients, versions, and responses should be logged.

A practical lesson from live transfers is that consultation and data diligence should run together. If the employee list is still being debated, the consultation message is often shaky. If the consultation message is unclear, employee questions expose the gaps in the data.

Common TUPE Pitfalls and Key Case Law Highlights

At the point a transfer looks settled commercially, HR risk often starts to rise. I usually see the same pattern. The parties agree the deal shape, assume the people issues are straightforward, then discover too late that scope, consultation records, and employee data do not stand up to challenge.

The exposure is real. Failure to inform and consult can lead to a protective award of up to 13 weeks’ gross pay per affected employee. Transfer-related dismissals can also become expensive if the reason for dismissal, or the process behind it, does not meet the legal test. In practice, the greater problem for many HR directors is not just tribunal cost. It is inheriting avoidable disputes on day one.

Pitfall one. Getting the scope decision wrong

The first error is treating TUPE status as obvious before anyone has tested the facts properly. That happens often in outsourcing, insourcing, and contractor change exercises, where service boundaries are messy and employees may split time across several accounts.

Scope errors rarely stay theoretical. They become arguments about who should transfer, whether assignments were genuine, and whether people left off the list were excluded for convenience rather than legal reason. Employees on family leave, long-term sickness absence, or atypical working arrangements are often where the claim starts.

Case law has repeatedly shown that tribunals look at substance over labels. If the organised grouping, activities, and assignment evidence point toward a transfer, a contractual description or commercial preference will not rescue a weak position.

Pitfall two. Consultation that cannot be defended

Late consultation is common. Defensible consultation is much rarer.

The problem is not only timing. It is quality. If representatives receive vague statements about "possible changes" with no detail on measures, impact, or timing, the employer has created risk without building trust. If line managers improvise answers that conflict with the formal message, that record can be damaging later.

Digital discipline matters. A Microsoft-based HR team should not be running TUPE consultation from scattered email chains and local files. Using a Dynamics 365 HR platform integrated with Microsoft 365 workflows gives HR one place to log consultation dates, version-controlled communications, representative questions, and management responses. That does not remove the legal duty. It makes the duty easier to evidence.

Pitfall three. Treating ELI as a data drop

Employee Liability Information often fails in a more practical way than legal teams expect. The file arrives on time, but it is incomplete, inconsistent, or stripped of context.

Salary, job title, and start date matter, but those are rarely the records that cause the post-transfer dispute. The harder issues are unresolved grievances, active disciplinaries, pending family leave, informal adjustments, secondment arrangements, and historical commitments that sit outside the standard contract template. If the transferee discovers those after transfer, confidence falls quickly between the parties and the integration plan starts under strain.

A stronger approach is to validate ELI like any other risk data set. Reconcile it against payroll, HR case records, absence history, and manager-held exceptions. If the transfer is being managed inside Microsoft 365, that means controlled document storage, clear version history, named data owners, and an exceptions log that can be reviewed before cutover.

Pitfall four. Post-transfer harmonisation pushed too early

This is the point where operational pressure usually collides with TUPE protection. Leaders want one payroll structure, one policy set, and one set of terms. The business case may be understandable. The legal route is often much narrower than stakeholders expect.

Changes are not automatically blocked after a transfer, but changing terms because the business wants inherited arrangements to disappear is where employers get into trouble. HR directors need to separate genuine organisational change from administrative tidying. If there is an economic, technical, or organisational reason entailing changes in the workforce, that still needs proper analysis, consultation, and process. It should never be presented as a simple alignment exercise.

Key case law HR should keep in mind

Litster v Forth Dry Dock still matters because it shaped the courts’ broad approach to employee protection around transfers. The practical lesson is simple. Do not rely on a narrow reading of timing or status to exclude someone from protection if the facts suggest they were dismissed to avoid the transfer.

Wilson v St Helens Borough Council remains a warning on harmonisation. Even where change appears commercially sensible, a transfer-linked attempt to replace inherited terms with new ones can fail.

Daddy’s Dance Hall is still cited for the same broad principle. Employee agreement on its own does not necessarily make a transfer-connected contractual change lawful.

None of those cases are just for lawyers. They affect how HR should document decisions, frame communications, and challenge business pressure before commitments are made.

What good practice looks like in live transfers

The HR teams that reduce TUPE risk usually do four things consistently:

1. Test assignment and scope using actual working patterns, not assumptions.
2. Record consultation activity in a way that can be produced quickly and defended clearly.
3. Audit ELI for omissions, disputes, and exceptions rather than accepting a spreadsheet at face value.
4. Treat post-transfer changes as a separate employee relations and legal workstream with its own approval path.

TUPE problems often begin as project control failures. They end as legal disputes because no one fixed the basics early enough.

Managing TUPE with HR Management for Dynamics 365

Monday starts with a transfer steering call. By Wednesday, HR is checking one spreadsheet against payroll, legal is working from a different employee list, and a line manager has sent consultation notes that never reached the central file. That is how a manageable TUPE transfer turns into a control problem.

TUPE is usually won or lost in the quality of the records, approvals, and handoffs. The legal framework matters, but the operational risk sits in fragmented data. If the organisation cannot show who is transferring, what information was issued, what measures were proposed, and when decisions were approved, the process is exposed.

For Microsoft-based organisations, the practical answer is to run TUPE inside the systems already used for HR, documents, identity, and reporting, rather than building another standalone tracker.

Manual transfer packs still create the same problems I see on live projects. Version confusion. Missing approvals. Late corrections to employee liability information. Weak audit trails when a challenge lands after transfer. A Dynamics 365 and Microsoft 365 setup will not remove legal judgement, but it does give HR directors a controlled way to manage the process and evidence the decisions behind it.

What good digital TUPE control looks like

A sound setup is built around governed records and clear ownership.

• Structured employee records in Dataverse. Keep one controlled record for each affected employee, with transfer status, assignment rationale, contractual data, absence history, and key dates.
• Role-based access through Entra ID. Limit access to sensitive transfer data by function and seniority, especially where commercial teams, payroll, and employee relations all need different views.
• Document control in Microsoft 365. Store consultation letters, representative communications, meeting notes, ELI working papers, and approval records in managed locations with retention and permission rules applied.
• Workflow automation with Power Automate. Trigger tasks for consultation milestones, payroll cut-off dates, document issue, and approval points so deadlines do not depend on inbox reminders.
• Power BI reporting for transfer governance. Give the project board a live view of outstanding data gaps, unresolved employee queries, consultation actions, and readiness by workstream.

That model works because it reflects how TUPE runs. It is cross-functional, date-sensitive, and heavily document-driven.

Where Dynamics 365 helps most

The first gain is control over employee liability information. HR can pull contract terms, job data, pay elements, disciplinary records, grievance history, and absence information from governed records instead of rebuilding them manually for each request. That reduces avoidable reconciliation work and makes exceptions easier to spot early.

The second gain is consultation administration. A well-configured workflow can log who received what, when meetings took place, what questions were raised, and whether proposed measures changed. That matters in practice. Consultation disputes often turn on the quality of the record, not just the intent behind the meeting.

Third, transfer-day execution becomes easier to manage. Access changes, organisational assignment, onboarding tasks, document issue, and policy acknowledgements can all sit within one controlled process. HR does not need to chase the same update across email, shared drives, and separate service desks.

The fourth gain is audit readiness. If the transferee later queries missing information, or an employee challenges what they were told before transfer, the organisation can produce a dated record of approvals, communications, and data changes. That shortens investigations and improves the quality of legal advice because the evidence is easier to retrieve.

For teams reviewing whether the wider Microsoft stack is the right fit, this overview of Dynamics 365 HR and connected HR transformation options is a useful starting point.

Why purpose-built HR tooling is better than patching TUPE through project tools

Generic project software can track actions, but TUPE needs more than a task list. It needs employee-level data control, restricted access to sensitive records, document retention rules, and a reliable link between case activity and the underlying HR record.

Hubdrive’s HR Management for Microsoft Dynamics 365 is known as a hire-to-retire solution built on Dataverse, with modules for recruitment, onboarding, document management, time, absence, and compliance processes. For TUPE, that architecture is useful because the transfer touches live employee data, contractual records, workflow approvals, and post-transfer administration. HR is not managing a one-off event. It is controlling a change to the employment relationship across multiple systems and stakeholders.

I usually advise HR directors to test the platform against four scenarios before committing. Can it hold a defensible record for each affected employee? Can it separate access between HR, legal, payroll, and managers? Can it evidence consultation activity clearly? Can it support post-transfer tasks without creating a second shadow process? If the answer to any of those is no, the configuration needs more work.

What doesn’t work

Some patterns create problems repeatedly:

• Using spreadsheets as the record of truth. Version control fails quickly once multiple teams start updating transfer data.
• Using email as the approval system. Important decisions become hard to evidence and easy to miss.
• Splitting HR, legal, and payroll records across unmanaged folders. Reconciliation takes longer and errors survive into transfer day.
• Treating TUPE as a data migration exercise. The core requirement is governance over people data, consultation activity, and decision-making.

The strongest setups support judgement with evidence. That is what reduces risk.

A Practical TUPE Compliance Checklist

A strong TUPE plan is built from small controls done consistently. The checklist below is the one I’d want an HR director to have beside them from the first transaction meeting to the first month after transfer.

Pre-transfer planning

• Confirm whether TUPE applies. Test the facts, not just the deal label.
• Identify affected employees. Include people on leave, long-term sickness, and non-standard arrangements.
• Set governance early. Name the HR lead, legal lead, operational lead, and payroll owner.
• Create a live risks and decisions log. If scope changes, record why.
• Review planned organisational changes. Separate genuine business need from post-transfer tidy-up.

Information and consultation

Use a written plan rather than a series of ad hoc meetings.

• Check representative arrangements. Existing representatives may be suitable, or elections may be needed.
• Prepare clear information for representatives. Keep the language accurate and plain.
• Document proposed measures carefully. Don’t let managers overpromise or improvise.
• Keep meeting notes and issue logs. Questions raised during consultation often reveal data gaps.

A consultation process is only as strong as the records behind it.

Due diligence and ELI control

This stage deserves far more discipline than it usually gets.

1. Compile the employee list and assignment rationale.
2. Check contractual terms against actual practice.
3. Gather ELI data fully and consistently.
4. Review live claims, grievances, and disciplinary matters.
5. Validate payroll and benefits data before disclosure.
6. Issue ELI on time and retain proof of delivery.

Where you need a broader operational framework for obligations, policies, and record keeping, this human resources compliance guide is a useful companion piece.

Transfer day and post-transfer integration

The legal transfer may happen on a single date. The employee experience doesn’t.

• Check payroll cutover and access rights. Errors here damage confidence immediately.
• Confirm continuity-sensitive records. Service, leave, and contractual data must be accurate.
• Issue welcome and practical communications. Employees need to know who to contact and what changes, if any, apply.
• Escalate unresolved people issues quickly. Don’t let inherited cases sit unowned.
• Review any proposed post-transfer changes cautiously. Document the reason and process before acting.

Simple communication templates to prepare

Keep drafts ready for:

• Representative information letter
• Employee announcement
• Manager briefing note
• ELI cover note
• Post-transfer welcome message
• FAQ for employee queries

Good TUPE management is rarely dramatic. It’s controlled, well evidenced, and boring in the best possible way.

Frequently Asked Questions about TUPE

Does TUPE only apply to large employers?

No. TUPE can apply to organisations of different sizes. The legal question is whether there is a relevant transfer, not whether the employer is large or small.

Do all terms transfer exactly as they are?

The general rule is that employment contracts transfer automatically and continuity is preserved, but some areas such as pensions have special rules and need separate review. HR should check the precise benefit design rather than making assumptions based on a broad benefits label.

Can the new employer change terms after transfer?

Sometimes, but not just because it would be administratively easier. Changes connected to the transfer are high risk unless they are supported by a valid ETO reason and handled through a fair process. This is an area where rushed harmonisation causes avoidable disputes.

What if the outgoing employer has unresolved grievances or claims?

Those matters may transfer with the employment liabilities. That’s why pre-transfer diligence matters so much. The incoming employer needs visibility of live issues before the handover, not after.

Do employees have to agree to transfer?

TUPE works through automatic transfer where the regulations apply. That said, employee communication still matters. Even when the legal position is clear, confusion and mistrust can create practical problems quickly if the business handles communication badly.

Does TUPE apply in an internal reorganisation?

Sometimes the answer is no, sometimes not. It depends on whether there is a relevant transfer between legal employers and on the underlying facts. Internal branding changes or management reshuffles on their own don’t answer the question.

How should HR handle TUPE where systems are fragmented?

Treat the transfer as both a legal project and a data-governance project. Centralise the employee list, lock down document versions, control access, log communications, and make sure payroll, HR, and line management are all working from the same record. That’s usually the difference between a manageable transfer and one that unravels under scrutiny.

Protection of employment regulations 2006 TUPE is demanding because it sits at the point where employment law, data quality, operational change, and employee trust all meet. HR directors who do it well don’t rely on last-minute heroics. They create a disciplined process, challenge assumptions early, and use systems that support evidence rather than undermine it.

DynamicsHub helps UK organisations deliver HR transformation built around the way their business works. Hubdrive’s HR Management for Microsoft Dynamics 365 is the premier hire‑to‑retire solution, more powerful, more flexible, and more future‑ready than Microsoft Dynamics 365 HR. If you’re planning a transfer and want a more controlled way to manage employee data, consultation records, workflows, and compliance in your Microsoft environment, speak to DynamicsHub. Phone 01522 508096 today or send us a message.

Chris Pickles Director / Dynamics 365 and Power Platform Architect & Consultant

Chris Pickles is a Dynamics 365 specialist and digital transformation leader with a passion for turning complex business challenges into practical, high-impact solutions. As Founder of F1Group and DynamicsHub, he works with organisations across the UK and internationally to unlock the full potential of Dynamics 365 Customer Engagement, HR solutions, and the Microsoft Power Platform. With decades of experience in Microsoft technologies, Chris combines strategic thinking with hands-on delivery. He designs and implements systems that don’t just function well technically — they empower people, streamline processes, and drive measurable performance improvements. Known for his straightforward, people-first approach, Chris challenges conventional thinking and focuses on outcomes over features. Whether modernising customer engagement, transforming HR operations, or automating processes with Power Platform, his goal is simple: build solutions that create clarity, capability, and competitive advantage.

See Full Bio

Dynamics 365 Customer Engagement (CE) Dynamics 365 Sales Dynamics 365 Customer Service Digital Transformation Microsoft Power Platform Power Apps Power Automate Power BI Dynamics 365 HR / HR Systems Hubdrive HR Business Process Automation