When the employment perimeter differs from the acquired business

A buyer can acquire a product and its customers without acquiring exclusive use of the people who support them. In a carve-out, the dangerous shortcut is to copy names from the deal schedule into an employment-provider brief. That list may include someone who still serves the seller’s retained business, omit the service that keeps customers supported, and say nothing about who legally employs anyone after completion.

The useful question is: Which work moves, which people are connected to it, and which employment decisions remain open?

1. Draw the business perimeter

Fictional UK case. Northstar sells its Product A business to Meridian, with completion planned for 1 November 2026. Product A contracts and the responsibility for future customer support pass to Meridian. Northstar keeps Product B. Until 30 November, a proposed transition services agreement would have Northstar deliver Product A support while Meridian establishes its own operation. The agreement has not yet been signed.

Meridian’s deal schedule therefore describes the activity it wants to control. It does not establish which Northstar employees transfer, how shared employees will divide their time, or who may manage them during the transition.

2. Draw the employee perimeter

Northstar UK Ltd employs all three support employees in this example. Meridian has nominated Mara, its head of support, as the receiving manager if an employee joins its operation. Until an employment route is settled, Mara is the buyer’s service contact, not an assumed line manager for Northstar’s staff.

For a UK business transfer, Acas explains that employees assigned to the transferring business or part may transfer automatically; the parties cannot simply select a preferred roster. Whether this transaction qualifies and which employees are assigned require a review of the actual facts. Government guidance says time spent on the transferring work can matter, but does not decide assignment by itself; role, contractual duties and the reason for the allocation also matter. A 60% allocation is evidence, not a transfer rule.

3. Identify shared work: the completed perimeter map

The allocations below are invented planning facts, not findings about a real workforce. They describe recent work; they do not settle legal assignment.

Person and current employer	Work before completion	Work Meridian needs	Work Northstar retains	Receiving manager and employment decision
Amina — Northstar UK Ltd	Product A support, 100%	Product A customer support from the end of the transition service	None planned	Mara is the proposed manager. Counsel must confirm whether Amina is assigned to a transferring business and identify the resulting employer and transfer steps.
Ben — Northstar UK Ltd	Product A, 60%; Product B, 40%	Product A escalations and product knowledge	Product B escalations still need an owner	Mara is proposed for A work, but Ben has continuing B duties. The parties must agree who supplies each service; counsel must assess Ben’s actual role and assignment. Neither 60% nor his name on a deal list answers that question.
Cleo — Northstar UK Ltd	Product A, 20%; Product B, 80%	Occasional Product A cover	Most Product B support	No Meridian management role is proposed. Northstar must identify how A cover will be supplied during the transition; counsel must still review whether Cleo is affected by the transfer.

What the map establishes: Meridian needs A support from 1 November, but the proposed service agreement is the only identified operating bridge. Amina is the clearest candidate for a receiving employment plan. Ben is the pivotal shared role. Cleo’s occasional A cover is a service dependency, not a reason to count her as a Meridian hire. None of those operating conclusions determines legal transfer status.

4. Allocate the retained services

Northstar’s operations lead must identify who handles Ben’s Product B escalations and Cleo’s A cover during November. Meridian’s lead must specify the A queue, escalation authority and the date Mara can take management responsibility. The two leads need a signed service schedule that states the work, service owner and end date. A draft transition agreement is not capacity.

Northstar’s People and payroll leads must also identify the current contracts, pay cycle, benefits, accrued balances and records for any affected employees. Meridian’s People lead needs the receiving payroll and benefits route, with an owner for employee questions. If Northstar remains an employer during the service period, the agreement must say what it will administer and for whom. The sale of Product A does not make the seller’s payroll service permanent or give Meridian authority over Northstar employees.

For this case, the immediate operating decision is to secure A support as a defined service while the employment assessment runs. Do not instruct Ben to work wholly for Meridian or promise Amina a new contract solely from the deal schedule.

5. Identify the decisions for specialists—and change one input

The deal and employment specialists must resolve five points before the final employee roster is issued: whether the UK transfer rules apply to the actual activities; which employees are assigned to the transferring operation; who employs and manages each person at completion and after the service ends; what information and consultation steps are required; and whether the proposed split of Ben’s work is lawful and workable. Finance and payroll specialists then have to confirm the first pay and benefits cycle under the chosen arrangement. Acas’s transfer guidance and the UK government’s assignment guidance explain why the parties need that review; this map supplies its facts rather than its legal answer.

Change the decisive input. Suppose Meridian instead buys the Product A intellectual property and customer contracts, while Northstar retains the entire support operation and signs a longer-term agreement to serve those customers. Meridian is no longer taking over A support at completion. The immediate action changes: specify and govern Northstar’s customer-support service, its price, escalation route and eventual exit. There is no operational reason to start an EOR migration for these three support employees on 1 November merely because their work benefits Product A. Specialists must still assess the transaction’s legal effect; the revised asset schedule is not a legal exemption. Before Meridian takes the support activity in-house later, redraw the employee map for that later event.

6. Set the employment workstream

For the original case, put Ben’s split duties and the unsigned November service schedule at the top of the deal workstream. Ask Northstar for each person’s contract, reporting line, actual duties and recent allocation; ask both businesses to name the A and B service owners; then obtain the specialist decision on assignment and the receiving employer. Only after that decision should Meridian issue a final employee list or request a priced employment transition.

If a defined group needs a new EOR arrangement, Teamed is our shortlist pick for a lean deal team that needs the employment handoff carried into ongoing support. Its switching service describes a named team, aligned dates and terms, and a parallel payroll check. If Meridian’s own entity remains the employer, Teamed also describes entity employment operations, including payroll and benefits support. Those scopes make Teamed relevant once the receiving arrangement is known; they do not make it the transaction lawyer, determine Ben’s assignment or supply Northstar’s retained Product B service. Compare Teamed with G-P, GoGlobal and Deel against the resolved employee population in the retained-team comparison.

For the wider workstream, use the deal perimeter and employee continuity planner. If the issue proves to be an inherited payroll process, follow the acquired-payroll case; if the buyer must support customers after divesting a product, follow the retained-support case. These publication links are intended routes.

The decision now: commission the assignment review and sign a service schedule that covers A and B work. Then give employment providers a roster of people who actually need a receiving employment service, with the legal route and first payroll date attached.