2026-08-20 · 3 min read · SONIL EHS360
The adoption problem
Field tools fail when they ask for a desktop essay at the workfront. Crews under schedule pressure will revert to WhatsApp voice notes. Adoption is a design and leadership problem, not a training-video problem.
SONIL EHS360’s field surface (/field) is built for gloves, glare, and short interactions: incidents, near misses, hazards, LMRA, and permit checks. This guide covers how to get people to use it.
Principles that work on site
- One job per screen — report the event; investigate later in the workspace.
- Language of the shift — LMRA, toolbox, permit, isolation — not abstract “EHS digital transformation.”
- Leadership closes the loop — if reports disappear into a black hole, reporting dies.
- Start with willing crews — expand after the first packages show verified CAPA, not vanity signup counts.
Week 0 — Prepare the workfront
- Confirm site and project names match how supervisors talk about locations.
- Nominate 2–3 coach users per pilot site (usually shift in-charge + HSE).
- Agree the minimum report set for go-live (for example: injuries, high-potential near miss, LMRA before high-risk tasks).
- Remove duplicate paper forms for the pilot scope, or people will dual-key once and quit.
Week 1 — Coach, don’t broadcast
Hold short toolbox-length sessions (10–15 minutes), not classroom days:
- Open the field app on a phone in landscape and portrait.
- Capture one sample near miss end-to-end.
- Show where that record appears for the HSE officer.
- Show one CAPA assigned from a finding.
Leave printed quick cards with three URLs or QR codes only: field home, how to report, who to call when stuck.
LMRA without friction
Last-minute risk assessment succeeds when it is part of task start — not a weekly homework assignment.
- Require LMRA for the high-risk task types you already control with permits (hot work, height, excavation, electrical isolation).
- Keep questions short and local: energy sources, controls in place, stop-work triggers.
- Review incomplete LMRA in the same meeting as open permits — same audience, same accountability.
If LMRA is “optional for everything,” it becomes optional for nothing useful.
Supervisor behaviours to reinforce
| Reinforce | Avoid | |---|---| | “Report before the shift moves on” | “Fill the portal when you get to the cabin Wi‑Fi tonight” | | Praise early near-miss reporting | Punishing the messenger for bad news | | Using dashboard overdue lists in weekly reviews | Maintaining a parallel Excel “real” tracker |
Connectivity and device reality
- Assume intermittent network on corridors, yards, and remote parks.
- Prefer devices already issued to supervisors; do not invent a hardware programme for a pilot.
- If a draft cannot sync, teach the recovery path once — then fix process or device policy.
Measuring adoption (honest metrics)
Useful leading indicators:
- % of high-risk tasks with LMRA completed before start (where you require it)
- Near-miss / hazard volume vs prior paper baseline (expect noise, then quality)
- Time from report → first assignment
- % of CAPA verified before close
Useless vanity metrics:
- Number of accounts created
- “App downloads” with zero weekly active reporters
- Invented TRIR improvements attributed to software alone
Escalation path
When a site stalls:
- Check whether leadership still uses a side spreadsheet.
- Check whether CAPA owners are real people with due dates.
- Reduce scope to one package and one event type for two weeks.
- Re-coach with a live report from that morning’s work.