RESPOND · MISSION LIVE BOARD
When it’s happening, the whole team works one map.
The moment an incident starts, every operator on the team works the same live map — same pins, same chat, same camera locks, all in real time. When it’s over, the case file is already written.
Click to enlargeOne incident. Many operators. One shared picture — live.
A common operating picture, not a group chat.
Open an incident and every operator joins a single canvas — real map, pins, chat, participant list, and camera locks all on one page — so no one works from a stale screen.
- One canvas per incident — map, pins, chat, participants, and camera locks on a single page
- Built for a team — operators, observers, and a commander work the same incident at once
- A real status lifecycle — new → triaging → engaged → contained → closed, readable from the room
- No private side-channels — coordination happens on the board, so it’s all on the record
- Read-only after close — a closed incident is preserved exactly as it was for replay and review
Click to enlargeParticipants, chat, presence, and PTZ locks — one incident, one shared record.
The conversation is the record.
The incident chat is append-only — the coordination record can’t be rewritten after the fact, making it the same conversation that ends up in the case file.
- Append-only chat — the coordination record can’t be rewritten after the fact
- System messages — status changes and command handovers post themselves into the log, time-stamped
- Live presence — see who is currently viewing the board, not just who’s assigned
- Roles you can read — each participant carries their role (commander, operator, observer) right on the rail
- Quiet by default — optional chimes flag a teammate’s new pin or message, never your own
Click to enlargeThe chat is append-only — the coordination record can’t be rewritten.
Close the incident. The case file is already done.
The moment an incident is marked closed, Sentinel assembles a complete, evidence-ready case file automatically — no tired operator writes it up at the end of a shift.
- Generated at close — assembled the instant the incident is marked closed, with zero manual write-up
- Captures everything — all pins (with person-pin movement history), the full chat, every camera, every PTZ lock, the participant and command timeline
- A real summary up front — a bottom-line-up-front headline plus a lessons-learned block, not just a dump
- Immutable — the file is locked on write; only a 2FA-gated supervisor summary edit is permitted, and it’s audited
- Evidence-ready — the same chain-of-custody discipline as the rest of Sentinel, ready for whoever needs it next
Click to enlargeThe case file is already written — nobody writes it up by hand.
Coordination layer
More of what keeps the team on the same picture.
PTZ locks
One operator drives a given camera at a time; the rest see who holds it. The lock releases when the holder is done, leaves, or after an idle timeout. Who held which camera, and for how long, is part of the case file.
Incident-commander handover
Every incident has exactly one commander. Command passes through a deliberate handover by an authorized supervisor — a system message posts to chat so the whole room knows, and it’s written to the audit trail.
Real-time sync
Every action — a pin, a message, a status change, a camera lock — reaches every other screen in about a second. If the connection blips, the board reconnects on its own and quietly picks the stream back up.
Auto-open on a watchlist hit
A watchlist match opens an incident automatically, titled with the person and camera so it’s instantly readable. A same-person cooldown folds repeat detections into the existing incident instead of spawning duplicates.
How it works
From a hit on a camera to a finished case file.
An incident opens
A watchlist match (auto-opened in seconds), a manual escalation, or a pattern-of-life deviation starts an incident. It surfaces across the console — sidebar badge, banner, chime — and one click puts an operator on the board.
The team coordinates
Operators join the shared map. They drop pins, watch person pins move across cameras on their own, talk in the append-only chat, and take PTZ locks — every change live on everyone’s screen in about a second.
Command is clear
One incident commander leads; a supervisor can hand command over deliberately, on the record. Observers watch without touching. Everyone can see who’s currently on the board.
The incident closes
The commander marks it contained, then closed. Two simultaneous closes can’t corrupt it — the board serializes them and the second simply confirms it’s already done.
The case file is already written
On close, Sentinel assembles the full record — all pins, the complete chat, cameras invoked, PTZ locks, participant and command timeline — with a summary up front, locked and evidence-ready.
Under the hood
Specifications
| Surface | Single multi-operator canvas per incident — map, pins, chat, participants, and PTZ locks on one page |
| Map engine | MapLibre tile map (same engine as Command Center); pins use true geographic coordinates; cameras render as context markers; deployable offline / on-prem |
| Pin types | Location · person · camera · note, color-coded; person pins track a subject across cameras automatically; full pin history retained (soft-delete, never hard-erased) |
| Real-time transport | One live server-sent-events connection per open board; ~1s propagation for pins, chat, status, presence, and locks; ticket-authenticated (no token in the URL) |
| Connection resilience | Automatic reconnect on TTL expiry or dropped link, with a non-blocking "reconnecting" indicator — no stale-view stranding |
| Status lifecycle | new → triaging → engaged → contained → closed → archived; backward transitions restricted to commander / supervisor; archive is final |
| Roles | Incident commander · operator · observer; observers cannot pin or chat; participation and handover are RBAC-gated |
| IC handover | Single deliberate action by an authorized supervisor; posts a chat system message; written to the tamper-evident audit trail |
| PTZ locks | Exclusive per camera; holder + acquire/release timestamps recorded; auto-released on hand-off, leave, close, or idle timeout; contention returns "in use," never a server error |
| Chat | Append-only (no edit / delete); auto-posted system messages for status changes and handovers; HTML-safe rendering |
| Presence | Live "currently viewing" set via lightweight heartbeat; updates only when the set changes, not per second |
| Auto-open | A watchlist match can open an incident automatically; severity derived from match confidence; same-person cooldown prevents duplicates; best-effort (never blocks event processing) |
| Case file | Assembled on close — all pins (with movement history), full chat, cameras invoked, PTZ locks, participant + command timeline, plus a structured summary and lessons-learned; immutable once written |
| Case-file edits | Supervisor summary refinement only — two-factor-gated and written to the tamper-evident audit chain |
| Audit | Open, status change, handover, close, and override all logged and hash-chained into the tamper-evident audit trail |
| Deployment | Cloud-managed, on-premise, or fully air-gapped — one codebase |
Specifications describe shipped platform capabilities; we’ll confirm the configuration that fits your deployment during your demo.
The rest of Respond
The board is where a team coordinates. Here’s what feeds it and what holds it.
Command Center
The operator’s everyday console — every camera on one map, a live threat picture, and the alerts and recommendations that open an incident in the first place.
Learn moreBriefing Mode
The morning-after side of incidents: every operator starts their shift with an auto-generated brief of what happened overnight and the top actions for the day.
Learn moreAlerts & Threat Detection
The watchlist matching and threat scoring that feed the incident-open trigger — including the auto-open watchlist match and the escalation rules that set the posture.
Learn moreRun a live incident across two operators.
Request demo access and we’ll send you a private, pre-loaded environment — take a watchlist hit, watch the incident open itself, join it from a second operator, drop pins on a moving subject, hand over command, and watch the case file assemble the instant you close.