Free 5 whys analysis template
Jump to download form ↓Enter your email below to download this 5 whys analysis template as a ready-to-use PDF.
Free 5 Whys template (PDF). State the problem, ask why five times to reach the root cause, then assign countermeasures and verify. Download free.
Commercial Director
Key takeaways
- The 5 Whys is a single-method root cause tool: ask why repeatedly, usually five times, until you reach a cause you can fix rather than a symptom.
- It suits one clear problem with a single causal chain; use a fishbone or full RCA when several independent causes are likely.
- Each answer must be evidence-based, not a guess. A weak link early in the chain leads the whole analysis to the wrong root cause.
- Every confirmed root cause needs a countermeasure with an owner and a due date, then verification that the problem has not recurred.
Updated 4 June 2026
How to use: download the PDF, print or complete digitally on any device.
- PDF format, ready to print or fill on screen
- Use as-is or customise to suit your operation
- Go digital in MapTrack for photos, alerts and audit trails
Download free PDF template
Trusted by teams across Australia and New Zealand
We respect your privacy. Unsubscribe anytime.
Used by construction, mining and field service teams
What is a 5 whys analysis template?
A 5 Whys analysis template is a simple, structured worksheet for finding the root cause of a problem by asking why it happened, then asking why of each answer in turn, typically five times, until the chain reaches a cause that can be acted on rather than another symptom. For each level it captures the question, the evidence-based answer and how that answer was confirmed, ending in a root cause statement and one or more countermeasures with owners and due dates. It deliberately follows a single causal chain, which makes it fast to run and easy to read.
The method came out of the Toyota Production System, where Sakichi Toyoda used repeated why questions to get past the obvious fault to the underlying condition. Maintenance, quality and operations teams in manufacturing, mining and construction use it for breakdowns, defects, near misses and recurring nuisance faults, because it forces the conversation past blame and toward the system that allowed the failure. In MapTrack, a 5 Whys worksheet can be attached to the work order or incident it relates to, so the analysis and its countermeasures stay with the asset history. It is a recognised analytical technique under the corrective action requirements of ISO 9001:2015, clause 10.2.
Learn more about maintenance and work orders in MapTrack.
Benefits of using this 5 whys analysis template
- Fast to run: a small team can complete a focused 5 Whys in minutes, so it suits the daily problems that never justify a full investigation.
- Gets past symptoms: asking why repeatedly moves the team from the visible fault to the system condition that actually needs fixing.
- Reduces blame: the chain points at procedures, controls and design rather than the last person to touch the equipment, which keeps the analysis honest.
- Evidence discipline: recording how each answer was confirmed stops the chain becoming a string of assumptions that lead to the wrong root cause.
- Clear countermeasures: tying the root cause to a named owner and a due date turns the analysis into action rather than a filed form.
- Easy to read: a one-page linear chain is simple for a supervisor or auditor to follow and to challenge, unlike a dense narrative report.
- Feeds bigger tools: a completed 5 Whys plugs straight into a fishbone, an A3 or a formal RCA when the problem turns out to be more complex.
Benefits of digitising forms in MapTrack
When you move your root causes from paper to MapTrack, you get:
- Field users can easily scan a QR code to complete a form on mobile. Unlimited users.
- Automatically get alerts when faults are identified.
- Link every form digitally as a PDF to the relevant asset, location or person.
- Receive a digital PDF copy with every submission to your email.
- Ability to share forms digitally.
- Build conditional logic (show or hide questions based on answers).
- Take pictures or attach photos. Not possible with a paper-based form.
- Electronic signatures.
- Edit forms later without reprinting.
- Restrict permissions (who can view, complete or approve).
- Build forms with AI (describe what you need and MapTrack suggests the form).
- Trigger work orders automatically when a fault is logged during an inspection.
- Track service intervals by hours, kilometres or calendar date in one place.
- Attach supplier invoices and parts receipts to each maintenance record.
Book a demo to see how MapTrack handles root causes.
Try MapTrack free for 30 days
Full access to every feature. No credit card required. Per-asset pricing so you scale as your fleet grows.
- No credit card required
- 30 days free trial
- Cancel anytime
1-2 days/week saved
“Bloody amazing! We used to spend 1-2 days a week tracking and managing our generators alone.”
Steve McAllister
Asset Coordinator, Saunders International
What to include in a 5 whys analysis template
This 5 whys analysis template covers 10 key areas:
- Header details: reference number, problem title, date, facilitator, team members and the work order or incident this analysis relates to.
- Problem statement: a factual, quantified description of what happened, when, where and the impact (downtime hours, units rejected, cost).
- Why 1: the first answer to why the problem occurred, with the evidence that confirms it.
- Why 2: why that first cause occurred, again supported by evidence rather than opinion.
- Why 3: the next level down the causal chain, confirming the link to the level above.
- Why 4: the next answer, checking whether the chain has reached a system or process condition.
- Why 5: the final why, or earlier if a true root cause is reached sooner, or further if it is not.
- Root cause statement: a concise statement of the underlying cause the chain has reached, distinguished from contributing factors.
- Countermeasures: the actions that eliminate the root cause, each with a responsible person and a due date.
- Verification: how and when effectiveness will be checked, and confirmation the problem has not recurred.
How to use this 5 whys analysis template
- Write a clear, factual problem statement before asking any why.: Describe exactly what happened, where, when and the size of the impact, using numbers such as downtime hours or rejected units. A vague problem statement sends the whole chain in the wrong direction, so agree the wording with the team before you start.
- Ask why the problem occurred and record the first answer with its evidence.: Capture the most direct cause of the stated problem and note how you know it is true, for example a meter reading, a photograph or a maintenance record. Resist jumping straight to a favourite theory; the first why should be the immediate, verifiable cause.
- Ask why of that answer, and keep going down the chain.: Treat each answer as a new problem and ask why it happened, confirming each link with evidence. Continue for about five levels, but stop when you reach a cause you can actually control and go further if you have not, since five is a guide and not a rule.
- Test the chain by reading it back from the root cause upward.: Start at the deepest answer and say therefore at each step back up to the problem. If the logic holds in that direction, the chain is sound; if a step does not follow, you have a gap or a missing branch that needs more evidence before you continue.
- State the root cause and write countermeasures that eliminate it.: Phrase the root cause as a system or process condition, not as individual error, then define actions that remove it. Give each countermeasure a named owner and a due date so the analysis converts into work that someone is accountable for completing.
- Verify effectiveness after a set period and close the analysis.: Agree how you will confirm the fix worked, such as no recurrence over the next 30 to 90 days or a measurable drop in the failure, then review it on that date. Record the outcome and sign off, escalating to a fuller RCA if the problem returns.
In MapTrack, you can schedule and track maintenance digitally. Each submission is stored as a timestamped PDF against the asset record.
Get the free templateEnter your email above to download the full 5 whys analysis template as a PDF.Back to download formHow often should you complete this root cause?
Run a 5 Whys whenever a problem is worth understanding but does not warrant a full team investigation: an equipment breakdown, a recurring nuisance fault, a defect, a near miss or a customer complaint. Use it immediately while the evidence and the people involved are still available, because detail is lost within days. Reserve a broader fishbone or formal RCA for high-consequence events or problems with several likely causes. In MapTrack, you can attach the completed worksheet to the related work order, so the root cause and its countermeasures stay visible against that asset the next time it fails.
Frequently asked questions
Applicable regulatory standards
This template aligns with the following regulations and standards:
- ISO 9001:2015, clause 10.2 - Nonconformity and corrective action (root cause analysis as part of corrective action)
- ISO 45001:2018, clause 10.2 - Incident, nonconformity and corrective action (investigation of underlying causes)
- WHS Act 2011, section 19 - Primary duty of care (investigating incidents to prevent recurrence)
Need to schedule and track maintenance digitally?
Register every asset in MapTrack, attach digital forms, and get a complete history of every inspection, service and compliance record.
Maintenance and work orders · All templates · Pricing · Book a demo