Every FDA guidance document says the same strange thing about itself: that it contains nonbinding recommendations, does not establish legally enforceable responsibilities, and describes only the agency’s “current thinking.” New readers see that disclaimer and relax. Practitioners read the same words and lean in — because a published map of the agency’s current thinking is the most useful document a regulator will ever hand you for free. The skill is knowing how to take one apart.
What a guidance actually is
Under 21 CFR 10.115, guidance documents are how FDA communicates its interpretation of the law it enforces — without making new law. The regulation binds; the guidance explains how the agency currently reads the regulation. That distinction sounds academic until you sit on either side of a review. The reviewer’s questions come from somewhere, and much of the time they come from the guidance you decided was optional.
So the professional posture is neither obedience nor dismissal. A guidance is evidence — the best available evidence — of what the agency will expect of your file. You can meet the expectation, or you can do something different and be ready to show your alternative satisfies the requirement. What you cannot do is be surprised by it.
The terms, precisely
- Draft guidance
- Issued for public comment, marked “not for implementation.” It tells you where the agency’s thinking is heading. Some drafts stay drafts for years while reviewers quietly absorb their logic — which is why practitioners read them anyway.
- Final guidance
- The agency’s current thinking, in force as an expectation. Check the date and whether it supersedes an earlier document — the cover page tells you.
- “Should” versus “must”
- In guidance, “must” marks a statutory or regulatory requirement being restated; “should” marks the agency’s recommendation. A “should” you skip without a reasoned alternative is a review question you scheduled for yourself.
- The docket
- Every guidance has one. The public comments — and the agency’s responses when finalising — show you exactly where industry pushed back and what the agency refused to move on.
The one-hour method
- The cover page. Draft or final, issuing center, date, and what it supersedes. Thirty seconds that prevent the classic error of studying a superseded document.
- The scope. Is your product inside it — and read the exclusions twice. Out of scope means the recommendations are not about you, however relevant they sound.
- The definitions. Guidance terms are load-bearing. Words you think you know often carry a narrower defined meaning that changes the recommendations downstream.
- The recommendations, as a table. Turn every “should” into a row: comply, propose an alternative, or not applicable — each with a one-line rationale. This table is the artifact; the reading was just how you built it.
- The docket. Skim the comments. Where industry objected and the agency held firm, you have found the expectations it considers non-negotiable.
The table in pass four is what separates reading from studying. A guidance read passively produces a feeling of familiarity that evaporates in the meeting. A guidance reduced to rows — expectation, your position, your rationale — produces the document your team will actually argue from, and the reviewer will recognise the structure, because it mirrors how the questions will come at you: one expectation at a time.
Where readers go wrong
Treating “nonbinding” as “optional”
The disclaimer is a statement about legal force, not about review behaviour. The reviewer’s checklist is built from the guidance. Skipping a recommendation without a documented alternative does not make the expectation disappear; it makes the deficiency letter longer.
Reading the recommendations without the scope
Half the misapplied guidance in circulation comes from readers who started at section four. The scope and definitions decide whether the rest of the document is even talking about your product.
Ignoring drafts because they are drafts
A draft is not enforceable — and it is still the clearest signal you will get of where expectations are moving. Programmes that plan multi-year development against only the final guidance are planning against the past.
Sources & further reading
- 21 CFR 10.115 — Good guidance practices ecfr.gov
- FDA — Search for FDA guidance documents fda.gov
- Regulatory Academy — The 510(k) Pathway, a free five-lesson course regulatoryacademy.com
This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal or regulatory advice.
