The Workbench · Craft
A 505(b)(2) application is defined by a right it lacks
This blog has already covered how a device master file lets FDA read a supplier's confidential data without ever handing it to the sponsor who relies on it. A right of reference or use, defined in FDA's own drug regulations, runs the opposite direction: it doesn't wall the data off from the applicant who needs it, it hands that applicant the authority to rely on it directly, on terms a named owner has to sign. And the one drug-approval pathway built around not having that authority carries the gap right in its own name.
What the regulation actually grants
21 CFR 314.3(b) defines “right of reference or use” as the authority to rely upon, and otherwise use, an investigation for the purpose of obtaining approval of an application — including the ability to make the investigation's own underlying raw data available for FDA's audit, if necessary. That's a grant over someone else's completed clinical work, not a confidentiality arrangement like a device master file's. An applicant holding this right isn't limited to whatever summary the data's owner is willing to disclose informally; the right reaches the raw data itself, on the terms the regulation sets, because the whole point of defining the right is to settle what an applicant is allowed to do with an investigation it didn't run.
The authorization has to come signed, from the owner
Holding access to a study isn't the same as holding the right to use it in a submission. 21 CFR 314.50 requires an applicant that has obtained a right of reference or use for a clinical investigation to include, in the application itself, a written statement signed by the person who owns that data, authorizing the specific reference being made. The letter does similar work to a device master file's own Letter of Authorization — a signed document that unlocks someone else's work for a named application — but the applicant ends up holding use-rights over the investigation itself, not waiting on a reviewer to consult a file it never sees.
505(b)(2) is named for the right it doesn't have
A 505(b)(2) application is, by its own regulatory definition, one where the applicant hasn't obtained a right of reference or use from the person who conducted at least one investigation its approval needs. Rather than filing a signed authorization for that missing piece, a 505(b)(2) applicant leans on a different authority: FDA's own prior finding that an already-approved listed drug under section 505(c) is safe and effective, filled out with whatever published literature or additional studies the applicant does hold full rights to. The pathway isn't a shortcut around needing rights to data — it's defined by exactly which rights the applicant is proceeding without, and which of the agency's own prior findings is standing in for them instead.
Each listed drug carries its own patent duty
Borrowing FDA's finding on a listed drug isn't a blanket pass on everything attached to that drug's own approval. 21 CFR 314.54 requires a 505(b)(2) applicant to identify each listed drug it's relying on, and the patent certification that would attach to an ordinary application referencing that drug attaches separately, drug by drug. A 505(b)(2) file leaning on FDA's findings for three different listed drugs owes three separate patent certifications, not one statement covering the submission as a whole.
Most files are a mix, not an either-or
None of this makes a 505(b)(2) application an all-or-nothing filing. A single submission routinely carries some investigations the applicant holds a full, signed right of reference for, some published literature it can cite without owning any rights to the underlying data at all, and one or more listed-drug reliances filling the gap the applicant's own data doesn't close. What makes the application a 505(b)(2) rather than a standard 505(b)(1) NDA is that at least one necessary piece comes from that third category — not that every piece does. A submission plan that treats the pathway as a single blanket status, rather than a line-by-line account of which category each piece of evidence falls into, loses the distinction the regulation is actually drawing.
Where this meets the file
A 505(b)(2) submission-readiness record needs each relied-upon piece tracked on its own line: which investigations the applicant holds a signed right of reference for, which listed drug's FDA finding is standing in for the ones it doesn't, and the patent certification that listed drug carries into the file. A worksheet built around that structure, alongside the launch catalog's other submission-readiness templates, is previewed there now. If your program tracks right-of-reference dependencies differently, the shelf takes that correction directly.
The Regulatory Toolkit launches soon — a free shelf of source-mapped templates, checklists and browser-only tools for regulatory teams. Get one email when it opens, or contribute a template.