Skip to main content
MapTrack
Book a demo
Skip to download form

Free root cause analysis template

Free root cause analysis template (PDF). 5 Whys, fishbone diagrams, contributing factors, corrective actions and verification.

Updated 28 Sept 2026

Root Cause Analysis Template

Your logo here
0 of 5 rows started
#NamePosition / RoleDepartment
e.g.---
1
2
3
4
5

The PDF includes all 4 numbered rows, ready to print or fill on screen.

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, reminders and audit trails

Two ways to use it

Use in MapTrack →

Download the free PDF

Use it digitally instead

Unlimited users

These same 3 columns, already built.

G2 rating 4.9 out of 5
Capterra rating 5.0 out of 5GetApp rating 5.0 out of 5Software Advice rating 5.0 out of 5
All MapTrack reviews
  • Scan the asset’s QR tag with any phone
  • Submitted forms can trigger alerts
  • Photos on fails, audit-ready records
  • Export responses, PDF reports with your logo

Free trial. No credit card needed.

Trusted by teams across Australia and New Zealand

We respect your privacy. Unsubscribe anytime.

These templates are free general guides provided as-is. They do not constitute legal, safety or compliance advice. You are responsible for ensuring any form meets your specific workplace obligations, industry standards and applicable regulations.

Don't just download it - use it live. Start a free workspace with this root cause analysis template already built, so your crew can run it from a phone.

Jarrod Milford

Jarrod Milford

Co-Founder & Commercial Director

Updated 28 September 2026
Also see:Compliance and inspections →Best inspection software →MapTrack vs SafetyCulture →

Short answer

A root cause analysis template records the problem, evidence, analysis method such as 5 Whys or a fishbone, the root and contributing causes, corrective actions and a check that they worked. Teams run one after significant incidents, failures or nonconformities, not on a schedule. ISO 9001:2026 clause 10.2 covers nonconformity and corrective action, and ISO 45001:2018 clause 10.2 covers incidents.

Checked against ISO 9001:2026 (Edition 6, published 16 September 2026) on by the MapTrack templates team. How we check templates

Key takeaways

  • The MapTrack root cause analysis template has 3 columns and room for 4 entries. Columns: Name, Position / Role, Department.
  • ISO 9001:2026 clause 10.2 covers acting on nonconformities, eliminating their causes and checking the corrective action worked.
  • The model WHS Act sets no express duty to investigate; regulation 38 requires controls to be reviewed when they fail.
  • Investigation timeframes such as within days or within two weeks are internal practice, not legal deadlines.
  • Collect evidence before analysis, then separate the root cause from contributing factors.
  • Track each corrective action to closure and verify it worked before closing the RCA.

Enter your email below to download this root cause analysis template as a ready-to-use PDF.

Used by construction, mining and field service teams

Saunders InternationalMineral ResourcesSupagasHacer GroupMetro TunnelUltrabuilt

What is a root cause analysis template?

A root cause analysis (RCA) template is a structured document used to systematically investigate an incident, failure, non-conformance or undesirable outcome to identify its underlying cause rather than just its symptoms. It guides investigators through defining the problem, collecting evidence, analysing contributing factors using structured methodologies (5 Whys, fishbone diagrams, fault tree analysis), identifying the root cause, developing corrective actions and verifying their effectiveness. The template provides a repeatable framework that ensures investigations are thorough, objective, evidence-based and documented.

Root cause analysis is used across every industry where understanding why something went wrong is essential for preventing recurrence. In manufacturing, it investigates product defects and process failures. In healthcare, it analyses adverse events and near misses. In construction and mining, it examines safety incidents and equipment failures. In quality management systems such as ISO 9001, it forms the investigation component of the corrective action process. Without a structured RCA approach, organisations tend to address only the visible symptoms of problems, implementing quick fixes that leave the underlying cause untouched. This results in recurring failures, repeated incidents, wasted resources and a gradual erosion of confidence in the organisation ability to manage quality and safety.

Learn more about compliance and inspections in MapTrack.

Get the free template

Enter your email above to download the full root cause analysis template as a PDF.

Download free PDF

Benefits of using this root cause analysis template

  • Recurrence prevention: identifying and addressing the true root cause eliminates the underlying condition that caused the problem, rather than just treating symptoms.
  • Structured investigation: the template provides a step-by-step framework that ensures investigators follow a logical, evidence-based process rather than jumping to conclusions.
  • Consistent documentation: a standardised template ensures every investigation is documented with the same level of rigour, making it easier to compare, review and learn from past investigations.
  • Compliance support: a documented RCA process satisfies the investigation requirements of ISO 9001:2026 clause 10.2, WHS legislation, industry regulations and customer quality requirements.
  • Knowledge capture: completed RCA documents capture organisational knowledge about failure modes, contributing factors and effective countermeasures that can be referenced for future investigations.
  • Accountability: clear assignment of corrective actions to named individuals with due dates and effectiveness verification ensures that investigation findings translate into actual improvements.

Benefits of digitising forms in MapTrack

When you move your reports from paper to MapTrack, you get:

  • Field users can easily scan a QR code to complete a form on mobile. Unlimited users.
  • Email the right people when a form is submitted, with an automation you set up.
  • File every completed form against the asset, location or person it covers.
  • Download any completed form as a PDF, with failed answers listed at the top.
  • Fill in forms offline; they upload when the device is back online.
  • 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.
  • Set who can view, fill in or edit forms with user roles.
  • Upload a paper form (PDF, Word, Excel or a photo) and MapTrack's AI builds a digital version for you to check.
  • Assign audits and send reminder emails to the people doing them.
  • Keep every audit, inspection and sign-off against the asset or site it covers.
  • Track corrective actions as work orders from finding to close-out, with each change in the activity log.

Book a demo to see how MapTrack handles reports.

Try MapTrack free

Full access to every feature. No credit card required. Per-asset pricing so you scale as your fleet grows.

Start free trial
  • No credit card required

1-2 days/week saved

“Bloody amazing! We used to spend 1-2 days a week tracking and managing our generators alone.”
Saunders International

Steve McAllister

Asset Coordinator, Saunders International

What to include in a root cause analysis template

This root cause analysis template covers 8 key areas:

  • Investigation header: unique RCA reference number, investigation title, date of event, date investigation initiated, lead investigator name, investigation team members and investigation status (open, in progress, awaiting verification, closed).
  • Problem statement: clear, factual description of what happened, when it happened, where it happened, who was affected, the magnitude or severity of the impact and the immediate consequences.
  • Evidence collection: list of evidence gathered during the investigation, including photographs, measurements, process records, equipment logs, maintenance records, training records, witness statements and environmental data.
  • Timeline reconstruction: chronological sequence of events leading up to, during and after the incident, with times, actions, decisions and conditions recorded to establish the chain of events.
  • 5 Whys analysis: iterative questioning starting from the problem statement, asking "why" at each level until the root cause is reached (typically five to seven iterations, though the actual number depends on the complexity).
  • Fishbone (Ishikawa) diagram: categorised analysis of contributing factors across people, process, equipment, materials, environment and management system categories.
  • Root cause statement: concise statement of the identified root cause, supported by evidence from the investigation, distinguishing the root cause from contributing factors.
  • Corrective action plan: specific actions to eliminate the root cause, responsible person for each action, due dates, resources required, changes to procedures or controls, and effectiveness verification method and date.

How to use this root cause analysis template

  1. Define the problem clearly, assemble the investigation team and collect all available evidence before beginning the analysis.: Write a clear, factual problem statement that describes what happened, when, where, who was affected and the severity of the impact. Avoid assumptions, opinions or premature conclusions. Assemble an investigation team that includes people with knowledge of the process, equipment or system involved. Collect all available evidence including photographs, process data, equipment logs, maintenance records, training records and witness statements. Preserve physical evidence where relevant.
  2. Reconstruct the timeline of events and identify the sequence of actions, decisions and conditions that led to the incident.: Map out the chronological sequence of events from normal operating conditions through to the incident and its immediate aftermath. Include times, actions taken by each person, decisions made, equipment states, environmental conditions and any deviations from normal procedures. Identify the points where the sequence diverged from the expected or planned path. The timeline often reveals contributing factors that are not immediately obvious from the problem statement alone.
  3. Apply structured analysis methods (5 Whys, fishbone diagram or both) to identify contributing factors and drill down to the root cause.: Start the 5 Whys analysis from the problem statement and ask "why" at each level, following the chain of causation until you reach a cause that can be directly addressed. If multiple causal chains exist, follow each one. Use a fishbone diagram to categorise contributing factors across people, process, equipment, materials, environment and management system categories. The root cause is typically a systemic issue such as an inadequate procedure, missing control, insufficient training, design flaw or management system gap, rather than individual human error.
  4. Document the root cause statement, distinguishing it from contributing factors, and develop corrective actions that specifically address the root cause.: Write a concise root cause statement that is supported by the evidence collected during the investigation. Contributing factors that increased the likelihood or severity of the incident should be documented separately but also addressed. Develop corrective actions that specifically eliminate the root cause, not just the symptoms. For each action, define what will be done, who is responsible, the due date, the resources required and any changes to procedures, training, equipment or controls.
  5. Implement corrective actions, verify their effectiveness after an appropriate period and close the investigation with lessons learned documented.: Implement each corrective action by the assigned due date and record the completion evidence. After an appropriate verification period (typically 30 to 90 days), assess whether the corrective action has been effective by reviewing whether the problem has recurred, whether similar issues have been prevented and whether the intended improvement is sustained. Document lessons learned and share them with relevant teams. Close the investigation with sign-off from the lead investigator and the accountable manager.

In MapTrack, you can automate compliance tracking and audit trails. Each submission is stored as a timestamped PDF against the asset record.

Get the free templateEnter your email above to download the full root cause analysis template as a PDF.Back to download form

How often should you complete this report?

Root cause analysis is conducted in response to specific events rather than on a fixed schedule. Every significant non-conformance, safety incident, near miss, equipment failure, customer complaint or quality escape should trigger an RCA investigation. The depth and rigour of the investigation should be proportional to the severity and potential consequences of the event. Critical incidents (injuries, regulatory breaches, major quality failures) warrant a full team-based RCA within days. Major non-conformances should be investigated within two weeks. Minor issues may be investigated using a simplified 5 Whys approach.

Organisations should review their RCA register at least monthly to monitor open investigations, track corrective action completion and identify recurring themes. Quarterly management reviews should include a summary of RCA findings, trends and systemic issues identified. An annual review of the RCA programme itself, assessing investigation quality, timeliness and effectiveness of corrective actions, helps drive continuous improvement of the investigation process.

Try MapTrack free

Full access to every feature. No credit card required. Per-asset pricing so you scale as your fleet grows.

Start free trial
  • No credit card required

Frequently asked questions

A root cause is the fundamental underlying condition or systemic failure that, if eliminated, would prevent the incident from recurring. A contributing factor is a condition that increased the likelihood or severity of the incident but did not directly cause it on its own. For example, if a machine failed because a bearing was not replaced at the scheduled interval, the root cause might be an inadequate maintenance scheduling system that failed to generate the work order. Contributing factors might include high workload that discouraged proactive maintenance and a parts inventory system that did not stock the replacement bearing.

ISO 9001 clause 10.2 covers nonconformity and corrective action, and the standard defines corrective action as action to eliminate the cause of a nonconformity and to prevent recurrence. Root cause analysis is the investigation methodology that fulfils this requirement. A structured RCA template provides the documented evidence that these requirements have been met, which is reviewed during internal and external certification audits.

A formal team-based RCA should be conducted for every significant incident, including safety injuries, regulatory breaches, major quality failures, significant equipment failures and serious customer complaints. Near misses with high potential consequences also warrant formal investigation. The depth of investigation should be proportional to the actual and potential severity of the event. Minor non-conformances may be investigated using a simplified 5 Whys approach by the process owner, while critical incidents require a dedicated investigation team with a structured methodology.

The 5 Whys method is a linear questioning technique that follows a single chain of causation by repeatedly asking "why" until the root cause is reached. It works well for straightforward problems with a clear causal chain. A fishbone (Ishikawa) diagram is a visual tool that categorises potential contributing factors across multiple categories (people, process, equipment, materials, environment, management) simultaneously. It works well for complex problems with multiple contributing factors. Many investigators use both methods together, starting with a fishbone diagram to map all potential factors and then applying 5 Whys to drill down on the most significant causal chains.

Yes. Download and use this root cause analysis template at no cost. It downloads as a ready-to-print PDF. No MapTrack account is required. If you want digital RCA investigations on mobile with photo evidence, corrective action assignment, effectiveness verification tracking and incident trend dashboards, MapTrack can do that. Book a demo to see how it works.

Describe what happened, when and where it happened, who was affected, and the magnitude or severity of the impact, in clear and factual terms. Leave out assumptions, opinions and early conclusions about the cause, because the analysis is meant to find the cause from the evidence. The statement matters because the 5 Whys starts from it, and the timeline and evidence collection are all measured against it.

Once enough time has passed to show whether the fix is working, which depends on how often the problem used to occur. A fault that happened weekly can be judged sooner than one that happened once a year. Look for evidence that each action was fully implemented and that the problem has not recurred, check whether similar issues have been prevented, and confirm the improvement has lasted. Record the completion evidence for each action and the lessons learned, then close the investigation with sign-off from the lead investigator and the accountable manager.

People with knowledge of the process, equipment or system involved, led by a named lead investigator. The depth of the investigation should match the severity of the event: critical incidents such as injuries, regulatory breaches or major quality failures warrant a full team-based analysis within days, while minor issues can be investigated by the process owner using a simplified 5 Whys approach.

Applicable regulatory standards

This template is a starting point. Check the current requirements that apply to your equipment, work and location. The template alone does not establish compliance.

  • Quality management systems - Requirements

    Edition: ISO 9001:2026 (Edition 6, published 16 September 2026)

    Nonconformity and corrective action: eliminating causes and reviewing whether corrective action worked.

    • 10.2: Nonconformity and corrective action.

    International Organization for Standardization (ISO)Sold by the publisher

  • Occupational health and safety management systems - Requirements with guidance for use

    Edition: ISO 45001:2018 (Edition 1) with Amd 1:2024 (climate action changes)

    Incident, nonconformity and corrective action in an OH&S management system, including investigating causes.

    • 10.2: Incident, nonconformity and corrective action, including investigation of causes.

    International Organization for Standardization (ISO)Sold by the publisher

  • Model Work Health and Safety Regulations

    Edition: Model WHS Regulations as at 5 December 2025 (cited within as the Work Health and Safety Regulations 2011)

    Controls must be reviewed when they fail to control a risk. The model WHS laws set no express duty to investigate.

    • reg 38: Control measures must be reviewed and revised as necessary, including when they fail, before changes creating new risks, for new hazards, after consultation, or on a qualifying representative's request.
    • Part 3.1: Managing risks to health and safety: identify hazards, eliminate or minimise risks using the hierarchy of controls, maintain and review controls.

    Safe Work Australia (drafted by the Parliamentary Counsel's Committee)

  • Model Work Health and Safety Act (Model Work Health and Safety Bill)

    Edition: Model WHS Bill as at 5 December 2025 (includes the Model WHS Legislation Amendment (Incident Notification) 2025)

    Notifiable incidents go to the regulator immediately, with a record kept for at least 5 years.

    • s 38: A PCBU must notify the regulator immediately after becoming aware of a notifiable incident, by the fastest possible means, by telephone or in writing.
    • s 38(7): A PCBU must keep a record of each notifiable incident for at least 5 years from the day notice of it was given to the regulator.

    Safe Work Australia (drafted by the Parliamentary Counsel's Committee)

  • Quality management systems - Requirements

    Edition: AS/NZS ISO 9001:2026

    Australian and New Zealand identical adoption of ISO 9001:2026.

    Standards Australia and Standards New ZealandSold by the publisher

Each source was read at its publisher and the page checked on 26 October 2026. The publisher's current text is the authority.

Check the current source

Root cause analysis template preview

Root cause analysis template template preview showing fields and layout

The numbers behind this root cause analysis template

The pages below gather the figures behind this kind of check. Each figure on them carries its source and date, so you can quote it in a toolbox talk, a budget case or a board paper without chasing the original report.

Get the free template

Enter your email above to download the full root cause analysis template as a PDF.

Download free PDF

Embed this free template on your website

Run an industry blog, trade association site, or training resource? Drop a preview of this free root cause analysis template straight into your page. The snippet is self-contained, needs no scripts, and links readers back to the full free template.

<div style="max-width:480px;font-family:system-ui,-apple-system,'Segoe UI',Roboto,sans-serif;border:1px solid #E5E7EB;border-radius:12px;padding:20px;background:#ffffff;">
  <p style="font-size:12px;font-weight:700;letter-spacing:0.05em;text-transform:uppercase;color:#071D49;margin:0;">Free template</p>
  <p style="font-size:18px;font-weight:700;color:#071D49;margin:6px 0 0;">Root cause analysis template</p>
  <ul style="margin:12px 0 0;padding-left:18px;color:#374151;font-size:14px;line-height:1.6;">
    <li style="margin:4px 0;">Investigation header: unique RCA reference number, investigation title, date of event, date investigation initiated, lead investigator name, investigation team members and investigation status (open, in progress, awaiting verification, closed).</li>
    <li style="margin:4px 0;">Problem statement: clear, factual description of what happened, when it happened, where it happened, who was affected, the magnitude or severity of the impact and the immediate consequences.</li>
    <li style="margin:4px 0;">Evidence collection: list of evidence gathered during the investigation, including photographs, measurements, process records, equipment logs, maintenance records, training records, witness statements and environmental data.</li>
    <li style="margin:4px 0;">Timeline reconstruction: chronological sequence of events leading up to, during and after the incident, with times, actions, decisions and conditions recorded to establish the chain of events.</li>
    <li style="margin:4px 0;">5 Whys analysis: iterative questioning starting from the problem statement, asking &quot;why&quot; at each level until the root cause is reached (typically five to seven iterations, though the actual number depends on the complexity).</li>
    <li style="margin:4px 0;">Fishbone (Ishikawa) diagram: categorised analysis of contributing factors across people, process, equipment, materials, environment and management system categories.</li>
  </ul>
  <p style="font-size:13px;color:#6B7280;margin:14px 0 0;padding-top:12px;border-top:1px solid #E5E7EB;">Free <a href="https://www.maptrack.com/templates/root-cause-analysis-template" style="color:#071D49;font-weight:600;text-decoration:none;">Root cause analysis template</a> by MapTrack</p>
</div>

Free to reuse, including commercially. This template is published under a Creative Commons Attribution 4.0 licence. Copy it, adapt it, put it on your own site or in your own docs. All we ask is that you credit MapTrack with a link back to this page. The snippet above already includes that credit, so if you use it as-is you’re covered.

Cite this template

Writing about this topic? You’re welcome to quote this checklist. Here’s the wording to use so your readers can find the original.

The MapTrack root cause analysis template has 3 columns and room for 4 entries.

Short attribution
MapTrack Root cause analysis template, https://www.maptrack.com/templates/root-cause-analysis-template
Reference list
MapTrack. (2026). Root cause analysis template [Checklist template]. Retrieved from https://www.maptrack.com/templates/root-cause-analysis-template

Free to reuse with credit under a Creative Commons Attribution 4.0 licence. If you’d rather link straight to it, the page is https://www.maptrack.com/templates/root-cause-analysis-template.

Need to automate compliance tracking and audit trails?

Register every asset in MapTrack, attach digital forms, and get a complete history of every inspection, service and compliance record.

Start free trialBook a demo

Compliance and inspections · All templates · Pricing · Book a demo