Template

Root cause analysis template (A3 / 5-Why + Action Tracker)

Interactive RCA template that combines A3 structure with a guided 5‑Why sequence and a structured action tracker so teams produce verifiable, measurable fixes and update standard work.

Interactive Tool

Root Cause Analysis (A3 + 5-Why) — Interactive Template

This guided RCA template helps teams capture a clear problem statement with data, run a disciplined 5‑why analysis with supporting evidence, capture immediate containment and longer‑term countermeasures, and track verification tests so fixes become lasting standard work. Use this for field incidents and engineering problems. Save the form to record the RCA and generate actions your team can follow up on.

Use your site or team naming convention (e.g., PLT1-2026-001).
Use YYYY-MM-DD for consistency.
Describe what happened, where, when, and the measurable impact (e.g., 150 rejected parts on Line 3 during shift B). Include numbers and customer impact if known.
Summarize immediate and potential downstream impacts.
List immediate actions to stop further harm or production of bad product and who performed them (owner;time).
For each why, state the answer in plain language and list evidence that supports it (measurements, observations, photos, logs). Do not assume causes — capture facts.
Start with the immediate cause of the problem.
Reference files, photo IDs, equipment logs, test readings, or witness notes.
Ask why the cause in Why 1 happened.
Summarize the team's consensus on the root cause and the key evidence that supports it.
List the types of fixes considered (engineering change, training, visual control, tooling update, inspection, procedure update).
Use the action tracker below to record up to five actions. If you need more, attach a separate action register and reference it in Related documents.
Describe the countermeasure or task.
Use ISO date format for consistency.
State a clear test, measurement, or observation that will prove the action worked.
Fill after verification testing.
After actions are complete, summarize test results and measured change (e.g., defect rate dropped from X to Y).
List KPIs, frequency of checks, dashboards or reports to review.
Include recommended changes to training, inspection points, or procurement.
List the procedure/doc name, owner, and target date for the update.
Reference photo IDs, folder paths, SAP/MES records, or shared drive links.
Person responsible for ensuring follow-through and longer-term monitoring.
If confidence is low, plan further testing before final closure.
State whether the RCA can be closed, requires monitoring, or needs escalation.
Selecting yes will flag this record for the reviewer workflow if configured.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.