top of page

How to Prepare for a Mock FDA Inspection: A 6-Step Guide

GxP Auditing & Consulting Services
23 minutes ago
4 min read

An FDA inspection rarely fails because of one dramatic problem. It goes badly when small gaps pile up: a batch record nobody can explain, a CAPA that was closed without proof that it worked, an operator whose answer doesn't match the SOP. A mock FDA inspection is how you find those gaps while there is still time to fix them.


Done well, a mock inspection feels like the real thing. Done poorly, it turns into a friendly facility tour that tells leadership what it wants to hear. Here is how to plan one that is actually worth the time.


1. Define the inspection you are preparing for


Start by naming the most likely inspection. A pre-approval inspection (PAI) for a new product looks very different from a routine surveillance inspection or a for-cause visit after a complaint or recall. Write down:

  • The products, processes, and buildings in scope

  • The regulations that apply (for example 21 CFR Parts 210 and 211 for finished pharmaceuticals, Part 212 for PET drugs, Part 111 for dietary supplements, and Part 11 wherever electronic records are involved)

  • Open items from your last inspection, recent 483 observations, and any commitments made to FDA


This scope drives everything that follows. A mock inspection without a defined scope tends to wander.


2. Build the document request list an investigator would use


Investigators usually begin with lists and logs, then sample from them. Prepare the same requests in advance and time how long it takes your team to produce them:

  • Deviation, CAPA, change control, and complaint logs for the last two to three years

  • Out-of-specification and out-of-trend investigations

  • Executed batch records for recent lots, including any that were rejected or reprocessed

  • Training records for the people who will be interviewed

  • Supplier qualification files and audit reports for critical vendors

  • Audit trails and access lists for key computerized systems


If a document takes hours to find, or arrives with gaps, that is already a finding. Slow, incomplete answers are one of the fastest ways to lose an investigator's confidence.


3. Test the quality system, not just the paperwork


The heart of a mock inspection is tracing a few threads end to end. Pick a recent deviation and follow it: was the root cause supported by evidence, was the CAPA proportionate, and did an effectiveness check show the problem actually stopped? Do the same for a change control and a complaint.


This is where weaknesses in CAPA effectiveness and investigation quality show up, and they are among the most common themes in FDA 483 observations. If the threads keep breaking, the fix is usually a systemic one. See our QMS remediation and FDA 483 response support.


4. Rehearse staff interviews


Investigators talk to the people doing the work. A mock inspection should include short, realistic interviews with operators, analysts, supervisors, and QA reviewers. The goal is not to script answers. It is to confirm that people can explain what they do, in their own words, in a way that matches the procedure and the record.


Also rehearse the logistics: who greets the investigator, where the front room and back room sit, who retrieves documents, and how requests are tracked so nothing is lost or promised twice.


5. Walk the floor the way an investigator would


When the scope includes a site visit, walk the process in the order product moves: receiving, warehouse, weighing and dispensing, manufacturing, packaging, QC laboratory, and release. Look for the details investigators notice: gowning practice, line clearance, status labels, logbooks completed at the time of the activity, and equipment that is overdue for calibration.


Where electronic systems support the process, check them on the spot. Shared logins, disabled audit trails, and unreviewed data are classic data integrity (ALCOA+) and CSV findings.


6. Rank the findings and close them


A mock inspection is only useful if it changes something. The report should separate critical, major, and minor findings so leadership knows where to act first. Each finding needs an owner, a due date, and a CAPA that addresses the cause, not just the symptom.


Schedule a short follow-up review a few weeks later to confirm the actions were completed and are working. That follow-up is what turns a mock inspection into real readiness.


Common mistakes to avoid


  • Running the mock inspection too late to fix what it finds

  • Using an internal auditor who is too close to the processes being reviewed

  • Treating the exercise as a training event instead of a genuine test

  • Ignoring suppliers. FDA can ask how you qualify and oversee your CMOs, CDMOs, and critical vendors. See vendor and CDMO qualification audits.


Get an independent mock FDA inspection


GxP Auditing & Consulting Services runs mock FDA and EMA inspections led by Ramzi W. Kozal, CQA, an independent GxP lead auditor with nearly 30 years of experience. He has led more than 300 GxP audits across the US and Europe and has hosted and defended more than 20 FDA inspections with zero critical observations. That is a record of past work, not a promise about any future inspection.


Learn how a mock FDA/EMA inspection is scoped, or contact us to plan one remotely, on site, or both.

 
 
 

Recent Posts

See All

Comments


bottom of page