RCA Facilitation Script & Evidence Collection Checklist

Welcome — purpose and outcome

Use this facilitator script and evidence checklist to run focused, timeboxed Root Cause Analysis (RCA) meetings that converge on verifiable corrective actions and learning. The goal is not to assign blame but to discover verifiable causes, decide whether to contain or fix systemically, and confirm verification of countermeasures.

Before the meeting — prep checklist

• Define the scope: specific event, time window, affected product/process, and outcome measure (e.g., defect rate, downtime minutes).
• Collect baseline evidence: incident report, machine logs, photographs, inspection records, process charts, and relevant SOPs.
• Invite essential participants: process owner, frontline operator(s), subject-matter expert(s), data owner, and a scribe. Keep the group small (4–8 people) and authoritative enough to decide actions.
• Distribute pre-reads: timeline, known facts, and the evidence package; ask participants to review before attending.
• Set meeting length: Typical focused RCA: 60–90 minutes for triage/containment; 2–3 hours for deeper causal mapping.

Roles & short script

• Facilitator: keeps the group focused, timeboxed, and neutral. Reads script prompts and enforces decision rules.
• Scribe: records facts, timeline, evidence references, causal claims, proposed countermeasures, owners, and verification criteria.
• Process/Area Owner: ensures actions are feasible and resourced.
• Subject Matter Expert(s): confirm technical or procedural facts.
• Evidence Owner/Data Owner: able to access or validate logs, CCTV, machine telemetry, or records.

Suggested timeboxed agenda & facilitator script

1. Welcome & purpose (5 minutes)

   Facilitator: "We’re here to understand what happened, agree on verifiable causes, and decide actions we can verify. Our timebox is [X minutes]. Let's keep statements evidence-based. The goal is SMART countermeasures that can be validated."

2. Confirm facts & scope (10–20 minutes)

   Scribe reads the timeline and available evidence. Facilitator asks: "What do we know? What are the confirmed facts?" Capture only verifiable facts, not interpretations.

3. Evidence review & gap identification (10–20 minutes)

   Walk through logs, photos, witness statements. For each claim, ask: "What evidence supports this? If none, is it an assumption? Who can verify?" Note missing evidence and assign owners to obtain it if needed.

4. Bias checks and hypothesis generation (15–30 minutes)

   Use short directed techniques (see Bias Checks). Generate causal hypotheses, label whether each is supported by evidence, and prioritize hypotheses that explain all key facts.

5. Decision rules: containment vs systemic fix (10–15 minutes)

   Decide which actions are immediate containment (stopgap to prevent recurrence now) and which are systemic fixes (address root cause). Apply decision rules below.

6. Agree actions, owners, verification criteria (10–15 minutes)

   For each action record: description, owner, due date, verification method (what you will measure), and acceptance criteria. Use the verification & sign-off template below.

7. Close & next steps (5 minutes)

   Facilitator summarizes decisions, outstanding evidence tasks, and schedule follow-up verification meeting. Confirm scribe distribution list and where the evidence will be stored.

Evidence checklist (what to capture and reference)

Always reference evidence with file/name, timestamp, and who validated it. Useful evidence items:

• Incident report or nonconformance record (ID and date/time)
• Machine logs / PLC traces (file name, time window)
• Operator statements or witness notes (who, when, signed)
• Photos or video (filename, timestamp, camera/phone owner)
• Quality inspection data or charts (lot numbers, measurements)
• Maintenance history and recent interventions (work order IDs)
• Change records: software, tooling, BOM, supplier changes
• Relevant SOPs, drawings, and training records

Bias checks (quick techniques to keep analysis honest)

• Assumption check: For each causal claim, ask "What am I assuming? How would we test that assumption?" Label assumptions explicitly.
• Devil’s advocate (2 minutes): Invite challenge: "What would disprove our favored hypothesis?"
• Pre-mortem (rapid): Imagine the fix failed — what would cause failure? Use those thoughts to strengthen verification.
• Evidence-first rule: Prioritize hypotheses that explain the greatest number of verified facts with the least assumptions.

Decision rules — containment vs systemic fix

Use these rules to categorize actions and avoid substituting temporary fixes for real root-cause work.

• Containment if: action prevents immediate recurrence or reduces harm but does not remove the root cause; intended as short-term (<30 days) and must have an owner and sunset.
• Systemic fix if: action removes or mitigates the underlying cause so the event cannot recur; requires change to process, design, training, supplier, or system and typically needs change control and a project plan.
• Escalation rule: If the systemic fix requires multiple functions, resources, or significant lead time, create a project with milestones and an executive sponsor.

Verification & sign-off template

For each countermeasure capture these fields and have the owner sign when verified:

• Action: short description
• Type: Containment or Systemic
• Owner: name and role
• Due date:
• Verification method: what evidence will demonstrate effectiveness (e.g., 30 days of zero defects in affected lot, specific log entries showing corrected parameter)
• Acceptance criteria: measurable pass/fail criteria (SMART)
• Signed verification: name, date, attached evidence references

Where to store records

Keep a single, auditable repository for the RCA package: timeline, evidence files (with filenames), meeting minutes, action tracker, and verification attachments. Link records to incident ID and include the evidence owner for each file.

Common facilitation pitfalls

• Allowing the meeting to become a blame session — intervene and refocus on systems and facts.
• Accepting unverified claims as facts — label them as hypotheses and assign evidence tasks.
• Mixing containment and systemic fixes without clear timing — require sunset dates for containments.
• Failing to define verification criteria — no verification means no closure.

Quick checklist — ready-to-print

• Scope & incident ID defined
• Essential evidence attached or assigned
• Participants invited and pre-read distributed
• Timeboxes set and roles assigned (facilitator, scribe, owner)
• Hypotheses labeled with evidence status (verified / assumption)
• Actions recorded with owner, due date, and verification method
• Repository location recorded and follow-up scheduled

Next-level improvements (optional)

If you regularly run RCAs, consider creating templates in your knowledge system for: timeline format, evidence naming conventions, a digital action tracker linked to verification attachments, and a recurring verification review. These artifacts turn one-off RCAs into organizational memory.