solvent differences, elemental impurities from new equipment, bioburden/endotoxin changes for parenteral routes, and functionality-related characteristics (FRCs) for excipients that can alter performance (e.g., microcrystalline cellulose grade, HPMC viscosity). Your dossier must show that these risks are anticipated and controlled, with transparent math and traceable anchors to data tables/figures in Module 3—and, when relevant, to BE/performance evidence in Modules 5 or 2.5.

Because ACTD is a wrapper rather than a new doctrine, you can carry forward harmonized expectations from the International Council for Harmonisation (e.g., Q7 for GMP, Q8/Q9/Q10/Q12 for development, risk, PQS, and lifecycle; Q3A/B/C/D for impurities; Q2(R2)/Q14 for methods) while using the U.S. Food & Drug Administration and the European Medicines Agency as interpretive anchors. In practice, that means: define the change in ICH language, build evidence that a reviewer can re-calc or re-run mentally, and make verification a two-click experience using deep bookmarks and caption-level anchors in your PDFs. If your change story is readable and re-checkable, national format differences won’t slow you down.

What Counts as a “Source Change” and How Reviewers Classify It: Definitions, Risk Categories, and Documentation Signals

API source changes typically include: (1) new or alternate manufacturing site; (2) new synthesis route or significant route modification; (3) different starting materials/critical reagents or catalysts; (4) different crystallization conditions that alter polymorph or particle attributes; (5) new primary packaging for the API (e.g., drum liner resin) with potential for different extractables/leachables; and (6) new contract lab or changed analytical methods for release and stability. Excipient changes include: (1) new supplier or site; (2) new grade with different physical properties (viscosity, particle size, substitution pattern); (3) co-processed excipients; (4) packaging material changes; and (5) shifts that affect FRCs such as flow, compressibility, and swelling, which can alter blend uniformity, tablet hardness/dissolution, or release kinetics in modified-release (MR) systems.

Authorities translate these into major/moderate/minor categories based on potential impact and verifiability. As a rule of thumb, the following tend to classify as major (prior approval): new API route of synthesis, new API site with different equipment class or impurity risks, new excipient with functional impact in an MR matrix, or any change that widens specs without strong process/clinical rationale. Moderate changes (notification type) often include like-for-like API sites within a mature PQS, excipient suppliers with analytical and performance equivalence, or tighter limits backed by capability. Minor changes (post-implementation notification) include document housekeeping and non-functional packaging changes. The dossier must help reviewers make this call quickly by stating the change in risk language, then showing the control strategy—what sits under PQS versus what is locked in the license.

Two documentation signals matter immensely. First, traceability: a map from the changed parameter to the exact places in Module 3 (and, if needed, Modules 2/5) that prove control—spec tables, chromatograms/peak IDs, particle/polymorph characterizations, dissolution/performance studies, and stability plots with prediction intervals. Second, numerical parity: dossier-wide units, decimal rules, and denominator labels so that numbers in summaries and labels are identical to the tables (no re-typing). When those signals are clean, the classification conversation becomes short and favorable, even in countries with strict administrative checklists.

Designing the Evidence Package: API Comparability, Excipient FRCs, Methods/Validation, and Stability That Tell a Coherent Story

Think in four layers of proof. Layer 1—Identity & Impurity Profile: Confirm API identity with orthogonal methods (IR/Raman, NMR where probative), and compare related substances under stress and release conditions. If a synthesis route changes, explicitly address potential genotoxic impurities (route-specific) per contemporary risk frameworks and define control points (limits, purge, or analytical detection). Show elemental impurities risk from new equipment or catalysts and how it is controlled to appropriate limits. Layer 2—Solid-State & Particle Attributes: For BCS II/IV APIs or dissolution-sensitive dosage forms, compare polymorph (XRPD/DSC), particle-size distribution, shape/morphology, and surface area. Link meaningful differences to in vitro performance (dissolution) and, where a control space exists, to the design space that keeps clinical performance invariant.

Layer 3—Excipient Equivalence & FRCs: Demonstrate compendial compliance and functional parity. For binders/film formers (e.g., HPMC), show viscosity and substitution patterns; for fillers (e.g., MCC), show bulk/tapped density and compaction behavior; for lubricants (e.g., Mg stearate), show specific surface area and fatty acid profile; for disintegrants, show swelling kinetics. If co-processed excipients or new grades are involved, present small-scale formulation screens showing blend uniformity, hardness/friability, and discriminating dissolution that detects meaningful shifts. For parenterals, emphasize bioburden/endotoxin profiles and filter compatibility.

Layer 4—Methods & Stability: Clarify whether methods are transferred or new. For new/updated methods, summarize validation per Q2(R2)/Q14—specificity (peak purity/orthogonal), accuracy/precision, range, and robustness—then map each method to the specification attribute it releases (so reviewers see the chain). Build zone-appropriate stability (IVa/IVb common in ACTD) with the limiting attribute clearly identified. If potential exists for performance shifts (e.g., particle growth, excipient moisture sensitivity), include in-use or accelerated/mechanistic studies and commit to ongoing pulls if time points are still maturing. The narrative should culminate in a conservative label claim that you can tighten later with more data.

API via DMF/CEP and the Mechanics of Referencing in ACTD: LOA, Open/Closed Parts, and Supplier Oversight

Many API changes lean on a Drug Master File (DMF) or a CEP-style certificate. Your ACTD package should explain how you reference confidential data and what you are responsible for as the MAH. If you cite a US DMF, include the Letter of Authorization (LOA) and list the specific sections you rely on (synthesis route, controls, stability) while supplying your own drug product comparability (impurity profile at the DP level, performance, stability). If your supplier provides an “open part/closed part” dossier, place the open part in Module 3 and describe how your quality agreement covers the closed part (audit rights, change notification windows, sample retains, reference standards alignment).

For European-style CEPs, state precisely which monograph and options are covered and what is not (e.g., particle-size or polymorph not controlled by the monograph). Where a CEP exists but your dosage form is sensitive to attributes outside the monograph, your DP spec must capture those attributes (e.g., D90, polymorph) and the evidence package must show linkage between API controls and dosage performance. Regardless of the referencing route, the MAH must show supplier oversight: audit schedule and outcomes, change notification clauses (days notice), sample retain/testing triggers, and verifications performed at receipt (ID by FTIR/Raman plus risk-based specific tests for high-risk attributes).

Confidentiality logistics matter in ACTD markets. Some authorities permit direct submission from the API supplier to the agency; others expect the MAH to include sufficient open data within the marketing application. Build a short confidential data plan in your cover letter (“DMF holder will submit under reference X within Y days; we commit to no shipment until acknowledgment is received”). This de-risks queries about missing route details while keeping proprietary content protected.

Excipient Supplier or Grade Changes: From Compendial Compliance to Functional Equivalence, Including MR and Sterile Use-Cases

Excipient changes are often misclassified as “minor” because the material is compendial. In practice, functional equivalence drives risk. Your dossier should separate identity/compliance (pharmacopeial tests, COA match) from performance (FRCs tied to process and product CQAs). Build a compact FRC matrix that lists the property, its role, the acceptable range for your process (e.g., HPMC viscosity 4–6 cP for film former), and the verification study that shows no adverse impact (blend metrics, tablet hardness, dissolution, or IVRT/IVPT where applicable). For MR systems, justify that new grades or suppliers don’t alter release kinetics; discriminating dissolution across media and agitation (and, when relevant, alcohol dose-dumping checks) should be included. For OINDP, show aerodynamic particle size distribution (APSD) equivalence if the excipient touches fluidization or valve behavior.

In sterile products, excipient microbiological quality and endotoxin contribution must be explicit. Show supplier microbiological controls, transport/storage protections, and, if the excipient is used in reconstitution or as a stabilizer, its compatibility with filtration and container–closure systems. If new primary packaging for an excipient is introduced (liners, caps), address extractables/leachables and the potential to alter bioburden. Tie every claim to a table or figure and keep caption-level anchors stable so Module 2 can link directly to proof. This discipline keeps the review focused on risk and control rather than on navigation friction.

ACTD Filing Playbook: Variation Buckets, Module Placement, Country Nuances, and Operational Tactics for First-Pass Acceptance

Classify first, then format. Decide whether the change is major (prior approval), moderate (notification, sometimes with a waiting period), or minor (post-implementation). In your Module 1 cover letter (or national form), state the classification logic in one paragraph using harmonized ICH language (impact on CQAs, control strategy, and clinical performance). Then map where each artifact lives: Module 3 for specs/justifications, methods/validation, stability, and packaging; Module 2.3 for the quality overall summary highlighting the change and the limiting attributes; and (if performance is relevant) Module 2.5/5 for dissolution/BE or IVRT/IVPT. Use leaf titles and ASCII-safe filenames that will remain stable across sequences to make “replace” behavior predictable in portals that don’t use a full XML backbone.

Country nuances. Some ACTD authorities accept CEP-style references readily; others expect more open data inside the application. Several treat IVb long-term stability as the default expectation for hot/humid climates; plan zone coverage accordingly or submit a conservative shelf-life with a commitment schedule. National portals may cap file sizes or enforce filename rules; include a one-page manifest index listing where the decisive proof lives. Where bilingual leaflets or labels are touched (e.g., storage changes), run translation QA with a copy deck and numeric parity checks so that numbers do not drift in the localized text.

Operational tactics. Adopt three lightweight tools: (1) a granularity charter that defines how you split leaves (specs, validation, stability figures) so reviewers land on captions in two clicks; (2) a hyperlink manifest that drives link injection from Module 2 to Module 3 captions and supports a post-pack link crawl; and (3) a leaf-title catalog that freezes names/filenames for lifecycle stability. Add a one-page “What Changed” note: list touched leaves, exact paragraphs/tables affected, and a hash of old vs new files. These publishing habits convert national format differences into minor logistics rather than obstacles.

Strategy & signals for reviewers. Lead with control strategy clarity (which parameters are Established Conditions vs under PQS control), show capability (Cpk/Ppk, trending) when tightening specs, and tie every risk to a verification (PPQ, stability, performance studies). If data are still maturing, declare a commitment and align label claims conservatively. The best indicator that you’ve pitched the change correctly is a reviewer who can reproduce your limit-setting logic or dissolution inference without guesswork. When that is true, first-cycle acceptance becomes the norm rather than the exception.