Contractor Incident Handover: 9 Steps in 24 Hours
A practical 24-hour contractor incident handover guide for EHS managers who need evidence, role clarity, and corrective control without blame.

Key takeaways
- 01Define one host lead and one contractor lead within the first 2 hours so decision rights do not disappear between legal, EHS, and operations teams.
- 02Preserve 3 evidence families, physical evidence, testimony, and system records, before the first review so the RCA does not overdepend on memory.
- 03Separate regulatory notification from learning coordination because 8-hour and 24-hour reporting windows do not replace control-restoration work.
- 04Convert early findings into 4 restart tests before contractor work resumes: stable hazard, restored control, named owner, and crew understanding.
- 05Use Andreza Araújo consulting or Safety School resources to turn contractor incident learning into a practical 24-hour handover routine.
Contractor incidents become harder to investigate after the first 24 hours because evidence moves, witnesses disperse, and site decisions begin to overwrite the original conditions. This guide shows how an EHS manager or site supervisor can run a contractor incident handover that protects facts, restores controls, and avoids the usual slide into blame.
Contractor incident handover is the structured transfer of facts, evidence, responsibilities, and immediate controls after an event involving a contractor crew. It should happen within 24 hours, before memories fade and before production pressure turns an investigation into a paperwork exchange.
Why contractor incident handover fails before RCA starts
Contractor incident handover fails when the host company treats the event as the contractor's administrative problem instead of a shared control failure. ISO 45001:2018 requires organizations to control outsourced processes that affect occupational health and safety, which means the host cannot delegate the learning simply because the injured person or exposed crew belongs to another employer.
As Andreza Araújo argues in Sorte ou Capacidade, translated as Luck or Capability, an accident is systemic rather than random. The contractor badge changes the employment relationship, but it does not change the failed interface among permits, supervision, work planning, and field verification.
ISO specifies the occupational health and safety management system requirements in ISO 45001, including the need to manage outsourced processes. For a contractor event, that requirement becomes practical only when both organizations leave the first meeting with the same timeline, evidence list, and control-restoration plan.
Step 1: Freeze the scene without freezing the operation
The first step is to preserve the incident scene for a defined period, usually the first 30 to 90 minutes, while a competent person decides what must remain untouched and what must be made safe. A blanket stop can create secondary risk, but immediate restart can destroy the very evidence needed to prevent repetition.
The trap is believing that production recovery and evidence preservation are opposites. In practice, the supervisor should create two zones: a protected evidence zone and a recovery zone, with a photo log showing what moved, who authorized it, and why.
When the event is a near miss rather than an injury, the same discipline applies. A fast field reset after a near miss can restart work only after critical controls are restored, not after the crew verbally agrees to be more careful.
Step 2: Who owns the first 24 hours?
The host site must own the first 24 hours because it owns the workplace interface, even when the contractor owns the employment contract. A clear handover names one host lead, one contractor lead, one evidence custodian, and one decision owner for restart authorization.
Across 25+ years leading EHS at multinationals, Andreza Araújo identifies that incidents often deteriorate when three leaders believe someone else is leading. In contractor events, that ambiguity is amplified because procurement, operations, EHS, and the contractor's supervisor may each assume the next person controls the response.
The practical rule is simple enough to audit. Before the first shift ends, write a one-page decision log with four names, four mobile numbers, the restart condition, and the time of the next review. If the log has a blank field after 2 hours, the handover is already weak.
Step 3: Build a single evidence register
A single evidence register prevents the host and contractor from building competing versions of the same event. The register should list photos, video, permits, training records, equipment logs, witness names, weather or process conditions, and any electronic data captured in the first 24 hours.
The market often overvalues witness statements because they feel immediate, but memory is not a control. A stronger handover triangulates statements with records and field traces, using the same discipline described in photos, witness statements, and equipment logs for RCA.
3 evidence families should appear in the register before the first review: physical evidence, human testimony, and system records. If one family is missing, the investigation will probably overread the other two.
Step 4: Separate notification duties from learning duties
Notification duties and learning duties must be separated because legal reporting asks whether a threshold was met, while investigation asks why the control system allowed the event. HSE explains RIDDOR reporting duties for specified injuries, dangerous occurrences, and work-related fatalities, but the reporting act itself does not identify the failed controls.
The same distinction appears in the United States, where OSHA requires employers to report a fatality within 8 hours and an inpatient hospitalization, amputation, or eye loss within 24 hours. Those windows matter, although they should not become the whole response.
In a contractor handover, assign one person to regulatory notification and another to learning coordination. When the same person tries to protect compliance, manage family communication, interview witnesses, and restart work, quality drops exactly when the organization needs discipline.
Step 5: Reconstruct the work as planned and as done
The fifth step is to compare the job as planned with the job as done, using the permit, JSA, pre-job brief, supervisor instructions, and field conditions as separate sources. The goal is not to catch the crew in contradiction, but to identify where the plan stopped matching the work.
Andreza Araújo's position in A Ilusão da Conformidade, translated as The Illusion of Compliance, is useful here because a signed document may prove formal compliance while still hiding a practical gap. Contractor work often carries more paper than clarity, especially when the crew changes, the scope shifts, or the host area owner is absent.
The handover team should mark each variance as one of 3 types: planned and followed, planned and not followed, or not planned but necessary in the field. The third type is often the most valuable because it shows where the procedure did not fit reality.
Step 6: What changed in the controls before the event?
The handover must identify which controls changed before the event, because serious incidents often follow small changes in supervision, equipment condition, access, weather, staffing, or work sequence. A contractor crew may see each change locally, while the host site is the only party positioned to see the combined pattern.
In more than 250 cultural transformation projects, Andreza Araújo observes that organizations tend to debate individual attention while missing control drift. That is why the first 24 hours should include a quick comparison between the approved control set and the control set that actually existed at the moment of exposure.
Use a control-change list with 5 columns: intended control, field condition, variation, owner, and immediate restoration. If the work involved high energy, confined space, lifting, traffic, or line breaking, connect this review to a reverse Bow-Tie RCA after the first handover is stable.
Step 7: Interview without outsourcing blame
Witness interviews should capture what people saw, heard, decided, and understood in the minutes before the event, not force them to defend themselves against a conclusion. James Reason's Swiss cheese model remains useful because it keeps attention on latent failures as well as active errors.
The wrong opening question is usually who failed. A better sequence asks what was expected, what changed, what information was available, which control was missing or weak, and what made the local decision seem reasonable at the time.
For contractor personnel, interview conditions matter. Put the host and contractor leads in the room only when their presence does not silence the worker, document the language used, and avoid group interviews for the first account because they can flatten details into a shared story.
Step 8: Convert findings into restart criteria
Findings must become restart criteria before they become a long corrective-action list. A contractor incident handover is incomplete if it describes causes but allows the same work to restart with the same weak permit, the same supervision gap, or the same equipment uncertainty.
This is where many organizations confuse RCA completion with risk reduction. A formal RCA timeline helps structure the facts, but the site still needs minimum restart conditions that are visible to the supervisor at the workface.
4 restart tests should be passed before work resumes: the hazard is stable, the control is restored, the owner is named, and the affected crew can explain the changed condition. If the crew cannot explain what changed, the restart is administrative rather than operational.
Every shift that restarts contractor work without explicit criteria teaches the workforce that handover is a meeting, while the real control decision remains informal.
Step 9: Close the 24-hour handover and schedule the RCA
The final step is a 24-hour handover closeout that confirms the evidence register, decision log, restart criteria, regulatory status, and RCA plan. The closeout should not pretend the investigation is finished, since its role is to stabilize facts and assign the next level of analysis.
The best closeout produces a short document that a new investigator can read without calling 6 people to reconstruct basic facts. If the organization lacks that competence internally, the next step may be to assign a trained lead using a pathway similar to an incident investigator first RCA plan.
Close the handover with three commitments: what remains stopped, what may restart under controls, and when the full RCA review will occur. A 72-hour RCA kickoff is often realistic for complex contractor events because it gives time to secure records without letting memory and accountability fade.
Contractor handover compared with ordinary internal handover
| Dimension | Internal incident handover | Contractor incident handover |
|---|---|---|
| Decision rights | Usually inside one reporting line | Split across host, contractor, procurement, and operations |
| Evidence access | Records often sit in one system | Permits, training files, and equipment logs may sit in 2 or more systems |
| Reporting pressure | Legal and corporate thresholds apply | Legal, corporate, contractual, and client thresholds may all apply within 24 hours |
| Learning risk | Blame can still distort the RCA | Blame is easier because the exposed worker belongs to another employer |
Contractor incident handover protects learning
Contractor incident handover works when the host organization treats the first 24 hours as a control-preservation window, not as a search for a convenient owner. The method protects evidence, clarifies authority, separates notification from learning, and converts early findings into restart criteria.
If your operation relies on contractors for high-risk work, Andreza Araújo can support the diagnosis, leadership alignment, and control-restoration plan. Talk to us at Andreza Araújo.
Frequently asked questions
How do you run a contractor incident handover in 24 hours?
Who owns a contractor incident investigation?
What evidence should be collected after a contractor incident?
What is the difference between incident handover and RCA?
How is contractor incident handover linked to safety culture?
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.