When Should The Osha Annual Summary Be Posted

When should the OSHA annual summary be posted?
If you’ve ever stared at a blank compliance calendar wondering, “Did I miss the deadline?” you’re not alone. The OSHA 300‑A Summary of Work‑Related Injuries and Illnesses is one of those regulatory chores that feels both inevitable and mysterious—until you actually map it out. Below is everything you need to know, from the legal deadline to the practical steps that keep you from scrambling at the last minute.

What Is the OSHA Annual Summary

In plain English, the OSHA annual summary is a one‑page snapshot of all recordable workplace injuries and illnesses that happened at your site during the previous calendar year. It’s the final piece of the OSHA 300 Log family, which also includes the daily 300 Log (the big spreadsheet of every incident) and the 301 Incident Report (the deep‑dive case file).

The 300‑A isn’t a detailed narrative; it’s a tallied table that shows the total number of cases, days away from work, job‑transfer or restriction days, and any other recordable incidents. Practically speaking, the purpose? Give OSHA and the public a quick, high‑level view of how safe a workplace really is.

Who Has to File

Most private employers with 250 or more employees, plus any employer with a high‑hazard industry classification (construction, manufacturing, maritime, etc.), must keep the logs and post the 300‑A. If you’re a small business under 250 employees in a low‑hazard sector, you’re probably exempt—but you still have to keep the logs in case you cross the threshold later.

Where It Goes

The summary must be posted in a “visible location” where all employees can see it. Think break room bulletin board, near the time‑clock, or on a shared digital screen that’s always on during shifts. The key is visibility, not just “it exists somewhere on the intranet.

Why It Matters

Missing the posting deadline isn’t just a slap on the wrist; it can trigger real consequences. First, OSHA can issue citations that start at $13,653 per day for each violation (as of 2024). Second, employees who can’t see the data may feel the company is hiding something, eroding trust and morale.

And there’s a bigger picture, too. Also, when the summary is posted on time, you’re essentially saying, “We’re transparent about safety. ” That transparency can be a selling point when you’re bidding for contracts, especially with government agencies that scrutinize safety records.

How It Works

Below is the step‑by‑step process that takes you from a raw incident log to a posted 300‑A summary. Follow it in order and you’ll never wonder “Did I do that right?” again.

1. Collect All Recordable Incidents

Pull the 300 Log – Export the data from your electronic safety management system (or flip through the paper log).
Verify Classification – Make sure each case meets OSHA’s “recordable” criteria: death, days away from work, restricted work, transfer to another job, medical treatment beyond first aid, or loss of consciousness.
Cross‑Check with Payroll – Days away or restricted work should line up with time‑off records. Discrepancies often surface here.

2. Tally the Numbers

Total Cases – Count every recordable case, regardless of severity.
Days Away From Work (DAFW) – Add up all days employees were completely off the job.
Job‑Transfer or Restriction Days (JTRD) – Sum days where workers were on modified duties.
Other Recordable Cases – Include medical‑only cases that don’t involve days away.

Most software will generate the 300‑A automatically, but if you’re still using spreadsheets, a simple pivot table does the trick.

3. Fill Out the OSHA 300‑A Form

The form is a single page with columns for each of the tallies above, plus a place for the employer’s name, address, and the year covered. Double‑check that the year you’re reporting matches the calendar year (January 1 – December 31).

4. Review for Accuracy

Internal Audit – Have a second person (safety manager, HR lead, or even an external consultant) review the numbers.
Cross‑Reference with 301 Reports – check that every incident listed on the 300‑A has a corresponding 301 incident report, if required.
Check for Exemptions – Some low‑hazard industries can claim an exemption; make sure you’re not posting when you’re not supposed to.

5. Post the Summary

Physical Posting – Print the form on standard letter‑size paper. Pin it up where all employees congregate.
Digital Posting – If you have a digital signage system, upload a PDF version. Make sure it’s accessible via the same login credentials all staff use.
Timestamp – Write the date you posted it on the board or in the file name. This helps prove compliance if OSHA shows up.

6. Keep the Original for Five Years

OSHA requires you to retain the original 300‑A, the 300 Log, and all 301 Incident Reports for at least five years after the end of the calendar year they cover. Store them in a fire‑proof cabinet or a secure cloud folder with proper backups.

Common Mistakes / What Most People Get Wrong

Mistake #1: Waiting Until February to Start

The deadline is February 2 of the year following the reporting year. That means you have just over a month after December 31 to gather, verify, and post. Procrastination is the number‑one cause of late postings.

Mistake #2: Posting the Wrong Year

It’s easy to slip a “2023” form onto a 2024 board when you’re juggling multiple years. Always double‑check the header on the form; the year should reflect the previous calendar year. That's the part that actually makes a difference.

Mistake #3: Forgetting to Include All Recordable Cases

Some employers only count cases that resulted in days away, ignoring medical‑only cases that still meet OSHA’s definition. The 300‑A must capture all recordable incidents, not just the severe ones.

Mistake #4: Posting in a “Hard‑to‑See” Spot

A bulletin board behind the break‑room fridge? In practice, not visible enough. OSHA expects a location where any employee can read it without hunting. If you’re unsure, ask a frontline worker where they’d look.

Mistake #5: Ignoring State‑Specific Requirements

A few states (California, Michigan, Washington, etc.Think about it: ) have their own OSHA‑equivalent agencies with stricter posting rules. If you operate in those states, you may need to post additional forms or meet earlier deadlines.

Practical Tips / What Actually Works

Set a Calendar Reminder – Put a recurring “OSHA 300‑A Deadline” event on your work calendar for January 15 each year. Gives you a two‑week buffer.
Automate the Export – Most EHS software can schedule a monthly export of the 300 Log. Use it to keep a running total so you’re not starting from scratch in January.
Create a One‑Page Checklist – Something like: 1) Pull data, 2) Verify recordables, 3) Tally, 4) Review, 5) Print, 6) Post, 7) Archive. Stick it on the safety manager’s desk.
Involve Employees – Let a union rep or employee safety committee member sign off on the posted summary. It builds trust and adds an extra layer of verification.
Use a Template – Save a blank 300‑A PDF with your company header pre‑filled. When it’s time, you only need to paste the numbers. No re‑typing errors.
Audit Your Posting Spot – Walk the floor during a shift and ask, “If you needed to see this, where would you look?” Adjust accordingly.

FAQ

Q: What if I miss the February 2 deadline?
A: File the summary as soon as possible and note the late filing date. OSHA may issue a citation, but showing prompt corrective action can mitigate penalties.

For more on this topic, read our article on two good measures of safety and health program effectiveness are or check out osha requirement for first aid kits.

Q: Do I need to post the summary if my company is exempt?
A: No, exempt employers don’t have to post the 300‑A. On the flip side, you still need to keep the 300 Log and 301 reports for five years in case the exemption status changes.

Q: Can I post the summary electronically only?
A: Yes, as long as the electronic version is accessible to all employees during their work shift. Many companies use a shared drive or intranet portal with read‑only access.

Q: How do I handle multiple work sites?
A: Each site with 250+ employees or a high‑hazard classification must post its own 300‑A. If you have a single corporate 300‑A covering multiple locations, you still need to post it at each site.

Q: What counts as a “visible location”?
A: Anywhere employees can see it without special permission—break rooms, near time clocks, locker rooms, or a digital screen in the main hallway. The key is that it’s not hidden behind a manager’s office door.

That’s the whole story, stripped of legalese and packed with the practical steps you can actually follow. The short version is: pull the data early, double‑check the numbers, post the form by February 2 in a spot everyone can see, and keep the records for five years. Do that, and you’ll stay on the right side of OSHA without pulling an all‑nighter in January.

Now go ahead—mark that calendar, set that reminder, and let the annual summary be one less thing you worry about each year. Happy posting!

Going the Extra Mile: Tips to Streamline Your Annual 300‑A Process

Automate Data Pulls – Most modern EHS platforms can generate a CSV of the 300 Log with a single click. Save that file in a shared folder labeled “2024 → 300A prep” so the safety team can import it directly into the summary template.
Create a Visual Summary Board – Design a small poster that shows the three key metrics (total recordables, DART rate, and total hours worked) as simple bar charts. Post it next to the 300‑A so employees can instantly grasp the safety performance snapshot.
Schedule a Pre‑Posting Review Meeting – Set a 30‑minute huddle with the safety manager, HR lead, and a union representative. Use the checklist you already have, but add a “data source verification” step: confirm that the numbers match the source log before any signatures are applied.
take advantage of a Mobile Check‑In – If you have a tablet on the shop floor, let the safety committee scan a QR code on the posted 300‑A. The scan logs who viewed it and when, providing an easy audit trail should OSHA request proof of accessibility.
Document the Posting Location – Take a dated photo of each posting spot (break room, time‑clock area, digital board, etc.) and store it in your compliance folder. This visual record helps demonstrate that the summary was visible throughout the entire year.

Quick‑Reference Year‑End Checklist (One‑Page)

Data Extraction – Export the 300 Log from your EHS software; save as CSV.
Number Verification – Cross‑check recordable counts against the source log; note any discrepancies.
Template Preparation – Open the pre‑filled 300‑A PDF; paste the verified totals.
Internal Sign‑off – Have safety manager, HR representative, and a union rep sign the document.
Posting Execution – Place printed or digital copies in all approved locations; capture photos.
Employee Communication – Send a brief email or post a notice on the intranet reminding staff of the posting and inviting questions.
Archive Creation – Store the signed 300‑A, the source CSV, and supporting documentation in your compliance archive for at least five years.

Common Pitfalls to Avoid

Assuming Exemption Applies Year‑Round – Exemption status can change; always verify the current year’s criteria before skipping the posting requirement.
Relying on Memory for Hours Worked – Use the system‑generated total hours rather than estimating; even a small variance can affect the DART rate calculation.
Neglecting to Update the Company Header – A generic template may look unprofessional and could raise questions during an audit.
Posting Only Digitally in a Hard‑to‑Access Folder – Ensure the electronic file is opened with read‑only permissions on a network drive that every employee can reach without a VPN.
Skipping the “Where Would You Look?” Walk‑through – The physical audit helps catch hidden postings that employees might miss, reducing the risk of citations.

Final Thought

By embedding automation, visual aids, and a structured review into your annual workflow, the 300‑A posting becomes a routine checkpoint rather than a last‑minute scramble. The goal isn’t just to meet the February 2 deadline—it’s to demonstrate a culture of transparency, safety, and continuous improvement that OSHA rewards

Integrating tablet technology into your safety protocols not only streamlines data collection but also strengthens your organization’s commitment to regulatory compliance. Pairing this digital scan with timely photo documentation of postings ensures that every location is accounted for, reinforcing visibility across the shop floor. Here's the thing — by leveraging the QR code scanning feature, you create a seamless audit trail that captures who accessed the information, when, and under what circumstances. Complementing these steps with a thorough post‑implementation sign‑off and a clear internal communication strategy further solidifies trust with oversight bodies.

Maintaining a consistent checklist and addressing common pitfalls—such as outdated exemption assumptions or inconsistent hours tracking—keeps your program strong and future‑proof. This proactive approach not only simplifies reporting but also positions your company as a leader in safety culture, ready to meet even the most stringent expectations.

To keep it short, these coordinated actions transform a simple checklist into a powerful compliance asset, supporting both operational efficiency and regulatory confidence. Conclude by recognizing that such diligence is the cornerstone of lasting safety excellence.