One incident, five obligations
The reporting clocks are unforgiving, and they run in parallel. In the US, a workplace fatality must be reported to OSHA within 8 hours; an in-patient hospitalisation, amputation or eye loss within 24. The UK’s RIDDOR requires deaths and specified injuries reported without delay, and over-seven-day incapacitations within 15 days of the accident. In the UAE, work injuries must be notified within 24 hours, though the reporting channel varies by emirate. Saudi Arabia runs a 24-hour accident notification alongside a three-day insurance window.
And on most GCC and enterprise projects the contract adds a second clock, often a faster one: immediate or 24-hour notice to the engineer or client, a draft investigation in 48 to 72 hours, a final report with corrective actions in 7 to 14 days. Missing the contractual clock can trigger a default notice even when the statutory report went in on time.
One incident, five obligations, five different forms, all of them running at once while the site is still in shock. This multi-regulator fan-out is precisely where manual processes fail — and it is the part software genuinely solves.
What an incident actually costs
OSHA’s own cost model puts indirect costs at roughly 4.5 times direct for smaller injuries — crew standdown, supervision time, retraining, replacement labour — and nearly all of it is uninsured, on contracts running 3–5% margins. The multiplier falls as the injury gets larger, which is the opposite of most people’s intuition: it is the small injury whose hidden tail is disproportionate.
Then the incident prices your future. In the US, injury frequency drives the experience modification rate that scales your premiums and gates your bidding — above roughly 1.0 to 1.2 commonly excludes you from prequalification outright. In the GCC, client HSE questionnaires demanding three-to-five-year LTIFR and fatality history perform exactly the same gating by a different instrument. The tail can outcost the incident.
The role of incident management in performance
Classification discipline drives everything downstream. The severity ladder — near miss, first aid, medical treatment, restricted work, lost time, fatality, plus “dangerous occurrence” for the no-injury high-potential event — determines what gets reported to whom, what gets investigated how deeply, and what enters TRIR versus LTIFR. One convention trips up multinationals constantly: TRIR uses a 200,000-hour base and LTIFR a 1,000,000-hour base. Comparing them across regions without converting produces nonsense, and then someone acts on it.
Honest metrics, or none. Every practitioner knows the games. A “suitable duties” programme that returns an injured worker to light duty on day one makes the lost-time injury vanish from the numbers without changing anything about the injury. That is why sophisticated clients now demand TRIR, DART and SIF-potential rates together — no single number survives contact with a determined case manager.
Near-miss culture is the leading indicator. Underreporting is the norm rather than the exception: systematic reviews put the share of workplace injuries that go unreported anywhere from 20% to 91%, and industry estimates suggest the large majority of near misses are never reported at all. Every metric that punishes reporting — TRIR-linked bonuses, “days since last incident” boards — suppresses exactly the data that predicts serious events. Rising near-miss counts with falling severity is what health looks like, and it looks like failure on a dashboard.
Match the investigation to the potential, not the outcome. 5 Whys for low-severity events: fast, but linear and heavily investigator-dependent. ICAM or a comparable systemic method — failed defences, individual actions, task conditions, organisational factors — for anything with serious potential, because it forces organisational factors into view instead of stopping at the operator. Universal practice either way: preserve the scene, photograph before anything is disturbed, quarantine the equipment, and take witness statements within 24 to 48 hours — separately, because witnesses left together converge on a shared narrative and you lose the independent accounts.
Heinrich’s triangle, and what replaced it
The famous safety triangle holds that a fixed ratio of minor incidents underlies each major one, so driving down the minor ones drives down the major ones. The modern critique — and it matters — is that this is only half true.
Minor-incident data predicts minor incidents. Fatalities and serious injuries have their own distinct precursors, and they are about energy: work at height, lifting operations, energised systems, mobile plant. A site can drive its cut-finger rate to zero and still kill someone, because nothing it did addressed the crane.
Which is why fatality prevention requires tracking high-energy precursors separately, and why a near miss with serious-injury potential deserves a full investigation at zero injury. The outcome was luck. The exposure was real.
What failure looks like
An unreported near miss leaves the hazard in place, and the same failure mode returns at higher energy as a recordable. The late report earns a citation and, worse, a presumption of poor management that colours the whole follow-up inspection. The blame-first investigation produces a name rather than a cause, so the cause repeats. And the paper log means the contractual 48-hour draft deadline arrives before anyone has assembled the timeline.
Every one of those is a records-and-workflow failure before it is a safety one. That is the whole argument for running incidents on a system rather than in a binder.
How Zepth runs incident management
One incident record drives everything. Classification sets the reporting obligations and starts their clocks. Notifications route to the right parties with deadlines visible. Investigation evidence — photographs, statements, the timeline — attaches to the record rather than living in someone’s phone. Corrective actions carry owners, deadlines and verified closure.
TRIR, LTIFR and DART compute from live data with both hour bases handled, so a regional comparison is a conversion rather than a mistake. The multi-regulator fan-out becomes a checklist with timestamps instead of a scramble.