OSHA 300 Case Numbering: How to Keep the Log, 301, and Privacy List Connected

Give each recordable case a unique number when it first goes on the 300 Log, and use that same number on its 301 and on the privacy case list. OSHA only asks for a unique case number; a year-sequence format such as 2026-001 works well and never needs to change.

Case numbers become the link between the OSHA 300 Log, the 301 details, and the confidential privacy list.

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. Assign the number once, when the case is first recorded.
2. Put it on the 300, the 301, and any privacy list entry.
3. Keep the number if the classification changes or the entry is lined out.
4. Audit changes instead of renumbering.

Tip: Use stable case numbers that stay attached to the incident even if classification changes.

Teams renumber rows after sorting spreadsheets and break the evidence trail.

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 cases need a confidential name list tied back to the public log case number.
• 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 coordinator sorts the log spreadsheet by date, and the row numbers they were using as case numbers shift. Case 14's 301 now points at a different employee's row. The fix is a case number column that is typed once (2026-014) and never derived from the row position, with the same value on the 301 and the privacy list.

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 Log Description Examples: Clear Enough Without Overexposing Details
• Can a Workers Comp Form Replace OSHA 301? Equivalent Form Rules
• Printable OSHA 300, 300A & 301 Forms: Official PDF Downloads
• OSHA ITA Filing With No Injuries: What to Submit for Zero Cases