A Former Employee Asks for the Injury Log. The Clock Is Already Running and the Log Is Three Time Zones Away.

A request for an injury log rarely arrives where the log is kept. A former employee emails the corporate careers address. A union representative calls the regional office. A current employee asks a supervisor at a site that keeps its records at a different location, or in a system administered from head office. Nobody in the chain recognizes the request as one with a legal deadline, so it travels from inbox to inbox while the time allowed for responding quietly runs out.

This piece covers one narrow question for an organization with many establishments: when a worker, a former worker, or a representative asks for OSHA injury and illness records, what does 29 CFR 1904.35(b)(2) require, how fast, and where does that obligation break down when the records and the requester are in different places? It is a separate question from the one governing requests from OSHA itself, which we cover in the piece on the front desk during an inspection. It is also separate from how a log is built in the first place, such as how privacy concern cases are handled.

Who has the right to ask

Section 1904.35(b)(2) provides that employees, former employees, their personal representatives, and their authorized employee representatives have the right to access the OSHA injury and illness records. The definitions matter. An authorized employee representative is an authorized collective bargaining agent of employees. A personal representative is a person the employee or former employee designates in writing, or the legal representative of a deceased or legally incapacitated employee or former employee.

Two features of that list are worth pausing on for a multi-site operator. First, it includes former employees. People who left your company, possibly years earlier, and who have no ongoing relationship with any site manager, can ask. Second, the request does not have to come through any particular channel. The regulation does not tell the requester to write to a named person or use a form. If your intake process assumes the request will reach the right desk, it is relying on something the standard does not guarantee.

The deadline for the 300 Log

For the OSHA 300 Log, the rule is direct. When one of those requesters asks for a copy of the current or stored 300 Log for an establishment where the requester has worked, the employer must give them a copy by the end of the next business day.

Two phrases carry the weight. "For an establishment where the requester has worked" ties the right to the location. A worker is entitled to the log for the establishment where they worked, which in a company that keeps a separate log per establishment means the log for their site, not a consolidated company-wide file. That fits how recordkeeping is organized under Part 1904, and it connects to the establishment questions we examined in the establishment trap in electronic recordkeeping.

"By the end of the next business day" is a short window. It is not tolled while the request is forwarded, and the regulation does not make an exception for a request that was routed to the wrong office. For a company with records held centrally, the practical meaning is that someone with access to every establishment's log has to be reachable the same or next day, including for requests that arrive on a Friday afternoon.

The standard also addresses names. The employer cannot remove employee names from the copy of the 300 Log it provides. The exception is the set of privacy concern cases that 1904.29(b)(6) through (9) allow to be recorded without the employee's name. In those cases the log is meant to carry "privacy case" in the name column, and that is what the requester sees. Sites that redact all names by habit, because a manager thinks it is safer, are not following the rule.

Form 301: a different clock for different requesters

The OSHA 301 Incident Report follows a split structure, and it is the part sites most often get wrong.

If the requester is an employee, former employee, or personal representative, the employer must provide a copy of the 301 describing that particular person's injury or illness by the end of the next business day. The right attaches to the incident that involved the requester. It does not extend to everybody else's forms.

If the requester is an authorized employee representative under a collective bargaining arrangement, the timeline is longer: copies within 7 calendar days. There is also a limit on content. The employer is required to give the representative only the information from the section of the 301 titled "Tell us about the case," and must remove all other information from the copies. A site that photocopies the entire form is giving out more than the standard asks for, and a site that sends the wrong section is giving less.

For an enterprise, these two timelines mean that identical-looking requests may belong to different categories. A request from a union steward and a request from the injured worker for the same incident carry different deadlines and different scope. Whoever triages the request needs to know which requester they are dealing with before they pull the file.

No charge for the first copy

The rule says that the employer may not charge for the copies the first time they are provided. A person who has designated a representative or asks again can be charged a reasonable fee for retrieving and copying. A site that tells a requester there is a processing fee for an initial request has misread the standard. It is a small point, but it is the kind that turns a routine request into a complaint.

Where multi-site records requests actually stall

The regulation is short and clear. The difficulty is organizational. Here are the places where the obligation tends to break down in operators with many locations.

The first is intake. Requests go to the site, to corporate HR, to a legal inbox, to a safety manager, to a general contact form. Unless one of those paths is defined as the place where these requests are logged with a time stamp, no one can say when the clock started.

The second is custody. Some companies keep each site's log on paper at the site. Others centralize the log in a software system. Still others do both, with a site-level working copy and a corporate version that is edited later. A request for the "current" log raises the question of which version is the one that should be given. The answer in the standard is the log for the establishment, but the process needs to say who is authorized to produce it and from where.

The third is requester identity. A former employee emailing from a personal address, or a person claiming to represent a worker, raises a verification question. The standard gives the employer the definitions above, but it does not spell out how to confirm that someone is a designee. A written procedure for verifying a personal representative's written designation, applied the same way everywhere, prevents each site manager from improvising.

The fourth is the interplay with an inspection. When an authorized government representative asks for the same records under 1904.40, the employer must provide copies within four business hours. If the records are kept at a location in a different time zone, the standard says the employer may use the business hours of the establishment where the records are located in calculating that deadline. The employee access rule has no matching time zone provision, so do not borrow it. The shorter four-hour clock and the next-business-day clock are different obligations, owed to different parties, and a records process built for one will not automatically satisfy the other.

A test you can run across the portfolio

You can find out how a records request would fare without waiting for a real one. Choose three or four establishments in different regions and have someone, ideally outside the safety function, submit a request for the establishment's current 300 Log through whichever channel a former employee would plausibly use, such as the general website contact or a main phone line. Record the time the request is sent, the time it reaches someone who knows what it is, and the time a compliant copy is produced. Then do the same with a mock request from a designated representative for a single 301.

The results show whether the process works in practice or only in the procedure binder. If one site turns it around in an hour and another cannot locate its log, the question is not about the individual manager. It is about whether the organization has a single, owned path for these requests.

None of this makes a company compliant with Part 1904 as a whole, and the standard contains requirements beyond access. But the access provisions are among the most time-sensitive in the recordkeeping rules, they are triggered by people outside the company, and they depend on records held in many places. That is the combination that tends to expose gaps between sites.