HR Questions to Ask During an Acquisition
For HR teams and employees working through an acquisition. The questions cover what usually goes unanswered longest: the integration timeline, whether roles are being cut, how benefits and accrued time off carry over, what happens to 401(k) accounts, and how two cultures get reconciled.
The questions
Open any question for the note
What is the timeline for integration, and what phases will employees experience?
Why ask it
Vague timelines are normal this early. What matters is whether they can name the next decision point: 'we will know more in Q3' is a real answer, 'soon' is not.
Will there be any layoffs or reductions in force?
Why ask it
Nobody expects a guarantee. A careful 'the org design is not finished, and you will hear before the market does' is more trustworthy than a flat no.
How will benefits and pay be affected, and from what date?
Why ask it
Benefit changes usually land on a plan-year boundary, so the effective date matters as much as the change. Ask for the date, not the direction of travel.
What happens to accrued PTO, sick leave and other balances?
Why ask it
Balances either transfer, get paid out, or reset into a new policy with a cap. Which of the three applies depends on state law and deal structure, so the answer has to be state by state.
Will the acquiring company recognise existing seniority and hire dates?
Why ask it
Hire date drives vacation accrual, vesting and severance formulas. If everyone starts fresh, long-tenured staff have taken a pay cut nobody announced.
How would you describe the differences between the two cultures?
Why ask it
'We are very similar' usually means nobody has looked. Useful answers name something concrete, like decision speed, or how much gets done in writing versus in meetings.
What happens to our policies and employee handbook?
Why ask it
Handbook harmonisation is where remote work rules, expense limits and leave policies quietly change. Ask which document governs on day one.
How will performance reviews, raises and promotions be handled this cycle?
Why ask it
Cycles often freeze during integration. If nobody will commit, ask whether a freeze delays merit pay or cancels it, because those are very different outcomes.
Will anyone need to reapply or interview for the role they already hold?
Why ask it
Reapplication is common wherever two teams overlap. Knowing early is the difference between preparing a case and being caught out.
How will 401(k) accounts and other retirement plans be handled?
Why ask it
Plans get merged, frozen or terminated, and each option has different consequences for vesting and for outstanding loans. Anyone with a 401(k) loan needs this answer first.
What support will displaced employees receive?
Why ask it
Ask for the components: weeks of pay per year of service, benefits continuation, outplacement, treatment of unvested equity. 'Generous' means nothing without those numbers.
How will reporting lines and management change?
Why ask it
Not knowing who you report to is the most common reason good people start looking. If the structure is undecided, ask for the date it will be announced.
What forum will employees have to ask questions and get answers on the record?
Why ask it
Anonymous questions with published answers slow rumours better than town halls, because people will submit the thing they would never say into a microphone.
How often will employees hear from you during the transition, and through which channel?
Why ask it
A commitment to a cadence, even a weekly note that reports no change, holds up better than a general promise of transparency.
What happens to existing employment agreements, non-competes and retention letters?
Why ask it
Some agreements assign to the buyer automatically and some do not, depending on whether this is a stock or an asset purchase. Anyone holding a signed side letter should ask directly.
How will you handle pay differences between the two workforces doing the same job?
Why ask it
Levelling usually raises the lower band over time rather than cutting the higher one. Ask about the timeline, because that is where the disappointment sits.
What training and support comes with the new systems?
Why ask it
Systems migration is the part of integration employees feel every day. If no one owns training, the work lands informally on whoever figures it out first.
Who do employees contact for HR questions during the transition, and how quickly should they expect a reply?
Why ask it
Integration makes HR queues long. A named contact and a stated response window stop people concluding that nobody is listening.
Will remote and hybrid work policies change?
Why ask it
This decides things for anyone who moved house under the current policy. Ask whether existing arrangements are grandfathered or renegotiated case by case.
What did your previous acquisitions look like a year afterwards?
Why ask it
Past behaviour is the best evidence available. Ask specifically about retention of the acquired company's managers, which is a number most acquirers can actually cite.
Working an Acquisition From the HR Seat
Practical guidance for the conversation itself
Groundwork before you brief anyone
- Confirm the deal structure first. A stock purchase generally carries employment relationships and plans across; an asset purchase often means terminations and rehires, with different notice and payout duties.
- Check whether WARN Act notice or a state equivalent is triggered before any headcount discussion becomes public. Thresholds are counted per site and over a rolling period.
- Lay both benefit plan years side by side. Most avoidable anger comes from a change that lands halfway through someone's deductible.
- Get written answers on accrued PTO for every state you employ in. Payout rules differ, so one national message will be wrong somewhere.
- Agree with the buyer who answers which question, and publish that split. Employees escalate as soon as two sources contradict each other.
What to say when you cannot answer yet
Name the category, not just the refusal
'Org design is not finished' is credible. 'No comment' tells people the answer is bad and they should ask elsewhere.
Give a date and keep it
Say when you expect to know. If it slips, say so on that date rather than going quiet, which is the point at which the rumour becomes the official version.
Never guarantee no layoffs unless it is contractual
One retracted guarantee devalues every other message you send for the rest of the integration, including the true ones.
Publish the open questions
Keep a visible list of what you have been asked and cannot yet answer. Being on the list is most of what people wanted.
For employees: what to get in writing
- Your hire date as the new employer will record it, since it drives accrual, vesting and any severance formula.
- The effective date of each benefits change, plus the actual plan documents rather than a summary slide.
- The status of unvested equity, options and any retention bonus, including what happens if you are let go before the vest date.
- Any promise made verbally about role, level, location or reporting line. Restate it in an email to the person who made it.
- Your current PTO balance, captured before the systems change over.
- Who signs off your existing flexible or remote arrangement in the new structure.
What goes wrong most often
Going quiet between announcements
The gap fills with rumour, and rumour is always worse than the facts. A short note saying nothing changed this week is worth sending.
Treating retention as a bonus problem
Money holds people for the length of the payment. What keeps them is knowing who they report to and what their job now is.
Letting managers hear the news alongside their teams
A manager surprised in a town hall cannot support anyone. Brief them a day ahead with answers to the obvious follow-ups.
Assuming culture will settle itself
Pick the few practices that will visibly differ, decide which one wins, and say so. Silence defaults to whatever the acquirer already does.