When Is The Osha 300 Log Due

When Is the OSHA 300 Log Due?

Let’s be honest—most people don’t think about their company’s OSHA 300 log until it’s already late. Or worse, until they get audited. So if you’re here, you’re probably either trying to get ahead of the deadline or scrambling to figure out when it’s actually due. Either way, you’re in the right place.

The short version is this: the OSHA 300 Log is due on the last day of the month following the calendar year in which the recordable injuries and illnesses occurred. But that’s just the surface. There’s a lot more beneath the surface—especially if you’re managing a larger team, multiple worksites, or just want to stay compliant without stress.

What Is the OSHA 300 Log?

First, let’s clear the air. In real terms, the OSHA 300 Log isn’t some random paperwork you file once a year for fun. That said, it’s a legally required record-keeping system that employers must maintain to document work-related injuries and illnesses. Think of it as your company’s public health diary—showing how safe (or unsafe) your workplace really is.

OSHA requires most private sector employers to keep this log if they have ten or more employees, or if they operate a workplaces with hazardous conditions—even if they only have one employee. Once you meet those criteria, every work-related incident that meets OSHA’s definition of “recordable” needs to go in there. That includes things like:

• Days away from work
• Restricted work cases
• Medical treatments beyond first aid
• Diagnoses like cancer, fractures, or amputations

You’re not just logging every paper cut. But if someone misses work or needs more than basic first aid, it goes in the log.

And here’s the kicker: you’re not just maintaining this log for yourself. It’s also a public document. And oSHA can request to see it during inspections, and in many cases, it’s posted where employees can view it. So if you’ve ever wondered why some companies have a big poster with a logbook on the wall, that’s why.

Why It Matters

So why does this matter? Well, for one, it’s the law. OSHA enforces recordkeeping rules to ensure workplaces are safer and more transparent. But beyond legal compliance, the log serves a bigger purpose: it helps identify patterns. Maybe you’ve had three back injuries in the warehouse over six months. That’s a red flag. Maybe your construction crew keeps getting minor cuts. That’s another.

The log is also a tool for improvement. When you can see where incidents are clustered—by department, by task, by time of year—you can start making smarter safety decisions. And let’s be real: fewer injuries mean fewer workers’ comp claims, fewer lost hours, and fewer headaches for everyone.

But here’s what most employers don’t realize until it’s too late: the log isn’t just about the present. It’s also a historical record. If you ever get audited, OSHA will want to see your logs for the previous five years. That’s a long time to keep accurate records. Miss a year? That’s a violation.

How It Works: The Timeline Breakdown

Alright, let’s get into the nitty-gritty. When is the OSHA 300 Log actually due? The answer depends on a few factors, so let’s break it down.

The Calendar Year Rule

For most employers, the OSHA 300 Log is due on the last day of the month following the calendar year in which the incidents occurred. That means if someone gets injured in January 2024, the log entry is due by February 29, 2024 (since 2024 is a leap year). If the injury happened in December 2024, your log is due by January 31, 2025.

But wait—there’s more to it than just the year. OSHA also requires you to post the log in a visible area for employees to see. That posting has its own deadline, which is usually April 30th each year. So if you had incidents in 2024, you need to have your OSHA 300 Log posted by April 30, 2025.

This is where the real value is.

What If Your Work Year Doesn’t Match the Calendar Year?

Some employers—like those operating on a fiscal year—might have a slightly different timeline. If your company uses a fiscal year that doesn’t align with the calendar year, you can request an exception from OSHA. But even then, the log is still due by the end of the month following your fiscal year-end. So if your fiscal year ends in June, your log is due by July 31.

When Do You Start Logging?

Here’s a common point of confusion: when do you actually start recording incidents? For calendar-year employers, that’s January 1. The answer is simple—the first day of your log year. For fiscal-year companies, it’s the first day of their fiscal year.

If an incident happens before your log year starts, you don’t record it on the current year’s log. Instead, you note it on the previous year’s log. And if it happens after your log year ends, you wait until the next year to record it.

Common Mistakes (And What Most People Get Wrong)

Let’s talk about where things usually go sideways. Because if you’re reading this, you probably want to avoid these pitfalls.

Mistake #1: Confusing the Log With the Summary

Many employers think the OSHA 300 Log and the OSHA 300A Summary (the posting form) are the same thing. They’re not. This leads to the 300A is the summary form you post for employees. The 300 Log is the detailed record of every incident. You fill out the 300A after you’ve completed the log for the year.

You can’t post the 300A until you’ve updated and reviewed the entire 300 Log. Because of that, it’s a chain. And you can’t update the log until you’ve recorded all the incidents. Miss one link, and the whole thing falls apart.

Mistake #2: Missing the Posting Deadline

This one trips up even experienced HR managers. In real terms, the log itself is due by the end of the following month, but the posting deadline is April 30 each year. That’s non-negotiable for most employers.

For more on this topic, read our article on what is an arc flash protection boundary or check out how old do you have to be to work construction.

Mistake #3: Incomplete or Inaccurate Incident Details

A common slip is filling in the log with the bare minimum—just the date, the injury, and the employee’s name. OSHA’s regulations demand far more granularity. Each entry must include:

Skipping any of these fields can trigger an audit, and missing data often leads to a “non‑compliant” flag on your OSHA record‑keeping status. It’s tempting to skip the “days of restricted duty” or to write “unknown” for the medical treatment, but OSHA expects concrete answers. If you’re uncertain, consult the employee’s medical record or your safety officer before finalizing the entry.

Mistake #4: Overlooking “Near‑Miss” Reports

OSHA’s 300 Log focuses on injuries身 and illnesses that result in Administratively or medically significant events. Even so, many organizations use the 300 Log as a broader safety tool to capture near‑misses—situations where an injury could have occurred but did not. While the 300 Log isn’t required for near‑misses, recording them in a separate safety database can help you identify trends and implement proactive controls. Ignoring near‑misses means you’re missing a huge opportunity to prevent future incidents.

Mistake #5: Failing to Update the Log in Real Time

Some employers wait until the end of the year to pull together all incidents and then scramble to fill out the log. This “end‑of‑year rush” often results in missed entries, especially for incidents that occurred in the last month of the year. Worth adding: oSHA requires that you record each incident within 30 days of its occurrence. By maintaining a rolling log—adding entries as soon as they happen—you’ll avoid the last‑minute panic and reduce the risk of errors.

How to Stay on Top of Your OSHA 300 Log

Below is a practical, step‑by‑step checklist that turns compliance into a routine, rather than a chore.

Automate Where You Can

Many software solutions now integrate OSHA 300 Log templates directly into your incident management system. Features to look for:

• Auto‑notification when a new incident is logged.
• Pre‑built compliance templates that map incident data straight to the OSHA fields.
• Audit trails that record every change to an entry.
• Reminders for the 30‑day recording window and April 30 posting deadline.

Automation reduces human error and frees up your safety team officially to focus on prevention rather than paperwork.

Resources to Keep You Informed

When in doubt, lean on OSHA’s help desk or your state OSHA plan. They’re there to answer questions and provide clarification.

Conclusion

Keeping an OSHA 300 Log isn’t just a bureaucratic requirement—it’s a cornerstone of workplace safety. By understanding the precise deadlines, recording every incident with full detail, and avoiding the common pitfalls that trip up even seasoned HR professionals, you’ll protect your employees,

and your organization from costly penalties and legal risks. This leads to regular audits and timely submissions not only meet regulatory standards but also demonstrate your company’s unwavering commitment to transparency and employee well-being. The resources provided serve as a safety net, ensuring you stay informed about evolving requirements and industry best practices. By implementing the outlined steps and leveraging automation tools, you transform recordkeeping into a proactive strategy for identifying hazards and preventing future incidents. The bottom line: a well-maintained OSHA 300 Log reflects a culture of accountability and continuous improvement—one that prioritizes people while safeguarding your business’s reputation and operational integrity.