OSHA 300A filing season: practical tips for cleaner reporting

Every year the same thing happens. The calendar turns to January, and occupational-health teams realize the data they need for the OSHA Form 300A summary is scattered across clinics, spreadsheets and a dozen people's memories. The work is not hard. The scramble is. With a steady process, filing season becomes a review, not a fire drill.

Two deadlines anchor the season. The annual summary must be posted in the workplace from February 1 through April 30 under 29 CFR 1904.32, and establishments covered by the electronic rule must submit their data to OSHA through the Injury Tracking Application by March 2 under 29 CFR 1904.41. Knowing which one applies to each site is the first step.

Start with a clean log, not a clean summary

The 300A is only a tally of the 300 Log. If the log is wrong, the summary is wrong — confidently. Most filing errors trace back to recordability decisions made months earlier and never revisited. Pull the full year of cases and re-read each one against the general recording criteria in 29 CFR 1904.7: did it involve medical treatment beyond first aid, days away, restricted duty or transfer, or loss of consciousness?

• Confirm each case has a clear work-relatedness determination on file.
• Reconcile restricted-duty and days-away counts against the actual work-status reports.
• Flag any case still marked privacy-concern and verify it is handled correctly.
• Check that establishment names, EINs and average employment match payroll.

Reconcile your counts before you certify

The most common audit finding is not a fabricated case — it is a miscount. Day counts that were never closed out, a case that moved from restricted to days-away and was tallied twice, or an establishment roll-up that double-counts a transferred worker. Run the totals two ways: by case type and by column total. If they don't agree, you have a data problem, not a math problem.

Average employee count and total hours worked drive your incidence rates and your peer benchmarks. Estimating them at the last minute is where credibility leaks out. Pull them from the same payroll source every year so the numbers are defensible.

Know who certifies and what that means

A company executive must certify the 300A — not the clinic, not the safety coordinator acting alone. That signature is an attestation that the executive examined the log and believes the summary is correct and complete. Build in time for that review rather than chasing a signature on deadline day. Post the signed summary where employees can see it for the full February-to-April window required by 29 CFR 1904.32.

Make next year's season boring

The teams that file calmly are the ones who treat recordkeeping as a year-round habit instead of a January project. When recordability is decided at the point of care, work-status changes update the log automatically, and establishment data lives in one place, the summary practically writes itself. The goal is a filing season where the only surprise is how few surprises there are.

When is the OSHA 300A due?

Covered establishments must electronically submit prior-year data through OSHA's Injury Tracking Application by March 2 (29 CFR 1904.41), and the printed summary must be posted in the workplace from February 1 through April 30 (29 CFR 1904.32).

Who has to submit electronically?

Electronic submission requirements depend on establishment size and industry. Confirm whether each site is covered under the criteria in 29 CFR 1904.41 and OSHA's recordkeeping guidance before assuming you are exempt.

Who signs the 300A summary?

A company executive must certify the summary, attesting that they examined the OSHA 300 Log and believe the 300A is correct and complete.