Medical Device Reporting Deadlines: A Manufacturer's Checklist for 5-Day and 30-Day Reports
A device manufacturer must file a Medical Device Report (MDR) no later than 30 calendar days after becoming aware of a reportable death, serious injury or malfunction. The deadline drops to 5 work days when the event needs remedial action to prevent an unreasonable risk of substantial harm to the public health, or when FDA has asked for 5-day reports in writing. Supplemental information is due within 30 calendar days of receipt. These rules come from 21 CFR Part 803 and FDA's MDR guidance for manufacturers, both indexed in our FDA surgical robotics and SaMD base.
What makes an event reportable
For a manufacturer, an MDR reportable event (21 CFR 803.3(o)) is information that reasonably suggests one of your marketed devices may have caused or contributed to a death or serious injury, or has malfunctioned and that the device, or a similar device you market, would be likely to cause or contribute to a death or serious injury if the malfunction recurred.
- Serious injury (803.3(w)): an injury or illness that is life-threatening, results in permanent impairment of a body function or permanent damage to a body structure, or needs medical or surgical intervention to prevent such permanent impairment or damage.
- Malfunction (803.3(k)): failure of a device to meet its performance specifications or otherwise perform as intended. Performance specifications include all claims made in the labeling.
- Caused or contributed (803.3(c)): includes events resulting from failure, malfunction, improper or inadequate design, manufacture, labeling, or user error.
- Work day (803.3(y)): Monday through Friday, except Federal holidays.
FDA's MDR guidance (final, 2016) adds that you do not need to assess whether a malfunction will recur: FDA presumes that once a malfunction has occurred, it will recur. On user error, the guidance says that events caused solely by user error, with no other performance issue and no device-related death or serious injury, need not be reported, but the supporting information should stay in your complaint files.
The three report types and their deadlines
Manufacturer MDR deadlines (21 CFR 803.10(c), 803.50, 803.53, 803.56)
| Report | Trigger | Deadline |
|---|---|---|
| 30-day report (initial) | Reportable death, serious injury or malfunction | No later than 30 calendar days after the day you become aware |
| 5-day report | Reportable event needing remedial action to prevent an unreasonable risk of substantial harm to the public health | No later than 5 work days after the day you become aware |
| 5-day report | FDA has made a written request | 5 work days; covers later events of the same nature for the period in the request |
| Supplemental / follow-up | New information not known or available at the initial report | Within 30 calendar days of receiving the information |
All of these go to FDA in an electronic format FDA can process, review and archive (803.12(a)), unless you have an exemption under 803.19, and they must be in English (803.13). The report content follows Form FDA 3500A blocks (803.52), and you must include everything “reasonably known” to you, meaning information you hold, can get from the initial reporter, or can get by analyzing or testing the device (803.50(b)).
When does the clock start? “Become aware” explained
The start date differs by report type, and this is where internal processes most often break.
- 30-day reports and requested 5-day reports: you become aware when any employee becomes aware of a reportable event (803.3(b)(2)).
- Remedial-action 5-day reports: you become aware when an employee with management or supervisory responsibilities over regulatory, scientific or technical staff, or one whose duties relate to collecting and reporting adverse events, becomes aware from any information, including trend analysis, that the event needs remedial action. FDA's guidance says it does not expect non-technical staff to recognize this.
- FDA's guidance treats the 5-day window for a remedial-action event as beginning the day after that person becomes aware.
Worked example (our own calculation)
Suppose your head of quality concludes on a Tuesday that a reported robotic-arm fault needs a field-wide fix. Counting from the next day, the 5 work days are Wednesday (1), Thursday (2), Friday (3), Monday (4) and Tuesday (5), so the report is due by the following Tuesday, a day later for each Federal holiday in between. For a routine event that an employee learns of on March 2, 30 calendar days after is April 1.
Remedial action: the most misread trigger
Remedial action (803.3(v)) is “any action other than routine maintenance or servicing of a device where such action is necessary to prevent recurrence of a reportable event”. FDA's guidance narrows it in practice:
- Correcting only the single device involved in the event is not a remedial action.
- Not every event tied to a remedial action is a 5-day report. Only those where the action is needed to prevent an unreasonable risk of substantial harm to the public health (or that FDA requested) qualify; the rest are 30-day reports.
- If the action is one FDA would consider a Class I recall, the MDR is due within 5 work days of the decision to start the remedial action.
- Once 5-day reports are filed for the events that triggered a remedial action, later events linked to that same action go in as 30-day reports.
- If you take remedial action after filing an initial MDR, file a supplemental report identifying the action.
- Separately, the guidance reminds you that a correction or removal to reduce a risk to health must, unless already reported, be reported to FDA within 10 working days of starting it, with the information required by 21 CFR 806.10.
Procedures and records FDA will inspect
Deadlines are only met reliably with written procedures. Under 803.17, manufacturers must develop, maintain and implement written MDR procedures covering the timely identification, communication and evaluation of events, a standardized review process for reportability, and timely transmission of complete reports, plus the related documentation.
Under 803.18, MDR event files must document your deliberations and decision-making on whether an event was reportable, keep copies of reports and FDA's electronic acknowledgments, and be retained for 2 years from the date of the event or the expected life of the device, whichever is greater. That retention rule still applies after a device is no longer distributed. The quality system rule ties in too: under the QMSR, 21 CFR 820.10(b)(3) requires manufacturers to notify FDA of complaints that meet the Part 803 reporting criteria.
Note on dates
The MDR guidance dates from 2016 and refers to the former Quality System regulation (for example 820.198 on complaint handling). FDA's notice on the document states that the QMSR, which incorporates ISO 13485:2016 by reference, took effect on February 2, 2026. Read older cross-references with that in mind.
A checklist for robotic surgery manufacturers
FDA's page on computer-assisted surgical systems notes that most MDRs it receives on robotically-assisted surgical devices concern malfunctions, such as component breakage, mechanical problems and image or display issues. It also notes that FDA has received reports of injuries and deaths. Your intake process should be built for that profile.
- Route every complaint into your complaint-handling process, including those picked up by field service engineers and clinical specialists.
- Record the “become aware” date and the person, and separately record when a supervisor first saw information pointing to remedial action.
- Screen each malfunction against the “likely to cause or contribute to death or serious injury if it recurred” test, without debating recurrence.
- Check whether a trend (repeated arm faults, display losses) points to remedial action, and escalate the same day.
- Calculate both the 30-calendar-day and the 5-work-day deadlines, excluding Federal holidays only for the latter.
- Chase missing information you can reasonably obtain, explain any gaps in the report, and diary a 30-day supplemental deadline when new facts arrive.
- File the decision rationale, report copies and acknowledgments in the MDR event file.
For edge cases, ask the base: for instance, “For a device-related event that needs urgent remedial action, how fast must a manufacturer report it to FDA, versus a routine report?” The answer cites Part 803 and the guidance side by side.
Turn Part 803 into cited answers
Ask questions about MDR timing, definitions and records, and get answers grounded in 21 CFR Part 803, the FDA MDR guidance and the QMSR, with the passages quoted.
Sources: 21 CFR Part 803 on eCFR and FDA's Medical Device Reporting for Manufacturers guidance. This article explains the rules; it is not compliance advice for a specific event.
Frequently asked questions
Are MDR deadlines calendar days or business days?
Both, depending on the report. 30-day and supplemental reports use calendar days. 5-day reports use work days, which 21 CFR 803.3 defines as Monday through Friday, except Federal holidays.
Who has to know about an event for the 5-day clock to start?
For remedial-action events, the clock starts when an employee with management or supervisory responsibility over regulatory, scientific or technical staff, or whose duties involve adverse-event reporting, becomes aware that remedial action is needed. FDA's guidance counts the 5 work days from the following day.
Do we report a malfunction that caused no injury?
Yes, if the device or a similar device you market would be likely to cause or contribute to a death or serious injury if the malfunction recurred. FDA presumes the malfunction will recur.
How long must MDR event files be kept?
For manufacturers, 2 years from the date of the event or a period equal to the device's expected life, whichever is greater, even if the device is no longer distributed (21 CFR 803.18(c)).
Does filing an MDR admit that our device caused the event?
No. Under 21 CFR 803.16, a report is not necessarily an admission that the device, the manufacturer or its employees caused or contributed to the event.
Get the Kopik newsletter
New knowledge bases, RAG guides and product news. One email every week or two, unsubscribe in one click.
By subscribing you agree to receive our newsletter. We never share your address.