Reportable Food Registry: FDA Reporting Duties Under FD&C Act 417

The Reportable Food Registry is the US FDA registry in which FDA may enter instances of reportable food after receiving reports through an electronic portal under FD&C Act §417(b)(1).

For US food reporting under that provision, the portal is the submission channel; the Registry is where FDA may enter instances received through that channel. Submitting a report and FDA entering an instance in the Registry are distinct actions.

Operationally, an RFR submission sits alongside other incident-response activities. The comparison below describes their working purposes and records, not legal definitions or recall classifications.

In practice, teams commonly connect these records through a shared incident reference while tracking each activity separately. A complaint investigation, distribution search and reporting decision answer different questions; keeping their status visible helps prevent one completed task from being mistaken for completion of the whole response.

This article addresses US food reporting under section 417, not recall execution or a universal reporting rule for every regulated product. For operational preparation, see recall readiness and mock-recall programs.

For US FDA-regulated food and feed, FDA’s industry page describes RFR coverage as all categories except dietary supplements and infant formula. This is FDA’s explanatory guidance. It describes the reporting population as registered facilities that manufacture, process, pack, or hold food for human or animal consumption in the United States.

For US food reporting, section 417(a)(1) defines the responsible party by reference to the person submitting registration for a facility required to register, where the food is manufactured, processed, packed, or held. For US reportable food, section 417(d)(1) places the reporting duty on that responsible party, subject to its statutory exception.

For US reportable food, §417(d)(2) excuses the responsible party from the report required by paragraph (1) only when all three conditions hold: the adulteration originated with the responsible party; that party detected the adulteration before any transfer of the food to another person; and that party either corrected the adulteration or destroyed or caused the destruction of the food. Each condition must be met—an internal hold, a supplier-caused defect, or a correction made after the food already moved to another person does not qualify.

For foreign-facility questions involving food for US consumption, check current section 417 and food-facility registration scope; do not use physical address alone as the jurisdictional test. Where classification crosses markets, such as US medical food and EU FSMP, document each market’s applicability assessment separately.

As operational practice, keep the legally relevant responsible party distinct from employees assigned to assess the incident, prepare the submission, authorize it, and maintain the record. Record those assignments and backups alongside the registration identity. A job title or portal account is not a substitute for that mapping.

For US food within the Registry’s scope, FD&C Act §417(a)(2) defines reportable food by a reasonable probability that use of, or exposure to, the food will cause serious adverse health consequences or death to humans or animals. SAHCODHA is shorthand for that health-consequence language—not a separate legal test or a severity score.

Build an evidence-to-consequence assessment

As a practical assessment structure, connect the following elements rather than treating an incident category as the answer:

• Hazard evidence: identify what was observed, the evidence’s reliability, and whether it concerns the food itself or a related process or environment.
• Affected food: explain which products or lots the evidence implicates and the basis for extending—or limiting—that scope.
• Plausible use or exposure: describe how humans or animals could encounter the hazard, including relevant preparation, handling, and intended use.
• Expected consequences: connect the hazard and exposure scenario to potential health effects, identifying susceptible consumers or animals where relevant.
• Remaining uncertainty: distinguish established facts from assumptions and specify which unanswered questions could change the conclusion.

A laboratory result, complaint, supplier message, or deviation is an assessment input. Document what it establishes and what it does not; its label alone is not the reasoning. Existing HACCP hazard analysis can provide context, while a data integrity risk assessment can help examine weaknesses in supporting records.

Record the conclusion separately from containment

A useful internal decision record contains the assessment basis, evidence references, decision maker, determination time, and unresolved questions. Explain why the available evidence supports the conclusion, including contrary evidence and assumptions. Keep later reassessments distinguishable from the original determination.

For operational control, document containment decisions separately from the reportability assessment. A hold can address uncertainty while the assessment proceeds. Do not use a hold, a positive test, or an absence of complaints as a standalone answer; connect each fact to the assessment above.

For US reportable food, FD&C Act §417(d)(1), subject to paragraph (2), requires the responsible party to act as soon as practicable, but in no case later than 24 hours after a responsible party determines that an article of food is a reportable food. For US reportable food, the responsible party’s required action under §417(d)(1)(A) includes submitting a report to FDA through the electronic portal. This outer limit is not a recommended waiting period.

See scope-and-reporting-parties above for the three cumulative conditions of the §417(d)(2) exception; confirm the current statutory text before relying on it.

Keep the incident timestamps distinct

As recordkeeping practice, use separate fields rather than a single incident date. Record each timestamp with its date, time, and explicit time zone; retain the person or source responsible for the entry.

Escalate the recorded determination immediately using the ownership and backup assignments described in the reporting workflow below; do not substitute the next shift handover, scheduled meeting, or investigation milestone for determined_at.

The recommended incident log preserves original timestamps alongside later corrections, including who corrected an entry and why. It documents the chronology; it is not a mechanism for changing the start of the statutory clock for US reportable food. Use management review to examine recurring escalation delays and unclear ownership, rather than making that meeting an incident-response gate.

For US reportable food, FD&C Act §417(d)(1)(A) calls for the responsible party’s report to include subsection (e) data elements except those in paragraphs (8), (9), and (10). The selected elements below are not a complete FDA form specification; check the current §417(e) text for the complete data-element list.

For US reportable food, selected statutory elements are the responsible party’s registration numbers under §417(e)(1), the date the food was determined reportable under §417(e)(2), and the unique number under §417(e)(11) described in §417(d)(4). For US reportable food, §417(e)(3) requires a description of the article of food including the quantity or amount, and §417(e)(4) requires the extent and nature of the adulteration. If the adulteration may have originated with the responsible party, §417(e)(5) requires the investigation results, as applicable and when known.

The following mapping is suggested internal practice, not a list of mandatory portal fields. Keep the statutory determination date separate from a more granular internal timestamp, including time zone, for clock control.

Use attributable recording to identify who prepared and reviewed the file, and production context tagging to connect evidence to the relevant product and lots. Keep the internal incident identifier distinct from the RFR report number.

Suggested internal data-model diagram—not an FDA schema or a software capability statement: Incident → determination record → submission record → correspondence. Link product/lot records and evidence to the incident; attach preparer and reviewer identities to the records they handled.

For US reportable food, FD&C Act §417(d)(1)(B), subject to paragraph (2), requires the responsible party to investigate the cause if adulteration may have originated with that party. For US reportable food, §417(e)(5) specifies investigation results as applicable and when known; the reporting deadline is not a deadline for completing the investigation.

A practical handoff model assigns separate owners while keeping reporting, product controls, and investigation coordinated:

• Food-safety assessment: document the determination and pass the risk rationale, affected-product scope, and uncertainties to the reporting lead.
• Regulatory reporting: assemble the submission, reconcile identifiers, and obtain authorization from the designated person.
• Product-control operations: use lot and shipment records to locate affected stock and execute human-approved control or disposition decisions.
• Investigation ownership: coordinate laboratory records, supplier correspondence, and the quality incident or deviation record; connect relevant out-of-specification findings without treating a laboratory result as the entire risk assessment.

Recommended workflow: determination → reporting preparation → human authorization → submission → receipt and version preservation. In parallel: determination → product controls and cause investigation → findings returned to the reporting lead. Neither parallel workstream waits for submission to finish.

Before submission, reconcile facility identifiers, product identifiers, lot references, and timestamps across these records. Assign each unresolved discrepancy to a named owner and make its status visible to the authorizer.

Any optional record-routing support should remain separate from human review: designated people retain submission authorization, risk decisions, and product disposition. Preserve the submitted version and receipt. Reconcile later corrections against that version, recording what changed and why rather than silently replacing the original.

Statutory review, linkage and alerts

For US reportable food, FD&C Act §417(b)(2) requires the Secretary to promptly review and assess submitted information for purposes including identifying reportable food and submitting entries to the Registry. Submission therefore feeds an agency review process, rather than replacing it.

For US reportable food, FD&C Act §417(d)(4) requires the Secretary to ensure that a unique number is issued through the electronic portal to the submitter upon submission under paragraph (1) or (3). The provision describes that number as enabling the Secretary to link reports and amendments about the US reportable food and identify its supply chain.

For US reportable food, FD&C Act §417(c)(1) requires the Secretary to issue, or cause to be issued, an alert or notification using Registry information as the Secretary deems necessary to protect public health. That qualification matters: submission is not a promise of a public alert.

Practical follow-through

As an internal control, maintain separate, cross-referenced records for FDA correspondence, supply-chain communications, investigation actions and product disposition. Preserve the report number alongside each relevant amendment and communication; connect affected lots to the site's lot genealogy. Keep investigation findings linked to the relevant HACCP assessment where applicable, without treating that assessment as the reporting decision.

For US reportable food, FD&C Act §417(d)(6) allows the Secretary, after consulting the responsible party that submitted a report under paragraph (1), to require that party—within a time the Secretary specifies—to amend its report to add the subsection (e)(9) supply-chain contact-information element, to notify specified recipients in the supply chain, or both.

For US reportable food, §417(d)(7) allows the Secretary, subject to the exception in paragraph (8), to require a responsible party that receives such a notification to submit its own report, investigate the cause if the adulteration may have originated with that party, and notify further recipients in the supply chain. For US reportable food, §417(d)(8) excuses a responsible party that already submitted a paragraph (1) report for the same article of food from submitting an additional report or notification under paragraph (7); instead, that party must amend its original report to add the data elements described in subsection (e)(9) and the unique number element in subsection (e)(11).

These follow-up duties are conditional on a Secretary-issued notification tied to another party's report about the same food, not a standing obligation on every responsible party. Check for an incoming §417(d)(6)(B) or (7)(C) notification before assuming that filing a primary report under paragraph (1) closes the matter, and route any such notification to the same reporting owner identified in the workflow above.

Keep the opening reporting-versus-recall comparison in view. Operationally, track submission, recall decisions, investigation closure and product disposition as separate statuses with their own supporting decisions. Do not mark a recall as initiated, an investigation as closed or product as released merely because a report was submitted.

These hypothetical cases illustrate reasoning and handoffs, not FDA determinations or contaminant-specific rules. Record formats and internal owners below are practical suggestions, not prescribed organisational arrangements.

Conventional food: signal versus determination

Assumptions: A registered US facility manufactures conventional food for US consumption; its registrant is the responsible party. An unconfirmed laboratory alert prompts assessment. Later, confirmed findings, product identification and a qualified health-risk assessment support its documented determination that the statutory threshold is met. No section 417(d)(2) exception is being relied on.

Decision: For this US food incident, the responsible party’s determination is the event to which the reporting clock discussed above attaches under section 417(d)(1). Supporting record: preserve the alert, assessment, determination timestamp and rationale; an audit trail review workflow can help reconstruct the sequence. Next owner: the designated reporting lead. Unresolved question: which other products share the implicated material?

Animal feed: upstream suspicion, separate workstreams

Assumptions: A registered US holding facility's responsible party determines that feed for US animal consumption is reportable. Supplier information and receiving records suggest upstream adulteration that the responsible party did not cause and could not have corrected or destroyed before the feed moved downstream. Because the adulteration did not originate with the responsible party, the §417(d)(2) exception's conditions are not met and no exception applies here.

Decision: proceed with reporting while separating supplier fact-finding from operational containment. For this US feed incident, section 417(d)(1)(B) requires cause investigation if adulteration may have originated with the responsible party; upstream suspicion alone does not resolve that condition.

Supporting record: retain the determination, supplier correspondence, receipt history, storage observations and containment decisions. Next owners: reporting lead for submission, supplier quality for fact-finding, operations for holds, and regulatory/quality reviewers for origin assessment. Unresolved question: could holding conditions have caused the adulteration? If FDA later notifies this facility under §417(d)(6)(B) or (7)(C) because another supply-chain party already reported the same adulterated feed, the conditional duties in §417(d)(7)-(8) above determine whether a new report or only an amendment to an earlier report is required; do not assume no action is needed merely because this facility already reported.

Product classification: dietary supplement

Assumptions: A US-market product enters a registered manufacturer’s conventional-food workflow, with its registrant initially treated as the potential reporting party. Label, formulation and intended-use review confirm a dietary supplement. This is a classification decision, not reliance on a reporting exception.

Decision: route to separate supplement regulatory review: FDA’s RFR scope statement excludes dietary supplements from the US Registry. Supporting record: preserve the classification rationale and hazard evidence. Next owner: the supplement regulatory lead, coordinating any contract manufacturer. Unresolved question: which separate response obligations apply?

For US food reporting, FDA's portal-outage advice says a person unable to use the Safety Reporting Portal may call 1-888-INFO-FDA and follow the prompts to report a problem. For US food reporting, FDA also recommends that the responsible party submit a report to the Safety Reporting Portal as soon as it resumes operation.

Internal recovery controls

As operational practice, maintain a recovery log separate from the legal reporting rule explained above. Assign a backup owner to coordinate recovery rather than leaving each failed handoff with its original sender.

• Retain attempted-submission timestamps, error details, contact records, the prepared report, and the eventual submission receipt.
• For unavailable credentials, use an authorised access-recovery route; for absent reviewers, activate the designated alternate reviewer.
• Apply the identifier-reconciliation control described in the reporting workflow above when an outage queue creates conflicting facility identifiers; record the resolved identity before transferring queued information.
• For failed information transfers, confirm receipt, compare the transferred content with the prepared report, and document discrepancies and corrections. Involve the HACCP team where hazard information needs clarification.

Do not treat an outage, an internal system failure, or a telephone contact as a statutory extension or proof that the reporting obligation has been discharged.

The following are practical incident-management controls, not additional statutory duties. Test whether they work during an actual incident or exercise, rather than whether a procedure names them. For timing, product scope, and recall distinctions, refer to the reporting-clock, scope, and downstream-consequences sections.

Configuration is not operation. A routing screenshot demonstrates setup; a completed handover demonstrates use. Sample completed reviews and reconciled incidents, checking that evidence remains retrievable and that closure addresses the discrepancy rather than merely changing its status. Consistent production context tagging can support record matching; use change control when revising ownership rules or identifier mappings.

Where software generates a draft, extracts a field, or routes a task, include a human review check: compare content with source records, confirm the recipient has accepted ownership, and document corrections. Treat generated output as pending review, not as evidence of approval or completed reporting.

Use this checklist to test response capability with an incident file, not just a procedure. The readiness checks are locally selected controls, not additional legal duties.

Statutory duties discussed above

• Applicability ownership: for US food subject to section 417, check readiness to perform the reporting duty discussed above under section 417(d)(1)(A). Can staff identify the responsible reporting owner and explain the applicability decision?
• Assessment competence: can the assigned assessor connect the determination to its evidence and identify unresolved questions needing specialist review?

FDA recommendations

• Recovery readiness: for US reportable food, FDA recommends portal submission by the responsible party as soon as the portal resumes operation. Is someone assigned to carry that recovery action through?

Locally selected operating controls

• Reporting access and backup coverage: demonstrate that an authorized alternate can take over when the primary reporter is unavailable.
• Record mapping: retrieve the submitted version, reconcile its receipt with the incident record, and trace identifier changes through an audit trail.
• Communication routing: show who receives assessment escalations, submission confirmation, and unresolved discrepancies.
• Exception recovery: run a tabletop exercise testing an assessment handoff, an unavailable primary reporter, and a conflicting identifier.
• Documented review: record findings, owners, corrective actions, and follow-up evidence for management review. Keep legal decisions and product-release approvals with designated people; this model needs no particular software or certification.

Can a designated reviewer reconstruct what was decided, by whom, on what basis, and what action followed?