The guidance isn't in the Federal Register.

A Federal Register entry titled “…; Guidance for Industry; Availability” reads, at a glance, like the guidance. It names the topic, states an abstract, and gives a docket number to comment against. It is tempting to treat that abstract as the guidance’s content. It is not the guidance at all — it is the notice that one now exists.

Two acts, not one

FDA’s good guidance practices rule, 21 CFR 10.115, does not let a guidance document arrive as a single act. Once FDA prepares one, the rule calls for FDA to publish a notice in the Federal Register announcing that the document is available, and separately, to post the guidance document itself online. A draft guidance follows the same two-step pattern. The notice and the document are two different publications, required by two different steps of the same regulation, and only one of them is what the Federal Register API actually returns.

What the notice carries, and what it doesn’t

The Federal Register’s own API is generous with structure: title, publication date, the docket and regulation-identifier numbers to comment against, the CFR parts it touches, and an abstract — usually a paragraph naming the topic and stating that recommendations exist. None of that is the recommendations themselves. The guidance’s scope, its testing expectations, the definitions of the terms a submission will be measured against — that content lives in the PDF the notice links to, on fda.gov, exactly where 21 CFR 10.115 requires FDA to post it, and it is not reproduced in the notice or its abstract at any length.

A structured feed of Federal Register notices is a feed of pointers. Reading the pointer instead of what it points to is the fastest way to summarize a guidance document without having read it.

The practice

Treat a guidance-availability notice as an event, not a source: it tells a team that a document exists, whether it arrived as draft or final, which CFR parts and which docket it touches, and — for a draft — that a comment window is open. None of that substitutes for opening the PDF before it informs a submission strategy; what a specific recommendation means for a specific device is a judgment for a regulatory professional reading the actual document, and that judgment, like every reading in Signals, is regulatory intelligence and method, never regulatory advice on its own.

FDA Radar ingests the Federal Register notice the day it publishes — title, dates, docket, CFR references, draft-or-final stage — and links straight to FDA’s own posting of the guidance itself; see what we monitor and how often for the rest of the pipeline. It does not fetch or rewrite the guidance PDF’s content, and it does not claim to: that document is the one part of this pipeline that stays exactly where FDA published it.