Built for the Safety Director whose firm runs projects in six states under 22 state OSHA plans plus federal — and a recordability call that has to be defensible eighteen months later.

SE's answer

One platform, every state's variant — resolved per establishment.

SE's state-plan registry covers all 29 US OSHA jurisdictions — 22 state plans covering private + public employers plus 7 public-employee-only plans — alongside federal OSHA. Each Establishment carries its jurisdiction; the Recordability Wizard knows which 1904.7 variant applies; Form 300 / 300A / 301 emit the right version automatically. The Cal/OSHA Form 5020 variant ships as a first-class peer to federal Form 300A. 1904.39 severe-injury reporting fires the 8-hour and 24-hour countdowns and routes to the right OSHA Area Office across 10 federal regions + every state.

Annual ITA submission (29 CFR 1904.41) lands electronically each March from the canonical incident records — no parallel data entry into OSHA's portal. The annual Form 300A posting cycle (29 CFR 1904.32) renders the summary from the same data layer. Plus Netherlands Arbeidsinspectie + UK HSE coverage for the international establishments that fall outside the US OSHA cascade.

22+7 US state plans + federal

Form 300 variant resolved per Establishment via jurisdiction dispatch.

ITA + 300A + severe-injury

1904.41 electronic submission + 1904.32 annual posting + 1904.39 countdowns.

SE's answer

Hazard → control → corrective-action lifecycle, with closure-gating.

Hazards captured via mobile + photo + GPS land in a 5×5 ALARP-aligned risk matrix. The hierarchy of controls is modelled as per-control entities with a forward-only lifecycle — Elimination, Substitution, Engineering, Administrative, PPE — and a hazard can't be resolved until at least one control is Verified. Extreme-tier hazards (score ≥ 17) surface an "RCA Recommended" banner before an incident has happened. The Construction IndustryPack pre-seeds 10 construction-specific hazard categories — Falls from Heights, Excavation Collapse, Crane / Lifting, Falling Objects, Scaffolding, Power Tools, Heavy Equipment, Trenching, Concrete Pour, Demolition — on top of the 22 universal categories.

When an incident does fire, the recordability cascade pulls the hazard history forward: the matched hazard, its controls, their verification state at the time. Root-cause analysis via 5-Whys or Fishbone attaches to both the incident and the originating hazard. Corrective actions track to completion and gate incident closure — an incident with open corrective actions stays open. The investigator question "when was this hazard identified and why wasn't it controlled" answers itself from the platform's audit trail.

SE's answer

A first-class Subcontractor Incident category in the IndustryPack.

The Construction IndustryPack pre-seeds a Subcontractor Incident category alongside the construction-specific hazard set. Capturing the incident under that category records the supervising employer + the subcontractor's employer name + the work-coordination context — so the 1904.31 determination is documented at intake rather than reconstructed from memory at audit. Every state-plan jurisdiction that recognises a parallel rule gets the same shape; international jurisdictions (NL / UK) capture the local-equivalent under the same entity.

The subcontractor-management surface is now live: a contractor roster with approval status and certificate-of-insurance documents, scored pre-qualification, per-worker rosters that track each worker's certifications and licences (OSHA 10/30, CDL, and the rest — with the same expiry alerts your own employees get), site-access clearances per site and window, and on-site field audits. Workers can be invited to a read-only self-service portal to see their own profile, credentials, and cleared sites. Still on the roadmap: letting contractors update their own records from that portal, and proof-of-coverage exports to a general contractor's portal.

SE's answer

Mobile-first capture meets the supt where the work is.

Mobile-optimised hazard reporting with photo + GPS pinning. Mobile observation capture against per-tenant Work Observation Item templates (the supervisor's audit ticket is a structured form, not a free-text field that misses the data the inspector wants). PWA support with offline data caching so a remote site without cell service still records every observation; queued changes sync when connectivity returns. The construction-specific incident wizard surfaces the right form per the project's NAICS + jurisdiction — 1926 versus 1910 derivation flows from the Establishment, not from supervisor judgment in the moment.

The platform meets superintendents where they are; the trailer's only job is end-of-week review. AI-assisted intake — voice dictation and audio-to-structured-fields transcription — is on the roadmap, building on the shipped mobile, offline, photo, and GPS layer.

SE's answer

Recordability codified — 1904.7 cascade with cited reasoning, audit-defensible overrides.

SE's Recordability Wizard codifies 29 CFR 1904.7 as a 6-step decision tree with cited reasoning on each branch. The right OSHA standard (1926 or 1910) flows from the Establishment's industry classification (NAICS code) — set per project at onboarding. Overrides are written-justification-required and audit-trailed; an inspector eighteen months later sees the determination, the cited regulation, and the override reasoning in one view.

DART vs. other-recordable classification flows automatically into Form 300. Lost-time day counting respects OSHA's max-180 rule. Severe-injury reporting countdowns under 1904.39 fire on hospitalizations, amputations, and fatalities. ITA submission lands the records electronically each March (29 CFR 1904.41). The 1904.31 supervising-employer rule for subcontractor incidents is captured at intake via the Subcontractor Incident category (see Pain 03); a fully-automated 1904.31(b) day-to-day-supervision predicate that pre-fills the determination is on the roadmap.