CCTV Installation Documentation: As-Built + Handover Pack

The install is finished. The documentation decides if it stays yours

Two installers finish identical CCTV jobs. Three years later, a camera goes dark on each site. On the first, the maintenance tech opens the as-built pack: camera ID, model, serial, exact mount point on the plan, cable route back to the switch. Twenty minutes. On the second, there is no pack — so the tech traces cable through two ceilings, and the client quietly decides the next contract goes elsewhere.

CCTV installation documentation isn’t bureaucracy; it’s the product the client keeps after your vans leave. This guide covers what a proper as-built pack contains — with a free checklist to work from.

Download the CCTV as-built checklist: PDF

What “as-built” means for a camera system

The quote described a design. The building disagreed: a camera moved because of a beam, a route changed because a riser was full, an extra detector appeared on a variation. As-built documentation records the installed reality, not the quoted intention — and the delta between the two is exactly the knowledge that evaporates when the crew moves to the next job. If the delta isn’t on paper the week you finish, it’s gone.

The camera and device schedule

The heart of the pack is one table: every device with its ID, model, serial number, exact location, mount height, and what it covers. Give each camera the same ID on the schedule, on the plan, and in the recorder’s channel naming — the discipline that makes “camera 12 offline” mean something.

The schedule is also a commercial document: maintenance contracts are priced on it. A client with 47 documented devices gets a real quote; a client with “about 40 cameras, we think” gets a padded one. Serial numbers anchor warranty per unit — photograph labels as you mount, not from a ladder afterwards.

Cable routes belong on a plan, not in memory

Every install has a moment when someone asks, years later: where does this cable actually run? Mark routes, containment and penetrations on the floor plan while the ceiling is still open. The person troubleshooting in three years wasn’t on the crew — draw it for them. Firestopped penetrations especially: recorded, they’re compliance evidence; unrecorded, they’re a liability hunt.

Commissioning checks that prevent callbacks

The difference between “installed” and “working” is a short list, run per camera and recorded:

• Recording verified — and playback checked, not just a live image
• Night/IR image checked per camera, in the dark, not at 3pm
• Remote access working for the client’s actual users on their actual phones
• Time sync (NTP) configured — evidence with a wrong timestamp is compromised evidence
• Privacy masking applied where views overlook neighbours or public space

Each of those lines is a callback you won’t get in the first month.

Legal signage: don’t skip the boards

Where cameras record areas people access, most jurisdictions require visible notice. In Spain, RGPD/LOPDGDD practice requires the “zona videovigilada” signage with the data controller’s details before the system goes live — and in most of Europe some equivalent notice duty applies. It’s the cheapest item on the job and the first thing an inspector sees, so it belongs on the commissioning checklist, not on the client’s to-do list. (Practice-level note, not legal advice.)

The handover pack

Deliver it as one bundle, not as attachments dribbled over a month:

• Marked-up as-built plan (devices + routes)
• Device schedule with serials
• Per-point photo set — each device, mounted, plus its field of view
• Credentials, sealed and handed over formally
• Quick guide for the client’s operators
• Signed acceptance report — the installation and service report that triggers your invoice

One bundle, one signature, one clean end to the project.

Keeping the evidence organized while you work

Here’s the honest failure mode: after a two-day install, there are 200 photos in a camera roll. Which junction box is that? Which floor’s riser? The pack you assemble a week later is only as good as your memory of it.

The practice that fixes it is pinning each photo to its position as you go: a pin on the floor plan per device, holding the mounting photo, the label shot with the serial, a voice note (“channel 12, IR checked, mask set on window”) transcribed automatically. Pending points get assigned with a status so second-fix items don’t vanish. At handover, the as-built evidence is already organised by location — you export and assemble instead of reconstructing. That’s what PinMy does on an install; the checklist above is still the structure you deliver against.

If you’re sizing the system side, our free CCTV storage & bandwidth calculator pairs well with this checklist — and the construction report types guide maps where the as-built sits among the rest of the paperwork.

FAQ

What should CCTV as-built documentation include? A device schedule (ID, model, serial, location, height, coverage), the marked-up plan with cable routes and penetrations, commissioning test results, photos per device, credentials, and the signed acceptance report.

Why document cable routes if the system works? Because troubleshooting, extensions and refurbishments happen years later, usually by someone who wasn’t there. A route on the plan turns a day of tracing into minutes — and keeps the maintenance contract attractive to price.

Is video surveillance signage really required? In most jurisdictions where cameras cover areas people access, yes — in Spain the “zona videovigilada” notice under RGPD/LOPDGDD is standard practice before go-live. Check local specifics; treat the sign as part of commissioning.

What PinMy is NOT

PinMy organises located field evidence — pins with photos, voice, owners, statuses on your plans. It does not generate the as-built pack or the acceptance document: assembling and signing those stays with you, and our web PDF export is useful today but still maturing. It doesn’t replace your VMS, your design tools or your judgement. It just means the 200 photos already know where they were taken.

Next install, try it once

Run one job with a pin per device instead of a camera roll, and compare the week-after pack assembly. Know an installer whose as-built is “somewhere in WhatsApp”? Send them this.

• Start free: pinmy.co
• Book a 15-minute walkthrough: tidycal.com/pinmy