Shopping for OSHA recordkeeping software has a strange property: the thing you are buying is a way to keep a legal record, and the regulation that defines that record — 29 CFR Part 1904 — says nothing at all about software. It does not name a format, does not certify a vendor, and does not care whether your 300 Log lives on paper, in Excel, or in a database. It cares whether the record is complete, correct, produced on time, and defensible five years from now.
That turns out to be the most useful thing to know before you compare products, because it means the regulation itself is the specification. Every duty in Part 1904 — decide recordability, keep three forms in agreement, hit six different clocks, submit the right data to OSHA, keep everything for five years and update it — is a concrete test any tool either passes or fails. This guide turns those duties into a buying checklist, and then answers the question most vendor pages avoid: when is a spreadsheet, or OSHA's own free forms, genuinely enough?
First: Confirm You Have the Obligation at All
Software cannot help with a duty you don't have, and a surprising number of small employers are shopping for something the rule does not require of them. Two exemptions in Subpart B decide it:
- Size. Under 1904.1, a company that had 10 or fewer employees at all times during the last calendar year does not have to keep the 300 Log, 300A, or 301 forms unless OSHA or BLS asks in writing. The count is company-wide, at peak — not per site.
- Industry. Under 1904.2, establishments in the low-hazard industries listed in Appendix A to Subpart B are partially exempt regardless of size.
Both exemptions cover recordkeeping only. Even an exempt employer must still report a fatality within 8 hours and an in-patient hospitalization, amputation, or loss of an eye within 24 hours under 1904.39. If you are near either line, the exemption walkthrough resolves it, and the free ITA Submission Checker will tell you which electronic-submission tier, if any, applies to your headcount and NAICS code. Once you know the obligation is real, keep reading.
There Is No Such Thing as "OSHA-Approved" Software
Start any product evaluation by discarding one phrase. In an interpretation letter dated April 29, 2025 — written to a software vendor asking exactly this question — OSHA said it plainly: "OSHA does not approve, endorse, recommend or certify any product or process." What the letter did confirm is the standard software has to meet: forms generated by software are acceptable if they satisfy the equivalent-form rules of 1904.29 and 1904.32, and "employers may maintain equivalent forms, in any file format (e.g. Excel, CSV) provided that the requirements in paragraph 1904.29(b)(4) are met." A substitute 300A must additionally carry the executive certification and the employee-access and penalty statements from the official form.
So compliance is a property of your records, not of the vendor's brand. Any product claiming to be "OSHA-approved" or "OSHA-certified" is misstating how the rule works — and that tells you something about how carefully the rest of its claims were written. (The legality question itself — may you keep the log electronically at all — has a longer treatment in our post on the equivalent-form and e-storage rules; the answer is an unambiguous yes.)
The Buying Checklist: Part 1904 as a Feature List
Here is the obligation surface, duty by duty, phrased as the question to ask of any tool — including the spreadsheet you already have.
1. Does it make the recordability decision reproducible — and documented?
The whole system starts with one determination: is this case recordable? The test runs through 1904.4 to 1904.7 — work-relatedness (with the nine exceptions in 1904.5(b)(2)), the new-case rules of 1904.6, and the general recording criteria of 1904.7 (death, days away, restricted work or transfer, medical treatment beyond first aid, loss of consciousness, or a significant diagnosed injury or illness). It has to be finished fast: 1904.29(b)(3) gives you seven calendar days from learning that a recordable case occurred to enter it on the 300 Log and 301. The full decision tree is the deepest page on this site for a reason.
The buying question is not "does the software have a wizard." It is: when an inspector or an attorney asks why case 14 was recorded and case 15 was not, can you show the reasoning? A good tool records the answers to each criterion, cites the subsection the determination hinged on, and reaches the same conclusion every time the same facts go in.
Why AI does not belong in the record of authority
Some newer recordkeeping tools now advertise AI-powered recordability classification. Treat that as a red flag, not a feature. A recordability determination is a legal finding you will have to defend — under 1904.35 to your employees, under 1904.40 to a government representative within four business hours, and potentially years later in a citation contest. It needs to be reproducible (the same facts always yield the same answer) and explainable (you can name the criterion that decided it). A probabilistic model that gets it right most of the time provides neither property, and "the software thought it was probably first aid" is not a defense OSHA's citation policy recognizes. The rule's criteria are deterministic; the tool that applies them should be too. Use AI to draft the incident narrative if you like — never to decide what goes in the log.
2. Does it keep the three forms consistent by construction?
Part 1904 is three documents that must agree: the 300 Log (one line per case), the 301 Incident Report (one detailed form per case, also due within seven days), and the 300A Annual Summary (year-end totals that must equal the sum of the log). Our guide to filling out the 300 Log covers the columns; the buying question is whether the tool derives all three from one incident record or makes you enter the same case three times.
Three sub-rules separate real recordkeeping software from a form-filler:
- Privacy cases. 1904.29(b)(7) lists the six situations in which you must write "privacy case" instead of a name on the 300 Log — and the list is exhaustive. You must then keep a separate, confidential list matching case numbers to names, available for updates and government requests. Software should enforce the name suppression on the 300 Log and everything derived from it (the printed log, the ITA case file) while keeping the confidential list — and the 301, which legitimately carries the name — intact. Details in the privacy-case post.
- Day counts. Columns K and L accrue in calendar days, capped at 180 per 1904.7(b)(3)(vii), and the most-serious-outcome classification must be updated as a case evolves. The tool should keep counting after the initial entry and re-classify without a manual re-key. See how to count days away and restricted days.
- 300A reconciliation. Under 1904.32(a)(1) you must review the log at year-end "as extensively as necessary to make sure that they are complete and correct" before creating the summary. Totals that come from the log by construction make that review a check, not a reconstruction.
3. Does it run the deadline clocks — all six of them?
Recordkeeping is a calendar problem as much as a classification problem. Any tool worth paying for should track, and ideally remind you of, every clock the rule sets:
| Clock | Requirement | Where |
|---|---|---|
| 7 calendar days | Enter each recordable case on the 300 Log and 301 after learning of it | 1904.29(b)(3) |
| February 1 – April 30 | Post the certified 300A at each establishment | 1904.32(b)(6) |
| March 2 | Submit required data to OSHA's Injury Tracking Application | 1904.41(c) |
| 8 hours / 24 hours | Report a fatality / in-patient hospitalization, amputation, or loss of an eye | 1904.39(a) |
| End of next business day | Give an employee or representative a copy of the 300 Log on request | 1904.35(b)(2)(iii) |
| 4 business hours | Provide records to an authorized government representative | 1904.40(a) |
Two of these are commonly missed by tools built around the annual summary alone. The posting duty requires a physical copy on the wall — electronic posting does not satisfy it — certified by a company executive as 1904.32(b)(4) defines the term (an owner, a corporate officer, the highest-ranking official at the establishment, or that person's immediate supervisor). And the access duties in 1904.35 and 1904.40 mean "can I produce a clean copy of the form right now" is a live compliance test, not a convenience feature.
4. Does it produce the ITA submission — the right data, in the right format?
Electronic recordkeeping (1904.29) and electronic submission (1904.41) are independent duties. Which one applies depends on headcount, counted at peak — "at any time during the previous calendar year," including part-time, seasonal, and temporary workers — and on industry:
- 250 or more employees: submit 300A data every year.
- 100 or more employees in an Appendix B (Subpart E) high-hazard industry: submit 300A, 300, and 301 data — the case-detail files, not just the summary.
- 20 to 249 employees in an Appendix A designated industry: submit 300A data.
OSHA's Injury Tracking Application accepts data three ways: keyed into a web form by hand, uploaded as a CSV file, or transmitted through an API from "automated recordkeeping systems." For a single small establishment, hand entry of the 300A's dozen numbers is entirely workable. The value of software shows up when you have several establishments, when you owe the 300/301 case-detail files (24 columns per case, in OSHA's published spec, with coded outcome and injury types), or when the summary numbers were re-keyed from a spreadsheet and don't quite match the log behind them. The ITA walkthrough covers the portal itself; the free ITA CSV Validator will check any upload file — from any tool — against the spec before you submit. Note that no vendor "submits to OSHA for you" in the sense of replacing the ITA: software generates the file, and you upload it to OSHA's system.
5. Does it keep an audit trail across the five-year retention window?
1904.33(a) requires you to keep the 300 Log, the privacy-case list, the 300A, and the 301 forms for five years following the end of the calendar year they cover — and 1904.33(b)(1) is the part people forget: during that window you must update the stored 300 Log with newly discovered recordable cases and with changes in classification of cases already recorded. (Updating the 300A and 301 is optional under (b)(2)–(3).) A tool that treats a closed year as read-only cannot comply; a tool that lets anyone silently overwrite a closed year cannot be defended. The property you want is an append-only history: who changed what, when, and from what — the record of the record. The retention post walks the update-the-log duty in detail.
6. Does it keep one log per establishment?
Under 1904.30 you keep a separate 300 Log for each establishment expected to operate a year or longer, and the 300A is posted at each one. If you have — or expect to have — more than one location, the tool needs per-establishment logs, per-establishment summaries, and a way to see them together. Multi-establishment recordkeeping is where single-workbook spreadsheets first start to strain.
7. Can you get your history in — and your records out?
Two portability questions decide whether a tool is a system or a trap. In: you likely have prior years in a spreadsheet or on paper; can the tool import them with validation, so the five-year window is complete inside one system? Out: the four-business-hour and next-business-day clocks above mean you must be able to produce official-layout Forms 300, 300A, and 301 on demand — as printable PDFs, not screenshots — and export your data if you ever leave. If a vendor cannot show you a full export, assume the records are the vendor's, not yours.
When a Spreadsheet Is Genuinely Enough
Vendors rarely say this, so we will: for a meaningful share of small employers, OSHA's own free forms package plus a disciplined spreadsheet is a legally sufficient recordkeeping system. OSHA publishes Forms 300, 300A, and 301 as fillable PDFs at no cost, and its forms page states directly that equivalent forms "may be maintained in any file format (e.g. Excel, CSV)." A spreadsheet is a legitimate equivalent form on the day you build it.
The profile where it works is specific, and worth being honest about:
- One establishment, so there is one log and one posting.
- A handful of recordable cases a year, so day counts and classifications can be tracked by hand without drifting.
- No 1904.41 submission duty (under 20 employees, or a non-designated industry), or a duty that only requires the 300A's summary numbers, which can be keyed into the ITA web form directly.
- One person who knows the counting rules and will still be there next January.
- A calendar somebody actually owns for February 1 and March 2.
If that describes you, the money is better spent elsewhere, and the free tools on this site — the Recordability Checker for the determination and the Rate Calculator for TRIR/DART — cover the two hardest parts without a subscription.
Where the Spreadsheet Stops
The failure modes are not exotic; they are the exact places where the checklist above needs enforcement rather than storage. Cases entered in seven days but never updated when the outcome worsened. Day counts typed once and frozen. A 300A whose totals no longer equal the log because a row was inserted outside the sum range. A privacy case whose name leaked into the CSV. Two establishments in one workbook. The 300/301 case-detail files for a 100+-employee high-hazard establishment, hand-assembled into 24 columns. And the most common one: the person who knew the rules left, and the spreadsheet kept accepting whatever the next person typed. Our electronic-recordkeeping post walks these one by one; the five citation-generating mistakes shows what each one looks like from the inspector's side of the table, where a recordkeeping citation runs up to $16,550 per violation.
The tell is turnover, multiplicity, or a submission duty. When any of the three arrives, "electronic recordkeeping that enforces the rules" stops being a nice-to-have.
Red Flags in a Vendor Pitch
A short list of claims that should end an evaluation, or at least prompt a hard question:
- "OSHA-approved" or "OSHA-certified." No such status exists; OSHA said so in writing.
- AI decides recordability. The record of authority needs a deterministic, explainable determination (see the callout above).
- "We submit to OSHA for you." The ITA is OSHA's system; software prepares the file. Ask what happens if the upload is rejected.
- The 300A is a separate data-entry screen. If totals are typed rather than derived, the year-end review is a reconstruction.
- One log, many sites. Per-establishment logs are the rule, not an enterprise feature.
- No full export, no printable official-layout forms. Your four-business-hour clock, their roadmap.
- A trial that requires a card, or a demo that requires a sales call. Neither is a compliance issue — but a product built for a safety manager with a 4:55 p.m. question should let you see it work first.
Frequently Asked Questions
Do I need OSHA recordkeeping software if I have 15 employees?
Not necessarily. At 11 or more employees you are past the 1904.1 size exemption and must keep the forms unless your industry is on the Appendix A partial-exemption list — but the rule is indifferent to how. One establishment, few cases, one knowledgeable person: a spreadsheet passes. Turnover, multiple sites, or a 1904.41 submission duty are what change the answer.
Is there any OSHA-approved recordkeeping software?
No. OSHA's April 29, 2025 interpretation letter states that the agency "does not approve, endorse, recommend or certify any product or process." Software-generated forms are acceptable when they meet the equivalent-form requirements of 1904.29(b)(4) and 1904.32.
Does using software satisfy the March 2 electronic submission?
No. Keeping records electronically (1904.29) and submitting data to the ITA (1904.41) are separate duties. Software can generate the CSV or, for automated systems, transmit through OSHA's API — but the submission is made to OSHA's Injury Tracking Application, and only establishments meeting the 1904.41 thresholds must make it.
Can I switch from a spreadsheet to software in the middle of a year?
Yes. The 300 Log is kept by calendar year, and 1904.29(b)(4) only requires that the resulting records contain the same information and be as readable and understandable as the official forms. Bring the current year's cases (and ideally the prior four years, to keep the retention window intact) into the new system with validation, and keep the old spreadsheet as part of the five-year record until it is fully migrated.
If I keep everything electronically, do I still have to print anything?
Yes — at least once a year. The certified 300A must be physically posted at each establishment from February 1 to April 30; electronic posting does not satisfy 1904.32(b)(6). Paper is also the default for employee access requests unless the requester agrees to an electronic copy.
Buy the Enforcement, Not the Form
The forms are free. What you are actually paying for, if you pay for anything, is enforcement of the rules between the moments you are paying attention: the determination that comes out the same way every time and shows its work, the day count that keeps accruing, the classification change that flows into the summary, the privacy case whose name never leaks, the calendar that fires before February 1 and March 2, and the history that proves what the record said on any given day. Measure every product — and your spreadsheet — against that list, and the decision usually makes itself.
That list is what LogStead is built to be. The recordability wizard walks the 1904.4–1904.7 criteria in plain English and cites the deciding subsection in the result — deterministically, with no AI in the determination; a single incident record produces the 300 Log line, the 301, and the 300A totals, with privacy-case names suppressed on the log and its exports; the deadline calendar tracks the 7-day, February 1, March 2, and 1904.39 clocks; and every change lands in an append-only audit trail across the five-year window. Existing logs import from CSV with row-by-row validation, official-layout PDFs print on demand, and the ITA export — including the 300/301 case-detail file — is ready ahead of March 2. You can see all of it working with sample data in the live demo, no account required.