PAI & PLI Readiness Toolkit
A pending drug or biologics application can be delayed or withheld on the strength of one facility inspection. This toolkit decodes the FDA Pre-Approval Inspection (PAI) and the biologics Pre-License Inspection (PLI), maps each inspection objective to the readiness it demands, and sequences the work into five phases you can run against the date on your calendar.
What a toolkit is not
A toolkit is a readiness playbook SPEQ assembled, not a regulator’s checklist and not a guarantee of an outcome. Working through it is not evidence of readiness; your own quality system decides that.
What a Pre-Approval Inspection is
A Pre-Approval Inspection (PAI) is FDA’s on-site evaluation of a manufacturing facility named in a pending drug marketing application — an NDA or ANDA, covering both drug substance (API) and drug product sites — conducted under FDA Compliance Program 7346.832, Pre-Approval Inspections. Its purpose is to determine whether the facility can be recommended for approval to manufacture the product described in the application.
The statutory hook is section 505(d) of the Federal Food, Drug, and Cosmetic Act: FDA may withhold approval of an application if the methods, facilities, and controls used for manufacturing, processing, and packing are inadequate to preserve the drug’s identity, strength, quality, and purity. The PAI is how that judgement is made on the ground. Compliance Program 7346.832 was substantially revised, issued June 29, 2026 and implemented August 10, 2026 — cite the version in force, not a remembered one.
What a Pre-License Inspection is — and how it differs
For a biologics licence application (BLA), the corresponding inspection is the Pre-License Inspection (PLI), conducted by the Center for Biologics Evaluation and Research (CBER) under Compliance Program 7345.848, Inspection of Biological Drug Products. Its legal basis is section 351 of the Public Health Service Act, under which a biologics licence issues only when the product is shown to be safe, pure, and potent and the facility meets standards designed to assure those attributes.
The readiness disciplines overlap heavily with the drug PAI — conformance to the application, data integrity, and commercial-scale control are common ground — but the PLI adds biologics-specific scrutiny: control of the biological manufacturing process and cell banks, viral and microbial safety, comparability across process changes, and potency assays. This toolkit’s phases apply to both; where a step is biologics-specific it is called out.
What triggers an inspection, and what the outcomes are
Not every application draws an inspection. The decision is risk-based, weighing the facility’s inspection history, the product’s risk and novelty, and whether recent coverage already supports the application. A site with a strong recent record and no new risks may be approved on the surveillance history alone.
The inspection produces a recommendation into the application assessment — essentially "approve" or "withhold" — informed by the district/ORA classification of the inspection: No Action Indicated (NAI), Voluntary Action Indicated (VAI), or Official Action Indicated (OAI). An OAI classification, or unresolved data-integrity findings, will hold an approval until they are addressed. Observations are issued on a Form FDA 483 at the close of the inspection.
Can the site actually make this product at commercial scale as described — equipment, utilities, personnel, procedures, and a functioning quality system? In the 2026 revision this objective is expanded into several sub-objectives, some assessed at every inspection and others triggered by identified risk. SPEQ reading: this is where facility qualification, process validation status, and the maturity of your quality system are on the line.
Official name — FDA Compliance Program 7346.832 (rev. June 29, 2026). Reading is SPEQ synthesis.
Does what the site actually does match what the application says — formulation, manufacturing process, in-process controls, batch records, analytical methods, and facilities as filed? SPEQ reading: every CMC claim in the submission needs an on-site record owner who can show the real process matches the filed one, with change control explaining any drift.
Official name — FDA Compliance Program 7346.832 (rev. June 29, 2026). Reading is SPEQ synthesis.
Are the data underpinning the application — submission/pivotal batch records, stability data, and analytical raw data — accurate, complete, and consistent with what was submitted? SPEQ reading: this is an ALCOA+ audit of the specific data that support the filing; audit trails, original records, and access controls on the relevant systems are the exposure.
Official name — FDA Compliance Program 7346.832 (rev. June 29, 2026). Reading is SPEQ synthesis.
Added in the 2026 revision: the program now assesses how well the pharmaceutical development program is supported, defined, managed, and continuously assessed for effectiveness — a quality-management-maturity lens on development itself. SPEQ reading: this rewards a science- and risk-based development story (QbD, a justified control strategy, knowledge management) and exposes development run as a box-ticking exercise.
Official name — FDA Compliance Program 7346.832 (rev. June 29, 2026). Reading is SPEQ synthesis.
SPEQ’s sequenced readiness synthesis across 5 phases, from first baseline to the post-inspection decision. Each phase carries its checklist and the record that proves each item was done.
Confirm the inspection scope, map the application against the facility, and run an internal data-integrity audit of the pivotal data.
- Confirm whether the application is likely to draw a PAI or PLI, and which sites and unit operations are in scopeEvidence: A documented scope assessment naming the covered facilities, dosage forms, and API/DS sites
- Reconcile every CMC claim in the application against an on-site record owner who can produce the underlying recordEvidence: A CMC-to-record traceability matrix with a named owner per claim
- Run an internal data-integrity audit of the submission/pivotal batch records, stability, and analytical raw dataEvidence: A DI audit report scoped to the filed data, with findings and CAPAs
- Verify the process validation (PPQ) status of the commercial process and the honesty of any "in progress" claimsEvidence: PPQ protocols/reports or a defensible plan with dates for outstanding batches
- Confirm facility, utility, and equipment qualification covering the in-scope operations is currentEvidence: Qualification summary and requalification status for the relevant systems
- For a PLI: confirm cell-bank characterisation, viral/microbial safety, and comparability documentation are completeEvidence: Cell-bank records, viral-safety package, and comparability reports across process changes
- Assemble the quality-system evidence for the four inspection objectives (Readiness, Conformance, Data Integrity, Development quality)Evidence: An objective-mapped evidence index pointing to the source records
- Inspection scope and covered sites are documented and agreed
- Every filed CMC claim has an identified on-site record owner
- The internal DI audit of the pivotal data is complete with CAPAs opened
Close the gaps, and verify that batch records, methods, and specifications actually conform to the filed application.
- Drive the P1 gaps and DI-audit CAPAs to closure with evidence, not just plansEvidence: Closed CAPA records with effectiveness evidence where the timeline allows
- Verify master and executed batch records match the process as filed, including in-process controls and limitsEvidence: Batch-record-to-application conformance review with discrepancies resolved through change control
- Confirm analytical methods are validated/verified and match the filed methods and specificationsEvidence: Method validation reports and a specification-to-application reconciliation
- Ensure every deviation and change touching the filed process is closed or has a defensible statusEvidence: Deviation and change-control logs for the in-scope process, current and reconciled
- Confirm the control strategy and development rationale (Objective 4) are documented and available on siteEvidence: A control-strategy document traceable to development understanding (QTPP, CQAs, CPPs)
- Verify data-integrity controls on the relevant systems: audit-trail review, access control, and original-record retentionEvidence: Audit-trail review records, access recertification, and retention evidence for the in-scope systems
- For a PLI: close comparability and potency-assay gaps and confirm biological-process controlsEvidence: Comparability conclusions and validated potency-assay records
- Filed process, methods, and specifications are verified to conform to the application
- DI controls on the systems holding pivotal data are demonstrably operating
- PPQ status is honest and defensible for every in-scope process
Run a mock inspection against the objectives, and stand up the document room, SME roster, and front/back-room protocol.
- Run a mock inspection structured against the four CP 7346.832 objectives (and the PLI additions where relevant)Evidence: A mock-inspection report with findings mapped to each objective
- Prepare and rehearse subject-matter experts on their systems, with a named backup for eachEvidence: An SME roster by system with backups and dry-run notes
- Stand up the front-room / back-room protocol, scribe roles, and a request-tracking logEvidence: A documented inspection-management plan and a tested request log
- Assemble the document room: filed application, validation packages, and objective-mapped evidence, retrievable on requestEvidence: A document-room index with retrieval tested against sample requests
- Define the escalation path and the rule for handling draft vs. controlled documents before a request arrivesEvidence: A written escalation and document-provision policy briefed to the team
- Confirm the CAPAs from the mock are closed or owned before the window endsEvidence: Mock-finding CAPA log with owners and dates
- The mock inspection is complete and its findings are being closed
- SMEs, scribes, and the front/back-room protocol are rehearsed
- The document room is assembled and retrieval-tested
Daily inspection discipline: request tracking, a scribe on every session, end-of-day reconciliation, and clear escalation.
- Log every investigator request with a timestamp, owner, and status, and reconcile it dailyEvidence: A live request-tracking log reviewed at each end-of-day meeting
- Keep a scribe in every session capturing what was asked, shown, and saidEvidence: Contemporaneous scribe notes filed by session
- Provide controlled copies with a document-provision log; never volunteer draft or working documentsEvidence: A document-provision log listing every item given to the investigator
- Hold a daily end-of-day reconciliation to align on open requests, likely observations, and next-day prioritiesEvidence: Daily reconciliation minutes with actions
- Escalate anything touching data integrity or a potential objectionable condition immediately, per the defined pathEvidence: Escalation records showing timely routing to quality leadership
- Every request is logged, owned, and answered or scheduled
- Each session is scribed and reconciled the same day
- Any DI or serious concern was escalated when it arose
Respond to any Form FDA 483 completely and on time, and track every commitment to closure through the application decision.
- Respond to any Form FDA 483 promptly and completely — FDA states it will consider a written response received within 15 business days before assigning a final inspection classificationEvidence: A dated 483 response addressing each observation with corrections, corrective actions, and timelines
- For each observation, distinguish immediate corrections from systemic corrective actions and give realistic datesEvidence: A commitment register separating correction from corrective action, with owners and due dates
- Provide evidence of completed corrections and interim controls where actions are still in progressEvidence: Attached objective evidence for closed items; interim-control descriptions for open ones
- Track every commitment to closure and be ready for a classification update or follow-upEvidence: A living commitment tracker maintained through the application decision
- The 483 response is complete and submitted within the window FDA considers before classification
- Every commitment has an owner, a date, and a tracking mechanism
- Correction vs. corrective action is distinguished for each observation
Template outlines are free; editable downloads require the Professional entitlement.
- FDA Compliance Program 7346.832 — Pre-Approval Inspections (rev. June 29, 2026; implemented August 10, 2026) ↗
- FDA (CBER) — Pre-License Inspections for Biologics: What Industry Should Know ↗
- FDA — Compliance Programs (CBER), including 7345.848 Inspection of Biological Drug Products ↗
- FD&C Act § 505(d) — grounds to withhold approval of an application ↗
SPEQ is not affiliated with the FDA. Program identifiers and dates are cited from the primary sources above and were verified before publish; the phased playbook and objective readings are SPEQ synthesis.
Is a Pre-Approval Inspection guaranteed for every NDA or ANDA?
No. The decision to conduct a PAI is risk-based. FDA weighs the facility’s inspection history, the product’s risk and novelty, and whether recent surveillance coverage already supports the application. A site with a strong recent record and no new risks may be approved without a new pre-approval inspection.
How long do we have to respond to a Form FDA 483?
FDA states it will review and consider a written response to a Form FDA 483 that is received within 15 business days of the inspection close before it assigns a final inspection classification. Responding completely within that window is therefore the practical deadline — address each observation with corrections, corrective actions, and realistic timelines, and continue tracking commitments to closure afterward.
Does this toolkit cover biologics?
Yes. Biologics licence applications (BLAs) are inspected under the Pre-License Inspection (PLI) program — FDA Compliance Program 7345.848, run by CBER under section 351 of the Public Health Service Act — which is a separate program from the drug PAI. The readiness disciplines overlap heavily, so this toolkit’s phases apply to both; biologics-specific steps (cell banks, viral safety, comparability, potency assays) are called out where they arise.
What changed in the 2026 revision of Compliance Program 7346.832?
The program was substantially revised, issued June 29, 2026 and implemented August 10, 2026. It now frames the inspection around four objectives — adding "Commitment to Quality in Pharmaceutical Development" to the long-standing Readiness for Commercial Manufacturing, Conformance to Application, and Data Integrity Audit — and expands the readiness objective into several sub-objectives, some assessed at every inspection and others triggered by identified risk. Always work from the version in force.