Usage Examples
- The PAI is scheduled for the commercial site, so every batch record cited in Module 3 needs to be retrievable in under a minute.
- We cannot file until the CMO agrees in writing to host a PAI.
- That discrepancy between the stability summary and the raw chromatograms is a PAI finding waiting to happen.
What is Pre-Approval Inspection (PAI)?
Pre-Approval Inspection is an FDA facility inspection conducted while a drug marketing application is pending, testing whether the site can manufacture the product under cGMP and whether the application's data matches what the site actually did.
A Pre-Approval Inspection exists because an application is a claim, not a fact. Reviewers read a dossier describing a process, a facility, and a set of results, none of which they have seen. The PAI is the agency's only chance to test that written description against the physical site and the underlying records before the product reaches patients.
A Pre-Approval Inspection covers three things: whether the site is ready to manufacture commercially, whether what the application says matches what the site actually does, and whether the data behind the submission is authentic and traceable to source records. It is not a review of the drug's clinical merit, and it does not replace routine cGMP surveillance of the same facility.
A Pre-Approval Inspection is run through the application itself. Investigators arrive holding the submitted batch records, specifications, and analytical methods, then work backward to raw data. The consequence is regulatory, not advisory: methods, facilities, or controls found out of conformance with parts 210 and 211 are a stated ground for refusing to approve the application.
Not to be confused with
- Routine cGMP surveillance inspection
- surveillance examines an operating site on a risk-based cycle regardless of any pending application. A PAI is anchored to one specific application, and its findings feed that approval decision.
- For-cause inspection
- a for-cause inspection is triggered by an adverse signal such as a complaint or a suspected data problem. A PAI is triggered by the filing, not by anything having gone wrong.
- BIMO inspection
- Bioresearch Monitoring audits how clinical and nonclinical studies were conducted and whether the study data holds up. A PAI audits the manufacturing site and the CMC data supporting the same application.
- Form 483
- a Form 483 is the list of observations issued at the close of an inspection, including a PAI. It is an output of the inspection, not a category of inspection.
A PAI has no standalone rulebook. Its leverage comes from the grounds FDA can invoke to refuse the pending application.
What you must do
- 1Give FDA an adequate opportunity to inspect the facilities, controls, and any records relevant to the application21 CFR 314.125(b)(12)
- 2Operate the methods, facilities, and controls used for manufacture, processing, packing, or holding in compliance with the cGMP regulations in parts 210 and 21121 CFR 314.125(b)(13)
- 3Ensure those methods, facilities, and controls are adequate to preserve the drug's identity, strength, quality, purity, stability, and bioavailability21 CFR 314.125(b)(1)
- 4Keep every statement of material fact in the application true, including the manufacturing and analytical figures an investigator will trace back to source records21 CFR 314.125(b)(7)
- 5Ensure contract parties holding study facilities or records also permit inspection, since their refusal is a refusal ground against your application21 CFR 314.125(b)(17)
Common mistakes
Treating the PAI as a facility audit only
Investigators trace application content down to raw data. A site that looks clean on cGMP but cannot reconstruct the numbers printed in its own submission has handed FDA a separate refusal ground for an untrue statement of material fact.
Leaving contract sites out of readiness planning
CMOs, testing labs, and CROs named in the application are inspectable, and a contract party that will not permit inspection creates a refusal ground against the applicant. The sponsor absorbs the delay, not the vendor.
Rehearsing the site tour instead of the data trail
Teams polish the facility walkthrough and leave the analyst who ran the assay unable to locate the original chromatogram. The distance between the submitted summary and its source record is the thing an investigator is there to measure.
When This Matters
- The PAI is scheduled for the commercial site, so every batch record cited in Module 3 needs to be retrievable in under a minute.
- We cannot file until the CMO agrees in writing to host a PAI.
- That discrepancy between the stability summary and the raw chromatograms is a PAI finding waiting to happen.
Frequently Asked Questions
FDA decides on a case-by-case basis; no regulation requires an inspection for every pending application. In practice it is most likely when the site, product, or process is new to the agency. What is not discretionary is access: an applicant that does not give FDA an adequate opportunity to inspect can have the application refused under 21 CFR 314.125(b)(12).
Related Use Cases
- Pharma Use Cases
Cut NDA and sNDA prep time by 60% with AI-assisted drafting and automated readiness checks
- Biotech Use Cases
Compress IND prep from 8-12 weeks to under 3 weeks with AI-assisted drafting and validation
- Regulatory Affairs Workflows
Cut regulatory intelligence tracking from 10+ hours/week to automated, real-time alerts
- Quality/QA Workflows
Track GxP regulation changes and enforcement trends
