How to Complete OSHA Form 301 Without Creating Rework

Complete a 301, or an equivalent form, for every case on the 300 Log within 7 calendar days, using the same case number and enough detail to support the entry. It covers the employee, the treating provider, and the case itself: what the employee was doing, what happened, the injury or illness, and what caused it.

The 301 is where weak incident intake becomes a filing-season problem.

Gather these first, and keep them with the record afterward:

• The 300 Log with stable case numbers
• A 301 or equivalent for every case on the log
• The confidential privacy case list, if you have privacy cases
• The certified 300A and the worksheet behind its totals

OSHA recordkeeping uses three forms (29 CFR 1904.29). The OSHA 300 Log lists every recordable case with a one- or two-line description. The OSHA 301 Incident Report, or an equivalent form such as an insurance first report of injury that carries the same information, holds the detail for each case. The OSHA 300A Summary totals the log at year end. Each recordable case must be on the 300 and the 301 within 7 calendar days of receiving information that it occurred. The 300A is the only form you post, from February 1 to April 30, and a company executive certifies it first (29 CFR 1904.32).

1. Collect the employee, event, treatment, and outcome facts.
2. Fill in the 301 fields using the log's case number.
3. Check that the 301 and the 300 entry tell the same story.
4. Store the 301 with access limited to the people who need it.

Tip: Complete the incident report with enough detail to support the OSHA 300 entry and future updates.

Teams sometimes treat the 301 as a narrative dump instead of a structured incident record.

When the three forms live in separate files, the log, the incident reports, and the summary drift apart, and the certified numbers stop matching the case files. The fix is to treat the forms as one record with three views: a case number ties each 300 row to its 301, and the 300A is only ever totaled from the reviewed log.

Coordinators tend to do the data entry and chase the facts, so a short list of what to ask for, and from whom, saves more time than any template.

• Privacy-sensitive details need controlled access even when the 300 Log name is withheld.
• Records kept in software count if the system can produce equivalent forms on demand: by the end of the next business day for an employee request and within 4 business hours for a government request.

A delivery driver's 301 first reads “Hurt shoulder unloading.” The reviewer sends it back with three questions: what was the driver lifting, from where, and what did the clinic do? The revised 301 says the driver was lifting a 60 lb appliance from the truck bed, felt a pull in the right shoulder, and was prescribed physical therapy. That supports the 300 entry (“Strained right shoulder, lifting appliance”, column J) and makes the later update to restricted work easy to follow.

Every 300 entry feeds the 300A totals, the TRIR and DART rates built from them, and, for establishments that must submit case data, a row in the ITA file. A description written carelessly in March is the one an employee reads when they ask for the log in October.

300log builds the 300 row, the 301 detail, and the 300A totals from a single incident record, so the three forms cannot drift apart, and it exports each one as a PDF when you need to post, print, or hand over a copy.

For a quick answer without an account, use the free recordability checker.

• OSHA 300 Injury Description Examples That Are Clear Without Oversharing
• OSHA Form 301 Seven-Day Rule: When the Incident Report Must Be Complete
• OSHA Equivalent Forms for 300, 300A, and 301: What Counts
• Employee Access to OSHA 300 Logs: What Employers Should Be Ready to Provide