The Proof Pack: What a Defensible CCTV Handover Should Contain on a UK Site

Commissioning is the point at which a surveillance installation stops being a set of products and becomes a system of record. It is also, disproportionately, the point at which projects unravel. The pattern is familiar to anyone who has sat on the client side of a handover meeting: cameras are up, images are on screen, the invoice is due — and nobody can produce a single document proving that the retention period was measured, that the recording server survived a pulled drive, or that the operator who will use the system at 3am has ever logged in.

That is not a technical failure in the usual sense. It is an evidence failure, and under UK procurement norms it is expensive. The following framework is written for buyers who need to know what to ask for, and for installers who would rather prepare a pack once than return to site three times.

Coverage Should Be Measured, Not Admired

A common weakness in handover is the substitution of judgement for measurement. The picture looks good on the monitor, so the camera is signed off. That tells you almost nothing about whether a face is identifiable at the entrance gate or whether a registration plate is legible at the barrier.

Ask for a coverage schedule tied to camera serial number and physical location, with pixel density at each defined area of interest stated in pixels per metre. Where the specification referenced a recognised performance framework — DORI, or a client-specific standard — the commissioning record should show the measured or calculated result against that threshold, not a qualitative comment. Test targets placed at the boundary of each detection and recognition zone make this auditable and take minutes to photograph. A handover pack without those images is, in practice, unverifiable.

Field of view matters as much as resolution. A camera nudged two degrees during a fascia clean can move a recognition zone off the doorway it was bought to cover. Record the final view, note whether the lens is fixed or varifocal and at what focal length, and photograph the lens setting where it is externally visible. This single habit resolves a large share of post-handover arguments.

Recording Failover Must Be Demonstrated

The retention figure in a quotation is a calculation. The retention figure in a working system is a measurement, and the two diverge more often than suppliers would like to admit.

Before acceptance, the client should witness — not merely be told about — the following:

• Retention verification. Playback from the oldest available recording on at least two cameras of differing resolution and bitrate, with the timestamp visible and the date stated in the record.
• Storage failure behaviour. Removal of a drive from a RAID array, with confirmation that recording continued, an alert was raised, and the array rebuilt correctly afterwards.
• Server and network interruption. Disconnection of a recorder or loss of uplink, with evidence of how the system behaved and how it recovered, including whether edge or on-board storage backfilled the gap.
• Power resilience. Measured runtime on the UPS at the actual connected load, not the nameplate figure, and a clear statement of which devices are and are not supported.
• Clock discipline. Confirmation that time is synchronised to a reliable source, with the drift tolerance documented. Unsynced clocks are the quiet destroyer of evidential value.

Each of these should generate a line in the pack with a date, a witness and a result. A tick box with no supporting detail is not evidence; it is decoration.

Cyber-Hardening Needs a Paper Trail

Surveillance estates are now assessed on their security posture as a matter of routine, and the purchaser carries much of the regulatory weight under the UK GDPR and the Data Protection Act 2018. Handover should therefore include a configuration record showing, at minimum: that default credentials have been replaced on every device including cameras, recorders and switches; that firmware versions are listed against each device with a statement of the source; that remote access paths are enumerated and justified; that management interfaces are segregated from the general network; and that unused services and ports are disabled.

Where the equipment claims conformance to a recognised baseline — ETSI EN 303 645, or a manufacturer's Secure by Default statement — the claim should be documented rather than asserted verbally. Provide an export of the device inventory and a labelled network diagram that an incoming engineer could follow without a phone call.

Documentation and Operator Competence

As-built drawings, a schedule of equipment with serial numbers, warranty registration confirmations, licence keys and expiry dates, and an operations and maintenance manual are baseline deliverables, not favours. So are the credentials register, held securely, and the contact route for support.

Then there is the part most often skipped: the operator. Software that has been configured but not taught is a liability. The handover pack should record who was trained, on what date, on which client, and what they were shown — playback, export, evidence handling, alarm acknowledgement and privacy masking in particular. A short signed acknowledgement from each operator is worth more than a glossy certificate of attendance, and considerably more than a promise of further training later.

The Release Mechanism

Buyers should not treat the handover pack as a filing exercise to be completed after final payment. It is the release mechanism. Structure the contract so that retention is discharged against a defined schedule: coverage evidence, failover evidence, cyber configuration record, as-builts, training log, and a closed defect register with dates for anything outstanding.

Installers benefit from the same discipline. A project closed with a complete pack generates fewer callbacks, fewer ambiguous warranty claims and a materially better chance of being specified again. The cost of assembling it is measured in hours; the cost of an unresolved handover dispute is measured in months.

On a live site, the difference between a system that works and a system that can be shown to work is paperwork — unglamorous, specific and, at 3am, decisive.