CORAA
University · Root cause analysis

Fishbone Diagram Generator.

Type the problem and list possible causes under six common categories. The fishbone (Ishikawa) diagram draws itself. Download it as SVG or PNG for your working paper or report. It runs in your browser and nothing is uploaded.

Up to six causes per category are drawn. Long causes are shortened on the diagram.

Duplicate paymentsto vendorsPeopleNew clerk not trainedApprover on leaveProcessNo check before payment runManual invoice entrySystemsERP allows duplicate invoice …Policy and controlsNo duplicate payment reportApproval limit too highDataVendor master has two entries…ExternalVendor sent the same invoice …

From diagram to root cause.

A fishbone diagram lays out possible causes so none is forgotten. It does not prove which cause is real. After drawing it, test each cause against evidence, keep the ones that hold, and ask why again until you reach a cause the organisation can change. Then record the corrective action and check that it worked.

Root cause analysis template (Word)CAPA report format

How a fishbone diagram works

A fishbone diagram, also called an Ishikawa or cause-and-effect diagram, puts the problem at the head of a fish and groups possible causes on bones that branch from the spine. Grouping causes into categories helps a team look beyond the obvious one. Common categories are people, process, systems, policy and controls, data and external factors, and you can rename them to suit your problem.

In audit, the fishbone is a way to organise the "why" behind a finding. It is most useful when several causes could combine, such as duplicate payments that arise from both a system gap and a missing control.

This tool draws the diagram from what you type. Everything stays in your browser. Download the picture for your working paper, then test each possible cause against evidence.

Worked example — duplicate payments

An internal audit finds the same vendor invoice paid twice. The team lists causes under each category.

Inputs
ProblemDuplicate payments to vendors
SystemsERP allows duplicate invoice numbers
Policy and controlsNo duplicate payment report
Output
Confirmed causes after testingSystem allows duplicate numbers; no duplicate check before payment
Corrective actionsBlock duplicate invoice numbers per vendor; run a duplicate report before each payment run
The diagram surfaced six possible causes. Testing showed two were real. The actions fix those two and the team checks the next three payment runs to confirm the fix worked.

Common mistakes

Treating the diagram as the answer
It lists possible causes. Each one still needs evidence before it counts.
Stopping at "human error"
Ask what in the process or controls allowed the error to happen and go unnoticed.
Too many causes, no priority
After drawing, pick the few causes supported by evidence and act on those first.

Frequently asked questions

What is a fishbone diagram used for?+
To organise the possible causes of a problem into categories so a team can examine them systematically and find the real root cause.
What are the usual fishbone categories?+
Many teams use people, process, systems, policy and controls, data and external factors. In manufacturing the "6 Ms" are common. You can use categories that fit your problem.
Is my data uploaded?+
No. The diagram is drawn in your browser and nothing is sent to a server.
Can I edit the diagram after downloading?+
The SVG opens in most drawing and presentation tools, where you can edit text and shapes.

Authoritative sources

ASQ — Fishbone (cause-and-effect) diagram — Background on the technique, which is attributed to Kaoru Ishikawa.
Always confirm against the latest version of the source. Regulations evolve and amendments are common.
Related calculators
Root cause analysis template (Word) →CAPA report format (Word) →Observation report generator →Issue rating matrix →
Share this tool
Last reviewed: 2026-10-17 · For informational purposes only — not professional advice.