Torres Workforce Health Partners
Your OSHA 300 log already knows where injuries will happen next.
Upload a redacted OSHA 300 log and get a clear pattern read in minutes — where injuries cluster, what’s driving lost time, and how your rates compare. No spreadsheet wrestling. No injury names needed.
Set up the read
Hours worked is what turns a case count into a real rate. If you don’t have it handy, use annual payroll hours (roughly 2,000 hrs per full-time employee).
No hours entered? The read still runs — you’ll get counts, patterns, and severity, just no TRIR / DART rates.
Redact, then upload
Before you share any log — here or anywhere — strip it down:
- Delete the employee name column (and any initials).
- Remove Social Security numbers, dates of birth, and home addresses if present.
- Keep: date, job title, location / department, what happened, injury type, classification, and days away / restricted.
- For privacy-sensitive cases, OSHA lets you write “Privacy Concern Case” in place of a name — that’s enough.
Upload your log
Column names don’t have to match OSHA’s exactly — the analyzer looks for dates, locations, descriptions, classifications, and day counts and maps what it finds. If a column can’t be mapped, that part of the read is skipped and noted, never guessed.
Your pattern read
Cases by month
How cases classified
Classification comes straight from columns G–J of the 300 log: death, days away, job transfer / restriction, or other recordable.
Where it’s happening — by location / department
What’s happening — event patterns in the narratives
Grouped from the “what happened” descriptions: lifting / strain, slips & falls, struck-by, cuts, caught-in, repetitive motion, and more.
Body parts involved
Rate check vs. BLS
Top findings
Ranked by how much each pattern is costing you in cases and lost time — not just by count.
Injury Pattern Read — One Page
Your establishment
HEALTH PARTNERS
Patterns are the easy part. Knowing what to do about them is the work.
A log can show you where injuries cluster. It can’t tell you which fix pays back first, which cases will drive your experience mod for the next three years, or how to build the supervisor and return-to-work habits that keep the pattern from repeating. That’s the conversation worth having.
See the rows that were analyzed ()
What you’ll get
TRIR and DART calculated the OSHA way (per 200,000 hours) and set against the BLS average for your industry — so you know if you’re actually ahead or behind, not just busy.
The department, task language, body part, and month where cases repeat. One strain is an incident. Nine back strains in one area is a system asking to be fixed.
Total days away and restricted days, and the handful of cases usually responsible for most of them — the ones that follow your mod and your premiums.
What a log alone can’t show: near misses, claim dollars, which injuries were preventable, or what your mod is doing. This read is the starting point for that conversation — it is not a compliance audit, and it doesn’t replace reviewing your 300A summary and workers’ comp loss runs.