AI GxP validation for regulated life sciences
Audit Readiness

FDA Inspection Preparation: The 90-Day Plan From First Signal to Inspector Walkthrough

A week-by-week guide to preparing for an FDA inspection: system inventory, audit trail review, deviation closure, training gaps, and the mock-audit protocol that finds problems before inspectors do.

Cybroscape Technologies6 min read

Key takeaway

A week-by-week guide to preparing for an FDA inspection: system inventory, audit trail review, deviation closure, training gaps, and the mock-audit protocol that finds problems before inspectors do.

You do not prepare for an FDA inspection when you receive the notification. You prepare for it every day — and when notification arrives, you verify that your preparation holds. This guide provides the 90-day playbook that validation and quality leaders use to move from "we think we are ready" to "we know we are ready, and here is the evidence." It covers the systems, documents, people, and processes that inspectors examine, in the order they typically examine them.

This is the plan for when an inspection is on its way. For staying ready the rest of the year, see the complete guide to inspection readiness.

Days 1–14: System and documentation inventory

The first two weeks are about confirming what you have, not fixing what you do not. Start with the system inventory: every GxP-critical computerised system, its validation status, its last periodic review date, and its change control history since the last review. Produce a one-page summary per system. Then move to documentation: the VMP, site master file, SOPs, training records, and deviation/CAPA logs. Confirm that every document is current, approved, and accessible from the DMS — not filed in someone's inbox.

  • Run a validation status report from Cybroscape GxP Copilot or your validation management tool. Flag any system overdue for periodic review.
  • Pull the last 12 months of change control records. Confirm every change has a completed impact assessment and, where required, regression testing evidence.
  • Verify that your approved supplier list is current and every GxP software vendor has a completed audit or assessment.
  • Confirm that your training matrix is current and all personnel in GxP roles have completed required training.

Days 15–30: Gap closure sprint

Take the findings from the inventory and close gaps aggressively. Prioritise by inspection risk: items that result in 483 observations, not items that are merely imperfect.

  • Overdue periodic reviews. Complete them now. A periodic review does not need to be a major exercise — it confirms that the system still operates as validated, changes have been controlled, and the risk assessment is still current.
  • Open deviations past their due date. Close them or document a justified extension. Open, overdue deviations are one of the most common 483 triggers.
  • CAPA effectiveness checks not completed. Verify that completed CAPAs actually achieved their intended outcome. This is the step most teams skip, and inspectors know it.
  • Training gaps. Any GxP role missing required training is a finding. Complete the training and document it before the inspection window.
  • Audit trail review. Run an audit trail review for your highest-risk systems. Look for patterns that inspectors flag: repeated login failures, after-hours modifications, data deletions followed by re-entries.

Days 31–60: Mock audit

The mock audit is the most valuable activity in inspection preparation. It simulates the inspector's walkthrough using the same techniques, questions, and evidence requests that real inspectors use.

  • Select your mock auditor. This should be someone who has seen real FDA inspections — either an internal audit team member with inspection experience or an external consultant. The mock auditor should not have been involved in the gap closure sprint.
  • Scope the mock audit. Cover the same ground an inspector would: the system inventory, validation records for 2–3 systems, the change control process, training records, deviation/CAPA management, and data integrity.
  • Run it realistically. The mock auditor requests documents, interviews staff, reviews audit trails, and follows deviation threads to their conclusion. Time the document retrieval — if it takes more than 15 minutes to produce a requested record, that is a readiness gap.
  • Debrief and remediate. The mock audit should produce a report with findings categorised by severity. Remediate critical findings immediately. Track minor findings as improvement actions.

audit readiness provides the mock-audit protocol framework, and Cybroscape GxP Copilot's audit readiness dashboard shows the current status of every system's validation records, periodic reviews, and change control history in real time.

Days 61–90: Readiness lock and team preparation

In the final 30 days, the focus shifts from systems and documents to people. Inspectors interview staff at every level — from operators to QA managers. Everyone who might interact with an inspector needs to know three things: what their role involves, where the evidence of their work lives, and how to respond to questions honestly without volunteering unnecessary information.

  • Conduct brief interview preparation sessions for all GxP-facing staff. Practice answering common inspector questions: "Show me how you handle a deviation," "Walk me through a recent change control," "How do you know this system is validated?"
  • Establish the inspection logistics: designated rooms, escort procedures, document request workflow, real-time communication protocol for the inspection team.
  • Run a final readiness check against all 60 items in the compliance checklist. Every item should be green. Any amber or red items should have documented remediation timelines.
  • Freeze non-critical changes. Do not deploy system upgrades, SOP revisions, or process changes in the 30 days before a known or anticipated inspection unless they are required to close a compliance gap.

The five most common 483 observations and how to prevent them

Rank483 CategoryRoot CausePrevention
1Procedures not followedSOP too complex or outdatedSimplify SOPs, verify training, audit compliance
2Inadequate investigation of failuresRoot cause analysis skipped or superficialTrain on RCA methods, require QA review of investigations
3Equipment not properly maintainedPM programme gaps or missed schedulesAutomated PM scheduling, calibration tracking
4Laboratory controls inadequateOOS investigation, data integrity, method validationdata integrity (ALCOA+) programme, audit trail review, method validation
5Buildings/facilities not properly maintainedEnvironmental monitoring, cleaning validation gapsEnvironmental monitoring programme, cleaning validation

Where to go next

Explore Cybroscape GxP Copilot for AI-native validation, Cybroscape TraceDraft for source-traceable clinical documentation, or book a demo to see either on your own data.

Audit trail
  1. 14:32Signed: Approved for releaseQA Manager
  2. 11:05Changed risk of URS-015Validation lead · Supplier test evidence acceptedMedium → Low
  3. 10:48Edited expected result, OQ-07Validation lead · Lockout after 5 attempts, per URSv3 → v4
  4. 09:12Recorded result, OQ-07Tester · Evidence attachedPassed
Append-only. Entries cannot be edited or deleted.
Who, what, when and whyOn every change
An audit trail an inspector can read: who did what, when, the old and new value and the reason. Entries are append-only and each one is linked to the one before, so a changed or missing entry shows.
See it on your own systemBring a URS or a system. We run GxP Copilot against it live on the call.
fda inspection preparationfda audit preparationprepare for fda inspectionfda inspection checklistfda 483 preventionprepare for fda auditfda inspection readiness plan

Keep reading

All articles
ComplianceInspection Readiness for Pharma: FDA & EMA Audit Checklist + Live Inspection Room GuideA practitioner's guide to FDA, EMA and MHRA inspection readiness: how to build an always-ready posture, the 7-item retrieval checklist, live inspection request room tracking (Cybroscape eQMS), and the findings that recur most often. · 8 min readAudit ReadinessThe Retrieval Drill: A 15-Minute Test of Whether You Are Actually Audit ReadyAudit readiness is a retrieval problem before it is a documentation problem. A simple unannounced drill that tells you the truth about your estate in fifteen minutes. · 5 min readAudit ReadinessHow to Prepare for a GxP Audit: A Practical ChecklistWhat a GxP audit examines, how to prepare in the weeks before, the evidence auditors ask for first, the findings that recur most often, and how to answer questions you do not know the answer to. · 8 min readSupplierSupplier qualification under CSA: don't re-prove what your vendor already provedVendor-evidence as a first-class test path, and how to document it defensibly. · 6 min readBuyer GuideSwitching validation platforms without losing your recordsWhen switching validation platforms, migrate templates and master data, finish in-flight work in the old system, keep executed records readable in read-only form or an archive, run in parallel to a fixed end date, and fix the process rather than copying it. · 3 min readBusiness CaseWhat AI Actually Costs in a Regulated CompanyThe licence is the visible number and rarely the biggest one. Validation, monitoring, SOP changes, training, revalidation on every model update and the review time that never goes away, all priced honestly. · 5 min readRegulatoryUS Says SI, Europe Says AI: One Quality System, Two VocabulariesThe rename applies to US federal writing only. EU GMP, the draft Annex 22, the EU AI Act and MHRA all still say artificial intelligence. How to run one set of procedures across both without creating a translation problem. · 5 min readIntegrationValidating an ELN-LIMS Integration Under GAMP 5: A Step-by-Step Technical GuideThe complete GAMP 5 validation lifecycle for an ELN-LIMS integration: from URS and risk classification through IQ/OQ/PQ execution, change control, and ongoing oversight. · 6 min read

Bring a system. We'll show you the package.

Book a demo, or ask a validation lead a quick question on WhatsApp.

  • We reply within one business day
  • We run your URS live on the call
  • You get a clear plan for your system
Chat on WhatsApp

Book a demo

Four fields. The right specialist replies within one business day.

Your details stay private. We never share them.