FDA Pre-Approval Inspection Readiness: What Inspectors Test First

If your company has an NDA, ANDA, or BLA sitting in FDA review, the pre-approval inspection is not a formality that happens after the science has already been judged sound. It is a separate, high-stakes verification exercise, and the sequence in which investigators test your site tells you exactly where most applications actually fail. Companies that prepare for a PAI as if it were a routine GMP walkthrough consistently get caught out, because inspectors are not there to confirm your equipment exists. They are there to confirm your application is true.

This guide goes deep into what a Pre-Approval Inspection, or PAI, actually verifies, what FDA investigators test first when they walk onto your site, how the 2026 update to FDA’s Compliance Program Guide changes the scope of readiness, and what happens if your inspection does not go your way. If you are searching for FDA PAI readiness checklist, pre-approval inspection preparation consultants, how to pass an FDA pre-approval inspection, or FDA data integrity inspection support, this is written for you.

What a Pre-Approval Inspection Actually Verifies

A PAI is triggered by a marketing application, an NDA, ANDA, BLA, or in the device world a PMA or 510(k), and its purpose is narrow but consequential: to verify that manufacturing capability and data integrity at the proposed site actually support what has been submitted in the application. It is the final check that what a company said on paper matches what is actually happening on the manufacturing floor and in the laboratory, and it happens after application submission but before FDA makes its approval decision.

FDA’s revised Compliance Program Guide, which takes effect from August 10, 2026, restates the objective of a PAI around four core questions:

• Is the facility genuinely prepared for commercial manufacturing
• Do manufacturing operations, processes, and controls align with the submitted regulatory application
• Is the manufacturing and quality data submitted across the application reliable, complete, and uncorrupted
• Does the organisation demonstrate a pharmaceutical quality culture and a real commitment to compliant manufacturing, not just a compliant paper trail

That fourth objective, quality culture, is a meaningful shift. It signals that inspectors are no longer only checking whether procedures exist, but whether the people running them actually understand and follow them under normal operating pressure, not just when an inspector is standing in the room.

What Inspectors Test First

This is the part most preparation guides skip past too quickly. Investigators do not start with a random sample of your SOPs. They start by testing whether the story in your application holds up, and they build outward from there in a fairly consistent sequence.

1. Data Integrity, Before Anything Else

Data integrity has become the true opening test of a modern PAI, not a section covered later in the visit. Investigators approach submitted data with active suspicion in the sense that they treat it as a claim to be verified, not a fact to be accepted. In practice this means:

• Requesting raw data files, audit trails, and metadata directly, not the summary reports that were submitted in the application
• Tracing a result from the raw instrument output through every intermediate step to the final reported figure
• Reviewing how invalidated, repeated, deleted, aborted, or excluded data points were handled and documented
• Checking whether audit trails in your LIMS, chromatography data systems, and standalone instruments are actually reviewed, not just captured

Modern forensic tools also allow investigators to recover deleted electronic files and to detect gaps in sequential data entries, so a data integrity gap that a company assumes is invisible is frequently not invisible at all. Failure to review audit trails, or shared login credentials across electronic systems, remain among the most commonly cited data integrity violations, and they are usually the first thing a well-trained inspector probes because they reveal how the rest of the quality system actually functions in practice.

2. Whether the Application Matches Reality on the Floor

Once data integrity has been probed, investigators walk the production floor to verify that equipment, process parameters, and controls genuinely match what was described in the application. This is not a simple equipment checklist. Experienced investigators are reading the coherence of the whole operation, how equipment, process, and control measures interact, because a facility that looks compliant piece by piece can still fail to hold together as a genuinely validated commercial process.

3. Process Validation and Batch History

Process validation batches, and the reports behind them, are scrutinised closely because they are the direct evidence that the manufacturing process described in the application actually performs consistently at commercial scale. Sites that begin validation batch production immediately after submission, rather than waiting for PAI notification, are in a materially stronger position, since it gives time to remediate any batch failures well before an inspector arrives and creates a buffer to demonstrate genuine confidence in the process rather than a rushed final push.

4. Development Program Governance, New for 2026

A genuinely underreported change in the 2026 program is a new, explicit inspection objective focused on how the pharmaceutical development program itself is supported, defined, managed, and continually assessed, including how development knowledge feeds back into improving the pharmaceutical quality system. FDA directs coverage of this objective during the initial PAI, and periodically in later PAIs based on risk, or whenever there has been a major change to the quality system, management team, or corporate structure. This makes development governance, knowledge transfer, and management oversight visible, testable parts of readiness rather than background activity that only shows up if something goes wrong.

There Is No Strict Time Limit on Relevance

A detail that catches many sites off guard: if a past event is relevant to current process control, inspectors may explore it regardless of how long ago it occurred. A quality event, deviation, or change from several years earlier is not automatically out of scope simply because it predates the current application. If that historical event still speaks to whether your current controls are genuinely robust, an inspector can and will ask about it.

Why Good Software Does Not Substitute for a Good Quality System

One of the more common misconceptions among sites preparing for a first PAI is that a modern Manufacturing Execution System, LIMS, or electronic batch record system will effectively cover for gaps elsewhere in the quality system. It will not. Digital systems can make evidence easier to retrieve and can support stronger controls, but they cannot substitute for a well-designed, well-governed pharmaceutical quality system. In fact, poorly governed digital systems frequently create new data integrity and control problems of their own, which can make a PAI genuinely harder to pass rather than easier, particularly when investigators start pulling audit trails from systems the site assumed were beyond scrutiny.

How FDA Classifies the Outcome

Once the inspection concludes, FDA investigators submit their initial recommendation, including any Form FDA-483 observations issued, to the compliance office, generally within 24 hours of completing the inspection. From there, the inspection is worked toward a final classification:

• No Action Indicated, meaning no objectionable conditions were found
• Voluntary Action Indicated, meaning minor observations were noted that do not typically block the approval timeline or require reinspection
• Official Action Indicated, meaning significant violations were identified that require remediation, and which can trigger reinspection or a formal withhold recommendation on the application itself

A withhold recommendation is a serious outcome. It can result when deficiencies are significant enough to affect the site’s ability to perform its designated function within the application, and in cases involving data integrity failures or fraudulent data submission, a facility can be placed under FDA’s Application Integrity Policy, which subjects all of that facility’s future applications, not just the one currently under review, to heightened scrutiny. A Complete Response Letter tied to PAI findings typically adds many months to an approval timeline, so the cost of a failed inspection is rarely limited to the immediate remediation work.

Practical Steps for PAI Readiness

• Run a genuine gap analysis that compares the application, its process description, controls, and named sites, against what is actually happening on the shop floor and in the lab, rather than against what your SOPs say should be happening
• Begin process validation batches immediately after submission rather than waiting for PAI notification, targeting completion at least 60 days before the expected inspection window
• Conduct a full data integrity audit well before the inspection, requesting raw data, audit trails, and metadata from your own systems exactly as an investigator would
• Build a mock inspection into your preparation timeline, since realistic simulation consistently surfaces the hidden shortcuts staff take under normal performance pressure, while there is still time to fix them
• Review development program governance and change management records, not just current manufacturing SOPs, given the expanded 2026 inspection objective in this area
• Prepare management and quality leadership to speak to quality culture directly, since inspectors are now explicitly assessing organisational commitment to compliance, not just documented procedure

Getting Your Site Genuinely Inspection Ready

Preparing a manufacturing site for a Pre-Approval Inspection is exactly the kind of cross-functional regulatory and quality work Quality and Vigilance Ltd supports clients through, alongside its core pharmacovigilance and regulatory affairs remit covering EMA, FDA, and MHRA requirements. A failed PAI does not just delay an approval, it can trigger reinspection, a Complete Response Letter, or in the most serious data integrity cases, an Application Integrity Policy listing that follows a facility across every future submission. For companies preparing their first PAI, or remediating findings from a previous one, the support that actually changes the outcome looks like this:

• Running an honest gap analysis between the application as submitted and current shop floor and laboratory reality
• Structuring a data integrity audit that mirrors exactly what an FDA investigator will request
• Coordinating process validation batch timelines so results are in hand well before the inspection window
• Preparing quality and management teams to demonstrate genuine quality culture, not just documented compliance

Get in touch with Quality and Vigilance Ltd today to build a Pre-Approval Inspection readiness plan that holds up when the investigator actually walks in.