Testing and Inspections

Testing and inspections by a competent company give you peace of mind that your fall protection and safe access systems are safe to use, and compliant.

It is a legal requirement that all fall restraint or arrest, rescue, and rope access systems are inspected, tested, tagged, and supported with formal certification.


Following installation, all systems must be tested and inspected annually by a competent and qualified person to ensure they are fit for purpose. This must be done in accordance with relevant industry regulations and standards including:

And manufacturer’s specific recommendations.

HOS fall protection specialist on a roof inspecting and tagging a lifeline system post
Man carrying out a swage test inspection on a lifeline cable and connector

Rope Access Systems

Rope access systems are also subject to the Lifting Operations and Lifting Equipment Regulations (LOLER), which stipulates six-monthly inspections. In addition, personal protective equipment (PPE) must  be inspected at least every 6 months, depending upon use.

If certification expires, or a system is subjected to a fall, it is your responsibility to ensure it is inspected, repaired where necessary, and recertified before further use.


Customers can rely on our CRM system and dedicated scheduling team to manage their annual recertification. 

We will notify you one month prior to an expiry date that a visit is required. This ensures the testing programme is in place and that you remain complaint. 

In the event of system failure or non-compliance, a full report and guidance on the necessary remedial action will be provided, together with the associated costs.

Person holding torn webbing from a fall protection harness
Height of Safety worker installing a guardrail on a roof. In the background you can see a city skyline

The Height of Safety team can inspect, test and certify all the following:

We also cover Personal Protective Equipment (PPE)

Most systems must be inspected and tested every 6 to 12 months, depending on the frequency of use, environment, and system type.