Multi-Site CCTV Delivery: Won on Documentation, Not Installation

We recently completed a CCTV programme across education sites in London — multiple buildings, one client, one standard to hit on every roof, corridor and entrance. The installation itself went the way disciplined installations go: cameras mounted, cables terminated, systems commissioned.

Which is precisely the point of these case notes. Multi-site work almost never fails at installation. It fails at documentation — quietly, weeks after the last camera goes up, when nobody can say which device covers which door on which site, and sign-off stalls into a correspondence war. We planned the programme around that failure mode from day one. Four disciplines did most of the work.

One labelling convention, agreed before the first fix

Before anything was mounted on the first site, the labelling scheme was decided, written down and made non-negotiable. Every site, every device, every cable — the same convention, encoding site, location and device, so a label tells you what you are looking at and where it lives without opening a drawing. That convention covered:

The alternative is what usually happens on multi-site programmes: each site gets labelled in whatever style the crew on it prefers, which feels harmless until a maintenance contractor stands in a plant room three years later translating between five private languages. A convention costs one meeting. The lack of one costs every visit that follows.

• Every camera, with an ID that encodes site and location
• Both ends of every cable run — not just the comfortable end
• Patch panels, switch ports and recorder channels
• Drawings updated to match what is physically on the wall

Results filed per building, not per programme

The temptation on a multi-site job is one big archive at the end: every test result and as-built in a single programme folder, delivered with a bow. We filed everything per building instead — test results, commissioning records, as-builts — because buildings live separate lives once you leave.

Each site has its own staff, its own maintenance visits, and one day its own incident. When someone needs footage or a fault traced at a single school, the pack for that building has to stand alone. Nobody dealing with a live problem should be excavating a programme-wide archive to find the one document that matters.

The snag list closes per site — it never travels

The classic multi-site trap: snags from site three are still open while you are installing site seven, so they get rolled into a programme-wide list to be negotiated at the end. That list does not shrink. Every site adds to it, the context behind each item fades, access gets harder to arrange, and the final account turns into an argument.

Our rule was simpler: each building's snag list is closed before we request sign-off on that building. Snagging while the crew, the access and the context are all still in place is cheap. Snagging months later, by appointment, in term time, is not.

A snag list that travels between sites does not get shorter. It compounds.

Site staff shown the system, not sent a manual

On education sites, the people who live with a CCTV system are caretakers, office staff and site managers — capable people, none of them security specialists. A handover pack they will never open is not a handover.

So at each building, the people who would actually use the system were walked through it: live view, playback, exporting footage properly, and what to do when a camera drops. Twenty minutes per site. It is the difference between a system that gets used and one that gets ignored until the day it is urgently needed.

Multi-site delivery is not installation done several times over. It is one standard enforced across every building, documentation that lets each site stand alone, and a handover made to the people who stay when the vans leave. That discipline is what turned the final week of this programme into a formality instead of a fight. If you are planning security or cabling works across more than one site, we are happy to talk through how we would run it. Talk to us about multi-site delivery