Monitoring

One page that reads every room for you: a live timeline, plain-English summaries of what each room is saying, and the signals that need a look — with the actions to deal with them.

What Monitoring Is For

On a busy day nobody can listen to every room at once. Monitoring listens for you. Open Incidents → Monitoring and one page shows what is happening across the whole workspace right now: how much each room is carrying, a running summary of what each one is saying, the public reports and keyword alerts arriving alongside, and — when several of those start pointing at the same thing — a signal that says so, before anybody has declared anything. The page keeps itself up to date; you never need to refresh it.

The idea underneath it is simple: things that line up happened together. If the Gate C stewards start talking about a queue, then Control starts talking about Gate C, then two members of the public report pushing at Gate C, that is one situation forming — and it is visible on this page as three lanes lighting up at the same moment, minutes before it becomes an incident.

The Condition Band

The top of the page is one line: a word for how the workspace is, a sentence saying why, and the figures behind it. The word is one of four, and it only takes a colour when there is something to look at — a calm workspace is a quiet grey line.

• Calm — Routine traffic everywhere. Nothing needs you.
• Watch — Something is worth a look: a room at medium concern, a public report nobody has opened yet, a high keyword alert, a drill running.
• Elevated — A room at high or critical concern, a signal at high or critical, or a critical keyword alert.
• Incident — A live incident that is not a drill. The incidents are listed under the word with an Open control beside each.

The sentence after the word is the situation summary: a few lines written from everything on the page — every room's summary, the open issues, the newest reports and alerts — and rewritten whenever any of them changes. For example: "Gate C is under crowd pressure: radio traffic in three rooms and two public reports describe pushing against the barrier. A request to open the relief gate has been outstanding for several minutes." The figures after it read left to right: open signals, rooms talking, rooms of concern, incidents, reports to triage, open issues, new keyword alerts. A figure takes a colour only when its number needs attention.

The Pulse

The pulse is the page's timeline. Every room is drawn as an audio track — a waveform that swells where the room was busy and flattens where it was quiet — over the last hour, three hours or six. Taller and hotter is busier: the colour runs from violet for a murmur through orange to yellow for the busiest stretches. The thin line under a room is how concerning its conversation was, from its summaries, and small markers sit where a keyword alert, a public report or an incident happened. The right-hand edge is now.

• Point at a moment — Move across the chart and a crosshair follows with a tooltip listing every room that was talking at that minute and anything that happened then. The arrow keys move it when the chart has focus.
• Choose a room — Click a lane, or its name, and that room goes into the Room in focus panel below. Click again to let it go.
• Point from the feed — Hover an item in Just now and the crosshair jumps to its moment on the pulse, so you can see what every room was doing when that report came in.
• Quiet rooms shrink — A room that said nothing in the window folds to a thin line so the rooms that carried something get the height; a room of concern always keeps a full lane.
• Table — The same figures without the picture: each room's total, its busiest minute and when that was.

When one room stands out — at high or critical — a line above the chart names it as the room to look at, with a Declare incident control beside it for people who can declare. The Declare launcher opens prefilled from that room's summary, so the record says what prompted it.

Room in Focus, Just Now, Needs a Human

• Room in focus — One room in depth: its summary as a few bullets, the topics it is about with a concern level on each, and the actions. Below it, every other room in one line each — name, a sparkline of its hour, its concern, its first bullet — so changing focus is one click. Until you choose, the most concerning room is in focus.
• Just now — Everything that happened, newest first: incidents declared, signals raised, keyword alerts heard, public reports, issues, rooms reaching high or critical, entries staff logged by voice. Click an item to open it where it is worked, or to find its signal or room on this page.
• Needs a human — New keyword alerts, public reports not yet in an issue, and the issues being worked, as one list with the most urgent at the top. A critical alert outranks everything; a high alert, a high-priority report and a high-priority issue are peers. Reports and issues open on Issue Reports; an alert opens its moment in Replay for people who hold Replay access, and is information for everyone else.

View conversation, on the room in focus, shows the transcript the summary was written from, right there under it: each message with its time and speaker, the messages the summary relied on marked, and a little either side for context. This is the one place on the page that shows a room's conversation itself, it only opens when you click it, and each opening is recorded in the workspace's audit trail. People who hold Replay access also get Open in Replay to hear it.

Signals

A signal is the page saying look at this. One is raised when the same subject is coming up in more than one room, when radio traffic matches an open issue or a public report, or when any single topic reaches high or critical. Each signal has a title, a sentence or two on what it is and why it matters, a severity from low to critical, the rooms it was heard in (each a way into the room in focus) and any issue it is tied to. Signals sit in a strip under the condition band, most severe first, and the strip is simply absent when there are none.

A signal is kept up to date rather than raised again: as the situation changes its detail and severity move with it, and if it is raised to a higher severity you are told. When nothing supports it any more — the rooms have moved on, the issue is resolved — it clears by itself. A signal that goes unseen for about half an hour clears too, so the page returns to calm without anyone tidying it.

• Acknowledge — I have seen this. The signal stays open, marked with your name, and stops counting towards the tab's badge.
• Raise issue — Opens the Raise Issue dialog prefilled from the signal — title, the rooms as the location, the detail as the summary, priority from the severity. The issue and the signal record each other, and raising an issue counts as acknowledging the signal.
• Declare incident — Opens the Declare launcher prefilled from the signal. When the incident is declared the signal is marked escalated, linked to it, and written to the incident's log, so the record says what the alarm answered.
• Dismiss — Not a concern. The signal closes and stays closed: the page will not raise the same thing again under a new name while the situation it described continues.

How a Reading Ages, and Standing a Room Down

A room's summary is rewritten whenever the room says something new — and only then. So a room that fell silent after a worrying reading would, left alone, look worrying long after the matter was over. Two rules keep the page honest. First, a reading counts as the room's current concern for fifteen minutes. After that it is shown as history — High · earlier, greyed, with its age on hover — and it no longer drives the condition, the figures or the lane. The next thing the room says is read afresh.

Second, a room can be stood down. The situation summary sees every room at once, so when other rooms make clear that the matter a room's reading described is over — Control says the casualty is with Medical and the gate is flowing — it stands that room's reading down in the same pass, and the room shows as Stood down. You can do the same yourself: Stand down on the room in focus says this has been dealt with, is recorded with your name, and re-runs the situation summary so any signal resting on the room can clear. Either way, standing a room down never silences it: its next reading counts as normal.

A Worked Example

1. Before kick-off. Every room is on radio checks and position updates. The band reads Calm, every lane is a low violet ripple, there are no signals.
2. A queue builds. Gate C stewards mention the queue is longer than usual and a turnstile is slow. The room's summary reads low, then medium as the queue passes the outer barrier and Control is asked for more people. The band moves to Watch: Gate C stewards at medium.
3. Things line up. Control starts talking about Gate C, the North stand can see the queue from the concourse, and two public reports describe pushing at the front. The summary raises a signal — Crowding at Gate C, high, three rooms and the two reports — and the band reads Elevated, with the situation sentence explaining why. Everyone who can see Monitoring gets one notification.
4. Somebody acknowledges it. The duty manager clicks Acknowledge: the signal stays open with their name on it, and the tab badge drops.
5. "Person down." A keyword alert fires in the Gate C room, the summary raises the signal to critical, and the notification updates. The duty manager clicks Declare incident on the signal: the launcher opens prefilled, the scenario picks the alarm and the checklist, and on declaring, the signal is marked escalated and linked. The band reads Incident.
6. It eases. The relief gate opens, Medical reports the casualty conscious, the rooms move on. The situation summary stands the intake room down, the signal clears as nothing supports it, and once the incident is resolved the band returns to Calm — without anyone tidying the page.

The Wallboard

Wallboard, in the page header, puts the board over the whole screen for a control-room wall: no menus, the same board a little larger, and a clock in place of the title. While nobody has chosen a room, the room in focus walks through the rooms of concern every twenty seconds, most concerning first; choose one and it stays. Press Esc, or the button again, to leave.

Settings and Privacy

Room summaries are on for a workspace unless you turn them off, and the switch is yours: Security Ops → Settings → Monitoring holds the workspace switch and a switch per room, so a room whose conversation should not be summarised can be left out while the rest carry on. Direct calls between two people are never summarised, nor are the private lines to outside callers, nor rooms shared in from another workspace — those belong to their owner's page. Summaries and signals are written about topics, not people: what is being said and how concerning it is, never who is saying it. A speaker's name appears only where you open the conversation behind a summary — View conversation, which opens on a click and is recorded — and on keyword alerts, which carry the speaker as Keyword Watchdog always has. Summaries and signals are kept for a limited time, and a summary is deleted as soon as the conversation it was written from is.