Automated escalation caught a near-miss before it became an incident

Priya Menon manages safety compliance for six active construction sites in and around Pune — two residential towers, a commercial complex, and three infrastructure projects. Safety reporting was split across a site supervisor WhatsApp group and a shared Google sheet that nobody updated on time.

In October, a near-miss at one of the residential sites sat unreported for 40 minutes. A scaffolding bracket had come loose on the fourth floor. The site supervisor's phone was on silent during a client walkthrough. By the time the report reached Priya, the bracket had been informally fixed and the moment was gone. No formal record. No root cause analysis. No evidence it had ever happened.

Three weeks later, an OSHA-equivalent audit raised a flag: the company had no documented evidence of its near-miss reporting process. The auditor asked to see the incident log. Priya pulled up the Google sheet. Two of the six sites had no entries for the previous month — not because nothing had happened, but because the process had broken down.

That audit report was the trigger.

Priya's core requirement was simple: if an incident is reported and not actioned within the SLA window, someone above the supervisor must be notified automatically. Not reminded. Notified. With a hard record of when the escalation fired.

She evaluated one other platform that offered escalation, but it required a webhook integration with an external notification service to work with WhatsApp. The setup complexity was outside what her team could manage without IT support — which Horizon's construction division didn't have.

SentinelIQ's escalation engine was self-contained and configurable without code. Priya set up two escalation rules for safety incidents: Level 1 at 20 minutes (notify the site safety officer), Level 2 at 60 minutes (notify Priya directly and the project director). She had it running the same afternoon she signed up.

Field officer onboarding took one site briefing per location — 15 minutes each. The field team was told: when you see something, open WhatsApp and tap the SentinelIQ contact. Answer the questions. That's it.

The first test of the escalation engine came 11 days after deployment. A field officer at the commercial complex site reported a chemical spill near the electrical panel at 6:18 PM. The site supervisor acknowledged receipt but didn't action the incident — he was managing a separate situation on the other side of the site.

At 6:38 PM — 20 minutes after logging — the Level 1 escalation fired automatically. The site safety officer was notified via WhatsApp. He reached the panel within four minutes. The chemical had not yet reached the wiring. A more serious electrical fault was averted.

Priya saw the entire sequence on the dashboard in real time, from her home.

In the four months since deployment, three Level 2 escalations have fired across Horizon's six sites. All three were actioned within 15 minutes of notification. Two of those three incidents, in Priya's assessment, would have gone unescalated under the old system.

The audit situation has reversed. Horizon now has a complete, timestamped log of every reported incident across every site — near-misses, equipment failures, safety observations. The next audit produced zero documentation flags.

Field officer reporting compliance — the percentage of incidents where a structured report was filed versus an informal WhatsApp message — went from an estimated 40% to over 90% in the first month. The structured flow in WhatsApp made the right behaviour the easy behaviour.

Priya's monthly safety review now runs from the SentinelIQ export. She filters by site, by incident type, by escalation outcome. The report that used to take a day to prepare is now a 10-minute task.