The Workbench · Craft
A shortage notice runs on 506C, not a fine
This blog has already looked at what a supply-chain mechanism asks a trading partner to produce on a fixed clock, in DSCSA’s package-level system, and at the clock a distributed defect starts running once it’s found, in a field alert report’s three-working-day window. Section 506C of the Act runs its clock the opposite way around: instead of reacting to a problem already in the field, it asks a manufacturer to warn FDA before the problem — a shortage — exists at all.
The duty is advance notice, not disclosure after the fact
21 U.S.C. 356c requires the manufacturer of certain drugs to notify FDA of a permanent discontinuance or an interruption in manufacturing likely to lead to a meaningful disruption in supply, and it wants that notice at least six months before the discontinuance or interruption — or as soon as practicable, if six months isn’t possible. The statute isn’t asking for a shortage report. By the time an actual shortage shows up on FDA’s own public list, the notice this section asks for was supposed to have already happened.
Not every drug carries the duty
The obligation attaches to drugs that are life-supporting, life-sustaining, or intended for use in the prevention or treatment of a debilitating disease or condition, along with drugs FDA designates as critical to public health during a declared emergency. The statute carves out radiopharmaceuticals and any other product FDA separately designates as exempt. A manufacturing change to a drug outside that scope doesn’t trigger 506C at all, however disruptive the change is to that manufacturer’s own operations. The determination sits with the manufacturer in the first instance — nothing in the statute requires FDA to pre-clear a drug’s covered status before the six-month clock starts, which means a manufacturer that guesses wrong about scope finds out only when FDA actually reads the notice, or the silence where one should have been.
The enforcement tool is a letter, not a fine
Section 356c(f) doesn’t give FDA a civil penalty to assess against a manufacturer that skips the notice. What it gives FDA is a noncompliance letter: FDA sends one when a manufacturer fails to provide required notice, the manufacturer gets 30 calendar days to respond in writing, and FDA has to post both the letter and the manufacturer’s response publicly within 45 days, redacting only genuinely confidential information. The agency’s own annual shortage report to Congress lists which manufacturers received a noncompliance letter that year. Public disclosure, not a dollar figure, is the entire enforcement mechanism this section runs on.
Devices got a parallel section, not a shared one
The CARES Act added a separate provision for devices in 2020, codified at section 506J rather than folded into 506C — a deliberate choice that keeps the drug and device shortage-notification duties textually distinct even though they share the same six-month, “as soon as practicable” structure. FDA’s guidance implementing 506J has its own revision history, most recently a January 2025 update, independent of whatever guidance covers the drug-side duty. A tracker that treats “shortage notification” as one undifferentiated obligation has merged two provisions that run on separate statutory text and separate guidance documents.
The output is a list FDA keeps current, not a one-time report
FDA maintains a public drug shortage database built from exactly this reporting duty — a drug that’s been the subject of a timely 506C notice shows up there well before most of the market notices a supply problem, and a drug that recovers is tracked back out of shortage against the same data. The database is the visible end product of a requirement that otherwise runs entirely between a manufacturer and FDA.
Where this meets the file
A shortage-notification tracker that records only whether a notice was sent has nowhere to put the two facts that actually decide how exposed a manufacturer is: whether the drug falls inside 506C’s covered scope at all, and whether the notice went in before the six-month mark or only “as soon as practicable” after it slipped. A notification-tracking template that keeps a drug’s covered-scope determination, its notice date, and the six-month deadline it ran against as separate required fields is previewed in the launch catalog alongside this week’s other drug-lifecycle templates. If your program tracks 506C exposure 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.