This is a ready-to-use work instruction for any subject matter expert (SME) brought into the front room during a live FDA or EMA inspection. Most surprise observations come from an SME saying too much, guessing, or contradicting a document. This instruction is what you train into every SME before the inspection and reinforce each morning. Replace every <<FILL: ...>> placeholder. A filled specimen exchange follows.
Control header
| Field | Entry |
|---|---|
| Document title | SME Conduct During a Live Inspection |
| Document number | <<FILL: WI-ID, e.g. WI-QA-030>> |
| Version | <<FILL: version>> |
| Effective date | <<FILL: date>> |
| Parent SOP | <<FILL: SOP-ID for inspection management>> |
| Owner | <<FILL: role, e.g. Head of Quality Assurance>> |
Purpose
To define how an SME answers an inspector’s questions accurately and completely without creating findings through over-talking, speculation, or contradiction. The SME’s job is to answer the question that was asked, anchored to controlled documents, then stop.
The core posture
Answer the question that was asked, accurately and completely, then stop. Be honest, calm, and specific. Do not perform, do not fill silence, and do not make commitments; commitments are the host’s job.
The dos
| Do | Why |
|---|---|
| Answer the question asked, then stop talking. | Silence after a complete answer is fine; inspectors use silence to draw out more. |
| If you do not know, say so and offer to find out. | ”I do not have that figure in front of me; I can get the exact number.” A strong answer, not a weak one. |
| Tell the truth, always. | A shaded answer during an inspection is a data integrity event and can escalate a process finding into something far worse. |
| Speak only to your own area. | ”That is handled by our microbiology group; I can bring the right person.” Let the host route it. |
| Anchor to the document. | ”Our procedure for that is <<FILL: SOP-ID>>; may I walk you through it?” Keeps you accurate and shows a governed system. |
| Pause before answering. | A two-second pause to confirm you understood is professional, not evasive. |
| Ask for clarification if a question is ambiguous. | ”When you say recent, do you mean this year or the last quarter?” |
The don’ts
| Do not | Why it hurts |
|---|---|
| Speculate or hypothesize. | ”I think it probably works like this” invites a tour of something you do not actually know. |
| Volunteer beyond the question. | Narrating a past, resolved problem opens a line of questioning that did not exist. |
| Say “we always” or “we never.” | Absolutes are easy to disprove; one exception and the inspector distrusts everything. |
| Argue or get defensive. | Disagreement is the host’s job, handled professionally, often deferred to the back room. |
| Blame colleagues, other departments, or “the system." | "IT never gave us the validation” creates two findings. |
| Guess at numbers, dates, or counts. | Retrieve them; a wrong guess damages credibility across the whole inspection. |
| Bring devices or unvetted papers into the front room. | No personal notes, no drafts, no phone screens shown to the inspector. |
How to ask for help
If you need to step out and consult the back room, use the pre-agreed signal to the host: <<FILL: describe the agreed signal>>. Do not improvise a technical answer under pressure; it is always acceptable to say you will confirm and come back with the precise information.
Before you enter (per-step preparation)
| Step | Action | Acceptance |
|---|---|---|
| 1 | Get briefed on your topic and its current state (open deviations, known weak points, recent changes). | You know the real status, not a rehearsed ideal. |
| 2 | Run a short mock question and answer in the back room. | You have said your key answers out loud once. |
| 3 | Confirm the document anchors for your area. | You can name the controlling SOP or record. |
| 4 | Confirm the help signal with the host. | You know how to step out if needed. |
Filled specimen exchange
Question: “How do you ensure the operator performing line clearance is qualified?”
Weak answer (do not do this): “Oh, everyone here is trained, we never let anyone on the line who is not qualified, the training group is usually pretty good about keeping up, though sometimes the matrix lags a bit behind.”
That answer used an absolute (“never”), volunteered a weakness (“the matrix lags”), and speculated about another group. The inspector will now ask for the training matrix and look specifically for lag.
Strong answer (do this): “Operators are qualified against the line clearance procedure, <<FILL: SOP-ID>>, before they perform it independently. Qualification is documented in the training record. Would you like me to show the training record for the operator who performed this clearance?”
That answer is accurate, anchored to a document, complete, and offers exactly what was asked for and nothing more.
Acceptance criteria for SME conduct
- Every answer is truthful and, where possible, anchored to a controlled document.
- No absolutes, no speculation, no volunteered out-of-scope material.
- Unknowns are stated plainly with an offer to retrieve the fact.
- No commitments are made by the SME.
- The SME stays within their own area and lets the host route the rest.
Common inspection findings this instruction prevents
- An SME narrates a resolved past problem and opens an inspection thread that did not need to exist.
- An SME says “we never,” the inspector finds one exception, and trust collapses across the record.
- Two SMEs describe the same process differently because neither anchored to the controlling procedure.
- An SME guesses a number that turns out wrong, undermining every later answer.
- A commitment an SME made informally is never tracked and then missed.
How to adapt this instruction
- Set the document number and parent inspection-management SOP in the header.
- Fill the document anchors and the agreed help signal for your site.
- Use this instruction as the SME coaching script in your mock inspection program so the conduct is muscle memory before the real event.
- Reinforce it in the morning briefing each inspection day, tailored to the topics expected that day.