When one subsidiary's bad year tanks the parent company's EMR, you need risk transfer architecture—not more training reminders.
Your roofing division had a bad fall in March. Your electrical contracting arm ran clean all year. But when renewal came, both entities saw their workers' comp premiums jump 18% because the underwriter pooled the risk and calculated a consolidated EMR that penalized everyone.
This is the multi-entity EMR problem nobody warns you about until you're already paying for it. Most growing contractors assume each subsidiary gets its own experience rating. They don't. Not automatically. And by the time you realize the consolidated calculation is bleeding you, you've already lost two bid opportunities because your composite EMR disqualified you before the proposal ever landed on a desk.
The National Council on Compensation Insurance (NCCI) uses ownership and operational control as the primary criteria for combining entities under a single EMR. If you own multiple companies—even if they operate in completely different industries, with separate management, separate payroll systems, and separate safety programs—the default assumption is consolidation.
Here's what triggers it: common ownership above 50%, intercompany transactions that suggest operational overlap, shared administrative staff, or consolidated financial reporting. The moment an auditor sees any of these, they treat your entities as a single insured for experience rating purposes. One entity's DART rate becomes everyone's problem.
The math is brutal. Let's say you run three entities:
If rated separately, Entity B stays competitive with a 0.78. But consolidated? The composite EMR comes in at 1.14, and now Entity B is getting rejected from bids they would have won on their own merit. Entity C's failure became Entity B's disqualification.
Most companies stumble into consolidated EMR. The ones who avoid it build separation intentionally, with three specific structural barriers:
1. Corporate structure isolation. Separate LLCs or S-corps with distinct ownership percentages. If Entity A is owned 60% by Person 1 and Entity B is owned 60% by Person 2, you've created enough separation to argue for independent rating—assuming you can also prove operational independence.
2. Administrative firewall. Separate payroll processors, separate bank accounts, separate HR systems, separate office locations if possible. Shared services are the fastest way to lose your separation argument. The moment an auditor sees that your "independent" entities share a single safety director or use the same accountant for workers' comp filings, consolidation is back on the table.
3. Financial and operational separation. No intercompany loans. No shared equipment leases. No project work where Entity A provides labor and Entity B provides supervision. Every transaction between entities has to be conducted at arm's length, documented like you're dealing with an outside vendor, or it becomes evidence of operational control.
This isn't about hiding anything. It's about designing your corporate structure so that the entity with high-hazard work and the inevitable bad year doesn't contaminate the EMR of the entity that runs clean. If you don't design it this way from the beginning, unwinding it later requires restructuring that costs more than the premium increase you're trying to avoid.
I watched a mechanical contractor try to separate two entities after five years of consolidated rating. They had the corporate structure right—separate LLCs, different ownership splits. But they shared a single workers' comp policy, a single safety manual, and the same project manager moved between both entities depending on workload.
When they requested separate EMR calculations, the NCCI auditor denied it in under a week. The intercompany overlap was so obvious that separation was never going to survive scrutiny. The fallback plan—switching to a PEO to isolate the high-risk entity's experience rating—worked, but it took 18 months and cost them two renewals at the inflated composite rate before the new structure took effect.
The lesson: you can't retrofit separation. You either build it into the structure from day one, or you accept that one bad entity drags everyone else down for the next three years.
Here's the part that kills most multi-entity EMR strategies: recordkeeping errors that span entities. If you're running separate companies but logging incidents inconsistently—one entity classifies a back strain as first aid, another logs the same injury as recordable—you're creating discrepancies that auditors will flag during the next experience rating review.
Worse, if you're consolidated and trying to argue for separation, inconsistent OSHA logs are evidence that you're not actually running independent operations. The auditor sees it as proof that your "separate" entities are really just divisions of the same company pretending to be independent.
The fix: if you're serious about entity separation, your OSHA 300 logs, injury classification standards, and return-to-work protocols have to be identical across entities—not because you're coordinating them, but because you're all following the same OSHA recordkeeping standard correctly. That's the difference between separate entities that happen to follow the same regulatory framework and a single company pretending to be three.
Yes, but it requires proving to the NCCI or your state rating bureau that the entities operate independently—separate management, separate administrative systems, and no shared operational control. If you've been consolidated for years, you'll need at least 12 months of documented separation before most rating bureaus will consider the split. Retroactive separation almost never happens.
Partially. A PEO (Professional Employer Organization) becomes the employer of record for workers' comp purposes, which means the employees under the PEO are rated under the PEO's EMR, not yours. This can isolate a high-risk entity's experience rating—but only if the PEO agreement is structured correctly and the entity genuinely operates under PEO payroll and HR systems. If you're still controlling day-to-day safety and operations, auditors may still consolidate the experience rating.
Three years. The EMR calculation uses a three-year lookback period (excluding the most recent year, which is still developing). A serious incident that happens today will affect your EMR for the next three rating periods. This is why a single fall from height in year one can disqualify you from bids in years two, three, and four—even if you ran zero recordables in the interim.
No. If the closed entity was consolidated with other active entities, the experience rating history remains part of the consolidated calculation until it ages out of the three-year lookback. Closing the entity doesn't erase the claims history—it just stops new claims from being added to that entity's record.
Building multi-entity EMR separation requires flawless recordkeeping across every entity: OSHA 300 logs that match the regulatory standard, workers' comp claims documentation that ties to the correct entity, and injury classification decisions that are defensible in an audit. Most safety managers don't have time to maintain that level of rigor across three separate entities while also doing actual safety work.
If the administrative burden of multi-entity compliance is eating the time you should be spending reducing the risk that drives the EMR in the first place, we handle it. OSHA logs, claims documentation, entity-level reporting, ISNetworld updates across multiple entities—completely off your plate.
Talk to EHS if the admin work is the thing stopping you from building the separation architecture you actually need.
Aaron West
Founder, EHS, Inc. — 18+ years in EHS compliance and contractor safety
Aaron West has spent over 18 years helping contractors and businesses navigate OSHA compliance, ISNetworld® certification, and workplace safety management. He founded EHS, Inc. to make enterprise-level EHS accessible to companies of all sizes — serving contractors and businesses nationwide — without long-term contracts or enterprise overhead.
Our team handles the complexity so you can focus on running your business. No long-term contracts, no learning curve.
Talk to EHSOne misclassified medical-only claim as lost time can inflate your EMR for three years and cost you tens of thousands in premiums.
One incident in 2023 is still killing your bids in 2026. Here's what the EMR lookback actually costs you and what you can do about it.
When near-miss reports drop after an incident, HOP principle #5 explains exactly why—and how your response killed future reporting.
Framework to achieve zero incidents
Stop hitting paywalls
54 topics in English & Spanish