This is a ready-to-use brief for the person playing the inspector in a mock inspection. The plan tells the program what the mock is testing; this brief tells the mock inspector specifically how to play the role that day, so the persona is consistent, the threads are pre-decided, and the mock inspector knows exactly when to escalate and when to stop. Replace every <<FILL: ...>> placeholder with your specifics and hand this to the mock inspector at the pre-brief, not the morning of the event. A filled specimen for a two-day, two-persona mock follows. This content is educational and general, not regulatory advice.
Header
| Field | Entry |
|---|---|
| Brief number | <<FILL: BRF-ID>> |
| Mock inspection plan reference | <<FILL: MIP-ID>> |
| Mock inspector(s) | <<FILL: name(s)>> |
| Prepared by | <<FILL: program owner>> |
| Date briefed | <<FILL>> |
| Scope covered by this persona | <<FILL: systems / areas / record window>> |
Part 1, Persona definition
Define the persona precisely enough that a stranger reading this brief could play it consistently. If the mock runs more than one day, use one row per day and rotate personas rather than running the same one twice.
| Day | Focus area | Questioning style | Pace and pressure | Tone |
|---|---|---|---|---|
<<FILL: Day 1>> | <<FILL: data integrity hawk / contamination-control specialist / investigations skeptic / computerized-systems specialist>> | <<FILL: thread-puller / document-driven / floor-walker>> | <<FILL: patient and quiet / fast and demanding>> | <<FILL: formal / conversational>> |
<<FILL: Day 2>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
Match the focus area to the mock’s scope and to current citation trends, not to the mock inspector’s personal comfort zone.
Part 2, Threads to pull
Pre-define each thread’s starting point and expected hops before the mock, so the mock inspector is not improvising the path in real time. Do not pre-define the answers; only the path.
| Thread # | Starting record | Expected hops | What “good” looks like at each hop | Escalate if |
|---|---|---|---|---|
<<FILL: T1>> | <<FILL: e.g. a random batch record from the record window>> | <<FILL: deviation to CAPA to OOS to instrument audit trail to training record>> | <<FILL: each hop is documented, dated, and reconciles with the prior record>> | <<FILL: a hop is missing, undated, or the explanation does not reconcile with the record shown>> |
<<FILL: T2>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
Part 3, Probe questions and lines of inquiry
A mix of openers, narrowing follow-ups, an out-of-lane test, and a consistency re-ask. Adapt the specifics to the scope; keep the pattern.
| # | Type | Question or prompt |
|---|---|---|
| P1 | Open-ended opener | <<FILL: "Walk me through everything that happens here.">> |
| P2 | Narrowing follow-up | <<FILL: a specific step from P1's answer, asked in detail>> |
| P3 | Out-of-lane test | <<FILL: a question slightly outside this SME's stated area, to see if they guess rather than defer>> |
| P4 | Consistency re-ask | <<FILL: a question already answered by a different SME earlier, re-asked here>> |
| P5 | Document-first | <<FILL: "Show me the last time this was reviewed," asked before any verbal explanation is accepted>> |
Part 4, Escalation and stop rules
| Rule | Instruction |
|---|---|
| When to escalate a finding to Critical in real time | <<FILL: e.g. any indication of falsification, fabrication, or a direct patient-safety gap; notify the program owner immediately, do not wait for the daily wrap>> |
| When to stop pulling a thread | <<FILL: e.g. after the finding is specific enough to act on, or after three hops with no gap found>> |
| What the mock inspector does not do | Does not coach the SME toward a better answer, does not script or preview questions, does not share findings with anyone outside the program owner and evaluators before the daily wrap, does not let the exercise become personal or punitive |
| What the mock inspector always does | Logs the thread and outcome for the scribe, states findings factually without editorializing, and keeps the persona consistent through the full session |
Part 5, Daily debrief (completed by the mock inspector)
| Field | Entry |
|---|---|
| Threads run today | <<FILL: T1, T2, ...>> |
| Findings surfaced (ID and one-line description) | <<FILL>> |
| Behavioral observations (over-answering, unknown-answer handling, consistency) | <<FILL>> |
| Threads to continue or open tomorrow | <<FILL>> |
| Persona notes for the program owner (did the persona hold up, anything to adjust) | <<FILL>> |
Acceptance criteria
- The persona is specific enough (focus area, style, pace) that a different person reading this brief would play it recognizably the same way.
- Every thread has a defined starting point and expected hops before the mock begins; the mock inspector is not inventing the path live.
- At least one probe question of each type in Part 3 is used per session.
- Escalation and stop rules are read and acknowledged by the mock inspector before the mock starts.
- The daily debrief is completed the same day, while the detail is fresh, and feeds the report’s findings register.
Signoff
| Role | Name | Signature | Date |
|---|---|---|---|
| Mock inspector (briefed and acknowledged) | <<FILL>> | ||
| Program owner (briefed) | <<FILL>> |
References
FDA Compliance Program Guidance Manual 7356.002, Drug Manufacturing Inspections (systems-based model, for a GMP persona). PIC/S inspection approach and deficiency classification (for scoring the findings this brief surfaces). For a GCP persona, score against ICH E6 and the relevant BIMO Compliance Program Guidance Manual instead of the six-systems model; see GCP mock inspections.
Confirm the current version of each reference before issue.
Filled specimen
A two-day, two-persona brief for an illustrative laboratory-focused mock. Values are illustrative.
Header: Brief BRF-2026-04, plan reference MIP-2026-03, mock inspector R. Alvarado (external consultant), prepared by the inspection readiness lead, scope QC HPLC lab and stability.
| Day | Focus area | Questioning style | Pace and pressure | Tone |
|---|---|---|---|---|
| Day 1 | Contamination-control and general operations | Floor-walker | Patient and quiet | Conversational |
| Day 2 | Data integrity hawk | Thread-puller | Fast and demanding | Formal |
Day 2 thread T1: starting record, a random stability batch record from the last 18 months; expected hops, deviation to CAPA (effectiveness verified) to OOS (root cause proven or assumed) to HPLC calibration and audit trail to analyst training record; escalate if the audit trail review is missing or dated after the disposition decision.
Day 2 probe questions used: P1 “Walk me through everything that happens to a stability sample from pull to reported result.” P3, asked of the chromatography analyst: “How does the stability chamber’s temperature excursion alarm get investigated?” (a metrology and facilities question, outside the analyst’s lane, to see whether they guess or defer). P4, re-asking the QC supervisor a question already answered differently by the bench analyst about how re-integrations are approved.
Daily debrief (Day 2): thread T1 surfaced MF-01 (audit trail unreviewed for 8 weeks, one aborted run not investigated). Behavioral note: the bench analyst answered P3 with a confident guess instead of deferring to metrology, a coaching point for the SME preparation program. Persona held up well; no adjustment needed for a future run.
This is the same thread and finding used as the worked example in the article and in the mock inspection report template; the value of this brief is that the path (T1’s hops) and the escalation trigger were written down before the mock inspector ever walked in, not improvised on the day.
Common inspection findings this brief prevents
- A mock inspector who improvises a friendly walkthrough because no persona or threads were defined in advance.
- A mock inspector who coaches SMEs toward better answers or previews questions, which defeats the purpose of the exercise.
- Findings that surface verbally in the room but are never captured because there was no structured debrief.
- A multi-day mock where the same persona runs every day, so staff simply learn to predict and manage that one person instead of being genuinely tested.
How to adapt this brief
- Set the persona and threads (Parts 1 and 2) from the mock’s actual scope and current citation trends, not from a generic template.
- If the mock covers GCP, replace the six-systems-based thread example with the informed-consent-to-EDC-query thread and score against ICH E6 and the applicable BIMO Compliance Program Guidance Manual instead.
- Rotate personas across mock events, not just across days of one event, so no single inspector’s blind spots become the program’s blind spots.
- Feed the daily debrief directly into the mock inspection report’s findings register and behavioral observations sections.