<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[LogStead Blog - Medium]]></title>
        <description><![CDATA[OSHA 300 log management, a recordability wizard, and injury and illness recordkeeping for small and mid-size employers. - Medium]]></description>
        <link>https://medium.com/logstead-blog?source=rss----645c4801a777---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>LogStead Blog - Medium</title>
            <link>https://medium.com/logstead-blog?source=rss----645c4801a777---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:15:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/logstead-blog" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[OSHA Recordkeeping Requirements for Small Employers]]></title>
            <link>https://medium.com/logstead-blog/osha-recordkeeping-requirements-for-small-employers-cebec65e6cb8?source=rss----645c4801a777---4</link>
            <guid isPermaLink="false">https://medium.com/p/cebec65e6cb8</guid>
            <category><![CDATA[osha]]></category>
            <category><![CDATA[workplace-safety]]></category>
            <category><![CDATA[small-business]]></category>
            <dc:creator><![CDATA[Ervin Amaya]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 14:29:52 GMT</pubDate>
            <atom:updated>2026-11-16T14:29:52.127Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LMGuJEfq9YNy1075" /></figure><p>OSHA’s injury and illness recordkeeping rule, 29 CFR Part 1904, is short enough to read in an afternoon and detailed enough to trip up almost everyone who tries. Its purpose, in its own words, is “to require employers to record and report work-related fatalities, injuries, and illnesses” (1904.0). What makes it hard for a small employer is not any single rule. It is that the obligations are spread across a dozen sections, run on different clocks, and apply to different employers. It is easy to get the log right and miss the posting date, or to be exempt from the log and still owe OSHA a phone call.</p><p>This page is the map. It lays out every Part 1904 requirement a small employer is likely to meet, in the order you meet them: whether you have to keep records at all, what goes on the log, the three forms, the yearly calendar, electronic submission, severe-injury reporting, retention and access, and what your employees are entitled to. Each section is short and links to the full guide for that topic. Where a paraphrase could mislead, the regulation’s own words are quoted.</p><h3>The Requirements at a Glance</h3><p>The rest of this guide takes them one at a time.</p><h3>Do You Have to Keep OSHA Records at All?</h3><p>Two partial exemptions decide whether routine recordkeeping applies to you. They are explained in full, with the industry list and a decision flow, in <a href="https://logstead.app/blog/do-you-need-to-keep-osha-300-log-recordkeeping-exemptions-small-employers">Do You Need to Keep an OSHA 300 Log?</a>. The short version:</p><p><strong>Size.</strong> “If your company had 10 or fewer employees at all times during the last calendar year, you do not need to keep OSHA injury and illness records unless OSHA or the Bureau of Labor Statistics informs you in writing that you must keep records under § 1904.41 or § 1904.42” (1904.1(a)(1)). Two details decide most cases. The count is company-wide: “The partial exemption for size is based on the number of employees in the entire company” (1904.1(b)(1)). And it is peak employment, not average (1904.1(b)(2)), so a company that had eleven people for two weeks last summer keeps records this year.</p><p><strong>Industry.</strong> An establishment classified in an industry group on the partially exempt list, Appendix A to Subpart B of Part 1904, does “not need to keep OSHA injury and illness records unless the government asks you to keep the records under § 1904.41 or § 1904.42” (1904.2(a)(1)), at any size. The test runs establishment by establishment: “some of the company’s establishments may be required to keep records, while others may be partially exempt” (1904.2(b)(1)). A company with an accounting office and a warehouse can owe a log for one and not the other.</p><p>If you are not exempt, everything below applies to each establishment that must keep records.</p><h3>What Goes on the Log</h3><p>Every employer that keeps records must record each fatality, injury, and illness that “Is work-related; and … Is a new case; and … Meets one or more of the general recording criteria of §1904.7 or the application to specific cases of §§1904.8 through 1904.12” (1904.4(a)). In practice that is three questions, asked in order:</p><ol><li><strong>Is it work-related?</strong> The starting point is yes: “Work-relatedness is presumed for injuries and illnesses resulting from events or exposures occurring in the work environment, unless an exception in §1904.5(b)(2) specifically applies” (1904.5(a)). The exceptions are specific and narrow. One covers an injury that is “solely the result of an employee eating, drinking, or preparing food or drink for personal consumption”, another an illness that “is the common cold or flu”.</li><li><strong>Is it a new case?</strong> It is, if the employee “has not previously experienced a recorded injury or illness of the same type that affects the same part of the body”, or had one but “recovered completely” before a workplace event or exposure brought the signs or symptoms back (1904.6(a)).</li><li><strong>Does it meet the recording criteria?</strong> A case is recordable if it results in “death, days away from work, restricted work or transfer to another job, medical treatment beyond first aid, or loss of consciousness”, or if it involves “a significant injury or illness diagnosed by a physician or other licensed health care professional” (1904.7(a)). A few kinds of case have their own rules instead: needlesticks and sharps (1904.8), medical removal (1904.9), hearing loss (1904.10), and tuberculosis (1904.11).</li></ol><p>The line people argue about most is medical treatment versus first aid. OSHA’s list of first-aid treatments is closed, so anything not on it counts as medical treatment, whoever provides it; the whole list is walked through in <a href="https://logstead.app/blog/first-aid-vs-medical-treatment-the-line-that-decides-recordability">First Aid vs. Medical Treatment</a>. The complete four-step decision, with the edge cases, is in <a href="https://logstead.app/blog/is-this-injury-osha-recordable">Is This Injury OSHA Recordable?</a>, and the free <a href="https://logstead.app/tools/recordability-checker">recordability checker</a> runs one case through it in a couple of minutes.</p><h3>The Three Forms, and What Each One Is For</h3><p>“You must use OSHA 300, 300-A, and 301 forms, or equivalent forms, for recordable injuries and illnesses” (1904.29(a)). Each has a different job.</p><ul><li><strong>The OSHA 300, the Log of Work-Related Injuries and Illnesses.</strong> One entry per recordable case, “a one or two line description for each recordable injury or illness” (1904.29(b)(1)), with its classification and day counts. It is a running document you keep all year. Column by column: <a href="https://logstead.app/blog/how-to-fill-out-osha-300-log">How to Fill Out the OSHA 300 Log</a>.</li><li><strong>The OSHA 301, the Injury and Illness Incident Report.</strong> The case file behind each line: “You must complete an OSHA 301 Incident Report form, or an equivalent form, for each recordable injury or illness entered on the OSHA 300 Log” (1904.29(b)(2)). Many employers use an insurance form that carries the same information (1904.29(b)(4)). See <a href="https://logstead.app/blog/osha-301-incident-report-completion-access-rules">the OSHA 301 guide</a>.</li><li><strong>The OSHA 300A, the Summary of Work-Related Injuries and Illnesses.</strong> The year’s column totals from the log, plus the establishment’s annual average number of employees and total hours worked (1904.32(b)(2)). OSHA’s worksheet for those two numbers is walked through in <a href="https://logstead.app/blog/how-to-calculate-average-number-of-employees-osha-300a">how to calculate the 300A average</a>. It is the only one of the three that goes on the wall, and every establishment that files with OSHA electronically each year submits its data. See <a href="https://logstead.app/blog/osha-300a-annual-summary">the 300A annual summary</a>. Its cases and hours are also the inputs to your <a href="https://logstead.app/blog/trir-dart-rates-explained-small-employers">TRIR and DART rates</a>.</li></ul><p><strong>Paper or electronic.</strong> An equivalent form “is one that has the same information, is as readable and understandable, and is completed using the same instructions as the OSHA form it replaces” (1904.29(b)(4)). Records can live on a computer “if the computer can produce equivalent forms when they are needed” (1904.29(b)(5)). The details, including the production clocks, are in <a href="https://logstead.app/blog/keep-osha-300-log-electronically-equivalent-forms-1904-29">Can You Keep Your OSHA 300 Log Electronically?</a></p><p><strong>Privacy cases.</strong> Six kinds of case keep the employee’s name off the log: an injury to an intimate body part or the reproductive system, an injury from a sexual assault, mental illness, HIV infection, hepatitis or tuberculosis, a contaminated needlestick or sharps cut, and other illnesses where the employee asks (1904.29(b)(7)). For these “you may not enter the employee’s name on the OSHA 300 Log. Instead, enter “privacy case””, and you keep a separate confidential list of the names (1904.29(b)(6)). See <a href="https://logstead.app/blog/osha-privacy-concern-cases-300-log-1904-29">Privacy Concern Cases</a>.</p><p><strong>One log per establishment.</strong> “You must keep a separate OSHA 300 Log for each establishment that is expected to be in operation for one year or longer” (1904.30(a)). Short-term sites can share one log (1904.30(b)(1)). Records can be kept centrally if information about each case reaches the central location within seven calendar days (1904.30(b)(2)(i)). Employees who work at several sites, or at none of yours, are linked to one establishment and recorded on its log (1904.30(b)(3)). See <a href="https://logstead.app/blog/multi-establishment-osha-recordkeeping-one-log-per-location">Multi-Establishment OSHA Recordkeeping</a>.</p><h3>The Recordkeeping Calendar</h3><p>One clock runs all year, and three dates close it out.</p><p><strong>All year: seven days.</strong> “You must enter each recordable injury or illness on the OSHA 300 Log and 301 Incident Report within seven (7) calendar days of receiving information that a recordable injury or illness has occurred” (1904.29(b)(3)). The clock starts when you learn of the case, not on the date of the injury.</p><p><strong>After December 31: close the year.</strong> “At the end of each calendar year, you must” do four things (1904.32(a)). “Review the OSHA 300 Log to verify that the entries are complete and accurate, and correct any deficiencies identified”; create the annual summary, the 300A; certify it; and post it. A year with no recordable cases still gets a summary: “if you had no recordable cases, enter zeros for each column total” (1904.32(b)(2)(i)).</p><p>The certification is not something anyone in the office can sign. It must come from a company executive: an owner (only in a sole proprietorship or partnership), an officer of the corporation, the highest-ranking company official working at the establishment, or that person’s immediate supervisor (1904.32(b)(4)). The executive certifies “that he or she has examined the OSHA 300 Log and that he or she reasonably believes, based on his or her knowledge of the process by which the information was recorded, that the annual summary is correct and complete” (1904.32(b)(3)).</p><p><strong>February 1 through April 30: post the 300A.</strong> “You must post the summary no later than February 1 of the year following the year covered by the records and keep the posting in place until April 30” (1904.32(b)(6)). It goes “in a conspicuous place or places where notices to employees are customarily posted”, and it must not be “altered, defaced or covered by other material” (1904.32(b)(5)).</p><p><strong>March 2: electronic submission,</strong> for the establishments the rule covers (next section).</p><p>For 2026 records, the calendar works out like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vjuSM3VgKYM5kuRp" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KWABff5Gggl-BvyS" /></figure><p>Enter each case on the 300 and 301</p><p>Within 7 calendar days, all year</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ae1CSJXsLTXejx9D" /></figure><p>Review, total, and certify the 300A</p><p>After December 31, 2026</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f7vJPqH05gVtsa7-" /></figure><p>Post the 300A</p><p>February 1 to April 30, 2027</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f5uGfIWT80fuAcBq" /></figure><p>Submit through the ITA, if covered</p><p>By March 2, 2027</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XaV_ImT8Ud6O7ZGz" /></figure><p>Keep the 300, 300A, 301s, and privacy list</p><p>Through December 31, 2031</p><h3>Electronic Submission: Who Files With OSHA Each Year</h3><p>Only three categories of establishment routinely submit their data to OSHA’s Injury Tracking Application (ITA). Each is measured by the establishment’s employees at any time during the previous calendar year:</p><ul><li><strong>20 to 249 employees in an industry on Appendix A to Subpart E:</strong> information from the Form 300A (1904.41(a)(1)(i)).</li><li><strong>250 or more employees in any industry that must keep records:</strong> information from the Form 300A (1904.41(a)(1)(ii)).</li><li><strong>100 or more employees in an industry on Appendix B to Subpart E:</strong> information from Forms 300 and 301, the case-by-case data, as well as the 300A (1904.41(a)(2)).</li></ul><p>Everyone counts toward those numbers: “each individual employed in the establishment at any time during the calendar year counts as one employee, including full-time, part-time, seasonal, and temporary workers” (1904.41(b)(2)). The free <a href="https://logstead.app/tools/ita-checker">ITA submission checker</a> applies all three tests to your headcount and NAICS code.</p><p>The deadline is “March 2 of the year after the calendar year covered by the form(s) (for example, by March 2, 2024, for the forms covering 2023)” (1904.41(c)). A covered establishment submits even in a year with no cases. OSHA’s ITA FAQ says such establishments “must report their Form 300A data even if they experienced no recordable injuries or illnesses”. If you miss March 2, the same FAQ says “the ITA will accept your injury and illness data through the end of the calendar year (December 31)”: late, but still required.</p><p>Two more rules complete the picture. The requirements “apply to employers located in State Plan States” (1904.41(b)(7)). And any employer can be asked outside the routine categories: “Upon notification, you must electronically submit the requested information from your part 1904 records” (1904.41(a)(3)). The step-by-step walkthrough of the portal itself is in <a href="https://logstead.app/blog/how-to-submit-osha-data-electronically-ita-portal">How to Submit Your OSHA Data Electronically</a>. The submitted 300A data is also what OSHA’s Site-Specific Targeting program uses to choose establishments for inspection; see <a href="https://logstead.app/blog/how-osha-picks-who-to-inspect-site-specific-targeting-program-explained">How OSHA Picks Who to Inspect</a>.</p><h3>Recording Is Not Reporting: The 8-Hour and 24-Hour Rules</h3><p>The log is paperwork you keep. A severe-injury report is something you make to OSHA, by phone, in person, or online, on a clock measured in hours. It applies to every employer covered by the OSH Act, including employers exempt from the log.</p><ul><li>“Within eight (8) hours after the death of any employee as a result of a work-related incident, you must report the fatality” to OSHA (1904.39(a)(1)).</li><li>“Within twenty-four (24) hours after the in-patient hospitalization of one or more employees or an employee’s amputation or an employee’s loss of an eye, as a result of a work-related incident, you must report the in-patient hospitalization, amputation, or loss of an eye to OSHA” (1904.39(a)(2)).</li></ul><p>Which events count is narrower than the headline:</p><ul><li><strong>Timing.</strong> “You must only report a fatality to OSHA if the fatality occurs within thirty (30) days of the work-related incident.” A hospitalization, amputation, or loss of an eye is reported only “if it occurs within twenty-four (24) hours of the work-related incident” (1904.39(b)(6)).</li><li><strong>Hospitalization.</strong> An in-patient hospitalization is “a formal admission to the in-patient service of a hospital or clinic for care or treatment” (1904.39(b)(9)). One “that involves only observation or diagnostic testing” is not reported (1904.39(b)(10)).</li><li><strong>Transport.</strong> A motor-vehicle accident on a public street or highway outside a construction work zone, and an event on a commercial or public transportation system, are not reported. They are still recorded if you keep records (1904.39(b)(3)-(4)).</li></ul><p>If you learn of the event, or that it was work-related, only later, the 8- or 24-hour clock runs from when you or your agent learn of it (1904.39(b)(7)-(8)). You report to the nearest OSHA Area Office by phone or in person, to 1–800–321-OSHA (1–800–321–6742), or through the online reporting application on osha.gov (1904.39(a)(3)). If the Area Office is closed, a voicemail, fax, or email does not count (1904.39(b)(1)). The full rules, with examples: <a href="https://logstead.app/blog/osha-severe-injury-reporting-1904-39-8-24-hour-rules">OSHA’s 8-Hour and 24-Hour Reporting Rules, Explained</a>.</p><h3>Keeping the Records and Handing Them Over</h3><p><strong>Five years.</strong> “You must save the OSHA 300 Log, the privacy case list (if one exists), the annual summary, and the OSHA 301 Incident Report forms for five (5) years following the end of the calendar year that these records cover” (1904.33(a)). The stored log is not frozen. You “must update your stored OSHA 300 Logs to include newly discovered recordable injuries or illnesses and to show any changes that have occurred in the classification of previously recorded injuries and illnesses” (1904.33(b)(1)). The 300A and the 301s do not have to be updated (1904.33(b)(2)-(3)). See <a href="https://logstead.app/blog/how-long-keep-osha-records-retention-updating-1904-33">How Long Do You Have to Keep OSHA Records?</a></p><p><strong>Employees.</strong> An employee, former employee, personal representative, or authorized employee representative can ask for the 300 Log “for an establishment the employee or former employee has worked in”, and you must provide a copy “by the end of the next business day” (1904.35(b)(2)(iii)). An employee, former employee, or personal representative gets the 301 for that employee’s own case by the end of the next business day (1904.35(b)(2)(v)(A)). An authorized employee representative gets only the “Tell us about the case” section of the 301s, for an establishment where it represents employees under a collective bargaining agreement, within 7 calendar days (1904.35(b)(2)(v)(B)). Names stay on the log copies, apart from privacy cases (1904.35(b)(2)(iv)), and “you may not charge for these copies the first time they are provided” (1904.35(b)(2)(vi)). See <a href="https://logstead.app/blog/can-employees-see-osha-300-log-access-rights-1904-35">Can Employees See the OSHA 300 Log?</a></p><p><strong>OSHA.</strong> “When an authorized government representative asks for the records you keep under part 1904, you must provide copies of the records within four (4) business hours” (1904.40(a)). If the records are kept in another time zone, you may use the business hours of the location where they are kept (1904.40(b)(2)). When an inspector asks for the records, that four-hour clock is the one running; the <a href="https://logstead.app/blog/what-happens-osha-heat-nep-inspection-walkthrough-2026">Heat NEP inspection walkthrough</a> shows how a programmed inspection unfolds.</p><h3>Your Employees’ Part: Reporting Procedures and Retaliation</h3><p>A log is only as complete as the reports that reach it, and Part 1904 makes the reporting channel an obligation of its own. You must:</p><ul><li>“establish a reasonable procedure for employees to report work-related injuries and illnesses promptly and accurately”, and “A procedure is not reasonable if it would deter or discourage a reasonable employee from accurately reporting a workplace injury or illness” (1904.35(b)(1)(i));</li><li>tell each employee what that procedure is (1904.35(b)(1)(ii)), and that “Employees have the right to report work-related injuries and illnesses” and that employers “are prohibited from discharging or in any manner discriminating against employees for reporting work-related injuries or illnesses” (1904.35(b)(1)(iii));</li><li>and follow through: “You must not discharge or in any manner discriminate against any employee for reporting a work-related injury or illness” (1904.35(b)(1)(iv)).</li></ul><p>Section 11(c) of the OSH Act adds its own protection for an employee who reports an injury, files a safety and health complaint, or “asks for access to the part 1904 records” (1904.36).</p><p>For a small employer the practical version is short. Tell every new hire how to report an injury and to whom. Say plainly that reporting will not cost them their job. And check that nothing about how reports are handled would discourage the next one.</p><h3>Temps, Contractors, Owners, and State Plans</h3><p><strong>Whose injuries go on your log.</strong> You record the cases of “all employees on your payroll, whether they are labor, executive, hourly, salary, part-time, seasonal, or migrant workers”, and of workers who are not on your payroll “if you supervise these employees on a day-to-day basis” (1904.31(a)). A temp you supervise day to day goes on your log, not the staffing agency’s (1904.31(b)(2)), and the two of you coordinate “to make sure that each injury and illness is recorded only once” (1904.31(b)(4)). Self-employed individuals are not covered (1904.31(b)(1)). In a sole proprietorship or partnership, “the owner or partners are not considered employees for recordkeeping purposes” (1904.31(a)). See <a href="https://logstead.app/blog/temp-staffing-agency-osha-recordkeeping-1904-31">Who Records a Temp Worker’s Injury?</a></p><p><strong>State Plans.</strong> States that run their own OSHA programs “must have occupational injury and illness recording and reporting requirements that are substantially identical to the requirements in this part” (1904.37(a)). What is recordable, and how, is the same everywhere (1904.37(b)(1)). For “industry exemptions, reporting of fatalities and hospitalizations, record retention, or employee involvement”, a State Plan’s rules “may be more stringent than or supplemental to the Federal requirements” (1904.37(b)(2)). If you operate in a State Plan state, check that state’s rules on those four points.</p><h3>What It Costs When the Records Are Wrong</h3><p>OSHA’s current maximum penalties, for violations assessed after January 15, 2026, are $16,550 per violation for serious, other-than-serious, and posting-requirement violations; $16,550 per day beyond the abatement date for failure to abate; and $165,514 per violation for willful or repeated violations (osha.gov/penalties, read September 29, 2026). Under OSHA’s recordkeeping enforcement directive, CPL 02–00–172, Part 1904 violations are cited as other-than-serious, though they can be classified as repeated or willful. The amount actually assessed is often lower: the Field Operations Manual reduces penalties by 70% for employers with 25 or fewer employees, with smaller reductions up to 250 (FOM Chapter 6, Table 6–2).</p><p>The larger cost is usually the inspection itself. The errors inspectors cite most, and how to avoid each one, are in <a href="https://logstead.app/blog/5-osha-recordkeeping-mistakes-that-lead-to-citations">5 OSHA Recordkeeping Mistakes That Lead to Citations</a>.</p><h3>A Small Employer’s Checklist</h3><p><strong>In January, for the year ahead</strong></p><ul><li>Check last year’s peak employment, company-wide, against the 10-employee test.</li><li>Check each establishment’s NAICS code against the partially exempt list.</li><li>Check each establishment against the three ITA categories.</li></ul><p><strong>Set up once</strong></p><ul><li>One OSHA 300 Log for each establishment expected to operate a year or longer.</li><li>A 301, or an equivalent form, for every recordable case, and a confidential privacy-case list.</li><li>A reporting procedure every employee knows, with the right to report and the no-retaliation rule stated plainly.</li></ul><p><strong>For every injury or illness</strong></p><ul><li>Decide recordability: work-related, new case, recording criteria.</li><li>Enter it on the 300 and the 301 within 7 calendar days.</li><li>For a qualifying fatality, call OSHA within 8 hours; for a qualifying in-patient hospitalization, amputation, or loss of an eye, within 24.</li></ul><p><strong>At year end, and in the spring</strong></p><ul><li>Review and correct the log, total it on the 300A (zeros if there were no cases), and have a company executive certify it.</li><li>Post the 300A from February 1 to April 30.</li><li>Submit through the ITA by March 2 if the establishment is covered.</li></ul><p><strong>All the time</strong></p><ul><li>Keep five years of 300s, 300As, 301s, and privacy lists, and update the stored 300 Logs.</li><li>Give employees copies by the end of the next business day, and OSHA copies within four business hours.</li></ul><h3>Frequently Asked Questions</h3><h3>Does OSHA require small businesses to keep injury records?</h3><p>Only if they had more than 10 employees at any time during the last calendar year, counted company-wide, and the establishment’s industry is not on the partially exempt list. Every covered employer, exempt or not, still reports fatalities within 8 hours and in-patient hospitalizations, amputations, and losses of an eye within 24 hours. See <a href="https://logstead.app/blog/do-you-need-to-keep-osha-300-log-recordkeeping-exemptions-small-employers">the exemptions guide</a>.</p><h3>Do we have to do anything if nobody was hurt this year?</h3><p>Yes, if you keep records. The 300A is still completed, with zeros in each column total, certified, and posted from February 1 to April 30 (1904.32(b)(2)(i)). If the establishment is in one of the ITA categories, it also submits that zero-case 300A by March 2.</p><h3>Is an OSHA recordable injury the same as a workers’ comp claim?</h3><p>No. The two systems use different tests, and one does not decide the other. Part 1904 says recording a case does not mean “the employee is eligible for workers’ compensation or other benefits” (Note to 1904.0). See <a href="https://logstead.app/blog/workers-comp-denied-osha-recordable-two-systems-explained">Workers’ Comp Denied but OSHA Recordable?</a></p><h3>Can we keep OSHA records in software or a spreadsheet?</h3><p>Yes, as long as the system can produce equivalent forms when they are needed (1904.29(b)(5)): the same information, as readable, completed with the same instructions as OSHA’s forms. If a spreadsheet is enough for you, the free <a href="https://logstead.app/tools/300-log-workbook">OSHA 300 Log workbook</a> totals the log and the 300A for you. <a href="https://logstead.app/blog/osha-recordkeeping-software-small-business-what-it-must-do">What recordkeeping software actually has to do</a> covers when it isn’t.</p><h3>Who has to sign the 300A?</h3><p>A company executive: an owner of a sole proprietorship or partnership, an officer of the corporation, the highest-ranking company official working at the establishment, or that person’s immediate supervisor (1904.32(b)(4)). A safety coordinator can prepare it, but can only sign it if they hold one of those roles.</p><h3>Does OSHA ever ask exempt employers for records?</h3><p>Yes. OSHA or the BLS can require records from an otherwise exempt employer in writing (1904.1(a)(1), 1904.2(a)(1)). OSHA can require any employer to submit Part 1904 records electronically “Upon notification” (1904.41(a)(3)).</p><h3>Build the Routine Once</h3><p>None of these requirements is hard on its own. What catches small employers is the number of separate clocks: seven days for each case, eight or twenty-four hours for a severe event, a February-to-April posting, a March 2 submission, a next-business-day request, and five years of storage. Set up a log for each establishment, a reporting procedure your people trust, and a year-end routine, and the requirements mostly take care of themselves. In ChatGPT or Claude, <a href="https://logstead.app/ai-assistants">LogStead’s checks for AI assistants</a> list those clocks for a given year’s records, with the regulation behind each.</p><p>LogStead is built around this map. The recordability wizard runs each new case through the Part 1904 tests, and every case lands on the right establishment’s 300 Log with its 301. Privacy cases keep their confidential list separately. The 300A totals, the year-end certification, and the ITA exports all come from the same log lines. The deadline calendar tracks the dates above, and employee record requests carry their own due dates. An existing log comes in from Excel or CSV through the <a href="https://logstead.app/import-osha-300-log">300 Log import</a>, and <a href="https://logstead.app/blog/osha-recordkeeping-software-prices-compared">the software price comparison</a> shows what it costs next to seven other tools. You can start with a single case in the free <a href="https://logstead.app/tools/recordability-checker">recordability checker</a>.</p><p><em>This post is general compliance information, not legal advice. Verify current regulatory text against eCFR and your state plan’s requirements.</em></p><p><em>Originally published at </em><a href="https://logstead.app/blog/osha-recordkeeping-requirements-small-employers"><em>https://logstead.app</em></a><em> on September 29, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cebec65e6cb8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/logstead-blog/osha-recordkeeping-requirements-for-small-employers-cebec65e6cb8">OSHA Recordkeeping Requirements for Small Employers</a> was originally published in <a href="https://medium.com/logstead-blog">LogStead Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSHA Recordkeeping Software Prices Compared (2026)]]></title>
            <link>https://medium.com/logstead-blog/osha-recordkeeping-software-prices-compared-2026-094f0400fa86?source=rss----645c4801a777---4</link>
            <guid isPermaLink="false">https://medium.com/p/094f0400fa86</guid>
            <category><![CDATA[workplace-safety]]></category>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[osha]]></category>
            <dc:creator><![CDATA[Ervin Amaya]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 14:28:15 GMT</pubDate>
            <atom:updated>2026-11-16T14:28:15.469Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ue5alB3WPSLjuqLU" /></figure><p>When we asked ChatGPT and Perplexity in September 2026 which OSHA recordkeeping software a 60-person company should use, both answered with a shortlist and prices: $49 a year, $99 a year, “starts at $5,000.” The numbers came from somewhere, and when we checked them against the vendors’ own pages, several were incomplete. One tool has two more pricing options than the answer mentioned. Another’s “per user” price is per <em>member</em>, and the page shows a different figure when you flip its billing toggle. When we asked ChatGPT the same question in late October, its first pick in all three answers was a ninth tool, 300log, at $40 a year, so we added it and read every vendor’s page again.</p><p>So we read every vendor’s pricing and product pages on <strong>September 27, 2026</strong>, and again on <strong>October 29, 2026</strong>, and wrote down what each one actually says: what it costs, which OSHA forms it produces, what it does about the Injury Tracking Application (ITA), whether it helps you import the log you already keep, and — the question that matters most for a legal record — who decides whether a case is recordable.</p><p>One disclosure up front: LogStead is one of the nine products below. We have tried to describe the others in their own words. Every competitor price and feature on this page is quoted or closely paraphrased from that vendor’s own site and linked, and we say plainly where a cheaper tool is enough or where another product does something we don’t.</p><h3>Published Prices at a Glance</h3><p>Three pricing models are hiding in that table. 300log, OSHA300.com, and HB NEXT charge a flat yearly fee — HB NEXT per establishment. OSHA Sentinel, Safesite, and LogStead sell subscriptions priced by the month, with annual options — Safesite per member. EHS Insight, iReportSource, and Vector quote each customer: EHS Insight publishes a starting price and says the quote depends on headcount and the modules you choose, iReportSource says it depends on organization size and program scope, and Vector publishes no price. OSHA Sentinel also sells the filing as a service, at “$299 per establishment”: “We keep your OSHA injury log, classify each case under 29 CFR 1904, and submit the 300A to OSHA’s ITA before March 2.”</p><h3>What Each Tool Says It Does</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*esY29inuhgMesos9" /></figure><p>Tool 300, 300A, 301 How the ITA filing reaches OSHA Who decides recordability Importing your existing log</p><p>Two columns in that table do most of the work when you choose, so they get their own sections.</p><h3>Which ITA Filing Do You Owe? It Changes Which Tool Is Enough</h3><p>The ITA obligation comes from 29 CFR 1904.41, and it has two tiers. If your establishment “had 20–249 employees at any time during the previous calendar year” and is in an industry listed in appendix A to subpart E, or had 250 or more employees, you submit information from your <strong>300A summary</strong> each year. If your establishment “had 100 or more employees at any time during the previous calendar year” and is in an industry listed in appendix B, you “must electronically submit information from OSHA Forms 300 and 301” too — every case, not just the totals. Both are due by <strong>March 2</strong> of the year after the one the forms cover.</p><p>That second tier is where the inexpensive end of the market differs. OSHA300.com’s and HB NEXT’s pages describe filing the 300A and say nothing about 300 and 301 case data. 300log’s pricing page says it submits both, through OSHA’s API with your own ITA token. OSHA Sentinel says it submits all three forms. Vector exports CSV files for you to file. LogStead generates both upload files — the 300A summary and the case-data file in OSHA’s published format — and you upload them to the ITA yourself. If your establishment is under 100 employees, or your industry isn’t on appendix B, the 300A is the whole filing, and any tool that produces or files it covers you.</p><p>Not sure which tier you’re in? The free <a href="https://logstead.app/tools/ita-checker">ITA filing checker</a> answers it from your NAICS code and peak headcount, and our <a href="https://logstead.app/blog/how-to-submit-osha-data-electronically-ita-portal">step-by-step ITA walkthrough</a> covers the upload itself.</p><h3>Who Decides Whether a Case Is Recordable</h3><p>This is the column that varies most, and it is the one you will eventually have to explain. When a case is questioned — by an employee, an insurer, or an inspector — “the software said so” is not an answer. The reason is. The vendors’ pages describe three different approaches:</p><ul><li><strong>You decide, and the tool records it.</strong> Safesite adds a case to its 300 log when you switch on the toggle that adds it to the injury log. OSHA300.com’s and HB NEXT’s OSHA 300 Cloud pages don’t describe a recordability determination.</li><li><strong>Rules decide.</strong> Vector says its software can “instantly determine if an incident is recordable or reportable.” 300log’s homepage invites you to “watch the same rules the workspace uses decide whether it goes on the OSHA 300 log.” LogStead’s recordability wizard walks the Part 1904 questions in order — work-relatedness, new case, the general recording criteria — and saves the result with its reasoning and the CFR section it rests on.</li><li><strong>An AI model decides.</strong> OSHA Sentinel’s page says: “Describe the incident in plain English. Our AI classifies it per 29 CFR 1904.7 criteria — determining recordability, work-relatedness, and case classification so you don’t have to interpret the regulation yourself.” EHS Insight’s FAQ lists “automated incident classification” among the differentiators of its AI-powered platform.</li></ul><p>An AI classifier can be quick, and it may well be right most of the time. Whichever approach a vendor uses, the question to ask is the same: for a close call, what would you show an inspector? The rule and the facts that met it, or a model’s output? Our longer <a href="https://logstead.app/blog/osha-recordkeeping-software-small-business-what-it-must-do">checklist for recordkeeping software</a> turns that into questions you can put to any vendor.</p><p>LogStead’s answer is the rule. It uses an AI model in exactly one place: reading a photo or scan of a paper log you have already filled in. That model transcribes what is written; it does not classify anything, and nothing is saved until you check each row against your page.</p><h3>What It Costs a 60-Person, Single-Site Company</h3><p>For one establishment with a typical year’s cases, here is what the published prices work out to:</p><ul><li><strong>Forms plus a 300A filing, and nothing else:</strong> 300log Starter at $40 a year, OSHA300.com Starter at $49 a year, or HB NEXT OSHA 300 Cloud at $99 a year. All three say they file the 300A for you.</li><li><strong>OSHA Sentinel:</strong> the free plan covers the 300A only, for up to 5 cases a year. Professional is $79 a month and adds the 300 and 301. Its done-for-you 300A filing service is $299 per establishment.</li><li><strong>Safesite Premium:</strong> $16 per member per month, so three members come to $48 a month.</li><li><strong>LogStead Starter:</strong> $39 a month or $390 a year, for one establishment, up to 100 incidents a year, and three team members. Professional ($79 a month or $790 a year) adds up to five establishments, unlimited incidents, ten team members, and the audit trail.</li><li><strong>EHS Insight</strong> starts at $5k a year; <strong>iReportSource</strong> and <strong>Vector</strong> quote by organization.</li></ul><h3>When the $40 Tool Is the Right Answer</h3><p>If you run one site, record a few cases a year, are comfortable making the recordability call yourself, and aren’t in the 100-plus, appendix B case-data group, a $40 to $99 a year form tool that files your 300A is a reasonable buy. Those tools also send the filing to OSHA for you, which LogStead does not. So is a well-built spreadsheet — we wrote about <a href="https://logstead.app/blog/free-osha-300-log-excel-template-where-it-works-where-it-breaks">where a free 300 log template works and where it breaks</a>.</p><p>LogStead costs more than those tools. It is built for the site where the recordability call is the hard part, where there is more than one establishment, or where last year’s log is on paper. What the difference buys:</p><ul><li>a recordability wizard that asks the Part 1904 questions in order and saves each result with its reasoning and CFR section;</li><li>both ITA upload files, including the 300/301 case data required of 100-plus establishments in appendix B industries;</li><li>privacy-concern cases handled on the 300 (the name is withheld and the case prints as “Privacy Case”);</li><li>an import for the log you already have — CSV, Excel, or a photo or scan of a paper page;</li><li>deadline reminders, and an audit trail on the Professional and Business plans.</li></ul><p>If none of that matters for your site, buy the cheaper tool.</p><h3>What LogStead Doesn’t Do</h3><p>It does not submit to the ITA for you: it generates the files, and you upload them in the ITA yourself. The three cheapest tools above say they do submit for you. It is not an EHS suite either. There are no inspections, training records, or chemical management, and if you need those, the platforms in our <a href="https://logstead.app/blog/ehs-software-alternatives-small-employers">map of EHS software alternatives</a> are the better fit. And the scan reader reads pages; it will not make a recordability call for you.</p><h3>How We Gathered This</h3><p>We read each vendor’s own pricing and product pages on September 27, 2026, and again on October 29, 2026, when we added 300log. Every price and quote here was checked against the vendor’s live page on October 29. Two things changed in between. OSHA Sentinel’s founding-customer offer no longer appears, and its page now lists the $299 filing service. Vector’s line about exporting CSV files now sits on its <a href="https://www.vectorsolutions.com/solutions/vector-ehs-management-software/incidents/">incident reporting page</a>. We used no review sites or reseller listings for prices, and where a vendor publishes no price, we say so rather than estimate one. One vendor page has moved: iReportSource’s former pricing page (/pricing) now returns &quot;page not found,&quot; and its prices are by quote. If you represent one of these vendors and something here is wrong or out of date, email <a href="/service/mailto:support@logstead.app">support@logstead.app</a> and we will correct it.</p><p>If you are moving from paper or a spreadsheet, the <a href="https://logstead.app/import-osha-300-log">LogStead import</a> reads the log you already keep — a CSV, an Excel workbook, or a photo or scan of the page — and runs every case through the same checks as manual entry. Nothing is saved until you review the rows and import them, and a row read from a scan must first be ticked as matching your page. It is included in the 14-day free trial.</p><p><em>Originally published at </em><a href="https://logstead.app/blog/osha-recordkeeping-software-prices-compared"><em>https://logstead.app</em></a><em> on September 27, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=094f0400fa86" width="1" height="1" alt=""><hr><p><a href="https://medium.com/logstead-blog/osha-recordkeeping-software-prices-compared-2026-094f0400fa86">OSHA Recordkeeping Software Prices Compared (2026)</a> was originally published in <a href="https://medium.com/logstead-blog">LogStead Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EHS Software Alternatives for Small Employers]]></title>
            <link>https://medium.com/logstead-blog/ehs-software-alternatives-for-small-employers-3ea500d7137a?source=rss----645c4801a777---4</link>
            <guid isPermaLink="false">https://medium.com/p/3ea500d7137a</guid>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[workplace-safety]]></category>
            <category><![CDATA[osha]]></category>
            <dc:creator><![CDATA[Ervin Amaya]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 14:26:46 GMT</pubDate>
            <atom:updated>2026-11-16T14:26:46.379Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G-EO_cmQR44LCb-8" /></figure><p>If you searched something like “Intelex alternative for small business” or “simple EHS software,” you have probably already discovered the problem with this product category: almost every comparison page is written by one of the vendors in it, and almost every product in it is built for a company with an EHS <em>department</em>. A 35-person machine shop that just needs its OSHA 300 Log kept right ends up reading feature grids about ESG reporting, contractor permit-to-work systems, and 3D ergonomic motion capture.</p><p>This post is the map we wished existed. It sorts the market into the three categories that actually matter for a small employer — full EHS suites, recordkeeping-focused tools, and the spreadsheet — and says plainly what each is for, what each costs you in practice, and how to pick using your <em>obligation</em> rather than a feature count. One disclosure up front: LogStead is a product in the second category, and this page says so where it’s relevant. The comparison is still honest — including the section on what LogStead deliberately does not do. For the published prices of nine tools side by side, see <a href="https://logstead.app/blog/osha-recordkeeping-software-prices-compared">OSHA recordkeeping software prices compared</a>.</p><h3>Start With the Obligation, Not the Product</h3><p>The fastest way to buy the wrong safety software is to start from a vendor list. Start from what 29 CFR Part 1904 actually requires of a company your size:</p><ul><li><strong>10 or fewer employees at all times during the last calendar year?</strong> You are exempt from routine recordkeeping under 1904.1 — no 300 Log, no 300A, no 301 — unless OSHA or the BLS asks in writing. The same is true regardless of size if your industry is on the low-hazard list in Appendix A to Subpart B. <a href="https://logstead.app/blog/do-you-need-to-keep-osha-300-log-recordkeeping-exemptions-small-employers">The exemption walkthrough</a> resolves borderline cases. If you’re exempt, you don’t need any of these products for recordkeeping — though note the severe-injury reporting duty in 1904.39 (8 hours for a fatality, 24 for an in-patient hospitalization, amputation, or eye loss) applies to everyone.</li><li><strong>11 or more employees in a covered industry?</strong> You owe the full recordkeeping surface: recordability determinations within 7 calendar days, the 300 Log, a 301 for every case, the certified 300A posted February 1 through April 30, five-year retention, and employee access on request.</li><li><strong>20 or more employees in a designated industry (or 250+ anywhere covered)?</strong> Add electronic submission to OSHA’s Injury Tracking Application by March 2 each year — and at 100+ employees in a high-hazard Appendix B industry, that means the detailed 300/301 case files, not just the summary.</li></ul><p>Notice what’s on that list and what isn’t. Nothing in Part 1904 requires inspection checklists, training management, chemical inventories, or behavior-based safety programs. Those may be worth doing — some are required by <em>other</em> standards — but they are not the recordkeeping obligation. The question “which EHS software should I buy” is really two questions: <strong>what does the law require of me</strong>, and <strong>what do I additionally want to manage?</strong> The categories below split exactly along that line.</p><h3>Category 1: The Full EHS Suites</h3><p>These are the platforms that dominate the “best EHS software” lists: broad, modular systems built to run an entire safety program across many sites. As of this writing (August 2026), the recognizable names look like this:</p><ul><li><strong>VelocityEHS</strong> — now operating at ehs.com under its “Accelerate” platform — spans eight solution areas: safety (incidents, audits, inspections), ergonomics, chemical management, operational risk, contractor safety and permit-to-work, environmental compliance, sustainability, and industrial hygiene. It reports 15,000+ customers globally.</li><li><strong>Intelex</strong> covers health and safety, environment and sustainability, quality, risk, and ESG for 1,400+ organizations — an enterprise EHSQ platform in the full sense.</li><li><strong>EHS Insight</strong> advertises 32 modules on an AI-powered platform, from incident and audit management to chemical management, claims, and safety drills.</li><li><strong>KPA</strong> pairs its Vera Suite software with 140+ consultants and training services, with a client base concentrated in automotive — dealerships, collision centers, and auto care make up much of its 15,000+ clients.</li><li><strong>SafetyCulture</strong>, the inspections-and-checklists platform many small businesses actually have installed, rebranded as <strong>Mitti</strong> on August 11, 2026, repositioning from a safety tool to an AI-powered “workplace operations system” covering quality, training, assets, and more for its 80,000 customer organizations.</li></ul><p>Two things are honestly true about this category. First, <strong>these are real, capable products</strong> — if you need chemical inventory management under HazCom, a contractor permit system, multi-site inspection programs, and training records in one place, a suite is the correct purchase, and nothing in the other two categories substitutes for it. Second, <strong>they are sized and sold for organizations that have someone to run them.</strong> Pricing is almost uniformly quote-and-demo-based rather than published, implementation is a project, and the module breadth you’re paying for is exactly the part a 30-person employer never opens. The common small-employer failure mode isn’t buying a bad suite — it’s buying a good suite and using six percent of it, with the 300 Log living in one module of a system nobody fully configured.</p><p>One nuance inside this category: some suite vendors do take the injury-log slice seriously. <strong>Vector EHS</strong> (Vector Solutions — the product formerly known as IndustrySafe) generates OSHA 300, 300A, and 301 forms and exports ITA-ready CSV files as part of its broader incident, inspection, and claims platform. If you’re already inside such an ecosystem for training or other modules, check whether the recordkeeping module meets the bar in the next section before adding a second tool.</p><h3>Category 2: Recordkeeping-Focused Tools</h3><p>The second category is narrow on purpose: software whose whole job is the Part 1904 obligation — deciding recordability, keeping the 300/300A/301 consistent, running the deadline clocks, and producing the ITA file. LogStead is in this category, so read the following as a vendor describing its own category honestly rather than a neutral survey.</p><p>The case for a narrow tool is the mirror image of the case for a suite. A small employer’s recordkeeping problem is not module count — it is that the obligation is <em>exacting</em> and lands on someone who does it a few times a year: an office manager, an HR generalist, the owner. The rules run on specifics — the 14-item first-aid list, calendar-day counts capped at 180, six privacy-case categories where writing the employee’s name is itself the violation, a 300A that must equal the log behind it, an ITA CSV with 24 coded columns per case. A tool focused on exactly this can walk a non-specialist through each determination, keep the three forms in agreement by construction, and cost what a small company will actually pay, with no implementation project.</p><p>What should you demand from anything in this category? We wrote the full checklist separately — <a href="https://logstead.app/blog/osha-recordkeeping-software-small-business-what-it-must-do">Part 1904 turned into a feature list</a> — but the short version: reproducible, documented recordability decisions with the citation behind each answer; one incident record that derives all three forms; all six deadline clocks; the ITA CSV in OSHA’s published spec; and an audit trail that survives the five-year retention window. Two red flags while you shop: any product claiming to be “OSHA-approved” (OSHA certifies nothing, and says so in writing), and — where a legal record is concerned — classification you can’t explain. Several tools in and around this category now advertise AI or automatic recordability determination; whatever the label, ask the vendor to show you <em>the reasoning the tool records</em> for why a case was or wasn’t recordable. If the answer is a probability rather than a criterion in 1904.5–1904.7, that determination will be hard to stand behind when an inspector, an employee representative, or opposing counsel asks — which is why LogStead keeps its own recordability logic deterministic and cited, with no AI anywhere in the record of authority.</p><h3>Category 3: The Spreadsheet (and OSHA’s Free Forms)</h3><p>The alternative every vendor page pretends not to see: OSHA publishes the 300, 300A, and 301 as free forms, keeping them in Excel is explicitly legal under the equivalent-form rules, and for some employers that is genuinely enough. If you have one establishment, a handful of recordable cases a year, and someone who knows the rules, a carefully kept spreadsheet passes the compliance test. We mean that — we wrote <a href="https://logstead.app/blog/free-osha-300-log-excel-template-where-it-works-where-it-breaks">an entire guide to the free-template route</a>, including a downloadable workbook that totals its own 300A, precisely because the honest answer for the smallest employers is often “you don’t need to buy anything yet.”</p><p>The failure modes are equally real, and they’re the ones that show up in citations: day counts kept in workdays instead of calendar days, the 180-day cap missed, a privacy case with a name on it, year-end 300A totals that don’t reconcile to the log, and the March 2 ITA file re-keyed by hand from cells that drifted during the year. The template guide walks each one. The practical rule: the spreadsheet stops being enough when case volume, multiple establishments, or the detailed 300/301 electronic-submission duty raises the cost of a manual error above the cost of a tool.</p><h3>The Decision, By Employer Profile</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lwohFVfC5669-i42" /></figure><p>Your situation Honest starting point</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZC--wJMGSMI2IDA1" /></figure><p>10 or fewer employees all last year, or Appendix A low-hazard industry</p><p>Nothing — you’re exempt from routine recordkeeping (verify with the <a href="https://logstead.app/blog/do-you-need-to-keep-osha-300-log-recordkeeping-exemptions-small-employers">exemption guide</a>; the 1904.39 reporting duty still applies)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SwA-StE3AU8hdzcy" /></figure><p>11–19 employees, one site, rare recordables, someone who knows the rules</p><p>OSHA’s free forms or a disciplined spreadsheet, honestly kept</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ebNaoM9QiU1D-zEI" /></figure><p>20–249 employees in a designated industry (ITA 300A duty), or multiple establishments</p><p>A recordkeeping-focused tool — this is the zone where consistency and the deadline clocks earn their keep</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YbfcogmuVjX8k-V8" /></figure><p>100+ employees in an Appendix B high-hazard industry (300/301 case-detail ITA duty)</p><p>A recordkeeping tool that produces the case-detail CSV in spec — hand-keying 24 columns per case is where spreadsheets break hardest</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DiE5-C2-eMzS7oIb" /></figure><p>Chemical inventories, contractor permits, formal training programs, dedicated EHS staff, many sites</p><p>A full EHS suite — and make sure its recordkeeping module meets the same bar you’d hold a narrow tool to</p><p>Two free checks help place you on that table: the <a href="https://logstead.app/tools/ita-checker">ITA Submission Checker</a> tells you from headcount and NAICS code which electronic-submission tier, if any, you’re in, and the <a href="https://logstead.app/tools/recordability-checker">recordability checker</a> shows you what a walked, cited determination looks like before you evaluate anyone’s wizard.</p><h3>What LogStead Does Not Do</h3><p>Since this page will be read as a comparison, here is our side of it stated plainly. LogStead does <strong>not</strong> do inspections or checklist programs, training management, chemical or SDS management, permit-to-work, ergonomics, or ESG reporting. If those are requirements, one of the suites above is the better buy, and we’d rather say so here than have you discover it in a trial. What LogStead does is the recordkeeping slice, thoroughly: a recordability wizard that walks 1904.4–1904.7 in plain English and cites the rule behind every answer, Forms 300, 300A, and 301 that stay consistent because they derive from one incident record, deadline tracking for every clock in the table above, and one-click export of the exact CSVs OSHA’s ITA portal accepts — including the case-detail file larger high-hazard establishments owe. You can poke through every screen of it with a fictional company’s data, no account required, at <a href="https://logstead.app/demo">the live demo</a>.</p><p>Whichever category you land in, buy against the obligation. The vendor lists will still be there next year; the March 2 deadline and the February 1 posting date come around regardless of what’s on them.</p><p><em>Originally published at </em><a href="https://logstead.app/blog/ehs-software-alternatives-small-employers"><em>https://logstead.app</em></a><em> on August 29, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ea500d7137a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/logstead-blog/ehs-software-alternatives-for-small-employers-3ea500d7137a">EHS Software Alternatives for Small Employers</a> was originally published in <a href="https://medium.com/logstead-blog">LogStead Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Average TRIR by Industry: 2024 BLS Benchmarks]]></title>
            <link>https://medium.com/logstead-blog/average-trir-by-industry-2024-bls-benchmarks-eec496700e16?source=rss----645c4801a777---4</link>
            <guid isPermaLink="false">https://medium.com/p/eec496700e16</guid>
            <category><![CDATA[benchmarking]]></category>
            <category><![CDATA[osha]]></category>
            <category><![CDATA[workplace-safety]]></category>
            <dc:creator><![CDATA[Ervin Amaya]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 00:04:55 GMT</pubDate>
            <atom:updated>2026-11-10T00:04:55.459Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3dJSxGNqUr3WFjyN" /></figure><p>You calculated your TRIR. Maybe it came out to 3.1, or 5.4, or 0 — and the number, by itself, tells you nothing. A 3.1 is excellent for a nursing home, unremarkable for a plumbing contractor, and alarming for a physician’s office. The only way to read an incident rate is against the rate for employers who do the same kind of work you do — and the authoritative source for that comparison is the Bureau of Labor Statistics’ Survey of Occupational Injuries and Illnesses (SOII), which publishes injury and illness incidence rates by industry every year.</p><p>This post is the reference for the <strong>2024 data</strong> — the most recent available, released January 22, 2026 — organized the way a small employer actually uses it: the headline numbers, a benchmark table for the industries where small businesses live, and then the part most benchmark articles skip: what the comparison does and doesn’t mean when your whole company is 15 people. (If you need the formulas themselves — what counts in the numerator, how to get the hours right — that’s covered in our <a href="https://logstead.app/blog/trir-dart-rates-explained-small-employers">plain-English guide to TRIR and DART rates</a>. This post assumes you have a rate and want to know what it means.)</p><h3>The 2024 Headlines</h3><p>From the BLS release (USDL-26–0101, January 22, 2026), covering calendar year 2024:</p><ul><li>Private industry employers reported <strong>2.5 million</strong> nonfatal workplace injuries and illnesses — down 3.1 percent from 2023, and the lowest count in the data series going back to 2003.</li><li>The <strong>total recordable case (TRC) rate was 2.3 cases per 100 full-time equivalent workers</strong>, down from 2.4 in 2023 — also the lowest on record for the series.</li><li>Injuries alone occurred at 2.2 cases per 100 FTE. Illnesses fell to 13.9 cases per 10,000 FTE (from 19.0 in 2023), driven mostly by a 46 percent drop in respiratory illness cases — the continuing post-COVID normalization.</li><li><strong>No industry sector’s rate increased in 2024.</strong> Five sectors decreased, including health care and social assistance (3.6 → 3.4) and information (1.0 → 0.7, the lowest of any major sector).</li></ul><p>One vocabulary note before the table: BLS says “TRC rate” where most safety professionals say “TRIR.” They are the same number — total OSHA-recordable cases × 200,000 ÷ hours worked. BLS also publishes a <strong>DART rate</strong> for most industries: cases involving days away from work, job transfer, or restriction, on the same per-100-FTE basis.</p><h3>2024 Benchmarks for Common Small-Business Industries</h3><p>All rates are per 100 full-time equivalent workers, private industry, all establishment sizes, from BLS SOII 2024. Find your industry — or the closest published level to your NAICS code — and read both columns: TRIR is how often people get hurt; DART is how often it’s serious enough to cost work time.</p><p>A few patterns worth noticing. The industries the public assumes are most dangerous are not the ones at the top of the table: construction of buildings, at 2.2, sits <em>below</em> the all-industry average, while couriers (8.0), warehousing (4.8), and nursing and residential care (5.5) run two to three times the national rate. And the TRIR-to-DART ratio varies a lot by industry — in warehousing, roughly 85 percent of recordables cost work time; in full-service restaurants, closer to a third do. If your DART is close to your TRIR, your cases are running more serious than your industry’s mix.</p><h3>The Small-Employer Problem: One Case Moves Your Rate More Than Anything You Did</h3><p>Here is the part that matters most below about 50 employees, and that benchmark articles written for corporate safety departments never mention.</p><p>The rate formula divides by hours worked and multiplies by 200,000 — the hours of 100 full-time workers. A 15-person shop puts in roughly 30,000 hours a year. Run the arithmetic:</p><ul><li><strong>Zero recordable cases → TRIR 0.0.</strong> You beat every industry in the table.</li><li><strong>One recordable case → TRIR 6.7.</strong> You are now nearly three times the national average and worse than any industry above except couriers.</li></ul><p>Nothing about your safety program changed between those two years — one employee needed stitches. At small hours denominators, TRIR is a coin-flip statistic year to year, and treating a single year’s number as a verdict (in either direction) is innumerate. What a small employer can honestly do with the benchmark:</p><ol><li><strong>Compare a multi-year average.</strong> Three years of cases over three years of hours smooths the coin flips into something closer to a signal.</li><li><strong>Watch DART separately.</strong> Whether cases cost work time is partly luck, but a DART that persistently tracks your TRIR means your incidents are serious, not just frequent — and the <a href="https://logstead.app/blog/counting-days-away-restricted-work-osha-300-log-1904-7">day counts that feed DART</a> are calendar days with specific rules, so a counting error moves this rate too.</li><li><strong>Treat the trend as the metric.</strong> Down and to the right over three years beats any single-year comparison to the table.</li></ol><h3>Who Actually Reads Your Rate — and Which Data They Use</h3><p>Three audiences compare your rates to these benchmarks, and it’s worth knowing they don’t all use the same data:</p><p><strong>Insurers and general contractors</strong> use the number you give them, usually straight off your 300A. Many GC prequalification forms ask for three years of TRIR and DART (“EMR and OSHA rates”), and some apply hard cutoffs — commonly your industry average or a fixed threshold. This is where the benchmark touches revenue: for a subcontractor, a rate above the 238-series averages in the table can mean lost bids before anyone reads a safety program.</p><p><strong>OSHA</strong> does not use SOII to pick inspection targets — SOII is an anonymized statistical survey. What OSHA uses is the establishment-level data you submit through the Injury Tracking Application every March 2, from which it computes your rates and feeds its <a href="https://logstead.app/blog/how-osha-picks-who-to-inspect-site-specific-targeting-program-explained">Site-Specific Targeting program</a>. Same underlying 300-log arithmetic, different pipeline — and it’s your own submitted data, not an industry average, that puts an establishment on that list.</p><p><strong>BLS itself</strong> collects SOII from a sample of employers each year (if you’re sampled, participation is mandatory), and the survey rides directly on your OSHA 300 log — the survey form is essentially “transcribe your log.” Accurate recordkeeping is what makes these benchmarks exist at all.</p><h3>How Serious Are the Cases Behind the Averages?</h3><p>The 2024 release also carries BLS’s biennial case detail for 2023–2024, which is useful for calibrating expectations when you do have a case:</p><ul><li>Cases with <strong>days away from work</strong> made up 61.5 percent of all DART cases, with a <strong>median of 8 days away</strong>.</li><li>Cases with <strong>job transfer or restriction only</strong> made up the rest, with a <strong>median of 15 days</strong> of restriction — restricted-duty cases run longer than days-away cases, which surprises people until they think about how return-to-work programs work.</li><li>The largest driver of DART cases across the two years was overexertion, repetitive motion, and bodily-condition events (about 946,000 cases), ahead of contact-with-object incidents (about 860,000).</li></ul><p>If an employee is out for two weeks after a lifting injury, that is not an outlier — it’s the median neighborhood. What decides whether the case lands in your K column or your L column (and therefore in your DART numerator) is the outcome classification, which is exactly the place <a href="https://logstead.app/blog/is-this-injury-osha-recordable">recordability and outcome calls</a> have to be made correctly before any rate is worth benchmarking.</p><h3>Common Questions</h3><p><strong>What is a “good” TRIR?</strong> There is no universal threshold. Below your industry’s published rate is the defensible claim; below it on a three-year average is the credible one. For contract prequalification, the practical bar is whatever the GC’s form says — commonly “at or below industry average.”</p><p><strong>Is a TRIR of 5 high?</strong> Against private industry overall (2.3), yes — more than double. Against nursing care (5.5) or hospitals (5.1), it’s average. Industry first, then judgment.</p><p><strong>Does OSHA fine you for a high TRIR?</strong> No. There is no citation for a high rate. Rates matter to OSHA as a targeting signal (via your ITA submission, not SOII), and recordkeeping violations are cited for inaccurate or late records — not for the injuries themselves being numerous.</p><p><strong>Where do I get the full BLS table?</strong> bls.gov/iif — the “Nonfatal injuries and illnesses tables” page carries the complete industry table (Table 1) for every published NAICS level. The 2025 reference-year data should arrive on roughly the same schedule, in late 2026 or early 2027.</p><h3>Benchmarking Without the Spreadsheet Step</h3><p>The comparison only means something if the inputs are right: every recordable case captured (and nothing over-recorded), day counts kept to the calendar-day rules, and hours worked totaled from payroll rather than estimated. LogStead computes TRIR and DART from your 300 log and hours as you keep them, so the rate you benchmark is the rate your records actually support — and the <a href="https://logstead.app/tools/rate-calculator">free rate calculator</a> runs the same 2024 BLS benchmark lookup shown in this post against any NAICS code, no account required. <a href="https://logstead.app/ai-assistants">LogStead’s checks for ChatGPT and Claude</a> run the same lookup from your case counts and hours.</p><p><em>Originally published at </em><a href="https://logstead.app/blog/average-trir-by-industry-2024-bls-benchmarks-naics"><em>https://logstead.app</em></a><em> on August 24, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eec496700e16" width="1" height="1" alt=""><hr><p><a href="https://medium.com/logstead-blog/average-trir-by-industry-2024-bls-benchmarks-eec496700e16">Average TRIR by Industry: 2024 BLS Benchmarks</a> was originally published in <a href="https://medium.com/logstead-blog">LogStead Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Free OSHA 300 Log Excel Template: Where It Breaks]]></title>
            <link>https://medium.com/logstead-blog/free-osha-300-log-excel-template-where-it-breaks-7bd3434a1516?source=rss----645c4801a777---4</link>
            <guid isPermaLink="false">https://medium.com/p/7bd3434a1516</guid>
            <category><![CDATA[excel]]></category>
            <category><![CDATA[workplace-safety]]></category>
            <category><![CDATA[osha]]></category>
            <dc:creator><![CDATA[Ervin Amaya]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 00:03:32 GMT</pubDate>
            <atom:updated>2026-11-10T00:03:32.577Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wkV7EA7eueRxCaKl" /></figure><p>Search for a free OSHA 300 Log template and you will find two kinds of page: the ones that want your email address in exchange for a spreadsheet, and the ones that want you to believe a spreadsheet is dangerous. Both are selling something. The honest version is shorter.</p><p>OSHA’s own forms package — the 300 Log, the 300A Annual Summary, the 301 Incident Report, the instructions, and the average-employees worksheet — is free at <a href="https://www.osha.gov/recordkeeping/forms">osha.gov/recordkeeping/forms</a>, as fillable PDFs. The agency does not distribute a spreadsheet version, but it says on that same page that equivalent forms “may be maintained in any file format (e.g. Excel, CSV)” as long as the equivalent-form rule is met. So a 300 Log in Excel is not a workaround. It is a legal record, and for a single-site employer with a handful of cases a year and one person who knows the rules, it is often all you need.</p><p>What a template cannot do is <em>enforce</em> the rules. The regulation has a small number of places where a cell that accepts whatever you type will quietly produce a wrong record — and those are the places where the cost of being wrong is an inaccurate federal form, a citation, or a March 2 submission OSHA rejects. This guide names them, so you can decide with open eyes whether the spreadsheet is still the right tool. (If your question is simply <em>may</em> I keep the log electronically at all, that is <a href="https://logstead.app/blog/keep-osha-300-log-electronically-equivalent-forms-1904-29">answered in full here</a>. The answer is yes.)</p><h3>What “Equivalent Form” Actually Requires</h3><p>The whole legal basis for a spreadsheet 300 Log is one sentence in 29 CFR 1904.29(b)(4): an equivalent form “is one that has the same information, is as readable and understandable, and is completed using the same instructions as the OSHA form it replaces.”</p><p>Three tests, then. The template must carry every column of the official 300 Log — case number, name, job title, date, location, description, the four outcome columns (death, days away, job transfer or restriction, other recordable), the two day-count columns, and the six injury/illness type columns. It must be as readable as the printed form. And it must be filled in by the <em>official instructions</em>, which is where templates start to drift: the instructions say calendar days, say check only the most serious outcome, say write “privacy case” instead of a name in six situations, and a blank spreadsheet says none of that.</p><p>For the 300A there is an extra condition. The annual summary is the one form that gets posted and certified, and a substitute must carry the same certification block and the employee-access and penalty statements as the official form — OSHA’s forms page cites 1904.32(b)(2)(iii) alongside the equivalent-form rule for exactly that reason. The safest practice, whatever you do with the log, is to transfer your totals onto OSHA’s official 300A PDF for posting. It costs nothing.</p><h3>Where a Spreadsheet Genuinely Works</h3><p>Be specific about the conditions, because they are the same conditions under which a template fails quietly when they stop being true:</p><ul><li><strong>One establishment.</strong> Part 1904 requires a separate 300 Log per establishment, and the exemptions and ITA thresholds are evaluated per establishment too. One tab, one site, no ambiguity. (Two sites is where <a href="https://logstead.app/blog/multi-establishment-osha-recordkeeping-one-log-per-location">multi-establishment recordkeeping</a> starts to complicate things.)</li><li><strong>Few cases.</strong> At three or four recordable cases a year, every day count, every reclassification, and every year-end total can be checked by hand against the rule.</li><li><strong>Cases that resolve quickly.</strong> A case that closes in a week never tests the 180-day cap or crosses a year boundary.</li><li><strong>One knowledgeable keeper.</strong> The rules the template does not enforce live in the head of whoever maintains it. That is fine as long as that person is consistent and stays.</li><li><strong>No 1904.41 submission duty.</strong> If your establishment is under 20 employees, or not in the designated industries, there is no CSV to produce and no portal to satisfy. (The <a href="https://logstead.app/tools/ita-checker">free ITA Submission Checker</a> settles this in a minute.)</li></ul><p>If all five hold, keep the spreadsheet and apply the hygiene rules at the end of this post. If two or more have stopped holding, read on.</p><h3>The Five Places a Template Breaks</h3><p>Each of these is a rule the regulation states precisely and a spreadsheet cell cannot enforce. In each case the failure is silent: the sheet looks complete, and it is wrong.</p><h3>1. Day counts are calendar days, start the day after, and cap at 180 combined</h3><p>Columns K and L of the 300 Log are the most mis-kept cells in small-employer recordkeeping, because the official rule contradicts what most people assume. Under 1904.7(b)(3):</p><ul><li>The count begins <strong>the day after</strong> the injury occurred or the illness began — (b)(3)(i).</li><li>You count <strong>calendar days</strong> the employee was unable to work, “regardless of whether or not the employee was scheduled to work on those day(s)” — (b)(3)(iv). Weekends and holidays count.</li><li>You <em>may</em> cap the total at <strong>180 calendar days</strong> — (b)(3)(vii) — and the cap is combined across days away and restricted days, not 180 for each.</li><li>If the employee leaves the company for a reason unrelated to the case, you may stop counting — (b)(3)(viii).</li></ul><p>A template gives you a cell. Whoever fills it in will type the number of <em>workdays</em> missed, because that is what the time-off system reports, or will type the count on the day the case was entered and never revisit it. Either way the 300A total days figure at year-end is wrong, and the error compounds: those day totals feed your DART rate and, if you submit, the ITA. The <a href="https://logstead.app/blog/counting-days-away-restricted-work-osha-300-log-1904-7">complete day-counting guide</a> walks every edge case; a spreadsheet enforces none of them unless someone builds and protects a formula — and locks it against the next person who “fixes” it.</p><p><strong>What it costs:</strong> a 300A that does not match the log, rate calculations built on bad inputs, and a standard correction item in a records inspection.</p><h3>2. Privacy cases put the employee’s name in the wrong place</h3><p>Under 1904.29(b)(7), six categories of case are privacy concern cases, and in those cases you must <em>not</em> enter the employee’s name on the 300 Log — you write “privacy case” in the name column instead. The list is exhaustive: injuries to an intimate body part or the reproductive system, injuries resulting from sexual assault, mental illnesses, HIV infection, hepatitis, or tuberculosis, contaminated needlesticks and sharps injuries, and any other illness where the employee asks that their name be left off. Then (b)(6): you “must keep a separate, confidential list of the case numbers and employee names” so you can update the cases and give the information to the government if asked.</p><p>A template has one name column. The moment a privacy case arrives, the spreadsheet needs a second, <em>separately stored</em> document, a rule about which copy of the log goes to whom, and the discipline to strip the name from every derived copy — the copy an employee or their representative can request under 1904.35, the version your insurance broker asked for, the CSV you export. In practice the name ends up in the log, or the confidential list ends up on the same tab, or a copy with names leaves the building. The <a href="https://logstead.app/blog/osha-privacy-concern-cases-300-log-1904-29">privacy-case post</a> has the details and the discretion rule in (b)(9) for the description column.</p><p><strong>What it costs:</strong> a disclosure you cannot take back, and a 300 Log that is wrong in the one column the rule tells you to get right.</p><h3>3. Cases change, and the log has to change with them</h3><p>The 300 Log records each case under its <em>most serious</em> outcome, and cases evolve. An employee on restricted duty in March is put on days away in May after surgery. A “medical treatment only” case becomes a days-away case when the provider writes a note. Under 1904.33(b)(1) you must update the log — “you must update the stored OSHA 300 Log” is the rule for prior years, and the live year is held to at least the same standard by the instructions — to reflect changes in classification, description, and outcome.</p><p>In a spreadsheet that means finding the row, un-checking one outcome column, checking another, adjusting two day counts, and remembering that the 300A you already drafted is now stale. Nothing prompts any of it. The row was correct the day it was entered, and that is the last time anyone looked at it.</p><p><strong>What it costs:</strong> a log that records what was true in week one, not what happened — which is what an inspector will compare against your workers’ compensation file.</p><h3>4. Year-end: the 300A has to equal the log, and then an executive signs it</h3><p>1904.32 is a four-step duty: review the log “as extensively as necessary to make sure that they are complete and correct,” total every column, certify, and post. The totals must agree with the log; a year with no recordable cases still gets a summary with zeros on it. A <strong>company executive</strong> — an owner, an officer, the highest-ranking person at the establishment, or that person’s supervisor — must certify that they have examined the log and reasonably believe the summary is correct. The summary is posted from <strong>February 1 to April 30</strong> where employee notices go.</p><p>The average-employees and total-hours fields have their own trap: the official worksheet computes annual average employees from <strong>pay periods</strong>, not a head count — add the employees paid in each pay period, divide by the number of pay periods (including any with zero), round up. The <a href="https://logstead.app/blog/osha-300a-annual-summary">300A guide</a> works the arithmetic.</p><p>A spreadsheet with a SUM row handles the easy half. It does not handle the row someone <em>deleted</em> in October instead of lining out - which the 1904.33 retention rule does not permit - so the totals are now right for a log that is wrong. It does not carry the certification language. And it puts the executive&#39;s signature on a document whose accuracy they have no practical way to audit, which is precisely the exposure the certification exists to create.</p><p><strong>What it costs:</strong> a certified, posted federal form that does not reconcile to its source, signed by the person with the most to lose from that.</p><h3>5. The ITA file is a column-exact CSV you re-key by hand</h3><p>If your establishment meets the 1904.41 thresholds — 20 to 249 employees in one of the designated high-hazard industries, or 250 or more in any industry required to keep records — you owe OSHA an electronic 300A submission through the Injury Tracking Application by <strong>March 2</strong>. Establishments with 100 or more employees in the narrower Appendix B industry list owe 300 and 301 <em>case-level</em> data as well. The <a href="https://logstead.app/blog/how-to-submit-osha-data-electronically-ita-portal">ITA submission guide</a> covers the portal mechanics.</p><p>The portal accepts a CSV in OSHA’s exact column layout: a nine-digit EIN without dashes, a six-digit NAICS code, integer-only totals, establishment size in coded buckets, and for case data, 24 named columns with coded outcomes and mm/dd/yyyy dates - and its rejection messages are terse about which row failed. A spreadsheet 300 Log has none of that structure. Producing the file means re-typing every total, and for case data every case, into a second sheet built to OSHA&#39;s template, in deadline week. That re-keying step is where transcription errors enter the one copy of your record that goes to the government.</p><p>The free <a href="https://logstead.app/tools/ita-csv-validator">ITA CSV Validator</a> will check a hand-built file against OSHA’s published formats before you upload it, entirely in your browser. It cannot make the re-keying go away.</p><p><strong>What it costs:</strong> a rejected submission two days before the deadline, or an accepted one that does not match the log you posted.</p><h3>If You Keep the Template: Six Hygiene Rules</h3><p>There is no shame in the spreadsheet. Make it as defensible as it can be:</p><ol><li><strong>Start from OSHA’s columns, not a vendor’s.</strong> Build the tab to mirror the official 300 Log exactly, in the official order, and keep the official instructions in a second tab. That is what (b)(4) means by “the same instructions.”</li><li><strong>Make the day counts a formula and protect it.</strong> =MIN(180, return_date - incident_date) with the return date as an input cell; lock the formula cells. Calendar days, starting the day after, capped at 180.</li><li><strong>Never delete a row.</strong> Strike the text and add a note. The five-year retention rule in <a href="https://logstead.app/blog/how-long-keep-osha-records-retention-updating-1904-33">1904.33</a> requires you to <em>update</em> stored logs, not rewrite them, and a deleted row cannot be explained later.</li><li><strong>Keep the privacy-case list in a different file</strong> with different access, and treat every export of the log as a copy that must be checked for names before it leaves.</li><li><strong>Post the official 300A PDF.</strong> Transfer your totals onto OSHA’s form so the certification language and the access and penalty statements are there by construction. Keep the worksheet you used for average employees with it.</li><li><strong>Date-stamp a snapshot at year-end</strong> and after every update to a prior year. When a question arises in year four, you will need to show what the log said on a given date.</li></ol><h3>Or Download the Workbook That Has the Rules Built In</h3><p><em>(Added August 24, 2026.)</em> Most of the hygiene list above can be built into the file once instead of remembered every time, so we did that. The <a href="https://logstead.app/tools/300-log-workbook">free auto-totaling 300/300A workbook</a> is a plain .xlsx - no email address, no account; the link is the file - with the rules from this guide enforced in-sheet:</p><ul><li>the 300 Log tab mirrors OSHA’s columns (A)-(M) in the official order, with the instructions in a Read Me tab — the (b)(4) “same instructions” condition from rule 1;</li><li>the outcome columns G-J and type columns M(1)-M(6) only accept an X, and a row-check column flags a row with zero or two outcomes marked, a day count whose outcome box isn’t checked, and combined day counts past the 180 cap;</li><li>the 300A tab is formulas over the log — failure mode #4 (year-end totals that disagree with the log) is gone by construction, and the totals are pinned by automated test to the same math LogStead itself runs;</li><li>the privacy-case convention from rule 4 is documented where you’ll see it, in the file.</li></ul><p>What it deliberately does not do: decide recordability, compute TRIR/DART, or generate the ITA CSV — failure mode #5 still applies to any spreadsheet, and the <a href="https://logstead.app/tools/ita-csv-validator">validator</a> is the safety net when you re-key that file. And rule 5 stands: post the official 300A PDF, whatever totals your workbook computed.</p><h3>When to Move</h3><p>The decision rule is not “spreadsheets are unsafe.” It is that the spreadsheet’s cost is invisible until the year it is not. Move when any of these becomes true: a second establishment; a 1904.41 submission duty; more than a handful of cases a year, or cases that run past a quarter; a privacy case; a change in who keeps the record; or a year in which the 300A and the log disagreed and nobody could say why. Those are the conditions under which the rules the template does not enforce start producing wrong records on their own — and the <a href="https://logstead.app/blog/osha-recordkeeping-software-small-business-what-it-must-do">buyer’s checklist for recordkeeping software</a> is built from exactly those rules, so you can hold any tool to them. Moving to <em>what</em> is a separate question, and a category-level one before it is a product-level one — <a href="https://logstead.app/blog/ehs-software-alternatives-small-employers">the alternatives map</a> covers full EHS suites, recordkeeping-focused tools, and staying on the spreadsheet, with what each genuinely does better. <a href="https://logstead.app/blog/osha-recordkeeping-software-prices-compared">The price comparison</a> adds what nine of those tools publish as their price.</p><p>If you do move, you do not start over. LogStead <a href="https://logstead.app/import-osha-300-log">imports an existing spreadsheet 300 Log</a> from CSV or Excel — it matches your column headings to the official fields, validates every row against the same rules described above, and flags the day counts, outcome columns, and dates that need a second look before anything is recorded. From there the record keeps its own rules: calendar-day counts that keep accruing and cap at 180, privacy-case names suppressed on the log and every export, a 300A whose totals come from the log by construction, and the ITA CSV — including the 300/301 case file — generated in OSHA’s layout rather than re-keyed. The <a href="https://logstead.app/tools/recordability-checker">free recordability checker</a> and the <a href="https://logstead.app/demo">live demo</a>, which runs on sample data with no account, are the quickest way to see whether that is worth more to you than the template.</p><p><em>Originally published at </em><a href="https://logstead.app/blog/free-osha-300-log-excel-template-where-it-works-where-it-breaks"><em>https://logstead.app</em></a><em> on August 22, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bd3434a1516" width="1" height="1" alt=""><hr><p><a href="https://medium.com/logstead-blog/free-osha-300-log-excel-template-where-it-breaks-7bd3434a1516">Free OSHA 300 Log Excel Template: Where It Breaks</a> was originally published in <a href="https://medium.com/logstead-blog">LogStead Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSHA Recordkeeping Software for Small Business]]></title>
            <link>https://medium.com/logstead-blog/osha-recordkeeping-software-for-small-business-328bf3c6f3ba?source=rss----645c4801a777---4</link>
            <guid isPermaLink="false">https://medium.com/p/328bf3c6f3ba</guid>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[workplace-safety]]></category>
            <category><![CDATA[osha]]></category>
            <dc:creator><![CDATA[Ervin Amaya]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 00:02:14 GMT</pubDate>
            <atom:updated>2026-11-10T00:02:14.458Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6AiYwm6NwjtL02Do" /></figure><p>Shopping for OSHA recordkeeping software has a strange property: the thing you are buying is a way to keep a <em>legal record</em>, 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.</p><p>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? If you have not yet narrowed to a <em>kind</em> of product — full EHS suite, recordkeeping-focused tool, or spreadsheet — <a href="https://logstead.app/blog/ehs-software-alternatives-small-employers">the map of EHS software alternatives for small employers</a> sorts the category first, and this checklist is what you then hold the finalists to.</p><h3>First: Confirm You Have the Obligation at All</h3><p>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:</p><ul><li><strong>Size.</strong> Under 1904.1, a company that had <strong>10 or fewer employees at all times during the last calendar year</strong> 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.</li><li><strong>Industry.</strong> Under 1904.2, establishments in the low-hazard industries listed in Appendix A to Subpart B are partially exempt regardless of size.</li></ul><p>Both exemptions cover <em>recordkeeping</em> only. Even an exempt employer must still <a href="https://logstead.app/blog/osha-severe-injury-reporting-1904-39-8-24-hour-rules">report a fatality within 8 hours and an in-patient hospitalization, amputation, or loss of an eye within 24 hours</a> under 1904.39. If you are near either line, the <a href="https://logstead.app/blog/do-you-need-to-keep-osha-300-log-recordkeeping-exemptions-small-employers">exemption walkthrough</a> resolves it, and the free <a href="https://logstead.app/tools/ita-checker">ITA Submission Checker</a> 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.</p><h3>There Is No Such Thing as “OSHA-Approved” Software</h3><p>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: <em>“OSHA does not approve, endorse, recommend or certify any product or process.”</em> What the letter did confirm is the standard software has to meet: forms generated by software are acceptable if they satisfy the <strong>equivalent-form</strong> 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.</p><p>So compliance is a property of <em>your records</em>, 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 — <em>may</em> you keep the log electronically at all — has a longer treatment in <a href="https://logstead.app/blog/keep-osha-300-log-electronically-equivalent-forms-1904-29">our post on the equivalent-form and e-storage rules</a>; the answer is an unambiguous yes.)</p><h3>The Buying Checklist: Part 1904 as a Feature List</h3><p>Here is the obligation surface, duty by duty, phrased as the question to ask of any tool — including the spreadsheet you already have.</p><h3>1. Does it make the recordability decision reproducible — and documented?</h3><p>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 <strong>seven calendar days</strong> from learning that a recordable case occurred to enter it on the 300 Log and 301. The <a href="https://logstead.app/blog/is-this-injury-osha-recordable">full decision tree</a> is the deepest page on this site for a reason.</p><p>The buying question is not “does the software have a wizard.” It is: <strong>when an inspector or an attorney asks why case 14 was recorded and case 15 was not, can you show the reasoning?</strong> 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.</p><h3>2. Does it keep the three forms consistent by construction?</h3><p>Part 1904 is three documents that must agree: the <strong>300 Log</strong> (one line per case), the <strong>301 Incident Report</strong> (one detailed form per case, also due within seven days), and the <strong>300A Annual Summary</strong> (year-end totals that must equal the sum of the log). Our <a href="https://logstead.app/blog/how-to-fill-out-osha-300-log">guide to filling out the 300 Log</a> 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.</p><p>Three sub-rules separate real recordkeeping software from a form-filler:</p><ul><li><strong>Privacy cases.</strong> 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 <strong>separate, confidential list</strong> 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 <a href="https://logstead.app/blog/osha-privacy-concern-cases-300-log-1904-29">the privacy-case post</a>.</li><li><strong>Day counts.</strong> Columns K and L accrue in <strong>calendar days</strong>, capped at <strong>180</strong> 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 <a href="https://logstead.app/blog/counting-days-away-restricted-work-osha-300-log-1904-7">how to count days away and restricted days</a>.</li><li><strong>300A reconciliation.</strong> 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.</li></ul><h3>3. Does it run the deadline clocks — all six of them?</h3><p>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:</p><p>Two of these are commonly missed by tools built around the annual summary alone. The <strong>posting</strong> duty requires a <strong>physical</strong> copy on the wall — electronic posting does not satisfy it — certified by a <em>company executive</em> 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 <strong>access</strong> duties in <a href="https://logstead.app/blog/can-employees-see-osha-300-log-access-rights-1904-35">1904.35</a> and 1904.40 mean “can I produce a clean copy of the form right now” is a live compliance test, not a convenience feature.</p><h3>4. Does it produce the ITA submission — the right data, in the right format?</h3><p>Electronic recordkeeping (1904.29) and electronic <em>submission</em> (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:</p><ul><li><strong>250 or more employees:</strong> submit 300A data every year.</li><li><strong>100 or more employees in an Appendix B (Subpart E) high-hazard industry:</strong> submit <strong>300A, 300, and 301</strong> data — the case-detail files, not just the summary.</li><li><strong>20 to 249 employees in an Appendix A designated industry:</strong> submit 300A data.</li></ul><p>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 <a href="https://logstead.app/blog/how-to-submit-osha-data-electronically-ita-portal">ITA walkthrough</a> covers the portal itself; the free <a href="https://logstead.app/tools/ita-csv-validator">ITA CSV Validator</a> 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.</p><h3>5. Does it keep an audit trail across the five-year retention window?</h3><p>1904.33(a) requires you to keep the 300 Log, the privacy-case list, the 300A, and the 301 forms for <strong>five years</strong> following the end of the calendar year they cover — and 1904.33(b)(1) is the part people forget: during that window you <strong>must update the stored 300 Log</strong> 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 <strong>append-only history</strong>: who changed what, when, and from what — the record of the record. The <a href="https://logstead.app/blog/how-long-keep-osha-records-retention-updating-1904-33">retention post</a> walks the update-the-log duty in detail.</p><h3>6. Does it keep one log per establishment?</h3><p>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. <a href="https://logstead.app/blog/multi-establishment-osha-recordkeeping-one-log-per-location">Multi-establishment recordkeeping</a> is where single-workbook spreadsheets first start to strain.</p><h3>7. Can you get your history in — and your records out?</h3><p>Two portability questions decide whether a tool is a system or a trap. <strong>In:</strong> 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? <strong>Out:</strong> 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.</p><h3>When a Spreadsheet Is Genuinely Enough</h3><p>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.</p><p>The profile where it works is specific, and worth being honest about:</p><ul><li><strong>One establishment</strong>, so there is one log and one posting.</li><li><strong>A handful of recordable cases a year</strong>, so day counts and classifications can be tracked by hand without drifting.</li><li><strong>No 1904.41 submission duty</strong> (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.</li><li><strong>One person who knows the counting rules</strong> and will still be there next January.</li><li><strong>A calendar</strong> somebody actually owns for February 1 and March 2.</li></ul><p>If that describes you, the money is better spent elsewhere, and the free tools on this site — the <a href="https://logstead.app/tools/recordability-checker">Recordability Checker</a> for the determination, the <a href="https://logstead.app/tools/rate-calculator">Rate Calculator</a> for TRIR/DART, and an <a href="https://logstead.app/tools/300-log-workbook">auto-totaling 300/300A workbook</a> for the log itself — cover the hardest parts without a subscription. Before you build your own, <a href="https://logstead.app/blog/free-osha-300-log-excel-template-where-it-works-where-it-breaks">where free 300 Log templates work and where they break</a> is worth ten minutes.</p><h3>Where the Spreadsheet Stops</h3><p>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 <a href="https://logstead.app/blog/keep-osha-300-log-electronically-equivalent-forms-1904-29">electronic-recordkeeping post</a> walks these one by one; the <a href="https://logstead.app/blog/5-osha-recordkeeping-mistakes-that-lead-to-citations">five citation-generating mistakes</a> 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.</p><p>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.</p><h3>Red Flags in a Vendor Pitch</h3><p>A short list of claims that should end an evaluation, or at least prompt a hard question:</p><ul><li><strong>“OSHA-approved” or “OSHA-certified.”</strong> No such status exists; OSHA said so in writing.</li><li><strong>AI decides recordability.</strong> The record of authority needs a deterministic, explainable determination (see the callout above).</li><li><strong>“We submit to OSHA for you.”</strong> The ITA is OSHA’s system; software prepares the file. Ask what happens if the upload is rejected.</li><li><strong>The 300A is a separate data-entry screen.</strong> If totals are typed rather than derived, the year-end review is a reconstruction.</li><li><strong>One log, many sites.</strong> Per-establishment logs are the rule, not an enterprise feature.</li><li><strong>No full export, no printable official-layout forms.</strong> Your four-business-hour clock, their roadmap.</li><li><strong>A trial that requires a card, or a demo that requires a sales call.</strong> 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.</li></ul><h3>Frequently Asked Questions</h3><h3>Do I need OSHA recordkeeping software if I have 15 employees?</h3><p>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 <em>how</em>. One establishment, few cases, one knowledgeable person: a spreadsheet passes. Turnover, multiple sites, or a 1904.41 submission duty are what change the answer.</p><h3>Is there any OSHA-approved recordkeeping software?</h3><p>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.</p><h3>Does using software satisfy the March 2 electronic submission?</h3><p>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.</p><h3>Can I switch from a spreadsheet to software in the middle of a year?</h3><p>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.</p><h3>If I keep everything electronically, do I still have to print anything?</h3><p>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.</p><h3>Buy the Enforcement, Not the Form</h3><p>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. For what nine of those products publish as their price, <a href="https://logstead.app/blog/osha-recordkeeping-software-prices-compared">the price comparison</a> lists them side by side.</p><p>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 <a href="https://logstead.app/import-osha-300-log">import from CSV or Excel</a> 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 <a href="https://logstead.app/demo">live demo</a>, no account required.</p><p><em>Originally published at </em><a href="https://logstead.app/blog/osha-recordkeeping-software-small-business-what-it-must-do"><em>https://logstead.app</em></a><em> on August 16, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=328bf3c6f3ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/logstead-blog/osha-recordkeeping-software-for-small-business-328bf3c6f3ba">OSHA Recordkeeping Software for Small Business</a> was originally published in <a href="https://medium.com/logstead-blog">LogStead Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are Mental Health Conditions OSHA Recordable?]]></title>
            <link>https://medium.com/logstead-blog/are-mental-health-conditions-osha-recordable-8e9932e3a186?source=rss----645c4801a777---4</link>
            <guid isPermaLink="false">https://medium.com/p/8e9932e3a186</guid>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[workplace-safety]]></category>
            <category><![CDATA[osha]]></category>
            <dc:creator><![CDATA[Ervin Amaya]]></dc:creator>
            <pubDate>Mon, 02 Nov 2026 03:23:46 GMT</pubDate>
            <atom:updated>2026-11-02T03:23:46.608Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iHUcjZ-y4AyXdIht" /></figure><p>A warehouse employee witnesses a fatal forklift accident and, months later, hands HR a psychologist’s letter diagnosing work-related post-traumatic stress disorder. Does that case go on the OSHA 300 Log?</p><p>For twenty-five years, the answer lived in a single unusual provision — <strong>29 CFR 1904.5(b)(2)(ix)</strong> — that made mental illness the most employee-controlled determination in all of Part 1904. The employer had no duty to ask, no right to guess, and no obligation to record anything unless the employee voluntarily delivered a qualifying medical opinion. And on <strong>July 21, 2026</strong>, the U.S. Court of Appeals for the Fifth Circuit threw the whole framework into question: in <em>Exxon Mobil Corp. v. OSHRC</em>, №25–60108, the court held that OSHA never had statutory authority to require employers to record work-related mental illnesses at all, and vacated the rule itself.</p><p>That decision is days old as this post publishes, and its practical reach is still settling. So this post does two jobs: it walks the rule as OSHA wrote it — which is still what your recordkeeping software, your state plan, and most compliance guidance are built around — and then it walks the decision, what it changed, and the conservative course for a small employer while the dust settles.</p><h3>How the mental illness rule works</h3><p>Mental illness enters Part 1904 through the work-relatedness exceptions. Under 1904.5(a), an injury or illness is work-related if an event or exposure in the work environment caused or contributed to it. Then 1904.5(b)(2) lists nine situations that are <em>not</em> work-related even when they surface at work — the same list that handles <a href="https://logstead.app/blog/is-this-injury-osha-recordable">the common cold, commuting accidents, and personal tasks</a>. The ninth exception is mental illness, and it works differently from the other eight. The regulation’s text:</p><blockquote><em>Mental illness will not be considered work-related unless the employee voluntarily provides the employer with an opinion from a physician or other licensed health care professional with appropriate training and experience (psychiatrist, psychologist, psychiatric nurse practitioner, etc.) stating that the employee has a mental illness that is work-related.</em></blockquote><p>Read that carefully and three design choices jump out.</p><p><strong>The employee holds the key.</strong> Every other work-relatedness call in Part 1904 is the employer’s to make. This one is triggered only by the employee’s voluntary act of handing over a qualifying opinion. You are under no obligation to seek out mental-health information from your workforce, and you should not: soliciting diagnoses creates legal exposure under other laws (the ADA’s limits on medical inquiries, for a start) and buys you nothing under Part 1904. If no qualifying opinion ever lands on your desk, there is nothing to record — full stop.</p><p><strong>Not every provider’s opinion opens the gate.</strong> The rule requires a physician or other licensed health care professional <em>with appropriate training and experience</em> in mental health — the regulation’s own examples are a psychiatrist, psychologist, or psychiatric nurse practitioner. That qualifier has teeth in practice. In the Exxon case that reached the Fifth Circuit, an employee submitted PTSD diagnoses from two licensed clinical social workers and from his primary-care physician, and the employer took the position that none of the three had the appropriate specialized training under the rule. It was only when a psychologist ran a full battery of assessments and diagnosed work-related PTSD that the employer conceded a qualifying opinion existed. A diagnosis note from a family-practice visit is not automatically enough.</p><p><strong>The opinion must connect the illness to work.</strong> The professional has to state both that the employee has a mental illness <em>and</em> that it is work-related. A diagnosis alone, with no causal opinion, does not make the case recordable.</p><p>OSHA’s preamble to the January 2001 recordkeeping rule added one more feature: the employer is not required to take the employee’s provider’s word as final. If you do not believe the reported mental illness is work-related, the preamble says, you “may refer the case … for a second opinion” (66 Fed. Reg. 5916, 5953, Jan. 19, 2001). In the Exxon litigation, the dueling-opinions scenario played out in full — the employee’s psychologist said work-related PTSD, the employer’s designated psychologist reviewed the file and said no, and the employer went with its own expert. Whether an employer may resolve that conflict in its own favor was one of the questions the case teed up; the Fifth Circuit never reached it, because it decided the rule itself was invalid.</p><h3>After the gate: the ordinary recording criteria</h3><p>Passing the 1904.5(b)(2)(ix) gate makes the case <em>work-related</em>. It does not by itself make the case <em>recordable</em>. From there, a mental illness case runs through exactly the same <a href="https://logstead.app/blog/is-this-injury-osha-recordable">general recording criteria</a> in 1904.7 as a laceration or a strained back:</p><ul><li><strong>Medical treatment beyond first aid.</strong> Prescription medication is medical treatment, so a work-related PTSD or anxiety case managed with prescribed medication meets a recording criterion. Psychotherapy and counseling are treatment as well; note that OSHA’s closed first-aid list — the fourteen items in 1904.7(b)(5)(ii), covered in <a href="https://logstead.app/blog/first-aid-vs-medical-treatment-the-line-that-decides-recordability">first aid vs. medical treatment</a> — is a list of physical interventions, so mental-health care that goes beyond a one-time conversation generally is not “first aid.”</li><li><strong>Days away, restriction, or transfer.</strong> A provider keeping the employee off work, or the employer restricting duties because of the condition, triggers the same <a href="https://logstead.app/blog/counting-days-away-restricted-work-osha-300-log-1904-7">day-counting rules</a> as any physical case, including the 180-day cap.</li><li><strong>Significant diagnosed condition.</strong> A significant illness diagnosed by a physician or other licensed health care professional can be recordable even without treatment or lost time.</li></ul><p>On the 300 Log itself, a recordable mental illness is classified in column M(6), “all other illnesses” — the form has no mental-health-specific category.</p><p>And one more layer applies automatically: a recordable mental illness is a <strong>privacy concern case</strong> under 1904.29(b)(7)(iii). You enter “privacy case” instead of the employee’s name on the 300 Log, keep the real name on a separate confidential list, and consider masking descriptive details in a small workplace where the facts alone would identify the person. We cover that machinery — all six privacy categories, the confidential list, and who may see what — in <a href="https://logstead.app/blog/osha-privacy-concern-cases-300-log-1904-29">privacy concern cases on the 300 Log</a>. The two provisions stack in the employee’s favor by design: the employee controls whether the case exists, and if it does, the name is suppressed from the start.</p><h3>What the Fifth Circuit decided in Exxon Mobil v. OSHRC</h3><p>The case grew out of a December 2021 explosion at ExxonMobil’s Baytown, Texas refinery. During repairs, a pipe in a hydrodesulfurization unit ruptured; the hydrocarbon release caused a major fire that burned for eight hours. A process technician — “Employee 2” in the litigation — twice entered the burning unit alongside company firefighters to help close fuel valves. Afterward, he sought counseling, and over the following months four different providers — two licensed clinical social workers, his primary-care physician, and finally a psychologist — diagnosed PTSD stemming from the fire.</p><p>Exxon accepted that the psychologist’s opinion met the 1904.5(b)(2)(ix) qualification bar but referred the file to its own designated psychologist, who concluded the employee did not have work-related PTSD. Exxon declined to record the case. The union reported it, OSHA cited Exxon for an other-than-serious recordkeeping violation, and an administrative law judge affirmed the citation with a <strong>$691 penalty</strong>. Exxon petitioned the Fifth Circuit for review.</p><p>The court never resolved who was right about the diagnosis. Instead it asked a more basic question: did Congress ever give OSHA the power to require recording of <em>mental</em> illnesses? The recordkeeping statute, 29 U.S.C. § 657(c)(2), directs the Secretary of Labor to require records of “work-related deaths, injuries and illnesses other than minor injuries requiring only first aid treatment.” Applying <em>Loper Bright</em> — the 2024 Supreme Court decision requiring courts to find the <em>best</em> reading of a statute rather than deferring to a merely plausible agency reading — the panel concluded that “illnesses” in that statute, read in context and against dictionaries contemporaneous with the 1970 Act, “refers to physical, and not mental, work-related ailments and conditions.”</p><p>The remedy was sweeping. The court granted Exxon’s petition and vacated not just the citation and penalty but “the rule itself” — 29 CFR 1904.5(b)(2)(ix), the mental illness provision that had been on the books since the 2001 recordkeeping overhaul.</p><h3>What the decision does — and doesn’t — settle</h3><p>A five-day-old circuit decision is a moving target, and it would be a mistake to read it as the final national word. Here is the honest state of play as of publication:</p><ul><li><strong>The core holding:</strong> the federal recordkeeping statute, as this panel reads it, does not authorize OSHA to require employers to record work-related mental illnesses. Within the Fifth Circuit (Texas, Louisiana, Mississippi — all federal-OSHA states for private employers), that is now controlling law.</li><li><strong>The vacatur:</strong> the panel purported to vacate the rule itself, not merely to set aside one citation. The Fifth Circuit treats vacatur of an agency rule as wiping the rule off the books, which would reach beyond the three states. How OSHA, the OSHRC, and other circuits will treat that remedy is not yet established.</li><li><strong>What could still change:</strong> the government can seek rehearing en banc or Supreme Court review, and OSHA has not, as of this writing, issued guidance on how it will apply the decision. A future Congress could also amend the statute — the court was explicit that the fix, if there is to be one, is legislative.<strong>Update, September 5, 2026 (corrected October 21; see the next note):</strong> the 45-day window for the government to seek panel or en banc rehearing (Federal Rule of Appellate Procedure 40 gives a United States agency 45 days, not 14) closed on September 4. The public docket mirror shows no rehearing petition and lists the mandate issue date as <strong>September 11, 2026</strong> — the schedule that applies when no petition is filed (FRAP 41(b): seven days after the rehearing window). We have not pulled the PACER docket itself, so read this as “none visible,” not “none filed.” A petition for certiorari remains possible until <strong>October 19, 2026</strong> (Supreme Court Rule 13.1: 90 days from the July 21 judgment). OSHA has still published no guidance, and its online text of 1904.5 still shows (b)(2)(ix) unannotated.<strong>Update, October 21, 2026, correcting the September 5 note:</strong> the government did ask for rehearing. The Fifth Circuit’s docket shows a petition for rehearing filed on September 4 by the Acting Secretary of Labor. Our September 5 note said none was visible. On September 22 the court denied the petition and set the mandate to issue on September 29. That moved the Supreme Court deadline. When a timely rehearing petition is filed, the 90 days run from the denial of rehearing, not from the judgment (Supreme Court Rule 13.3), so a petition for certiorari is due by <strong>December 21, 2026</strong>. A Justice can extend that by up to 60 days, on an application filed at least 10 days before it is due except in extraordinary circumstances (Rule 13.5). As of October 21, the Supreme Court’s docket search shows no petition or extension application in this case. OSHA has published no guidance that we can find, and its online text of 1904.5 still shows (b)(2)(ix) unannotated.</li><li><strong>State plans are their own question.</strong> Roughly half the states run OSHA-approved state plans that enforce their <em>own</em> recordkeeping rules — adopted nearly verbatim from federal Part 1904 but existing under state law. A federal court’s reading of the federal statute does not automatically strike a state’s identical rule. If you operate in a state-plan state (California, Washington, Oregon, and many others), assume your state’s mental illness recording provision remains in effect unless and until your state says otherwise. Multi-state employers should expect a patchwork; the same logic that makes <a href="https://logstead.app/blog/multi-establishment-osha-recordkeeping-one-log-per-location">each establishment subject to its own state’s rules</a> applies here.</li><li><strong>Everything outside Part 1904 is untouched.</strong> The decision is about one recordkeeping provision. Workers’ compensation for mental injuries, ADA accommodation duties, FMLA leave, and any state workplace mental-health requirements all operate on their own rules — the same <a href="https://logstead.app/blog/workers-comp-denied-osha-recordable-two-systems-explained">two-systems separation</a> that has always kept comp determinations and OSHA determinations independent.</li></ul><h3>What a small employer should actually do now</h3><p>The practical playbook barely changes, because the rule’s employee-triggered design always meant there was nothing to do until a qualifying opinion arrived:</p><ol><li><strong>Never solicit.</strong> Do not ask employees whether work is affecting their mental health for recordkeeping purposes, and do not go hunting for diagnoses after a traumatic incident. That was true under the rule, and it remains true after it.</li><li><strong>If an employee hands you a provider opinion, read it against the three requirements:</strong> a licensed professional with appropriate mental-health training, a stated diagnosis, and a stated work connection. Document what you received and when.</li><li><strong>Check your jurisdiction.</strong> Federal-OSHA state? The Fifth Circuit has vacated the federal rule, and at minimum the decision is controlling in Texas, Louisiana, and Mississippi — but OSHA’s nationwide response is still unwritten. State-plan state? Treat your state’s rule as live and record when the criteria are met.</li><li><strong>If you record, record it as a privacy case</strong> — “privacy case” in the name column, confidential list, M(6) classification, and the description-masking discretion where needed.</li><li><strong>Support is separate from recordkeeping.</strong> EAP referrals, counseling after a traumatic incident, and time off are good practice regardless of what Part 1904 requires. In the Exxon case, the employer’s grief counselors and EAP were how the employee got care; none of that depended on whether a log entry was ever made.</li><li><strong>Date-stamp your decisions.</strong> This area of law just moved and may move again. A file note that says what rule you applied and why, on what date, is cheap insurance.</li></ol><p>However this litigation resolves, the recordability analysis for everything else on your log is unchanged — and it still has to be run case by case, against the current text of the rules. LogStead’s recordability wizard walks each incident through the work-relatedness exceptions and the 1904.7 criteria in order, flags privacy concern cases so the name never reaches the 300 Log view, and keeps the confidential name list where only the right people can see it. You can test the decision logic free with the <a href="https://logstead.app/tools/recordability-checker">recordability checker</a> — no signup required.</p><p><em>This post is general compliance information, not legal advice — and it describes active litigation current as of July 26, 2026. Verify the status of</em> Exxon Mobil Corp. v. OSHRC <em>and any OSHA response before relying on it, and check your state plan’s requirements, which may differ from federal law.</em></p><p><em>Originally published at </em><a href="https://logstead.app/blog/mental-health-condition-osha-recordable-ptsd-1904-5"><em>https://logstead.app</em></a><em> on July 26, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e9932e3a186" width="1" height="1" alt=""><hr><p><a href="https://medium.com/logstead-blog/are-mental-health-conditions-osha-recordable-8e9932e3a186">Are Mental Health Conditions OSHA Recordable?</a> was originally published in <a href="https://medium.com/logstead-blog">LogStead Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>