21 CFR 820.198 · Part 803 MDR · EU Vigilance
Complaint Handling
& Medical Device Reporting
Every Complaint Is a
Signal and a Clock
Every Complaint Is a
Signal and a Clock
Complaint handling and adverse event reporting are where a company's post-market quality system meets the regulator most directly. Every complaint is a potential safety signal and, if it involves a death, serious injury, or reportable malfunction, the start of a legal reporting clock. Handled well, the system turns field feedback into safer devices; handled poorly, it becomes the finding that anchors a warning letter.
A complaint does not end when it is logged. It moves through a defined sequence, and every step carries a standard, a record, and — once reportability is in play — a clock.
Every complaint recorded, through any channel, with the detail a later decision will need.
A rapid assessment for reportability and patient risk before anything else proceeds.
Root-cause analysis proportionate to risk, including device evaluation when units are returned.
The documented call on whether, where, and by when the event must be reported.
MDR, MIR, and vigilance filings inside statutory timelines, to each authority.
Aggregate analysis that surfaces issues no single complaint reveals.
The hardest and most scrutinized step is deciding whether an event is reportable, and doing it fast. FDA expects a Medical Device Report within 30 calendar days of awareness, or within 5 working days when remedial action is needed to prevent a risk to public health. The standard the Agency applies: when the information reasonably suggests a reportable event, you report.
The standard MDR timeline from becoming aware of a reportable death, serious injury, or malfunction.
The accelerated clock when remedial action is needed to prevent an unreasonable risk to public health.
The defensible posture: if the information reasonably suggests reportability, report. Under-reporting is the costly error.
A device sold globally generates parallel reporting obligations that do not align on timelines, thresholds, or forms. Run them as one coordinated system, not as separate fire drills each time an event lands.
Mandatory reports for deaths, serious injuries, and reportable malfunctions, filed to FDA on the 30-day or 5-day clock.
Serious-incident and field-safety-corrective-action reporting to competent authorities, plus periodic trend and PSUR obligations.
Canada, the UK, Japan, and more each run their own vigilance rules — harmonized in spirit, divergent in the detail.
None of these are exotic. They are the everyday breakdowns that turn a routine complaint system into a warning-letter exhibit.
Closing a complaint as non-reportable when the information reasonably suggested otherwise.
Recognizing a reportable event but filing late, turning a safety report into a compliance finding.
A system that logs and reports but never feeds the corrective action that would stop recurrence.
Root-cause work too shallow to support the reportability decision or the CAPA that should follow it.
Reviewing complaints one at a time and missing the aggregate signal that defines the real problem.
Frontline staff who do not recognize a complaint, or a reportable event, when it arrives.
The judgment here is bought across audits: knowing how an investigator tests a reportability decision, where timelines quietly slip, and how to connect complaints to CAPA so the system actually improves the device. Your leads are senior quality practitioners who have run and defended complaint and vigilance systems.
We build the complaint file an investigator will pull first, because we have answered for one.
We make the decision defensible and fast, with the rationale documented every time.
FDA MDR and EU vigilance run as one system, so parallel clocks are never a scramble.
We wire complaints into CAPA and trending, so the system prevents, not just records.
A complaint system is one node in the post-market quality loop. It feeds corrective action, surveillance, and the risk file that should learn from every signal.
Where a complaint's root cause becomes a corrective action that actually stops recurrence.
Explore CAPA →The proactive surveillance program complaint trends feed into and draw from.
Explore PMS →The ISO 14971 risk file that every field signal should update, not just close.
Explore Risk →Tell us about your device, your markets, and the state of your complaint and reporting system. We will assess the gaps and match you with a senior quality lead, with a response within one business day. All inquiries are strictly confidential.
