Responding is Mary Foley, expert services strategy director, Enhesa, Shrewsburry, England.
Mergers, divestments and reorganizations make headlines for the deal value. They rarely make headlines for what happens to the safety system underneath. Yet, in 30 years of working across deal-intensive sectors, I’ve watched the same pattern repeat: a transaction closes, the org chart is redrawn, and the health and safety program that quietly managed thousands of workers the day before is now operating across two – possibly more – legacy systems, alongside several reporting lines and a safety leadership team that might not have met.
The real question isn’t whether safety survives a restructuring; it’s where the cracks appear first – and whether anyone is looking.
In my experience, risk can surface in three distinct phases. The first is during due diligence. Safety can sometimes be treated as a three-ring binder of policies rather than a live operating system. Deal teams may check that a certified safety and health management system exists. At this stage, they rarely check whether the program actually works at the site level, whether incident reporting is robust, or whether obvious gaps exist between the safety culture at the acquired entity and the acquiring organization.
The second phase is Day 1 integration. New reporting lines land before new processes have been codified. Site leaders can inherit policies they didn’t write and standards on which they’ve never been trained. Safety leadership can become confusing precisely when clarity is most needed.
The third phase can happen later. Two, three, sometimes five years after a deal closes, sites are still running on sometimes competing or cannibalized legacy systems. Different definitions of a recordable incident sit alongside each other. Different audit cadences. Different contractor management standards. Boards can assume integration is complete because the financial reporting has been consolidated. The safety system can sometimes tell a different story.
What separates the organizations that emerge stronger from those that spend the next five years reconciling inconsistencies is rarely budget; it’s foresight, evaluation, improvements and sequencing. More-prepared organizations treat safety integration as a parallel workstream to financial integration, not a downstream consequence of it. They standardize the things that should never vary – hazard classification, incident reporting thresholds, contractor competence requirements, leadership accountability – before they worry about harmonizing the things that can flex by site. They sweat the details early.
They also do something simpler. They put a senior safety and health leader at the integration tabletop on Day 1, with the authority to slow down processes when something isn’t ready to scale.
If I had to define “good” in one sentence for a safety and health leader walking into a post-deal integration, it would be this: Every site, regardless of which legacy company it came from, can answer the same three questions in the same way by the same date:
- What are our top risks?
- Who owns them?
- And how do we know our controls are working?
The organizations that manage restructuring well are the ones that stay grounded in three fundamentals:
- Understanding the organization’s strategic objectives
- Maintaining visibility over regulatory obligations across every site and business
- Keeping focus on material risks throughout the integration process and afterward
Because when reporting lines change overnight, unmanaged risk doesn’t wait for the integration roadmap to catch up.
In the end, the organizations that navigate change safely are the ones whose leaders treat safety integration as an operational priority from Day 1.
Editor’s note: This article represents the independent views of the author and should not be considered a National Safety Council endorsement.
