5 Myths About Working at Height Rescue That Supervisors Still Believe

Working at height rescue is not an emergency appendix. It is part of the control system, because the moment a worker is suspended, the site is already managing time, access, and pressure. A rescue plan that cannot be executed is only documentation.

HSE guidance, OSHA fall protection rules, and ISO 45001 all treat emergency preparedness as part of the job, not as a separate afterthought. Across 25+ years in multinational EHS and more than 250 cultural transformation projects, Andreza Araujo has seen the same pattern repeat. The paper looks complete while the crew still lacks a named rescuer, staged equipment, or a stop rule that can be used in the field. In Safety Culture: From Theory to Practice, she argues that real culture shows up in repeated decisions under pressure, which is exactly where height rescue usually fails.

This article is for supervisors, maintenance leaders, and EHS managers who need rescue to behave like a live control, not a folder tab. If your team wants the broader permit view first, the rescue plan control guide shows how the permit should already be carrying the rescue logic.

Why these myths cost more than they look

A suspended worker does not wait politely while the site decides what to do. The clock starts when the fall is arrested, and the organization then has to manage access, communication, and movement without improvisation. That is why rescue delay is not a paperwork problem. It is a time problem that can quickly become a medical problem.

Many leaders still think rescue is something the emergency team handles after the task has started. That sounds sensible until the crew is on a roof edge, a scaffold bay, or a mobile platform with poor access and poor radio quality. The rescue plan exists to keep that moment from becoming a guessing game. If the site cannot prove the route, the roles, and the equipment before exposure starts, it is relying on hope.

Myth 1. A rescue plan attached to the permit means the job is ready

This myth feels true because the permit looks complete. There is a form, there is an attachment, and there may even be a signature at the bottom. A busy supervisor can mistake paper volume for control readiness, especially when the job seems routine and the crew wants to start on time.

ISO 45001 requires operational planning and emergency preparedness, which means the rescue plan must work in the field, not only in the binder. A generic phrase such as rescue available does not tell anyone whether the crew can reach the worker, lower the worker, or move the worker away from suspended exposure. Across more than 250 projects, Andreza Araujo has seen that the weak point is rarely the existence of a form. The weak point is the absence of a testable scenario.

What to do instead is simple and strict. Require one sentence that states the exact fall scenario, the access path, the recovery method, and the obstruction the team will face. If the supervisor cannot write that sentence for the south roof edge, the scaffold bay, or the MEWP basket, the job is not ready. The rescue plan is only real when it can be read as action.

Myth 2. If emergency services can come, the site is covered

This myth survives because outside help feels reassuring. Fire crews, site medical teams, or municipal responders are real assets, and nobody should dismiss them. The problem is that external response is only one part of the chain, while height rescue begins much earlier, with immediate access, communication, and a decision owner who can act without waiting for another organization.

The site still has to bridge the time gap before help arrives. That gap matters because suspension, weather exposure, and awkward body position do not pause for dispatch. James Reason's latent failure logic applies here, because the visible emergency is often only the last layer. The real failure may sit in planning, access, shift coverage, or the assumption that someone else would arrive in time.

The better practice is to name the internal rescuer and the back-up rescuer on the permit, then verify that both are present for the full exposure period. If the job needs an external responder, the site should also define the route, the access gate, the radio channel, and the person who calls for help. For teams that already manage other high-risk systems, the same thinking used in LOTO verification before restart applies here. The rescue cannot depend on a promise that has not been tested.

Myth 3. Fall arrest gear solves rescue

This myth is attractive because the harness feels like the safety answer. It stops the fall, which is real protection, and that visible protection can make leaders relax too soon. Once the fall is arrested, however, the work is not done. The worker may still be suspended, and the site may still lack a clear path to recovery.

The rescue problem is often hidden by equipment comfort. A site can have the right harness, lanyard, and anchor and still fail to stage the rescue kit, verify the anchor as a retrieval point, or confirm that the team can move the worker without crossing other hazards. As Andreza Araujo argues in Safety Culture: From Theory to Practice, culture is revealed when the organization compares what it says with what it can actually do.

The practical move is to treat fall arrest as the first barrier, not the last one. Stage the kit at the workface, verify the anchor as a rescue asset, and cross-check isolation if the rescue route passes near live systems. If the crew also needs a reminder that the rescue route and the energy isolation are linked, the rescue control guide shows the same logic from the permit side. Rescue is complete only when the worker can be reached, moved, and handed over.

Myth 4. One rescue drill proves readiness

This myth feels efficient. The drill happened, the team moved, and the form can now show a completed test. A single rehearsal is better than none, but it still does not prove that the next job will have the same crew, the same access, the same weather, or the same equipment location.

Andreza Araujo's diagnostic work has shown that culture is a pattern, not a snapshot. In Safety Culture Diagnosis: Learn how to do your own, the question is not whether the organization can perform once. The question is whether repeated decisions still hold when conditions change. A rescue drill that is never repeated after crew turnover or equipment changes does not deserve the word ready.

What to do instead is to time the drill, record the barriers found, and repeat it when the setup changes. If the drill is slow, confusing, or dependent on one experienced person, the plan is still fragile. Treat that fragility as a signal and not as a failure to be embarrassed by. A rescue drill is useful exactly because it exposes the weak point before a suspended worker pays for it.

Myth 5. Rescue is the rescuer's job, not the supervisor's

This myth sounds tidy because it assigns rescue to the specialist. The problem is that the supervisor owns the permit, the access decision, the crew mix, and the stop-work call. If the permit does not name the rescuer, communicator, and equipment handler, the rescue specialist is being asked to rescue a plan that never had ownership.

The supervisor also controls the conditions that keep rescue visible. That includes the workface walkdown, the communication check, and the decision to stop the job when the rescue setup is not present. Across 25+ years in multinational operations, Andreza Araujo has seen that the strongest rescue systems are the ones where line leadership accepts that control starts before the fall, not after it.

If the crew wants a clearer view of how declared control becomes field behavior, the broader rescue article on working at height rescue controls is the best companion. The supervisor does not need to be the rope rescuer. The supervisor does need to be the person who refuses to start work until the rope rescuer, the kit, and the stop condition are all real.

What to do now

Start with the next high-risk job and force the rescue plan to answer four plain questions. Who rescues? How do they reach the worker? What equipment is already at the workface? What condition stops the job if rescue is not ready?

• Write one exact rescue scenario for the next height task.
• Stage the kit where the fall can happen, not in a distant store room.
• Name the rescuer, communicator, and stop-work owner on the permit.
• Time one live drill and repeat it when the crew, location, or equipment changes.
• Treat any rescue delay as a precursor, not as a minor administrative miss.

If your team wants a stronger diagnostic lens, Andreza Araujo's safety culture work shows why declared controls fail when the field cannot verify them. The fastest way to improve rescue is not to write more words. It is to remove every assumption that has not been tested.

For leaders who want rescue to act like a control instead of a folder tab, start with the book at Andreza Araujo's store and then use Andreza Araujo to check whether the permit, the drill, and the field are still telling the same story.