What a correction-and-removal record has to decide before the 10-day clock starts

A correction or removal often starts as an operational decision — pull three lots, fix a labeling error, swap a component — and only becomes a regulatory event once someone asks whether FDA needs to hear about it. 21 CFR Part 806 answers that question narrower than most quality teams assume: a report is owed to FDA within 10 working days only when the action was initiated to reduce a risk to health the device poses, or to remedy a violation that may present a risk to health, under 21 CFR 806.10. Everything below that bar is still a corrections-and-removals record — 21 CFR 806.20 requires the file to exist, and to justify why it wasn't reported, even when the answer to the reportability question is no. A tracker built only around the reportable cases is missing the file 806.20 requires for every other one.

Correction and removal are not the same action

21 CFR 806.2 defines the two terms apart on purpose. Correction means the repair, modification, adjustment, relabeling, destruction, or inspection — including patient monitoring — of a device without physically removing it from its point of use. Removal means physically taking the device to another location for one of those same actions. The distinction the section draws isn't about severity: a correction can close a serious risk with a field labeling fix or a patient-monitoring instruction, and a removal can pull a batch that never posed any real risk at all. What Part 806 tracks is where the work happens, not how serious it is, and a record that files everything under “recall” regardless of whether the device physically moved is already using the wrong vocabulary for what the section requires it to name.

Reportability turns on risk, not on the fact that something was corrected

806.10(a)'s trigger is that the manufacturer or importer initiated the correction or removal to reduce a risk to health posed by the device, or to remedy a violation that may present a risk to health. A routine label update fixing a typo, or a distribution correction unrelated to any risk, doesn't clear that bar and isn't reportable under 806.10 — however much it feels like the kind of action a recall tracker was built to catch. The record's first job is deciding this question explicitly, with a stated reason, rather than defaulting to “report it to be safe” — because 806.20's separate record-keeping duty exists for exactly the cases that don't clear the bar.

The clock starts at initiation, not at discovery

Once the risk trigger is met, the report is due within 10 working days of initiating the correction or removal — not from when the problem was first found, and not from when the internal investigation concluded. That's a different clock logic from the one a complaint record runs under 21 CFR 803.50, where the reporting clock starts at awareness of a reportable event rather than at the action taken in response to it. A correction-and-removal record that dates its 10-day clock from the closeout of an investigation, rather than from the date the action was actually initiated in the field, is measuring against the wrong event — and the gap between those two dates is exactly where a late report happens without anyone noticing until FDA asks for it.

Three exemptions from reporting, none of them an exemption from the record

806.10 exempts specific categories from the FDA report itself: market withdrawals (correcting or removing product over a minor violation FDA wouldn't act on, or no violation at all — normal stock rotation, routine equipment adjustments), routine servicing (regularly scheduled maintenance, calibration, parts replaced at their normal end of life), and stock recovery (correcting or removing product that never left the manufacturer's own control). None of the three waives 806.20. The section still requires a record for every correction or removal that wasn't reported — naming the product, the lot or serial numbers involved, a description of what happened, and, specifically, the justification for the decision not to report it. A file that only opens a folder for the reportable cases has no place to put the record 806.20 requires for the other three categories, and “we didn't think it needed reporting” without that justification on paper is the exact gap an inspector tests for.

Retention outlives the product, deliberately

806.20 sets the retention floor at two years beyond the device's expected life, and that clock doesn't stop when the manufacturer discontinues, stops importing, or stops distributing the device. The record has to survive the product's own market life by design, not by whatever the company's general document-retention policy happens to specify elsewhere.

A correction or removal this often starts downstream of exactly the signal a CAPA tracker is built to surface first — a complaint trend, a nonconformance pattern — which makes the reportability decision the hinge between two records that are otherwise easy to run as one. A corrections-and-removals record built around this structure — the correction/removal split, the risk-driven reportability test, the initiation-dated clock, and the record 806.20 still requires when the answer is no — is previewed in the launch catalog. If your program handles the reportability call differently, the shelf takes that correction directly.