FDA guidance documents tell you what the FDA currently thinks. They do not tell you what you must do. Understanding that distinction, and knowing how to work with it rather than around it, is one of the more practically useful skills in regulatory affairs.
Good Guidance Practices (GGPs), codified at 21 CFR 10.115, are the FDA’s own rules for how it develops, issues, and uses guidance documents. For regulated industry, understanding GGPs means understanding how FDA signals its current thinking, when that thinking is open to challenge, and how to engage with the process before guidance becomes entrenched practice.
These 10 tips are for regulatory affairs professionals, quality managers, submissions specialists, and anyone whose work is shaped by what FDA guidance says or doesn’t say.
1. Know the difference between guidance and regulation before you act on either
Per 21 CFR 10.115, guidance documents represent the agency’s current thinking on a regulatory issue but do not establish legally enforceable responsibilities and are not binding on FDA or the public. Regulations, by contrast, have the force of law. This distinction matters practically: failing to follow a binding regulation is a legal violation. Failing to follow guidance may draw inspection attention, but you have the right to use an alternative approach if it satisfies the applicable statute or regulation.
2. Distinguish Level 1 from Level 2 guidance before deciding how to engage
FDA categorises guidance into two levels. Level 1 guidances address new or significant regulatory requirements, complex scientific issues, or highly controversial topics. They are typically preceded by a draft open for public comment before FDA finalises and implements them. Level 2 guidances address existing practices or minor changes in interpretation and are implemented without prior public comment, though they are still posted publicly and open to comment at any time.
This distinction affects your engagement strategy. If FDA issues a draft Level 1 guidance that would materially affect your submissions, manufacturing, or labelling processes, that draft comment period is your primary opportunity to shape the final document. Level 2 guidance shifts are easier to miss because they arrive without a public notice period.
3. Comment on draft guidances with specific, documented alternatives, not general objections
FDA reviews and considers all comments on draft Level 1 guidances in preparing the final version, as required by 21 CFR 10.115. A comment that says “this approach is too burdensome” is much less effective than one that says “the draft recommends X; we propose Y as an alternative that achieves the same public health objective because…” and then provides the supporting rationale and data.
FDA also accepts proposed draft guidance documents, not just comments on existing drafts. If your organisation has identified a regulatory gap where guidance is absent, submitting a proposed draft guidance (rather than just a general topic request) gives the agency a concrete starting point and positions your organisation’s perspective within the document’s development.
4. Use FDA’s guidance agendas as forward intelligence
FDA Centers and Offices publish annual Guidance Agendas listing topics they are considering for guidance development or revision in the coming year. These agendas are publicly available and represent the clearest advance signal of where regulatory policy is heading before it arrives in a final document.
Regulatory teams that read guidance agendas as part of their annual planning cycle can begin preparing for regulatory shifts months or years before they become final guidance requirements. This is particularly valuable in fast-moving areas like cell and gene therapy, AI in manufacturing, and novel drug delivery systems, where FDA is actively developing new guidance frameworks.
“We review every Center’s guidance agenda in Q1. It saves us from being surprised when a draft comes out, and it tells us where to pre-invest in our quality documentation before FDA formally signals expectations.”
5. When taking an alternative approach to guidance, document your rationale thoroughly
The right to use an alternative approach is real and codified in 21 CFR 10.115: “You can use an alternative approach if the approach satisfies the requirements of the applicable statutes and regulations.” FDA’s guidance documents state this explicitly in their standard header language. The practical question is how to exercise that right without triggering unnecessary inspection friction.
The answer is documentation. A deviation from FDA guidance without documented rationale creates an inspection question (“why didn’t they follow the guidance?”) that an inspection team cannot answer from the record. A deviation from FDA guidance with a clear, scientifically grounded rationale demonstrating that the alternative approach satisfies the regulatory requirement gives the inspector something to evaluate rather than something to cite.
6. Treat “FDA’s current thinking” as exactly that: current
Guidance documents can be revised, withdrawn, or superseded. A compliance programme built around the expectation that guidance represents a permanent, stable framework can be disrupted when FDA updates its thinking, particularly in response to new scientific evidence, public health events, or policy shifts. FDA revised its GGP practices during the COVID-19 public health emergency by issuing Level 1 guidances for immediate implementation without prior comment, which was within its regulatory authority but moved faster than industry was accustomed to.
Set up notifications for FDA guidance updates in your product and program areas. The FDA guidance search database allows filtering by date and program area. Checking it monthly is not excessive for active development programs.
7. Read guidance documents for what they don’t say as much as for what they do
Silence in a guidance document is not the same as FDA having no view. Areas where no guidance exists may still have applicable regulations, existing enforcement precedents, or informal agency positions communicated through other mechanisms (meeting minutes, advisory committee discussions, warning letters). Regulatory teams that treat absent guidance as absent expectation can encounter inspection findings that reference standards they did not know applied.
Conversely, areas where guidance is specific and long-standing typically represent the highest-confidence picture of what FDA expects. In those areas, the rationale for an alternative approach needs to be proportionally stronger.
8. Use the FDA guidance search database systematically, not just when drafting submissions
Many regulatory professionals search for guidance documents when preparing a specific submission or response, but the guidance database is also a monitoring tool. FDA’s December 2024 Report and Plan on Best Practices for Guidance noted that FDA has significantly increased the number of guidance documents it publishes annually as part of its transparency initiative. That increase means new guidance is arriving more frequently across more program areas.
A scheduled monthly review of guidance publications in your product area takes less time than responding to an inspection finding that traced to guidance you missed. The FDA guidance database at fda.gov/regulatory-information/search-fda-guidance-documents allows filtering by product area, date, and status (draft vs. final).
9. Understand how guidance interacts with inspection and enforcement
21 CFR 10.115 includes inspection and enforcement policies among the topics that guidance documents may address. This means that guidance can, and regularly does, describe what FDA inspectors will examine, how they will interpret what they find, and what will be characterised as an objectionable condition. Guidance documents covering inspection procedures are particularly important for inspection readiness, because inspectors will use the agency’s current thinking about what “compliant” looks like as part of how they assess a facility.
At the same time, even in an inspection context, a facility that followed an alternative approach and documented sound scientific rationale for that approach has a defensible position. The defensibility depends entirely on whether the rationale was captured before the inspection, not constructed during it.
10. Engage the process at every stage, not just when guidance affects you negatively
FDA’s GGP framework explicitly welcomes public participation: commenting on draft guidances, suggesting topics for new guidance, submitting proposed draft documents, and participating in public meetings and advisory committee reviews. Most regulated companies engage this process only reactively, when a draft guidance creates a problem they need to address.
Proactive engagement, suggesting guidance on topics where you have seen regulatory inconsistency, submitting data to support a scientific position in a draft comment, or proposing a new guidance topic in an underserved area, builds a relationship with the agency and shapes the regulatory environment in ways that benefit the industry and ultimately patients.
| Common mistake | What to do instead |
|---|---|
| Treating guidance as binding regulation | Identify the applicable CFR section; use guidance as FDA’s current interpretation of that regulation, not as the regulation itself |
| Ignoring draft guidances during comment periods | Treat Level 1 draft comment periods as strategic opportunities; submit specific, data-supported alternatives, not general objections |
| Using an alternative approach without documenting the rationale | Document before deviating: scientific rationale, regulatory basis, and evidence that the alternative satisfies the applicable statute/regulation |
| Assuming silence in guidance means no requirement exists | Check applicable regulations, enforcement precedents, warning letters, and advisory committee records for areas where guidance is absent |
| Not monitoring guidance updates systematically | Set up a monthly guidance database review for your product and program areas; subscribe to Federal Register notices |
CDER’s Guidance Snapshot Pilot is worth bookmarking for drug development teams. It provides visual, plain-language summaries of selected cross-cutting guidance documents on drug development topics, and was specifically designed by FDA to increase engagement with guidance on innovative trial design and development approaches. For any organisation working on clinical development, it is a lower-burden entry point into guidances that otherwise require significant reading time.
For organisations that regularly engage FDA in formal meetings (Type B, Type C, INTERACT meetings), the positions you take in meeting briefing documents and FDA’s responses become an informal record of FDA’s application of guidance to your specific situation. These responses are not binding either, but they represent the most specific signal of FDA’s thinking about your program and product that is available short of an approval decision. Tracking and filing them systematically is as important as tracking guidance document changes.
If your organisation manufactures products in multiple FDA-regulated categories, remember that GGPs and the guidance infrastructure are consistent across FDA (21 CFR 10.115 applies to all Centers), but each Center has its own guidance agenda, update cadence, and priority areas. CDER, CDRH, CBER, CFSAN, and CVM all publish separate annual guidance agendas. Monitoring all of them at once is feasible only with a systematic process, and is worth building one.
Sources
- eCFR, “21 CFR 10.115: Good Guidance Practices”
- FDA, “Background: FDA Good Guidance Practices”
- FDA, “Guidances” (search database and overview)
- FDA, “Food and Drug Administration Report and Plan on Best Practices for Guidance” (December 2024)
- Federal Register, “Administrative Practices and Procedures; Good Guidance Practices” (September 2000)
- Federal Register, “FDA’s Draft Report and Plan on Best Practices for Guidance” (January 2024)
- FDA, “Opportunities for Input into Guidance Development”
- FDA, “2011 Report on Good Guidance Practices: Improving Efficiency and Transparency”