A drug master file is referenced, not approved

This blog has already drawn the line a borrowed right sits on, in what a 505(b)(2) applicant proceeds without, and looked at the device-side version of a confidential supplier file, in a device master file that stays the supplier’s secret. A drug master file runs on a similar confidentiality logic, but its own mechanics — how a sponsor actually gets access to one, and what FDA does with it once an application cites it — are specific enough to the drug side that the device-side file is a poor guide to them.

FDA never rules on a drug master file by itself

21 CFR 314.420 lets a holder submit a drug master file (DMF) to FDA so it can either incorporate the information into the holder’s own IND or marketing application, or let another firm’s application cite it without the holder ever handing that firm the underlying data. Submitting a DMF isn’t required by law or regulation — it’s a voluntary mechanism a manufacturer uses specifically to keep its process or formulation confidential from the customer who’s buying it. FDA doesn’t approve or disapprove a DMF on its own, and it never issues a standalone action letter for one. The content only gets reviewed once an IND, NDA, ANDA, or BLA actually cites it, and the review happens inside that application’s own clock, not on a separate DMF timeline.

Five types narrowed to four in 2001

FDA originally recognized five DMF types. Type I, covering a facility’s manufacturing procedures and personnel independent of any specific product, was eliminated by a final rule effective in 2001; FDA stopped accepting new Type I filings and updates to existing ones. What’s left are Type II, for a drug substance, drug substance intermediate, or the material used to make them; Type III, for packaging material; Type IV, for an excipient, colorant, flavor, or similar material; and Type V, for FDA-accepted reference information that doesn’t fit the other three. An API manufacturer filing to keep its synthesis route confidential from the formulator buying its material is filing a Type II DMF — the category this post is mostly about, though the mechanics below apply across all four surviving types.

The letter of authorization is the only door in

A DMF holder has to submit a signed letter of authorization (LOA) naming the specific applicant, and for a Type II DMF, matching the referencing application’s product name, dosage form, strength, and application number. Without that LOA on file, FDA won’t connect the application to the DMF at all, no matter how precisely the applicant’s submission cites the DMF number. What the LOA buys the applicant is narrower than it sounds: the applicant gets to say “see DMF #XXXXX” in its own filing, but the DMF holder’s underlying data stays with FDA’s reviewers and never reaches the applicant’s own file. Only the agency ever sees both sides of the application at once.

A DMF has to stay current, or it stops doing its job quietly

314.420 requires a DMF holder to keep the file current and to notify FDA of relevant changes, and a holder that limits an authorization to particular products has to keep that list of authorized persons accurate as it changes. Falling behind on that upkeep doesn’t produce a rejection letter the way a lapsed registration might — it produces a DMF that’s quietly out of step with what a pending application assumes it says, discovered only when FDA’s reviewer actually opens the file behind someone else’s citation.

GDUFA III lets a Type II DMF get assessed before the ANDA that cites it even exists

A final guidance FDA issued in October 2024 implements a GDUFA III commitment letting a sponsor request an early assessment of certain Type II DMFs up to six months before the ANDA or prior-approval supplement that will cite them is actually submitted. The request still needs at least one LOA naming a pre-assigned ANDA number and proof the DMF holder has paid its GDUFA DMF fee. The pre-ANDA assessment doesn’t change the underlying rule that FDA reviews a DMF only in support of an application — it just lets that support start running on a clock that opens before the application it’s supporting has a filing date.

Where this meets the file

A supplier-qualification file that records a DMF number as though it were a credential the supplier holds has missed what actually makes the arrangement work: the current LOA naming this specific applicant, the application number it’s tied to, and the date the DMF was last confirmed current. A DMF-reference tracking template that keeps those three facts as separate required fields — distinct from the DMF number itself — is previewed in the launch catalog alongside this week’s other drug-lifecycle templates. If your program tracks a DMF reference differently, the shelf takes that correction directly.