Height Safety: What Your Building Must Prove

A roof access door opens, a contractor goes through it, and the building becomes a working-at-height site. At that point, height safety cannot be assumed from an old certificate, a familiar-looking safety line or a guardrail that appears intact from ground level. The duty holder needs evidence that the route, equipment and system are suitable for use now.

For facilities and estates teams, the issue is rarely a lack of intent. It is fragmented information: a handover file from a previous owner, undocumented alterations, several contractors, expired test dates and defects that have not been risk-prioritised. That is where compliance fails. Not because a document is missing in isolation, but because nobody can show a clear chain from asset condition to corrective action and certified handover.

Height safety is a system, not a product

Working at height is governed by the Work at Height Regulations 2005. The starting point is straightforward: avoid work at height where reasonably practicable; where it cannot be avoided, prevent falls; where risk remains, minimise the distance and consequences of a fall. The control measure must suit the task, the building and the people using it.

That means a roof safety line is not automatically the right answer. Collective protection, such as permanent edge protection or guarded walkways, normally protects more people with less reliance on individual behaviour. Personal fall-protection systems may be necessary where a parapet is too low, equipment sits close to an edge or access constraints prevent guardrails. But they introduce further requirements: compatible PPE, rescue planning, user competence, anchor strength and clear instructions.

A compliant arrangement considers the full journey. Can the person reach the roof safely? Is the fixed ladder secure and correctly configured? Does the roof hatch provide a protected transition? Are fragile rooflights identified or protected? Is there a defined walkway to plant? Can the user connect to an anchor without entering an unprotected area? If an incident occurs, can they be recovered promptly?

Treating each item as a separate purchase creates gaps. Treating the route as one controlled system exposes those gaps before somebody is put at risk.

What an auditor will expect to see

An auditor does not need a polished folder. They need current, traceable evidence. A certificate with no asset reference, no inspection scope and no defect record may be of limited value. Equally, an asset register that lists equipment but does not state its status, location or next inspection date leaves the duty holder unable to control use.

A credible height safety record should identify each relevant asset, its precise location, its manufacturer or installation details where available, the applicable standard or design basis, and its inspection status. It should also show what was inspected, who completed the work, what defects were found and what action is required.

Photographic evidence matters. A pass or fail result alone may not explain why an eyebolt has failed, why a rooflight guard needs replacement or why a cable system requires components to be changed. Clear photographs allow estates teams, procurement colleagues and senior decision-makers to understand the issue without relying on verbal interpretation.

The strongest documentation also separates defects by risk. An immediately unsafe anchor point should be taken out of service and clearly labelled. A damaged handrail, missing signage or incomplete asset data may require correction but could be managed differently depending on the risk assessment. Everything cannot be treated as equally urgent, but nothing should be left vague.

Inspection is not the same as recertification

This distinction causes avoidable confusion. A visual walkover can identify obvious concerns, but it may not be enough to establish that a system remains safe and fit for use. Inspection and testing requirements depend on the equipment type, manufacturer guidance, usage, environment and relevant standards.

For example, anchor devices and safety-line systems are commonly assessed against requirements linked to BS EN 795, with multi-user arrangements also requiring consideration of CEN/TS 16415 where applicable. The inspection needs to consider more than the visible post or eye. Fixings, substrate condition, cable tension, energy absorbers, intermediate brackets, labels and previous modifications can all affect performance.

Fixed ladders, guardrails, roof walkways, davit systems, abseil anchors, mobile man anchors and skylight protection each have different failure modes. Corrosion at hidden fixings, water ingress around penetrations, loose ballast, altered roof finishes and incompatible repairs are regular problems on live estates. Lightning protection systems require their own inspection approach and records under BS EN 62305.

The correct interval is not simply a date copied from last year's certificate. Many fall-protection systems require periodic formal inspection at least every 12 months, while some equipment, use cases and manufacturer instructions require more frequent checks. PPE also needs pre-use checks and periodic examinations by a competent person. The point is not to apply one interval to every asset. It is to define, record and maintain the right interval for each one.

The common failures on established buildings

Legacy buildings are where height safety becomes most complicated. Roof plant changes over time. New air-conditioning equipment is installed, solar arrays alter access routes, roof coverings are renewed and contractors create temporary solutions that quietly become permanent. The original fall-protection design may no longer reflect how the roof is actually used.

The most serious issue is often an access route that directs a user towards an unprotected hazard. A roof hatch may open beside a fragile rooflight. A plant engineer may need to step outside the reach of a safety line to work on equipment. A guardrail may stop short of a route used for maintenance. These are operational defects, not paperwork defects.

Another recurring problem is unverified anchors. An eyebolt may look serviceable but have no traceable installation record, no identifiable fixing specification and no current inspection result. Until its suitability is confirmed, it is non-compliant by default for planned personal fall-protection use.

There is also a commercial risk in partial reporting. A contractor may identify a defect but offer no clear recommendation, no fixed scope for remediation and no certification after the repair. The facilities team is then left to coordinate separate parties and explain who holds responsibility. That is exactly where no subcontracted gaps in the chain matters.

A controlled route from inspection to handover

The practical answer is a repeatable process. Start with a site survey that records all roof-access and fall-protection assets, not just the assets already listed by the client. The engineer should assess the access route, condition, use case, test status and visible surrounding hazards.

The written report should follow quickly, ideally within 48 hours, and use clear pass, fail and advisory findings. It should include asset references, defect photographs and a risk-prioritised action plan. This gives the duty holder a usable decision document rather than a technical report that sits unread.

Where remedial work is required, the scope needs to be precise. “Repair safety line” is not a scope. Replacing identified cable components, re-tensioning to the manufacturer's requirement, renewing damaged labels, testing the completed system and issuing revised certification is a scope. The difference protects budget control and makes final handover auditable.

After installation or remediation, the documentation pack should bring the record back together: inspection or test certificates, asset register updates, photographs, installation details, user information where relevant, and the next due date. Same team, same documentation, no missing paperwork.

Height safety decisions should follow actual use

There is no single best solution for every roof. Guardrails may be the strongest option where frequent access is expected and roof geometry allows them. They can reduce reliance on PPE and simplify contractor use, but may need structural consideration, visual planning approval or careful detailing around drainage and roof warranties.

Safety lines and anchor systems can be appropriate where collective protection is impracticable. They are less visually intrusive in some settings and can protect access to constrained plant areas. However, their effectiveness depends on user training, correct lanyard selection, connection discipline and a workable rescue plan. A system that requires perfect user behaviour is not automatically wrong, but it needs tighter management.

Skylight protection deserves particular attention. A rooflight is often mistaken for a safe walking surface, particularly where it is dirty, painted or visually similar to the surrounding roof. Guards, covers, protected routes and clear identification should be considered based on the roof layout and maintenance activities. A warning sign by itself does not prevent a fall through a fragile surface.

Questions procurement teams should ask

Before appointing a contractor, ask whether the inspection will cover the complete access route and associated hazards, not merely a named asset. Ask who will carry out the work, whether testing and remedial works are delivered by the same accountable specialist, and what evidence will be supplied after the visit.

Also ask how failed assets are controlled. Will they be labelled or isolated where necessary? Will the report distinguish urgent restrictions from planned improvements? Will the contractor provide a defined remedial quotation and updated certification once work is complete? These questions reveal whether you are buying a compliance process or simply a site visit.

Sky Height Safety works on this basis: inspect the assets, identify the risk, correct the defect and provide the certifications your auditor actually wants to see. That approach gives facilities teams a controlled record of what is safe to use, what is not and what happens next.

The useful test is simple. If a contractor arrived tomorrow to service roof plant, could you show them a safe route, current equipment status and clear instructions without searching through old files? If not, the next inspection should be used to build that control, not merely renew a certificate.