By Cortni Lawson, Founder & CEO, InfraNet HR
The Form That Costs You $15K Per Violation
OSHA Form 301. Injury and Illness Incident Report.
It's a simple form. Employees fill it out when they get hurt. You keep copies. Every year, you compile a summary on the OSHA 300 log. You post the 300A summary (annual totals) in the workplace.
Simple, right?
Except it's not. And OSHA violations from incomplete, inaccurate, or missing 301 logs are some of the most common citations employers get.
The penalty: up to $15,000+ per violation. A single inspection can reveal multiple violations—multiple employees who should have filed 301s but didn't, multiple forms with missing information, discrepancies between the 301s and the 300 log.
Suddenly you're looking at $30,000-$100,000+ in penalties.
But the financial penalty isn't even the worst part. The worst part is that OSHA violations from injury reporting are a red flag for other safety problems.
An inspection starts with a question about recordkeeping. Ends with citations for failure to maintain safe working conditions.
Why 301 Compliance is Hard
1. Definitional confusion
Is a cut that doesn't need medical treatment recordable? What about a minor burn that the employee treats at home with ice? What about a near-miss that didn't actually result in injury?
OSHA has specific rules about what's recordable and what's not. But the rules are complex, and interpretation varies.
Err on the side of over-reporting. Better to report something that might not be technically required than to miss something that is.
2. Delayed reporting
An employee gets hurt. Doesn't report it immediately. Three days later, the injury is still bothering them, and they tell their supervisor. Now you need to file a 301. But you're doing it three days after the injury.
If you don't date it correctly, or if there are questions about when the injury actually occurred, you've got a documentation problem.
3. Incomplete information
The 301 requires a lot of information: employee name and SSN, date of injury, nature of injury, part of body affected, object or substance that directly injured the person, description of how the injury occurred.
If any of that information is missing, the form is incomplete. An incomplete 301 is a violation.
4. Failure to record
Maybe the employee reported the injury to their supervisor, but the supervisor never told HR. The injury never gets recorded. When OSHA audits, they find employees who had injuries that were never put on the 300 log.
That's a failure to record violation.
5. Misclassification
An injury is recorded, but classified incorrectly. Maybe it's recorded as a minor cut when it was actually a laceration requiring stitches. Maybe it's recorded as involving one part of the body when it involved another.
Misclassification is a violation.
6. 300 log discrepancies
You have 301s filed throughout the year. At year-end, you compile them onto the OSHA 300 log. But you miss some. Or you count some twice. Or information doesn't match between the 301 and the 300.
Now your 300 log is inaccurate. That's a violation.
Why This Matters Beyond Compliance
OSHA recordkeeping violations are low-hanging fruit for federal citations, but they're also a window into other safety problems.
If your injury reporting system is so disorganized that OSHA finds missing 301s, that suggests you don't have good hazard control either.
Companies with strong injury reporting systems tend to have strong overall safety programs. Companies with weak injury reporting tend to have weak overall safety programs.
So an OSHA inspection that starts with a recordkeeping question often expands into broader safety investigations.
You get cited for incomplete 301s. You also get cited for the hazards that caused the injuries, or for failure to follow up on injuries to prevent recurrence.
One violation becomes three.
The Retaliation Risk
There's another layer to injury reporting: retaliation.
Employees report injuries. If they subsequently experience adverse action, is that retaliation?
Under OSHA, yes. The OSH Act protects employees from retaliation for reporting workplace injuries or safety hazards.
An employee gets hurt, files a 301, and then gets written up or disciplined or has hours cut. That's potentially OSHA retaliation.
The problem: if your injury reporting system is separate from your employee record system, you might not see the pattern.
An employee files a 301 on Monday. Gets written up on Friday. If those two events are in different systems, nobody's looking at them together.
But if there are three employees with the same pattern—injury report followed by adverse action—that's a pattern of OSHA retaliation.
OSHA takes that seriously. They can investigate. They can issue citations. They can require remediation.
And it all starts because you couldn't see the connection between the injury report and the employment action.
A Real Scenario
Your manufacturing facility has an employee, David, who works in the assembly line.
David gets his hand caught in a piece of equipment. He reports it to his supervisor immediately. The supervisor tells him to go to the ER. David gets stitches. It's a laceration requiring medical care.
This is clearly OSHA-recordable. Someone should file a 301.
But here's what actually happens:
David's supervisor is busy. He doesn't immediately report the injury to HR. David goes to the ER, gets treated, reports back to work the next day.
Three days later, someone notices David is still favoring his hand. HR asks about it. David mentions the injury from three days ago. HR realizes a 301 never got filed.
They file one now, but it's dated the day it's filed, not the day the injury actually occurred. Or maybe they figure out the actual date and date it correctly, but now there's ambiguity about when the injury was actually reported.
Meanwhile, the supervisor never documented the injury in his notes. There's no contemporaneous record from the day it happened.
A month later, David's supervisor is frustrated that David can't do certain tasks because his hand is still healing. The supervisor documents a performance issue—"slow work, low productivity."
In the interim, David has filed a complaint with HR saying he thinks he's being retaliated against for the injury.
Now you have:
- A 301 that was filed late
- A performance issue documented shortly after the injury
- A retaliation complaint
If OSHA investigates, they'll ask: Why was the 301 filed late? Why is there no contemporaneous documentation from the day of injury? Why was the employee written up shortly after reporting the injury?
The supervisor's answer will probably be, "I didn't know about the injury until later," which is true. But it also shows you don't have a system for capturing injuries when they happen.
The performance issue documentation will look retaliatory, whether it was intended that way or not.
You've got an OSHA recordkeeping violation, possibly a retaliation violation, and poor documentation across the board.
What OSHA Compliance Actually Requires
1. A system for reporting injuries
Employees need an easy way to report injuries. A form, a hotline, a supervisor, or an online system.
Whatever the mechanism, it needs to:
- Be accessible (employees know about it)
- Be quick (doesn't require extensive documentation from the employee)
- Be immediate (happens as close to the injury time as possible)
- Be documented (you have a record that the report was made)
2. A process for determining recordability
When an injury is reported, someone (ideally HR or a designated safety person) needs to evaluate whether it's OSHA-recordable.
The evaluation should be documented. You should be able to show your reasoning for why something is or isn't recordable.
If there's uncertainty, err on the side of recording.
3. A 301 form completed for every recordable injury
The form needs complete information:
- Employee name, SSN, date of birth
- Date of injury
- Time of injury
- Nature of injury (fracture, burn, laceration, etc.)
- Part of body affected
- Object or substance that directly injured the person
- Description of how the injury occurred
Incomplete forms are violations.
4. A 300 log updated and accurate
At the end of each year (or continuously throughout the year), you compile the 301s onto the OSHA 300 log.
The 300 log needs to be:
- Complete (all recordable injuries are included)
- Accurate (information matches the 301s)
- Timely (updated within a reasonable time after the injury)
5. A 300A summary posted
By February 1 each year, you post a summary of the previous year's injuries (OSHA Form 300A). The summary shows total injuries, totals by category (e.g., injuries with days away from work), etc.
The summary must be posted until April 30.
6. Documentation and retention
You keep records for five years (or as required by state law, which might be longer).
7. Employee access
Employees have the right to access the OSHA 300 log and related documents. You can't hide injury records.
The System Challenge
The challenge is coordination across systems and processes.
An injury gets reported to a supervisor. Does it get communicated to HR? Does HR evaluate recordability, or does the supervisor? If the supervisor evaluates it, is there a way to verify they did it correctly?
If the injury is recordable, who files the 301? Where is it stored? How is it tracked?
At year-end, who compiles the 301s onto the 300 log? Is there a process for checking that all injuries are included, or do some slip through?
If an injury is reported late, how is that tracked? Do you still file the 301, or do you assume it's too late?
If the employee reports an injury to HR, and then the employee subsequently experiences adverse action, is that tracked together? Or are the events in separate systems?
Most companies manage these through a combination of email, spreadsheets, HR systems, and manual tracking. Things slip through.
What Visibility Actually Requires
You need a system where:
Injuries are reported and captured immediately. Not days later. Not through email chains. Through a system that creates a record.
Recordability is evaluated promptly. Someone (designated) evaluates whether the injury is recordable. The evaluation is documented. There's a process for escalating uncertain cases.
301s are completed fully. All required information is captured. Missing information is flagged. You don't send incomplete forms to OSHA.
300 logs are accurate. The log is compiled from the 301s with no gaps. You can see what's included and what's not. Discrepancies are resolved.
Timeline visibility exists. You can see when an injury was reported, when it was evaluated, when the 301 was completed, when it was added to the 300.
Retaliation risk is visible. You can see if an injury report was followed by adverse employment action. You can flag concerning timing.
Regulatory deadlines are tracked. You know when the annual 300A summary is due. You know when it needs to be posted and removed.
This level of coordination is nearly impossible across fragmented systems. It's automatic with an integrated system.
The Real Cost
A single OSHA citation for recordkeeping violations: $15,000+
Multiple violations from a single inspection: $50,000-$150,000+
Added citations for safety hazards identified during the investigation: $50,000-$200,000+
Retaliation violations: $30,000-$100,000+
A single inspection can cost you $200,000-$400,000+ in penalties alone.
That's not including legal fees, remediation costs, or the operational disruption.
What You Should Do
- Audit your current process. How are injuries currently reported? How is recordability evaluated? Who files the 301s? How are they stored and tracked? How do you compile the 300 log?
- Identify gaps. What's missing? What's not documented? What's vulnerable if OSHA asks for it?
- Implement controls. Get a system (or process) that captures injuries immediately, tracks recordability, maintains 301s, and compiles the 300 log. Train your supervisors and HR team on what's recordable and how to report. Document everything.
- Review for patterns. Look at your injury data. Are certain areas of the facility more dangerous? Certain job roles? Are certain employees repeatedly injured? Are there retaliation patterns?
- Close the loop. After an injury, follow up. Is the employee back to full duty? Were there lessons learned? Did you address the hazard that caused the injury?
That's what a real safety program looks like.
And that's what OSHA expects to see.