Occupational Safety

How to Audit Contractor Rescue Readiness Before High-Risk Work in 6 Checks

A rescue plan is not evidence of rescue readiness. This six-check audit helps EHS managers and permit owners test whether contractor teams have the people, equipment, access, communication, and decision authority required to recover a worker when the planned controls fail.

By 5 min read
industrial scene illustrating how to audit contractor rescue readiness before high risk work in 6 checks — How to Audit Contr

Key takeaways

  1. 01A written rescue plan becomes credible only when the contractor can demonstrate the decisions, resources, access, and communication it requires.
  2. 02The audit should test the gap between the plan on paper and the first ten minutes of a realistic rescue scenario.
  3. 03Permit approval is not the same as rescue readiness because the permit may confirm controls without proving recovery capability.
  4. 04Contractor and host responsibilities must be explicit before work starts, including who calls for help, who stops the job, and who leads the response.
  5. 05ISO 45001, published in 2018, supports emergency preparedness and response, but the organization still has to verify that the planned response can work at the point of use.

F2 how-to guide for EHS managers, permit owners, and contractor supervisors

A contractor can submit a polished rescue plan and still be unable to recover a worker when the job changes. The document may name a rescue team, list equipment, and describe an escalation route, yet none of those statements proves that the response will work from the actual point of exposure.

This guide gives the host organization a practical audit before high-risk work starts. The thesis is direct: rescue readiness is a capability to demonstrate, not a document to file. The six checks focus on the first decisions and actions that follow a credible rescue trigger.

Key Takeaways

  • A written rescue plan becomes credible only when the contractor can demonstrate the decisions, resources, access, and communication it requires.
  • The audit should test the gap between the plan on paper and the first ten minutes of a realistic rescue scenario.
  • Permit approval is not the same as rescue readiness because the permit may confirm controls without proving recovery capability.
  • Contractor and host responsibilities must be explicit before work starts, including who calls for help, who stops the job, and who leads the response.
  • ISO 45001, published in 2018, supports emergency preparedness and response, but the organization still has to verify that the planned response can work at the point of use.

What you need before starting

Bring the permit, task risk assessment, rescue plan, crew list, equipment register, emergency contacts, site map, and host emergency procedure. Use the actual work location rather than a generic contractor template, because distance, access, weather, simultaneous operations, and shift coverage can change the response.

Review the material with the contractor supervisor and host permit owner together. A joint review exposes interface failures earlier than two separate approvals, particularly when each party assumes that the other owns the call, the equipment, or the first response.

Step 1: Define the rescue trigger

Ask the team to name the conditions that require the work to stop and the rescue response to begin. The trigger might be a fall, loss of consciousness, entrapment, hazardous atmosphere, failed communication, or medical event. Avoid accepting “in an emergency” because it leaves the first decision to interpretation under pressure.

Then ask who can declare the trigger and whether that person can stop the task without waiting for a manager. The answer should be clear to the contractor crew, host representative, and anyone taking over the shift. If the team cannot state the trigger in operational language, the plan is not ready for approval.

Step 2: Trace the first ten minutes

Walk through the response in sequence. Who sees the problem, raises the alarm, calls the site emergency number, stabilizes the area, protects other workers, and starts the rescue? Put each action against a clock and a named role, because “the team will respond” is not a sequence that anyone can verify.

Test the sequence against a night shift, blocked access route, missing radio, or supervisor at another work front. The purpose is to identify the dependency that would make the response fail before a real person is waiting for help.

Step 3: Verify people and competence

Match every critical action to a person who is present, trained for that action, and able to perform it in the work environment. Check the rescue lead, first responder, equipment operator, communicator, isolation owner, and host emergency contact. A certificate in a file does not prove that the named person is on the shift or can reach the worksite.

Ask each role holder what they would do if the planned method became unavailable. This tests understanding without turning the audit into a memory contest. James Reason’s distinction between active failures and latent conditions is useful because a missed response can reflect staffing, planning, supervision, or equipment availability rather than one person’s final action.

Step 4: Inspect equipment at the point of use

Locate the equipment where the plan says it will be. Check compatibility, inspection status, accessibility, lighting, storage, and whether the team can move it through the required route. A rescue device locked in a vehicle, stored on the wrong level, or incompatible with the anchor arrangement is not available evidence.

Ask the contractor to demonstrate the critical setup without exposing anyone to unnecessary danger. Where a live demonstration is unsafe, use a controlled verification with equivalent equipment and record the differences.

Step 5: Test communication and host interfaces

Have the contractor and host team use the real communication method, emergency number, location description, and escalation route. Confirm who receives the call, who meets external responders, who controls access, and who communicates with the worker’s supervisor. These details often fail at the boundary between organizations, where each side believes the other has already made the arrangement.

Include language, literacy, and shift pattern in the check. Communication is a control only when people can understand the message, repeat the location, and act on the instruction. A posted number nobody has tested is an administrative detail, not rescue capability.

Step 6: Close the gaps before authorizing work

Classify each finding according to whether it blocks the work, requires correction before the next shift, or can be monitored without increasing exposure. Do not turn every gap into a low-priority action because the permit deadline is approaching. If the crew lacks a critical skill, equipment, access route, or communication path, delay or redesign the work.

Assign one owner to each correction and define the evidence required for closure. The permit owner should show what changed, who verified it, and why the remaining exposure is acceptable. Andreza Araujo’s work on the difference between compliance and culture makes this practical: a signed approval is weak evidence when the operating team cannot explain how the control will function under pressure.

What to record after the audit

Keep the rescue trigger, first-ten-minute sequence, named roles, equipment location, communication test, host interface, open gaps, decision owner, and revalidation trigger in the work package. Update the record when the contractor changes crew, method, location, shift, or equipment.

  • The contractor can state the rescue trigger and stop-work authority.
  • Every critical action has a present and competent role holder.
  • Rescue equipment is inspected, compatible, accessible, and verified at the point of use.
  • The host and contractor have tested the real communication and escalation path.
  • Blocking gaps are closed before authorization, not after the task has started.

Conclusion: approve demonstrated capability

A rescue plan earns trust when the people who must use it can demonstrate its first decisions, resources, and interfaces before exposure begins. The audit is not designed to make contractors produce more paperwork. It reveals whether the work package contains a response that can function when the original controls no longer protect the worker.

For a related control-ownership process, read how to run a contractor induction that tests control ownership. Andreza Araujo’s Make The Difference: Be a Leader in Health & Safety and Safety Culture: From Theory to Practice develop the leadership discipline behind this approach. Explore her books and Safety School resources for further guidance.

Topics contractor safety rescue readiness high-risk work permit to work emergency response

Frequently asked questions

What is contractor rescue readiness?
Contractor rescue readiness is the demonstrated ability of the contractor and host team to recognize a rescue trigger, communicate it, reach the affected worker, provide the required equipment and skills, and transfer control to the right responder without improvising basic responsibilities.
Is a rescue plan enough for permit approval?
No. A plan describes an intended response, while readiness requires evidence that the people, equipment, access route, communication method, and decision authority are available and understood before the work begins.
Who owns contractor rescue arrangements?
Ownership is shared but not vague. The contractor should own the capability it brings to the task, while the host organization should verify interfaces, site constraints, access, escalation, and the conditions under which work must stop.
How often should rescue readiness be audited?
Audit rescue readiness before high-risk work starts and repeat the check when the task, crew, equipment, location, shift, weather, access route, or emergency interface changes. A calendar alone is not a substitute for change-based verification.

About the author

Andreza Araújo

Safety Culture Expert | Senior EHS Executive

Andreza Araújo is a safety culture expert and senior EHS executive with more than 25 years of experience in environment, health and safety. She is a Civil Engineer and Occupational Safety Engineer from Unicamp, holds a Master's degree in Environmental Diplomacy from the University of Geneva, and completed sustainability studies at IMD Switzerland. Andreza has served in Global Head of EHS roles in Fortune 500 environments, leading cultural transformation programs across multinational operations. She has represented Brazil as a speaker at the United Nations in Paris and has spoken at the International Labour Organization in Turin. She is the author of more than 16 books on safety culture in Portuguese, Spanish, English and German. Her work has earned more than 10 EHS awards, including two recognitions from Indra Nooyi, former PepsiCo CEO.

  • Civil & Safety Engineer (Unicamp)
  • M.A. Environmental Diplomacy (University of Geneva)
  • Sustainability Cert (IMD Switzerland)
  • People Management & Coaching (Ohio University)
  • UN Paris speaker representative for Brazil
  • ILO Turin speaker
  • LinkedIn Top Voice
  • Indra Nooyi PepsiCo CEO recognition (2x)

Documentaries

Watch Andreza's documentaries

Three productions on safety culture, organizational failure and the human lessons behind major disasters.

Podcasts

Listen to Andreza's podcasts

She hosts three shows on safety leadership, EHS and organizational culture, in English and Portuguese.

Summarize with AI