A medical device report runs two different clocks

Deciding whether an event has to be reported to FDA and writing the report FDA actually receives are two different jobs, governed by two different sections of 21 CFR Part 803. A complaint record's reportability test under 803.50 answers the first question. It doesn't answer the second: once an event clears that bar, which deadline applies, what the report has to say, and whether an individual report is even the right vehicle at all.

The default is thirty days, not the trigger

803.50 sets the reportability test: a manufacturer that becomes aware of information reasonably suggesting a device may have caused or contributed to a death or serious injury, or has malfunctioned in a way that would be likely to cause or contribute to a death or serious injury if the malfunction recurred, has to report it. 803.52 governs what the report itself has to contain once that test is met — device and event identification, a narrative of what happened, and whatever corrective action followed — and the standing deadline for filing it is 30 calendar days from the day the manufacturer becomes aware. A file that stops at the 803.50 determination and treats every reportable event as automatically a 30-day report has stopped one section short of the one that actually times the filing.

Five days, on a different test entirely

803.53 doesn't reopen the reportability question. It asks a narrower one, on top of an event 803.50 has already made reportable: does the event need remedial action to prevent an unreasonable risk of substantial harm to the public health? If it does, the manufacturer owes a 5-work-day report instead of the standard 30-day one, timed from awareness that the remedial action is needed — a determination that can come from the manufacturer's own trend analysis as easily as from a single incident. FDA can also convert a report to the 5-day track directly, by written request. A report scheduled against the 30-day default without a live check against 803.53 is treating a shrinking deadline as though it only ever runs one length.

There's no paper form left to file

FDA's electronic-submission rule requires manufacturers and importers to file medical device reports in an electronic format the agency's own system can process, review, and archive, retiring the Form 3500A mail-in workflow as the default path. A reporting procedure still written around a paper MedWatch form and a mailing address is documenting a process FDA no longer runs.

A quarterly exception for the events that aren't the point

FDA's Voluntary Malfunction Summary Reporting program lets an eligible manufacturer report certain malfunction events in summary form on a quarterly basis instead of filing an individual 30-day report for each one. Eligibility runs narrow on purpose: it only reaches malfunctions, not deaths or serious injuries, and only product codes FDA has already tracked for two years or more, with FDA revising the eligible-code list periodically since the program's terms were updated on August 29, 2024. A manufacturer that qualifies for the quarterly path still owes an individual, timed report for anything the program's own scope excludes — the exception narrows the volume of routine filings, not the underlying reportability test.

A medical device reporting procedure built around this structure — the 803.50 trigger, the 803.53 escalation test, the electronic filing requirement, and the VMSR carve-out's own limits — is previewed in the launch catalog. It runs on a different clock than a correction-and-removal record's own 806.10 deadline, which times from the date a field action was initiated rather than from awareness of a reportable event — a file that shares a due-date column between the two is measuring two different clocks against one line. If your program draws the 803.53 escalation test differently, the shelf takes that correction directly.