The most reliable starting point for finding FDA device guidance documents is the agency's consolidated Search for FDA Guidance Documents page, which allows keyword queries and filtering by product, issue date, FDA organization, document type, subject, draft or final status, and comment period [1]. For medical devices specifically, CDRH maintains a companion page that links to the main search, Class II Special Controls Documents, withdrawn or expired guidance, proposed guidance development, and instructions for submitting comments [2]. A complete search strategy usually requires more than one query because device-specific guidance and broadly applicable guidance are organized differently. This article explains the named workflow, the technical decision points that affect search results, the limitations of each search surface, and a concrete evaluation example for a hypothetical device.

Start with the consolidated guidance search

The Search for FDA Guidance Documents page is designed as a single location for keyword searching across FDA guidance documents [1]. The table defaults to sorting by issue date, which helps when looking for recently issued guidances, and users can narrow results by product, date issued, FDA organizational unit, type of document, subject, draft or final status, and comment period start and end dates [1]. The page also offers topic browsing collections, including General and Cross-Cutting Topics, Medical Devices, Radiation-Emitting Products, and International Council for Harmonisation documents [1]. For device work, selecting Medical Devices under the Product filter or browsing the Medical Devices topic collection is the first narrowing step.

The main search includes filters for Draft or Final status, Open for Comment, and Comment Closing Date on Draft [1]. These filters matter when a regulatory affairs team needs to distinguish binding final guidance from draft guidance that may still change. The search also exposes a Document Type filter and a Docket Number column, which can help link a draft guidance to its public comment docket [1]. Because the table is the primary interface, users should confirm the content current as of date on the page before relying on a result set; the retrieved page shows a current as of date of 11/19/2026 [1].

Separate special controls from general guidance

FDA has separated guidance searching into two sections based on whether special controls apply: a search specific to Class II Special Controls Documents for particular device types, and a search for other guidance documents [7]. The Class II Special Controls Documents page is now a separate search with a link from the main search page, and it provides guidance documents that mandate special controls [7]. The main guidance search must still be used for standards that apply across many device types, such as biocompatibility, sterilization, software, and cybersecurity, and it also includes Safety and Performance Based Pathway guidance documents [7].

This split creates a practical decision point. A manufacturer working on a Class II device should check both the special controls search for device-specific requirements and the general search for cross-cutting topics [7]. Emergo by UL, a regulatory consulting firm, notes that companies must search both surfaces to avoid missing relevant FDA guidance [7]. The same source reports that during an FDA update, not all browsers were appropriately returning results, and clearing the browser cache or using a different browser may resolve the issue [7].

A suggested workflow for a hypothetical Class II software device

Suppose a regulatory affairs team is preparing a 510(k) for a hypothetical Class II device with software functions. A suggested sequence would be: first, run the product classification search for the device's product code to identify device-specific guidance [7]. Second, open the Class II Special Controls Documents search to check for special controls guidance tied to that device type [7]. Third, run the main guidance search for cross-cutting topics such as software, cybersecurity, and biocompatibility, because these will not appear in the product classification results [7]. Fourth, consult the Medical Device Software Guidance Navigator for software-specific guidances relevant to the submission [3]. Finally, verify the draft or final status and any open comment window for each retrieved document [1]. This workflow is a suggestion, not an FDA requirement, and it does not guarantee that every applicable guidance has been identified.

Use product classification to surface device-specific guidance

FDA has updated its product classification results so that selecting a specific product code includes relevant device-specific guidance documents in addition to recognized consensus standards [7]. Using a suture example, a product classification search returns 31 results, and choosing one product code shows device-specific guidance from both the special controls search and the general guidance search [7]. However, broadly applicable guidance documents such as biocompatibility are not included in the product classification results, in the same way that broadly applicable standards are not included [7].

This means product classification is useful for finding guidance tied to a particular device type but insufficient as a standalone search. A regulatory affairs professional should treat the product code result as one input and then run separate searches for cross-cutting topics that may apply to the device [7]. The Product Code Classification Database is also referenced by FDA as a way to search for guidances specific to medical device product codes [3]. The limitation is explicit: the classification search does not return every guidance that could affect a submission.

Use topic navigators for software and digital health

For medical device software, FDA provides the Medical Device Software Guidance Navigator, a resource designed to help innovators identify FDA guidance documents relevant to software development and marketing submissions [3]. The Guidance Navigator provides a list of commonly applicable guidances across device types and can support preparation of a marketing submission via eSTAR and initial guidance identification throughout the software device development life cycle [3]. Each section contains descriptions and links to FDA guidances and other resources that may be relevant to a corresponding domain area of software development [3].

FDA also maintains a separate page titled Guidances with Digital Health Content, which lists FDA guidances with digital health content and is intended to provide clarity on FDA's regulation of digital health products [8]. The list includes issue date, guidance title, and guidance status, with entries such as Clinical Decision Support Software, General Wellness: Policy for Low Risk Devices, and Cybersecurity in Medical Devices [8]. For questions about whether a product is the focus of FDA oversight or which regulatory pathway may apply, FDA directs users to the Digital Health Policy Navigator and Digital Health Frequently Asked Questions first [3].

Confirm status, comment windows, and withdrawal risk

Guidance documents describe FDA's interpretation of or policy on a regulatory issue under 21 CFR 10.115(b), and they generally do not establish legally enforceable responsibilities [4]. They should be viewed as recommendations unless specific regulatory or statutory requirements are cited, and an alternative approach may be used if it satisfies the applicable statutes and regulations [4]. This legal status means a search result must be checked for whether it is draft or final, and whether it is open for comment, before it is treated as current agency thinking.

Some guidance documents on the search page are indicated as open for comment, and although comments can be submitted on any guidance at any time under 21 CFR 10.115(g)(5), submitting by the closing date helps ensure the agency considers the comment before work begins on the final version [4]. FDA also publishes annual Guidance Agendas listing possible topics for future development or revision, but these agendas do not bind FDA to issue every listed guidance [4]. Withdrawn or expired guidance is tracked separately, and the medical devices page links to a withdrawn or expired guidance collection [2].