How to validate a working at height rescue plan in 8 steps

A rescue plan for working at height is not a document that sits behind the permit. It is the proof that someone can bring a person down, transfer them safely, and hand them to medical care before the delay becomes the hazard.

Across 25+ years leading EHS at multinationals, Andreza Araújo has seen the same pattern repeat. The paperwork looks complete, yet the rescue path was never tested in the field. During the PepsiCo South America tenure, where the accident ratio fell 50% in six months, the lesson was hard to ignore: a control that nobody can execute on time is not a control.

As Andreza Araújo argues in Make The Difference: Be a Leader in Health & Safety, leadership is not approval theater. It is the discipline of checking whether the operation can do what the form promises. In Safety Culture: From Theory to Practice, the same logic appears from another angle, because culture shows up when a team repeats the right behavior under pressure, not when it files the right template.

In more than 250 cultural-transformation projects supported by Andreza Araújo's team, rescue planning usually failed in three places. Nobody owned the descent, nobody timed the sequence, and nobody verified the equipment against the actual access route. This guide fixes those three traps before the shift starts.

What you need before starting

Before anyone signs the rescue plan, collect the permit, the work-at-height method, the access drawing, the rescue equipment list, the communication method, and the name of the person who can actually trigger the response. You also need the team that will do the rescue, because a plan that depends on a person who is not on site is only a hope.

The point is not to build a thick folder. The point is to make sure the crew can point to the exact equipment, the exact route, and the exact owner without hesitation. If the team cannot do that, the plan is still a draft, even if the form is signed.

Step 1: Name the exact rescue scenario

Start by naming the event you are trying to control, because "working at height rescue" is too vague to be useful. A suspended worker, a stranded worker, a blocked ladder, and a failed transfer from a platform do not require the same response, the same tools, or the same person in charge.

The verification is simple. Ask the supervisor and the permit issuer to describe the rescue scenario in one sentence without reading the form. If they need the paper to remember what they meant, the scenario is not specific enough. The common error is to let emergency services become the whole plan, which answers who may arrive but not who completes the rescue.

Step 2: Confirm the access path and the descent path

A rescue plan only works if the team knows how to reach the person and how to bring them down. That means the access path, the anchor point, the lowering method, and the landing area all need to be visible in the same sequence, because one weak point in that chain can stop the whole response.

Verify the path in the same conditions the crew will face during the job. If the route depends on a locked gate, a blocked corridor, or a piece of equipment that is not there yet, the plan is weaker than it looks. The common error is to assume the rescue line will be improvised after the event starts, which turns delay into the first failure.

Step 3: Assign one owner and one backup

Every rescue plan needs one owner who can trigger the sequence and one backup who can take over if that person is absent. Across 250+ projects, Andreza Araújo has seen plans drift the moment ownership became collective in theory and invisible in practice. When everyone is responsible, nobody moves first.

Verify the ownership by asking two questions. Who gives the stop signal, and who takes control if the first person is unavailable? If the answer is "the team" or "the supervisor and EHS," the role is still too broad. The common error is to make the rescue owner the same person who is already overloaded with production decisions, because then the rescue plan loses attention exactly when attention matters most.

Step 4: Check the equipment against the real height task

Rescue equipment must match the actual work, not the generic category on the purchase order. A kit that is right for one scaffold or one platform can fail on another if the anchor height, clearance, or descent distance is different. In Safety Culture: From Theory to Practice, the practical lesson is clear: the field decides whether the control is real.

Lay out the equipment before the shift and compare it with the real access point. If a lifeline, descent device, stretcher, or connector cannot be deployed without improvisation, the plan is still incomplete. If your access system itself is not yet clear, read Scaffold Handover: How to Accept It in 20 Minutes before you treat the rescue plan as ready.

Step 5: Time the rescue sequence under field conditions

The only time that matters is the time the team actually needs to reach, secure, lower, and hand over the person. A rescue plan that looks elegant on paper can still fail if the team has never rehearsed the sequence against the real access route, the real equipment, and the real communication delay.

Run the sequence with the people who will be present on the day, not with an idealized team. Ask them to show the path, not explain it. Verify whether the sequence remains smooth when gloves, weather, height, or limited space make the job less convenient. The common error is to treat a verbal walkthrough as a rehearsal, because a spoken description does not expose the friction that the field will create.

Step 6: Confirm communication and trigger thresholds

Rescue fails when the alarm is unclear, the escalation line is slow, or the first caller wastes time deciding who to contact. The team needs a simple trigger threshold, a named contact path, and a communication method that still works when the worker is out of sight or the noise level is high.

Test the communication the same way you test the equipment. Use the device, call the number, and check whether the right person answers fast enough to matter. The common error is to depend on a radio channel, a phone number, or a verbal chain that is reliable in the office but weak on the platform. That is why this step belongs in the plan, not in a separate memo.

Step 7: Rehearse with the actual crew and the actual constraints

Andreza Araújo has seen field teams change the quality of a rescue plan in one rehearsal, because the drill exposed what the meeting had hidden. The rehearsal does not need to be theatrical. It needs to be honest enough to show where the plan slows down, where the team hesitates, and where the equipment becomes awkward.

Use the same crew that will do the work, or at least the same roles, because rescue logic changes when the people change. Ask the crew to point out the first confusing moment and the first risky movement. The common error is to run the drill only for compliance, then file the result without changing the weak point that the drill exposed.

Step 8: Record the approval, the stop condition, and the review date

A rescue plan is not finished when it is signed. It is finished when the approval has a stop condition, a review date, and a clear rule for when the work must pause. If the rescue method changes, the access changes, or the crew changes, the plan needs another look before the task continues.

Verify the record by checking whether the sign-off includes the owner, the backup, the drill date, and the conditions that invalidate the approval. In more than 250 transformation projects, Andreza Araújo has found that the strongest controls are the ones the field can revisit quickly, because that is how plans stay alive. If you want the companion view on who should actually provide rescue capacity, compare this guide with On-site Rescue Team vs Municipal Emergency Services vs Mutual Aid: Which Model Fits High-Risk Work.

Final checklist

• The scenario is specific, and the crew can describe it without reading the form.
• The access path, descent path, and landing area are visible in the real work area.
• One owner and one backup are named, and both know the trigger signal.
• The rescue equipment matches the actual height task and is staged where it will be used.
• The crew rehearsed the sequence under field conditions, not only in a meeting room.
• The approval includes the stop condition, the review date, and the change trigger.

Conclusion

A valid rescue plan for working at height is the one the crew can execute before improvisation starts. It names the scenario, matches the access route, assigns ownership, proves the equipment, and tests the sequence under the same constraints the job will create.

That is why Andreza Araújo treats rescue planning as a leadership test, not a paperwork test. The operation is safer when the form and the field say the same thing, and the field can prove it. For the next layer, read On-site Rescue Team vs Municipal Emergency Services vs Mutual Aid: Which Model Fits High-Risk Work and then review MEWP Pre-Use Inspection: 8 Steps in 15 Minutes if the height task depends on mobile access equipment.