How to read a Drug Master File

A Drug Master File gets talked about like an approval — “we have a DMF for that excipient,” said the way you’d mention a certification. It isn’t one. A DMF is a submission that sits in FDA’s files doing nothing on its own; the agency doesn’t review it, approve it, or disapprove it until a specific application asks FDA to look at it. And even then, the sponsor making that application never gets to read what’s inside.

What a DMF is for

A Drug Master File lets a manufacturer share confidential information about a drug substance, an excipient, packaging, or a production facility with FDA once, instead of handing it to every company that wants to reference it. An active pharmaceutical ingredient supplier that wants several different sponsors to be able to point FDA toward its manufacturing process doesn’t have to disclose that process to any of them. It discloses the process to FDA, once, in a DMF, and then authorizes each sponsor to reference it for their own application. FDA holds the information and uses it when evaluating the referencing application — the supplier’s customers never see it, and don’t need to.

The four types that remain

21 CFR 314.420 originally described five types of DMF. FDA eliminated Type I — manufacturing site, facility, and personnel information — in a final rule published January 12, 2000, and folded that content into the types that remained. Four are still accepted. Type II covers a drug substance, a drug substance intermediate, or the materials used to prepare either, as well as the finished drug product itself. Type III covers packaging materials. Type IV covers an excipient, colorant, flavor, or essence, or the materials used to prepare one. Type V covers FDA-accepted reference information that doesn’t fit the other three, nonclinical study data most often. None of the four function as a standalone application; a DMF cannot substitute for an IND, NDA, ANDA, or export application on its own.

Why the Letter of Authorization is the part that matters

Having a DMF number from a supplier tells you almost nothing by itself. What makes it usable is the Letter of Authorization — the document the DMF holder files that tells FDA which applicant may reference the DMF, which sections of it apply, and who the holder will notify if the DMF’s content changes. Without a current LOA naming your specific application on file, FDA has no instruction to open the DMF for your review; the DMF existing is not the same as FDA being allowed to use it. Confirming the LOA is in place, current, and correctly scoped is closer to regulatory affairs’ actual job here than anything involving the DMF’s content, which you’ll typically never see. The mechanics of that document are covered in how to read a Master File Letter of Authorization.

The DMF relationship usually starts on the manufacturing side, not in regulatory affairs’ own filings — one more reason it’s easy to treat as background noise until a submission’s timeline depends on it. How regulatory affairs works with manufacturing covers more of that handoff. The habit worth building either way is simple: a DMF reference is only as good as the authorization behind it, and that authorization is the one thing worth confirming before you count on it.