Skip to content
GraviPointThe Centre of Productivity
  • AI AgentNew
  • Pricing
  • Community
Log inGet started free
TemplatesBusiness & StrategyKPIs & PerformanceRoot Cause Analysis

DocumentKPIs & PerformanceFree

Root Cause Analysis

Investigate a problem with 5 Whys and a fishbone diagram, verify the cause and fix it so it stays fixed.

Shown with sample data

Colour

Root Cause Analysis Report

Reference

[RCA-2026-031]

Site / department

[Meridian Foods Distribution Centre, Chilled Picking]

Date opened

[3 November 2026]

RCA lead

[Name, Quality Manager]

Team

[Shift Manager, two senior pickers, WMS administrator, Customer Service Lead]

Status

[Actions in progress]

1. Problem statement

[Between 1 September and 31 October 2026, picking accuracy in the chilled section fell from 99.6% to 98.7%. 412 order lines were mis-picked, mostly wrong product variants (e.g. 500 g instead of 1 kg), leading to 63 customer complaints, $18,400 in credits and two retail customers issuing formal performance notices.]

2. Impact

Area

Impact

Customer

[63 complaints; 2 formal notices from top-10 customers]

Financial

[$18,400 credits plus $6,100 re-delivery cost]

Operational

[Return handling and re-picks: about 90 labour hours]

Safety / compliance

[None identified; no allergen substitutions]

3. Containment

Action

Owner

Date

Status

[100% check of chilled orders for top-10 customers before dispatch]

[Shift Manager]

[3 Nov]

[In place]

[Separated look-alike variants onto different aisles as a temporary measure]

[Warehouse Lead]

[4 Nov]

[Done]

4. Data gathered

  • [Errors by product: 71% involve 18 SKUs that come in two or more pack sizes with near-identical packaging]

  • [Errors by shift: night shift 2.1× the day-shift error rate]

  • [Errors by picker tenure: pickers with under 3 months’ service made 64% of errors]

  • [Slotting change on 28 August moved variants of the same product into adjacent locations to save travel time]

  • [Scanners on night shift: 6 of 20 handhelds had faulty triggers; pickers keyed location codes manually]

5. Fishbone (Ishikawa) analysis

Category

Possible causes identified

Likely?

People

[High share of new pickers after summer hiring; shortened induction (2 days instead of 4)]

[Yes]

Methods

[Pick confirmation by location scan only, not product barcode; slotting places variants side by side]

[Yes]

Machines

[Faulty scanner triggers on night shift lead to manual key entry]

[Yes]

Materials

[Supplier packaging for 500 g and 1 kg variants differs only in a small weight label]

[Yes]

Measurement

[Accuracy report produced monthly, so the trend was spotted 6 weeks late]

[Contributing]

Environment

[Lower lighting levels in two chilled aisles; pickers wear gloves, making labels harder to handle]

[Possible]

6. 5 Whys

Cause chain 1: wrong variant picked

  1. Why were wrong variants sent? [Pickers picked from the adjacent location holding the other pack size.]

  2. Why was the error not caught at picking? [The system confirms the location barcode, not the product barcode.]

  3. Why does it only confirm the location? [Product-barcode confirmation was switched off in 2024 to speed up picking.]

  4. Why was it switched off without other controls? [The change was judged low-risk because variants were then stored in separate aisles.]

  5. Why did the risk come back? [The August slotting change put variants side by side, and slotting changes are not risk-assessed against pick controls.]

Root cause 1: [Slotting changes are made without a check against error-proofing controls, so a change that saved travel time removed the separation that compensated for location-only scanning.]

Cause chain 2: higher error rate on night shift

  1. Why is the night-shift error rate higher? [More manual key entry of location codes.]

  2. Why more manual entry? [Six scanners have faulty triggers.]

  3. Why were they not repaired? [Faults are reported verbally and not logged; no spare pool on nights.]

Root cause 2: [No equipment fault-reporting process or spare scanner pool for night shift.]

7. Verification of root causes

Root cause

Test

Result

Confirmed?

[Slotting without control check]

[Compared error rate for variant SKUs before and after 28 Aug]

[0.3% before, 2.6% after]

[Yes]

[Scanner faults]

[Error rate on lines picked with manual entry vs scanned]

[3.9% vs 0.8%]

[Yes]

[Shortened induction]

[Error rate of new pickers with 2-day vs 4-day induction]

[Small difference once slotting controlled for]

[Contributing only]

8. Corrective and preventive actions

#

Action

Type

Root cause

Owner

Due

Status

1

[Turn on product-barcode confirmation for all multi-variant SKUs]

[Corrective]

[1]

[WMS Administrator]

[15 Nov 2026]

[Done]

2

[Re-slot variants at least one bay apart]

[Corrective]

[1]

[Warehouse Lead]

[22 Nov 2026]

[In progress]

3

[Add pick-control risk check to the slotting change procedure]

[Preventive]

[1]

[Operations Manager]

[30 Nov 2026]

[Open]

4

[Equipment fault log on every shift; 4 spare scanners on nights]

[Corrective]

[2]

[Shift Manager]

[20 Nov 2026]

[In progress]

5

[Ask supplier to add colour-coded pack-size bands]

[Preventive]

[Materials]

[Procurement]

[31 Jan 2027]

[Open]

6

[Restore 4-day induction with a variant-picking module]

[Preventive]

[People]

[Training Coordinator]

[1 Dec 2026]

[Open]

7

[Weekly accuracy report by zone and shift]

[Preventive]

[Measurement]

[Quality Manager]

[15 Nov 2026]

[Done]

8

[Apply the same review to the ambient and frozen sections]

[Preventive]

[1, 2]

[Operations Manager]

[31 Dec 2026]

[Open]

9. Effectiveness check

Measure

Baseline

Target

Check date

Result

[Chilled picking accuracy]

[98.7%]

[99.6% or better for 8 consecutive weeks]

[31 Jan 2027]

[ ]

[Customer complaints for wrong variant]

[32 a month]

[Under 3 a month]

[31 Jan 2027]

[ ]

[Lines picked with manual key entry]

[9%]

[Under 1%]

[15 Dec 2026]

[ ]

10. Lessons learned

  • [Any change to layout or slotting must be checked against the controls that depend on it.]

  • [Weekly measurement would have caught the trend within two weeks instead of six.]

11. Sign-off

Role

Name

Date

RCA lead

[Name]

[Date]

Operations Manager

[Name]

[Date]

Closed by (after effectiveness check)

[Name]

[Date]

Text in [brackets] is yours to replace.

  • About
  • What’s included
  • How to use
  • Questions
  • Related resources

About this template

Fixing symptoms means the same problem comes back next month. This root cause analysis template takes a team from a clear problem statement through containment, a fishbone (Ishikawa) review of every cause category and a 5 Whys chain, to a verified root cause, corrective and preventive actions, and an effectiveness check, worked through for picking errors at a fictional food distribution centre.

Who it’s for

  • Quality defects and customer complaints
  • Safety incidents and near misses
  • Recurring operational failures
  • Corrective and preventive action (CAPA) records for audits

What’s included

  • 1. Problem statement
  • 2. Impact
  • 3. Containment
  • 4. Data gathered
  • 5. Fishbone (Ishikawa) analysis
  • 6. 5 Whys
  • 7. Verification of root causes
  • 8. Corrective and preventive actions
  • 9. Effectiveness check
  • 10. Lessons learned

How to use it

  1. 1Write a specific problem statement: what, where, when, how big, and the impact, without blaming or guessing the cause.
  2. 2Record the containment action taken to protect customers while you investigate.
  3. 3Brainstorm possible causes in each fishbone category with the people who do the work.
  4. 4Take the most likely causes through 5 Whys until you reach something you can control, then verify it with data.
  5. 5Agree corrective and preventive actions with owners and dates, and check effectiveness after 30 to 90 days.

Tips

  • Stop asking why when you reach a cause you can act on and that, if removed, would prevent recurrence. That may be three whys or seven.
  • If your root cause is "human error" or "operator did not follow the procedure", keep going: ask why the system made the error easy to make.
  • Verify before you fix. Test the suspected cause against data (when it happens, where, to whom) so you do not spend money on the wrong solution.

Questions

What is the difference between 5 Whys and a fishbone diagram?

A fishbone diagram widens the search by listing possible causes across categories (people, methods, machines, materials, measurement, environment). 5 Whys deepens it by following one cause chain down to the root. Use the fishbone first, then 5 Whys on the likeliest causes.

Can a problem have more than one root cause?

Yes. Complex failures often have two or three contributing root causes. Record each and give each its own action.

What is the difference between corrective and preventive action?

Corrective action removes the cause of a problem that has happened. Preventive action removes the cause of a potential problem elsewhere, such as applying the same fix to other sites or products.

How do I know the fix worked?

Define the measure and the target before you implement, then check it after enough time has passed for the problem to recur, usually 30 to 90 days.

Related searchesroot cause analysis templaterca template5 whys templatefishbone diagramishikawa diagramcorrective actioncapa

Details

Format
Document
Category
KPIs & Performance
Setup
60 min
Level
Intermediate
Price
Free

Download a copy

Downloads need a free account.

DocumentKPIs & PerformanceFree

Root Cause Analysis

Investigate a problem with 5 Whys and a fishbone diagram, verify the cause and fix it so it stays fixed.

A free account keeps your copy safe so you can come back to it. Have one? Log in

Download a copy

Downloads need a free account.

Details

Format
Document
Category
KPIs & Performance
Setup
60 min
Level
Intermediate
Price
Free

Your copy is private to you.

More kpis & performance templates

View all
OKR Tracker3 sheets

Overall progress

49%

Quarter elapsed

53%

On track or achieved

7

Progress by objective
54%
53%
39%
Delight new customersBuild a great teamGrow efficiently
SpreadsheetKPIs & Performance

OKR Tracker

Objectives and key results with progress from start to target, pace against the quarter, confidence and an objective roll-up.

10 min setupPreview
KPI Scorecard2 sheets

On target

6

Amber

5

Red

1

Achievement by KPI
125%
125%
119%
107%
105%
Support first response (hrs)Employee turnover (%)Churn rate (%)New customersRevenue ($k)
SpreadsheetKPIs & Performance

KPI Scorecard

Business KPIs against target with achievement, red-amber-green status, change since last period and a perspective summary.

10 min setupPreview
Balanced Scorecard2 sheets

On track

4

At risk

2

Off track

2

Entries by category
2
2
2
2
FinancialCustomerInternal processLearning and growth
SpreadsheetKPIs & Performance

Balanced Scorecard

Objectives, measures, targets and actuals across financial, customer, process and learning perspectives.

10 min setupPreview

Practical guides and new resources, monthly.

One short email with new templates, calculators and how-tos. Unsubscribe any time.

GraviPointThe Centre of Productivity

Find the right resource. Make it work for you. Get things done with spreadsheets, documents, forms and calculators you can use right in your browser.

support@gravipoint.com
  • @gravipoint
  • @GraviPoint
  • GraviPoint
  • 𝕏@gravipoint

Templates

  • All templates
  • Budgets & expenses
  • Invoices & billing
  • Project management
  • HR & people
  • Inventory & stock
  • Sales & CRM
  • Financial calculators

Popular

  • Monthly budget
  • Invoice
  • Employee shift schedule
  • Weekly timesheet
  • Project plan & Gantt chart
  • Inventory tracker
  • Expense report
  • Mortgage calculator

Solutions

  • Individuals & households
  • Freelancers & consultants
  • Founders & startups
  • Small business owners
  • Teams & operations
  • Students & educators

Company

  • About
  • Features
  • Pricing
  • Community
  • Journal
  • Contact
© 2026 GraviPoint. All rights reserved.
  • Privacy
  • Terms
  • Help centre
  • FAQ