Electronic Injury Reporting Is Per Establishment, Not Per Company — And That's Where Multi-Site Operators Get Caught

The most common recordkeeping failure at large operators is not a badly kept log. It is a site nobody realised was in scope.

Electronic injury reporting under 29 CFR 1904.41 is written around the establishment, not the company. That single word is why a business with fifteen thousand employees can submit exactly what it believes it owes, on time, through the right portal, and still be short several sites. The corporate number is irrelevant to the obligation. What matters is the headcount and the industry classification at each physical location, evaluated separately.

The rule counts locations, not payroll

An establishment, in OSHA's language, is a single physical location where business is conducted. A company running forty distribution centres has forty establishments. Whether each one must submit — and what it must submit — depends on that location's own peak employee count during the previous calendar year and its own industry classification.

There are three separate triggers, and they do not stack neatly:

Establishments with 100 or more employees in the higher-hazard industries listed in Appendix B to Subpart E must submit their Form 300 log and Form 301 incident reports, in addition to the 300A summary. This is the newest of the three and the one most often missed, because it asks for case-level detail rather than an annual total.
Establishments with 20 to 249 employees in the industries listed in Appendix A must submit the Form 300A summary.
Establishments with 250 or more employees in industries that are required to keep OSHA records at all must submit the Form 300A summary.

The deadline is March 2 for the prior calendar year. Verify the current appendices against the standard itself before you rely on any summary of them, including this one — the industry lists have been revised more than once and are the part most likely to have moved.

Why the miss happens

Nobody sets out to skip a site. The pattern is almost always structural.

Headcount is measured at the wrong level. Corporate HR reports company-wide or business-unit headcount. The rule wants peak employment at each location during the year, which is a number many organisations do not routinely produce. A distribution centre that runs 80 employees most of the year and 140 through a seasonal peak crosses a threshold that the annual average never shows.

Classification is inherited, not checked. A location acquired three years ago carries whatever NAICS code was on the paperwork at the time. If the work changed — a warehouse that took on light assembly, a service depot that started doing fabrication — the classification may no longer describe what happens there. The obligation follows the actual work.

Sites are grouped for convenience. Several small locations in one metro area get treated as one operation for management reporting, then get treated the same way for recordkeeping. They are separate establishments if they are separate physical locations.

Nobody owns the boundary. Corporate assumes each site handles its own submission. Each site assumes corporate submits centrally. This is the failure mode that produces a clean-looking process and no filing at all, and it is far more common than either party expects.

What good looks like at scale

The organisations that get this right treat it as an annual reconciliation rather than a filing task.

Start from a definitive list of physical locations — not the org chart, not the cost-centre list, both of which will disagree with reality. Property or facilities records are usually closer to the truth than either. Every location where people work is a candidate establishment, including ones that were opened, closed, or acquired part way through the year. A site that operated for four months still has a recordkeeping history for those four months.

For each location, capture peak employment during the calendar year and the industry classification that actually describes the work performed there. Both numbers belong to the site, and both need to come from someone who can see the site, not from a corporate roll-up.

Then determine the obligation per location and record the determination — including the locations you concluded were not in scope, and why. That second list is the one that matters when an inspector asks how you decided. "We submitted for every site that needed it" is an assertion. A dated list showing each location, its headcount, its classification, and the conclusion drawn is evidence.

The detail requirement changes the calculus

For establishments that fall under the 100-employee trigger, submitting case-level data from the 300 and 301 is a different exercise from submitting a summary. The 300A is four numbers and a signature. Case-level submission exposes how consistently your sites classify injuries.

If one plant records a recordable case as restricted duty and another plant records a materially identical case as lost time, that inconsistency has always existed — it was simply invisible while each site kept its own log. Submitting the underlying cases makes the variation legible to a regulator who is looking at your whole portfolio at once.

This is worth confronting before March rather than after. The remedy is not to reclassify anything retrospectively to look consistent, which creates a considerably worse problem. It is to make sure the people making classification decisions across your sites are working from the same definitions, and to be able to explain any variation that remains.

Personally identifiable information

Case-level submission includes fields that OSHA does not publish, and the agency applies its own handling to what it releases. That does not remove your obligation to keep the underlying records appropriately — the 301 contains information about individual employees, and internal access to it should be scoped accordingly. Several organisations have discovered during preparation that their incident records were readable by a wider internal audience than anyone intended.

Where to start this quarter

If you do nothing else before the next cycle, produce the location list and get peak headcount against each line. Most multi-site operators cannot generate that quickly today, and everything else in this article depends on it.

The organisations that struggle in March are rarely the ones with bad safety programs. They are the ones that could not answer, in the first week of February, how many establishments they actually operate.

General guidance only, not legal advice. Verify current requirements, appendices and deadlines against 29 CFR 1904.41 and your applicable state plan before relying on any summary.