Policy Integration After an Acquisition Closes: The First 100 Days
The deal has closed and a new group of employees is now yours. Here is what to settle on Day 1, how to decide policy by policy what happens next, and how to get every new employee onto the right documents.
In short
After an acquisition closes, decide with counsel which of your policies apply to acquired employees from Day 1, and tell everyone that the rest of their existing policies stay in force for now. Then sort each acquired policy into keep, adopt ours, merge or retire, roll the changes out in waves, collect a dated acknowledgment from each person, and hand over to your long-term subsidiary model.
This guide starts at closing. For what to check before the deal is signed, see policy compliance in M&A due diligence. For how to run policies across subsidiaries once integration is done, see building policy programs across acquired subsidiaries.
Day 1: decide what applies straight away
On the day the deal closes, acquired employees need a clear answer to one question: which rules am I working under today? Keep the Day 1 list short, and agree it with counsel before closing, not after.
Most organisations look at a handful of areas where a gap of even a few weeks would be hard to defend. Whether each one must change on Day 1, or whether the acquired company’s existing version is adequate for now, is a decision to make with counsel.
Code of conduct
Sets expectations for behaviour, conflicts of interest and how to raise concerns. Many acquirers want one code from Day 1 so there is a single standard to point to.
Harassment and reporting
Acquired staff need to know where to report a concern under the new ownership. If the reporting route has changed, that cannot wait for a later phase.
Workplace safety
Site safety procedures usually keep running unchanged, because they reflect the actual equipment and premises. Confirm who now owns them and who to call in an incident.
Data handling and access
Once systems start connecting, data moves between the two companies. Agree the rules for customer and employee data, and system access, before that happens.
Say “status quo” out loud. Everything not on the Day 1 list should be confirmed in writing as still in force. Silence leaves acquired managers guessing whether their old handbook still counts.
Map every policy to one of four outcomes
Put both policy libraries side by side and give each acquired policy one of four labels. Record who made the call and why, so the decision can be explained later.
Keep theirs
It works and it is local
Site procedures, role-specific rules or anything tied to their equipment, customers or jurisdiction. Change the owner and branding, not the substance.
Adopt ours
One standard is needed
Group-wide commitments such as conduct, anti-bribery or information security, where two versions would cause confusion or risk.
Merge
Both have something worth keeping
Take the stronger clauses from each. Sometimes the acquired company’s version is better; say so and use it as the base.
Retire
Replaced or no longer relevant
Withdraw it on a set date, tell the people who used it what replaces it, and keep a copy of the retired version for the record.
Check contracts and labour agreements first. Employment contracts, collective bargaining agreements or works council arrangements at the acquired company may limit what you can change, or how. Ask counsel to flag these before a policy is labelled “adopt ours” or “retire”.
Sequencing the first 100 days
A hundred days is a planning frame, not a rule. What matters is that changes arrive in planned waves rather than all at once.
- 1
Days 1–10: Day 1 policies and status quo
Issue the Day 1 policies, confirm in writing that everything else stays in force, and name an integration owner for policy questions.
- 2
Days 10–30: import and map
Bring the acquired company’s documents into one place, label each one keep, adopt, merge or retire, and get decisions signed off.
- 3
Days 30–70: roll out in waves
Release changes in small groups by topic, highest risk first. Give each wave an explanation, a deadline for acknowledgment and someone to answer questions.
- 4
Days 70–100: retire, check, close out
Withdraw superseded policies, chase outstanding acknowledgments, and review completion by location before calling integration done.
Communicating with acquired employees and getting sign-off
For each change, explain what is different, why, and what they need to do. A short summary of changes alongside the full document works better than a new handbook with no explanation.
Then record that each person has received and acknowledged the policies that now apply to them. Plan for three practical issues:
- Who is in the population. Get an accurate list of acquired employees by location from HR on Day 1, and keep it updated as people join and leave.
- How they will sign in. Frontline staff at the acquired company may not have a company email address. PolicyTrak’s documented sign-in is email-based, so settle how these employees will get access before the first rollout wave.
- Who chases. Give location managers visibility of their own team’s status, so follow-up does not all fall on the central compliance team.
This is where policy management software takes the manual work out of integration. In PolicyTrak:
Distribution and tracking
Assign policies to several locations at once, by location and jurisdiction. New employees are auto-assigned relevant policies by location, and the dashboard shows completion by policy, location or time period.
Document acknowledgment
Each person’s acknowledgment is recorded with a date, visible per employee and per location. Onboarding bundles group the policies a new hire needs and track progress.
Policy management
PDF import with AI extraction brings the acquired company’s documents in for review and editing. Every save creates a numbered version with the author’s name and date.
NoteAI-extracted content from imported PDFs still needs a person to review it. All documented PolicyTrak sign-in is email-based, so plan access for any staff without a company email address.
When to hand over to the long-term model
Integration should have an end. Once the Day 1 policies are in place, every acquired policy has been mapped and acted on, superseded documents are retired and acknowledgment completion is where you need it, stop running the work as a project. Hand ownership of each policy to its permanent owner and move the acquired business onto your normal review cycle.
From there the question changes from “what do we change?” to “what stays local and what stays common?”. That is covered in how to build policy programs across acquired subsidiaries.
Bring an Acquired Workforce onto the Right Policies
Assign by location, track dated acknowledgments and see completion across every site. Sign up and see plans without booking a call.
