Write the day's log by saying it: a phrase over the radio turns what follows into an entry under your name, with the recording kept. The Log page keeps every day in order beside everything else that happened.
On a shift, the things that matter get said on the radio and never written down. A gate opened, a car park filled, a medic left a position — everyone heard it, nobody logged it, and at the end of the night the occurrence book is written from memory. The voice log fixes that at the moment it happens. Say a phrase — "Control, log: relief gate opened" — and the words after the phrase are written to the day's log as an entry under your name, with the recording kept, so anyone can hear exactly what was said.
Security Ops → Log is the day's book. Voice entries sit in time order beside entries people typed in and beside everything the platform recorded itself: incidents declared and resolved, keyword alerts, signals, voice rooms stood down, issues raised and closed. Open any day and read it through, newest first or oldest first.
An entry is matched at the start of a transmission. You can address Control first — "Control, log …" or "Control, this is Sam, log …" — and the page skips past that. Everything after the trigger phrase becomes the entry. Some lines, and what each one logs:
Everything else said in the voice room is untouched: ordinary radio traffic stays ordinary radio traffic, and a transmission that mentions the word log in the middle of a sentence is not an entry. If an incident is live when the phrase is said, the entry is linked to it, so the incident's record and the day's log agree.
The page shows one day. The date control at the top steps back a day at a time or jumps to any date; Today brings you back. Beside it, Newest first and Oldest first switch the reading order — newest for keeping up, oldest for reading a shift through. Under the title, one chip per kind of line with its count for the day: click a chip to hide or show that kind. A voice room filter, a person filter and a search box narrow the day further, and Show everything clears them all.
Every line has its time to the second, a badge for what it is, the text, and who and where it came from. On a voice or typed entry:
Add entry, in the page header, types an entry by hand: what happened, an optional category, an optional voice room. It is timed when you save it and carries your name. Use it for anything that did not go over the radio — a phone call, a visitor, a handover note.
Today keeps itself up to date: a new entry appears within moments of being said, and you never need to refresh the page. Earlier days are the settled record. Entries are kept for as long as your workspace chooses — thirteen months unless you change it — and then deleted.
Entries also appear on Incidents → Monitoring: on the pulse as a small notebook mark on the voice room's lane at the moment it was said, and in Just now as a quiet Log line — Log · Gate C: relief gate opened. Click either to open the entry on the Log page. An entry never changes the workspace's condition, never raises a signal and never counts towards a badge. A log line is a record, not an alarm — that is the point of it. The situation summary does read the log, though: an entry that says relief gate opened or casualty with medical, all clear is a person's own account, and it outranks what the summary would otherwise infer from the voice rooms — it is what stands a voice room down or lets a signal clear. An entry logged during a live incident also appears on that incident's Timeline.
The Log is the day's occurrence book, and a book is something you hand over and something you hand in. Export, in the page header, gives the day as a CSV (every line with its time, kind, who, where, the entry, the trigger phrase, how it was heard and any correction) or as a PDF occurrence book — the artefact for an inspector, a licensing officer or the file — with the workspace's name and the day on the cover and every line in order. Each export is recorded.
Above the lines sits the handover summary: what happened, in order, for whoever takes over — how the day went, incidents declared and resolved, duress cases, the notable entries, and anything still open. A security manager writes it with Summarise the day; it is written by a language model from the day's lines and kept, and Update summary rewrites it once the day has moved on (nothing changed, nothing rewritten). It goes into the PDF book too. It is something to read, not the record: the lines are the record, and anything that matters should be checked against them.
Good phrases are short and not something people say at the start of an ordinary message. Log works well because nobody opens a normal transmission with it. Avoid a phrase that is also a common opener — "Control, update" would log every update — and keep to a handful; the team has to remember them under pressure.
Only the words after the trigger phrase are logged, and only from a transmission that starts with one. An entry carries the speaker's name because a log needs one. Entries are visible to people who can view Security Operations in your workspace, kept for as long as the workspace chooses and then deleted. The voice log adds no recording and no transcription of its own: it reads the transcripts your voice rooms already produce under their existing settings, and nothing here changes those.