Mock Audit Guide
Step-by-step guide for conducting effective internal mock audits
A well-run mock audit is the single highest-impact preparation activity before any regulatory inspection. This guide walks through planning the mock audit scope, selecting and briefing the internal audit team, structuring the inspection day, documenting findings using a standard observation form, and prioritizing remediation of critical gaps. Includes a 60-day mock audit planning timeline.
Why Mock Audits Outperform Other Inspection Preparation Activities
Internal checklist reviews and document reconciliation exercises are valuable but they share a critical limitation: they are conducted by the same team that created the documentation, using the same mental models that generated the gaps in the first place. A mock audit introduces a different perspective — structured, adversarial, and calibrated to what actual inspectors look for.
Organizations that conduct mock audits within six months of a scheduled inspection consistently report two benefits: they find critical gaps earlier (when there is still time to remediate), and their staff perform significantly better during actual inspections because they have experienced an inspection-like environment and know what to expect.
Step 1: Planning the Mock Audit Scope
The scope of your mock audit should mirror the scope of the expected regulatory inspection as closely as possible. An FDA BIMO site inspection will focus on investigator conduct, consent processes, source data integrity, and IP accountability. An EMA GCP inspection of a sponsor will focus on QMS, TMF completeness, and CRO oversight. Calibrate your mock accordingly.
- Identify the type of inspection expected and the regulatory authority's current focus areas
- Determine whether the mock will cover the full inspection scope or specific high-risk domains
- List all document categories and process areas within scope
- Identify which subjects or data batches will be reviewed — use a random sample plus flagged outliers
- Define the inspection simulation period: how many inspection days will the mock replicate?
Step 2: Selecting and Briefing the Mock Audit Team
The mock audit team should be composed of individuals who were not directly involved in the work being audited. Using an external QA consultant provides the most objective assessment and the most accurate simulation of an actual inspection. Internal staff from a different site, functional area, or study can also serve as mock inspectors if an external resource is not available.
Brief the mock inspection team on the regulatory authority's current focus areas and the specific inspection type, but do not give them advance access to the documents being reviewed — this defeats the purpose of the simulation.
- Use external QA consultants for the highest-impact mock inspection experience
- If using internal staff, select individuals with no prior involvement in the study being audited
- Provide mock inspectors with the applicable regulatory guidance documents (FDA BIMO manual, EMA GCP inspection guidance)
- Confirm mock inspectors are familiar with the inspection format: opening meeting, document review, closing meeting
- Do not brief mock inspectors on known gaps in advance — the goal is independent identification
Step 3: Structuring the Inspection Day
The mock inspection day should replicate the actual inspection structure as closely as possible. This includes a formal opening meeting, structured document and data review sessions, staff interviews, and a closing meeting with verbal findings. Staff participation should mirror who would actually be present during a real inspection — not just QA staff.
Staff interviews are often the weakest area in mock inspection preparation. Many sites focus almost exclusively on document readiness and underinvest in preparing staff for real-time questions from inspectors about their processes and responsibilities.
- Conduct a formal opening meeting with introductions, agenda review, and facility overview
- Rotate through document review, data review, facility walk-through, and staff interview sessions
- Interview staff from all functions that would be questioned in a real inspection (PI, coordinator, pharmacist, data manager)
- Ask staff to explain their processes in their own words, not to recite SOP language
- Document all staff responses, including answers that are inconsistent with SOPs or each other
Step 4: Documenting Findings
All mock inspection findings should be documented using a standardized observation form that classifies findings as critical, major, or minor — the same classification system used by regulatory inspectors. This classification determines the remediation priority and timeline.
Critical findings: directly affect patient safety or data integrity, or indicate a fundamental failure of GCP. Require immediate remediation before the actual inspection.
Major findings: significant deviations that could affect the reliability of trial data or subject welfare. Require remediation within 30 days.
Minor findings: procedural inconsistencies that do not affect data integrity or subject safety. Should be remediated before the inspection but are lower priority.
- Use a standardized observation form with fields for finding description, classification, reference standard, and recommended action
- Classify every finding before the closing meeting
- Reference the specific regulation, guideline, or SOP that the finding violates
- Group related findings to identify systemic issues versus isolated errors
- Present all findings at the closing meeting — do not filter out uncomfortable findings
Step 5: Prioritizing Remediation
Mock inspection findings should be immediately converted into a formal CAPA plan with assigned owners, due dates, and evidence requirements. Critical findings should have remediation completed and verified before the actual inspection date. Major findings should be substantially remediated with visible progress documented.
Do not attempt to remediate every minor finding before remediating critical and major findings. Prioritize by risk impact, then by the time remaining before the actual inspection.
- Open a CAPA for every critical and major finding within 48 hours of the mock inspection closing meeting
- Assign each CAPA to a named owner with a specific due date
- Schedule a remediation status review at 2 weeks and 4 weeks post-mock
- Verify remediation effectiveness — do not close CAPAs without evidence of completion
- Re-inspect critical finding areas before the actual inspection to confirm closure
60-Day Mock Audit Planning Timeline
- Day 60: Define scope, select mock inspection team, confirm inspection date
- Day 52: Provide mock inspectors with regulatory guidance materials; prepare document packages
- Day 45: Confirm all staff who will be interviewed are available and briefed on inspection logistics
- Day 30: Conduct the mock inspection — opening meeting, document review, interviews, closing meeting
- Day 28: Distribute written mock inspection report with all findings classified
- Day 25: Open CAPAs for all critical and major findings; assign owners and due dates
- Day 14: Remediation status review — confirm critical findings are closed or on track
- Day 7: Re-inspect critical finding areas to confirm remediation effectiveness
- Day 1: Final staff briefing on real inspection logistics and expectations
Browse all resources or contact us to discuss your QA needs.