An OSHA 300 Log Cleanup Needs Case-Level Proof Before the Annual Summary

An OSHA 300 log recordkeeping cleanup checklist helps covered employers identify missing cases, test recordability, reconcile Forms 300, 301, and 300A, protect privacy cases, and document corrections.

An OSHA 300 Log Cleanup Needs Case-Level Proof Before the Annual Summary
Recordkeeping control

An OSHA log cleanup starts with the incident source file because a polished annual summary cannot repair missing cases, unsupported classifications, or dates that do not reconcile across the underlying records.

CoverageInventoryClassifyReconcileCertify
Test each case. Do not start by forcing the Form 300A totals to match an assumption.

For an OSHA 300 log recordkeeping cleanup, first confirm whether the establishment must keep Part 1904 records. Then inventory every possible work-related injury or illness from incident reports, workers compensation files, clinic notes, restrictions, absences, and supervisor messages; test each case against the recording criteria; and reconcile Forms 300, 301, and 300A.

Do not assume a workers compensation claim is automatically recordable, treat first aid as medical treatment, remove a case because it looks bad, or place protected private information on the public-facing log or annual summary.

The OSHA Log and Incident Recordkeeping Cleanup Kit adds editable case inventory, recordability worksheet, form reconciliation, privacy review, annual control, correction log, and management follow-up tools behind this free checklist.

Reconcile six recordkeeping surfaces

SurfaceWhat to captureGap it can reveal
CoverageEstablishment, employee count, industry, exemption status, state-plan rules, and electronic-submission applicability.The business used the wrong recordkeeping or submission assumption.
Incident inventoryReports, dates, people, location, event description, care, restriction, days away, and source records.A possible case never reached the log review.
RecordabilityWork-relatedness, new-case analysis, general or special recording criterion, and decision support.A case was added or omitted without a documented test.
Form 301Case details, event narrative, treatment facts, and equivalent-form support.The incident-level file is missing or cannot support the log entry.
Form 300Case number, employee or privacy-case handling, job title, event, classification, and day counts.Case classification, dates, days, or privacy treatment are inconsistent.
Form 300AYear-end totals, hours, employment figures, executive certification, posting, submission, and retention proof.The summary does not tie to the final case-level log.

OSHA's recording guidance explains the general criteria and the duties of covered employers. OSHA's Form 300, 300A, and 301 rule states that a recordable case must be entered on the Form 300 Log and Form 301 Incident Report within seven calendar days after receiving information that a recordable injury or illness occurred. Coverage, work-relatedness, first aid, restricted work, privacy cases, day counting, fatality or severe-event reporting, electronic submission, and state-plan rules can be technical. Verify uncertain cases with a qualified safety professional or counsel.

Use four rules while cleaning the log

1. Start from source eventsThe workers compensation list, first-aid log, absence record, and supervisor inbox can expose cases missing from the formal incident queue.
2. Test one case at a timeDocument work-relatedness, whether it is a new case, and the exact criterion before choosing a classification.
3. Reconcile forms in orderThe incident detail supports the log; the completed log supports the annual summary. Reverse engineering the totals hides weak cases.
4. Preserve the correction trailRecord what changed, why, who reviewed it, and when. Do not erase the history that explains the cleanup.
Totals-first cleanup

The office manager changes the annual totals to match an insurance report, deletes an unclear case, and cannot show the rule or incident record behind either decision.

Case-level cleanup

The business inventories possible cases, applies the same decision test, reconciles incident support to the log, recalculates the summary, protects privacy cases, and preserves each correction.

Copy this OSHA case decision row

Injury and illness recordkeeping row
Case ID and establishment: [ID and site]
Employee or privacy case ID: [name or protected ID]
Event date and awareness date: [dates]
Source records: [incident, clinic, workers comp, schedule, restriction, messages]
Event or exposure: [factual description]
Work-relatedness review: [yes / no / uncertain and basis]
New case review: [yes / no / uncertain and basis]
General criterion: [death / days away / restricted or transfer / medical treatment beyond first aid / loss of consciousness / significant diagnosis / none / uncertain]
Special criterion: [needlestick / medical removal / hearing loss / tuberculosis / none / uncertain]
First aid or medical treatment facts: [facts]
Days away: [calendar dates and count]
Restricted or transfer days: [calendar dates and count]
Form 301 or equivalent: [file and completion date]
Form 300 classification and entry date: [classification and date]
Privacy-case treatment: [yes / no and control]
Correction needed: [field, reason, date, and reviewer]
Form 300A impact: [totals affected]
Electronic submission impact: [yes / no / professional review]
Advisor question: [question and owner]
Final status: [status and date]

Use a source-record request inside the business

Internal incident-record request:
We are reconciling the injury and illness records for [establishment and year]. By [date], send any incident report, first-aid note, clinic or restriction document, absence record, schedule change, workers compensation notice, or supervisor message involving a possible work-related injury or illness to [restricted location]. Do not alter earlier records, decide recordability by email, or include medical details in a shared team channel. The recordkeeping owner will review each case against the applicable criteria and will contact you for factual clarification if needed.

This draft organizes source records. It is not a determination that an event is work-related, recordable, compensable, reportable, or exempt.

Get the free Emergency Triage Sheet

The first three moves for any business emergency, plus one practical fix in your inbox each week.

No spam. Unsubscribe anytime.

Worked example: treatment and restriction records disagree

A hypothetical distribution business finds a supervisor message saying an employee strained a shoulder and returned to light work. The workers compensation file contains a clinic note, but the incident folder and OSHA log contain no case. The safety lead does not automatically add the case based on the claim or leave it off because the employee kept working.

The business records the event in the cleanup inventory, obtains the source note through the restricted process, identifies the treatment and restriction facts, tests work-relatedness and the recording criteria, and sends the uncertain classification to a qualified safety professional. If a correction is required, the business documents the changed fields and recalculates the annual summary from the final case list. The example shows the workflow, not the legal classification of an actual injury.

OSHA 300 log recordkeeping cleanup checklist

  • Confirm establishment coverage, exemptions, state-plan differences, and electronic-submission duties.
  • Inventory possible cases from every incident, medical, absence, restriction, insurance, and supervisor source.
  • Preserve original records and create a correction log before changing a form.
  • Test work-relatedness and whether the event is a new case.
  • Apply the general or special recording criteria to each possible case.
  • Distinguish first aid from medical treatment using the actual rule.
  • Complete or reconcile a Form 301 or equivalent for every recorded case.
  • Check Form 300 descriptions, classifications, day counts, and establishment assignment.
  • Protect privacy cases and avoid putting unnecessary medical details on shared records.
  • Recalculate Form 300A totals from the completed Form 300 Log.
  • Document executive certification, posting, submission, and retention as applicable.
  • Escalate uncertain, severe-event, retaliation, state-plan, or inspection issues for qualified advice.

FAQ: does a workers compensation claim belong on the OSHA log?

Not automatically. Workers compensation and OSHA recordkeeping use different systems and standards. The claim can be an important source record, but the employer still must evaluate OSHA coverage, work-relatedness, whether it is a new case, and whether a recording criterion applies. Keep the systems reconciled without treating one as the legal answer for the other.

Connect the log to incident and people records

The workers compensation audit records guide helps keep payroll and class-code evidence separate from injury recordability. Use the commercial vehicle accident reporting workflow when a road incident also creates insurance and operational records. If injury, restrictions, leave, or performance overlap, the employee evaluation decision boundary helps keep medical and safety processes out of performance ratings.

Free version vs. full kit

This article gives you the free version: the six-surface reconciliation, case decision row, source-record request, worked example, and cleanup checklist. The paid kit adds editable coverage, case, recordability, form, privacy, annual-summary, correction, and prevention tools.

Get the OSHA Log and Incident Recordkeeping Cleanup Kit

The All-Access membership includes the complete kit library while membership is active. The one-time OSHA recordkeeping kit remains the primary next step for this article.

Fix the next one before it starts.

Join the list for the free Emergency Triage Sheet and a new practical fix every week.

No spam. Unsubscribe anytime.

Get the fix before you need it.

Practical tips and new kits straight to your inbox—plus the free Emergency Triage Sheet when you join.