A record can have several valid dates
A clearance decision date, a recall initiation date, and a report received date describe different source events. The date a monitoring service detects a record describes collection. These dates can be weeks or months apart without describing a contradiction.
The label beside a date matters as much as the date itself. In MedTech Watch, the original source date and first observation are displayed separately. Account-specific matching also distinguishes when a particular customer first received a match.
Dataset updates are not individual event dates
openFDA publishes its clearance dataset monthly and its recall and device-event datasets weekly. The upstream dataset date identifies the version available from the source. The last successful check tells you when MedTech Watch successfully checked or collected it.
A successful check does not prove the source published new data. Likewise, a current collection timestamp does not make an older FDA dataset a daily publication. Both timestamps are useful and neither should replace the other.
Separate history, discoveries, and revisions
When you start a watch, historical matching establishes a baseline. A later discovery is new to that watch even if its FDA date is earlier. A revision is a change to a source record already known to the service.
This distinction matters when another customer already followed the same company. Their earlier collection should not suppress your baseline or make your own history appear to begin before you joined. The public catalog uses shared FDA records, while the paid workspace retains account-specific matching history.
Read monthly reports with their stated basis
MedTech Watch monthly reports group clearances by FDA decision date and recalls by initiation date. They list the dataset versions used and identify records without the date needed for that grouping. They are not counts of announcements issued that month.
Later source changes can revise an earlier month. A report’s revision date changes when its substantive contents change. Ordinary daily checks do not continually reset its publication date.
Recognize an import problem
A failed or incomplete import must not be presented as an empty result. Public pages continue using the last complete release and show source status. Paid digests distinguish unavailable source updates from a source that was successfully checked and had no new matches.
Before comparing periods or sharing a figure, check the coverage statement, date basis, dataset date, and collection status. This short check prevents many apparent “spikes” or “quiet weeks” from being misread.
Why a new match can have an older date
A record first found after you establish a watchlist may carry a decision date from an earlier month. It is newly detected for that watch, but it does not belong in the current month’s decision-date count.
Our monthly reports use clearance decision dates and recall initiation dates. Their source releases and missing-date totals are disclosed so the comparison can be reproduced.