The Handover File That Makes a Scaffold Alarm Auditable

A scaffold alarm should not end at the control panel and a set of keys. On a well-run UK site, it should become a documented security system with a handover file that a site manager, insurer or principal contractor can audit without relying on oral history. The file is not bureaucracy for its own sake. It is the evidence that the system was designed for the site, commissioned properly, maintained since installation and supported by a response that someone has actually agreed to.

Why the handover file matters

Principal contractors increasingly ask for alarm documentation because security is part of their management of the works. Under CDM 2015, the principal contractor has a coordinating role in managing construction-phase risks, and theft, trespass and unauthorised access are practical site risks even where they are not the first item on a risk register. Insurers, meanwhile, want to see that the alarm specification matches the risk and that the system is not merely a box on the hoarding. A handover file answers both demands in one place.

As-built zone map and asset register

The as-built zone map should show what is actually installed, not what was proposed. It should identify each zone, the devices within it, the coverage boundary and the label used at the control panel. Where the design changed during installation, the map should record the final arrangement. An asset register should list detectors, sounders, control equipment and communication paths, with serial numbers where available. This matters when a device fails or when a replacement is needed and the site wants to avoid mixing incompatible equipment.

Commissioning and configuration records

Commissioning records should capture the date of commissioning, the engineer, the tests performed and the results. Configuration records should show zone names, sensitivity or threshold settings, entry and exit arrangements, and any verification logic. If the system can be accessed remotely, the file should record who holds that access and how it is controlled. These details turn a vague assurance that the alarm was set up correctly into a verifiable statement.

Response escalation and keyholder matrix

An alarm without a response is a notification, not a security system. The handover file should include an escalation matrix: who is called first, who is called next, what constitutes a confirmed activation and when the police or a guarding provider is contacted. Keyholder details should be current and held with appropriate confidentiality. The file should also state the expected response time and any limits on out-of-hours attendance. The matrix should be tested at handover, not discovered during the first genuine activation.

Maintenance and event logs

Maintenance logs should record scheduled inspections, battery changes, device replacements and fault rectification. Event logs should be retained where the system supports them, with a clear note on how long they are kept and who can access them. Repeat nuisance activations are particularly important: they are the early warning that a detector is poorly positioned or that site activity has changed. A log that simply says no faults found is less useful than one that shows what was checked and what was changed.

Cameras, UK GDPR and signage

Where cameras are integrated with the alarm, the handover file should include a camera coverage plan, signage details and a note on the lawful basis for processing. UK GDPR still applies to construction-site CCTV, and the file should show that the operator has considered purpose limitation, retention and access. A data protection impact assessment may be appropriate for larger or more intrusive systems. The file should also record who is responsible for subject access requests and how footage is exported and stored.

Insurance and principal contractor evidence

Insurers may ask for evidence that the alarm was specified to the risk, installed by a competent person, commissioned, maintained and linked to a response. The handover file should include the specification, commissioning certificate, maintenance schedule and confirmation of monitoring or keyholder arrangements. For principal contractors, the same file supports site security audits and demonstrates that the alarm is part of the site management regime rather than an isolated purchase.

A handover review, not a handover box

The final step is a handover review with the site manager and, where appropriate, the principal contractor. The review should confirm that the zone map matches the panel, that keyholders know their roles, that signage is in place and that the file is stored where it can be found. A handover file that exists only in an email attachment is little better than no file. The test is whether someone unfamiliar with the installation could understand the system, verify its condition and follow the response path. That is the standard UK contractors should expect in 2026. For NRG Scaffold Alarms, the handover file is part of the product, not an afterthought.