Five Whys helps investigators test what allowed an incident or control failure, but a chain is not proof. Verify each answer, branch when causes interact, choose stronger controls and check them in real work. Keep statutory reporting separate and use the correct Great Britain or Northern Ireland route.
Understanding Five Whys for Incident Investigation
Five Whys helps investigators test what allowed an incident or control failure, but a chain is not proof. Verify each answer, branch when causes interact, choose stronger controls and check them in real work. Keep statutory reporting separate and use the correct Great Britain or Northern Ireland route.
Why this matters at work
Branch when more than one credible condition contributed, when causes interact, or when separate pathways explain occurrence and severity. A vehicle incident may involve layout, visibility, scheduling, route information and supervision. Forcing all those conditions into one line can suggest a false sequence. A timeline, fishbone or barrier review may better organise the wider system before selected branches are examined in depth. Stop a branch that is irrelevant, disproved or unsupported, recording why. Refer technical failures, complex processes and high-consequence uncertainties to suitable specialists. Do not continue asking why until speculation sounds persuasive. Shared conditions should be shown once with clear links rather than counted as multiple independent causes. Keep immediate protection in place while questions remain open. Final findings should explain what the evidence establishes and what remains unknown, with an owner for further work. A method is useful only if it helps choose effective controls; completion of a diagram is not evidence that the hazard has been resolved.
Treat culture as a prompt for observable evidence: conflicting instructions, ignored defect reports, resource decisions, repeated workarounds or incentives that affected a specified barrier. Interview people openly and preserve contrary evidence. Do not assume lack of a signature proves no briefing occurred, or that a signature proves understanding. Set a stopping point when further claims cannot be established and identify the next inquiry. Keep conduct questions separate from fair prevention-focused analysis. The resulting finding should name a change the organisation can implement and verify, not attach blame to a worker or use a vague root-cause label to avoid difficult design or management decisions.
How organisations manage this in practice
Map every final finding to a control purpose and an accountable owner with authority and resources. Prefer suitable changes to design, layout, containment, maintenance or planning before relying on reminders. Training and supervision can support those changes but do not replace physical protection. State interim measures, target dates, dependencies and evidence needed for technical acceptance or completion.
Worker health information requires actual lawful basis and special-category condition, necessary purpose, limited access, security and appropriate retention. Signature or interview participation is not automatic freely given employment consent. ICO guidance is under review after DUAA; clinical referral consent and work controls remain separate.
Map each supported finding to a specific control change, owner and acceptance criterion. Completion is separate from effectiveness. Verify safely under relevant conditions and check extent elsewhere; reopen, correct and safely retest failed protection rather than close from attendance or email delivery.
Who should use this Five Whys page?
This page is for people who need to investigate incidents, near misses or weak signals without stopping at the first visible cause.
Supervisors and line managers
People who often complete first-line investigations and need a practical method that avoids blame-based conclusions.
Safety advisers and investigators
People who need to facilitate evidence-led analysis and connect findings to corrective actions.
Worker representatives
People who help explain work-as-done, normal adaptations, pressure points and practical barriers.
Operations, maintenance and engineering teams
People who understand plant condition, job design, maintenance history, technical controls and change history.
Senior managers
People who must challenge weak actions, allocate resources and check whether learning has been embedded.
Learners and auditors
People studying incident investigation, root cause analysis, HSG245, human factors, monitoring and management system improvement.
Updated 2026-10-02.
Reader navigation, terms and proposed documents only; no linked-page evidence, instructional asset or reuse approval is implied.
How can this guidance help in practice?
Workers and people carrying out the task
Use the Five Whys for Incident Investigation guidance to recognise relevant hazards, understand the precautions and identify when to stop, report a problem or ask for competent support.
Supervisors and managers
Use the task examples and control checks to plan work, brief the team, check implementation and assign improvements with owners and follow-up.
Safety, health, risk and assurance professionals
Use the explanations, sources and operational examples to develop assessments, audits and control verification. Check the actual scope and jurisdiction before applying a duty.
Learners, trainers and organisational decision makers
Use the definitions and examples to connect theory with workplace decisions, build briefings and ask informed questions. This page does not certify competence or authorise work.
Let contradictory evidence change the branch instead of preserving a neat story
The conveyor-jam teaching chain is a set of hypotheses. Suppose the first explanation is “the worker had not been trained”, but records and demonstration establish relevant training. Reject that unsupported answer; investigate the recurring jam, access design, isolation method, production demands and previous defect response rather than using the fifth box to reach a predetermined blame conclusion.
Best-practice guide · six simple steps
Best-practice guide: Five Whys for Incident Investigation
Start with the key actions, then explore value, a workplace example, harm, stronger controls and further help. Choose a step or use Previous and Next; the guide does not advance automatically.
Let contradictory evidence change the branch instead of preserving a neat story
Avoid / redesign
Remove pedestrian movement from the vehicle zone through a redesigned delivery route.
Control the task
Install robust vehicle-pedestrian separation and controlled crossings.
Verify before release
People still cross the reversing path: reject layout.
The conveyor-jam teaching chain is a set of hypotheses. Suppose the first explanation is “the worker had not been trained”, but records and demonstration establish relevant training. Five Whys helps investigators test what allowed an incident or control failure, but a chain is not proof.
Apply it: Which part of this plan would you check at the workface before authorising the task?
Turn five whys for incident investigation knowledge into a decision
Change at source
Remove pedestrian movement from the vehicle zone through a redesigned delivery route.
Make it observable
People still cross the reversing path: reject layout.
Keep useful evidence
Injury and incident record, machine state, photographs.
Five Whys helps investigators test what allowed an incident or control failure, but a chain is not proof. Verify each answer, branch when causes interact, choose stronger controls and check them in real work. Injury and incident record, machine state, photographs.
Apply it: What evidence would show that the change improves this task, rather than only completing a record?
A packing line has a recurring jam during an identified task. The area is protected through the assessed arrangements.
Act
Test maintenance, access and work-demand explanations against records and observations, including evidence against each claim.
Hold / review
Keep uncertain causal links and unsafe intervention held; do not switch to another event or stop automatically at five questions.
Setting: A packing line has a recurring jam during an identified task. The area is protected through the assessed arrangements. Act: Test maintenance, access and work-demand explanations against records and observations, including evidence against each claim. Hold / review: Keep uncertain causal links and unsafe intervention held; do not switch to another event or stop automatically at five questions.
Apply it: At which point would you hold this example, and what evidence would allow it to proceed?
The chain starts with blame: The investigation begins from a conclusion. Every answer is opinion: The chain cannot be defended. There is only one line for a complex event: Interactions are hidden.
Apply it: Who could be exposed, including other trades, cleaners, maintainers and people nearby?
Remove pedestrian movement from the vehicle zone through a redesigned delivery route.
Substitution
Use forward-only access or smaller delivery vehicles where geometry allows.
Engineering controls
Install robust vehicle-pedestrian separation and controlled crossings.
Administrative controls
Use booked deliveries, approved temporary route changes and contractor briefings.
PPE
Use visibility clothing for residual exposure, never as a substitute for separation.
Elimination: Remove pedestrian movement from the vehicle zone through a redesigned delivery route. Substitution: Use forward-only access or smaller delivery vehicles where geometry allows. Engineering: Install robust vehicle-pedestrian separation and controlled crossings. Administrative: Use booked deliveries, approved temporary route changes and contractor briefings. PPE: Use visibility clothing for residual exposure, never as a substitute for separation. Read the full control table for qualifications, ownership and verification. Use the actual task and applicable jurisdiction; existing technical approval remains unchanged.
Apply it: Which stronger option can be used here, and who will verify it before accepting the remaining risk?
Use the full five whys for incident investigation lesson
Official guidance
HSG245
Official guidance
HSE human-factors guidance
Task decision
Match the corrective action to the supported control gap, with an owner and real-task test. Avoid a single blame-based root or an arbitrary five-question stopping rule.
Use the full topic for the decision points, practical examples, detailed control tables and source scope. HSE guidance applies to Great Britain; use HSENI for the Northern Ireland route and the source’s stated jurisdiction. A simplified guide does not change the page’s technical-review or approval status.
Apply it: Which official source and full-topic section will you use to resolve the next decision?
Keep one card or the full set for social sharing, team briefings and learning. Each PDF contains a workplace image with separate learning notes. Read the full topic for sources and further detail.
Read all six steps as text
1. Let contradictory evidence change the branch instead of preserving a neat story
The conveyor-jam teaching chain is a set of hypotheses.
Avoid / redesign: Remove pedestrian movement from the vehicle zone through a redesigned delivery route.
Control the task: Install robust vehicle-pedestrian separation and controlled crossings.
Verify before release: People still cross the reversing path: reject layout.
The conveyor-jam teaching chain is a set of hypotheses. Suppose the first explanation is “the worker had not been trained”, but records and demonstration establish relevant training. Five Whys helps investigators test what allowed an incident or control failure, but a chain is not proof.
Apply it: Which part of this plan would you check at the workface before authorising the task?
2. Turn five whys for incident investigation knowledge into a decision
Use the evidence to improve the actual work arrangement.
Change at source: Remove pedestrian movement from the vehicle zone through a redesigned delivery route.
Make it observable: People still cross the reversing path: reject layout.
Keep useful evidence: Injury and incident record, machine state, photographs.
Five Whys helps investigators test what allowed an incident or control failure, but a chain is not proof. Verify each answer, branch when causes interact, choose stronger controls and check them in real work. Injury and incident record, machine state, photographs.
Apply it: What evidence would show that the change improves this task, rather than only completing a record?
Example: a practical application of the existing topic lesson.
Setting: A packing line has a recurring jam during an identified task. The area is protected through the assessed arrangements.
Act: Test maintenance, access and work-demand explanations against records and observations, including evidence against each claim.
Hold / review: Keep uncertain causal links and unsafe intervention held; do not switch to another event or stop automatically at five questions.
Setting: A packing line has a recurring jam during an identified task. The area is protected through the assessed arrangements. Act: Test maintenance, access and work-demand explanations against records and observations, including evidence against each claim. Hold / review: Keep uncertain causal links and unsafe intervention held; do not switch to another event or stop automatically at five questions.
Apply it: At which point would you hold this example, and what evidence would allow it to proceed?
Connect the task, the route to the person and the control that can fail.
The chain starts with blame: The investigation begins from a conclusion.
Every answer is opinion: The chain cannot be defended.
There is only one line for a complex event: Interactions are hidden.
The chain starts with blame: The investigation begins from a conclusion. Every answer is opinion: The chain cannot be defended. There is only one line for a complex event: Interactions are hidden.
Apply it: Who could be exposed, including other trades, cleaners, maintainers and people nearby?
Control summary. Read the complete task-specific controls and checks in the linked topic.
Elimination: Remove pedestrian movement from the vehicle zone through a redesigned delivery route.
Substitution: Use forward-only access or smaller delivery vehicles where geometry allows.
Engineering controls: Install robust vehicle-pedestrian separation and controlled crossings.
Administrative controls: Use booked deliveries, approved temporary route changes and contractor briefings.
PPE: Use visibility clothing for residual exposure, never as a substitute for separation.
Elimination: Remove pedestrian movement from the vehicle zone through a redesigned delivery route. Substitution: Use forward-only access or smaller delivery vehicles where geometry allows. Engineering: Install robust vehicle-pedestrian separation and controlled crossings. Administrative: Use booked deliveries, approved temporary route changes and contractor briefings. PPE: Use visibility clothing for residual exposure, never as a substitute for separation. Read the full control table for qualifications, ownership and verification. Use the actual task and applicable jurisdiction; existing technical approval remains unchanged.
Apply it: Which stronger option can be used here, and who will verify it before accepting the remaining risk?
6. Use the full five whys for incident investigation lesson
Follow the official sources below and retain the task-specific evidence.
Official guidance: HSG245
Official guidance: HSE human-factors guidance
Task decision: Match the corrective action to the supported control gap, with an owner and real-task test. Avoid a single blame-based root or an arbitrary five-question stopping rule.
Use the full topic for the decision points, practical examples, detailed control tables and source scope. HSE guidance applies to Great Britain; use HSENI for the Northern Ireland route and the source’s stated jurisdiction. A simplified guide does not change the page’s technical-review or approval status.
Apply it: Which official source and full-topic section will you use to resolve the next decision?
Simplified learning guide. Use the full topic and the actual work arrangements; existing technical-review and approval statuses still apply.
A useful causal map can have fewer or more than five questions and more than one branch. Record the evidence for each link, the remaining uncertainty and what would disprove it. Choose upstream actions such as eliminating the recurring intervention or making safe isolation practical, then verify effectiveness at the workface. Retraining may support a control change, but it is not an adequate automatic ending to every chain.
The conveyor records contradict the first answer
Illustrative example. A hand-injury investigation initially blames missing training during jam clearance, but the evidence shows training was delivered and understood.
Decision. The team revises the branch to examine recurring jams, access, isolation and operational pressure.
Evidence to check. Machine condition, jam history, energy-isolation evidence, observation, accounts and training demonstration.
Hold or escalation point. Do not keep a disproved answer because it completes a five-step narrative.
Follow-up. Assign an upstream design or maintenance action and field-test that the hazardous intervention is no longer required.
Test each causal step instead of forcing five answers
Use one defined event throughout the chain. A why question needs a supported explanation, and the evidence may branch or stop short of five levels.
Define the jam event
Record the actual conveyor task, event and protected state; do not switch unnoticed to a different transport example.
Explain rather than instruct
A statement such as follow the procedure is an action, not evidence explaining why the event occurred.
Check competing paths
Compare maintenance, access and work-demand evidence; record contradictions and the observation still needed.
Verify the action
Match the corrective action to the supported control gap, with an owner and real-task test. Avoid a single blame-based root or an arbitrary five-question stopping rule.
Read the complete task-specific control examples
ERICPD is a planning cross-map: Discipline verifies and sustains every control. ESEAP compares effectiveness. A label does not authorise the task; retain the owner, evidence and stop or change decision.
Five Whys for Incident Investigation · ERICPD
Eliminate
Remove pedestrian movement from the vehicle zone through a redesigned delivery route.
Reduce
Use forward-only access or smaller delivery vehicles where geometry allows.
Isolate
Install robust vehicle-pedestrian separation and controlled crossings.
Control
Use booked deliveries, approved temporary route changes and contractor briefings.
PPE
Use visibility clothing for residual exposure, never as a substitute for separation.
Discipline
Review near-miss trend and field-test the revised traffic plan after changes.
Five Whys for Incident Investigation · ESEAP
Elimination
Remove pedestrian movement from the vehicle zone through a redesigned delivery route.
Substitution
Use forward-only access or smaller delivery vehicles where geometry allows.
Engineering controls
Install robust vehicle-pedestrian separation and controlled crossings.
Administrative controls
Use booked deliveries, approved temporary route changes and contractor briefings.
PPE
Use visibility clothing for residual exposure, never as a substitute for separation.
What are the key points about Five Whys?
Five Whys is a way to ask what allowed an incident or control failure to occur. A five-question chain is a prompt, not proof: each answer needs evidence, competing explanations and a control decision.
It starts with facts
The first problem statement should describe what happened, where, when and with what consequence or potential consequence.
Five is not a rule
Stop when the team reaches a correctable system weakness, not when it has counted five questions.
Branching is normal
Incidents often involve several causal paths: equipment, work method, supervision, environment, competence, change and organisational pressure.
Human error is not the end point
If a person made an error, the next question is why the task, equipment, information or organisation made that error possible.
Evidence must test each answer
Each why should be supported by records, observations, interviews, measurements or technical assessment.
Actions must strengthen controls
The output should change design, planning, supervision, equipment, maintenance, competence, verification or management arrangements.
HSE HSG245 sets out evidence gathering, analysis, risk-control selection and an action plan; it is a 2004 investigation workbook, not a statutory Five Whys rule.
Sources and references
Official context: HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
What is Five Whys in incident investigation?
Five Whys is a causal questioning method used to explore why an incident, near miss or control failure happened.
The investigator starts with a neutral event statement and asks why the event occurred. The answer becomes the basis for the next why. This continues until the team reaches a cause that the organisation can control, correct and verify. The method is attractive because it is easy to understand, but that simplicity can be dangerous if it is used without evidence.
In safety investigations, Five Whys should expose conditions rather than personalities. 'The worker was careless' is not a useful final answer. A stronger answer might be that the procedure conflicted with normal work, the isolation point was not labelled, maintenance records were wrong, supervision did not detect drift or the task was authorised without a hold point.
Good useMove from visible event to correctable system causes.
Poor useFind a quick person to blame.
AspectQuestioning
Good useAsk why a factual condition existed.
Poor useAsk why someone lacked common sense.
AspectEvidence
Good useTest each answer against records, observations and accounts.
Poor useAccept assumptions because they sound plausible.
AspectDepth
Good useContinue until the cause is controllable and useful.
Poor useStop after exactly five questions regardless of quality.
AspectOutput
Good useVerified findings and stronger controls.
Poor useA neat chain with weak reminders.
AspectComplexity
Good useBranch where several causes contributed.
Poor useForce one linear chain for a multi-causal event.
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
Where does Five Whys sit in the investigation process?
Five Whys belongs after immediate response and evidence gathering, and before corrective actions are finalised.
HSE's investigation approach is a learning cycle: gather information, analyse information, identify risk control measures, then implement an action plan. Five Whys sits mainly in the analysis stage, but it depends heavily on the quality of information gathered earlier.
If a team starts asking why before it has preserved evidence, interviewed people or checked records, the chain can become a polished story rather than a reliable analysis. Used well, the method helps test the event sequence and identify which controls were missing, weak, defeated or not verified.
Investigation stages and Five Whys use
Stage
What happens
Five Whys contribution
StageRespond and make safe
What happensTreat casualties, prevent escalation and preserve urgent evidence.
Five Whys contributionDo not analyse until the immediate risk is controlled.
StageDecide level and team
What happensSet investigation depth based on actual and potential severity.
Five Whys contributionUse only where the method matches event complexity.
StageGather information
What happensCollect scene, witness, document, digital and technical evidence.
Five Whys contributionCreate evidence-backed starting points.
StageBuild timeline
What happensDescribe what happened before, during and after the event.
Five Whys contributionCheck that each why fits the sequence.
StageAnalyse causes
What happensIdentify immediate, underlying and system causes.
Five Whys contributionDrill down into selected causal paths.
StageSelect actions
What happensChoose stronger controls and assign responsibilities.
Five Whys contributionMake sure actions address verified causes.
StageReview effectiveness
What happensCheck whether the action reduced risk.
Five Whys contributionTest whether recurrence is less likely.
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
When should Five Whys be used?
Five Whys is best for bounded problems where the facts are reasonably clear and one or more causal paths can be tested.
The method is useful for repeated minor events, housekeeping problems, simple equipment defects, near misses, quality issues, procedural failures and focused lines of enquiry within a larger investigation. It is also useful as a teaching tool because it helps learners move beyond immediate causes.
Use it with caution where there is serious harm, major accident potential, technical uncertainty, conflicting accounts, contractor interfaces, fatigue, process safety barriers, design failure, emergency response weakness or possible legal sensitivity. In those cases, Five Whys may still help, but only as one tool among several.
Good and poor uses of Five Whys
Situation
How to use it
Watch point
SituationSimple near miss
How to use itUse a short evidence-led chain to identify why the control nearly failed.
Watch pointStill check potential severity.
SituationRepeated minor incidents
How to use itUse Five Whys on a representative event and compare with trend data.
Watch pointRepetition may indicate a system weakness.
SituationToolbox learning
How to use itUse it to teach workers how surface causes lead to deeper controls.
Watch pointAvoid public blame discussions.
SituationHigh-potential event
How to use itUse only under competent investigation governance.
Watch pointCombine with timeline, fishbone and barrier review.
SituationTechnical failure
How to use itUse for management questions but involve technical specialists.
Watch pointDo not replace engineering analysis.
SituationDisciplinary concern
How to use itDo not use Five Whys as a disciplinary shortcut.
Watch pointSeparate fair investigation from blame-led assumptions.
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
How should Five Whys be completed step by step?
The method should be written as a chain of evidence-tested answers, with branches where several causes are credible.
Five Whys: test every link.
Start with the neutral event, then test why each condition existed. The five answers shown are hypotheses: photographs could support oil on the floor, but they cannot prove why a work order was closed. That deeper link needs the actual repair history and workflow evidence. A plausible sequence becomes an accepted causal finding only when the evidence supports the links and reasonable alternatives have been examined. This branch asks why the release persisted; the initial seal-failure mechanism needs its own engineering enquiry.
How to use the chain
Write one neutral event statement before asking why. Keep the event separate from its explanation: 'Worker slipped on oil in the walkway' describes an event; 'the worker was careless' is a judgement. For every proposed answer, record the supporting source, the limits of that source and what could contradict the answer. Do not turn a question into a finding merely because the next box needs filling.
What this example does and does not establish
This branch explores why a release persisted, not the physical mechanism of initial seal failure. That mechanism needs engineering examination. The enquiry also needs separate branches for containment, pedestrian exposure and detection. If the work-order audit shows the repair was never closed, reject the fourth hypothesis and revise the chain. Five is a familiar prompt, not a stopping rule or a demand to find one root cause.
A useful stopping point
A branch can end when the evidence supports a specific, correctable system weakness and the team can explain how addressing it would reduce recurrence. Check that explanation backwards from the proposed system weakness to the event. Keep unresolved links visible. Escalate complex, high-potential or technically uncertain events to an appropriately competent investigation; this small chain is not a substitute.
Learning check
The photograph shows oil near a pump. Does it prove a maintenance manager closed a defect incorrectly? No. It supports a scene condition only. You need the original work-order history, repair evidence and relevant accounts before drawing a conclusion about closure.
Which link needs evidence beyond the scene photograph?
The links about unresolved repairs, work-order closure and the missing verification gate require records, accounts and workflow checks. A photograph of oil does not establish those management conditions.
Worked example, not findings from a real incident. Five is a prompt rather than a required number; investigate other causal branches and record unknowns.
Start with a neutral event statement. Good wording describes the event without judgement: 'Worker slipped on oil in workshop bay 2 and fractured wrist', not 'worker was careless'. Then ask why the event happened and write the answer as a condition that can be tested.
Continue only while the answers remain evidence-supported. If the team does not know the answer, mark it as a question and gather more information. If two credible answers exist, branch the chain rather than arguing one away. Stop when the answer is a controllable weakness that can be corrected and checked.
Five Whys step-by-step method
Step
Instruction
Quality check
Step1. Define the event
InstructionWrite what happened, where, when and the actual or potential consequence.
Quality checkIs it neutral and specific?
Step2. Confirm evidence
InstructionCheck photographs, statements, task records, permits, maintenance, training and relevant data.
Quality checkWhat facts are available and what is missing?
Step3. Ask the first why
InstructionExplain why the event happened in factual terms.
Quality checkIs the answer supported by evidence?
Step4. Ask why that condition existed
InstructionMove from the immediate event to the work condition behind it.
Quality checkIs the answer controllable by the organisation?
Step5. Branch where needed
InstructionCreate more than one line if equipment, people, environment or management factors interacted.
Quality checkAre we forcing a single chain?
Step6. Stop at useful causes
InstructionStop when the team identifies correctable system weaknesses.
Quality checkWould fixing this make recurrence less likely?
Step7. Test backwards
InstructionRead the chain from final cause back to event.
Quality checkDoes the logic still make sense?
Step8. Convert to actions
InstructionAssign actions, owners, dates and effectiveness checks.
Quality checkDo actions strengthen controls or merely remind people?
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
What evidence standard should each why meet?
For every “why”, record the evidence, its source and what could disprove the explanation. Where several causes interact, branch the chain instead of forcing one path to a preferred answer.
A good answer is specific, testable and connected to the event. It should be possible to say what evidence supports it and what evidence might disprove it. If the answer relies on memory, opinion or assumption, that does not make it useless, but it should be marked as an open line of enquiry.
The evidence standard protects the investigation from hindsight bias. After an incident, the warning signs can look obvious. The job of the investigator is to understand what was known, expected, available and practical at the time.
How to use itPhotograph and compare with expected condition.
Evidence typeDocumentary evidence
ExamplesRisk assessment, RAMS, permit, inspection, maintenance, training and audit records.
How to use itCheck whether paperwork matched work-as-done.
Evidence typeDigital evidence
ExamplesCCTV, access logs, telemetry, alarm history, process data and messages.
How to use itUse timestamps to test the sequence.
Evidence typePeople evidence
ExamplesWitness accounts, worker experience, supervisor explanation and contractor input.
How to use itInterview respectfully and test consistency.
Evidence typeContext evidence
ExamplesWorkload, staffing, weather, lighting, shift pattern, fatigue, change and time pressure.
How to use itExplain why decisions or conditions existed.
Evidence typeTechnical evidence
ExamplesEngineering inspection, failure analysis, sampling, exposure results or specialist opinion.
How to use itUse when the cause cannot be assessed by generalists.
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
When should a Five Whys chain branch?
A Five Whys chain should branch whenever more than one credible condition contributed to the event.
Branch when more than one condition matters.
A slip needs both a release and an opportunity for contact; delayed detection or response may contribute too. Explore those paths separately rather than making one explain every condition. Each question is an enquiry, not a finding. Evidence may support, contradict or leave a link unresolved. If relevant training and demonstrated competence are established, reject a missing-training hypothesis and continue examining the conditions that actually fit the evidence.
Why branch?
Release, exposure and response are separate questions. A well-maintained pump can still suffer an unexpected failure; effective containment and route design should limit the resulting exposure. Conversely, a sound spill response does not explain why an avoidable leak recurred. Keep credible pathways separate so that the actions address the combination of conditions rather than one convenient story.
Apply the evidence gate to each link
YES means retain the link with its evidence and confidence limits, then test further. NO means reject or revise it and explain why. UNKNOWN means identify the evidence needed and who will obtain it. A contradictory record is useful: if relevant training and competent performance are established, do not retain a missing-training conclusion. Examine equipment, task demands, information and organisational conditions without assuming those alternatives are already proven.
Use a practical enquiry log
For each branch record the question, proposed explanation, supporting and contradictory evidence, confidence, next enquiry and responsible person. Distinguish an untested possibility from a supported finding in the final report. No voting exercise or neat five-box chain can replace that evidence test.
Learning check
Two witnesses offer different explanations for the same intervention. Keep both accounts and investigate what each person could see, know and recall. Compare available records and technical evidence; do not discard an account simply because it conflicts with the preferred narrative.
What should happen when two credible explanations remain?
Keep separate branches, identify evidence that can distinguish them and show uncertainty. Do not choose a favourite story or force both explanations into one five-box chain.
The branches are examples, not an exhaustive cause taxonomy. Complex, high-potential or technically uncertain events may need a broader causal map and specialist input.
Many poor Five Whys worksheets fail because they force a single line. A forklift near miss may involve pedestrian route design, reversing visibility, delivery pressure, supervision, driver competence and a temporary storage change. One chain cannot hold that complexity without distorting it.
Branching does not make the method complicated; it makes it honest. Each branch can be short, but it should follow evidence. The final report can then explain how the branches interacted and which controls need strengthening.
Branching prompts for Five Whys
Prompt
Why it matters
Example branch
PromptDid more than one barrier fail?
Why it mattersIncidents often occur when controls line up badly.
Example branchGuard missing, isolation not verified and supervision absent.
PromptDid people, plant and process all contribute?
Why it mattersDifferent cause types need different actions.
Example branchCompetence, machine design and procedure conflict.
PromptWas there recent change?
Why it mattersChange can create hidden mismatches.
Example branchTemporary layout, new contractor or altered shift pattern.
PromptWere there repeated weak signals?
Why it mattersPrevious near misses may show the system already knew.
Example branchDefect reports, audit findings or informal workarounds.
PromptWas work-as-done different from work-as-imagined?
Why it mattersProcedures may not reflect real constraints.
Example branchTask normally requires shortcut to meet production demand.
PromptWas the final answer too neat?
Why it mattersOverly simple chains may hide organisational causes.
Example branchFinal cause is 'carelessness' or 'did not follow procedure'.
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
How should immediate, underlying and root causes be separated?
Five Whys should help the team move from what directly happened to why the control system allowed it to happen.
Different organisations use slightly different language, but the investigation purpose is consistent. Immediate causes are closest to the event. Underlying causes explain the unsafe conditions or acts that allowed the event. Root or system causes sit deeper in management arrangements, design, competence, maintenance, planning, procurement, leadership or review.
The chain is useful only when it creates a clear line from event to action. A root cause that nobody can control is too vague. A root cause that points only to an individual's attitude is usually too shallow.
Cause levels in Five Whys
Cause level
Plain English meaning
Example
Cause levelImmediate cause
Plain English meaningHSG245 describes the condition or action closest to harm; organisations may use different terminology.
ExampleOil underfoot and the resulting loss of footing are close to the harm; investigate how the leak and failed controls arose.
Cause levelUnderlying cause
Plain English meaningThe unsafe condition or system gap that allowed the immediate cause.
ExampleOil leak had not been identified or contained before work started.
Cause levelRoot/system cause
Plain English meaningA deeper management weakness from which other failings grew.
ExampleInspection regime did not cover leak-prone equipment and defect escalation was weak.
Cause levelContributing factor
Plain English meaningA condition that increased likelihood or severity.
ExampleLighting made the oil difficult to see.
Cause levelLatent condition
Plain English meaningA hidden weakness present before the event.
ExampleMaintenance backlog had normalised small leaks.
Cause levelCorrectable cause
Plain English meaningA cause the organisation can realistically control.
ExampleRevise inspection, containment and defect close-out arrangements.
HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
How should Five Whys handle human error?
A decision or action by a worker may be one fact, but it rarely explains why the work system allowed the hazard. Test task design, equipment, information, staffing, supervision and organisational pressure.
People make decisions inside a work system. They see certain information, use available equipment, manage workload, respond to supervision, follow local norms and adapt to pressure. If an investigation stops at 'the worker forgot', it has usually stopped just when the useful questions begin.
Better questions include: why was the task easy to forget, why was the interface confusing, why was the hold point missing, why did the person feel unable to stop, why had supervision not detected drift and why had previous warnings not led to change?
Human factors prompts for Five Whys
Area
Questions to ask
Possible evidence
AreaTask
Questions to askWas the task complex, rushed, abnormal, poorly sequenced or hard to perform safely?
Possible evidenceTask observation, method statement and worker accounts.
AreaEquipment
Questions to askWas the equipment intuitive, reliable, guarded, labelled and suitable?
Possible evidenceInspection, design information and defect history.
AreaEnvironment
Questions to askDid noise, heat, lighting, space, weather or congestion influence the event?
Possible evidenceScene photographs and environmental records.
AreaCompetence
Questions to askWas competence defined, trained, assessed and refreshed for the actual task?
Possible evidenceTraining matrix, assessment record and supervisor check.
AreaSupervision
Questions to askWere expectations clear and was work checked at the right points?
Possible evidenceBriefings, supervision logs and shift handover.
AreaOrganisation
Questions to askDid resources, workload, culture, procurement, maintenance or production pressure shape the conditions?
Possible evidenceManagement review, audit findings and action trackers.
Use HSE human-factors guidance to test job, individual and organisational influences without stopping at blame.
Sources and references
Official context: HSG245. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
What does a good Five Whys example look like?
The conveyor chain below is a set of possible explanations, not a verified finding. Check each step against machine condition, energy-isolation records, work observation, witness accounts and maintenance history before accepting a cause.
A suspected wrong part needs identity evidence across the chain
Normal component-and-record review. The boxed component is not fitted; the separate analytical comparison supplies no match, alloy, fit, state or restart finding.Full written explanation
A normal machine-workshop review shows a component inside a closed box, review papers and a closed machine enclosure. Picture key: 1 Closed component box · 2 Review papers · 3 Closed machine enclosure. The boxed component is not shown fitted. Three separate analytical comparisons distinguish the specified requirement and revision, ordering/receipt identity and revision, and the actual fitted component identity. Two dashed conceptual links compare those questions; a separate coupling-and-shaft insert is for identity only, not assembly, tolerance or live testing. The box, machine and records do not establish a match, mismatch, alloy, fit, energy state, fault or permission. Four unnumbered checks protect the task, trace identity and revisions, test competing explanations and verify an effective correction through competent arrangements. Keep uncertainty open; a neat Why chain does not justify restart.
Machine-workshop comparison: specification, order, receipt and fitted identity are questions to check, not assumed failures.
Protect the equipment and task. Use competent arrangements and preserve evidence; do not recreate the failure.
Trace identity and current revisions. Compare actual specification, ordering/receipt records and the fitted part.
Test competing explanations. Keep supported, contrary and missing evidence distinct before assigning a cause.
Verify the effective correction. Use competent change/acceptance checks and confirm the outcome in real work safely.
When the evidence does not fit: An uncertain identity or neat Why chain does not justify restart. Keep the affected task protected and unresolved causes open for competent review.
Who acts: Investigation lead, engineering/maintenance owner, procurement or information owner and affected operations team.
Changed workplace
Distribution centre: Test interacting physical-route and delivery/change explanations with their sources.
Machine-workshop part identity: Trace specification, records and fitted identity without assuming which organisation failed.
Evidence check: Illustrative hypotheses only. No actual near miss, component mismatch, blame finding, fit/tolerance, assembly instruction or permission to restart is assigned.
Consider a worker who cuts their hand while clearing a jam on a powered conveyor. A weak investigation might conclude that the worker failed to follow the procedure. A stronger Five Whys chain tests why the jam had to be cleared manually, why isolation was not used, why supervision did not detect the practice and why previous jam reports had not led to redesign.
The result should be practical. If the chain ends with 'worker did not follow procedure', the action will likely be a reminder. If the chain reaches design, isolation, planning and maintenance weaknesses, the action can reduce risk at source.
Worked example: hand injury during jam clearing
Why level
Hypothesis to test
Action implication
Evidence to check
Why levelEvent
Hypothesis to testWorker cut hand while clearing jammed material from powered conveyor.
Action implicationMake area safe, treat injury and preserve evidence.
Evidence to checkInjury and incident record, machine state, photographs.
Why levelWhy 1
Hypothesis to testHand entered nip point while stored energy remained available.
Action implicationReview guarding, isolation and energy control.
Evidence to checkGuard/access condition and isolation test.
Why levelWhy 2
Hypothesis to testJam clearing was routinely done through access panel during production stops.
Action implicationObserve work-as-done and revise method.
Evidence to checkWork observation, production and training records.
Why levelWhy 3
Hypothesis to testProcedure required isolation, but production targets and frequent jams encouraged quick clearing.
Action implicationAddress workload, planning and supervisor expectations.
Evidence to checkProcedure, shift targets, interviews and supervision records.
Why levelWhy 4
Hypothesis to testFrequent jams had been reported but treated as production inconvenience, not a safety design issue.
Action implicationReview defect escalation and engineering change criteria.
Evidence to checkJam/defect logs and escalation trail.
Why levelWhy 5
Hypothesis to testThe maintenance and improvement process did not classify repeated jams as a safeguarding concern.
Action implicationIntroduce risk-based escalation for repeated equipment faults.
Evidence to checkMaintenance priority and safeguarding review criteria.
Why levelPossible combined finding if evidence confirms
Hypothesis to testThe injury arose from exposed energy during a normalised workaround, driven by recurring equipment jams and weak escalation.
Action implicationEngineering review, interlocked access, jam reduction, permit/LOTO verification and action effectiveness checks.
Evidence to checkConverging physical and documentary evidence; competing explanations.
Observe or test tasks only under a safe competent plan. Stop affected machinery work until guarding, isolation and task controls are verified; investigate past records or use controlled simulations instead of recreating an injury mechanism.
Sources and references
Official context: HSG245; HSE human-factors guidance; HSE work-equipment and machinery precautions; HSE HSG85 electrical safe working. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate. Machinery/electrical precautions supply GB control context; inspect work only under a safe plan, never recreate an uncontrolled jam or expose live energy.
Investigation methods and worked examples
How can Fishbone and Five Whys help explore causes?
A fishbone, also called a cause-and-effect or Ishikawa diagram, places the event at its head. The main bones group possible contributors; smaller branches explore what led to each one. Categories are prompts to investigate, not findings.
Fishbone: explore the wider picture
Use it when several things may have contributed. Start with categories such as people, equipment, methods, materials, environment and management; rename them to suit the work. Add causes and subcauses without forcing a single chain.
Ask what led to a specific explanation. Branch when there is another reason, and stop where the evidence runs out. Five is a guide, not a target. Use the two methods together to examine a broad picture and its individual paths.
Define what happened, including the task, place and sequence. Keep the event separate from assumptions about why.
Gather accounts from people involved and add several possible explanations. Explore work conditions, equipment and management arrangements as well as individual actions.
Record supporting and contradictory evidence for each explanation. Keep untested ideas separate from accepted findings; add an open question where evidence is missing.
Review immediate, underlying and root causes from the evidence. A category, the final card or the depth of a branch does not decide the cause level.
Link actions to the supported causes, assign an owner and date, then check implementation and whether the action prevents recurrence.
Compare the worked examples
The two BuildOut reports examine the same invented excavator-arm/scaffold incident: 18 explanations and six actions. Their evidence references are fictional teaching records.
BuildOut fishbone
Six cause categories with subcauses, evidence checks and actions · 24 pages.
How do Five Whys and fishbone analysis work together?
Fishbone analysis widens the investigation; Five Whys drills down into selected causes.
Fishbone analysis is useful when the team needs to map many possible causes across people, plant, method, environment, materials and management system factors. Five Whys is useful when the team wants to examine one branch more deeply.
Used together, they reduce two opposite risks. Five Whys alone can become too narrow. Fishbone alone can become a long list of possibilities without depth. The stronger workflow is to map the landscape, select important branches, drill down, test evidence, then write actions.
Using fishbone and Five Whys together
Stage
Tool
Output
StageDefine event
ToolBoth
OutputNeutral problem statement.
StageMap possible causes
ToolFishbone
OutputBroad categories and possible causal factors.
OutputDeeper cause chains under selected branches.
StageTest evidence
ToolBoth
OutputConfirmed, possible, disproved and open findings.
StageChoose actions
ToolAction review
OutputCorrective actions linked to verified causes.
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
How should Five Whys connect to barriers and controls?
Every cause should be connected back to the control that should have prevented, detected or mitigated the event.
Barrier thinking makes Five Whys more useful. Instead of asking only why the event happened, ask which barrier was missing, weak, defeated, bypassed, unavailable, misunderstood or unverified. This keeps the analysis close to risk control.
For higher-risk work, the final output should show whether prevention, detection, control, mitigation, emergency response and assurance arrangements were reliable. If the analysis cannot name the failed control, it may still be too vague.
Barrier prompts for Five Whys
Barrier question
What it reveals
Example
Barrier questionWhat should have prevented the event?
What it revealsMissing or weak prevention controls.
ExampleGuarding, segregation, isolation, ventilation or planning.
Barrier questionWhat should have detected the problem earlier?
What it revealsInspection, monitoring or alarm gaps.
ExampleDefect reporting, gas detection, audits or supervision.
Barrier questionWhat should have controlled the situation?
What it revealsProcedures, permits, competence or engineering controls.
ExamplePermit hold point or lock-off check.
Barrier questionWhat should have reduced the consequence?
What it revealsEmergency response, PPE or mitigation weakness.
ExampleFirst aid, spill kit, fire response or eyewash.
Barrier questionHow was the barrier assured?
What it revealsWhether controls were checked, tested and maintained.
ExampleAudit, inspection, maintenance or competence verification.
Barrier questionCould the same barrier be weak elsewhere?
What it revealsExtent of condition and wider learning.
ExampleOther lines, sites, shifts or contractors.
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
How should Five Whys findings become strong corrective actions?
Close an investigation action only after a named owner installs the measure, checks it in real work and tests whether the failure recurs. Training alone is weak when the verified problem is equipment or layout.
The action plan is where investigation quality becomes visible. Weak actions tell people to be careful, repeat training without evidence of a competence gap, or update a procedure nobody uses. Strong actions change the work system: design, engineering controls, access, maintenance, planning, supervision, procurement, competence verification and leadership review.
Actions should also be tested. Completion is not the same as effectiveness. A revised procedure is complete when it is issued; it is effective only when the task is observed, workers understand it and the original weakness has been reduced.
ExampleRemove the need to access the danger zone during clearing.
Action typeEngineering control
StrengthStrong
ExampleInterlock access panel, improve guarding or redesign equipment to reduce jams.
Action typeSystem control
StrengthStrong to medium
ExampleIntroduce risk-based defect escalation and independent isolation verification.
Action typePlanning and resources
StrengthMedium to strong
ExampleAllow downtime to clear defects rather than normalising workarounds.
Action typeCompetence and supervision
StrengthMedium
ExampleTarget training and supervisor checks to a verified gap.
Action typeProcedure update
StrengthMedium to weak unless verified
ExampleRevise method and check use in real work.
Action typeReminder or poster
StrengthWeak if used alone
ExampleUse only as supporting communication, not the main action for a serious finding.
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
How can the hierarchy of controls turn Five Whys findings into effective risk reduction?
Use ERICPD and the HSE five-level hierarchy on the hazard that evidence reveals. The Why chain helps locate a failed barrier; it is not itself a protective measure.
A near miss can have interacting explanations, not one blame chain
Normal distribution-centre review beside two candidate Why branches. Neither the draft board nor rail establishes a near miss, cause or approved traffic arrangement.Full written explanation
A normal distribution-warehouse scene provides rail, draft-layout-board and clipboard context beside a separate branching Why enquiry. Picture key: 1 Warehouse rail · 2 Draft layout board · 3 Review clipboard. A reported reversing near miss is the neutral analytical starting point, not a pictured incident. Two independent dashed candidate branches ask about route/separation and actual work conditions, and about delivery/change information, revisions, bookings and communication. Both join a demonstrated-control-gap question before owned action and effectiveness checking. Retain contrary evidence and interacting explanations; exactly five answers are not required. Three complete paired explanations establish the event basis, test branches and choose stronger action. The scene proves no event, cause, safe route, barrier adequacy, role, equipment state or permission.
Distribution-centre example: each Why is a hypothesis until its evidence and competing explanations are checked.
Start from a verified event basis. Separate observation, source and uncertainty before asking why a barrier failed.
Branch and test the explanations. Compare physical protection, task/change information and management evidence.
Choose and test stronger action. Act on the supported gap and verify the actual outcome, reopening repeated failure.
Change the pathway
Five is not a proof requirement. Stop a line when evidence does not support it; follow interacting branches where needed.
A plausible answer is not a source. Record contrary material and what remains to be checked instead of forcing agreement.
A Why chain is not a safeguard. Select a feasible source-level or physical control before relying only on reminders.
Evidence check: Illustrative hypotheses only. No actual near miss, component mismatch, blame finding, fit/tolerance, assembly instruction or permission to restart is assigned.
HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate. GB traffic/DSEAR sources support the respective illustrative control examples.
A delivery change causes a reversing vehicle to pass near a worker. Test the route plan, barriers, booking and supervision before accepting “worker error” as a cause.
A workshop has repeated solvent spills. Test container design, couplings, task timing and maintenance against physical evidence before choosing a corrective measure.
How can the ERICPD hierarchy of controls turn Five Whys findings into effective risk reduction?
Worked activity: Task application for Five Whys for Incident Investigation
Activity and release context
A delivery change causes a reversing vehicle to pass near a worker. Test the route plan, barriers, booking and supervision before accepting “worker error” as a cause.
Task intervention and feasibilityUse pre-use inspection, change approval and trained shutdown/withdrawal. Source: official guidance.
Owner, test and evidenceShift lead observes task and permit.
Failure and stop decisionProcedure differs from real equipment: hold task.
Hazard and harm routeSame scenario
ERICPD → five-level controlPPE → PPE
Task intervention and feasibilitySelect chemical PPE for residual splash using substance data, not as the primary release barrier. Source: official guidance.
Owner, test and evidenceSupervisor checks compatibility and fit.
Failure and stop decisionSubstance or PPE compatibility unknown: stop.
Worked activity: Task application for Five Whys for Incident Investigation
Activity and release context
A delivery change causes a reversing vehicle to pass near a worker. Test the route plan, barriers, booking and supervision before accepting “worker error” as a cause.
Task intervention and feasibilityUse pre-use inspection, change approval and trained shutdown/withdrawal. Source: official guidance.
Owner, test and evidenceShift lead observes task and permit.
Failure and stop decisionProcedure differs from real equipment: hold task.
Hazard and harm routeSame scenario
ERICPD → five-level controlPPE → PPE
Task intervention and feasibilitySelect chemical PPE for residual splash using substance data, not as the primary release barrier. Source: official guidance.
Owner, test and evidenceSupervisor checks compatibility and fit.
Failure and stop decisionSubstance or PPE compatibility unknown: stop.
Task intervention and feasibilityTrend spills and test whether corrective action prevents recurrence. Source: official guidance.
Owner, test and evidenceInvestigator reviews field evidence after restart.
Failure and stop decisionRepeat spill: reopen Why chain and halt method.
Sources and references
Official context: HSE hierarchy. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate. GB traffic/DSEAR sources support the respective illustrative control examples.
What are the limitations of Five Whys?
A single linear chain can miss parallel failures and time sequence. For complex or high-potential events, use a timeline, fishbone or barrier analysis and specialist evidence alongside Five Whys.
The method can become linear, biased and too shallow. It can also produce different answers depending on who is in the room. A manager may see behaviour; a worker may see poor equipment; an engineer may see design; a safety adviser may see missing assurance. The value comes from testing these perspectives, not choosing the quickest one.
For major injury, major accident potential, process safety, complex technical failure, occupational disease, high-value asset damage or legal sensitivity, Five Whys should be supported by competent investigation governance and other tools.
Five Whys limitations and safeguards
Limitation
How it can mislead
Safeguard
LimitationLinear thinking
How it can misleadForces one chain even where causes interact.
SafeguardBranch the analysis.
LimitationHindsight bias
How it can misleadMakes the event look obvious after it happened.
SafeguardAsk what was known and available at the time.
LimitationBlame endpoint
How it can misleadStops at carelessness or failure to follow rules.
SafeguardAsk why the behaviour was possible or likely.
LimitationWeak evidence
How it can misleadTurns guesses into causes.
SafeguardMark evidence status and gather missing information.
LimitationOver-simple actions
How it can misleadProduces retraining and reminders.
SafeguardReview action strength and effectiveness checks.
LimitationWrong tool for complexity
How it can misleadMisses technical, organisational or barrier interactions.
SafeguardCombine with fishbone, timeline, barrier or technical analysis.
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
Which investigation and reporting duties apply by jurisdiction?
Five Whys is not a named legal requirement. GB and Northern Ireland have distinct general work-health and RIDDOR reporting routes; the analysis method does not replace notification or risk control.
HSG245 is 2004 HSE method guidance. Its stages support an evidence-led investigation, but the employer still has to meet the current law that applies at the site.
Screen reportability before deciding the investigation method. GB RIDDOR 2013 and NI RIDDOR 1997 have different thresholds, including over-seven-day GB reporting versus the separate NI over-three-day route. Use HSENI for NI incident reporting.
The register should connect each verified cause to a control improvement, owner, timescale and effectiveness check.
Five Whys action register fields
Field
Purpose
Example
FieldEvent reference
PurposeLinks the analysis to the incident or near miss.
ExampleINV-2026-021
FieldProblem statement
PurposeDefines the event neutrally.
ExampleWorker slipped on oil in workshop bay.
FieldCause chain or branch
PurposeShows the evidence-led why sequence.
ExampleLeak not detected because inspection route excluded rear of machine.
FieldEvidence status
PurposeSeparates confirmed, possible and open findings.
ExampleConfirmed by inspection record and photo.
FieldControl weakness
PurposeNames the failed or missing control.
ExampleInspection regime and defect escalation.
FieldAction
PurposeStates the practical improvement.
ExampleRevise inspection route and add leak-response standard.
FieldOwner and due date
PurposeCreates accountability.
ExampleWorkshop manager, 30 September 2026.
FieldEffectiveness check
PurposeConfirms whether the action works.
ExampleThree inspection samples and worker feedback after one month.
FieldWider applicability
PurposeChecks whether the weakness exists elsewhere.
ExampleReview similar machines across all workshops.
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
How could BuildOut Ltd use Five Whys?
BuildOut Ltd would use Five Whys to drill into construction incidents while keeping the investigation evidence-led and practical.
BuildOut Ltd
BuildOut Ltd is a construction and refurbishment contractor used by SHARE to show how investigation topics apply in a practical business context.
A BuildOut labourer trips over temporary lighting cable in a refurbishment corridor and suffers a sprained wrist. The supervisor first makes the area safe, arranges first aid, photographs the cable route, records witness accounts and checks the construction phase plan, site inspection records, temporary electrical plan and contractor handover notes.
The Five Whys chain does not stop at 'worker did not look where they were going'. It asks why the cable was in the walkway, why the temporary lighting route had changed, why the change had not been captured in the permit or daily coordination meeting, why the subcontractor was allowed to alter the route without supervisor approval and why the inspection checklist did not include temporary services crossing pedestrian routes.
BuildOut's actions include using a competent temporary-services plan to remove cables from walking routes, with suitable high-level routing where practicable and without introducing electrical, access or falling-object hazards, adding temporary service routes to the daily coordination board, briefing subcontractors on cable management rules, updating the inspection checklist, and reviewing similar projects. The close-out check includes a site walk with the supervisor, subcontractor and worker representative.
BuildOut Five Whys management example
Management step
How BuildOut applies it
Evidence
Management stepAssess
How BuildOut applies itClassifies the trip by potential harm and checks whether temporary services create wider risks.
EvidenceInvestigation level decision and site photos.
Management stepAnalyse
How BuildOut applies itUses Five Whys branches for cable route, coordination, subcontractor control and inspection failure.
EvidenceEvidence-led cause chain.
Management stepTrain
How BuildOut applies itBriefs supervisors on neutral problem statements, branching and evidence status.
EvidenceSupervisor investigation training record.
Management stepImplement
How BuildOut applies itUpdates temporary services control, coordination board, subcontractor rules and inspection prompts.
EvidenceRevised site documents and briefing record.
Management stepCheck
How BuildOut applies itSamples inspections and observes cable management during active work.
EvidenceInspection record and close-out photos.
Management stepLearn
How BuildOut applies itShares learning across similar refurbishments and updates the contractor induction.
EvidenceLearning bulletin and management review.
Sources and references
Official context: HSG245; HSE human-factors guidance; HSE GB construction slips and trips; HSE HSG85 electrical safe working. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate. HSE GB construction/electrical context supports planned cable routing; competent temporary-services design and field verification remain necessary.
Who needs Five Whys competence, and what proves it?
Test evidence handling, neutral questioning, jurisdiction screening and action effectiveness with a realistic incident, not attendance alone.
Who needs to demonstrate what
Role
Learning to test
Competence demonstration
Assessor and record
Reassessment trigger
RoleWorkers and witnesses
Learning to testPreserve facts and distinguish observation from interpretation.
Competence demonstrationDescribe the timeline and evidence source.
Assessor and recordSupervisor records briefing.
Reassessment triggerIncident or process change.
RoleSupervisors
Learning to testSecure scene and screen GB or NI reportability.
Competence demonstrationWork through sample report route and evidence capture.
Assessor and recordSafety lead reviews decision.
Reassessment triggerJurisdiction or threshold change.
RoleInvestigators
Learning to testTest each Why and branch where evidence supports multiple causes.
Competence demonstrationBuild a chain with counter-evidence and causal rationale.
Assessor and recordCompetent investigation lead reviews.
Reassessment triggerComplex event or new evidence.
RoleTechnical specialists
Learning to testValidate engineering or human-factor findings.
Competence demonstrationUse safe analysis, inspection or controlled tests to validate barrier design; do not recreate exposure to live machinery or other hazardous failure.
Assessor and recordIndependent authority signs technical finding.
Reassessment triggerDesign or failure mode change.
RoleAction owners
Learning to testInstall stronger controls and verify their effect.
Competence demonstrationShow field test, owner and recurrence review.
Assessor and recordSponsor signs closeout.
Reassessment triggerControl fails or event recurs.
Sources and references
Official context: HSG245; HSE human-factors guidance; RIDDOR 2013; RIDDOR (NI) 1997; HSENI incident reporting. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate. Separate reporting rules support only reporting-route learning in this table.
How does Five Whys support study and professional development?
Five Whys helps learners explain the movement from immediate causes to underlying and root/system causes.
For practical learning, place Five Whys inside the wider investigation process. Start with evidence gathering, then analyse causes, select controls and review whether actions work. Do not write a generic chain that ends with 'worker error'. Show how work design, supervision, equipment, competence and management arrangements shaped the event.
Scenario-based answers should be specific. In a machinery injury, discuss guarding, isolation, maintenance, jams, supervision and production pressure. In a slip incident, discuss contamination, flooring, cleaning, footwear, lighting, reporting and inspection. In a process safety event, discuss barriers, alarms, procedures, competence, change control and assurance.
Study and professional application
What to know
How to apply it
Common trap
What to knowHSG245 process
How to apply itUse Five Whys during analysis, after evidence gathering.
Common trapStarting with causes before facts.
What to knowCause levels
How to apply itSeparate immediate, underlying and root/system causes.
Common trapCalling every answer a root cause.
What to knowEvidence status
How to apply itLabel confirmed, possible, disproved and open answers.
Common trapTreating assumptions as facts.
What to knowHuman factors
How to apply itExplore job, individual and organisational conditions.
Common trapStopping at human error.
What to knowAction strength
How to apply itChoose controls that reduce recurrence risk.
Common trapRelying on reminders and retraining only.
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
How can BS EN ISO 45001 support five whys for incident investigation management?
A voluntary occupational health and safety system can connect evidence-led investigation, verified causes, stronger controls and effectiveness checks without treating a Why chain as proof.
HSE public guidance supports practical management themes in Great Britain. ISO clause mapping, conformity and certification claims remain held for current licensed-text and specialist review; this page does not establish compliance or certification.
Sources and references
Official context: HSE health and safety management-system overview. HSE public guidance supports practical management themes in Great Britain. ISO clause mapping, conformity and certification claims remain held for current licensed-text and specialist review; this page does not establish compliance or certification.
What are the warning signs of poor Five Whys analysis?
Poor Five Whys analysis usually sounds neat, quick and certain, but does not improve the work system.
Why it weakens learningThe investigation begins from a conclusion.
Better practiceUse a neutral event statement.
Warning signEvery answer is opinion
Why it weakens learningThe chain cannot be defended.
Better practiceShow evidence or mark as open.
Warning signThere is only one line for a complex event
Why it weakens learningInteractions are hidden.
Better practiceBranch the chain.
Warning signHuman error is the final answer
Why it weakens learningSystem causes are missed.
Better practiceAsk why the error was possible.
Warning signThe answer repeats the event
Why it weakens learningNo deeper cause has been found.
Better practiceAsk what condition allowed it.
Warning signActions are reminders
Why it weakens learningControls are not strengthened.
Better practiceUse stronger design, engineering, planning or assurance actions.
Warning signNo effectiveness check exists
Why it weakens learningActions can close without reducing risk.
Better practiceDefine field verification or trend review.
Sources and references
Official context: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
Which related SHARE pages help build the investigation picture?
Five Whys should connect with wider investigation methods, evidence handling, human factors and corrective action tracking.
Reader navigation, terms and proposed documents only; no linked-page evidence, instructional asset or reuse approval is implied.
Five Whys FAQs - what do people ask?
People usually ask whether Five Whys is enough, how to avoid blame and how to turn causes into actions.
Must a Five Whys chain have exactly five questions?
No. Continue or branch only as far as the evidence supports; the number five is a prompt.
Sources and references
Official support: HSG245. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
Can a Why answer be only “human error”?
No. Test job design, equipment, instructions, supervision and organisational conditions.
Sources and references
Official support: HSE human-factors guidance; HSG245. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
Does Five Whys prove a root cause?
No. It structures hypotheses; verify findings against physical, documentary and witness evidence.
Sources and references
Official support: HSG245. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
When should the chain branch?
Branch when independent failures or interacting pathways appear; a single line can hide them.
Sources and references
Official support: HSG245; HSE human-factors guidance. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
Does a RIDDOR report replace the investigation?
No. Screen the correct GB or NI reporting route and separately investigate control failures.
No. It is a 2004 HSE investigation workbook, used as method guidance.
Sources and references
Official support: HSG245. HSG245 is a2004 GB method workbook; historical reporting references/statistics are not current law.
What closes a corrective action?
Installation, field verification and an effectiveness check, with recurrence triggering a renewed review.
Sources and references
Official support: HSG245. HSG245 2004 and HSE GB human factors support investigation stages and evidence-led causal analysis. Five Whys chains are illustrative hypotheses, not a mandated method or proof; reporting law is separate.
Which official sources support this guidance?
Use the direct source for the jurisdiction and decision in question; a guide, statute and voluntary standard have different roles.
Jurisdiction and editionGreat Britain; Current HSE guidance
Supported claim or decisionHSE Great Britain workplace-transport guidance supplies the separate illustrative traffic-control context; voluntary activity campaigns do not replace vehicle/pedestrian controls.
Jurisdiction and editionGreat Britain; Current HSE guidance
Supported claim or decisionHSE Great Britain DSEAR background supports dangerous-substance assessment and the priority of prevention, control and mitigation; NI law and licensed equipment specifications require separate review.
HSE Great Britain machinery guidance supports appropriate safeguarding, competent work and controlled maintenance; a Five Whys chain does not prove cause or authorise recreating a hazardous jam.
HSG85 supplies Great Britain electrical safe-working and competent isolation context; the investigation illustration does not authorise live work or hazardous failure recreation.
HSE Great Britain construction slips-and-trips guidance supports planning routes and temporary services to avoid trailing cables, including suitable high-level routing or cordless equipment; verify no new electrical or access hazard.
HSE public guidance supports practical management themes in Great Britain. ISO clause mapping, conformity and certification claims remain held for current licensed-text and specialist review; this page does not establish compliance or certification.
What do the acronyms and key terms mean?
Acronyms should be explained so investigation language remains accessible to workers, supervisors and learners.
Acronyms and meanings
Acronym
Meaning
Plain English use
AcronymHSG245
MeaningHSE guidance on investigating accidents and incidents
Plain English useMain HSE investigation workbook.
AcronymHSE
MeaningHealth and Safety Executive
Plain English useGreat Britain workplace health and safety regulator.
AcronymRCA
MeaningRoot Cause Analysis
Plain English useStructured analysis of deeper causes and system weaknesses.
AcronymRIDDOR
MeaningReporting of Injuries, Diseases and Dangerous Occurrences Regulations
Plain English useStatutory reporting regime for specified work-related events.
Plain English useControl-selection teaching aid applied to verified hazards.
Reader navigation, terms and proposed documents only; no linked-page evidence, instructional asset or reuse approval is implied.
Documents to download
Download editable resources from the SHAREhub environment to support your work. Working forms and spreadsheet input areas are blank. Reports, plans, guides, briefings, procedures and policies contain completed worked example content to adapt.
Fishbone and Five Whys evidence branching worked guide
For investigators, worker representatives and managers using existing incident records. Use fishbone to organise possible causes and Five Whys to test selected causal paths. Pages 2 and 3 are an independently invented case; page 4 has blank local-use fields. A diagram or chain does not prove causation.
Completed practical guide with blank working record · DOCX · 29 KB · v1.0
Blank 12 page investigation report in editable Word with a matching fillable PDF. Record the event, precursor and follow up timeline, evidence, interviews, findings, controls, SMART actions and separate completion and effectiveness decisions. Duplicate record pages in Word as needed.
Blank editable report form · DOCX · 284 KB · v1.0 · UK; check the current Great Britain or Northern Ireland reporting route
Practical training on evidence gathering, timelines, Five Whys, fishbone analysis, human factors, corrective action strength and investigation report quality.
Professional learning
Bring this into my business
Link my operations to SHARE knowledge and AI Intelligence.
Connect near-miss reports, investigation stages, evidence records, Five Whys chains, fishbone diagrams, action registers and management review.
From guidance to action
Connect this topic to workplace controls, records and actions. Select relevant guidance, tailor it to the work and check that the controls are effective.
Ask SHARE Intelligence
This access journey shows how SHARE Intelligence will work. The live service will return permission-aware answers with supporting official sources.
Welcome back
Action recorded
This SHARE action is ready to connect to the live service.