Working at Height Safety: UK Employer Guide 2026
- Jul 13
- 14 min read
50 workers died in falls from height in Great Britain in 2023/24, making it the leading cause of worker fatalities and accounting for 36% of all worker deaths according to IOSH Magazine's report on HSE findings. That figure should change how employers think about working at height safety. This isn't a narrow construction issue, and it isn't solved by buying harnesses and sending out a toolbox talk.
In practice, most failures happen much earlier. The task wasn't designed out. The wrong access method was chosen. The ladder became a workstation. The supervisor accepted a shortcut. The rescue plan didn't exist because everyone assumed prevention was enough.
That last point is where many organisations still have a dangerous blind spot. They plan for stopping the fall. They don't plan for recovering the person who's left suspended after it. Legally and operationally, that gap matters.
Table of Contents
Your Legal Duties Under the Work at Height Regulations 2005 - What the law expects in practice - Reasonably practicable means defensible choices
The Hierarchy of Controls A Practical Framework - The sequence matters - A workable hierarchy on live sites
Choosing and Inspecting the Right Equipment - Choose equipment for the task not for convenience - What a competent inspection process looks like - Where ladder use goes wrong
Bridging the Rescue Gap Planning for the Worst - Why calling emergency services isn't a rescue plan - What a site specific rescue plan should contain
Embedding Safety Through Training Audits and Documentation - Competence has to be evidenced - Audits should test reality not paperwork - Documentation should help people work safely
Why Working at Height Safety Demands Your Full Attention
Falls from height remain one of the main causes of fatal work injuries in Great Britain. That point was set out earlier. What matters here is what that figure means on site. A height risk can sit inside ordinary work, pass through planning unnoticed, and turn a routine task into a fatal one within seconds.

Clients and contractors often picture work at height as exposed roof edges, steel frame erection, or complex scaffold operations. Those jobs carry obvious risk, but they are not the only problem. I see incidents and near misses arise from short-duration maintenance, access to plant, fragile surfaces, loading areas, ladder work, and improvised methods used to save time.
Routine jobs cause real harm.
A caretaker changes lighting from the wrong access equipment. A contractor steps onto a roof for a quick inspection without checking the surface. A warehouse team member climbs racking to free stock because the proper platform is not nearby. None of that looks dramatic at the start. That is exactly why weak controls survive for so long.
Another point gets missed in many height safety discussions. Preventing the fall is only part of the duty. If a worker is left suspended in a harness, the risk does not stop because the person did not hit the ground. Suspension trauma, restricted access, delayed retrieval, and poor coordination can turn a survivable incident into a medical emergency. That rescue gap is still badly handled on many UK sites, and it exposes employers both legally and operationally.
From a client-side view, a frank evaluation of trade-offs becomes necessary. The fastest access method is not always the safest. The cheapest equipment option may increase supervision demands. A contractor with a clean RAMS pack may still be the wrong choice if they cannot explain how they would recover a suspended worker. Good height safety management means testing the reality of the job, not accepting paperwork at face value.
One practical rule applies across every sector. If safe completion depends mainly on someone being careful, the system has already been set up poorly.
Effective control comes from decisions made before the job starts and checked while it is underway. Access method, ground conditions, competence, inspections, exclusion zones, weather, nearby services, and rescue capability all need to line up. When they do not, the job should stop until they do.
That is the standard clients should expect from any business directing work at height. Luck is not a control measure.
Your Legal Duties Under the Work at Height Regulations 2005
The Work at Height Regulations 2005 are often quoted but not always applied properly. The legal duties sound simple enough. Work at height must be properly planned, appropriately supervised, and carried out by competent people. The challenge is translating those duties into decisions on real sites, with deadlines, contractors, changing conditions, and pressure to keep work moving.
What the law expects in practice
Start with the basics. An employer has to make sure the task has been assessed before anyone leaves the ground. That means identifying the hazard, selecting the safest access method, controlling the surrounding area, and deciding how the task will be supervised. It also means checking whether the work can be avoided altogether.
A legally sound approach usually includes:
Task definition: State exactly what the worker is doing at height, for how long, and with what tools or materials.
Access choice: Match the method to the duration, frequency, environment, and consequence of failure.
Ground conditions: Confirm that floors, roofs, platforms, and support points are suitable for the intended load and equipment.
Supervision arrangements: Decide who is authorising the work, monitoring the controls, and stopping the task if conditions change.
Competence checks: Verify that the people involved understand the method, equipment limits, and emergency actions.
Rescue provision: Put a realistic recovery plan in place before work starts, not after an incident.
The law doesn't expect perfection. It expects employers to make sensible, informed, and defensible decisions before exposing people to risk.
Many organisations fail by confusing documentation with planning. A generic risk assessment copied from a previous job won't help if the actual workface is different. A method statement that says “use suitable PPE” isn't a control. It's a placeholder.
Reasonably practicable means defensible choices
“Reasonably practicable” doesn't mean doing the minimum you can get away with. It means weighing the risk against the time, trouble, and cost of control, then choosing measures that a competent employer would regard as sensible. For work at height, that usually means stronger controls than managers first assume, because the consequence of failure is so high.
The business impact is also too large to ignore. Non-fatal falls from height led to 416,000 working days lost in 2024/25, and the estimated total cost exceeded £956 million in 2023/24, as set out in UK falls from height statistics. Even where nobody dies, the disruption can be substantial. Absence, investigation time, delayed programmes, replacement labour, insurer scrutiny, damaged relationships with clients, and lower workforce confidence all follow.
A practical legal standard looks like this:
Core duty: Avoid the work at height where it's reasonably practicable. If you can't avoid it, prevent falls. If you can't fully prevent them, reduce the distance and consequences.
That standard should be visible in everyday management. If supervisors routinely accept short-duration ladder jobs that should be done from a tower or MEWP, the system isn't compliant in substance. If contractors arrive with their own method and nobody tests whether it matches site rules, the client side is too passive. If a permit is issued without rescue arrangements being checked, the authorising process is incomplete.
Employers who stay out of trouble do one thing consistently. They make the safe method the default method. Workers shouldn't have to argue for proper access. The system should already require it.
The Hierarchy of Controls A Practical Framework
The hierarchy of controls is the backbone of effective working at height safety. It isn't a menu. It's a sequence. Teams get into trouble when they jump straight to personal protective equipment because it feels tangible and easy to issue. In UK practice, that shortcut has serious consequences. Personal fall arrest systems are a last resort, and HSE enforcement data indicates that over 60% of fatal fall incidents involve premature reliance on them instead of collective protection, as explained in this guide to work at height risk assessment.
The sequence matters
A control only counts if it removes or reduces the risk better than the option below it. That's why a harness can't automatically outrank a guardrail just because it looks specialist. The hierarchy starts by asking whether the task can be done without anyone working at height at all.
Here's the framework in practical terms:
Control Level | Principle | Practical Example |
|---|---|---|
Avoid | Remove the need to work at height | Use extendable tools from ground level or inspect roof areas by camera rather than sending someone onto the surface |
Existing safe place | Use a location that is already safe | Carry out work from a permanent walkway with fixed edge protection |
Collective protection | Protect everyone exposed to the risk | Install scaffold with guardrails, toe boards, or safety netting |
Personal protection | Protect the individual only when stronger measures aren't reasonably practicable | Use a restraint or fall arrest system with suitable anchorage and a rescue plan |
The common mistake is easy to spot. A job is awkward, time is tight, and someone says a harness will “cover it”. It won't, unless the anchor, clearance, swing fall risk, user competence, and rescue arrangements have all been thought through. In many environments, restraint is safer than arrest because it stops the person reaching the fall edge in the first place.
If a team reaches for PPE before it has asked whether the task can be avoided or collectively protected, it has skipped the legal logic of the hierarchy.
A workable hierarchy on live sites
On construction projects, avoidance might mean assembling components at ground level before lifting them into position. In manufacturing, it might mean relocating a routine inspection point so operators don't need to climb onto plant. In events and theatre settings, it often means designing rigging, lighting maintenance, or access routes so technicians can work from suitable platforms rather than improvised positions.
The stronger the planning stage, the easier the hierarchy becomes to apply. A proper risk assessment should force the team to justify the access method instead of choosing it by habit. That's where a structured approach helps. This guide on how to conduct a risk assessment is a useful prompt for making sure hazards, controls, and residual risks are tested in the right order.
A practical decision process often looks like this:
Challenge the task: Is it necessary for someone to go up, or is this legacy practice?
Check fixed infrastructure: Is there an existing safe platform, walkway, or guarded area?
Select collective controls: Could a tower, scaffold, edge protection, or netting control the risk for everyone?
Use personal systems carefully: If personal systems are the only realistic option, define anchor points, clearance, exclusion zones, and rescue arrangements before work starts.
There's also a cultural element. Supervisors need permission to reject weak methods, even when the client wants speed. Procurement teams need to stop buying access solutions on price alone. Maintenance planners need enough lead time to arrange the right kit rather than sending operatives with whatever fits in a van.
That's what effective working at height safety looks like in practice. The hierarchy becomes part of how the organisation thinks, not just a diagram in a policy.
Choosing and Inspecting the Right Equipment
Equipment selection is where good intentions often drift into poor control. A site may have ladders, harnesses, scaffold tags, anchor points, and MEWPs available, but that doesn't mean the task is properly equipped. The right question isn't “what do we own?” It's “what gives the worker the safest, most stable, and most controllable way to do this specific job?”

Choose equipment for the task not for convenience
Ladders, tower scaffolds, podiums, fixed platforms, MEWPs, and personal fall protection all have their place. Problems start when convenience drives the choice. The ladder is nearest. The harness is already in the stores. The scaffold takes longer to arrange. Those are operational reasons, not safety reasons.
Use broad decision criteria before authorising equipment:
Duration and frequency: Short, light access work may suit a ladder. Repetitive or hands-on tasks usually need a more stable platform.
Need for both hands: If the worker has to handle tools, materials, or fixings, a platform is often more appropriate than a ladder.
Ground and access conditions: Uneven surfaces, pedestrian routes, vehicle movement, and weather all change what's suitable.
Fall consequence: The more severe the likely outcome, the less tolerance there should be for minimal controls.
Rescue implications: If a personal system is involved, the rescue method must be compatible with the location.
Scaffold and MEWP decisions need the same discipline. A mobile tower may be fine indoors on a level surface and completely wrong outside on congested ground. A MEWP may be the best option for reach and duration, but only if the route, outriggers, overhead obstructions, floor load, and operator competence have been checked.
What a competent inspection process looks like
Inspection has two layers. The first is the pre-use check carried out by the user. The second is the formal inspection regime carried out by someone with the right knowledge and authority. Businesses often have one and neglect the other.
A reliable pre-use check should look for obvious defects, missing parts, damage, contamination, poor storage condition, insecure fixings, illegible markings, and anything that suggests the equipment has been modified or overloaded. For harnesses and lanyards, that means checking webbing, stitching, buckles, connectors, energy absorbers, and attachment points. For ladders, it means checking stiles, rungs, feet, locking mechanisms, and signs of bending or cracking.
Formal inspection is different. It needs records, intervals, traceability, and a clear process for taking defective equipment out of service. If nobody can say who last inspected a harness or whether an anchor point was verified for the intended use, the system is weak.
This short demonstration is useful for reinforcing correct harness setup before use:
Field test: Ask a supervisor to show you the quarantine process for defective equipment. If the answer is vague, damaged kit is probably staying in circulation too long.
Where ladder use goes wrong
Ladders remain one of the most commonly misused access tools. According to UK working at height statistics from Leading Edge Safety, the majority of non-fatal incidents from height stem from ladder misuse, especially failure to maintain the 75° angle, lack of lashing or footing, and using ladders as working platforms rather than for short-duration access.
That pattern shows up repeatedly in site reviews. The ladder is too shallow or too steep. It isn't secured. The operative overreaches because the ladder wasn't repositioned. Materials are carried in a way that compromises three points of contact. The task lasts far longer than a ladder should reasonably support.
Practical ladder controls are straightforward:
Set the angle correctly: The 75° or 4:1 rule matters because it improves stability.
Secure the ladder: Lash it where possible, or provide effective footing where that is the control.
Use it for access or brief work only: If the task needs time, force, or two-handed effort, upgrade the access method.
Reposition instead of overreaching: Belt buckles outside the stiles are a warning sign.
Inspect before each use: Don't normalise bent feet, worn treads, or makeshift repairs.
Most equipment failures in this area aren't technical mysteries. They're management failures expressed through equipment choice.
Bridging the Rescue Gap Planning for the Worst
Many employers put real effort into preventing falls and almost none into recovering a worker after one. That's the rescue gap. It exists because organisations treat rescue as an emergency services issue instead of a work planning issue. Under the regulations, that approach is not good enough. Emergency rescue procedures are the most frequently overlooked statutory duty under the Work at Height Regulations 2005, and 40% of UK construction firms fail to have site-specific rescue plans, according to HSE guidance on work at height.
Why calling emergency services isn't a rescue plan
A suspended worker may be injured, unconscious, trapped against a structure, or unable to self-recover. Waiting passively for external responders can leave the person exposed to worsening harm. A rescue plan has to answer who will act, with what equipment, by what route, under what command, and how the casualty will be transferred to a place of safety.

A generic statement such as “call 999” fails on two fronts. First, it doesn't provide an immediate site response. Second, it doesn't show that the employer has considered the actual rescue geometry of the task. Lowering a suspended worker from a steel frame, retrieving someone from a roof edge, or recovering a person inside an event structure all need different arrangements.
Rescue planning should start with a blunt question. If the worker falls and remains suspended, how exactly do we get them down safely with the people and equipment on site?
A changing workface makes this harder. One day the task is from a MEWP. The next it's from a temporary platform near services, ducting, or public areas. That's why rescue planning has to be site specific and task specific, not copied from a training folder.
A useful supporting discipline is dynamic assessment. This explanation of dynamic risk assessment is relevant because rescue arrangements often need revisiting when access routes, weather, occupancy, or nearby operations shift.
What a site specific rescue plan should contain
A workable rescue plan doesn't need to be long. It needs to be usable. In practice, include the following:
Likely fall scenarios Identify where suspension could occur, what the worker may strike, and whether the casualty could be conscious, injured, or difficult to access.
Rescue method State whether the plan is to lower, raise, recover to a platform, use the MEWP basket, or deploy a dedicated rescue kit. One method rarely fits every task.
Named people and roles Specify who leads the rescue, who manages the area, who contacts emergency services, and who supports casualty care once the person is down.
Equipment list Detail what must be on site, where it is stored, how it is checked, and who is trained to use it.
Access and exclusion arrangements Confirm how rescuers reach the casualty and how the ground area below is controlled.
Practice and review Drill the plan often enough that the team can carry it out under pressure, then update it when the task or location changes.
One final point matters. Rescue planning shouldn't sit with the safety adviser alone. Supervisors, contract managers, and the people doing the work must understand it well enough to act decisively. In an actual suspension event, hesitation is common. Good planning reduces it.
Embedding Safety Through Training Audits and Documentation
Strong working at height safety doesn't depend on one excellent risk assessment or one energetic supervisor. It depends on a management system that keeps producing the right decisions after the initial attention has faded. That means training people properly, checking whether the rules are being followed, and maintaining documents that support real work rather than satisfy a file.
Competence has to be evidenced
“Competent person” is one of the most misused phrases in health and safety. Plenty of organisations assume that experience alone is enough. Sometimes it is. Often it isn't. Competence in work at height comes from a combination of training, knowledge, practical skill, and the ability to recognise when conditions have changed enough to stop and reassess.
For managers, a critical question is evidence. Can you show why a person is authorised to inspect ladders, specify an anchor point strategy, supervise roof work, or approve a rescue method? If the answer is “they've always done it”, that's weak.
This guide to what counts as a competent person is a useful reference point when you're defining responsibilities for supervisors, facilities teams, and contractors.
A practical competence system usually includes:
Role-specific training: Differentiate between users, supervisors, inspectors, permit issuers, and rescue team members.
Authorisation limits: Define what each person can approve and what must be escalated.
Refreshers and reassessment: Revisit high-risk activities when work methods, equipment, or environments change.
Contractor verification: Check external teams with the same rigour you apply internally.
Audits should test reality not paperwork
A good audit asks whether the planned controls are visible where the work happens. It doesn't stop at document review. It checks the ladder angle. It checks whether harnesses are in date and stored correctly. It checks whether operatives understand the rescue plan without reading it aloud from a clipboard.
Useful audit themes include:
Method versus practice: Is the team working the way the RAMS say it will?
Equipment condition: Are access tools and fall protection gear fit for use and traceable?
Supervision quality: Does the supervisor intervene when the method starts to drift?
Permit standards: Are high-risk tasks being authorised with meaningful checks?
Learning loop: Do incidents, near misses, and observations lead to updated controls?
Paperwork should predict the job. If it describes an ideal task that nobody is actually doing, it won't control risk.
The best audits also sample ordinary jobs, not just high-profile ones. Serious failures often hide in routine maintenance, reactive fixes, and contractor visits because those tasks attract less scrutiny than major projects.
Documentation should help people work safely
Documents fail when they become too generic, too long, or too detached from the task. A risk assessment should identify the actual hazards on that site. A method statement should explain the sequence clearly enough that a supervisor can brief it and a worker can follow it. A permit should force the right conversations before work starts.
That means writing for use, not for appearance. Keep language direct. Match photos, sketches, or diagrams to the actual work area where useful. Remove stale controls that no longer reflect the equipment or layout. Version control matters, but usability matters more.
For most organisations, the strongest system is cyclical:
Train people for their role
Plan the task properly
Authorise high-risk work carefully
Observe the job in the field
Correct drift immediately
Update documents and training from what you learn
That cycle is what turns working at height safety from a legal requirement into an operational standard.
If your organisation needs practical support with work at height compliance, rescue planning, competent-person training, audits, or site-specific documentation, KODOBI can help you build a proportionate system that works in practice, not just on paper.














Comments