FDA Pre-Approval Inspections: Timing After NDA/BLA Submission and How Facilities Are Selected

FDA pre-approval inspections: when they happen and how FDA picks the facilities

When a sponsor files an NDA or BLA, the manufacturing sites named in the Chemistry, Manufacturing, and Controls (CMC) section become candidates for a pre-approval inspection (PAI). A PAI is not an automatic, uniform event triggered by the filing itself. FDA runs the program (Compliance Program 7346.832, Pre-Approval Inspections) as a risk-based exercise: the agency decides whether to inspect, which sites to cover, and how deeply, based on the totality of information it has about each facility and the application ⁶⁴⁹¹³⁷⁰⁷²⁵⁴⁶⁰. This article walks through what the PAI is designed to accomplish, when in the review cycle it is scheduled, and the factors that determine which facilities get a reviewer at the door.

What the PAI is meant to accomplish

The compliance program frames the PAI around a set of inspectional objectives, and the depth of coverage for each objective scales with risk. Some objectives are covered on every PAI; others are covered only when specific risk factors or inspection findings warrant it ⁶⁴⁹¹³⁷⁰⁷²⁵⁴⁶⁰. The core objectives are:

Readiness for commercial manufacturing. Determine whether the establishment has a quality system designed to achieve adequate control over the facility and its commercial manufacturing operations ⁵⁶⁵⁸⁸⁹.
Conformance to the application. Verify that the formulation, manufacturing and processing methods, analytical methods, and batch records at the site are consistent with the CMC section of the application ⁵⁶⁵⁸.
Data integrity audit. Audit and verify the raw data behind the product to confirm the CMC data are accurate, complete, and reliable ⁸⁶⁸⁹⁸⁵⁶¹⁸⁸.

The program also identifies a fourth objective, commitment to quality in pharmaceutical development, and it integrates the PAI with the application assessment so that product-quality issues can be identified and resolved as part of the review ⁸⁶⁸⁹⁶⁴⁹¹.

Which facilities are in scope

Any establishment named in the application and relevant to the objectives above can be inspected. That includes drug substance (API) and drug product manufacturing sites, associated laboratory and testing capabilities, and packaging-related activities ⁹⁵⁹⁶⁵⁶⁵⁸⁶⁴. Coverage extends to the components and materials that define product quality: APIs, in-process materials, finished product, containers and closures, and supplier qualification ⁵⁶⁵⁸⁶⁴. FDA can expand coverage to additional areas of a site based on risk and the facility's role in the application ⁶⁴.

In practice a single application can pull in several distinct sites, each evaluated on its own merits. The compliance program's language reflects both API establishments and finished-dosage establishments as separate coverage categories, along with the labeling and packaging materials tied to them ⁹⁵⁹⁶⁸⁵.

When the inspection happens in the review cycle

The filing alone does not schedule an inspection. The sequence in the compliance program runs roughly as follows:

Post-submission risk assessment. After the application is submitted, CDER's Integrated Quality Assessment (IQA) team assesses the application's risk and decides whether a PAI is needed. If it is, the team recommends the inspection and communicates the specific quality risks and concerns to the inspection team ⁷³⁷⁵.
Inspection planning. Before any on-site work, the inspection team reviews the CMC section, relevant Drug Master Files, and the IQA feedback, then builds an inspection plan tailored to the product and the facility ⁷⁰⁷².
District file review, where used. CDER's Office of Pharmaceutical Manufacturing Assessment (OPMA) can issue a request for a district file review to ORA, which must respond within 10 business days ⁷⁴.
On-site inspection. The PAI is conducted for the specified application(s); significant deficiencies are discussed with the firm and may be listed on a Form FDA 483 ⁷³⁷⁵.
Post-inspection assessment. The IQA team reviews the inspection findings, the 483, the Establishment Inspection Report, and the firm's responses; OPMA makes the final facility recommendation ⁷³⁷⁵.

The whole process is deliberately woven into the review clock so that the facility decision supports a timely action on the application. The program states that FDA coordinates these efforts to meet PDUFA and GDUFA performance goals ⁷. On the front end, FDA aims to inspect early, well before the user-fee goal date; for original NDAs the program describes notifying the facility of a planned inspection at least 60 days in advance and no later than mid-cycle when the product will be manufactured during the inspection window ²³. If planning has begun and a site is not ready, the firm is expected to submit a written explanation and an available date ²³.

The PDUFA performance reports reinforce that inspection activity is managed within the review timeline rather than tacked on at the end. FDA commits to informing applicants of the planned review timeline, including the internal mid-cycle meeting date ⁹¹¹¹⁵¹⁶, and in recent cycles reported work under an "enhancing inspection communication for applications" commitment, including revised PAI compliance-program communication language and guidance on alternative tools to assess manufacturing facilities named in pending applications ⁸¹⁰¹³. The reports do not, however, fix a single calendar rule tying the inspection date to the action date; timing remains risk- and readiness-driven ⁸¹⁰¹³.

What determines which facilities actually get inspected

This is the heart of the question, and the answer is a risk-based determination made for each named site. FDA weighs whether it already has enough information to assess the facility without an on-site visit. If it does, a PAI may not be warranted, and the agency can use other tools in advance of or in lieu of a PAI, such as a Section 704(a)(4) records request or a remote regulatory assessment (RRA) ⁵³⁶²⁵⁴⁶⁰.

The factors that push toward (or expand) an inspection include:

Inspection and surveillance history. A systems-based CGMP inspection may be added when the establishment appears on CDER's site surveillance inspection list generated by the risk-based site selection model ²³. FDA also considers the site's overall compliance status and prior inspection or RRA findings ⁵³⁶⁴⁶⁵.
For-cause concerns. A pending or issued for-cause inspection can prompt added CGMP coverage ²³.
Application-specific manufacturing risk. FDA evaluates whether the site is ready to manufacture as described in the application, using a risk-based approach that considers the firm's change-management system and lifecycle controls ⁷.
New or changed facilities, equipment, and processes. New construction or facility design, new uses of existing equipment (for example, adding a highly potent product), equipment operations unique to the application, and significant changes to material or personnel flow all warrant coverage ⁵⁶.
Contamination and cross-contamination risk. Highly potent or potentially sensitizing products draw particular attention because of cross-contamination concerns ⁵⁶.
Concerns surfaced during the assessment. Inspectional concerns collected during the IQA application assessment feed directly into the inspection plan ²³.
Findings during the PAI itself. If findings on-site indicate the need to look at marketed products, FDA can expand coverage accordingly ²³.

How the inspection outcome feeds the approval decision

The PAI is a gate on approval, not a standalone event. When there are no significant issues, the site earns an "acceptable" (approve) recommendation ⁴⁵⁴⁷⁴⁸⁴⁹. When significant deficiencies would adversely affect the establishment's ability to perform its designated functions in the application, the site draws a "withhold" recommendation ⁴⁵⁴⁷⁴⁸⁴⁹.

Issues that can drive a withhold include significant data-integrity problems; serious CGMP concerns with biobatches, pivotal clinical, exhibit, or validation batches; significant process differences from the application; inadequate master production record instructions; insufficient capacity; failure to meet application commitments; a failed full-scale process performance qualification; no demonstration of reliable commercial-scale manufacture of the critical quality attributes; and incomplete or unsuccessful analytical method validation ⁴⁵⁴⁷. Data-reliability and stability problems, and refusal or delay of an inspection, can also support a withhold posture ⁴⁴⁵⁵. When a withhold is issued, OPMA and ORA review the EIR, the 483, and the firm's responses; a later approve recommendation depends on satisfactory correction of the findings that led to the withhold, and a follow-up inspection may be required ⁴⁴⁴⁶.

The practical takeaway for regulatory teams

For a sponsor, the operational implications are straightforward. Every manufacturing, testing, and packaging site named in the CMC section is a potential inspection target, and the sites most likely to be inspected are those that are new to FDA, have an unfavorable or stale surveillance history, carry a for-cause flag, or introduce novel or high-risk manufacturing (new construction, unique equipment, highly potent products, significant changes to flow) ²³⁵⁶⁵³⁶⁴⁶⁵. Because FDA aims to inspect early and integrates the facility decision into the review timeline, site readiness should be treated as a mid-cycle deliverable rather than an end-of-review scramble, and CMC filings should match what a reviewer will find on the floor ²³⁷. Where FDA already has current, favorable information, a records request or remote assessment may substitute for an on-site PAI, so a clean, recent inspection record is itself a way to reduce inspection exposure ⁵³⁶²⁵⁴⁶⁰.