Construction & field ops checklist
Incident Investigation Checklist
Investigate incidents systematically through scene control, event reconstruction, evidence preservation, worker interviews, technical and organizational factors, failed controls, root causes, corrective actions, prevention learning, and final report approval.
Are immediate hazards controlled and is enough scene, evidence, and witness information preserved to support an objective investigation?
Lead Investigator · Due immediately · Scene release blocked
Select an answer to preview the workflow.
About this checklist
What an incident investigation should help you determine
Establish what happened, how the work actually unfolded, why preventive controls failed, which system conditions contributed, and what changes are needed to prevent recurrence without reducing the investigation to individual blame.
When
As soon as the scene is safe and evidence can be preserved
Use it for injuries, illnesses, near misses, property damage, equipment events, environmental incidents, high-potential events, and other cases requiring structured causal analysis.
Who
Investigators, workers, managers, HSE, contractors, and technical specialists
Use a team appropriate to the event so work knowledge, management context, technical evidence, contractor interfaces, and safety-program factors are all represented.
Outcome
Evidence-backed root causes and prevention actions
Create a traceable investigation record connecting scene evidence, interviews, task reconstruction, failed controls, root causes, corrective actions, broader learning, and final approval.
Complete incident investigation checklist
Investigate from scene preservation through system-level prevention
Ten sections, sixty checks. Expand any section, then adapt investigation authority, reporting interfaces, interview protocols, evidence handling, technical analysis, root-cause methods, corrective-action criteria, confidentiality, and approvals to your jurisdiction and organization.
Section 1Investigation setup, authority, scope, team, and case control
- Confirm the project, incident location, incident date and time, investigation start date, case number, incident type, affected employer, lead investigator, team members, HSE reviewer, and approver.
- Define the investigation scope, including affected people, contractors, task, equipment, materials, work area, shift, and systems to be examined.
- Confirm the investigation team has appropriate management, worker, technical, contractor, HSE, or specialist representation for the nature and severity of the event.
- Verify roles are clear for scene control, evidence collection, interviews, technical analysis, regulatory coordination, corrective-action development, and final approval.
- Review the initial incident report and previous similar incidents, near misses, repeat hazards, unresolved findings, or relevant risk history without treating early assumptions as final conclusions.
- Record open questions, immediate restrictions, evidence priorities, specialist support needs, investigation milestones, and the expected route for review and sign-off.
Section 3Event chronology, task reconstruction, people, and work conditions
- Reconstruct the sequence from pre-task planning through the incident and immediate response using times, actions, locations, communications, and changes in work conditions.
- Identify who was present, each person's role, employer, task, location, line of supervision, and interaction with equipment, materials, controls, or other workers.
- Compare the work that was actually performed with the approved risk assessment, method statement, permit, procedure, drawing, work instruction, or pre-task plan.
- Record changes in scope, sequence, staffing, equipment, materials, weather, access, schedule, production pressure, simultaneous operations, or site conditions before the incident.
- Identify decision points where the task could have been stopped, changed, escalated, or controlled differently and determine what information was available at the time.
- Build a fact-based timeline that distinguishes verified evidence from estimates, assumptions, conflicting accounts, and unanswered questions.
Section 5Witness interviews, statements, worker participation, and information quality
- Identify witnesses, affected workers, supervisors, operators, contractors, first responders, planners, maintainers, permit issuers, and others who may have relevant information.
- Conduct interviews as soon as reasonably practicable while allowing for medical, emotional, legal, language, and representation needs that may affect timing.
- Use open, non-leading questions to establish what the person saw, heard, did, understood, expected, and believed the hazards and controls to be at the time.
- Distinguish direct observation from assumption, hearsay, later discussion, interpretation, and information learned after the event.
- Resolve important inconsistencies by comparing statements with physical evidence, records, timelines, and additional interviews rather than selecting the first plausible account.
- Include workers and managers in the investigation process so practical task knowledge and program-level perspectives are both considered.
Section 7Procedures, permits, training, supervision, communication, and organizational factors
- Verify applicable procedures, permits, risk assessments, method statements, work instructions, and emergency plans were current, usable, available, and appropriate for the actual task.
- Determine whether workers and supervisors received the training, competency assessment, authorization, information, and practical instruction required for the work.
- Evaluate whether supervision, staffing, shift coverage, workload, fatigue, contractor coordination, pre-task planning, or management presence affected the incident.
- Review communication between employers, trades, shifts, planners, operators, supervisors, permit issuers, and workers for gaps, conflicting instructions, or missing hazard information.
- Consider scheduling, production pressure, incentive structures, procurement decisions, design constraints, maintenance backlog, staffing shortages, or other organizational factors that may have weakened controls.
- Check whether earlier inspections, incidents, near misses, worker concerns, maintenance records, audit findings, or safety observations had already identified the same hazard or control weakness.
Section 9Corrective actions, hierarchy of controls, broader risk, and prevention plan
- Develop corrective actions that address the identified root causes, contributing factors, failed controls, and immediate hazards rather than only the visible outcome.
- Prioritize elimination, substitution, engineering controls, isolation, design change, physical safeguards, or other higher-level controls before relying mainly on warnings, retraining, or PPE.
- Assign each action a named owner, priority, due date, resource need, affected project or system, required evidence, and effectiveness-verification method.
- Define interim controls and work restrictions where permanent solutions cannot be completed immediately so similar exposure remains controlled.
- Review other projects, contractors, equipment, tasks, locations, or work groups for the same causal conditions and extend preventive actions where the risk is not unique to the original incident.
- Escalate actions that require design, procurement, engineering, policy, contractor, executive, or cross-project decisions beyond the authority of the local investigation team.
Section 2Immediate response, hazard control, scene preservation, and release
- Verify first aid, medical care, rescue, evacuation, fire response, spill control, or other emergency actions were completed before investigation activities began.
- Confirm continuing hazards were controlled, including hazardous energy, unstable structures, traffic, equipment movement, excavation, falls, fire, chemicals, electrical sources, or other exposure.
- Preserve the incident scene as far as reasonably practicable without delaying rescue or actions needed to prevent further harm.
- Secure relevant equipment, tools, materials, temporary works, controls, energy sources, and work areas against movement, alteration, use, repair, or disposal until released by the authorized person.
- Document any necessary scene changes made for rescue, stabilization, weather protection, access, production needs, or other justified reasons.
- Do not release the scene, equipment, or affected work for normal use until required evidence is captured and the authorized investigation or project lead approves release conditions.
Section 4Physical evidence, photographs, documents, records, and data preservation
- Capture wide, medium, and close-up photographs or video showing the incident scene, equipment positions, damage, controls, access, environment, and relevant physical evidence.
- Record measurements, dimensions, distances, levels, clearances, guard positions, equipment settings, control positions, damage patterns, environmental readings, or other physical facts relevant to the event.
- Collect the actual versions of permits, risk assessments, job plans, methods, drawings, inspection records, equipment logs, maintenance records, training records, and shift records used at the time.
- Preserve relevant electronic data such as equipment telematics, access logs, CCTV, alarms, communications, mobile records, inspection submissions, sensor data, or system audit trails where available and authorized.
- Identify, label, store, and control physical evidence so its origin, condition, custody, and any testing or examination remain traceable.
- Apply applicable confidentiality, privacy, legal-hold, medical-information, and evidence-retention rules without compromising the operational investigation record.
Section 6Equipment, materials, environment, engineering, and technical factors
- Inspect involved equipment, tools, guards, controls, interlocks, alarms, attachments, safety devices, structures, and materials for defects, damage, modification, wear, or abnormal condition.
- Review maintenance, inspection, calibration, certification, repair, pre-use check, defect, and operator records for the equipment or system involved.
- Evaluate whether equipment selection, capacity, guarding, ergonomics, access, layout, temporary works, design, or physical separation contributed to the event.
- Assess environmental and worksite conditions such as lighting, noise, heat, cold, wind, rain, visibility, ground condition, congestion, traffic, housekeeping, dust, atmosphere, or restricted access.
- Determine whether material properties, chemicals, stored energy, pressure, load, stability, compatibility, contamination, or unexpected physical behavior influenced the incident.
- Obtain engineering, manufacturer, laboratory, occupational-health, medical, specialist, or third-party technical input where the evidence requires expertise beyond the investigation team's competence.
Section 8Causal analysis, failed controls, contributing factors, and root causes
- Identify the immediate events and conditions that directly preceded the incident without treating them as the complete explanation.
- Identify contributing factors involving equipment, work environment, procedures, planning, communication, training, supervision, coordination, design, maintenance, or organizational systems.
- Map the preventive controls that should have stopped the event and determine whether each control was missing, inadequate, unavailable, bypassed, misunderstood, degraded, or not verified.
- Ask why each significant condition existed and why it had not been identified or corrected earlier, continuing the analysis until underlying system weaknesses are exposed.
- Avoid conclusions that stop at carelessness, worker error, or failure to follow a procedure without explaining why the action was possible and why the system did not prevent it.
- Confirm root causes and contributing factors are supported by evidence, explain the event coherently, and are specific enough to guide preventive corrective actions.
Section 10Investigation report, communication, approval, handoff, and closeout
- Prepare a clear investigation report that states the event facts, sequence, evidence, causal factors, root causes, failed controls, corrective actions, uncertainties, and references used.
- Confirm photographs, evidence logs, interview records, technical reviews, diagrams, timelines, and key source documents are linked or traceable to the investigation case.
- Communicate relevant findings and prevention lessons to affected workers, supervisors, contractors, managers, and other groups exposed to similar hazards while protecting confidential information.
- Verify the investigation has not been closed merely because a report is complete; corrective actions and effectiveness checks should transfer into an accountable follow-up process.
- Record required regulatory, client, insurer, legal, or internal review comments and incorporate approved changes without altering source evidence or hiding unresolved disagreement.
- Record final investigation approval, open preventive actions, continuing restrictions, follow-up owner, effectiveness review date, lead investigator, HSE reviewer, contractor or project manager, approver, date, time, and sign-off.
Take it with you
Use the complete checklist during your next incident investigation
Download the printable version, or continue below to see how the same investigation can run with scene evidence, interviews, timelines, root causes, failed controls, corrective actions, review comments, and final approval in Taqtics.
How to use it
Turn every incident investigation into a structured evidence-to-prevention workflow
Control the scene, reconstruct the actual work, collect evidence and worker perspectives, identify failed controls and root causes, then convert findings into preventive actions.
Control and preserve
Stabilize hazards, secure the scene, preserve equipment and records, and define investigation roles and evidence priorities.
Reconstruct and collect
Build the event timeline, interview workers, gather documents and digital data, and compare actual work with planned controls.
Analyze causes and failed controls
Examine technical, procedural, environmental, supervisory, communication, and organizational factors without stopping at blame.
Prevent and hand off
Develop higher-level corrective actions, apply lessons to similar exposures, communicate findings, and transfer open actions into follow-up.
Live interactive demo
See how an incident investigation works when it is run in Taqtics
Complete representative investigation checks, flag missing critical evidence, attach live proof, and create an investigation hold before the scene or case is released.
Assign by project, incident type, contractor, task, equipment, location, severity, investigator, or investigation stage.
Capture scene photos, documents, witness records, event sequence, technical factors, failed controls, root causes, and action plans.
Missing scene evidence, unresolved hazards, incomplete interviews, unsupported causes, or unverified controls can hold investigation release.
Illustrative website demo. Responses are not stored or submitted.
Why digitize it
A clearer way to investigate incidents from evidence through prevention
Taqtics connects investigation cases, scene evidence, interviews, timelines, failed controls, root causes, corrective actions, review comments, approvals, and recurring incident trends across every project.
Preserve investigation evidence in one case
Capture scene photos, documents, interviews, measurements, timelines, technical findings, root causes, actions, and approvals together.
Standardize root-cause investigation
Use the same evidence stages, causal questions, failed-control analysis, review gates, ownership, and sign-off across projects.
Prevent unsupported conclusions
Keep unresolved questions, missing evidence, conflicting accounts, technical reviews, and unsupported root causes visible before approval.
Compare recurring causal patterns
Review failed controls, equipment factors, procedure gaps, supervision, contractor interfaces, organizational causes, and prevention trends.
Frequently asked questions
Incident investigation checklist FAQs
What should an incident investigation checklist include?+
It should cover investigation scope and team, immediate hazard control, scene preservation, event reconstruction, physical and digital evidence, witness interviews, equipment and environmental factors, procedures and training, supervision and organizational conditions, failed controls, root causes, corrective actions, broader prevention, investigation reporting, communication, approval, and handoff to follow-up.
What does OSHA recommend as the purpose of incident investigation?+
OSHA strongly encourages employers to investigate injuries, illnesses, and close calls to identify hazards and shortcomings in safety and health programs. The goal is to identify and correct underlying or root causes so similar incidents can be prevented, rather than focusing on fault or blame.
Who should participate in an incident investigation?+
OSHA recommends an investigation approach that includes both managers and employees because they bring different knowledge and perspectives. Depending on the event, contractor representatives, technical specialists, maintenance, engineering, occupational-health, or other subject-matter experts may also be needed.
Why should an investigation look beyond worker error?+
Stopping at carelessness or failure to follow a procedure can hide the system conditions that made the event possible. OSHA recommends asking why the action or condition existed and why it had not been addressed earlier, including equipment, training, procedures, supervision, production pressure, and other program factors.
What evidence should be preserved during an incident investigation?+
Useful evidence can include scene photographs, measurements, damaged equipment, control positions, documents, permits, risk assessments, maintenance records, training records, witness information, CCTV, electronic logs, telematics, alarm data, communications, environmental readings, and any technical analysis relevant to the event.
Does this checklist replace legal investigation or reporting requirements?+
No. Use it as an operational investigation template and adapt incident reporting, regulatory notification, evidence preservation, interviews, worker participation, privacy, legal review, recordkeeping, corrective actions, and approval requirements to the applicable jurisdiction, employer, client, contract, and incident type.
Ready when you are
Run incident investigations with traceable evidence, root causes, and prevention actions
Track investigations by project, contractor, incident type, task, equipment, location, and investigator, capture live evidence and worker input, analyze failed controls, assign prevention actions, and hand every open commitment into accountable follow-up.
Printable PDF · Free Taqtics trial · No credit card required