Generic AI Doesn't Know OSHA. Your Investigation Tool Does.
The output it gave you was thorough. It identified a cause, listed some corrective actions, summarised the incident. Nowhere in that response did it mention OSHA. Nowhere did it flag whether this incident met the threshold for recordkeeping. Nowhere did it note the obligations that applied to your business in your state.
That silence is a problem — because in the US, some workplace incidents carry specific documentation obligations, and not knowing about them doesn't change whether they apply to you.
This article is part of the series Why a Chat Window Isn't an Investigation.
What OSHA Requires — and What a Chat Window Doesn't Know
The Occupational Safety and Health Administration (OSHA) sets federal workplace safety standards across most US industries. For workplace incidents, two OSHA obligations are relevant to many small businesses.
OSHA recordkeeping — Most employers with more than ten employees are required to record certain types of workplace injuries and illnesses on OSHA Form 300 (the Log of Work-Related Injuries and Illnesses). A lost-time injury — one where an employee misses work — is typically a recordable event. The record must be maintained and is subject to inspection.
OSHA reporting — Certain severe incidents — fatalities, in-patient hospitalisations, amputations, or loss of an eye — must be reported to OSHA directly, within defined timeframes (24 hours for hospitalisations, 8 hours for fatalities).
These are federal minimums. State-level plans (such as California's Cal/OSHA or Washington's L&I) may have additional or different requirements.
A general AI tool has general knowledge of OSHA's existence. It does not apply OSHA recordability criteria to the specific incident you described, in the specific jurisdiction where it occurred, to determine what obligations you have. It produces a helpful response to your input — and OSHA compliance is simply not part of what it was designed to address.
What Jurisdiction-Aware Investigation Looks Like
A purpose-built investigation tool for the US market understands that the jurisdiction matters. The state where your business operates, the type of incident, and the severity of the outcome all determine what documentation and reporting obligations apply.
This means surfacing the correct federal OSHA framework for your incident type, identifying whether state-specific regulations apply that go beyond the federal standard, noting whether the incident characteristics suggest OSHA recordkeeping is required, and flagging whether a reporting obligation may be triggered.
It does not replace legal advice. It does not make compliance determinations on your behalf. But it surfaces the regulatory context that is relevant to your incident — so you are aware of what to look into, rather than finding out later that an obligation existed and wasn't met.
The Worked Example: A Lost-Time Injury With No Regulatory Context
A warehouse worker slips on spilled oil near a loading dock in a small manufacturing business and loses time from work. The owner describes the incident to a general AI tool and receives a summary: cause identified, corrective actions listed, narrative produced. The response makes no mention of OSHA. It does not flag that a lost-time injury is typically an OSHA-recordable event. It does not note that OSHA Form 300 may need to be updated. It does not identify the jurisdiction or flag whether any state-specific obligations apply.
The owner files the chat output and moves on. Six months later, during a routine OSHA inspection, the inspector asks to see the Form 300 log. The entry for this incident isn't there — because no one flagged that it needed to be.
A jurisdiction-aware investigation tool would have surfaced the recordkeeping context as part of the investigation process — not as a compliance determination, but as a prompt to ensure the owner is aware of the obligation and can take the appropriate steps.
Want to see how a structured investigation handles this? Start your free trial
The Difference Between Awareness and Compliance
It's worth being precise about what a purpose-built investigation tool does and does not do here.
It surfaces applicable OSHA regulations and codes of practice that are relevant to your incident type and jurisdiction. It incorporates these into the investigation process — the evidence checklist, the root cause analysis, the recommendations. It ensures that what a regulator would look for in a workplace investigation of this type is reflected in what you produce.
It does not determine whether you are legally compliant. It does not file reports on your behalf. It is designed to support the investigation process — and part of a sound investigation process, for a US business dealing with a workplace incident, is understanding what regulatory framework applies.
A general AI tool skips this entirely. It is not built for a specific jurisdiction, a specific industry, or a specific regulatory regime. It responds helpfully in general terms. For most questions, that is fine. For a workplace incident investigation in the US, the regulatory context is not optional background — it is part of the investigation.
As discussed in the series overview, this is one of four gaps between a general AI tool's output and a complete investigation. The others — evidence collection, root cause analysis depth, and completeness checking — each compound this one.
If a regulator reviews your investigation and finds no reference to applicable OSHA standards, that gap works against you. Not as proof of wrongdoing, but as evidence that the process lacked the regulatory awareness a proper investigation requires. A jurisdiction-aware tool closes that gap from the start.