Running a Mock FDA Inspection: Roles, Document Requests, and Trip-Wire Questions

A mock FDA inspection is a scheduled internal exercise that simulates a real inspection — front-room interviews, staged document requests, and a closing discussion — run against a lab, manufacturing site, or quality unit before an actual inspector arrives. It is one specific tool used to build and test inspection readiness, not a synonym for it: readiness is the underlying continuous state (organized records, trained staff, a working CAPA process); a mock inspection is the periodic, structured drill that checks whether that state actually holds under pressure. This guide is about running the exercise itself — who plays which role, how to simulate the document-request cycle, which questions reliably trip up unprepared staff, and how to close out what the exercise finds.

Why a Mock Inspection Is a Different Exercise Than a Document Review

A tabletop document review checks whether records exist and are complete. A mock inspection checks something a paper review cannot: whether staff who did not write the SOPs can find them under time pressure, whether the person retrieving a batch record knows where the original is versus a working copy, and whether an answer given in an interview matches what the file actually shows. FDA investigators build their impression of a site’s data-integrity culture as much from how confidently and consistently staff respond in the room as from the records themselves — a gap between what a document says and what a person says about it, however small, is exactly the kind of inconsistency that turns a routine walkthrough into a longer one. A mock inspection is the only readiness exercise that tests that interaction directly.

Setting the Scope Before You Schedule One

Run a mock inspection against a defined scope, not “the whole quality system.” Reasonable scopes: a single production line or test method ahead of a known trigger (a marketing-application submission, a new product launch, high enrollment on a study using the site’s equipment); a system that has drawn observations elsewhere in the organization or industry (data integrity and computerized-system controls are consistently among the areas FDA investigators spend the most time probing, so many programs default to including at least one data-integrity thread in every cycle regardless of what else is scoped in); or a full facility exercise run on a fixed interval as part of the standing internal-audit program. Decide the scope, the systems in play, and which specific SOPs and logs are fair game before the exercise starts — an unscoped “surprise” mock inspection mostly tests whether staff can improvise, not whether the quality system works.

Structuring the Exercise: Front Room and Back Room

Real FDA inspections run on a two-room structure, and a mock inspection should mirror it exactly — rehearsing the logistics is as much the point as rehearsing the content.

The Front Room

The front room is where the mock investigator conducts the opening meeting, interviews staff, and observes operations. Roles to assign:

• Mock investigator — typically an internal quality/audit staff member, or an external GMP consultant for added objectivity, working from a written list of areas to probe (not improvising). Playing an unfamiliar or skeptical outsider, rather than a colleague who already knows the answers, is what makes the exercise useful.
• Facilitator / front-room lead — manages the meeting, makes introductions, and is the one person authorized to redirect a question to the back room rather than let an interviewee guess.
• Subject matter experts (SMEs) — the actual staff who would field questions on their own area (a specific test method, a piece of equipment, a batch record) during a real inspection. Rotate through the people who would genuinely be pulled into the room, not just the quality department; an operator or analyst who has never sat across from an outside auditor is exactly who benefits most from the rehearsal.
• Scribe — logs every question asked, who answered, and how, independent of the back room’s document log. This record is what the post-exercise scoring is built from.

The Back Room

The back room is the document-control and coordination hub the front room never sees directly during a real inspection — and shouldn’t see directly during the mock one either, which is part of what’s being tested.

• Document request log coordinator — receives each request relayed from the front room, timestamps it, assigns it to the person who can locate the record, and timestamps when it’s delivered back. This log is the single most useful artifact the exercise produces.
• Document runners — physically or electronically retrieve what’s requested. For electronic systems, this also tests whether the right people actually have the access and search skills to pull an audit trail or a specific record version on demand, not just whether the record exists.
• Back-room lead — watches for requests that reveal a gap (a document that takes too long to find, a record that turns out to be in the wrong format, a request nobody in the room knows how to fulfill) and flags it for the closing review, separate from just fulfilling the request itself.

Keeping the two rooms genuinely separated — front room staff relaying requests rather than back room staff overhearing them directly — is what actually rehearses the workflow. A mock inspection where the same three people staff both rooms interchangeably tests almost nothing about coordination.

Simulating the Document Request Process

The document-request cycle is usually where a real inspection either stays calm or starts to escalate, so it deserves more structure in the mock exercise than “ask for some records.” A working simulation:

1. The mock investigator states a request in the same form a real one would take — by record type and date range or batch/lot number, not by internal document ID (an investigator does not know your filing system’s shorthand).
2. The facilitator relays it to the back room exactly as stated, without translating or narrowing it.
3. The document log coordinator timestamps receipt, logs who it was assigned to, and timestamps delivery back to the front room.
4. The scribe timestamps when the front room actually received the document, so the two logs can be compared afterward for gaps — a request that the back room shows as “fulfilled” quickly but the front room experienced as a long, awkward wait usually means a handoff step is broken, not a records problem.

A reusable document-request log needs, at minimum: request time, requester, exact wording of the request, record type, who retrieved it, retrieval time, and whether the retrieved document matched the request as stated (a near-miss — the wrong version, a redacted copy where an unredacted original was needed — is worth logging as its own category, since that’s a specific, recurring finding in real inspections and a realistic one to rehearse for).

Common Trip-Wire Questions to Rehearse

Certain interview questions reliably expose gaps between what an SOP says and what actually happens day to day, and are worth rehearsing specifically rather than trusting general familiarity with the topic to cover them:

• “Walk me through what you actually did, step by step, the last time you did this” — tests whether practice matches the written procedure, not whether the procedure can be recited.
• “Who else can do this task if you’re out?” — probes training records and cross-coverage, a common area where documentation lags reality.
• “Show me the audit trail for this record” — for any electronic system, tests whether staff can actually pull an audit trail on demand (21 CFR Part 11 territory) rather than just knowing it exists in principle.
• “What happens if this result is out of specification?” — tests whether staff can describe the deviation/CAPA pathway correctly, including who has authority to make the call, without reaching for a binder.
• “When was this SOP last revised, and why?” — tests document-control discipline and whether the person using the SOP knows it changed, not just whether the SOP itself is current.
• “Can I see the original, not a printout or a summary?” — directly probes ALCOA+ data-integrity expectations (attributable, legible, contemporaneous, original, accurate) and whether staff understand the difference between a true original and a convenient copy.

Score each answer on the spot: confident and correct, correct but hesitant (a coaching opportunity, not a finding), or wrong/unable to answer (a real finding). The scribe’s log from the front room, cross-referenced against the back room’s document log, is what turns the exercise into a written record rather than an impression.

Scoring and Closing the Findings

End every mock inspection with a closing meeting that mirrors the real one: the mock investigator states what was observed, in the same register a Form 483 would use — specific, factual, tied to a particular record or answer, not a general impression. Findings from the exercise should feed the same corrective and preventive action (CAPA) process that would track a real inspectional observation, not a separate informal to-do list; see CASRAI’s CAPA report and plan structure guide for how to write the finding up so it’s actually trackable to closure. Findings that recur across successive mock inspections without being closed are themselves a signal worth escalating — a mock-inspection program that never closes its own findings is not functioning as a readiness tool, whatever else it accomplishes.

How Often to Run One

There is no single FDA-mandated interval for mock inspections. In practice, most quality systems build a baseline exercise into the standing internal-audit schedule (commonly annually, sometimes more often for higher-risk systems) and add a targeted one ahead of a specific trigger — a marketing-application submission, a new product line, high enrollment on a pivotal study using the site’s equipment, or after a prior real inspection surfaced findings that need re-testing before the next visit. A program with no baseline cadence and no trigger-based additions tends to only exercise readiness right before a known visit, which defeats the purpose for the unannounced, for-cause inspections that give no comparable warning.

Frequently Asked Questions

Is a mock inspection the same thing as an internal audit?

They overlap but are not identical. An internal audit is typically a document- and record-focused review against a checklist or standard (see CASRAI’s GMP audit checklist), often conducted by the quality team alone. A mock inspection specifically simulates the interactive, real-time mechanics of a regulatory visit — front-room interviews, live document requests, a closing meeting — and deliberately involves staff outside the quality department who would actually be pulled into a real inspection.

Who should play the mock investigator?

Either an internal quality/audit staff member who was not directly involved in the area being tested, or an external GMP/GLP consultant. An outsider (internal or external) who does not already know the answers produces a more realistic test than a colleague from the same team, who tends to unconsciously soften questions or accept an answer the team already agreed on.

Should staff be told in advance exactly what will be tested?

Most programs announce the exercise window and general scope (which systems or areas are in play) without scripting the specific questions in advance — announced timing keeps the logistics realistic (staff availability, room booking) while unscripted questions keep the interview portion a genuine test rather than a rehearsed performance.

How does a mock inspection connect to Form 483 and inspection classification?

A real FDA inspection concludes with one of three classifications — No Action Indicated (NAI), Voluntary Action Indicated (VAI), or Official Action Indicated (OAI) — and a Form 483 listing inspectional observations is typically issued when conditions warrant at least a VAI outcome. Structuring a mock inspection’s closing meeting and findings log the same way lets a site rehearse not just avoiding a finding, but responding to one the way it would need to respond to a real 483.

Related CASRAI Resources

• Inspection Readiness — the continuous state a mock inspection tests.
• GMP Audit Checklist — the document- and record-level audit framework a mock inspection complements.
• GxP Compliance — orientation across GLP, GCP, GMP, and GDP.
• CAPA Report and Plan Structure — how to track a mock inspection’s findings to closure.
• FDA Form 483 — the real document a mock inspection’s closing meeting rehearses responding to.
• FDA Inspection Database — how to check an inspection’s classification history.
• GCP Inspection Preparation (FDA and EMA) — the clinical-trial-site equivalent of this exercise.