Skip to content
SentinelHSE
Prove

The day somebody asks you to show your work.

An auditor, a regulator, a client, or a court. The evidence either already exists because the work was done in the system — or it gets rebuilt from four sources and somebody's memory.

Indicators

Counting harm, or preventing it

Lagging indicators tell you how much you already hurt people. Leading indicators are the only ones you can still act on.

Lagging

the count of harm done

TRIRTotal Recordable Incident Rate
recordable cases × 200,000 / hours worked
LTIFRLost Time Injury Frequency Rate
lost-time injuries × 1,000,000 / hours worked
DARTDays Away, Restricted or Transferred rate
per 200,000 hours worked
SeverityLost days per million hours worked
lost days × 1,000,000 / hours worked

Every organisation already reports these. They are necessary, and they arrive too late to change anything.

Leading

what you can still act on

Near-miss ratio
Near misses reported per recordable — rising is good
Safety observations
Hazards and unsafe acts logged before harm
Actions closed on time
The percentage that did not run late
Inspections on schedule
Completed against planned, by site
Toolbox talks held
And signed by the people who attended
Training compliance
Certificates valid, not expired

These cost almost nothing to collect once reporting takes a minute. That is the entire value proposition.

Work out your own rates

The four lagging indicators, on the standard formulas

Exposure

Hours worked: 480,000

Cases in the period

TRIR

5.00

Total Recordable Incident Rate

recordable cases × 200,000 / hours worked

LTIFR

6.25

Lost Time Injury Frequency Rate

lost-time injuries × 1,000,000 / hours worked

DART

2.08

Days Away, Restricted or Transferred

DART cases × 200,000 / hours worked

Severity

95.8

Lost days per million hours worked

lost days × 1,000,000 / hours worked

Standard industry formulas, computed from the figures you enter — nothing here is SentinelHSE-specific. In the platform these are produced automatically from live records, site by site and month by month, with the cases behind every figure one click away.

ISO 45001:2018

Which clause, and where the evidence lives

The artefact an auditor actually asks for. Twelve clauses, mapped to the modules that produce the evidence for each one.

5.4

Consultation & participation of workers

Field reporting · Surveys · Consultations · Toolbox sign-off

6.1.2

Hazard identification & risk assessment

Hazard Reports · Risk Assessments · JHA

6.1.3

Legal & other requirements

Compliance Register

7.2 / 7.3

Competence & awareness

Training & Competency · certificate expiry tracking

7.4

Communication

HSE Notifications · alerts · Toolbox Talks

7.5

Documented information

Every record retained and retrievable

8.1.2

Hierarchy of controls

Elimination to PPE, recorded against each assessment

8.1.3

Management of change

Approval workflow with signatures

8.1.4

Procurement & contractors

Contractor register · prequalification · site access

8.2

Emergency preparedness & response

Emergency Drills · SOS · response records

9.1

Monitoring, measurement & analysis

Dashboards · leading and lagging indicators

10.2

Incident, nonconformity & corrective action

Incident to investigation to action to closure

Stated honestly: the platform is where the evidence for these clauses is captured and produced. Certification audits your organisation, not your software — but this is what you hand the auditor.

Audit trail

Every change, attributed

An HSE system that cannot evidence its own history is a filing cabinet with a login screen.

Every change is recorded

The field, the old value, the new value, the person and the timestamp — captured automatically as records are written.

Attributed to a human

Each request is tagged with the acting user, so “the system changed it” is never the answer.

Wherever it happened

An edit made on a phone in a tank farm is recorded exactly like one made at a desk.

Approvals leave signatures

Who signed, in what order, and when. A permit cannot go active without the signatures its template requires.

Nothing is quietly deleted

Closures and removals are events in the trail, not gaps in it.

The pack exports in minutes

Filter, review, export. PDF for the narrative, Excel for the tables, with a column chooser.

Watch it happen: the ninth scenario traces an auditor's request for a full quarter, from filter to exported pack, in twenty minutes.

See the audit scenario

Hand your IT team the data-protection pack

Where it runs, who can reach what, how location consent works and how you export everything if you ever leave.