The Acquired Site Problem: Day One You Own Their Safety Record
An acquired facility arrives with its own programs, its own injury history and its own citation record. Integration usually addresses systems and payroll long before it addresses either.
Integration plans are thorough about payroll, ERP, email and branding. Safety usually appears as a line item called "align EHS policies", scheduled for somewhere in month four.
By month four you have owned the site's exposure for a hundred and twenty days.
What actually transfers
The building and the equipment transfer, and so does a set of things that are easy to overlook because they are not on any asset schedule.
The injury history. The site's recordable history exists and does not reset. Depending on the structure of the transaction and how the entity is treated, prior citation history may follow the operation in ways that matter for classification of future findings — which is a question for counsel on the specific deal, not a general rule, but it is a question worth asking before signing rather than after.
The programs, as written. The site has an energy control program, a hazard communication program, training records, an emergency action plan. They may be excellent. They are certainly different from yours.
The habits, as practised. More consequential than the documents. How this site actually decides whether something is recordable, when it stops work, whether the guard goes back on before the shift ends. These are invisible during diligence and dominant afterwards.
Any open obligations. Abatement commitments, ongoing settlement terms, outstanding items from a prior inspection. These do not pause for a change of ownership.
Integration frequently makes the site less compliant
This is the counterintuitive one, and it is common enough to plan around.
An acquired site in a state-plan jurisdiction operated under a program written to that state's requirements, which exceed federal in specific places. Integration folds it onto the corporate standard, which is written to federal. The state-specific provisions are removed, nobody logs the removal as a change, and the site is now doing less than it was under previous ownership.
The same thing happens with practices that looked like local eccentricity. A site required two-person verification on a particular isolation. Corporate has no such requirement, so the practice is dropped during alignment. It existed because of an incident in 2019 that nobody at the acquiring company has heard about.
Before you replace anything, find out why it is there. "This is not in our standard" is a reason to ask a question, not a reason to delete a control.
A sequence that works
Before close, establish the baseline. Citation history, recordable history, open obligations, the programs as written, and the jurisdictions involved. This is diligence, and safety diligence is routinely thinner than financial diligence by an order of magnitude.
In the first thirty days, do nothing structural. Learn how the site actually operates. Walk it with the people who run it. The instinct to impose the corporate standard immediately is strong and usually wrong, because you do not yet know what you would be removing.
Then apply the baseline additively. Bring the site up to your corporate standard where it is below, without stripping out anything it does that exceeds your standard. Where a local practice is stricter, keep it and record why. Where it is different but equivalent, decide deliberately rather than by default.
Reconcile jurisdiction last but explicitly. Confirm which state plan applies and what that adds. If your corporate standard has no jurisdiction overlay, this is the moment the gap becomes concrete rather than theoretical.
Record what changed and why. A dated integration record showing what the site did before, what it does now, and the reasoning is the artefact you want if a condition surfaces later at a site you recently altered.
The two-way audit
The best integrations treat the acquired site as a source of practice rather than only a recipient of it.
Sites that have been inspected recently, or that came through a serious incident, frequently run controls that are better than the acquirer's — because they were built in response to something real. A one-directional integration that pushes the corporate standard outward and takes nothing back will systematically discard those.
Ask, early: what do you do here that you would fight to keep? The answers are informative both about the site and about the gaps in your own standard.
The diligence question nobody asks
Financial diligence asks for the numbers. Safety diligence, where it happens at all, usually asks for the recordable rate and the citation list.
The more revealing question is procedural: show me how you decided that your last three recordable-looking incidents were or were not recordable. The answer tells you whether the low injury rate you are buying reflects a safe operation or a conservative recording practice — and the difference between those two shows up on your numbers, under your ownership, within a year.
General guidance only, not legal advice. Successor liability and citation history treatment are fact- and transaction-specific. Consult qualified counsel on any particular acquisition.
Not sure where you stand?
Take the 5-minute compliance assessment. Answer a few questions about your business and get a prioritized list of what OSHA expects, free.
Related Articles
Continue learning about OSHA compliance and workplace safety
Construction Safety
Excavation's Competent Person Is Designated at the Site. Corporate's Org Chart Assigns the Role by Title.
OSHA's excavation standard, 29 CFR 1926.651, requires a competent person who evaluates that specific site's soil daily. A title alone cannot substitute for it.
Fire Protection
Combustible Dust Isn't One Hazard. Across a Portfolio of Sites, It's a Different One at Each Address.
Combustible dust falls under OSHA's General Duty Clause and NFPA standards, not one rule — a portfolio policy must fit a different material at each site.
Health Hazards
Silica Table 1 Is Written Per Task, Per Tool. Your Compliance Program Is Written Per Company.
OSHA's respirable silica standard, 29 CFR 1926.1153, specifies controls by task and tool. Across many job sites, that specificity is exactly what a corporate policy tends to flatten.