OSHA Form 300 Recordkeeping: What Manufacturing HR Teams Actually Need to Track

Last updated: June 2026

OSHA Form 300 recordkeeping isn’t complicated in theory. In practice, manufacturing HR teams get it wrong in predictable ways — and the consequences range from correctable paperwork issues to willful violations that carry serious financial penalties. The gap between “we think we’re compliant” and “we actually are” is usually a handful of specific misunderstandings about what counts as recordable, what the deadlines are, and who’s responsible for maintaining the log.

This guide covers what manufacturing HR teams need to track, what the most common recording errors look like, and how to set up a process that holds up under inspection.

OSHA Form 300 Basics: What You’re Required to Maintain

OSHA’s recordkeeping rule (29 CFR Part 1904) requires covered employers to maintain three documents: the OSHA 300 Log (a running list of recordable work-related injuries and illnesses), the OSHA 300A Summary (an annual summary posted each year from February 1 through April 30), and the OSHA 301 Incident Report (a detailed form for each recordable incident). These apply to most manufacturing establishments with 10 or more employees — the OSHA recordkeeping page has the full applicability criteria.

Records must be maintained for five years following the end of the calendar year that covers the injury or illness. They must be available for inspection by OSHA, and the OSHA 300A Summary must be posted in a location where employees can see it every year from February 1 through April 30. Missing the posting window is one of the most common — and most easily avoided — citations manufacturing facilities receive.

What Counts as a Recordable Incident

The definition of “recordable” is where most HR teams get into trouble. A work-related injury or illness is recordable if it results in any of the following:

• Days away from work
• Restricted work or job transfer
• Medical treatment beyond first aid
• Loss of consciousness
• Diagnosis of a significant injury or illness by a healthcare professional

First aid treatment — including non-prescription medications at nonprescription strength, cleaning and covering a wound, using a non-rigid means of support — does not require recording. The distinction between “first aid” and “medical treatment beyond first aid” is where most recording disputes arise.

The Work-Relatedness Requirement

An injury or illness is work-related if an event or exposure in the work environment caused or contributed to the condition, or significantly aggravated a pre-existing condition. The work environment includes any location where employees are present as a condition of their employment.

Exceptions exist: injuries that occur while the employee is eating lunch in a company cafeteria, injuries that result from personal grooming, injuries that are caused solely by a personal medical condition, and injuries from voluntary participation in wellness activities or recreational programs that the employer sponsors are generally not recordable. Manufacturing HR teams frequently over-record in these categories and under-record in others — particularly for repetitive motion injuries and hearing loss, which have specific recording criteria.

Musculoskeletal Disorders and Hearing Loss

Musculoskeletal disorders (MSDs) — back injuries, carpal tunnel, tendinitis — are recordable under the same criteria as any other injury. There’s no separate MSD standard, but manufacturing HR teams sometimes treat them differently because they develop gradually rather than from a single incident. The gradual onset doesn’t change the recording requirement.

Occupational hearing loss has specific recording criteria: you must record a standard threshold shift (STS) — a change in hearing threshold, relative to baseline, of 10 decibels or more in either ear averaged across 2000, 3000, and 4000 Hz — if the total hearing level in either ear is 25 decibels or more above audiometric zero. If your manufacturing environment includes significant noise exposure and you’re not tracking audiometric test results against these criteria, you’re likely under-recording.

Common OSHA 300 Recordkeeping Mistakes in Manufacturing

Recording Incidents After the 7-Day Window

Recordable incidents must be entered on the OSHA 300 Log within seven calendar days of receiving information that an injury or illness is recordable. When a supervisor holds an incident report on their desk for a week before forwarding it to HR, the deadline may already have passed. The seven-day clock starts when you have enough information to know the incident is recordable — not when the paperwork makes it to HR.

Confusing Reporting with Recording

Recording and reporting are different obligations. Recording means maintaining the OSHA 300 Log. Reporting means notifying OSHA directly. Fatalities must be reported to OSHA within 8 hours. In-patient hospitalizations, amputations, and eye losses must be reported within 24 hours. These reporting requirements exist alongside the recording requirement — they don’t replace it.

Not Posting the 300A Summary on Time

The 300A Summary must be posted in a conspicuous place where employees can see it by February 1 each year, covering the previous calendar year’s injury and illness data. It must remain posted through April 30. The summary must be certified by a company executive — not just an HR manager. Many manufacturing facilities miss the February 1 deadline or take the summary down before April 30. Both are citable violations.

Failing to Track the Privacy Case Requirement

For certain injury types — sexual assaults, mental illness cases, HIV/AIDS, tuberculosis, needlestick/sharps injuries, and injuries to intimate body parts — OSHA requires that employee names be withheld from the 300 Log and replaced with “privacy case.” These must still be recorded; only the name changes. HR teams that don’t have a process for identifying and flagging privacy cases end up either recording protected information on the public log or inadvertently omitting the record entirely.

Building a Recordkeeping Process That Holds Up Under Inspection

OSHA inspections in manufacturing can be triggered by a reported injury, a worker complaint, a programmed inspection under a national or local emphasis program, or a referral from another agency. When an inspector arrives, your 300 Log, 300A Summaries for the past five years, and 301 Incident Reports need to be accessible and accurate. Discrepancies between what’s on the log and what’s in your workers’ compensation records are a common trigger for deeper scrutiny.

The components of a recordkeeping process that survives inspection:

• Incident reporting from the floor up: Supervisors need a clear process for reporting incidents to HR within 24 hours — not after they’ve decided whether it’s recordable
• HR determines recordability: The decision of whether an incident is recordable belongs to HR, not the supervisor or the treating physician
• Consistent application of the first aid/medical treatment distinction: Document the criteria your facility uses and apply them consistently
• Annual audit before February 1: Review all 301 forms against the 300 Log before the summary is posted and certified
• Five-year retention policy: Records must survive management turnover and system changes — store them in a location that doesn’t depend on a single person’s filing system

Netchex’s HR management tools help manufacturing teams track incident documentation alongside employee records, with reporting capabilities that surface the data you need for OSHA compliance reviews without manual spreadsheet reconciliation.

Frequently Asked Questions

This guide reflects publicly available product information and independent reviewer data (G2, Capterra, Trustpilot, Yelp, Better Business Bureau, Reddit, Software Advice, GetApp) as of 2026. Feature availability and pricing may vary by plan. Contact each provider for current details.

Disclaimer: Any product roadmap or future plans provided herein are for informational purposes only. They do not represent a commitment to deliver any material, code, feature, or functionality. Plans may change without notification. The development, release and timing of any features or functionality described remain at the sole discretion of Netchex, its affiliates, and partners. Netchex does not give legal, tax, or accounting advice. You are responsible for ensuring your use of Netchex product meets your individual business and compliance requirements.

Print this page