[Shane Bullen]

To secure the sale, we made a commitment in the sale agreement that incoming employees would have “no less favourable conditions” post-transition. While this provided reassurance to staff, it has significantly complicated the integration of employment terms. Many legacy conditions have had to be preserved and ring-fenced, requiring extensive consultation with employees, essentially gaining agreement on every change.
Has anyone else encountered similar challenges with such commitments during an HR transition or business acquisition? If so, how did you manage these requirements at the deal stage to avoid committing to conditions that are difficult and costly to administer long-term? Are there alternative approaches or best practices for balancing employee assurance with operational flexibility?

[Jennifer Winter]

That’s a really good point and one I think a lot of buyers underestimate. On paper, “no less favourable conditions” sounds like a straightforward way to reassure employees, but in practice it often locks in a patchwork of terms that are very hard to streamline later.

One way I’ve seen this handled is by being more specific at the deal stage. Instead of a blanket promise, some acquirers define which elements are guaranteed (like base pay and core benefits) and which are subject to alignment post-transition. That way, the big concerns of employees are addressed, but it leaves some flexibility around smaller, legacy perks that may not be sustainable long-term.

Another tactic is to build in a transition period—say 12–18 months, where existing terms are honored, but it’s clearly communicated that “harmonization” will follow. That gives employees time to adjust and lets the acquirer plan changes with proper consultation.

Finally, some companies position the conversation less about “taking away” and more about “standardizing upward” wherever possible, so that employees see harmonization as an opportunity rather than a loss. Of course, that depends on how much room there is in the overall economics of the deal.

I’d be curious if others have found ways to strike this balance, because it feels like one of those issues where what looks simple in the agreement can become one of the biggest integration headaches!

[Author]

Posts