OSHA 300 / 300A Recordable Log Builder
Walk through the recordability decision for every injury and illness, then build the OSHA 300 log and 300A summary - with incidence rates - per establishment and year. The AI suggests recordable yes/no with a rationale; you decide.
Enter cases, get an AI-proposed recordable determination and classification with a written rationale, approve or edit each one, then generate a clean OSHA 300 log and 300A summary with TRIR/DART incidence rates - exported as CSV and printable, form-ready output.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account (for email alerts and digests)
- Your injury/illness cases in a Google Sheet or CSV (or you'll enter them by hand)
- Your establishment list plus hours-worked and average headcount per year
The problem this kills
Every recordable-injury season the same scramble starts. Someone digs through emails, urgent-care notes, and a messy spreadsheet trying to remember: was that sprain work-related? Was the antibiotic medical treatment or just first aid? Did the employee end up on restricted duty or days away? Get any of those calls wrong and your OSHA 300 log is wrong - and the 300A summary you post on the wall in February (and now file electronically) is wrong too.
The recordability decision tree is real, it's specific, and it's easy to fumble under deadline. Most teams either over-record (and inflate their rates) or under-record (and risk a citation). And the math at the end - TRIR, DART, hours-worked rates per establishment - gets redone by hand every year.
This tool encodes the decision tree, walks you through each case, and does the math. It never decides for you - it proposes, with a plain-English reason, and you approve.
What you'll build
A private, login-protected web app where your safety team can:
- Enter or import injury/illness cases - date, employee/job, body part, what happened, treatment given, days away/restricted - from a Google Sheet, a CSV, or a built-in form.
- Get an AI-proposed recordability determination for each case: recordable yes/no, the classification (death / days away / restricted or transfer / other recordable), and a written rationale that walks the OSHA decision tree (work-related? new case? beyond first aid? days away or restricted?).
- Review and approve every call. The manager edits or confirms; nothing is final until a human signs off.
- Handle privacy cases correctly (the cases OSHA lets you keep off the visible log).
- Build the OSHA 300 log and the 300A annual summary per establishment and year, with TRIR and DART incidence rates computed from hours worked.
- Export a clean CSV and printable, form-ready output you can post and file.
What's inside the Implementation Plan
A step-by-step runbook you paste into an AI coding agent (Claude Code). It builds the whole thing with you, in plain language, no prior coding needed.
It starts by interviewing you about your business - your establishments, how cases reach you today, the exact fields and naming your incident reports use, your typical and peak case volumes, who makes the recordability call, and your messiest edge cases. Then it reflects a short tailored spec back, gets your thumbs-up, and shapes the data model, validations, and every later step around your answers. You get a tool fitted to how you actually work - not a generic template.
Inside you'll find: the recordability decision tree encoded as guided questions, privacy-case handling, the 300/300A field layout, the TRIR/DART rate formulas, the human approval gate, the audit trail, duplicate guards, and a no-integration CSV fallback so you can build it today.
The governance it includes (this is the point)
- Login so only your team can open the tool.
- Row-level security so each establishment/organization only ever sees its own cases.
- A complete audit trail - every determination, every edit, and the rationale behind it, with who and when.
- A hard human-in-the-loop gate - the AI drafts a recordability call; the EHS manager reviews and approves before any case is posted to the log or the 300A is finalized.
- Duplicate guards keyed on case-id so the same incident can't land on the log twice.
Who it's for
US EHS managers, safety coordinators, and anyone responsible for OSHA recordkeeping who wants the decision tree and the rate math handled consistently - while keeping the final call firmly in human hands. (This tool is a helper, not legal advice.)
You've got this. Open the plan, paste the first prompt, and let's build it.