Work Instruction: Blame-Free Investigative Interview for Deviations

This is a ready-to-use work instruction. Replace every <<FILL: ...>> placeholder with your own specifics and reference it from your parent deviation and investigation SOP. A worked filled specimen follows the template. It is an educational aid to adapt and verify, not legal, HR, or disciplinary advice; route any accountability decision through your own HR and legal processes, and use this work instruction only for the fact-finding interview itself.

Control header

Purpose

Give an investigator a repeatable way to interview a person involved in a deviation that produces an accurate, factual account rather than a defensive or rehearsed one. Accurate interview data is what lets an investigation separate a slip from a lapse from a mistake from a violation, apply the substitution test, and reach a root cause that is a system property rather than a name. See Human error in deviations for the reasoning behind the taxonomy this interview technique is built to support.

When to use

Use this work instruction for any interview of a person whose action is part of a deviation, an out-of-specification or out-of-trend investigation, or a complaint investigation, before a root cause is drafted. It is not a disciplinary meeting; if an accountability decision is also needed, that follows a separate process, generally informed by the just-culture classification work instruction, after the facts from this interview are gathered.

Definitions

• Objective account: what the person did, saw, heard, and observed, in their own words, without the interviewer’s interpretation or conclusion added.
• Conclusion: a judgment about cause, fault, or category (for example “I made a mistake” or “it was human error”). Conclusions belong to the investigator’s analysis afterward, not to the interview notes.
• Intention versus action: what the person meant to do versus what they actually did. The gap between the two is what separates a slip or lapse (intention was correct) from a mistake (the plan itself was wrong) or a violation (intention was to depart from the procedure).

Procedure

Step 1: Prepare before you speak to anyone

1. Gather the objective evidence first: the batch or test record, the audit trail or system log, the SOP revision in effect that day, training records, equipment logs, and a draft timeline. Interview after you have the facts, not to discover them from scratch.
2. Interview each person involved separately, before they have a chance to compare accounts with each other.
3. Schedule promptly, ideally the same day or the next working day, while memory is fresh.
4. Do not form a theory of what happened before the interview. A theory formed early biases every question that follows.

Per-step acceptance: the objective evidence and a draft timeline exist before the first interview is scheduled; each person is interviewed separately.

Step 2: Set the room and the framing

1. Interview privately, one on one unless your local policy requires a second observer; if a second person is present, they take notes only and do not ask questions.
2. Sit so the conversation feels like a conversation, not an interrogation across a desk with a closed door and a stack of paper between you.
3. Open by stating the purpose plainly: this conversation is to understand what happened so the process can be fixed, it is not to decide blame, and the account will be used to complete the investigation.

Suggested opening: <<FILL: "Thanks for making time. I want to understand exactly what happened with [event], step by step, so we can fix whatever let it happen. This isn't about getting anyone in trouble, it's about getting an accurate picture. Can you walk me through it?">>

Per-step acceptance: the interviewee can state back, in their own words, that the purpose is fact-finding, not blame.

Step 3: Open with a walk-through, not a why

1. First question is always some form of “walk me through exactly what you did, from the beginning.” Never open with “why did you do that” or “why did you make that mistake.”
2. Let them tell the story in their own order before you start asking about specific details. Interrupting early loses information and signals you are steering toward a conclusion.
3. Take the account at face value initially; you will test it against the evidence afterward, not challenge it in the room.

Per-step acceptance: the interviewee gives an uninterrupted narrative account before any targeted follow-up question is asked.

Step 4: Separate intention from action

1. Once you have the narrative, ask directly what they meant to do at each key point, and compare it to what actually happened. “What were you trying to do right there?” and “What actually happened?” are two different questions; ask both.
2. If intention and action match but the outcome was wrong, you are looking at a slip (attention) or a lapse (memory), not a mistake.
3. If the intention itself was to follow the wrong rule or a plan that could not have worked, you are looking at a mistake, not a slip.
4. If the person tells you they knowingly did something other than the written procedure, ask why, without judgment in your tone; that answer is what separates a routine violation (the normal way, done because the official way is impractical) from a situational violation (forced by conditions that day).

Per-step acceptance: the interview notes contain a specific statement of what the person intended, distinct from what they actually did, at the point where the deviation occurred.

Step 5: Explore the conditions, not just the action

1. Ask about the task as it normally goes, and what was different this time: staffing, workload, time pressure, shift handover, interruptions, the state of the equipment, the clarity and availability of the procedure, lighting, noise, alarms.
2. Ask what they would change so this could not happen again. This question often surfaces the real system gap directly, and it signals the interview is aimed at the process, not the person.
3. Ask whether this has happened before, to them or to anyone else they know of. A “yes” here is significant evidence for the substitution test.

Per-step acceptance: the notes cover task conditions on the day, not only the specific action, and record the interviewee’s own suggestion for what would prevent recurrence.

Step 6: Handle a defensive or frightened interviewee

1. If the person becomes defensive, stops elaborating, or starts giving short, guarded answers, stop pushing for detail and restate the purpose: “I want to be clear, I’m not trying to catch you out, I need to understand the process so we can fix it.”
2. Slow down. Ask about the process in general before returning to the specific event (“walk me through how this task normally goes” is often easier to answer than “walk me through what you did wrong”).
3. Do not promise an outcome you cannot control (“nothing will happen to you”) if accountability is a genuinely open question; instead be accurate about what you can promise: the account will be used to understand the process, and any accountability question is handled separately and fairly.
4. If the person is too upset or guarded to give a useful account in the moment, pause the interview and reschedule rather than push through a low-quality account you will have to discount later.
5. Never threaten, never raise your voice, never interrupt to correct or contradict them mid-account.

Per-step acceptance: if defensiveness or distress is observed, the interviewer’s response is documented (reassurance given, pace changed, or interview paused and rescheduled), not pushed through.

Step 7: What never to ask or say

Do not use any of the following in this interview:

• “Why did you make that mistake?” or any question that names a conclusion before the facts are gathered.
• “Don’t you think you should have known better?” or any question that invites self-blame.
• Leading questions that supply the answer (“you were rushing, weren’t you?”).
• Naming or discussing another person’s account (“Sarah said you did X, is that true?”).
• Any statement, explicit or implied, about disciplinary consequences during a fact-finding interview.
• Interrupting to correct the person’s account with what you already believe happened.

Per-step acceptance: none of the above appear in the interviewer’s questions as recorded in the notes; a self-review of the notes against this list is completed before filing.

Step 8: Take notes as an objective account, not a conclusion

1. Record what was said, close to verbatim on key points, and what was observed, not your interpretation of what it means.
2. Keep facts and inference visibly separate. If you write an inference, label it as yours, not as something the interviewee said.
3. Do not write conclusions into the interview record (“this shows the operator was careless”). Conclusions belong in the root-cause analysis section of the investigation, built from the evidence across all interviews, not in any one interview’s notes.
4. Note the time, date, location, and who was present, alongside the account.

Per-step acceptance: the interview notes contain no cause conclusion, classification, or blame language; every entry is either a direct quote, a paraphrase clearly marked as such, or an observed fact.

Step 9: Close the interview

1. Summarize back what you heard, in your own words, and ask the person to confirm or correct it. This step catches misunderstandings before they become part of the record.
2. Thank them, and explain what happens next in plain terms: the account becomes part of the investigation, other evidence will also be reviewed, and the root-cause statement and CAPA will focus on the process.
3. Confirm you can follow up with a clarifying question later if needed, and how.

Per-step acceptance: the interviewee confirmed the summarized account, or a documented correction was made to it, before the interview closed.

Step 10: After the interview

1. File the interview record in the confidential investigation file, separate from the deviation record that may be more broadly circulated.
2. Do not put the person’s name in the root-cause statement or in the CAPA description. Names live in the interview record, not in the analysis that a reader outside the investigation will see.
3. Feed the factual account, especially the intention-versus-action detail from Step 4 and the conditions from Step 5, into the human-error classification and root-cause work (see the human error classification and hierarchy of controls checklist).
4. If the account revealed a data-reliability or falsification concern rather than an honest error, route that separately through your just-culture and data integrity procedures; this work instruction covers the fact-finding interview, not the accountability decision.

Per-step acceptance: the root-cause statement and any published CAPA description contain no names; the interview record is filed and referenced, not duplicated, in the investigation file.

Acceptance criteria

A completed interview is acceptable when all of the following are true:

• The interview opened with a stated fact-finding purpose and a walk-through question, not a why question.
• Intention was separated from action, with both recorded specifically enough to support an error-type classification.
• Task conditions on the day were explored, not only the specific action.
• None of the banned questions or statements in Step 7 appear in the record.
• Notes are an objective account: quotes, clearly marked paraphrase, and observed facts, with no cause conclusion written into them.
• The account was summarized back and confirmed or corrected before closing.
• The person’s name does not appear in the root-cause statement or CAPA description that leaves the confidential file.

References

21 CFR 211.192 (thorough investigation of discrepancies and failures, which the interview supports with accurate evidence). FDA guidance, Data Integrity and Compliance With Drug CGMP: Questions and Answers (December 2018), on blame-free reporting culture as a condition for accurate data. The human-error taxonomy (slip, lapse, mistake, violation) developed in James Reason’s human-error research, which the intention-versus-action question in Step 4 is built to surface. The just-culture framework as applied in high-reliability safety fields, distinguishing the fact-finding interview from the separate accountability decision.

Confirm the current version of each reference before you rely on it.

Record generated: interview record

Revision history

Approvals

Filled specimen

The following shows the interview record completed for an example deviation, so you can see the level of objective detail expected. The company and names are illustrative and generic; replace them with your own, and in practice keep the interviewee’s real name out of any copy of this record that leaves the confidential investigation file.

Event: During dispensing for a batch, an operator dispensed material from a container labeled with the wrong lot number, caught at reconciliation before use.

This account, taken without blame language and focused on the walk-through and the conditions, is what let the investigation classify this as a slip enabled by a design gap (no lot-level scan at dispensing) rather than close it as “operator error, retrain.” The operator’s own suggested fix, a scan-to-verify step, matched the CAPA the investigation independently selected.

Common inspection findings this work instruction prevents

• Interview notes that record a conclusion (“operator was careless”) instead of an objective account, so the investigation’s root cause cannot be traced back to evidence.
• Leading or blame-framed interview questions that produce a defensive, incomplete, or inaccurate account.
• No separation of intention from action, so the investigation cannot distinguish a slip from a mistake from a violation and defaults to “human error.”
• The interviewee’s name appearing in the root-cause statement or CAPA description in the circulated investigation record.
• An interview conducted so late, or so adversarially, that the account is unreliable or the person declines to cooperate in future investigations.

How to adapt this work instruction

1. Point the parent-SOP field at your real deviation and investigation procedure, and set your document number and effective date.
2. If your policy requires a second person present at interviews (a union representative, an HR observer), adjust Step 2 accordingly while keeping that person’s role limited to observing, not questioning.
3. Translate the opening script in Step 2 into language that fits your site’s culture and, where needed, the interviewee’s working language.
4. Keep Step 7’s banned-question list visible to new investigators; it is the fastest way to train a consistent, blame-free technique.
5. Confirm every reference against its current published version before issue.