Corrections and Removals Reporting under 21 CFR 806.10

1. Key takeaways

Under 21 CFR 806.10, medical device manufacturers (and importers, where applicable) must report a correction or removal to the FDA within 10 working days after initiating the action, when the correction or removal is undertaken to reduce a risk to health or to remedy a violation of the FD&C Act. The reporting trigger is the initiation of the correction or removal, not its completion, and not the moment when the company has confirmed that the problem is real. This distinction matters because many companies instinctively wait until they have fully investigated an issue and executed the field action before drafting a report. Under 806.10, that instinct creates compliance risk: the clock starts when the decision to act is made and the action begins, which means the internal work of verifying the issue, deciding on the corrective approach, and preparing the report must all fit inside the same 10-working-day window.

2. Legal basis

The obligations described in this article rest on the following provisions of United States federal regulation, which remain in force as of the verification date noted at the end of this page.

3. Expert insights

Insight one: the 10-working-day period runs from initiation, which sets the speed requirement for internal processes.

Under 21 CFR 806.10, the time limit starts when the correction or removal is initiated. This has a direct operational consequence: problem confirmation, decision-making, and report preparation inside the company must all be compressed into those 10 working days. A company cannot wait until the recall has been executed in the field and then file the report retrospectively. In practice, this means that the moment a firm decides to launch a correction or removal, the reporting workflow should already be moving in parallel with the field action, so that the report reaches FDA within the statutory window rather than after the window has closed.

Insight two: Part 806 and Part 803 are two parallel reporting regimes, and both are often triggered at the same time.

If the same event also constitutes a reportable event under the Medical Device Reporting regime, then a separate reporting deadline applies under 21 CFR 803.10. For events that require remedial action, section 803.10(c) requires the report within 5 working days. A single product correction action can therefore start two timers at once: the 10 working days under Part 806 and the 5 working days under Part 803. Companies that treat these as a single obligation frequently miss the shorter deadline, because the MDR clock runs out while the corrections-and-removals report is still being prepared. Every correction or removal that qualifies as a reportable event should therefore be logged against both timers on the day the action is initiated.

Insight three: the content requirements of the report include traceability elements.

According to the relevant FDA guidance on Corrections and Removals reports, the report must include traceability elements such as serial numbers, registration numbers, and UDI. This demands preparation on the company side: these identifiers should be assembled before the correction is initiated, rather than being hunted for at the moment the report is due. Firms whose device history records, distribution records, and UDI data are not maintained in a retrievable form will find that the 10-working-day window is consumed simply by locating the data that the report must contain. Treating these identifiers as report-input data, to be maintained continuously rather than assembled ad hoc, is the practical way to keep the filing deadline achievable for every action.

Insight four: the trigger standard for Part 806 reports includes remedying violations of law, and is not limited to reducing risks to health.

Under 21 CFR 806.10, there are two categories of triggering circumstances: first, actions undertaken to reduce a risk to health; and second, actions undertaken to remedy a violation of the FD&C Act. The second category covers compliance-level problems. Even where an issue does not directly constitute a risk to health, correcting it may still give rise to a reporting obligation. A company that screens its corrective actions only for patient-safety impact will under-report, because actions taken purely to restore regulatory compliance also fall inside the scope of 806.10. This practical estimate should be applied to every corrective action decision: before the action is initiated, the firm should determine whether it is a reportable correction or removal under either trigger, and document that determination.

4. Practical recommendations

• Build a 10-working-day countdown process into the quality system, starting automatically from the date of the correction or removal decision.
• At the same time, assess whether the 5-working-day timer under Part 803 has been triggered; if it has, advance both reports in parallel.
• Assemble serial numbers, registration numbers, UDI, and other required elements before initiation of the action.
• Include remedying violations of law in the trigger assessment, not only risks to health.
• Maintain a reconciliation ledger linking corrections-and-removals reports with MDR reports, so that neither report is omitted.

5. Verification checklist

• □ A 10-working-day countdown process has been built into the quality system
• □ It has been assessed whether the 5-working-day reporting obligation of 21 CFR 803.10(c) is also triggered
• □ Serial numbers, registration numbers, UDI, and other required elements have been assembled
• □ The trigger assessment covers both categories: reducing risks to health and remedying violations of law
• □ A reconciliation ledger between corrections-and-removals reports and MDR reports has been established
• □ Evidence of report submission has been archived

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, US Agent and local testing support for the United States market. Our team manages FDA establishment registration and listing, 510(k)/De Novo/PMA submissions, and supports post-market reporting obligations. Business enquiries: info@grzanglobal.com