How to Submit a Public Comment on FDA Draft Guidance

Most substantive draft FDA guidance opens for public comment before it’s finalized, and almost nobody outside the regulated industry realizes that anyone can weigh in — not just the companies the guidance will eventually apply to. Submitting a comment doesn’t require a law degree or a trade association letterhead. It requires reading the draft closely enough to say, in plain language, what specific part of it doesn’t work and why.

In brief

Good guidance practices at 21 CFR 10.115 set the process: most substantive draft guidance gets a public comment period before it’s finalized, announced through a Federal Register notice and posted alongside the guidance itself.
Comments go to the specific docket named in that notice, filed through regulations.gov — not emailed to FDA directly. The docket number is usually printed on the guidance document’s own cover page.
A comment doesn’t need to come from a company or a trade association. An individual practitioner pointing at one specific section, with a specific proposed fix, is often more useful to FDA than a general objection filed on letterhead.
FDA reads comments and may revise the draft before finalizing it, but isn’t obligated to adopt any of them. Read how to read the finished guidance once it publishes to see which comments, if any, changed the text.

What makes a comment worth reading

The comments that get engagement cite a specific section number and quote the specific sentence that doesn’t work, rather than objecting to the guidance in general. Describe a concrete scenario the wording doesn’t handle well — “under this language, a Special 510(k) covering a labeling-only change would be unclear about which testing section applies” — and propose the specific alternative wording you’d use instead. A comment that only argues the underlying policy is wrong, without engaging the text, gives FDA nothing concrete to change.

The mechanics of actually filing one

Find the docket number in the Federal Register notice or on the guidance document’s cover page, then search for it directly on regulations.gov rather than the guidance topic generally — a general search often surfaces the wrong docket. Comment periods are typically open for a defined window stated in the notice; once it closes, the formal channel closes with it, though a genuinely important gap can sometimes still be raised through a citizen petition, which is a much higher bar. You can submit as an individual, and you can choose whether your name is attached publicly — either way, the comment becomes part of the public docket once it’s submitted.

Where this goes wrong

Commenting on the policy instead of the text

Arguing that a policy is a bad idea, without pointing at the specific wording that implements it, doesn’t give a reviewer anything they can act on.

Missing the window

Once a guidance is finalized, the comment mechanism that produced it is closed. A criticism that shows up after finalization has no functional channel until the next revision cycle, if there is one.

Assuming it doesn’t matter because you’re not a company

A practitioner’s comment naming exactly where a section reads unclearly in practice is a distinct and genuinely useful category of input — it doesn’t need a company’s name attached to matter.

Guidance documents are nonbinding, but they shape how reviewers actually apply the rules for years afterward. The comment period is the one formal point where the people who’ll live with that wording get to argue with it before it sets.

Sources & further reading

21 CFR 10.115 — Good guidance practices ecfr.gov
regulations.gov — Search dockets and submit public comments regulations.gov
Regulatory Academy — How to Read an FDA Guidance Document regulatoryacademy.com
Regulatory Academy — How to Read a Federal Register Notice 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.