The U.S. Food and Drug Administration has issued a revised version of Compliance Program 7346.832, Preapproval Inspections, dated 29 June 2026 and effective 10 August 2026. The revision sharpens the agency’s risk-based strategy for deciding whether a preapproval inspection (PAI) is needed at all, restructures how inspections are scoped once they happen, and formally embeds the reorganized Office of Inspections and Investigations (OII) into the roles and responsibilities that govern the program.
For any facility named in a pending NDA or ANDA, this is the document that determines whether FDA shows up at the gate before approval, and what the inspection team will look at when it does.
Why This Revision Matters
Compliance Program 7346.832 is the operating manual FDA staff follow when evaluating manufacturing facilities in support of pending drug applications. It is not guidance for industry in the formal sense, but it functions as one of the most practical inspection readiness references available, because it tells manufacturers exactly what investigators are instructed to cover, which findings belong on a Form FDA 483, and which deficiencies trigger a withhold recommendation that blocks approval.
The 2026 revision has two stated aims: to make a prompt decision on the need for an inspection, and to promote efficient conduct of the inspections that do occur. Behind both sits the same principle FDA has pushed since the Pharmaceutical Quality for the 21st Century initiative: concentrate inspectional resources where product and facility risk actually lives, and use alternative tools everywhere else.
The Risk-Based Inspection Decision
When a marketing application is submitted, CDER assembles an integrated quality assessment (IQA) team consisting of a drug substance assessor, a drug product assessor, an OPMA manufacturing assessor, an inspection team lead, and a preapproval program manager (PAM). The IQA team determines the need for a PAI based on a cumulative risk assessment of the application, built on two pillars.
- Product and manufacturing risk. The manufacturing operations described in the application are compared against what has previously been evaluated or inspected at the facility, including profile codes, compliance status, inspection history, hazard signals such as recalls, complaints, field alert reports and MedWatch reports, and the complexity of both the process and the product.
- Accuracy and reliability of the application. A PAI can be triggered specifically to confirm the accuracy and reliability of quality data submitted in the application, or to confirm that the facility’s actual operations match what was filed.
Within 60 calendar days of receiving an NDA or ANDA, OPMA must either request a PAI through the CDER Informatics Platform with a clear, risk-based justification, or enter a facility recommendation without one. If OII’s own evaluation suggests an inspection is not warranted, the final determination is made jointly with OPMA, and the PAM must document the reason within 10 business days.
Alternative Tools Get Equal Billing
The revised program elevates alternative tools from a pandemic-era workaround to a standing element of the decision tree. Where the risk assessment supports it, FDA may rely on:
- Inspection reports from trusted foreign regulators obtained through Mutual Recognition Agreements with the EU, the United Kingdom, and Swissmedic, or under other confidentiality agreements.
- Records requests under section 704(a)(4) of the FD&C Act, used in lieu of or in advance of a PAI to support assessment of a pending application.
- Remote interactive evaluations (RIEs), voluntary remote assessments using livestreamed video, teleconferencing, and screen sharing.
FDA is explicit that remote regulatory assessments are not inspections within the meaning of section 704(a)(1) and do not satisfy the statutory inspection requirement under section 510(h). But for preapproval purposes, information gathered through these tools can answer the inspection question outright, or narrow the objectives of an on-site visit before anyone travels.
Inspection by Objectives: What Is Mandatory and What Is Risk-Based
The four familiar PAI objectives remain: readiness for commercial manufacturing, conformance to application, data integrity audit, and commitment to quality in pharmaceutical development. What the revision changes is the coverage model.
Objective 1 is now broken into five sub-objectives, and only some of them are mandatory on every inspection. The rest are switched on by risk factors that the IQA team communicates to the inspection team in writing before the inspection begins.
| PAI Objective | Coverage under the revised program |
|---|---|
| Objective 1a: Readiness evaluation of capabilities, changes, deviations, and trends | Covered on every PAI. |
| Objective 1b: Sampling, testing, and release programs, including supplier qualification | Risk-based. Triggered where the application assessment or previous facility information (inspections, RRAs) identified issues. |
| Objective 1c: Facility and equipment controls against contamination | Risk-based. Triggered by never-inspected facilities, new buildings or equipment, major changes, or products requiring special containment. |
| Objective 1d: Batch release, change management, investigations, and FDA reporting procedures | Risk-based. Triggered by no prior coverage, quality system changes since the last inspection, or previously identified deficiencies. |
| Objective 1e: Feasibility and scientific justification of the proposed commercial process and batch record | Covered on every PAI. Depth varies with the extent of process validation activities and application assessment issues. |
| Objective 2: Conformance to application | Covered on every PAI. |
| Objective 3: Data integrity audit | Covered on every PAI. Depth varies with inspectional findings. |
| Objective 4: Commitment to quality in pharmaceutical development | Covered on the initial PAI, periodically thereafter based on risk, and after major changes to the quality system, management team, or corporate structure. |
The practical consequence for manufacturers: the inspection you receive is increasingly a mirror of your own history. Facilities with clean prior coverage, stable quality systems, and no application assessment concerns can expect narrower PAIs. Facilities with new buildings, new equipment, recent quality system changes, or prior findings should expect the corresponding sub-objectives to be in scope, and should prepare accordingly.
Data Integrity Remains Non-Negotiable
Objective 3 stays mandatory on every PAI. Investigators are instructed to compare raw data, whether hardcopy or electronic chromatograms, spectrograms, and analyst notebooks, against the summary data filed in the CMC section.
The program lists the classic indicators: substitution of passing data for failing data, improper invalidation of out-of-specification results, exclusion of lots from stability programs, backdating of stability results, fabrication of results without testing, and manufacturing operations that do not match the filed application, including production at undisclosed shadow facilities.
Where a pattern of data reliability issues emerges, the inspection team lead is directed to consider expanding coverage to marketed products under Compliance Program 7356.002, and OII may recommend that CDER invoke the Application Integrity Policy. Significant data integrity problems remain the first-listed ground for a withhold recommendation.
See Also: Data Integrity and Data Governance in GMP
Withhold Recommendations and the Process Validation Exception
Part V lists thirteen example grounds for a withhold recommendation, including serious CGMP concerns with biobatch or exhibit batch manufacture, significant differences between pivotal clinical and exhibit batch processes, incomplete master production records, lack of manufacturing capacity, failed full-scale process performance qualification without appropriate corrective changes, significant stability failures, unjustified non-reporting of failing data, and delaying, denying, limiting, or refusing an inspection.
One long-standing principle is restated clearly: a withhold recommendation will not be made solely because commercial-scale process validation is incomplete at the time of the PAI. Stage 1 process design data must be available and defensible, and the firm must achieve a high degree of assurance before distribution, but finishing Stage 2 process performance qualification is not a precondition for a facility approval recommendation. Where a firm claims Stage 2 is complete, however, investigators are instructed to fully audit those studies and conclusions.
Related Article: Process Validation in Pharmaceutical Industry
ICH Q12 and Established Conditions Move Into Inspection Scope
The revision integrates the ICH Q12 lifecycle management framework into inspectional practice. Where an applicant proposes established conditions (ECs) and reporting categories in a product lifecycle management document, the OPMA manufacturing assessor will request written coverage of the development studies supporting those ECs before the inspection starts.
Investigators are directed to verify that the change management system assesses the need for new or revised ECs and that procedures exist to determine appropriate reporting categories. A deficient change management system can lead the IQA team to request a higher reporting category than the applicant proposed, a direct commercial consequence of an inspectional finding.
Scheduling, Notification, and Timelines
Several timelines are worth noting for planning purposes:
- For original NDAs, FDA’s goal is to notify the facility at least 60 days before the PAI, and no later than midcycle, where the inspection must coincide with manufacture of the application product.
- FDA nonetheless reserves the right to inspect at any time during the review cycle, announced or not.
- If inspection planning has started and the establishment is not ready, it must provide a written explanation from a responsible official, along with a date of availability. Lack of readiness is itself a listed ground for a withhold recommendation.
The PAM enters the facility recommendation no later than 20 business days after the inspection closes and, in all cases, before the user fee goal date.
Related Article: How to Prepare for Unannounced Global Audits
What Manufacturers Should Do Now
The revised program rewards facilities that can demonstrate, with documentation, that they are ready before FDA decides whether to come. Practical priorities before the 10 August 2026 implementation date:
- Assume the data integrity audit and conformance-to-application review will happen and rehearse them: reconcile filed CMC descriptions, batch records, and analytical methods against what is actually in use on the floor and in the laboratory.
- Map your facility risk profile against the Objective 1 triggers: new construction, new equipment, quality system changes, and prior findings all pull additional sub-objectives into scope.
- Ensure Stage 1 process validation data, scale-up studies, and the scientific justification for the proposed commercial batch record are inspection-ready, with a documented timeline for remaining validation activities.
- Prepare for remote regulatory assessments as seriously as for on-site inspections. A 704(a)(4) records request or an RIE may now be the inspection, and the quality of the response can determine whether an on-site PAI follows.
- If your application uses ICH Q12 tools, verify that the development data supporting each established condition are retrievable and that the change management system can withstand scrutiny.
Compliance Program 7346.832 has always been required reading for anyone preparing a site for a preapproval inspection. The 2026 revision makes it something more: a clear statement that FDA intends to inspect less often, decide faster, and look harder where it does go. Facilities that understand the risk logic behind that decision hold the advantage.
Final Takeaway
FDA’s revised Preapproval Inspection Compliance Program 7346.832 does not alter the PAI’s basic purpose. FDA still needs assurance that the facility can manufacture the product under the application and that the submitted data are accurate, complete, and reliable. What changes is the inspection logic.
FDA is moving toward faster, more targeted, and more risk-based facility decisions. Some PAIs may be avoided or narrowed through prior inspection history, foreign regulator reports, records requests, or remote evaluations. But where FDA does inspect, the scope is likely to be more focused on known risks, application concerns, and the facility’s own quality history.
For manufacturers, the strongest position is not simply to prepare for “an FDA inspection.” It is to understand why FDA may inspect, which objectives are likely to be triggered, and whether the application, quality system, validation package, and site operations tell the same story.
