01
Records are scattered
Permits, maintenance logs, procedures, toolbox talks and emails live in different systems with different owners.
Telha for HSE teams
Reconstruct the
operating context.
After a safety event, connect reports, procedures, maintenance records and approvals into one chronology of what was in force and what was known.
Why it's hard today.
The investigation isn't just what happened at the asset; it's what the paperwork and communications said around it.
02
Versions decide
The question is which procedure version was current at the time, not which one exists today.
03
Regulator timelines are tight
Notifiable events demand a coherent, evidence-backed account within days, not months.
Safety event
The event, in context.
Assemble the operating picture as it stood: the procedure versions in force, the maintenance and permit history, and the communications around the work.
- Procedure versions as they stood
- Maintenance and permit history
- Communications around the event
Case 26-071 · Safety event
5 record classes
Records in force at event time
06:30
Permit to work issuedVersion and approver preserved with the record.
10:15
Event reportedInitial report linked to site, asset and crew.
Scoped by approval.
Sealed by default.
The mandate defines exactly what this case can reach. Everything else in company memory stays sealed.
Inside this case
What the approved mandate opens.
- The site and asset involved
- The event window
- Record classes named in the mandate
- Named roles and reviewers
Stays sealed
What investigators never see.
- Other sites and assets
- Personnel records out of scope
- Data outside the event window
- Any access after closure
Design partner programme
Reconstruct the next safety event properly.
Run one safety event through Telha end to end (records, systems and a chronology that holds up to scrutiny) inside your own environment.