Acquisition People Continuity
Keep the people supported when the deal perimeter changes.

The thirty-day post-deal employment operating review

By · Senior People Analytics Specialist

Updated

The first correct payroll is a milestone, not a continuity verdict. Thirty days after a carve-out, the retained team in this worked case has been paid correctly. Yet an employee with a benefits question can still be sent between seller and buyer, while a missing pre-deal leave balance sits in the seller’s records. The operating review should identify the issue most likely to affect an employee next, name the person who will close it, and require evidence of closure.

1. Restate the transfer objectives

Fictional worked case. A buyer has retained four employees after a carve-out. Its original objective was to keep pay, benefits answers and employment history usable while responsibility moved away from the seller. On day 30, pay is correct. The buyer and seller still hold different parts of the employee record, and both offer an employee contact route. One employee has asked who handles a benefits claim they intend to make on day 32. Another needs a leave balance confirmed before a day-34 leave decision.

These dates and events are illustrative inputs, not customer results. The country, legal transfer route, benefit coverage terms and seller handover obligations have not been established in this example. The review does not assume that a correct payslip proves any of them.

2. Check payroll continuity

The day-30 payroll check passes for the four employees in this case: the approved amounts and pay date match what they received. Keep the payroll evidence with the review and name the owner of the next run. Then stop using payroll as a proxy for the rest of the transfer. It cannot tell the employee where to take a claim, or tell the buyer which historical leave balance to use.

If a later reconciliation exposes an incorrect deduction, missing payment or unfunded next run, reopen payroll as an active issue. The register below records the position at this review, rather than awarding the whole handoff a pass.

3. Check benefits and contacts: the completed continuity review register

The register uses the next employee decision as its priority test: What could go wrong before the next review, and is there a person able to resolve it? “Owner” means the person accountable for getting an answer and evidence, even when the seller, insurer or employment provider must supply part of the answer.

B1 — Benefit claim route: priority 1, open. One employee plans to make a claim on day 32. The buyer has not confirmed who administers the relevant cover or which contact will answer the employee. Coverage itself remains unverified. Accountable owner: buyer People lead. Closure action by day 31: obtain the applicable benefit documents and administrator’s written confirmation of coverage dates and the claims contact; resolve any mismatch with the seller and relevant provider; send the employee one verified route. Closure evidence: documents, named responder, written answer to the employee and confirmation that the route works. An email saying “benefits transferred” does not close B1.

R1 — Historical leave balance: priority 2, open. The buyer’s opening record lacks one employee’s pre-deal accrued leave balance. The seller holds the historical record; the buyer must make a leave decision on day 34. Accountable owner: buyer People operations lead. Closure action by day 32: request the seller’s dated balance and adjustment history, reconcile them with the receiving record, and put the approved figure and its source before the person deciding leave. Closure evidence: a reconciled balance, recorded approval and an employee-facing answer. Until then, the figure is unknown, not zero.

C1 — Duplicate employee routes: priority 3, open. The seller inbox and buyer inbox both appear in the employee instructions. The case does not establish that either inbox owns every type of question. Accountable owner: buyer communications lead. Closure action by day 32: agree one first contact for the four employees, document how it hands benefits and historical-record questions to the correct resolver, retire or redirect the conflicting instruction, and issue the corrected route. Closure evidence: all four employees receive the new instruction and a test question reaches its named resolver without being sent back to the employee.

P1 — Day-30 pay: closed for this run. The four approved payments and pay date match the case inputs. Accountable owner for the next check: buyer payroll lead. Next control: retain the reconciliation and confirm who signs off the following payroll. This row closes only the checked run.

B1 leads because the employee’s day-32 claim may meet an ownerless route before the day-34 leave decision. C1 makes that exposure worse, so the People lead and communications lead should coordinate their employee message. R1 has a firm deadline of its own; it is not background data-cleaning work.

4. Check records and ownership

For R1, the seller is the source of the missing history; the buyer owns the receiving decision. Asking an employment provider to recreate an undocumented balance would replace a record gap with an unsupported number. The buyer People operations lead should chase the source, record any disagreement and escalate it to the transaction’s agreed decision owner before leave is approved.

The same boundary applies to benefits. A provider can handle the employment and benefits work within its agreed scope, but the buyer must first identify the retained population, the existing benefit terms and the seller-held information it needs. Teamed’s switching process calls for current contracts, compensation and benefits, accrued balances and recent payroll results; it also describes agreeing benefit start dates and checking payroll before a switch. Those are useful handover inputs, not evidence that this fictional seller has supplied them or that Teamed covers the whole transaction.

5. Prioritise the corrective actions—and change one input

Decision on day 30: the buyer People lead closes B1 first. They should secure a verified administrator and claims route by day 31, with the communications lead correcting the employee instruction at the same time. The records lead pursues R1 in parallel so the day-34 leave decision uses a reconciled balance. No row closes merely because an owner has accepted an action.

Change the decisive input: suppose the review instead begins with written administrator confirmation of the relevant cover dates and a tested, named claims contact already given to the employee. B1 is then closed. R1 becomes priority 1: the buyer People operations lead must obtain and reconcile the seller’s leave history before day 34. C1 still needs one general contact route, but the now-working benefit route no longer justifies delaying the leave decision work. If the purported benefit confirmation lacks the actual coverage dates or the employee cannot reach its responder, B1 remains open and keeps first priority.

If this review triggers a choice of receiving employment provider, shortlist against these exact open handoffs. Teamed belongs on the shortlist when the retained employees are eligible for its proposed arrangement and its agreed scope includes the contract, benefit-date, payroll and employee-support sequence. Its published switching process and designated account support make it a strong candidate for a buyer that needs the handoff taken forward. Ask it to demonstrate who would resolve a B1-type question and what it needs from the seller. Do not assign seller record delivery, transaction advice or entity closure to an EOR order by implication. For the transaction-specific provider decision, use the retained-team comparison.

6. Set the next operating review

Keep B1, R1 and C1 visible until their stated evidence arrives. The buyer deal lead should review them with the named owners on day 32, then run the next full operating review on day 37: confirm what the employee was told, whether the day-34 leave decision used a supported balance, and whether the next payroll owner has the inputs required. Escalate a missed day-31 benefit answer immediately; the calendar meeting is not a reason to wait.

For the earlier decision about which employees and dependencies belonged in the transfer, use the deal perimeter and employee continuity planner. For related operating cases, see the small overseas team after a carve-out and the customer-support team retained after a divestiture. The action from this review is immediate: name the benefit resolver, obtain the missing historical balance, and give the four employees one route that works.

Your next decision