Recordable Determinations: 30-Day OSHA Audit Guide
A 30-day OSHA recordkeeping audit helps senior EHS leaders test recordable determinations, severe-injury reporting, and 300A readiness.
Principais conclusões
- 01Freeze the full case universe before judging the OSHA 300 log, because missing clinic, HR, or supervisor records can hide classification errors.
- 02Separate recordkeeping from severe-injury reporting so fatalities, hospitalizations, amputations, and eye-loss events receive the timing review OSHA requires.
- 03Rebuild work-relatedness, medical treatment, restriction, transfer, and diagnosis decisions from evidence rather than supervisor memory or dashboard pressure.
- 04Reconcile recordable cases with SIF exposure, DART interpretation, corrective-action aging, and reporting trust before executives rely on the annual summary.
- 05Use Headline Podcast conversations to move injury data review from paperwork compliance into a leadership discussion about credibility, prevention, and care.
The Bureau of Labor Statistics reported 5,070 fatal work injuries in the United States in 2024, which means a worker died every 104 minutes according to the 2024 Census of Fatal Occupational Injuries. This guide shows senior EHS leaders how to audit recordable determinations in 30 days before OSHA data becomes a public trust problem, not just a compliance file.
Why recordable determinations deserve executive attention
Recordable determinations decide whether an injury or illness belongs on the OSHA 300 log, but the real decision is whether the organization can tell the truth about harm without turning the log into a negotiation. OSHA recordkeeping under 29 CFR 1904 sets the rule, while leadership behavior decides whether supervisors preserve facts or pressure cases toward the cleanest possible dashboard.
On the Headline Podcast, Andreza Araujo and Dr. Megan Tranter often bring safety back to leadership credibility, because a number that cannot survive questioning cannot guide prevention. That is the deeper issue with recordability. A wrong entry may pass unnoticed for months, although the same classification habit can also hide weak controls, case management pressure, and emerging serious risk.
This 30-day audit works best for a multi-site operation, a high-hazard business, or a company preparing OSHA 300A submission and executive review. It does not replace legal advice. It gives the EHS leader a disciplined way to test decisions before they harden into annual data.
Step 1: Freeze the case universe before judging the cases
A recordkeeping audit starts with the full universe of injuries, illnesses, first-aid cases, near misses with medical evaluation, contractor interface events, and cases moved into occupational health review. If the audit begins only with the OSHA 300 log, it cannot find what was never entered.
The common failure is procedural tunnel vision. Teams compare the log against itself, then celebrate consistency. Co-host Andreza Araujo's book Safety Culture: From Theory to Practice makes the harder point that culture is visible in ordinary decisions, including which facts receive attention and which facts are made administratively inconvenient.
Build a single case list from clinic records, supervisor reports, HR absence files, restricted-duty rosters, workers' compensation notices, incident investigations, and EAP or ergonomic referrals when those referrals relate to a possible work-related condition. Then assign each case a temporary audit ID so the review can test completeness without debating names in the first meeting.
Step 2: Separate recordkeeping from reporting within the first week
OSHA recordkeeping and OSHA severe-injury reporting are related duties, but they are not the same decision. OSHA's severe injury rule requires employers to report a work-related fatality within 8 hours and an in-patient hospitalization, amputation, or eye loss within 24 hours, while the OSHA 300 log records qualifying injuries and illnesses under the recordkeeping standard.
This distinction matters because executives often ask one blended question: did we report it? A case can be recordable without triggering the severe-injury reporting rule, and a severe event can also expose a weak classification process whose consequences reach the annual summary.
Create two review columns, one for recordability and one for severe-injury reporting. When an amputation, inpatient admission, eye loss, or fatality appears in the case universe, require a documented timestamp for management knowledge, notification decision, and confirmation path. Then link the resulting decision to serious incident potential classification so the company does not confuse legal threshold with risk severity.
Step 3: Rebuild the work-relatedness decision from evidence
Work-relatedness is the hinge of most disputed recordable determinations, since OSHA generally presumes an injury or illness is work-related if an event or exposure in the work environment caused or contributed to the condition. The audit should therefore rebuild the decision from evidence, not from the supervisor's first impression.
What most recordkeeping checklists miss is the power dynamic around causation. A plant manager who wants a clean month, an HR team worried about absence cost, and a supervisor whose bonus tracks injury rate can all shape the story before EHS sees the file. That is why Headline's leadership lens matters.
For each case, pull the incident narrative, medical recommendation, task description, shift schedule, exposure information, prior symptoms if documented, and witness notes. The audit question is not whether the company likes the answer. The question is whether the evidence would still support the decision if OSHA, a union representative, or a board safety committee asked for the rationale six months later.
Step 4: Test medical treatment, first aid, restriction, and transfer separately
A case becomes recordable when it meets OSHA criteria such as medical treatment beyond first aid, days away from work, restricted work, job transfer, loss of consciousness, death, or a significant diagnosed injury or illness. The audit must test each trigger separately, because teams often hide a recordable case by focusing on only one dimension.
The most dangerous shortcut is treating the physician note as the whole decision. Medical advice matters, although the employer still owns the recordkeeping determination. A prescription, a rigid splint, physical therapy, or formal work restriction can shift the answer even when the local story still sounds minor.
Build a four-column grid for every contested case: treatment, restriction, transfer, and diagnosis. Put the exact evidence in each cell, not a summary. Then compare the resulting pattern with the organization's DART rate interpretation, because days away and restricted duty can distort executive decisions when the underlying classification process is weak.
Step 5: Audit restricted duty against the real job, not the job title
Restricted duty should be tested against what the employee normally does, not against a generic job title. A maintenance technician who cannot climb, isolate energy, or enter confined spaces may be restricted even if the formal role still says maintenance technician.
In more than 250 cultural transformation projects, Andreza Araujo has seen that organizations often solve discomfort by changing the label rather than changing the risk. Recordkeeping has the same trap. A company may call an assignment normal duty while everyone on the shift knows the person has been removed from essential tasks.
Ask the supervisor to list the worker's regular essential tasks for the preceding 30 days, then compare those tasks with the medical recommendation and actual assignment. If the worker was moved to paperwork, observation, training, or light cleaning because the normal task could worsen the condition, document the reason and test whether the OSHA criteria point to recordability.
Step 6: Reconcile OSHA logs with SIF and leading-indicator data
The OSHA log is a lagging record, which means it should be reconciled with SIF exposure, weak signals, and corrective-action data before leaders treat it as a safety scorecard. A low recordable count can coexist with high serious-risk exposure when reporting trust is poor.
This is where the 30-day audit moves beyond compliance. If a site has few recordables but many high-potential near misses, overdue critical-control actions, or repeated energy-isolation deviations, the executive team should question the story. The clean log may be true, but it may also be too narrow to describe risk.
Cross-check the audited cases against SIF exposure hours, overdue actions, repeated task types, and high-potential reports. The goal is not to force more cases onto the log. The goal is to prevent the log from becoming the only safety narrative leadership believes.
Step 7: Prepare the annual summary and electronic submission evidence
OSHA's Injury Tracking Application requires covered establishments to submit required injury and illness data by March 2 for the prior calendar year, including OSHA 300A data and, for certain establishments, additional 300 and 301 information under the current electronic submission rule. The audit should prove that the annual summary is traceable before the deadline, not after a question arrives.
Senior leaders usually see the annual summary as an administrative finish line. The stronger view is that 300A certification is a governance act. The executive who signs or relies on the summary should know what was checked, which disputes remain, and whether any classification pressure was found.
By day 21, prepare a submission evidence pack with the final log, the annual summary, establishment coverage rationale, headcount basis, NAICS check, case-count reconciliation, and open questions. Keep a short decision memo for each contested case, because memory is not an acceptable control when the same question returns during inspection or due diligence.
Step 8: Turn disputed cases into control questions
A recordable determination audit should end with control questions, because a correct log entry does not prevent the next event. The final week should convert disputed cases into evidence about task design, medical management, supervisor behavior, and reporting trust.
The trap is treating the audit as a correction exercise only. If the team changes three entries but leaves the incentive plan, supervisor briefing, or clinic referral process untouched, the next year will reproduce the same dispute. James Reason's work on latent conditions helps here, since the classification problem often reflects deeper system design rather than one careless form.
For each disputed case, ask three questions: what exposure produced the injury or illness, what organizational condition shaped the decision, and what control change would make the next decision easier and more honest. Then place the resulting action into the same governance rhythm used for corrective action aging.
Comparison: compliance-only review vs leadership audit
| Dimension | Compliance-only review | 30-day leadership audit |
|---|---|---|
| Starting point | Current OSHA 300 log | Full case universe from EHS, clinic, HR, supervisors, and workers' compensation |
| Main question | Is the form complete? | Would the evidence support the decision under scrutiny? |
| Executive view | Annual injury count | Classification quality, reporting trust, and exposure pattern |
| Risk signal | Recordable rate | Recordable rate plus SIF exposure, disputed cases, and overdue control actions |
| Outcome | Cleaner paperwork | More defensible data and better prevention decisions |
Each month without a recordkeeping audit gives disputed cases more time to harden into annual data, while executives continue making resource decisions from numbers whose evidence chain may be incomplete.
Conclusion: recordability is a leadership system
Recordable determinations are not clerical details, since they reveal whether the organization can classify harm honestly while still looking at the controls that failed. A 30-day audit gives EHS leaders a practical route from case evidence to executive decision, especially when OSHA deadlines, board scrutiny, and public injury data converge.
Headline Podcast is the space where leadership and safety come together to shape better workplaces and better lives. If your leadership team needs a sharper conversation about injury data, reporting trust, and the decisions behind the dashboard, start with the next episode at Headline Podcast.
Perguntas frequentes
What is a recordable determination in OSHA recordkeeping?
How long should an OSHA recordkeeping audit take?
What is the difference between OSHA recordkeeping and severe-injury reporting?
Who should review disputed recordable cases?
How does Headline Podcast connect recordkeeping to leadership?
Sobre a autora
Andreza Araujo
Host & Editorial Lead
Andreza Araujo is an international reference in EHS, safety culture and safe behavior, with 25+ years leading cultural transformation programs in multinational companies and impacting employees in more than 30 countries. Recognized as a LinkedIn Top Voice, she contributes to the public conversation on leadership, safety culture and prevention for a global professional audience. Civil engineer and occupational safety engineer from Unicamp, with a master's degree in Environmental Diplomacy from the University of Geneva. Author of 16 books on safety culture, leadership and SIF prevention, and host of the Headline Podcast.
- Civil Engineer (Unicamp)
- Occupational Safety Engineer (Unicamp)
- Master in Environmental Diplomacy (University of Geneva)