Gates, Not Perimeters: Alarm Zoning for Scaffold Loading Towers and Hoist Landings

Most scaffold alarm designs begin with a line: the perimeter. Sensors are placed to detect someone crossing the scaffold elevation, and the zoning follows the geometry of the building. That logic works well for a continuous face of scaffolding. It works less well at a loading tower, where the scaffold is designed to have a hole in it, and at a hoist gate, where the opening must be used many times a day by authorised people and materials.

The result is a familiar blind spot. The hoist gate is either left outside the alarm specification altogether, or it is folded into a broad elevation zone that cannot distinguish between a legitimate lift and an intrusion. Neither outcome is acceptable on a live UK site. The loading tower is not a peripheral detail; it is a vertical access route with ground-level approach, intermediate landings and a gate at each level. If the alarm design does not treat it as its own controlled access envelope, the perimeter can be perfectly monitored while the most practical way onto the scaffold remains open.

Why the hoist gate sits outside perimeter logic

Perimeter detection assumes that a breach is a crossing. A hoist gate is a legitimate opening. It is meant to open, it is meant to be approached, and it is meant to admit loads. A simple contact switch on the gate leaf may therefore be treated as a status indicator for the hoist rather than a security device. That distinction matters. A gate interlock that prevents the hoist operating with the gate open is a safety control, not necessarily an intruder detection control.

There is also a physical problem. Landings accumulate materials, pallets and shrink-wrapped loads. Passive infrared detection aimed across a loading tower can be blocked by stored goods or disturbed by moving sheeting. Beams placed inside the tower may be interrupted by legitimate loads. If the detection layer is poorly positioned, the site team learns to ignore it, and a ignored zone is worse than no zone because it creates false confidence.

Map the vertical access envelope before specifying hardware

A loading tower should be divided into named zones rather than treated as one lump. At minimum, consider three planes: the ground-level loading bay, the tower interior, and each gate landing. The gate landing is the critical plane because it is where a person steps from the platform or landing into the scaffold. Give each gate its own identity in the alarm system, for example LT-01-GATE, LT-02-GATE and so on, with the landing level recorded in the zone description. This naming discipline pays off during commissioning, handover and incident review, when a log entry needs to be understood by someone who was not on site when the system was installed.

The ground-level approach should not be ignored. A loading tower often has a defined approach route, and that route may be screened from the main site compound. A beam or contact arrangement at the tower base can provide early warning, but it must be designed around vehicle movements and material deliveries. The objective is not to alarm every delivery; it is to detect access outside the agreed lifting window.

Detection that survives legitimate use

The primary detection at a hoist gate should be a monitored contact switch fitted to the gate leaf and its frame. Specify an industrial-grade unit with a positive opening action, a sealed enclosure suitable for external use, and a tamper circuit. The contact should report gate opening, not merely latch position. A gate that is left ajar after a lift is a security event even if the latch has not been operated.

A through-beam pair across the gate aperture can add useful confirmation, provided it is positioned at the gate line rather than inside the tower. The beam should detect a person stepping through the opening, not a pallet sitting on the platform. Two beam heights are often appropriate: one low enough to catch a person who steps over a raised sill, and one at torso height. The beam brackets should be rigid, adjustable and protected from impact by the gate or load. On exposed UK scaffolds, beam alignment should be checked after high winds and after any alteration to the gate or landing.

Passive infrared detection should be used cautiously at loading towers. It can be useful for the tower interior, but it should not be the sole detection at an open gate where thermal movement, sheeting and weather can cause nuisance activations. The combination of a gate contact and a gate-line beam is more defensible because each device answers a different question: has the gate been opened, and has someone passed through it?

Arming schedules tied to lifting operations

The most common reason hoist zones are disabled is that they generate activations during legitimate lifts. The solution is not to leave the zone off all day. It is to create a defined lifting window, recorded in the alarm system and tied to the lift plan. During the window, the gate zone can be placed on a time-limited shunt that automatically re-arms at the end of the period. The shunt should be logged, and the log should show who authorised it and when it ended.

A key switch or dedicated code at the hoist control position is preferable to a generic user fob, because it limits the ability to silence the zone to those responsible for the lifting operation. The site manager should retain overall control of the schedule. If a lift runs beyond the window, the extension should be authorised rather than achieved by repeatedly resetting the system. Outside the lifting window, a gate activation should be treated as an intrusion until proven otherwise, and the response plan should say so.

Coordination with the hoist contractor

The hoist contractor and the scaffold alarm provider often have different scopes, and the interface between them is where gaps appear. The hoist contractor may own the gate, the landing gates and the hoist car; the alarm provider may own the detection and the control panel. Agree the mounting points, cable routes, fixing method and testing responsibilities before installation. A simple interface schedule should record which party supplies each bracket, who drills the gate frame, and who signs off the gate contact as operational.

Commissioning should test every gate at every landing, not a sample. Each gate should be opened, held open, closed and left ajar in turn, with the resulting panel events recorded. Beam alignment should be proven with a test object at the gate line. The handover file should include the zone list, the lifting-window procedure, the shunt authorisation method and the name of the person to call if a gate zone will not reset.

Closing the gap without adding noise

The loading tower is not an unavoidable weakness. It is a controlled access point that needs to be designed as one. Give the hoist gates their own zones, fit contacts that report opening rather than latch status, use gate-line beams to confirm passage, and tie the arming schedule to the lift plan. Coordinate the work with the hoist contractor and record the interface in the handover file. Done properly, the alarm protects the vertical route without turning every legitimate lift into a nuisance activation.