Accident Investigation for General Contracting

Look at the initial incident report, medical status, and any early notes from the scene. Pay attention to severity, potential regulatory impact, and whether the event involved high-risk activities such as work at height, lifting, or confined spaces.

Check company guidelines for when a basic, standard, or major investigation is required. Criteria may include lost time injuries, hospitalizations, large property damage, or events with high potential severity.

Based on severity and criteria, determine which level applies to this accident. Document your decision briefly, including why you chose that level.

List the roles that should participate: typically the project manager, superintendent, safety representative, and sometimes a representative from the trade involved. For major events, include higher management or subject matter experts.

Assign named people to each role and confirm their availability. Make sure at least one person on the team has investigation and root cause analysis experience.

Inform the project team and safety management who will lead the investigation, who is on the team, and what level of investigation will be conducted.

Write one to three clear statements describing what the investigation must determine, such as “understand how the worker came to be in the line of fire” or “identify why fall protection was not used.” Avoid vague objectives like “find out what happened.”

For each objective, list questions that must be answered (for example, “What was the planned method of work?” “What training had been provided?” “What barriers failed?”). This list will guide interviews and document review.

Identify types of evidence needed: photos, measurements, equipment condition, work procedures, risk assessments, training records, and permits. Note which team member is responsible for each evidence type.

Agree on target dates for scene review, interviews, draft findings, and final report. Consider any regulatory or client deadlines as well as the availability of key people.

Put interviews, site visits, and team meetings on calendars. Ensure injured workers are only interviewed when medically and emotionally ready to participate.

Write a short investigation plan summarizing objectives, questions, evidence, and timelines. Share it with the investigation team so everyone understands the approach before detailed work begins.

Verify that immediate hazards (fire, unstable structures, live energy) have been controlled and that emergency response activities are complete. Do not enter areas that remain unsafe; request additional controls if needed.

Starting from a safe distance, walk toward the incident area, observing floor conditions, lighting, access routes, signage, and positions of tools and materials. Look at the scene from multiple angles, not just where the incident occurred.

Capture overall context photos showing the broader area, then closer shots of relevant equipment, tools, and surfaces. Include close-ups of any damage, markings, or unusual conditions. Keep a logical sequence so photos tell a clear story.

Draw simple sketches showing locations of key objects, people positions, and distances. Take basic measurements (for example, height of platforms, distances between items) where useful to understand clearances and reach.

If equipment, tools, or materials may have contributed to the accident, tag and secure them in a safe location for later inspection. Record serial numbers and conditions before moving anything.

Immediately after the examination, write down your observations in a structured way, grouping them by area or hazard type. Avoid assumptions or explanations at this stage; focus on what you saw and measured.

Based on the investigation plan, write down open-ended questions to ask each person, such as “Tell me what you were doing right before the accident” and “What did you see or hear?” Tailor some questions to each person’s role.

Schedule interviews in a location where the person can speak freely without distractions. For injured workers, coordinate with medical providers and supervisors to ensure they are well enough to participate.

At the start, explain that the investigation is focused on understanding what happened and improving safety, not blaming individuals. Assure them that you will treat their information respectfully and will focus on facts.

Ask them to describe what happened from their perspective. Listen without interrupting, only asking follow-up questions to clarify details or fill gaps. Avoid leading questions that suggest answers.

In addition to the event itself, ask about lighting, noise, time pressure, clarity of instructions, equipment condition, and whether they had any previous concerns about the task or area.

Write down key points during the interview. At the end, summarize back what you heard and ask if you missed anything or misunderstood any part. Thank them for their time and input.

List all relevant documents: job hazard analyses, method statements, permits, pre-task plans, inspection reports, training records, equipment manuals, and prior incident reports for similar work.

Request documents from the project manager, safety lead, foremen, and company systems. Confirm you are looking at the versions that were in effect at the time of the accident, not older or draft versions.

Read procedures and plans and compare them to what interviews and scene observations indicate actually occurred. Note any steps in the plan that were skipped, changed, or not understood.

Verify whether the involved workers and supervisors had completed required training or certifications for the tasks and equipment used. Note any missing or outdated training.

Look at daily and weekly inspection logs and near miss reports for issues related to this task or area. Identify whether earlier warnings were present but not fully addressed.

Write a brief summary highlighting where documents and reality matched and where they diverged. This summary will feed into the event timeline and root cause analysis.

From interviews, logs, schedules, and observations, write down each known event related to the accident: start of shift, toolbox talks, equipment setup, key actions, and the accident itself. Include approximate times even if exact times are not known.

Arrange the events in time order, from the earliest relevant preparation steps through the accident and immediate response. Use a simple line or table with times on one side and events on the other.

Look for missing time periods or conflicting accounts (for example, different people reporting different times or sequences). Mark these areas for clarification.

Re-interview witnesses or check additional records (like access logs or equipment telematics) to fill missing information or resolve conflicts wherever possible.

On the timeline, mark where important decisions were made, where conditions changed (weather, shift changes, new tasks), or where barriers failed. These are often critical points for understanding causes.

Present the timeline in a simple visual format (chart or diagram) that the investigation team can review together. Use this as the foundation for root cause analysis discussions.

Choose a simple method such as the “5 Whys” technique or a basic cause-and-effect diagram. Make sure all team members understand how the chosen method works before starting.

Begin the session by reviewing the agreed timeline, scene findings, interviews, and document review. Confirm that everyone is working from the same factual baseline.

List the direct actions or conditions that immediately preceded the accident (for example, “worker entered area under suspended load” or “guardrail section missing at edge”). These are starting points, not root causes.

For each immediate cause, ask “Why did this happen?” and record the answer. Continue asking “Why?” for each answer until you reach system-level factors such as planning, supervision, training, procedures, or organizational decisions.

Once you have a list of deeper causes, group them into themes such as human factors, equipment, environment, procedures, or management systems. This helps prioritize which systems need change.

Discuss and refine the list until the team agrees which causes are fundamental and actionable. Document these root causes clearly and in neutral language that focuses on systems, not individuals.

For each root cause, brainstorm practical changes that could address it. Ideas may include revising procedures, adding controls, changing layout, enhancing supervision, or updating training programs.

Discuss each proposed action in terms of its likely impact on risk reduction and the effort or cost required. Focus first on actions that significantly reduce risk and are reasonably achievable.

Choose the actions that will be implemented and rank them in order of priority. Distinguish between actions that must be done immediately, soon, and in the longer term.

For each selected action, name a single responsible person and set a realistic completion deadline. Make sure owners understand what is expected and have the authority and resources to complete the action.

Decide how you will confirm that each action has actually reduced risk (for example, follow-up inspections, audit of new procedure use, or monitoring incident trends). Note this check in the plan.

Enter all actions, owners, deadlines, and effectiveness checks into the company’s corrective action tracking system or log. Link the plan to the accident investigation record.

Use the standard investigation report template if one exists. This usually includes sections for summary, background, description of event, evidence, analysis, causes, and corrective actions.

At the beginning, write a short summary of what happened, who was affected, and the main causes and actions. Keep this section factual and free of technical jargon so non-specialists can understand it.

Provide a clear narrative of the accident, including timeline and key facts. Briefly state what methods were used (interviews, scene exam, document review, root cause analysis).

List the main findings from the investigation and the root causes you identified. Use numbered points and neutral language, focusing on conditions and systems rather than individuals.

Describe the actions that have been or will be taken, including owners and deadlines. Note any actions already completed and early signs of impact if available.

Have investigation team members and, if required, safety management review the draft report. Incorporate feedback, check for clarity and accuracy, then finalize and sign or electronically approve the report as per company policy.

Decide who needs to be informed: project team, company leadership, client, and possibly all field staff. For each group, determine how much detail is appropriate and what key messages to emphasize.

Present the main causes and corrective actions to the project’s supervisors and safety committee. Focus on what will change in planning, supervision, and field practices on this site.

Use toolbox talks, safety bulletins, or short presentations to share anonymized lessons with other projects or the wider company. Emphasize what workers should do differently in similar situations.

Regularly check the corrective action tracking system to ensure owners are completing actions by the agreed deadlines. Follow up with reminders or escalation where actions are falling behind.

After actions are reported complete, inspect the relevant work areas, observe tasks, or review procedures to confirm changes are actually in place and working. Adjust or add actions if problems remain.

Once all planned actions are completed and checked, mark them as closed and update the investigation record to “closed.” Store the report, evidence, and related documents in the designated archive for future reference and audits.