The incapacitation register & injury rates
Person-days, kept apart from crew-hours: the injury door that drafts a stoppage record, the register that stores facts and derives the statutory answers, the deadline chases, and the exposure entries behind AFR/LTIFR.
An injury costs time in a different currency from a stoppage: person-days — one person, away from work or on restricted duty, day by calendar day. SimOps keeps those on the incapacitation register — the HSE register tile of the full-screen Health & Safety surface (H), one drill-in away from the launcher grid — and keeps them strictly apart from the site's crew-hours: wherever the two appear together they render as two blocks with a rule between them and one fixed sentence — different subjects: crew-hours are the site's lost production; days are one person's incapacity; they are never added.
This page is for the safety adviser who runs the register, and for the coordinator or QS who meets its outputs. The crew-hours world is How lost time is counted.
The injury door — one question, asked once
Capturing an incident asks one extra question: "Did the work stop, slow down, or carry on?" (with don't know an honest fourth answer). If the answer is anything but carried on, and the injured person's employer is known, the system drafts a stoppage Blocker for that firm — pre-dated to the accident, with no crew count (nobody is asked for headcounts at an injury), waiting in the triage queue like any suggestion. The employer answers for the count later, on their own panel.
That is the one place a loss record is machine-drafted, and it is bounded on purpose: the draft names the employer the incident named, never a guess; where no employer can be read, the system offers the raise to a person instead of minting an ownerless record; and if the incident is later withdrawn before anyone touched the draft, the draft withdraws with it, on the record.
Asking who employs an injured person is part of the same capture — it decides whose register the case lands in, and who is asked about the stoppage. Not employed on site is an accepted answer.
Facts in, answers derived
The register stores facts: dated periods away from work or on restricted duty, the treatment given, the category of injury, the person's employer and occupation, a fatality where one occurs. Everything statutory is derived from those facts, live:
- Day counts run in calendar days from the day after the accident, weekends included, concatenated across adjacent periods; a gap the periods don't cover breaks the run, and a broken run is flagged on the row ("run broken by 2 uncovered days") so an entry artefact is visible and correctable, never a silent under-count.
- Reporting duties derive limb by limb — the specified-injury report, the over-7-day report, the over-3-day record, the dangerous occurrence, the member-of-public hospital case, and the fatality, anchored on the stamped fatality fact. Most carry their own clock, but not all: the over-3-day limb is a record duty with no report at all, and a fatality stamped after the accident's written-report window has closed must be notified without delay and carries no written-report deadline. The fatality limb itself has no year bound — the year-long look-back is a chase that ends after 365 days, not a limit on the duty. The row's chip shows the most urgent duty and its deadline; recording a report discharges what it discharges and the row says so ("already reported ⟨date⟩"). Where the regulations' wording could be read two ways, the register states the reading it uses on the row rather than deciding silently.
- The severity ladder (fatality, lost-time injury, restricted work, medical treatment, first aid) derives per case for the rates below — a convention beside the statute, never a statutory answer itself.
A nil is also a fact: "none declared (initials, date)" is the employer stating the person lost no time — distinct from "no incapacitation recorded", which is only the register not having been told yet, and which is chased.
Deadlines chase themselves. Each derived duty arms a dated task to the person who owes it — the employer's register-holder for their own people, the principal contractor's band otherwise — naming a case count, an accident date and a deadline, never a name or an injury in the task text. A duty with no owner assigned falls back to the permission band and says so.
Who sees what
The full register — named people, narratives, periods — is the safety band's, under its own grant. A contractor's own safety holder sees their firm's slice only: the cases their firm answers for in law. The commercial band sees none of it: where a blocker was minted from an incident, the commercial side reads a generated label ("Stoppage from incident · 12 Aug 11:05"), never the incident's own text. The statutory extract — the register as the regulations require it kept, filterable, printable — always states any filter applied, so a filtered print can never quietly drop a case.
Exposure and the two rates
The register's foot carries the Exposure & rates band. Each month the site declares its hours worked and headcount (from gate logs, timesheets, or a stated estimate — the method is recorded). Entry is deliberately four-eyes: the commercial side submits, the safety band accepts, and the accepter is never the submitter; a returned month goes back with a reason and is chased until resolved.
From accepted months the band derives the two industry rates — AFR (reportable injury cases per 100,000 hours worked) and LTIFR (lost-time injury cases per 1,000,000 hours) — and both carry a coverage token on their face: "AFR 2.43 (3 of 3 mo)". The honesty mechanism is one-sided by design: the injuries always count in full, and only the hours are limited to what was declared and accepted — so a thin denominator can only make the rate read worse, never better. A register younger than three complete months shows no rate at all ("a rate needs 3 complete months"), and a zero at full coverage prints as an honest 0.00, not a blank. Rates are site-level only — never per firm, and never divided against crew-hours.
Next: Lost time, scene by scene · How lost time is counted
Blockers & lost time guide: Overview · Reviewing & triaging · Raising · How lost time is counted · The ledger · Your firm's panel · Slip & nil returns · Standing cost · The register · Scene by scene · Reference