The issue date printed inside an FDA guidance document and the 'Content current as of' date on its webpage describe different publication events. For example, the Clinical Decision Support Software guidance is issued January 29, 2026, and its webpage displays the same current-as-of date [1][4]. These are guidance publication and webpage dates, not device clearance or approval decisions. A document's issue date, revision history and supersession statement help identify the version being cited; the webpage date and retrieval timestamp record the online source examined. A reliable capture process preserves these fields separately. This article describes that process and a worked documentation example.
Why the printed issue date is the anchor
Inside a guidance PDF, FDA places a short statement near the title, such as 'Document issued on January 29, 2026' for the Clinical Decision Support Software guidance [1]. That date is tied to the agency's issuance event. When a revision occurs, the same title block is updated, and the document often names the prior version, as the Computer Software Assurance guidance does when it says the February 3, 2026 document supersedes the September 24, 2025 version [2]. A reader storing only the web crawl date would miss that the document text changed on a specific day.
A second internal signal is the guidance history table. The CDS guidance contains a table implemented beginning January 2026 showing January 2026 revisions, with a minor correction to delete a reference to time-critical decision-making for alignment with the January 6, 2026 update [1]. The table also notes that previous guidance history may not be captured in totality. That table records the agency's description of what changed and when. It can distinguish a major revision from a minor correction, a difference that the landing page timestamp alone cannot communicate. The issue date therefore belongs to the document's issuance lineage, while the page date belongs to web publication infrastructure.
The 'content current as of' line is not an issuance date
On the search and guidance landing pages, FDA attaches a separate indicator. The Clinical Decision Support Software page shows 'Content current as of: 01/29/2026' [4]. The general guidance search page uses the same pattern, with a 'Content current as of' value of 11/19/2026 [5]. This marker refers to when the web content was refreshed, not when FDA completed a new review or issued a new decision. It can align with a PDF issuance date, as the matching January 29, 2026 values suggest for the CDS document [1][4], but a team should not assume alignment is reliable without checking both places.
A minimal submission summary format
One workable template would contain four separate fields: the document title, the printed issue date from the PDF, the landing page capture date, and the 'content current as of' value from the page [4][7]. The Study Data Technical Conformance Guide shows a comparable structure: an October 2026 cover date and a revision history with dated version summaries [7]. For a revision scenario, a fifth field could hold the supersession language, such as the February 3, 2026 note that replaces the September 24, 2025 version in the Computer Software Assurance guidance [2]. This format keeps the issue date distinct from the source update date without imposing new testing or validation work.
A complete capture might look like a row for the CDS guidance: issued date January 29, 2026 in the PDF, landing page current as of January 29, 2026, and the history table noting a January 2026 minor correction [1][4]. The row would not assert that the two dates are related; it would simply preserve both values as found. The eCTD v4.0 Technical Conformance Guide offers another example: a June 2026 cover date and a revision history listing dated version summaries [6]. That precision is what auditors can follow later, and what a collapsed 'last updated' field would obscure.
A capture workflow for regulatory affairs documentation
A pragmatic sequence is to first retrieve and freeze the PDF, recording the document issue date and the supersession statement from the first page [1][2]. Second, extract the guidance history table if one exists, so the revision date and the agency's description sit next to the printed issue date [1]. Third, capture the landing page with its own retrieval timestamp and 'current as of' value [4]. At no point should the analyst overwrite the printed date with the page date, or combine them into an ambiguous single cell.
This sequence is a suggestion, not a validated testing procedure. It aligns with the distinctions visible in FDA's own products: the title page date, the history table, and the separate web page update. Separating those fields lets a reviewer see both the current thinking as issued and the state of the online source at the moment of capture, which are different evidentiary propositions.
Limitations when the source itself is silent
Some pages and files do not expose both dates cleanly. A guidance PDF may provide an issue date but no comprehensive history, as the Content of Premarket Submissions guidance does with its June 14, 2023 issuance date and reference to a preceding draft [8]. The web listing may show only a current-as-of date without mapping it to any discrete document version [4][5]. When one value is missing, a researcher should leave that field empty or explicitly record 'not stated.' Filling a blank with an inferred date would manufacture an FDA event that the source does not document.
Date extraction from PDFs can also fail silently. A digitizer may interpret the revision history date instead of the title page date, or the cover date may appear without a time zone relevant to international operations. The CDS guidance title page and web page happen to show consistent January 29, 2026 information in the source documents, but this example does not establish that FDA always synchronizes the two [1][4]. The general guidance search page shows a different 'Content current as of' value, 11/19/2026, which is not tied to any single document issuance date in the source [5]. Teams operating across global submissions should therefore treat the printed date as the document issue-date anchor and the page timestamp as a separate retrieval artifact, never as a proxy.
Sources & references
- Clinical Decision Support Software - Guidance for Industry and Food and Drug Administration Staff · www.fda.gov
- Computer Software Assurance for Production and Quality Management System Software · www.fda.gov
- [PDF] Content of Premarket Submissions for Device Software Functions · www.fda.gov
- Clinical Decision Support Software | FDA · www.fda.gov
- Search for FDA Guidance Documents | FDA · www.fda.gov
- Electronic Common Technical Document (eCTD) v4.0 Technical Conformance Guide · www.fda.gov
- [PDF] Study Data Technical Conformance Guide - FDA · www.fda.gov
- Content of Premarket Submissions for Device Software Functions — Guidance for Industry and FDA Staff (June 14, 2023) · www.fda.gov