Most people meet FDA’s rules through a guidance document first, because guidance is written to be read: plain sentences, worked examples, a clear table of contents. The regulation underneath it is not written that way, and the statute underneath that is older and drier still. That order of exposure quietly trains a habit — citing the guidance as if it were the rule — that eventually gets someone in trouble, because a guidance document is not binding on anyone, and was never meant to be.

Guidance is a paraphrase, not the source

FDA writes guidance documents to explain how it currently interprets and intends to apply a regulation or statute — a narrative, often with examples, aimed at being readable by people who are not lawyers. Good Guidance Practices, codified at 21 CFR 10.115, say this directly: guidance documents do not establish legally enforceable responsibilities, and a company may use an alternative approach if it satisfies the requirements of the underlying statute and regulations. In practice that means a guidance document is FDA’s best current explanation of the rule, not the rule itself, and a citation to the guidance is a citation to someone’s paraphrase. Our guide to reading a guidance document covers that skill on its own terms; this one is about the layer underneath it.

Start with the definitions, then trace the cross-references

Pick almost any CFR part FDA administers and the pattern repeats: Subpart A opens with scope and definitions before Subpart B gets to substance, because a term used loosely five sections later usually has a specific meaning fixed at the top of the part. Skipping that section is the single most common way to misread a regulation confidently. From there, regulations lean heavily on cross-reference — a requirement in one section frequently only makes sense once you have followed the citation to the section it modifies or an exception it carves out. eCFR makes both of these cheap: definitions are usually one click from wherever you land, and every section carries its own Source note showing the Federal Register citation and date of the text currently in force, which is the fastest way to confirm you are not reading something that has since been amended. The same literal, cross-reference-aware reading matters when the text in front of you is enforcement correspondence rather than a regulation; see how to read an FDA warning letter for that adjacent skill.

A five-minute routine before you trust a citation
  1. Open the part’s definitions section first, even if the term you care about seems obvious.
  2. Check the verb. “Shall” or “must” in a regulation binds; “should” or “we recommend” in guidance does not, however confident the sentence sounds.
  3. Check the section’s Source note on eCFR to confirm the text is current and see when it last changed.
  4. Follow any cross-referenced section before relying on your reading — the exception is often two clicks away, not in the sentence you are looking at.
  5. If a guidance document is the thing you are actually citing, say so, and note its own disclaimer that alternative approaches are permitted.

Two habits that turn a confident reading into a wrong one

Citing the guidance as if it were the rule

A guidance document is easier to quote in a meeting than the regulation is, so it gets quoted as though it settles the question. It explains FDA’s thinking; it does not bind FDA or you, and treating it as though it does gives up a legitimate, defensible alternative approach without anyone deciding to.

Reading a section in isolation

A single section rarely carries its full meaning alone. Skipping the definitions at the top of the part, or the cross-referenced exception two sections over, produces a reading that is confident and wrong in a way that is hard to catch later, because it never felt uncertain in the first place.

Sources & further reading

  1. 21 CFR 10.115 — Good guidance practices, including the nonbinding status of guidance documents ecfr.gov
  2. 21 CFR 807.3 — Definitions used throughout the premarket notification part, a working example of a part’s definitions section ecfr.gov
  3. 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, regulatory, or career advice.