Root Cause Analysis: Steps, Tools & Factory Example

6 min read

By

TranZact Solutions Team

· Published

Hero Background
Functions of ERP System Explained

Root cause analysis (RCA) is a step-by-step way to find the real reason a problem happened. You fix it once instead of fighting the same symptom again. In a factory, you first define the problem and collect the facts: which batch, machine, shift and supplier. Then you list the possible causes and test them until you find one you can change. Finally, you fix it and check the problem does not come back. The most common tools are the 5 Whys, the fishbone (Ishikawa) diagram and the Pareto chart.

What is root cause analysis?

A root cause is the reason behind a problem that, once fixed, stops it from coming back. RCA separates three things that often get mixed up:

  • Symptom: the packing line keeps stopping.

  • Trigger: cartons jam at the feeder.

  • Root cause: the carton guide is set wrong at every changeover, and no one checks it.

Clearing the jam fixes today. Adding a changeover check fixes every day after.

A problem can have more than one root cause. If two causes both had to be present, fix both.

When should a factory do an RCA?

Do an RCA when a problem costs you money or keeps repeating. Common triggers for a manufacturer:

Causes fall into three groups. Physical causes sit in machines and material. Human causes come from a step done differently. Organisational causes are missing rules, checks or training, and these are often the real root.

How to do root cause analysis in 5 steps

Step 1: Write down the problem

Write one or two lines: what went wrong, where, when and how much. "Customer rejected cracked housings from Tuesday's dispatch" is clear. "Quality is poor" is not.

Step 2: Collect the facts

Pull the records before anyone guesses. You need the batch or lot number, the supplier's GRN, the work order, machine, shift and inspection result. A clear GRN format and batch tracking make this quick.

Then ask one question: what changed? A new supplier, operator, die or machine setting is often where the answer sits.

Step 3: List every possible cause

Get the people closest to the problem together. List every cause they can think of before deciding on any. A fishbone diagram helps here.

Step 4: Find the root cause you can change

Test each cause against the facts from Step 2. Keep asking why until you reach something you can change, like a rule, a check or a setting. Don't stop at "operator error". Ask why the process let the error happen.

Step 5: Fix it, then check it doesn't come back

Write the fix with one owner and a date. Set a recheck date and look at the next few batches. If the problem returns, the root cause was wrong, so go back to Step 3.

Why RCA fails without good records

Step 2 is where most RCAs break. When GRNs, batch numbers and work orders sit across paper, Excel and Tally, facts go missing. RCA becomes guesswork.

Finding RCA facts: patchwork vs one system


Paper, Excel and Tally

TranZact

Supplier lot behind a batch

Search GRN files by hand

GRN and batch tracking

Work order and route

Ask the supervisor

Work orders and process routing

Current stock of the material

Count it on the floor

Stock tracking and bin card

Purchase history with a supplier

Dig through emails and files

Indent, RFQ, PO and GRN

Where TranZact helps a manufacturer with RCA

Software does not do the root cause analysis for you. Your team does. TranZact has no RCA, 5 Whys, fishbone, CAPA or 8D tool.

What TranZact does is keep the records RCA depends on in one place, including production costing. The Grow plan includes 65+ reports. Batch-wise stock tracking starts on Scale+.

Batch Tracking & QC and machine planning are on Dominate. Check each plan on our pricing page.

If your shop floor still writes in registers, TranZact's AI reads a photo of a paper entry and turns it into a system entry. Accounting stays in Tally, with one-way sync and no double entry.

TranZact is manufacturing AI software used by 10,000+ manufacturers, and it goes live in 2–3 weeks. Comparing options? Our quality control software buying guide lists what to check.

Book a demo →

RCA tools explained simply

5 Whys (not always exactly five)

Ask "why?" and answer from facts. Then ask why again about that answer. Stop when you reach a cause you can fix. Sometimes three whys are enough, and sometimes it takes more than five.

Fishbone diagram

Write the problem as the fish's head. Each bone is an area where causes may sit: machine, method, material, people, measurement and environment. Listing causes under each bone stops the team from chasing only the first idea.

Pareto chart

Count your rejections by reason for a month and sort them, largest first. A few reasons usually cause most of the rejections. Start your RCA there.

Other methods in one line

FMEA ranks risks before failure, a fault tree maps how failures combine, and 8D is an eight-step team report.

Which tool when

Use the 5 Whys for one clear problem that keeps repeating. Use a fishbone when the cause could be in several areas.

A worked example from an Indian factory

This illustrative case from a plastic-moulding unit uses made-up details.

Problem: A customer rejects part of a dispatch of moulded housings because they crack during assembly.

Facts: All cracked parts come from one work order, run on one machine on night shift. The granules came from a new supplier, received on a GRN the day before. The lot was not inspected at receipt.

5 Whys:

  1. Why did the housings crack? The plastic was brittle.

  2. Why was it brittle? The granules still held moisture when moulded.

  3. Why was there moisture? The night shift cut the drying time to catch up.

  4. Why did they need to catch up? The new supplier's lot arrived late, so the job started late.

  5. Why could drying time be cut? It was not written in the process route, so no one checked it.

Root causes: two. Drying time was missing from the route, and lots from a new supplier were not checked at receipt.

Fix: The production head adds a fixed drying step to the process route. The stores in-charge adds an incoming quality inspection for new suppliers. Both fixes get a date, and the next few lots are rechecked.

Common mistakes that make problems come back

  • Stopping at the first cause. "Bad material" is a start, not an answer.

  • Blaming the operator. Ask what let the mistake happen. Fix the process, not the person.

  • Guessing from memory. Check the batch, GRN and work order records instead.

  • No owner for the fix. A fix with no name and no date rarely happens.

  • Not checking the gauge first. A worn or wrong gauge can make good parts look bad.

Root cause analysis checklist

Run through this one-page list before you close any RCA.

Root cause analysis checklist
  • Problem written: what, where, when, how much

  • Facts: batch, GRN, work order, machine, shift

  • Every possible cause listed

  • Root cause confirmed against records

  • Fix has an owner and a date

  • Recheck date set for next batches

Don't be the bottleneck. Become the AI-Run Factory.

Your next RCA should start with facts, not memory. See how TranZact keeps your GRN, batch and work order records together.

Book a demo →

Check out other blogs

Hero Background
Become the
AI-Run Factory

Born in India. Building for the world.

Built by IIT & IIM founders

Hero Background
Become the
AI-Run Factory

Born in India. Building for the world.

Built by IIT & IIM founders

Hero Background
Become the
AI-Run Factory

Born in India. Building for the world.

Built by IIT & IIM founders