A safety officer might check a compliance board. A shift supervisor, a store keeper and a maintenance technician will not. Due reminders, finding alerts and escalations go out on WhatsApp, email and SMS — on the channel those people already read, before the date rather than after the lapse.
The point of an alert is not that it was sent. It is that it reached somebody who could act, in time to act.
The channel field staff actually read, used for due reminders, finding alerts and escalations without requiring any app installation.
Detailed notifications for office roles, plus a weekly compliance digest for management.
For sites and roles where data connectivity is unreliable, so an alert is not lost to a dead spot.
Sent before a check falls due, because an alert on the day a date is missed is a report, not a reminder.
Unactioned items climb to the next level on a schedule, rather than repeating to somebody who is already ignoring them.
Refill, hydrotest and statutory certification expiries flagged well ahead, to purchase as well as safety.
Alerts addressed to an area group or a role rather than one individual, so leave and turnover do not create silence.
A weekly summary of compliance, overdue devices and open findings, sent rather than requested.
What was sent, to whom and when — which matters when the question is whether somebody was told.
Most missed checks are not refusals. They are things nobody was reminded about at a moment when they could act.
No. WhatsApp, SMS and email all reach people on what they already have. That matters more than it sounds — requiring an app install is the single most reliable way to ensure a maintenance technician or a store keeper never receives a compliance notification.
Because an alert sent on the day something falls due is a status report, not a reminder. Pre-due alerts give the assigned person a window to actually schedule the round. Overdue alerts still fire, but by then the purpose has shifted from prevention to escalation.
A repeated alert goes to the same person who has already not acted. An escalation goes to somebody with the authority to make it happen. Escalation paths are configured per alert type, so a routine check reminder and an overdue high-priority finding do not climb at the same speed.
Yes, and generally they should. Alerts addressed to one person go silent when that person is on leave or leaves the company. Group and role-based routing means the area still gets told.
Yes. Refill dates, hydrotest dates and statutory certification expiries all raise advance warnings, typically at 30 and 7 days. These are routed to purchase as well as safety, since the delay is usually procurement rather than awareness.
Yes. Alerts are logged with recipient and timestamp. It is an unglamorous feature that becomes important quickly, because after an incident the question is rarely whether a system existed — it is whether the responsible person was actually told.
We will configure a rule and send it to your own phone during the demo. It takes about a minute.
