Seek Shelter: One Instruction, Every Screen, Seconds
The twelfth of ProAlert™'s fourteen operational disciplines covers two distinct things: getting an emergency instruction to every person in a facility within seconds, and keeping a formal record of safety incidents afterwards.
The bottom line: A loudspeaker cannot tell you who heard it. After an evacuation or a shelter event, the plant's most urgent question is who is accounted for, and that is the question a PA (Public Address) system structurally cannot answer. Seek Shelter records the acknowledgement, which is the difference between a warning and a headcount.
What Happens When It Fires
A severe weather warning, a chemical release, an active threat or any other site-wide emergency. A supervisor or manager triggers a single broadcast, and:
Why It Works When Other Things Fail
The broadcast runs over the plant's own network, through ProAlert's real-time transport. It does not depend on internet connectivity, a cellular carrier, or a third-party notification service.
In a severe weather event, those three are precisely the things most likely to be degraded, and they are the three that a cloud-hosted mass notification product depends on entirely. This is one of the practical reasons ProAlert is deployed LAN-first, on the customer's own network. The architecture page covers the rest of that reasoning.
Who Can Trigger It
Triggering is restricted by role, and deliberately not available to every user:
| Role | Can trigger a site-wide broadcast |
|---|---|
| Admin | Yes |
| Manager | Yes |
| Supervisor | Yes |
| Production Manager | Yes |
| Maintenance Manager | Yes |
| Operator and all other roles | No... they receive and acknowledge |
Role membership is configured in administration, so which named people hold those roles is the plant's decision rather than a fixed list.
Safety Incident Register
Separate from the emergency broadcast, ProAlert keeps a structured register of safety incidents: near misses, injuries, unsafe conditions, and the follow-up on each.
Because it sits on the same database as maintenance and quality, a safety incident connects to the asset involved, the work order that resolved the hazard, and the corrective action that followed. In most plants the safety record is a separate binder or spreadsheet that never connects to the maintenance history of the machine that caused the injury, which is exactly the connection an investigation needs.
Who Uses It
| Role | What they do here |
|---|---|
| Plant Manager / Supervisor | Trigger a Seek Shelter broadcast, review acknowledgements afterwards |
| Safety Officer | Incident register, follow-up, trend review |
| Every employee | Receive and acknowledge broadcasts on any device |
| Maintenance | Work orders arising from unsafe conditions |
Common Questions
| Question | Answer |
|---|---|
| Does this replace our plant alarm system? | It complements it. A physical alarm tells people something is wrong. Seek Shelter tells them what it is, what to do, where to go, in their own language, and records who confirmed. Most customers run both. |
| What if the internet is down? | The broadcast runs on the plant's local network and does not depend on internet connectivity. |
| Can we test it? | Yes. Emergency broadcast history is retained, so drills are recorded alongside real events. |
Run a shelter drill and get a number back.
Book a 30-minute demo... we'll fire a test broadcast to a browser, a phone and a work cell display, and show you the acknowledgement list.
