Show the reasoning behind your investigation and keep a branded report. A company-branded PDF investigation report with the branching why map and its supporting detail.
Trace the evidence behind each explanation, explore alternative branches and connect reviewed causes with improvement actions. Add your organisation’s name, logo and investigation reference, then download the PDF as an appendix to your investigation report or attach it to the relevant case in your incident reporting system.
Move beyond the first explanation, make alternative causes visible and give reviewers a clear trail from the event to evidence and improvement actions.
Keep it with your own records
Choose a browser save to retain an account-scoped working copy. Download the report for your investigation file; this worksheet does not automatically approve findings or update an organisation case.
How it works — the theory and its limits
Ask why an event or condition occurred, then investigate the explanation with evidence. Where there is more than one plausible contributor, develop separate paths.
“Five” is a guide, not a target or stopping rule. Stop a path for an explained reason, keep uncertainty visible and use other investigation methods where the event needs them.
The number of whys does not establish a root cause. Conclusions and action effectiveness still need review.
Five is a guide, not a stopping rule. Investigate as far as the evidence supports, keep alternative explanations visible and use other methods where needed. This local worksheet does not accept findings, approve work or update private organisation cases.
Work locally, add a business name and logo, and download a branded report. After your first browser save, applied changes save automatically for that account. This worksheet does not update an organisation’s private incident records.
Opening the Five Whys investigation tool…
Investigation methods and worked examples
Explore causes with Fishbone and Five Whys
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.
Fictional scaffold fishbone
Six cause categories with subcauses, evidence checks and actions · 24 pages.