FDA recall records embed several dates that answer different questions. The recall initiation date marks when a firm first began notifying the public or consignees, while the enforcement report date marks when FDA published the classified recall [1][3]. A third field, the classification date, records when FDA assigned Class I, II, or III and often falls between those two events [3]. The medical device database adds a create date that FDA explains indicates classification, not the start of the action [6]. Treating these fields as interchangeable distorts timelines of regulatory response. The reliable method is to separate the firm's operational act from FDA's administrative publication and to verify each field against the primary record rather than a single search result.

What Each Date Field Actually Documents

FDA defines the recall initiation date as the date the firm first began notifying the public or consignees of the recall [1][3]. This is an operational event under the firm's control. The classification date is assigned by the responsible FDA center when the agency places the recall in Class I, II, or III [3]. The classification necessarily follows review of the firm's action and therefore can occur after customers have already been contacted [6].

The weekly enforcement report date records when FDA issued the enforcement report containing that product recall [3]. A separate field, create date, marks when the recall was first posted [3]. For medical devices, FDA states plainly that the create or classification posting date does not necessarily mean the recall is new [6]. Comparing these fields against the initiation date is the first check for identifying a dated record that describes an older action.

How the Initiation Date Is Established

The initiation date derives from the recalling firm's first notification, whether to consignees or to the public [1][3]. FDA guidance recommends that firms follow written recall procedures and execute a prepared communications plan under 21 CFR 7.46, including issuing recall communications that FDA may review [2]. The event begins with that notification act, not with an FDA request, a firm's internal investigation, or a meeting about a possible recall.

For a firm-initiated recall, the manufacturer or distributor may decide on its own to remove or correct a distributed product and is requested to notify the appropriate FDA district office immediately [7]. The removal is considered a recall only if FDA regards the product as violative [7]. The date the firm first acts and the date FDA formally treats the matter as a recall can therefore differ, which is why the initiation field must be read as a firm-reported operational datum rather than an agency adjudication.

Concrete Example Using One Public Record

Suppose a quality analyst finds a Class II infusion pump recall in the current weekly enforcement report. The API record shows recallinitiationdt of 2026-10-02, centerclassificationdt of 2026-11-10, and enforcementreportdt of 2026-11-18 [3]. The correct interpretation is limited to what these fields state: the firm first began notifying consignees or the public on October 2, FDA classified the product on November 10, and FDA issued the enforcement report on November 18. The November report is not evidence of a newly started recall [6].

If the same record's Event ID has a modification history, an eventlmd value later than November 18 would indicate a posted change, not a new initiation [3]. The analyst should cite the initiation date for questions about when the firm acted and the report date only for questions about when FDA made the classified recall publicly available. This suggested example uses only field definitions and does not describe an actual event.

Where the OIG Found Initiation Date Errors

A HHS Office of Inspector General review of 30 voluntary food recalls from 2012 through 2015 found that recall initiation dates in the Recall Enterprise System were inaccurate for 11 recalls, or 37 percent of the sample [8]. The inaccurate dates were off by a median of 4 days and an average of 16 days, and ranged from 1 day before the initiation date inputted into the RES to 89 days after [8]. The OIG attributed the errors partly to a lack of a clear definition of recall initiation, describing one recall coordinator who entered the date the firm started discussing a possible recall as the initiation date [8].

The OIG also reported that the 30 recalls had a median of 29 days to initiate after FDA learned the product was potentially hazardous, with an average of 57 days and a range of 9 days before to 303 days after [8]. These figures describe a historical audit sample and cannot be generalized to current recall timing, but they show that initiation date accuracy is a documented data-quality concern. An analyst comparing public records should therefore note that the initiation field may carry entry error even when the official definition is precise.

Using the Fields to Reconstruct a Recall Timeline

A defensible timeline starts with the recall initiation date from the API field recallinitiationdt, defined as the date the firm first began notifying the public or consignees [3]. The next reference point is the center classification date, which documents when FDA assigned the numerical class [3]. The enforcement report date then shows when FDA issued the public report containing the recall [3]. These three fields represent firm action, agency review, and public dissemination respectively.

The FDA Investigations Operations Manual describes the Recall Enterprise System record as the source of the reference number publicized in the Enforcement Report when a recall is classified [4]. That means the public report is downstream of classification. An analyst encountering a recall listed in a current weekly report should not conclude the recall was initiated that week; the initiation field may predate the report by days or considerably longer, as the OIG sample illustrated [8].

A Suggested Verification Workflow

For each recall event, pull the Recall Number, Event ID, recall initiation date, center classification date, enforcement report date, and posted internet date from the same API record [3]. Check the product-level record as well, since the numeric Product ID tracks a specific recalled product and can distinguish product-level modifications from changes to the event-level initiation date [3]. This separation matters when a single event includes multiple products with different lot codes or when a record is corrected after posting.

When the recall is a medical device, consult the FDA Medical Device Recalls database and compare the Date Action Initiated and Date Record Classified sort fields [6]. If the initiation date is older than the classification or posting date by a meaningful interval, label the recall as an older action that has just been classified rather than a newly initiated correction. If the initiation field appears to postdate a public announcement, treat the record as suspect and check the event modification history rather than silently accepting the value.