2026-08-20 · 2 min read · SONIL EHS360
Purpose
Leadership does not need every field field. It needs a small set of signals that answer:
- Are people getting hurt or nearly hurt?
- Are controls closing, or are loops aging?
- Are high-risk authorisations under control?
- Are statutory and ESG reporting inputs trustworthy?
SONIL EHS360 provides workspace and executive-oriented views on tenant data. This guide describes how to use those signals honestly — without inventing industry benchmarks or fake “AI scores.”
Separate FACT from narrative
When you present analytics:
- FACT — counts and statuses taken from system records (open incidents, overdue CAPA, active permits).
- INFERENCE — interpretation (for example, “reporting culture is improving”). Label inference as such.
Future assistive intelligence (see the Phase 18 advanced AI specification in the repository docs) should keep the same discipline. Do not present model output as audited fact.
Core leadership pack (weekly)
| Signal | Why it matters | Typical filters | |---|---|---| | Open incidents by severity | Harm and potential harm in view | Site, severity, status | | Overdue CAPA | Control debt | Site, owner, age | | Verification backlog | Soft-close risk | Site, due date | | Active / expiring permits | Authorisation posture | Site, type | | Near-miss / hazard volume | Reporting culture (context required) | Site, period | | Compliance tasks due | Statutory surprise risk | Horizon (7/30/90 days) |
If a chart cannot be filtered back to records a site lead recognises, it will not drive action.
Leading vs lagging
Lagging (necessary, late): recordable injuries, lost time, severe incidents.
Leading (earlier, noisier): LMRA completion on required tasks, near-miss quality, inspection finding closure rate, permit expiry discipline.
Treat leading indicators as coaching tools. Spikes often mean better reporting, not suddenly worse sites.
ESG and BRSR-oriented views
Where ESG/BRSR modules are entitled, leadership should see operational inputs (incidents, hours, training evidence when present) that sustainability teams later map into disclosures.
- Use the public BRSR applicability checker for orientation only.
- Do not claim autofiled SEBI submissions from dashboards.
- Glossary terms such as TRIR and BRSR Core explain definitions without replacing your company secretary.
Meeting design
15-minute site standup: open high-severity + overdue CAPA only.
45-minute HSE weekly: aging loops, recurring causes, permit exceptions.
Monthly leadership: cross-site themes, compliance horizon, programme risks — not a slide dump of every KPI tile.
Anti-patterns
- Vanity “health scores” with no drill-down to records
- Dashboards that only work after a weekend Excel refresh
- Comparing sites with different reporting cultures as if TRIR alone explains performance
- Attributing injury-rate changes solely to software go-live