FDA New Drug Applications · Section 505(b)(2)
The 505(b)(2)
Pathway
A Faster, Lower-Risk NDA
Built on Evidence That Already Exists
A Faster, Lower-Risk NDA
Built on Evidence That Already Exists
505(b)(2) is a full New Drug Application — the same approval, the same label rights as any NDA — but it relies in part on data the applicant never generated: FDA's prior findings of safety and effectiveness for an already-approved drug, or published literature. You bring the studies that address what is genuinely different about your product and lean on the established record for everything that is not. Done well, it removes years and much of the cost of a de novo program without lowering the bar for approval.
The pathway fits a product that is meaningfully different from an approved drug, but not so different that the evidence base has to be built from scratch. If your change is one of these, 505(b)(2) is usually the route worth modeling first.
A modified-release version, a new excipient system, or an improved delivery of an approved active ingredient.
Moving an approved molecule from oral to injectable, or to a topical, inhaled, or ophthalmic route.
A different dose, a new titration, or a dosing schedule the reference label never covered.
Two approved actives combined into a single product, where each component's record already exists.
A new use for an approved drug, supported by targeted studies rather than a full development program.
Moving a prescription product to over-the-counter status on the strength of its established profile.
A 505(b)(2) application is assembled from three streams of evidence. Knowing which of your conclusions each stream can carry — and exactly where a gap forces a new study — is the whole of the strategy.
The new data you generate to characterize what is different: the reformulation, the new route, the added indication. This is the part you fund and run — and the part we work to keep as small as the science allows.
The Agency's own previous conclusions of safety and effectiveness for an approved listed drug. You may rely on them without a right of reference and without the originator's underlying data or permission.
Peer-reviewed studies robust enough to support a specific conclusion, cited in place of a study you would otherwise have to repeat yourself.
Reliance is only permitted when you can show it is scientifically justified. The bridge — usually a comparative bioavailability or pharmacokinetic study, sometimes a limited safety study — is what connects your product to the listed drug and earns the right to lean on its record. Underscope it and you invite a first-cycle complete response letter. It is the single most common way these programs stall.
Establishes that your product and the listed drug are similar enough for FDA's prior findings to apply to yours.
Bridging strategy is a pre-IND decision, not a late one. It determines which studies you can drop and which you cannot.
Most avoidable 505(b)(2) complete response letters trace to a bridging package that asked the Agency to rely on more than it could support.
Because 505(b)(2) lives inside the Hatch-Waxman framework, it comes with both a reward and an obligation that an entirely in-house program never has to weigh. Plan for both from the first meeting.
A 505(b)(2) approval can earn three years of exclusivity for the change that required new clinical investigations, and in some cases five-year new-chemical-entity or seven-year orphan-drug exclusivity. Structured deliberately, it protects the specific improvement you invested in.
Because you reference a listed drug, you must address the patents in the Orange Book — certifying, under Paragraphs I through IV, that each is expired, does not apply, or is invalid or not infringed. A Paragraph IV certification can trigger litigation and a thirty-month stay. This is planned at the start, not discovered at filing.
It is easiest to understand the pathway against its neighbors. 505(b)(2) occupies the middle ground — more than a generic copy, less than a full de novo application.
Every safety and efficacy conclusion rests on studies the applicant conducted or has a right to reference. The route for a genuinely new molecule with no relevant precedent to build on.
A full NDA that leans on FDA's prior findings and published literature for the established parts, with new studies only for what is different. It yields its own approval, its own label, and its own exclusivity.
A duplicate of an approved drug — same active ingredient, strength, route, and labeling — demonstrating bioequivalence. No new clinical data, and no independent label of its own.
The sequence matters more than any single task. Each decision constrains the next, and the expensive mistakes are the ones made early and discovered late. We run it in this order, with FDA alignment built in before the spend.
Confirm the change genuinely fits 505(b)(2), then select the listed drug and literature the application will rely on — the decision everything downstream inherits.
Take the reliance and bridging strategy to FDA early, so the Agency agrees the approach before you commit to studies.
Design the comparative study that justifies reliance, scoped precisely to carry the argument and no further.
Generate only the manufacturing and nonclinical data the change actually requires; cite the established record for the rest.
Compile the eCTD, document every point of reliance, and file the Orange Book patent certifications correctly the first time.
None of these are science problems. They are strategy problems — treating a reliance NDA like either a generic or a de novo program when it is neither.
Building on a reference product whose record does not actually cover the conclusions you need, so the reliance collapses under review.
Asking FDA to rely on more than a thin bridging study can justify — the leading cause of a first-cycle complete response.
Treating Orange Book patent certification as paperwork, then meeting a Paragraph IV surprise or a thirty-month stay at filing.
Assuming bioequivalence is enough. A 505(b)(2) still owes an NDA's safety and efficacy argument for everything that is new.
Overlooking unexpired exclusivity on the reference drug that blocks approval or even submission, regardless of how strong your data is.
Designing the whole program before FDA has agreed the reliance strategy, then rebuilding it after a costly pre-NDA meeting.
The judgment here is bought with reps: knowing which listed drug a division will accept, how much a bridge has to carry, and where a patent certification will bite. Your leads are senior regulatory practitioners who have chosen the reference drug, negotiated the bridging strategy with FDA, and assembled the applications that cleared.
We know what FDA's prior findings can and cannot carry, and where reliance quietly runs out.
We scope the bridging study to exactly what the argument needs — neither a gap nor wasted spend.
Orange Book certifications, exclusivity, and the thirty-month stay, planned before they can surprise you.
We stay past strategy into the eCTD assembly and the review responses that decide the outcome.
A reliance NDA touches the rest of the regulatory program. These are the services 505(b)(2) sponsors reach for most, and where a designation strategy connects to the wider path to market via our regulatory submissions and accelerated pathways work.
The pre-IND and pre-NDA meetings where a reliance strategy is agreed or unravels, prepared so your scarce agency interactions land.
Explore Meetings →The manufacturing story for a reformulated or combination product, built to the standard a 505(b)(2) review applies.
Explore CMC →NDA assembly, eCTD publishing, and the documented reliance that a 505(b)(2) filing lives or dies by.
Explore Submissions →Tell us about your product, the change you are making, and the approved drug you would build on. We will assess whether 505(b)(2) fits and match you with a senior regulatory lead, with a response within one business day. All inquiries are strictly confidential.
