CAPA Investigation Guide: Interview Script, Evidence-Based 5-Whys Template & Verification

How to use this playbook

Use this guide every time you investigate a quality escape, nonconformance, or other problem that requires a corrective and preventive action (CAPA). The goal is to move from anecdote to evidence, producing a clear root-cause statement, a mapped set of countermeasures, and concrete verification steps so the problem doesn't recur.

Quick checklist before the interview

• Gather basic facts (part number, lot, date/time, process step, machine, operator).
• Collect initial evidence: inspection records, machine logs, tooling history, photos, batch records, work instructions, and previous CAPAs.
• Identify primary stakeholders and potential interviewees (operator, lead, maintenance, quality, supervisor).
• Schedule a private, respectful interview and explain the purpose: fact-finding, not blame.

Interview script (suggested flow and phrasing)

1. Introduction: "Thank you for taking the time. I want to understand what happened so we can stop it from happening again. I'm not here to blame anyone—I'm here to clarify facts and learn."
2. Context: Ask the interviewee to describe their role, shift, and responsibilities relevant to the event.
3. What happened: "Tell me, in your own words, what you observed or did when the nonconformance occurred." Encourage concrete details and avoid hypotheticals at first.
4. Timeline: Work backward and forward—"What happened before that? What happened next?" Capture time stamps, sequence of steps, and any handoffs.
5. Who observed: "Who else was present or might have seen this?" Record names and roles for follow-up interviews.
6. Containment performed: "What was done immediately to contain the issue?" Record disposition of affected items and any interim controls applied.
7. Variations from standard work: "Was anything different from normal—materials, tooling, instructions, personnel, environment, or equipment settings?" Compare against the documented standard work.
8. Evidence & artifacts: Ask for records, photos, logs, or samples. "Can you show me the record or snapshot from that time?"
9. Closing: Confirm contact info for follow-up, thank them, and note any immediate actions they recommend.

Interview tips: ask open questions, avoid leading or yes/no questions at first, pause to let the interviewee think, record with permission, and capture exact phrases when they describe actions or conditions.

Evidence-based 5-Whys template

Use 5-Whys as a structured chain of cause-and-effect, but require evidence at each why. If an assertion lacks evidence, mark it as "hypothesis" and plan how to verify.

Example (short): Problem—100 units failed visual inspection on line B on 2026-07-12.

1. Why 1: Operator used different glue. Evidence: batch label on workstation—Hypothesis to verify with material log.
2. Why 2: Supplier sent unlabeled boxes. Evidence: receiving records and photo. Confirms root cause is inadequate incoming inspection.

Mapping countermeasures to verification

Every countermeasure needs a measurable verification. Use this short table for each countermeasure:

• Countermeasure: (what will change)
• Measure: (metric to confirm effect, e.g., defect rate, number of nonconforming units, audit score)
• Owner: (person accountable)
• Due date: (target completion)
• Verification method: (audit, inspection, test run, sample count, system log review)

Record these fields in the CAPA record and schedule verification events. Avoid open-ended verification such as "monitor"—be specific.

Common pitfalls and how to avoid them

• Accepting unverified statements as facts—mark hypotheses and collect evidence.
• Stopping at human error—ask why the error was possible and fix system-level causes.
• Vague corrective actions—prefer specific changes with owners and dates.
• No verification—every action should have a measurable confirmation method.

Suggested documentation template (paste into CAPA record)

Problem statement: [specific].
Interview summary: [who, when, key facts].
5-Whys chain: [concise bullets linking to evidence].
Countermeasures: [list with measure, owner, due date, verification method].
Follow-up plan: [dates for verification and closure].

How this playbook supports audits and continuous improvement

Using a standardized script and evidence-linked 5-Whys improves repeatability, reduces audit findings, and helps build organizational learning. Save interview artifacts (photos, logs, transcripts) with the CAPA so future teams can learn what worked.

Next steps / customization

Adapt question language, evidence fields, and verification metrics to match your product, process, and regulatory needs. Consider adding role-specific prompts for maintenance or suppliers.