Stage 06 of 06
Control room
Everything above ends up here. Is anybody able to act on it?
Time it
Somebody asks for ten minutes of footage. How long until they have it?
Every stage before this one ends here. This is the moment all of it is either worth something or it is not. Press start on each.
The request
“We need the corridor camera, 19:40 to 19:50, on the fourteenth of July.”
06:00 minutes
No written procedure
- 00:00Police at the front deskAsking for one corridor camera, ten minutes
- 04:00Camera found on the systemFour minutes to work out which one covers that corridor
- 25:00Export menu, nobody is sureThe operator has never done this
- 55:00Call to the vendorNo answer. Ticket raised.
- 13h 00mCallback next morningRemote session booked for the afternoon
- 1d 03hClip finally exportedNo hash, no receipt, emailed as an attachment
A procedure at the desk
- 00:00Police at the front deskAsking for one corridor camera, ten minutes
- 01:00Procedure taken off the deskOne page. Anybody on shift can follow it.
- 03:00Camera and window selected14 July, 19:40 to 19:50
- 05:00Clip exported with its hashFormat the police accept
- 06:00Handed over on a drive, receipt signedSix minutes
No written procedureThe recording is there. Every camera worked, the retention held, nothing failed. What is missing is one page telling somebody on shift how to get a clip out, and the man who knew left in April.
A procedure at the deskOne page, written at handover, kept at the desk. It does not depend on who is on shift or how long they have been there. Six minutes, in a format the police accept, with a receipt.
Both rooms had the footage. One of them could hand it over. Everything the other five stages did well arrives here, and if this last step is missing, none of it can be produced when somebody official is standing at the desk.
Three vendors normally share this stage, and each subsystem brings its own software. The video platform is one contract, the network and servers belong to IT, and the room itself (consoles, video wall, furniture) to a fit-out contractor. What none of them owns is whether one person can operate the result at three in the morning, which is the only question that matters here.
What lives at this stage
Where every other stage arrives, and where most of them stop.
- The integration platformThe software layer where cameras, doors, alarms and building systems appear as one picture rather than five.
- Alarm handling and escalationWhat happens on an alarm, who is told, in what order, and what happens if nobody answers.
- Evidence retention and exportHow long, at what quality, and how a clip is produced when somebody official asks for it.
- ReportingThe reports that go out on a schedule, to a named person, whether or not anything happened.
- The room itselfSightlines, screen count, seating and lighting, so an operator can work an eight-hour shift and still be looking.
- Data residency and accessWhere the recordings physically sit, who can reach them, and whether that is recorded.
What fails here
Command fails as a room full of working equipment that produces nothing.
These are the six we find most often on assessment. If two of them sound familiar, the rest are probably true on your site as well.
| What fails | Why it fails | What it costs |
|---|---|---|
| Too many screens, no priority | Every camera displayed because the client asked to see all of them. | An operator watching forty views is watching none of them. |
| Alarms with no escalation path | Configured to appear on screen and no further. | The alarm was raised at 2am. Nobody was there. It was still on screen at 9. |
| Retention shorter than believed | Sized at a lower quality or frame rate than the cameras actually record. | Ninety days on the quotation, twelve days in the recorder. Found when footage is requested. |
| Nobody can export a clip | The person who knew has left, and it was never written down. | You have the evidence and you cannot hand it to anybody. |
| Reports configured and never delivered | Set up at commissioning, sent to an address that no longer exists. | Nobody has looked at a system report in three years. |
| The integration is a stack of separate windows | Sold as integrated, delivered as five applications on one desk. | Every incident requires an operator to correlate by hand, in real time, from memory. |
3
Three vendors normally share this stage. None of them owns the gaps between.
The video platform is one contract, the access and alarm systems another, and the IT infrastructure the room runs on is a third. Every failure above lives in the space between two of them: and the BoQ never said whose job that space was.
So on the day it matters, there is nobody to call. Each vendor can show you their own scope, correctly delivered. Nobody has to answer for the join.
How we specify it
Six decisions that determine whether this stage works in year seven.
- Retention measured against real recording, not calculated from a datasheetVerified on site after commissioning, and re-verified at every service visit.
- Screens designed around what an operator can act onA small number of prioritised views, with everything else one click away.
- Every alarm carries an escalation path with a timeoutIf nobody acknowledges, it goes somewhere else. Defined, tested, and written down.
- Evidence export documented as a procedure, not as a personA one-page instruction anybody on shift can follow, kept at the desk.
- Reports scheduled to a named role, and reviewed when they arriveNamed role, not named person, so it survives them leaving.
- Data residency and access recorded as part of the designWhere recordings sit, who can reach them, and how that is logged.
Sector variations
The control room means something different depending on what you are protecting.
Year seven
The control room is where every other stage's failure finally becomes visible: years late.
The camera that stopped working, the door that was propped, the detector that was never tested, the credential that was never revoked: none of them announced anything. They arrive here, all at once, on the day somebody asks for footage.
By then the room cannot help. It can only report what it was given.
What decides whether this stage still works in three years is Maintenance cover and whether anyone has produced a signed condition report since.
Technical reference
Find out
Ask your team to produce ten minutes of footage from six weeks ago. Time how long it takes.
A signed condition report naming what works, what has failed, and what was never commissioned.
The assessment is chargeable, quoted against the site, and adjusted in full against the first year if you take cover. Where cover is not taken, the fee covers our team’s time on site and the report we leave behind, and the report is yours either way.
Chargeable, and adjusted in full if you take cover.
Book an assessment