FDA Inspection Preparation: A 90-Day Quality Team Readiness Checklist

Cloudtheapp Inc. — Fri, 03 Jul 2026 12:16:17 +0000

The FDA does not schedule most inspections in advance. For many facilities, the first sign that an investigator is coming is the knock on the front door. That reality makes one point clear: inspection readiness is not a project you run in the weeks before an inspection. It is how your quality system operates every single day.

If you have a 90-day window before an anticipated inspection, or if your facility is overdue for one, this checklist gives you a structured approach to finding and closing the gaps that most commonly generate FDA">https://www.cloudtheapp.com/glossary-fda-form-483-inspection-observation/">FDA Form 483 observations.

What FDA inspectors look for under QMSR

The FDA Quality Management System Regulation (QMSR), which took effect in February 2026, aligns 21 CFR Part 820 with ISO 13485:2016. Under QMSR, FDA investigators evaluate the quality management system as a whole, not individual procedures in isolation. They want to see that your processes are documented, implemented consistently, and producing measurable results.

The most frequently cited areas in FDA inspections of device manufacturers include:

CAPA systems — Are corrective and preventive actions initiated promptly, investigated thoroughly, and verified as effective?

Complaint handling — Are all complaints captured, classified, and evaluated for MDR reportability?

Design controls — Do design history files contain complete evidence of design verification and validation?

Document control — Are procedures current, accessible to staff who use them, and protected from unauthorized changes?

Supplier qualification — Are critical suppliers approved, monitored, and periodically re-evaluated?

Training records — Can you demonstrate that personnel performing quality-critical tasks are qualified and trained for those specific roles?

An investigator who finds problems in one area will typically expand the inspection scope. A single gap in CAPA documentation can trigger a full review of complaint files, audithttps://www.cloudtheapp.com/glossary-audits/">audit> records, and training histories.

Months 1 and 2: Fix the systemic gaps

Audit your CAPA backlog

Pull every open CAPA and sort by age. CAPAs open for more than 90 days without documented progress are a consistent finding in FDA inspections. For each open item, confirm:

Is the root">https://www.cloudtheapp.com/glossary-root-cause-investigation/">root cause investigation complete and documented?

Is the corrective action defined with an assigned owner and a realistic due date?

Have effectiveness checks been scheduled?

Close CAPAs that can be resolved quickly. For complex items, document a clear timeline and visible evidence of active progress. A backlog with no movement is one of the most reliable predictors of a 483 observation.

Review your document control system

Walk through your most critical procedures: SOPs covering CAPA, complaints, design controls, supplier qualification, training, and internal audits. Check whether:

All documents are at their current approved revision

Obsolete versions have been removed from work areas and controlled storage

All recent changes are documented with rationale and reviewed by appropriate personnel

Pay particular attention to procedures updated after a previous inspection finding. FDA investigators sometimes return to verify those specific changes were actually implemented.

Verify training records match your current workforce

Investigators routinely ask to see training records for specific employees who perform regulated tasks. If your training matrix does not reflect current job roles, or if records are missing for recently hired or promoted staff, close those gaps now.

Training that happened but was never recorded is treated the same as training that never happened. That distinction matters during an inspection.

Month 3: Simulate the inspection

Run a focused internal audit

Conduct a focused internal audithttps://www.cloudtheapp.com/glossary-audits/">audit> using FDA's published guidance and QMSR requirements to review the areas most commonly cited in 483 observations. Assign a cross-functional team and have them review records the way an FDA investigator would: by sampling specific products, specific date ranges, and specific personnel files.

Document every finding with an audit">https://www.cloudtheapp.com/glossary-audit-finding/">audit finding record. Then open CAPAs for anything material.

This exercise serves two purposes. It closes real gaps before the inspector arrives. It also gives your team practice locating and presenting their own records under time pressure, which matters when an investigator asks for something specific and expects a response within minutes.

Develop your inspection plan

Every facility should have a documented process for receiving FDA investigators. Your inspection">https://www.cloudtheapp.com/glossary-inspection-plan/">inspection plan should cover:

Who greets the investigator and confirms their credentials

Which room is designated as the inspection workspace

How document requests are handled and logged

Who is responsible for reviewing documents before they are provided

How responses to verbal observations are coordinated across your quality team

Review this plan with relevant staff well before an inspection is anticipated. The first time your team learns what to do should not be the day an investigator walks through the door.

Verify your audit trail integrity

Under 21">https://www.cloudtheapp.com/glossary-21-cfr-part-11/">21 CFR Part 11 and QMSR, audit">https://www.cloudtheapp.com/glossary-audit-trail/">audit trail records in electronic systems must capture who made a change, what changed, and when. Run a sample review of your electronic quality records to confirm the audit trail is functioning correctly and has not been disabled or altered.

FDA investigators specifically test audit trail functionality in electronic systems. A system with missing or inconsistent audit trail data can elevate a minor finding into a significant observation.

When the investigator arrives

When an FDA investigator presents credentials at your facility, escort them to a private conference room, notify your inspection coordinator immediately, and offer them a clean workspace with access to the records they need.

Several practical points apply throughout the inspection:

Provide only what is requested. Do not volunteer documents or information beyond the scope of each specific request. If you are uncertain whether a document is responsive to a request, check with your quality team before providing it.

Document every request. Keep a written log of every document requested, every question asked, and every record provided. This log becomes critical if you need to prepare responses to 483 observations after the inspection closes.

Answer questions accurately. Staff who speak with investigators should answer questions directly and accurately. If they do not know an answer, saying "I'll get you that information" is better than guessing. Inconsistent answers create complications that an honest gap would not.

Do not correct records during the inspection. If the investigator identifies an error in a document, do not modify the record during the inspection. Note the issue and address it through your CAPA system after the inspection closes.

Responding to FDA Form 483 observations

A FDA">https://www.cloudtheapp.com/glossary-fda-form-483-inspection-observation/">FDA Form 483 observation is a written notice of conditions that may constitute violations of the Food, Drug, and Cosmetic Act. Receiving one does not automatically lead to enforcement action. What matters is how you respond.

You have 15 business days to submit a formal written response. A strong response:

Acknowledges the observation specifically without admitting more than the observation states

Describes the immediate corrective action already completed

Describes the systemic corrective action planned, with a specific timeline and responsible owner

Includes supporting evidence where available, such as revised procedures or completed training records

FDA evaluates whether your response reflects genuine corrective action. Generic responses promising to "review procedures" without specific actions are viewed unfavorably. A response with documented, concrete corrections already initiated signals a quality system that is functioning as intended.

How an eQMS supports inspection readiness year-round

Quality teams that manage their systems in spreadsheets and shared drives spend significant time reconstructing records before an inspection and locating specific files during one. An electronic QMS centralizes document control, CAPA management, training records, complaint handling, supplier qualification, and audit management in a single system with a complete, tamper-evident audit">https://www.cloudtheapp.com/glossary-audit-trail/">audit trail.

When an FDA investigator requests all CAPA records for a specific product line over the past two years, your response time in a capable eQMS is measured in seconds rather than hours.

Cloudtheapp is a fully validated, AI-powered eQMS built for pharmaceutical, medical device, biotech, and food and beverage manufacturers. With 60+ applications covering every major quality process, Cloudtheapp gives quality teams the documentation depth, traceability, and system integrity to enter any FDA inspection with confidence.

Schedule">https://www.cloudtheapp.com/demo/">Schedule a demo to see how Cloudtheapp supports inspection readiness across your entire quality system.

QMS inspection readiness Archives | Cloudtheapp