A Technician Hurt Her Wrist at Site C but Works Out of Site A. Whose OSHA 300 Log Does It Go On?

Consider a field service technician who is based out of a regional branch but spends most of the week at customer facilities and at two other company locations that are short on staff. On Thursday afternoon she strains her wrist lifting a panel at the third location. It is a recordable injury. The branch manager at that site says she is not on his roster. Her home branch says the injury happened somewhere else. Corporate safety wants the case entered before the month closes. Three people each have a reasonable argument for why it is somebody else's entry.

Float nurses, rotating maintenance crews, regional trainers, delivery drivers who start at one depot and finish at another, and managers who cover several stores all create the same problem. The injury is real and the recording obligation is not in doubt. What is unclear is which establishment's log it belongs on, and in a multi-site company that question is rarely answered anywhere in writing.

The rule starts from the establishment, not the company

OSHA's recordkeeping regulation is built around the establishment, a single physical location where business is conducted. Under 29 CFR 1904.30, an employer keeps a separate OSHA 300 Log for each establishment that is expected to remain in operation for a year or longer. The same section addresses how to handle employees who do not fit neatly in one place, and it does so by requiring that each employee be linked to an establishment for recordkeeping purposes.

That link is the whole mechanism. An injury is recorded on the log of the establishment the employee is connected to under that rule, and the details differ depending on whether the person has a fixed home site, moves among several, or works without any fixed location at all. Section 1904.30(b) walks through those situations, and anyone designing a company procedure should read it directly rather than rely on a summary. The point for a portfolio operator is simpler: the regulation expects you to have decided, in advance, where every employee is anchored.

Why this is a portfolio problem and not a paperwork nuance

At a single location the assignment question never comes up, because everyone belongs to the same place. Across dozens of locations it shows up daily, and the answers matter in ways that go beyond whose spreadsheet holds the entry.

Take the headcount-based obligations first. Whether an establishment is partially exempt from recordkeeping, and whether it must submit injury data electronically, depends on its size and industry. Those determinations are made site by site, which we covered in our piece on establishment-level electronic submission and in our discussion of headcount and the recordkeeping exemption. If float workers are counted inconsistently, a site can look smaller or larger than it is, and an injury can land on a log that tells the wrong story about the place where the work was done.

Then there is what the numbers are used for. Plant managers are measured on their recordable rates, regional vice presidents compare locations, and customers sometimes ask for a site's incident history as part of a bid. A site that regularly hosts loaned staff but never records their injuries will look safer than it is. A site that exports its own workers to cover shortfalls elsewhere may carry cases that came from conditions at other buildings. Neither pattern is deliberate. Both are what happens when no one has decided a rule and every manager improvises.

Finally, there is inspection exposure. When a compliance officer asks for an establishment's injury and illness records, the employer has four business hours to produce them under 1904.40, a deadline we describe in the piece on the front desk during an inspection. An inspector looking at Site C will reasonably ask about injuries that happened there. If the technician's wrist injury sits on a log at Site A, the site manager may not know it exists and the answer to the question may be incomplete, not because anyone concealed it but because the records are organized by assignment while the question is about the physical place.

Where assignments quietly drift

The tricky part is that employee-to-establishment assignments are not static. Several ordinary events change them without anyone updating a record.

A person is hired into one location and then asked to cover a second one. A regional role is created and the holder keeps a home office address that does not match any establishment. A seasonal crew is dispatched from a central yard to temporary sites. A site closes and its staff are dispersed. An acquisition brings in employees whose payroll location reflects the seller's structure. In each case, the HR system and the safety log can quickly fall out of agreement.

Staffing arrangements add another layer. Workers supplied by an agency are generally recorded by the employer that supervises them on a day-to-day basis, which is why the division of responsibility is so important and is covered in our post on temporary workers and joint responsibility. The recording question for those workers belongs in the same written procedure as your own float staff, because the same manager is likely to be asking the same question about both.

What a workable procedure looks like

The goal is not to find the perfect rule for every situation. It is to make a decision once, write it down, and apply it the same way everywhere. A few elements tend to matter.

First, give every employee a single recordkeeping home. This should be a field in the HR or safety system, distinct from cost center or reporting line, and it should be tied to an establishment as defined for the logs. People who split time among sites still get one anchor, chosen by the criteria your procedure sets out and consistent with 1904.30(b).

Second, define who updates it and when. If a person's regular location changes, who notices and who changes the field? The most reliable approach is to make it part of the transfer or role-change workflow instead of leaving it to a safety coordinator who may never hear about the change.

Third, decide how the injury report reaches the right log. When an incident occurs at a site that is not the employee's anchor, the host site needs a way to notify the recording site quickly, and the recording site needs a way to see the details. A shared incident form with a mandatory field for the employee's home establishment, filled in at the moment of the report, closes most of the gap. The recordability decision itself should follow the same corporate guidance as every other case, a topic we explore in the piece on recordable classification consistency.

Fourth, audit it. Once a quarter, compare the list of employees assigned to each establishment against the injuries entered on each log and look for people who appear in one system and not the other. Look also for sites with unusually high numbers of visiting workers and no corresponding entries. These checks are inexpensive and they find the cases that were lost between sites.

The question to ask on Monday

If you are accountable for safety across a portfolio, the useful exercise is to pick three employees who do not work at a single location, such as a floating supervisor, a traveling technician and a shared trainer, and ask the site managers involved where an injury to each would be recorded. If you get three different answers, or if nobody can say, you have found the gap before an incident exposes it.

The regulation gives you the structure, and the rest is a matter of deciding and documenting. This article is general information, not legal advice. Read 29 CFR 1904.30 and the related OSHA interpretations for your specific workforce arrangements, and take guidance from counsel or your OSHA area office if a particular situation is not clear.