Skip to main content

Investigate & improve

Fishbone investigation

Turn possible causes into a visual investigation and a branded report. A company-branded PDF investigation report containing the fishbone diagram and supporting detail.

Bring different perspectives together, test contributing factors against evidence and make improvement actions easier to explain. 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.

Open the tool

What you can take away

A company-branded PDF investigation report containing the fishbone diagram and supporting detail.

  • The event, cause categories, causes and subcauses shown in the map.
  • Evidence, contradictions, open questions and recorded cause reviews.
  • Accountable actions; CSV export is also available for structured data.
View completed example (PDF)

How it helps you at work

Bring different perspectives together, explore several contributing factors and make the reasoning and evidence easier for others to review.

Keep it with your own records

Choose a browser save to retain an account-scoped working copy. Download the branded report for your investigation file; it does not automatically update a private organisation case.

How it works — the theory and its limits

A fishbone diagram groups possible causes around a clearly defined event or problem. Categories help the team search broadly; subcauses let it explore an explanation in more detail.

Test each explanation against supporting and contradictory evidence before recording conclusions. Link improvements to the causes that the investigation supports.

A category, branch or position on the diagram does not prove a cause or approve a finding.

Method and guidance

  1. 1Define the event
  2. 2Build and test the fishbone
  3. 3Review causes and actions
A practical starting pointQuick guide to fishbone analysisSix steps from a clear event to evidence-led improvements.

Map the possibilities. Test what contributed.

Bring together people who know the work. Use the fishbone to explore several explanations, then check them against the facts. A branch is a line of enquiry, not proof of a cause.

Annotated fishbone with six numbered steps: put the event at the head; use the six main bones as enquiry categories; add possible causes; branch into subcauses; test explanations against evidence; and assign, complete and verify actions. A fictional trolley and storage-rack example shows how the parts connect.
How to read the fishbone The numbered parts match the steps below. All example branches are questions to investigate.Open full-size diagram (new tab)
  1. Define the event at the head

    Write one factual sentence describing what happened, where and when. Keep the outcome separate from an assumed explanation: “A trolley struck a storage rack in the loading bay” is a starting point; “the operator was careless” is a conclusion that has not been established.

    In the tool Complete Event or problem to explain, add the investigation details, then choose Start the fishbone.

  2. Choose useful enquiry categories

    The main bones organise the discussion. Start with the tool’s six categories shown in the diagram, or rename them to suit the work. Explore equipment, planning, the workplace and organisational arrangements as well as people. An empty category is a prompt to ask, not a reason to invent a cause.

    In the tool Use Keep category names after editing them, or Add a category when a different line of enquiry is useful.

  3. Add specific possible causes

    Place one explanation on each branch. Ask what could have contributed and record it clearly enough to investigate. “Restricted sightline?” is more useful than “environment”. Invite different perspectives and keep alternative explanations visible; the number or position of branches does not establish their importance.

    In the tool Choose a category, add a cause and select Keep this answer. Use Add parallel cause for another explanation.

  4. Explore what sits behind each cause

    Use the smaller branches to ask what could have allowed the preceding condition to arise. For “restricted sightline?”, ask whether stored pallets obstructed the view and what arrangements governed that storage. Follow each useful pathway without forcing every chain to five questions or calling its final branch a root cause.

    In the tool Select the relevant explanation and choose Add subcause. Diagram and Written inputs offer two ways to work with the same entries.

  5. Test the explanations against evidence

    Record what supports each explanation, its source and date, and anything that challenges it. Compare accounts, observations and relevant records. Identify the next check where evidence is missing. Keep uncertainty visible and record your review reasoning; a plausible idea or an agreed diagram is not a confirmed finding.

    In the tool Complete the evidence and review fields. Classify causes from the evidence, rather than from their category or depth on the diagram.

  6. Agree actions and check they work

    Link improvements to the reviewed explanations. Give each action an owner, a due date, an implementation check and a test of effectiveness. Review whether the change addresses the problem in practice, and carry unresolved questions forward. Share the findings with the people who need to act and learn.

    In the tool Open Review causes & actions to add actions. Choose Save in this browser to keep your working copy. Download the PDF and attach it to your investigation report or incident record.

Ready to build your own?

Start with the event. Keep evidence, uncertainty and action ownership clear as the map develops.

Go to the investigation

Method and further reading: HSE investigation workbook · SHAREknowledge fishbone guide

Before you use this tool

Categories are prompts for enquiry. They do not prove causation, assign cause level or approve a finding. Keep contradictory evidence and uncertainty visible. This local worksheet does not 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 Fishbone investigation tool…

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.

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.

Take the next step

Sources, scope and guidance

Use the current guidance for the work and jurisdiction. Source review: 29 October 2026.