Fall Restraint Versus Work Positioning Explained
A roof operative is clipped on, but that fact alone does not establish compliance. The critical question is what the system is designed to do. In the fall restraint versus work positioning decision, confusing the two can leave a worker exposed to an unprotected edge, unsupported during a task, or connected to an anchor arrangement that has not been specified for the load it may receive.
For facilities and estates teams, this distinction matters at survey, procurement, inspection and handover. A certificate stating that components have been inspected is not a substitute for confirming that the selected system matches the work. The Work at Height Regulations 2005 require work at height to be properly planned, appropriately supervised and carried out by competent people. Equipment choice is part of that planning, not an item to resolve once an operative reaches the roof.
Fall restraint versus work positioning: the essential difference
Fall restraint prevents a person from reaching a position where a fall can occur. The lanyard, anchor position and adjustment are configured so that the user cannot physically get to an unprotected edge, fragile rooflight or opening. It is a collective objective delivered through personal equipment: keep the person away from the hazard.
Work positioning serves a different purpose. It holds or supports a worker in a controlled position so they can carry out a task with both hands available. Typical examples include work on a mast, structural member or façade where the operative needs to lean back under tension while remaining stable. A work positioning arrangement is not automatically fall protection. If there is any foreseeable fall, a separate backup system is normally required.
That is the operational dividing line. Restraint removes access to the fall hazard. Work positioning enables work at the location of the hazard. The latter usually demands more detailed planning, closer attention to anchor suitability and a defined rescue method.
Start with the hierarchy of control
The correct system does not begin with a harness model or lanyard length. It begins with whether the work can be avoided, completed from a safe place, or protected through collective measures. Guardrails, protected walkways, fixed platforms and suitably designed edge protection should be considered before personal fall-protection equipment.
Where personal protection is necessary, restraint is generally preferable to fall arrest because it prevents the fall rather than managing its consequences. On a flat roof, for example, a correctly designed horizontal safety line or fixed anchor layout may allow maintenance staff to reach plant while remaining unable to access an unprotected perimeter.
It depends on the roof geometry and task. A short lanyard does not automatically create a restraint system. Its usable length changes with the harness connection point, line deflection, anchor location, body movement and the route taken around obstructions. An operative may be restrained at one point on the roof yet able to reach an edge after moving past a corner or changing anchor. This is why generic assumptions are non-compliant by default.
Work positioning may be justified where the task cannot be carried out from a guarded area and where the worker must be supported at the workface. That decision should be supported by a task-specific risk assessment and method statement, competent-user requirements and equipment manufacturers' instructions.
Equipment classifications are not interchangeable
A full-body harness to BS EN 361 is designed for fall arrest. A work positioning belt or harness attachment to BS EN 358 is intended to support the user during positioning or restraint activity. The presence of an EN 358 attachment point does not make a belt suitable for arresting a fall.
Similarly, a work positioning lanyard is designed to take tension and hold a working position. It should not be selected as a fall-arrest lanyard unless the manufacturer explicitly states it is suitable for that use and the whole system has been assessed accordingly. A fall-arrest arrangement also needs sufficient clearance below the user to allow for lanyard extension, energy absorber deployment, body length, system deformation and a safety margin. On roofs with plant decks, lower roofs or changes in level, that clearance can disappear quickly.
Anchors require the same discipline. An eyebolt, horizontal lifeline, rail system or mobile man anchor must be suitable for its intended direction of loading and system type. A positioning task can apply forces in directions that differ from a straightforward vertical fall-arrest scenario. The anchor design, fixing substrate, installation record and current inspection status all need to support the proposed use.
Applicable standards will depend on the equipment and arrangement, but may include BS EN 358 for work positioning and restraint equipment, BS EN 361 for fall-arrest harnesses, BS EN 363 for personal fall-protection systems and BS EN 795 for anchor devices. Standards help define equipment requirements. They do not remove the need for a site-specific plan.
Why rescue planning changes the answer
A restrained worker should not be able to fall over an edge. That reduces the need for post-fall recovery, but it does not eliminate emergency planning. A worker may still become incapacitated, stranded due to a medical event or unable to return safely after a change in weather or roof condition.
For work positioning and fall arrest, rescue planning is more immediate. Suspension after a fall or loss of consciousness can become life-threatening. Calling the emergency services is not, by itself, a rescue plan. Building access, roof routes, casualty location, anchor availability, recovery equipment, trained personnel and response time must be considered before work begins.
This is particularly relevant where contractors use rope access, davit systems or temporary anchors. The equipment may be technically capable, yet the site may lack a safe route for recovery. A compliant plan identifies who will act, what they will use and how that action will be practised or verified.
Inspection evidence must reflect the intended use
Facilities managers often inherit mixed roof-access assets: ageing safety lines, eyebolts with incomplete records, harnesses stored without clear issue history and roof drawings that no longer reflect installed plant. In that situation, assumptions create exposure.
Periodic inspection confirms condition at a point in time. It should identify defects, missing labels, corrosion, damaged fixings, unauthorised alterations and evidence that equipment is no longer fit for service. But inspection must also verify asset identity and traceability. Each anchor and line should be mapped, uniquely identified and tied to certification records, test information and any usage restrictions.
A useful report does more than state pass or fail. It records photographs, explains the risk priority, identifies whether a defect affects immediate use and sets out a clear remedial action. Where system documentation is missing or the original design intent cannot be established, the asset should not simply be treated as suitable for restraint, positioning or arrest. It requires technical review.
The same principle applies to PPE. Pre-use checks by the user, formal periodic examinations, quarantine procedures and equipment registers need to be controlled. A harness and lanyard with no legible identification, inspection history or compatible system specification is not audit-ready equipment.
Questions to settle before work starts
Before approving roof or façade work, the responsible person should be able to answer four practical questions: Can the task be completed from a protected area? Is the worker being prevented from reaching the fall hazard, or supported while working near it? What loads and directions can the anchor system safely accommodate? If the worker becomes suspended or incapacitated, how will they be recovered?
If any answer is unclear, pause the work and obtain a competent assessment. A contractor's method statement should match the installed assets and the actual route to the task, not describe a generic arrangement copied from another site.
Sky Height Safety approaches these decisions as an asset and compliance issue, not a catalogue exercise. The same team can inspect the existing installation, identify defects, specify remediation and provide the certifications your auditor actually wants to see. No subcontracted gaps in the chain and no missing paperwork.
The safest choice is often the one that prevents access to the danger altogether. Where work positioning is genuinely required, treat it as a controlled specialist activity: specify the system for the task, verify every component and make rescue arrangements real before anyone clips on.