Complaint management in regulated industries is different
In most businesses, complaint management is customer service. In FDA-regulated industries, it is a legal obligation and a safety system. A complaint about a drug or device may signal a defect, a labeling problem or a patient injury, and it may trigger a regulatory report with a fixed deadline. Complaint handling also feeds CAPA, risk management and post-market surveillance.
It is a frequent inspection finding. An analysis of FDA’s FY2025 data found complaint handling (21 CFR 820.198(a)) was the second most cited device observation, with 211 citations (GMP Insiders). In early QMSR inspections in 2026, “inadequate complaint handling” ranked third (RAPS).
For FDA and EU MDR complaint handling requirements for medical devices, see Medical Device Complaint Handling: FDA Requirements, MDR Reportability and a 2026 Checklist.
What the regulations require
| Area | Requirement |
|---|---|
| Drugs: 21 CFR 211.198 | ”Written procedures describing the handling of all written and oral complaints regarding a drug product,” and “A written record of each complaint shall be maintained in a file designated for drug product complaints” (eCFR) |
| Devices: QMSR and ISO 13485 | ”In addition to Clause 8.2.2 in ISO 13485, Complaint Handling, the manufacturer shall maintain records of the review, evaluation, and investigation for any complaints” (21 CFR 820.35) |
| Device complaint record content | Device name, date received, UDI or UPC, complainant contact, “The nature and details of the complaint,” corrective action taken and any reply (820.35) |
| Decision not to investigate | Records “documenting justification for not performing such investigation” (820.35) |
| Regulatory reporting | Device complaints that are reportable under 21 CFR 803 must be identified and reported; drug safety reports follow 21 CFR 314.80 |
| Definition | Under the QMSR, the ISO 13485 definition applies: a communication that alleges deficiencies in identity, quality, durability, reliability, usability, safety or performance |
What complaint handling software should do
| Capability | Why it matters |
|---|---|
| Multichannel intake | Captures complaints from calls, email, web, field service, sales and social media into one record |
| Required fields | Enforces record content such as UDI and complainant details |
| Reportability assessment | Guided decision trees for MDR and drug safety reporting with timers for 30-day, 5-day and 15-day clocks |
| Investigation workflow | Assignments, evidence, root cause and justification when no investigation is done |
| Links to CAPA, nonconformance and risk | Moves signals into corrective action and updates risk files |
| Trending | Coding by product, failure mode and severity; statistical trend alerts |
| Electronic reporting | eMDR and safety report submission or export |
| Compliance controls | Part 11 audit trails, e-signatures, access control and validation support |
Market estimates vary widely by scope; one research firm estimates the medical device complaint management market at “USD 8.91 Billion in 2025” (Fortune Business Insights). Treat such figures as directional.
Where AI helps, and where it must not decide
Complaint text is unstructured and high in volume, which makes it a natural place for AI. FDA said as much in 2023: “AI can be used to examine consumer complaints and deviation reports” and “can be used to proactively monitor manufacturing operations for trends” (FDA CDER). FDA itself uses its Elsa tool to “summarize adverse events to support safety profile assessments” (FDA).
Useful AI tasks include extracting product, failure mode and patient outcome from free text; suggesting codes; finding similar past complaints; flagging possible reportable events for human review; and checking investigation records for completeness.
The guardrails are clear. Reportability and safety decisions must be made by qualified people. FDA’s April 2026 warning letter on AI misuse requires that AI output “must be reviewed and cleared by an authorized human representative” of the quality unit (FDA). A missed report is costly: a January 2026 device warning letter noted a reportable malfunction where “no MDR was received by the FDA” (FDA).
For device makers, complaint software used in the QMS should be validated proportionate to risk under FDA’s Computer Software Assurance guidance (FDA).
Complaint management software checklist
- Intake from every channel, including field and sales staff
- Required record fields enforced per 21 CFR 211.198 or 820.35
- Reportability decision documented for every complaint, with timers
- Justification captured when no investigation is performed
- Investigation, root cause and CAPA links supported
- Coding and trending with defined thresholds
- Electronic submission or export for MDR and safety reports
- Part 11 controls and risk-based validation evidence
- AI suggestions cite source text and require human approval
- Metrics feed management review
Check complaint records before an inspector does
Complaint files fail inspections when required content is missing, reportability decisions are unexplained or investigations stop short. AskDona reviews complaint records and procedures against 21 CFR 820.35, 211.198, ISO 13485 or your own procedure, flags gaps and cites the passage behind every finding.
Run a sample complaint record assessment on a batch of closed complaints. AskDona shows the evidence; your team decides.
FAQ
What is complaint management in regulated industries? The documented process for receiving, evaluating, investigating, reporting and trending complaints about regulated products.
What must a device complaint record include? Under 21 CFR 820.35: device name, date received, identifiers such as UDI, complainant contact, complaint details, corrective action and any reply.
Do all complaints need investigation? Not always, but a decision not to investigate must be justified and recorded.
Can AI decide whether a complaint is reportable? AI can flag likely reportable events, but qualified people must make and document the decision.
Does complaint software need validation? Yes, in regulated use, proportionate to risk.
References
All pages opened and checked by October 13, 2026.
| Source | Type | Date | Used for |
|---|---|---|---|
| GMP Insiders: FY2025 observations | Trade analysis | Jan 5, 2026 | Citation counts |
| RAPS: Top QMSR observations | Professional body | May 14, 2026 | QMSR findings |
| eCFR: 21 CFR 211.198 | Regulation | Current | Drug complaints |
| eCFR: 21 CFR 820.35 | Regulation | Current | Device complaint records |
| Fortune Business Insights: Market | Market research | Sep 21, 2026 | Market estimate |
| FDA CDER: AI in drug manufacturing | Regulator | Mar 2023 | AI for complaints |
| FDA: Elsa launch | Regulator | Jun 2, 2025 | Adverse event summaries |
| FDA warning letter: Purolea | Regulator | Apr 2, 2026 | AI human review |
| FDA warning letter: Beta Bionics | Regulator | Jan 28, 2026 | Missed MDR |
| FDA: CSA guidance | Regulator guidance | Feb 2026 | Validation |