Skip to content
RTI

Process & workflow

How to do root cause analysis on a defect

Fixing a defect closes one instance; root cause analysis stops it from happening again. When the same crack, leak, or out-of-tolerance condition keeps showing up, patching each one is a losing game — the process that produced it is still running. Root cause analysis is the discipline of tracing the defect past the symptom to the thing that actually let it occur, then changing that. This guide walks a practical version a field team can run without turning it into an academic exercise.

For QC managers and superintendents facing a recurring or high-consequence defect who need to stop it at the source, not just correct instances.

Step by step

  1. Define the defect precisely

    State exactly what's wrong, where, how often, and against which requirement — with photos and measurements. 'Cracking' is a symptom; 'map cracking on the third-floor slab pours after the mix change' is a defect you can investigate.

  2. Contain it first

    Before you analyze, stop the bleeding: correct or isolate the known instances and check whether the defect is still being produced right now. Root cause work runs in parallel with containment, not instead of it.

  3. Gather the facts around each occurrence

    Pull what was different where the defect appeared and where it didn't — the crew, the material lot, the weather, the sequence, the shift. Defects usually correlate with a change; the record is where you find it.

  4. Ask why until you pass the symptom

    Keep asking why each layer happened. The crack happened because the slab cured too fast; it cured too fast because it wasn't kept wet; it wasn't kept wet because no one owned curing after the pour crew left. The last answer is where the fix lives.

  5. Separate the direct cause from the root cause

    The direct cause is the physical mechanism; the root cause is the process gap that allowed it — a missing hold point, an unclear submittal, an untrained crew, a scheduling squeeze. Fixing only the mechanism leaves the gap open.

  6. Put a corrective action against the root cause

    Change the thing that let it happen — add the missing check to the ITP, retrain, fix the detail, reassign the responsibility. A corrective action aimed at the symptom isn't corrective; it's another patch.

  7. Verify the fix held

    Watch the next occurrences of the same work. The defect not recurring across subsequent pours, runs, or units is the only proof the root cause was actually the root cause.

What gets missed

  • Stopping at the direct cause — fixing the crack — and never touching the process that keeps producing cracks.
  • Blaming a person when the real cause is a missing check, an ambiguous spec, or a schedule that made the shortcut inevitable.
  • Skipping containment while you investigate, so the defect keeps being built in the meantime.
  • Declaring a root cause from one occurrence without checking what was different where the defect didn't appear.
  • Closing the analysis before verifying the corrective action actually stopped recurrence.

Questions people ask

When is root cause analysis worth the effort?
When a defect recurs, when one instance is expensive or safety-related, or when a nonconformance keeps coming back after correction. A one-off, low-consequence defect usually just needs a corrective action, not a full analysis.
How does root cause analysis relate to a nonconformance report?
The NCR documents and dispositions the specific defect; root cause analysis is what you attach when the corrective action has to prevent recurrence, not just fix this instance. Mature QC programs trigger RCA on repeat or significant nonconformances.

Terms worth knowing

Checklists that make this a one-tap job

Free, field-ready checklists, each with the photo every item needs before it can be submitted.

QC planConstruction quality control planRoles, definable features of work, three-phase control, nonconformance.12 items15 photosITPInspection and test plan (ITP)Activities, acceptance criteria, hold points and the record per row.11 items8 photosPunch listPunch list templateRoom-by-room closeout items with the before-and-after that closes them.15 items21 photosConcrete Pre-pour· ConcreteConcrete pre-pour inspection checklistThe hold-point walk before the pour buries reinforcement, embeds and vapor barrier7 items15 photos
See the whole checklist library

Related guides

Reading the steps is one thing. Proving you walked them is the job.

RTI holds the submit button until every mandatory item is answered and the photos are attached, then chains the record so it can be proven untouched later.

Start freeBrowse the checklist library