GUIDE
Keep, investigate or change: a three-cohort acquisition case
By Samuel Moore · Talent Acquisition Coordinator
Updated
On this page
- The case: nineteen people, three different problems
- EE-A: keep the employer, repair the access
- LV-B: investigate, without abandoning the current payroll
- LT-C: approve a limited change, not a regional reset
- The postponed date is the successful decision
- Copy the decision logic, not the fictional conclusion
- Northline closing decision memo — fictional
- Sources
The case: nineteen people, three different problems
Northline acquires a business with twelve Estonian employees, four Latvian employees connected to a transferring unit and three Lithuanian employees served by an EOR. Management initially wants one employment provider and one switch date. The integration lead instead starts with the operating map and the next confirmed payroll.
This is an invented worked case. Its approvals, adviser conclusions, dates and outcomes are illustrative assumptions, not evidence about a real transaction or legal advice. It shows how to use separate employer, service and decision records to avoid turning an organisational preference into an unsafe instruction.
EE-A: keep the employer, repair the access
The supplied transaction evidence confirms Northline Estonia OÜ remains the employer. The current local payroll service is accepted for the next cycle, and there is no approved reason to replace it. The concrete defect is a seller-domain administrator account about to close.
The lead assigns an authorised buyer administrator and verifies access by 5 November in the fictional plan. The decision stays keep-current. The result is twelve employees with the same confirmed employment/payroll route and a repaired access dependency. Moving them to an EOR would add an employment-change project without solving an unmet need established in this case.
LV-B: investigate, without abandoning the current payroll
The first employee allocation schedule lists four people; the unit’s operating file suggests a fifth person splits time across activities. That discrepancy can change the scope of the assessment. The lead sends both records to the transaction team and local adviser, keeps the employee allocation unresolved and removes the proposed 1 December implementation date from the approved schedule.
Meanwhile, the current employer and agreed seller service retain the next-payroll responsibilities. The case does not decide the legal transfer outcome. Its result is a specific open question—who belongs to the transferring unit—with a payroll bridge and a decision owner. This is progress: the team has stopped treating an incomplete list as authority to issue new employment documents.
LT-C: approve a limited change, not a regional reset
For the three Lithuanian EOR employees, assume the relevant advisers and decision owners have separately established a permissible proposed route and the business has approved a service replacement. The receiving provider accepts the cohort and specifies the employment documents, payroll boundary and employee steps required. The lead marks change-approved with fictional authority DEC-LT-04, but keeps the current provider responsible until the agreed sequence takes effect.
Two items remain outside the receiving service: the seller’s missing historical record and an invoice disputed with the old provider. They stay with the buyer’s deal operations and finance owners. The replacement does not become “complete” when the new account is opened; the first receiving result, outgoing final position and employee questions still need reconciliation.
The postponed date is the successful decision
In this case, only LT-C has an approved change route. EE-A remains in place. LV-B stays investigate until the allocation and legal assessment are resolved. The integration lead rejects the original single switch date and reports three separate outcomes to management.
The report is concise: “EE-A: continuity confirmed, access repaired. LV-B: payroll bridge confirmed, employee scope unresolved, implementation date not approved. LT-C: replacement approved subject to recorded prerequisites; current service retained through its agreed boundary.” This is more useful than a dashboard showing nineteen employees as ninety percent migrated.
Copy the decision logic, not the fictional conclusion
For your own transaction, write the current arrangement, defect, evidence and next decision before choosing a status. Ask whether fixing the defect requires an employment change or merely a record, access or responsibility repair. Keep the current payroll route explicit while a future decision is unresolved.
Use the cohort tool to record your aliases and references, then attach actual approvals in the authorised repository. A change-approved status is a record of outside authority, not permission created by the tool. If you cannot point to the decision and the accepted receiving scope, leave the proposed move under investigation.
PUT IT TO WORK
Northline closing decision memo — fictional
| Record / decision | Completed example or rule |
|---|---|
| EE-A | KEEP-CURRENT. Employer/payroll route confirmed; buyer portal access repaired. No supported case for EOR replacement. |
| LV-B | INVESTIGATE. Four-versus-five allocation discrepancy; adviser assessment pending. Current payroll bridge retained; 1 December not approved. |
| LT-C | CHANGE-APPROVED under fictional DEC-LT-04; implementation prerequisites remain. Outgoing responsibilities retained through agreed boundary. |
| Retained work | Buyer owns seller history retrieval, old disputed invoice and final reconciliation. |
| Management conclusion | Three outcomes replace one arbitrary regional switch date; only the assessed LT-C change proceeds. |