top of page

Medical Device Complaints: Intake, Investigation and Trending

Oct 12
7 min read

Updated: 1 day ago

Reviewed by Aaron Lyon, President of A.P. Lyon and former Director of Quality Assurance and International Regulatory, with more than 30 years in medical device quality. Last reviewed November 10, 2026.


How do complaint intake, investigation and trending connect?


Use Complaint Handling for individual intake, assessment and investigation, Complaint Trending for patterns across cases, and Product Hold for controlled containment. A complaint bundle is useful when the connected reporting and field-action workflows are also missing. Trending must not delay a time-sensitive assessment of an individual case.


A complaint process should preserve the original report, assess immediate concerns and move the case toward a documented conclusion. Trending examines patterns across cases. Both depend on usable data, but neither should delay an individual safety or reportability assessment while the team waits for a trend to develop.


Decision table: match the gap to the evidence


Situation

Decision

Evidence to retain

New complaint arrives

Preserve facts and assess urgent escalation.

Case identity, awareness date and missing information.

A recurring pattern appears

Examine severity, exposure and coding.

Trend analysis, rationale and action.

Potentially affected stock exists

Control identity and disposition.

Hold scope, location and authorized release.


Capture information that supports decisions


Record the device identity, lot or serial information where available, the event description and relevant use circumstances. Identify what is missing and assign follow-up. Keep returned-product examination and investigation findings linked to the case. Document why an investigation is performed, limited or not performed under the applicable process.


Analyze patterns with context


Choose consistent complaint codes and review whether they remain meaningful as the product portfolio changes. Compare periods using appropriate exposure information and consider severity as well as frequency. Set a defined route for escalation when an alert is reached or a new pattern appears. Record the decision and follow-up even when further investigation finds no confirmed product defect.


Worked example: a fictional planning decision


A fictional device has a recurring intermittent failure. Several reports lack serial numbers and returned devices. The investigation records the unavailable information, seeks follow-up and assesses other evidence. It does not close all cases as 'no defect found' simply because no unit was returned. The trend review keeps those cases visible and asks whether the combined information changes the need for action.


Implementation record: make the decision reviewable


Give the case a traceable identifier and retain the original account, device identity, event circumstances, dates, investigation steps and reportability decisions. Separate customer descriptions from confirmed findings. For trends, record code definitions and exposure sources and assess changes in reporting behavior or market mix. Document the escalation decision even when a threshold is not reached but severity or a novel failure warrants review. Link product holds, related investigations and any action to the initiating cases.


Applicability, exceptions and conclusion limits


Low counts are not proof of low risk when reporting or exposure data are incomplete. An inability to reproduce the complaint is a finding with limits, not automatic proof that nothing happened. Service questions and returns need an intake route that can identify potential complaints; avoid letting commercial terminology hide relevant quality information.


Choose documentation by the missing workflow


The six-procedure complaint bundle includes handling, trending, recall/remedial action, FDA MDR, vigilance and product hold. It does not include every clinical or corrective-action document. Buy an individual procedure for a focused gap and check whether the wider QMS package already includes it. Documentation cannot supply a completed investigation or establish the reportability outcome for a real event.



Use complaint handling documentation for intake, assessment, investigation, reporting decisions and closure.



Use complaint trending to organize analysis methods, alert limits and escalation of patterns.



Use product hold when affected or potentially affected devices need controlled identification and segregation.



Compare the complaint bundle for connected intake, trending, reporting, recall, vigilance and hold controls.


Complaint records that serve several markets


When a device is sold in more than one country, one complaint can start several reporting clocks at once. Build the intake record so each market's reportability decision can be made from the same facts. These fields make that possible:


Field on the complaint record

Why it matters

Countries where the affected lot or serial number was distributed

Determines which reporting rules apply. Without it, the assessment defaults to the home market.

Date and source of first awareness

Starts the reporting clock in every jurisdiction, even when the complaint reaches quality later.

Local regulatory partner, and the date they were informed

In Australia, Brazil and Japan a sponsor, registration holder or Marketing Authorization Holder files the report. In Canada the importer may report on the manufacturer's behalf.

Reportability decision for each market, with rationale

A 'not reportable' conclusion needs its basis recorded for every market, not only the first one assessed.

Link to the MDR or vigilance case

Keeps the complaint, the investigation and each report consistent.


How MDSAP auditors sample complaints


The Medical Device Single Audit Program reviews complaint handling within its measurement, analysis and improvement chapter, then follows selected complaints into adverse-event reporting. Expect an auditor to choose complaints that involve injury, malfunction or returned product and trace each one: intake, investigation or the documented reason for not investigating, the reportability decision for each MDSAP market where the device is sold, any report filed, and links to trending and CAPA. ISO 13485:2016 clause 8.2.2 already requires the investigation rationale and the reporting decision to be recorded; MDSAP adds the country-by-country view.


The trace tends to expose the same gaps: reportability assessed for the United States only, no evidence that the local partner was told, and complaints closed as 'no defect found' with no record of what else was examined. The MDSAP Upgrade Kit (ISO 13485 edition or Dual-Standard edition) revises the complaint handling procedure for these points and adds a five-jurisdiction reporting procedure. The MDSAP-ready Manufacturing Plus systems (ISO 13485 or Dual-Standard) have the changes built in. For the reporting deadlines themselves, see FDA MDR, EU Vigilance and Medical Device Recall Workflows.


Common mistakes and an additional practical check


Avoid closing a case because no sample was returned without documenting what other information could be assessed. Do not let a product hold replace the investigation and reporting decisions that still need to occur.


Several reports described as handling difficulty may refer to different mechanisms. Reviewing the event narratives and use circumstances can reveal whether the coding hides a common interface problem or combines unrelated issues.


Review checklist before approving the workflow


  • Capture the original event account.

  • Assess safety, reportability and containment needs.

  • Assign investigation and follow-up ownership.

  • Use consistent codes and relevant exposure.

  • Document conclusions, escalation and closure.


Inside the supplied document: complaint intake and coordination


Source: supplied A.P. Lyon SOP 8-001, revision 2, effective September 19, 2026. This is a selected preview. Image wording is retained from the source; the explanation below is adapted. It is not an executed record or a quotation from a regulation.


The complaint procedure gives the coordinator responsibility for preserving the chronology and evidence needed for later decisions. This is especially useful when information arrives through several channels.


Original supplied SOP 8-001 excerpt on complaint intake and coordination

Selected original document text: complaint intake and coordination.



  • Record the first date and source of manufacturer awareness, event and receipt dates and device identifiers.

  • Retain efforts to obtain missing information and maintain the complaint record.

  • Coordinate reportability assessment, due-date tracking, investigation, communications, reassessment and closure under the applicable workflows.


Buyer decision: Compare your existing intake record with these interfaces. Complaint Handling supports the individual case; Complaint Trending supports analysis across cases. A low complaint count is not a substitute for a complete intake and investigation process, and reportability must be assessed under the applicable market rules.


Scope and how to use this guide


This is general implementation guidance for selecting and organizing documentation. The worked planning scenarios are fictional. Separately labeled document extracts come from the supplied A.P. Lyon files identified in their source notes. Neither is a completed study or evidence of compliance. Apply the requirements for your device, process and markets, and have the responsible technical and quality personnel approve decisions. Product downloads supply editable documentation; your organization remains responsible for its implementation and evidence.


Related buyer decisions





Primary references and review date


Technical references and linked product scope checked October 13, 2026. Regulatory summaries are identified above; checklists, decision tables and fictional examples are A.P. Lyon implementation recommendations. Consult the full applicable standards and regulations before approving a project.





Publisher and editorial standards


Published by A.P. Lyon. Aaron Lyon is the company’s founder; his professional background is described on the About page. These guides use AI-assisted research and drafting. Each guide is reviewed and approved by Aaron Lyon before publication; that review does not certify applicability to your device.




Frequently asked questions


What is the difference between complaint handling and complaint trending?


Complaint handling covers each individual report: intake, assessment, investigation, the reportability decision and closure. Complaint trending looks for patterns across many cases using consistent complaint codes, exposure data and a defined escalation route. Trending supports the individual process but must never delay a time-sensitive assessment of a single case.


Can a complaint be closed if the device was never returned?


Not automatically. Record what information was unavailable, seek follow-up and assess the other evidence you do have. Being unable to examine or reproduce the problem is a finding with limits, not proof that nothing happened, and those cases should stay visible in trend reviews.


What does the Complaint Handling Procedures Bundle include?


Six procedures: complaint handling, complaint trending, recall and remedial action, FDA MDR, vigilance and product hold. It does not include every clinical or corrective-action document, so check your existing CAPA and clinical procedures separately.


Do we need a separate complaint process for each country?


No. One process can serve every market if the record captures where the affected product was distributed, the first awareness date, the local partner and a reportability decision for each market. What changes from country to country is who reports, to whom and by when.


Building a complete quality system? Build Your QMS lets you choose ISO 13485 + FDA QMSR, Dual-Standard or ISO 9001:2026 procedures in one place, and applies volume discounts automatically: 20% off 5–9 procedures, 35% off 10–19, 50% off 20–39 and 60% off 40 or more.



Not sure where your quality system stands? Take the free QMS gap check: about 20 questions, an instant report of your gaps by clause, and the procedures that close each one.


Just getting started? The free Startup Quality Plan shows which procedures you need now, which can wait, and how long they take to put in place.

Recent Posts

See All
QSR to QMSR: What to Change in Your Procedures

How to update procedures written for the old Quality System Regulation to the FDA QMSR: what changed, the substantive gaps that come up most often, a repeatable revision method, before and after wordi

 
 
 

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page