Track all three OSHA 300A obligations, at every site

1. What is the OSHA Form 300A?

Form 300A is the annual summary of the injury and illness log a covered employer keeps through the year. It carries the column totals from the log, plus the establishment's name and address, the calendar year, the annual average number of employees, and the total hours they worked. It is a one-page document that says, in effect: here is what happened at this workplace last year. What makes it worth its own tracking is not the form — it's that three separate obligations attach to it, each owed to a different party, and each complete on its own terms. Remindax helps you track when each one falls due at each establishment and reminds you before it does; it doesn't keep your log, certify the summary, post anything, or submit data to OSHA, and it holds no injury or health information.

Because these dates land on the same people who are already carrying training renewals, inspections, and permits, they belong in the same register as everything else the site owes — which is what health and safety tracking is for, and why the annual summary tends to sit next to the rest of a compliance calendar rather than in a folder of its own.

1.1 One record, three audiences

• →Certification — the audience is you. A company executive examines the log and certifies that the summary is correct and complete. Nobody outside the company sees this happen. It's the gate the record passes through before it's allowed to be shown to anyone.
• →Posting — the audience is your own employees. A copy goes up in each establishment, in a conspicuous place where notices to employees are customarily posted, and stays there from February 1 through April 30.
• →Electronic submission — the audience is OSHA. Establishments over a size threshold, and those in designated industries, submit the data through the Injury Tracking Application by March 2. It is a different act, in a different medium, to a different reader.
• →Coverage is settled per establishment. Whether a site keeps records at all, and whether it has to submit electronically, turns on facts about that site — its headcount, its industry classification — not on facts about the company above it.

Recordkeeping rules are set by OSHA and, in State Plan states, by the state's own program, and they change. Confirm what applies to your establishments at the official sources in section 11. This is general information, not EHS or legal advice.

2. When is the OSHA 300A due?

The first line of that box is worth reading carefully, because it is the part most often stated wrongly. Employers go looking for an OSHA 300A certification deadline somewhere in January, and the regulation doesn't contain one — there is no date a signature has to beat. Certification is a precondition: the summary must be certified, and it must be posted by February 1, so the signature has to happen first. That sounds like a technicality until you notice what it does to the failure mode. A deadline announces itself. A precondition doesn't — it just quietly makes everything downstream of it defective. A summary that goes up on the wall on time, in the right place, and stays there the full three months is still a violation if the executive never certified it, and nothing about the wall will tell you.

The 300A electronic submission sits inside that same window and has nothing to do with it. It is not a copy of the posting sent onward, and it is not triggered by the posting having happened. It's an independent obligation with its own coverage test, and an establishment can owe the posting and not the submission, which is the ordinary case for smaller sites. The reverse never happens, and that asymmetry is exactly what makes the mistake so easy: the site did the visible thing, on time, and the invisible thing was never on anyone's list.

3. Why tracking the 300A obligations matters

The OSHA 300A posting deadline is the one most employers already know. The other two are the ones that produce citations — and four properties combine to turn an apparently trivial annual task into a reliable source of them:

The second point deserves more than a card, because the split it describes is genuinely counter-intuitive. Most compliance work has a single beneficiary, and it is usually the regulator: you renew a permit for the authority that issued it, you keep a certificate for the auditor who will ask. The posting obligation is one of the very few in a business's whole calendar whose intended reader is the workforce itself. OSHA enforces it, but OSHA is not who it's for. The point of putting last year's totals where employees pass is that the people who worked through those injuries get to see the count. Once you see it that way, the reason it can't double as an electronic submission stops being a technicality and becomes obvious: a sheet on a wall in one building was never going to reach a federal database, and a federal database was never going to reach the people on the floor.

This is the same structural mistake that a device's calibration and its sealing certificate produce in a retail setting — two obligations about the same object where holding one current does not satisfy the other — except that here the two obligations concern not just the same object but the identical piece of information, which is why the substitution feels so much more reasonable when someone makes it.

4. Who needs to track these deadlines

Any employer whose establishments aren't partially exempt carries this calendar — and the more sites there are, the less likely it is that one person can see all of them:

Manufacturers & industrial employers

Usually the full set at every plant — certification, a posting window on each site's notice board, and an electronic submission for the establishments over the threshold.

Learn More

Construction & multi-site contractors

The hardest version of the posting problem: a three-month window that has to hold across trailers and offices, on sites whose notice boards move with the work.

Learn More

Warehousing, healthcare & retail

Sectors where designated industry classifications pull sites into electronic submission at lower headcounts than employers expect — a coverage question, not a size question.

HR, EHS & safety coordinators

The people who actually own the calendar, and who need the executive chased for a signature before the window opens rather than after somebody notices the wall is bare.

Learn More

Multi-establishment employers

Where the real risk lives: a set of sites with different answers to the same question, and no single company-level status that tells you which is which.

Learn More

HR teams carrying annual filings

For whom this is one of several employer obligations landing in the first quarter, each with its own audience, its own medium, and its own way of being quietly missed.

Learn More

What connects them is a division of labor that almost guarantees a gap. The person who maintains the log is rarely the executive who certifies it, the executive is never the person who walks to the notice board, and none of the three is usually the person with an Injury Tracking Application account. Four hands, one record, and no single place where all of it is visible — which is the argument for keeping the dates somewhere shared. For the wider view of every safety credential and recurring obligation a site carries, see certification tracking software.

5. What happens when a 300A deadline is missed

Because there are three obligations, there are three distinct ways to be cited, and they fail in noticeably different ways.

A missing certification is the quietest of the three, and the only one that is invisible from every angle. The summary looks finished. It is on the wall, on time, in the right place, with correct numbers on it. What's absent is a signature from a company executive attesting that they examined the log and believe the summary is correct and complete — and because the defect is in the record's provenance rather than its content, no walk-through of the building will surface it. It surfaces when someone asks who signed, which is usually an inspector.

A posting failure is the opposite: entirely visible, and visible to everyone. It also has the widest attack surface, because it can happen at four different moments — the summary never goes up, it goes up late, it comes down before April 30, or it goes up somewhere employees don't actually pass. The last two are the ones that catch conscientious employers, since both begin with the task being done correctly. And there's an aggravating feature that no amount of good faith softens: the window is February 1 to April 30 every single year, for everyone, forever. Nothing about it is announced, moved, or conditional. An inspector standing in front of an empty notice board in March isn't looking at a scheduling accident; they're looking at a lapse that a calendar reminder would have prevented. That's the same quality that makes a registration deadline shared by an entire industry unforgiving — there is no version of the story in which the date was unclear.

A missed electronic submission is different again, because nothing in the physical world changes when it happens. March 2 passes, the establishment carries on, the summary is still on the wall doing its job, and the only record of the failure sits in a federal system nobody at the site logs into. This is the failure the whole page is built around, because it is the one employers walk into while believing they complied: the visible obligation was met, thoroughly and on time, and it was never capable of satisfying the invisible one. Worse, the data OSHA collects this way feeds its enforcement targeting, so an establishment that doesn't appear is conspicuous by a different route than the one it was worried about.

None of these is catastrophic in isolation. They are ordinary citations, and an employer can absorb one. What makes them worth systematic attention is that they multiply cleanly — across establishments in a single year, and across years at a single establishment — and every one of them is avoidable by a date in a calendar. Holding the certification, the posting window, and the submission for each site is what keeps a simple annual record from becoming a stack of findings.

6. How Remindax keeps every site on all three

The shape of the problem is a handful of recurring dates, owned by different people, that only mean something together and are reviewed together once a year at best. Four pieces address exactly that:

7. Why spreadsheets fail here

A spreadsheet models this obligation wrongly at the most basic level, and it does it in a way that feels like good record-keeping. It gives each establishment a row and the year a column, and somebody writes done in the cell. But done is not a state this obligation has. Three separate things were owed, to three different audiences, and the cell collapses them into a single claim that cannot distinguish the site that certified, posted and submitted from the site that only posted. The one piece of information you would actually want — which of the three is outstanding, where — is precisely what the format destroys.

The window compounds it. A row marked complete on February 1 is a claim about February 1, and it goes on asserting itself confidently through March and April while the summary may or may not still be on the wall. A spreadsheet has no way to represent an obligation that stays open, so it represents the moment it began and calls that the whole thing. And because the dates are identical every year, last year's file gets copied forward with a new tab, which quietly carries forward last year's coverage answers to a set of sites whose headcounts have since changed.

An automated register holds each establishment's obligations as separate items with separate dates, keeps the posting open until it actually closes, and reminds the executive, the site, and whoever holds the submission account at the point each still has time to act — which is the only version of this that survives contact with a company that has more than one address.

8. Key takeaways

• ✓One record, three audiences: a company executive certifies it, employees read it on the wall, and OSHA receives it electronically — three deliveries of identical information.
• ✓Certification is a precondition rather than a dated deadline — it has to happen before the summary is posted, and an uncertified summary is defective while looking perfect.
• ✓February 1 to April 30 is a duration, not a due date: the obligation is to keep it up, so it can be met on day one and failed in the middle.
• ✓Posting and electronic submission are independent — covered establishments submit by March 2, and doing the visible one never satisfies the invisible one.
• ✓Coverage is decided per establishment and can change as a site's headcount or classification changes, so it's worth re-asking each year rather than inheriting last year's answer.