Leer en español
Compliance & Recordkeeping

OSHA 300 Log: Requirements, Posting Deadline, and How It Differs From the 300A

By the IncidentLog Editorial TeamReviewed against 29 CFR Part 1904, current as of publication

The OSHA 300 Log is the year-round injury and illness log most covered employers must keep; the 300A is the annual summary of that log, required to be posted in a visible location from February 1 through April 30 regardless of how many recordable cases occurred (29 CFR 1904.32); the 301 is the incident-level detail behind each entry. Separately, three groups of establishments must submit data through OSHA's Injury Tracking Application (ITA) by March 2 each year (29 CFR 1904.41): those with 20–249 employees in an industry listed in Appendix A to Subpart E, which includes construction and manufacturing (300A data); those with 250 or more employees in any industry that has to keep the log (300A data); and those with 100 or more employees in an industry listed in Appendix B to Subpart E (300 and 301 data as well).

OSHA 300 log requirements by date: post the 300A Feb 1, e-file by March 2, take it down Apr 30, keep records 5 years
The recordkeeping year at a glance: cases go on the log within 7 days all year, and the 300A has three dates.

The three OSHA forms, and how they differ

"OSHA 300 log" gets used loosely to mean three related but distinct documents under 29 CFR Part 1904:

FormWhat it isPosted?
Form 300The running log: one line per recordable case, updated all yearNo
Form 300AYear-end summary of the 300 log's totals, with a certifying signatureYes, Feb 1 to Apr 30
Form 301Incident-level detail behind a single recordable caseNo

When someone searches "OSHA 300 log requirements," they're usually really asking about the 300A's posting rule, since that's the one with a hard calendar deadline. This guide covers all three, since getting the 300A right depends on having the 300 log accurate first.

When the 300A must be posted

Under 29 CFR 1904.32, the 300A summarizing calendar year Y must be posted from February 1 through April 30 of year Y+1, in a location where employees normally see notices, like a break room bulletin board, not a filing cabinet. This applies even in a year with zero recordable cases: a "no cases" 300A still has to go up.

Do you have to submit anything electronically?

Posting the 300A satisfies the display requirement, but some employers separately owe an electronic submission through OSHA's Injury Tracking Application (ITA), due by March 2 each year under 29 CFR 1904.41. As of this writing:

  • Establishments with 20 to 249 employees in an industry listed in Appendix A to Subpart E (the list includes construction and manufacturing) submit their 300A data.
  • Establishments with 250 or more employees in an industry covered by the recordkeeping rule submit their 300A data.
  • Establishments with 100 or more employees in a designated high-hazard industry (Appendix B to Subpart E, which includes construction and several manufacturing sectors) submit 300, 300A, and 301 data.

Both the employee-count thresholds and the high-hazard industry list have been revised before and could be again, so confirm the current rule on OSHA's ITA page rather than assuming last year's thresholds still apply.

The 7-calendar-day rule most logs miss

Under 29 CFR 1904.29, a recordable case has to be entered on the 300 log within seven calendar days of the employer learning it happened: not seven business days, and not "by the time someone gets around to updating the spreadsheet." This is where a shared file usually breaks down: the incident happens on-site, but the person who maintains the log is often somewhere else entirely, and the two don't sync up inside the window.

OSHA 300 log case starting point: IncidentLog's mobile form filled in by a worker after a hand laceration at a conveyor
The worker files the report from the floor, so the person who keeps the 300 log has the facts the same day.

You also don't have to keep the log on paper or OSHA's own form. Digital substitutes are explicitly permitted under 29 CFR Part 1904, as long as the record captures every field OSHA's Form 300 requires. The rule is about what data you keep, not what software you keep it in. What actually changes when you switch is covered in paper vs. digital incident logs.

Privacy cases: when the name stays off the log

For some cases you must not write the employee's name on the 300 log. Under 29 CFR 1904.29(b)(6) and (b)(7), you enter "privacy case" in the name column for an injury or illness to an intimate body part or the reproductive system, one resulting from a sexual assault, a mental illness, HIV infection, hepatitis or tuberculosis, a needlestick or sharps injury contaminated with another person's blood or other potentially infectious material, and any other illness when the employee voluntarily asks that their name not be entered. That list is closed: no other case qualifies.

The names don't disappear. You keep a separate, confidential list of the case numbers and employee names, so the case can be updated and the name given to the government if it asks. If the description itself could identify the person, you may leave out details of an intimate or private nature, but the log still has to show what caused the injury or illness and how serious it was (1904.29(b)(9)).

In IncidentLog, the person who keeps the log marks the case as a privacy case on the report. The site's 300 log, its CSV and its printed form then show "Privacy case", and the names go on a confidential list that only owners and admins can open.

Why a spreadsheet usually isn't enough

A lot of small employers start their 300 log in Excel, and it works fine right up until it doesn't: the 300A totals have to be calculated by hand from the log every year, a shared spreadsheet has no record of who changed what or when, and there's nothing stopping a cell from getting edited after the fact, which matters if a claim or an inspection ever turns on the original numbers. None of that makes a spreadsheet non-compliant on its own, but it does mean the accuracy of your 300A rests entirely on someone remembering to do the math correctly, every year, with no audit trail if a number gets questioned later and, per the 7-day rule above, on that same person hearing about the incident in time.

IncidentLog keeps a 300 log for each site automatically as incidents get filed, computes the 300A totals from the same counts, and locks each report into a tamper-evident record the moment it's filed. The log updates the moment a report is submitted from the job site, not whenever someone remembers to open the spreadsheet, and it prints on OSHA's Legal-size Form 300 layout, 10 cases a page with page totals. For the other options, from OSHA's free forms to enterprise suites, see our comparison of the best OSHA recordkeeping software.

How to stay compliant, step by step

  1. Confirm you're a covered employer. Most employers with more than 10 employees are covered, unless your industry is on OSHA's partially-exempt list (29 CFR 1904 Subpart B, Appendix A); see the security-guard and daycare guides for two examples.
  2. Log each recordable case on Form 300 as it happens. Every work-related injury or illness that meets OSHA's recordable criteria (death, days away, job transfer/restriction, medical treatment beyond first aid, loss of consciousness, or a significant diagnosed condition) gets a line on the 300 log, not just the ones you remember at year-end.
  3. Total the year's cases and hours onto Form 300A. At year-end, add up case counts, days-away counts, and total hours worked across the establishment, plus the certifying executive's name, title, and signature.
  4. Post the 300A from February 1 through April 30. It has to be displayed somewhere employees normally see notices, even if the total is zero recordable cases for the year.
  5. Check whether you owe an electronic submission. If your establishment meets the size/industry thresholds, submit the required data through OSHA's Injury Tracking Application (ITA) by the annual deadline. Confirm the current thresholds and due date on OSHA's ITA site, since both have changed before.

Frequently asked questions

What is the OSHA 300 log?

It's the year-round log of every work-related injury and illness that meets OSHA's recordability criteria: one line per case, updated throughout the year as incidents happen. It stays on file at the establishment; it isn't the document that gets posted.

When is the OSHA 300A due?

The 300A summary must be posted in a visible location at the establishment from February 1 through April 30 of the year following the one it summarizes (29 CFR 1904.32), regardless of whether any recordable incidents occurred that year. It isn't "due" to OSHA on a specific date; it's a posting requirement, not a submission deadline, unless your establishment also owes an electronic ITA submission.

What's the difference between the OSHA 300 log and the 300A?

The 300 log is the running, case-by-case record kept all year. The 300A is the year-end summary of that log's totals (case counts, days away, injury and illness types) plus establishment info and an executive's certifying signature. The 300A is what gets posted; the 300 log doesn't.

What are the OSHA 300 log posting requirements?

Only the 300A summary gets posted, not the 300 log itself (which can contain details some employers prefer to keep less visible). It must be posted where employees can reasonably see it, for the full February 1 – April 30 window, even in a zero-incident year.

Do I need to submit the OSHA 300 log electronically?

Only if your establishment falls into one of three groups under 29 CFR 1904.41: 20–249 employees in an industry listed in Appendix A to Subpart E, a list that includes construction and manufacturing (submit 300A data); 250 or more employees in any industry that has to keep the OSHA 300 log (submit 300A data); or 100 or more employees in an industry listed in Appendix B to Subpart E (submit 300 and 301 data as well as the 300A). Submissions go through OSHA's Injury Tracking Application (ITA) by March 2 of the following year. These thresholds have been updated before, so confirm the current rule on OSHA's ITA site rather than assuming last year's figures still apply.

When is the OSHA 300A due this year?

The posting window is fixed by regulation, not the calendar year: whatever year you're in, the prior year's 300A goes up February 1 and comes down April 30 (29 CFR 1904.32). There's no separate "due date" announced each year. If you're asking because a deadline is approaching, check today's date against that February 1–April 30 window rather than searching for a year-specific number.

What is the purpose of the OSHA 300 log?

It gives OSHA, employees, and employers a standardized, year-round record of work-related injuries and illnesses at each establishment. The point is to make injury patterns visible (which tasks, shifts, or locations keep producing recordable cases) rather than just to satisfy a filing requirement. The 300A posting exists so employees can see that record too, not just OSHA.

What is a privacy case on the OSHA 300 log?

A case whose employee name you must leave off the 300 log, entering "privacy case" in the name column instead (29 CFR 1904.29(b)(6)). The list is closed: an injury or illness to an intimate body part or the reproductive system, one resulting from a sexual assault, a mental illness, HIV infection, hepatitis or tuberculosis, a needlestick or sharps injury contaminated with another person's blood or other potentially infectious material, and any other illness when the employee independently and voluntarily asks that their name not be entered (1904.29(b)(7)). You keep a separate, confidential list of the case numbers and names, so you can update the case and give the name to the government if asked.

Who is exempt from keeping the OSHA 300 log?

Employers with 10 or fewer employees at all times during the last calendar year (29 CFR 1904.1), and establishments in the partially exempt industries listed in Appendix A to Subpart B (1904.2). Neither group keeps the log unless OSHA or BLS asks in writing, and both still report a fatality within 8 hours and an in-patient hospitalization, amputation or loss of an eye within 24 hours (1904.39).

Where should the OSHA 300 log be posted?

The 300 log itself isn't posted. What gets posted is the 300A summary, in each establishment, in a conspicuous place where notices to employees are customarily posted, from February 1 to April 30 (29 CFR 1904.32(b)(5) and (b)(6)). The 300 log stays on file, and employees and their representatives can ask for a copy.

Does each location need its own OSHA 300 log?

Yes, each establishment expected to operate for a year or longer keeps its own log (29 CFR 1904.30(a)) and posts its own 300A. Short-term sites, like most construction jobs, can share one log. The records can live at headquarters as long as each case reaches the central log within 7 calendar days of learning about it.

Can I keep the OSHA 300 log in Excel?

Yes. OSHA publishes the forms as fillable PDF and Excel files, and 29 CFR 1904.29(b)(5) allows computer records if the system can produce equivalent forms when they're needed: within four business hours for a government request, and by the end of the next business day for an employee. What a spreadsheet doesn't give you is a record of who changed what, or a check on the 7-day entry window.

Sources

Keep reading

Let IncidentLog keep your 300 log and 300A

Every recordable incident logged through IncidentLog goes on that site's OSHA 300 log, with privacy cases kept off it by name, and rolls up into your 300A: case counts, day counts and injury/illness types, ready to review before the February 1 posting date. Plans start at $49/mo per site, no seat limits.

Not ready to sign up? Try the worker form first, no account needed