Appearance
OSHA 300 management
Live now
GoSafety OSHA 300 management provides a running OSHA 300 case log in the web app plus supporting API endpoints. The product stores case-level injury and illness data over time instead of treating OSHA 300 as a year-end spreadsheet only.
Snapshot
| Item | Details |
|---|---|
| Who uses it | Safety managers, office admins |
| Current status | Live now |
| Main surface | Web plus API |
| Related pages | Injury forms, OSHA 300A management and calculations per hour worked |
What it is
This workflow manages the OSHA 300 running log. Each case stores the intake facts, recordability state, classification, injury type, and tracked day counts that can change after the initial incident.
Who uses it
- Safety managers maintaining the annual log.
- Office admins reviewing case details and updates.
- Teams connecting injury submissions into OSHA intake.
Step-by-step workflow
- A case is created through the OSHA API or through mapped claims-style submission plumbing.
- The case is stored with recordability, classification, injury type, incident details, and linked references.
- The web app displays the annual running log at
/osha300. - Managers update the case as more facts become known.
Data captured
- Employee identity fields and optional employee ID.
- Incident date, location, and description.
- OSHA case number.
- Recordability: pending, recordable, or not recordable.
- Classification: death, days away, job transfer or restriction, or other recordable.
- Injury type values.
- Days away and days restricted plus related start and return dates.
- Establishment ID and optional links to attestation and time entry records.
Outputs and downstream effects
- An annual OSHA 300 running log.
- Yearly summary data used by the 300A page.
- API summary output for recordable totals.
- A structured source of truth for case-level OSHA tracking.
Device and platform context
- Current management is a web and API workflow, not an iOS-first workflow.
- Existing create flows auto-assign the organization's default establishment if one is not provided.
Practical construction examples
- Recording a fall, struck-by, or lifting injury that may stay pending until recordability is confirmed.
- Updating days away from work after the employee's return date is known.
- Auto-creating an OSHA 300 intake case from a mapped injury submission.
Limitations and notes
- Establishment support exists, but not every create flow exposes establishment selection directly to users.
- The current codebase does not provide a separate dedicated OSHA 301 manager.
- OSHA 300A is a separate workflow and page, not the same record surface.