Alerts & communications · the process
From verified incident to every person accounted for.
The full alerting process, step by step — what Highground does automatically, what people decide, what your employees receive, and how every answer is followed through.
Analyst + senior analyst
Incident verified
An analyst creates the incident from a report with an exact location; an independent senior analyst approves it before it reaches the map.
Senior review of a new incident
Highground (automatic)
Exposure identified
The incident area is checked against your sites, employees by their assigned worksite or home address, and travelers at their approved-trip hotel or a check-in from the last 24 hours. Highground does not know where an employee physically is unless they have checked in.
Exposure panel
Operator
Audience selected
From the map, a Live Monitor card or the Command Center, the operator opens the composer. Targeting starts from the severity's standard radius and can be changed to a custom radius, polygon, state, country or worldwide; recipient categories narrow it further.
Alert composer — targeting and recipients
Operator
Message prepared
The message is pre-filled with the incident's facts and sources and edited by the operator. The recipient preview shows who will receive it, with contact details masked.
Message snapshot and approver chain
A second authorized person
Approval
The alert is submitted for approval. Another authorized person reviews and approves it — nobody approves their own alert.
Operator
Human send
A person presses send. Nothing — no workflow, timer or AI — sends an alert, update, reminder or all-clear on its own. In the current build delivery is simulated: no message leaves the system.
Recipients
What the employee receives
Employees see only what is happening, where, when and the source — never your organization-wide impact. They tick their status, can add a comment, and submit. Shown as a push notification, the response screen, a text message and an e-mail advisory. These are format previews with a fictional incident — delivery channels are In Development and simulated in this build.
Preview only · fictional demonstration incident · nothing is sent from this page
HIGHGROUNDnowCRITICAL ALERT
M6.4 earthquake — strong shaking reported
Fukuoka Prefecture, Japan · 09:39 JST
Source: National seismic agency; local broadcasters · verified by Highground analysts
Respond
CRITICALM6.4 earthquake — strong shaking reported
Fukuoka Prefecture, Japan · 09:39 JST
Source: National seismic agency; local broadcasters · verified by Highground analysts
HIGHGROUND CRITICAL: M6.4 earthquake, Fukuoka Pref., JP 09:39 JST. Source: national seismic agency. Tell us your status: hg.example/r/7KQ2
From: Highground Alerts
Subject: [CRITICAL] M6.4 earthquake — strong shaking reported — Fukuoka Prefecture, Japan
CRITICALM6.4 earthquake — strong shaking reported
Fukuoka Prefecture, Japan · 09:39 JST
SituationA magnitude 6.4 earthquake struck near Fukuoka. Strong shaking was reported across the prefecture; transport services are suspended while inspections take place.
SourceNational seismic agency; local broadcasters · verified by Highground analysts
- Expect aftershocks; stay clear of damaged buildings.
- Follow instructions from local authorities.
- Tell us your status below.
Recipients
How they respond
Each recipient answers with one of four standard responses, can add a note or photo, and can change their answer later — every answer is kept.
- I'm safe — Counted safe.
- I need help — Escalated immediately.
- I'm safe but affected — Follow-up list for security / HR.
- I'm not in the area — Clear; location record flagged for correction.
Recipient response page — SIMULATED, fictional recipient
Responsible team
Live tracking
The alert report updates live: safe, need help, safe but affected, not in the area, and no response — with responses over time, a breakdown by category, department or site, and the map at the moment of sending.
Live alert report — SIMULATED delivery and responses
Highground prepares · a person sends
Follow-up windows
No response is treated as unknown — never as safe. When the window passes, non-responders are listed, the responsible team gets a task, and a reminder round is prepared for a person to approve and send.
Responsible team
“I need help” escalation
A need-help answer goes straight into the live review queue with Critical timers — Highground's team for managed clients, or the client's own team for its own sends. Authorized responders open the person's location, profile and contact; every view is recorded.
Security → client HR / follow-up unit
Hand-off to HR or a designated unit
Security (or Highground staff for managed clients) hands the alert's results to the client's HR or follow-up unit — for example everyone who needs follow-up. That unit then sees only that alert and records each outcome. The hand-off is a logged, revocable action.
HR / follow-up unit view — fictional people, SIMULATED delivery
Security, leadership, HR
Reports & export
Every alert round is searchable afterwards. Export the recipients, contact details, reporting line, department, time sent and each response as a spreadsheet, with a map snapshot of the alert as PNG or PDF. Every export is stored and audited.
Alert response search in Reports
Hand-off recorded on the alert report — SIMULATED
Alert Management overview — SIMULATED
Ready to see Highground in action?
See the alerting process live
We'll walk you through the full process with demonstration data — from incident to every person accounted for.