Complaint Management Software: Customer Complaint Handling for Regulated Industries

Complaint management software built for FDA and ISO 13485

Complaint Management Software for Regulated Industries

A product complaint in a regulated industry is not a customer service event. It is a quality system event with regulatory consequences. A complaint about a medical device that malfunctioned in clinical use may require a Medical Device Report to the FDA within 30 days. A complaint about a drug product that caused an adverse reaction may require a MedWatch submission. A batch-level complaint may require a recall evaluation. A complaint that reveals a manufacturing defect requires investigation, root cause analysis, and a CAPA that addresses the quality system gap that allowed the defect to reach the customer.

General-purpose complaint management tools — customer service platforms, CRM-based complaint trackers, broad compliance workflow systems — can log that a complaint was received and track its resolution status. What they cannot do is structure the MDR evaluation against Part 803 decision criteria, enforce the mandatory intake fields that 21 CFR Part 211.198 and ISO 13485 Clause 8.2.2 require, link the complaint investigation to a CAPA with bidirectional traceability, or track the submission status of a 30-day MDR against the clock from the date the manufacturer became aware.

This page covers the regulatory framework governing complaint management in medical devices and pharmaceuticals, the complaint types that regulated industries manage, how eLeaP structures the intake-through-CAPA workflow, and how the system supports MDR and MedWatch reportable event documentation.

A complaint that requires a five-day MDR submission cannot sit in an intake queue while a quality coordinator decides which fields to complete. The regulatory clock starts when the manufacturer receives information that reasonably suggests a reportable event occurred — not when the complaint record is finalized.

The Regulatory Framework: Three Complaint Handling Obligations with Specific Requirements

Complaint handling in regulated industries is governed by specific regulatory requirements that define what must be captured, when investigations are required, what reporting obligations are triggered, and what records must be maintained. The three primary frameworks for US-regulated manufacturers are as follows.

QMSR and ISO 13485 Clause 8.2.2 — Medical Device Complaint Handling

Under the FDA’s Quality Management System Regulation (QMSR, effective February 2, 2026), medical device complaint handling requirements are governed by ISO 13485:2016 Clause 8.2.2, incorporated by reference into 21 CFR Part 820. FDA also retained specific complaint record-keeping requirements in 21 CFR § 820.35, which defines the content requirements for complaint files and investigation records.

ISO 13485 Clause 8.2.2 requires that manufacturers establish documented procedures for receiving and handling complaint communications related to medical devices. The procedure must define the process for receiving and recording complaints, evaluating them to determine whether an investigation is required, conducting investigations, determining whether information needs to be reported to regulatory authorities, and handling any corrective actions. Records of complaint-related activities must be maintained, and the complaint handling process must connect to the CAPA system when investigation reveals a product or quality system nonconformity.

21 CFR § 820.35 specifies the record content requirements that FDA retained beyond what ISO 13485 Clause 8.2.2 requires: the name of the device, the date the complaint was received, the unique device identifier if known, the name, address, and phone number of the complainant, the nature and details of the complaint, the dates and results of the investigation, any corrective action taken, and any reply to the complainant. Each of these fields is a required capture element in eLeaP’s complaint intake form — not an optional field that the quality team may or may not complete.

21 CFR Part 211.198 — Drug Product Complaint Handling

21 CFR Part 211.198 requires that drug manufacturers establish written procedures describing the handling of all written and oral complaints regarding a drug product. Any complaint representing a possible failure of a drug product to meet its specifications must be investigated. A written record of each complaint investigation must include the name and strength of the drug product, the lot number, the name of the complainant, the nature of the complaint, the reply to the complainant, the findings of the investigation, and any follow-up. Part 211.198 also requires that the quality control unit review complaints involving possible product defects and that any complaint requiring investigation be reviewed with respect to possible product recall.

The recall evaluation requirement in Part 211.198 is a distinctive obligation that general-purpose complaint tools do not accommodate. When a drug product complaint indicates a possible product defect, the quality unit must evaluate whether the defect extends to other distributed lots and whether a recall is warranted. In eLeaP, the complaint record includes a recall evaluation field that routes to the quality unit and regulatory affairs when the complaint type indicates a possible product defect, ensuring this evaluation is documented and does not depend on a manual process trigger.

21 CFR Part 803 — Medical Device Reporting

21 CFR Part 803 is the Medical Device Reporting regulation that establishes the mandatory reporting obligations triggered by certain complaint types. Manufacturers must report to the FDA when they become aware that a device they manufacture may have caused or contributed to a death or serious injury, or when a device malfunctioned and would be likely to cause or contribute to a death or serious injury if it recurs. The 30-day reporting window applies to most MDR-required events; the five-day window applies to events requiring remedial action to prevent unreasonable risk to public health. Both windows are measured from the date the manufacturer received or otherwise became aware of information that reasonably suggests a reportable event occurred.

The MDR reporting obligation is triggered at the complaint evaluation stage — before the investigation is complete. The evaluation must assess whether the available information meets the MDR threshold; if it does, reporting proceeds on the applicable timeline regardless of whether the investigation has concluded. eLeaP’s MDR evaluation workflow structures this assessment against the Part 803 decision criteria with documented rationale at each step, and tracks the submission deadline from the complaint receipt date.

Complaint Types in Regulated Industries: Product Failures with Regulatory Consequences

Regulated-industry product complaints are categorized at intake based on the type of complaint and its potential regulatory consequence. The category determines the investigation requirements, the reporting obligations, and the CAPA threshold. eLeaP’s complaint intake form captures the complaint type as a required field that drives the downstream workflow routing.

Medical Device Malfunction or Adverse Event Complaints

A complaint that a medical device malfunctioned in a way that caused or could have caused serious injury or death is the highest-priority complaint type and the one most likely to require MDR submission under 21 CFR Part 803. The complaint must be evaluated within the MDR reporting window: 30 days for complaints involving a malfunction that could cause or contribute to serious injury if it recurs, and five days for complaints requiring remedial action to prevent an unreasonable risk to public health. The MDR evaluation is a required workflow stage in eLeaP’s medical device complaint record. The evaluation fields capture the device identification, the nature of the malfunction, the patient outcome if applicable, and the MDR determination with documented rationale.

Drug Product Quality Complaints

Drug product quality complaints — complaints about tablet appearance, unusual odor, container defects, foreign particulates, or potency concerns — trigger the Part 211.198 investigation requirement when they indicate a possible failure to meet specifications. The investigation must determine whether the complaint represents an isolated event or a batch-level or process-level quality failure. If the investigation indicates that the defect extends to the distributed product, a recall evaluation is required. In eLeaP, the drug product complaint record links to the batch record for the lot identified in the complaint, allowing the investigation to access production and testing data for the specific lot without manual data retrieval.

Adverse Drug Experience Reports

Adverse drug experience reports — complaints describing an adverse event in a patient who used the drug product — trigger MedWatch reporting obligations. For approved drugs, expedited 15-day reporting of serious unexpected adverse experiences is required under 21 CFR Part 314.81(b)(1), and for certain marketed drugs, under 21 CFR Part 310.305. For investigational drugs, expedited reporting is governed by 21 CFR Part 312.32. Periodic adverse experience reports are required quarterly for the first three years following approval and annually thereafter. eLeaP’s adverse experience complaint record captures the mandatory MedWatch fields at intake, generates the reportable event documentation from the record data, and tracks the submission status and date against the applicable reporting window.

Field Safety and Post-Market Complaints

Field safety complaints — reports of device performance issues identified in the field that may require a Field Safety Corrective Action or recall — require evaluation against the manufacturer’s field safety and recall procedures. The complaint record in eLeaP captures the device configuration in use at the time of the complaint, the implant or installation date where applicable, and the healthcare facility or distribution channel from which the complaint originated. If the field safety evaluation indicates that a correction or removal is required, the complaint record links to the field safety or recall management record initiated in response.

Complaint Intake and Evaluation Workflow: Capturing the Right Information at the Right Time

The regulatory requirement that complaints be evaluated for reportability and investigation necessity is time-sensitive. eLeaP’s complaint intake form captures the information required to make initial evaluation decisions at the point of intake, before the complaint is routed for investigation.

Required intake fields in eLeaP’s complaint record include the complaint source and date received, the product identification including lot number and serial number where applicable, the nature of the complaint and the patient or user outcome if reported, the reporter’s contact information, and the initial complaint classification by type. The classification at intake automatically routes the complaint to the appropriate evaluation workflow: an MDR-potential device complaint routes immediately to the quality unit for MDR evaluation; a drug product quality complaint routes to the quality control unit for investigation determination; an adverse drug experience routes to pharmacovigilance for MedWatch evaluation.

The evaluation stage in eLeaP is a structured workflow rather than a free-text assessment. For medical device complaints, the MDR evaluation walks through the Part 803 decision criteria: did a device malfunction occur, was there a death or serious injury, could the malfunction cause or contribute to serious injury if it recurred. Each criterion is assessed and documented with the rationale, and the MDR determination — reportable, not reportable, or undetermined pending investigation — is the documented output of the evaluation stage. The determination and its rationale are part of the complaint record’s permanent, immutable history under 21 CFR Part 11.

MDR and MedWatch Reporting: Mandatory Fields, Submission Tracking, and Regulatory Deadlines

eLeaP captures all mandatory eMDR fields within the complaint record structure. The mandatory fields for a manufacturer MDR include the manufacturer’s name, address, and contact information; the device identification including the UDI, model number, catalog number, and lot number; the patient information and outcome; the event description; and the initial and follow-up report dates. These fields populate from the complaint intake record, from the device master record in the quality system, and from the investigation findings — reducing the manual data entry required to generate the MDR submission documentation.

The MDR submission tracking in eLeaP records the submission date against the applicable reporting window, the FDA acknowledgment date, and the status of any follow-up reports required after the initial submission. When an investigation produces new information that changes the initial MDR determination or requires an amendment to a submitted MDR, the amendment record links to the original MDR submission in the complaint record. Overdue MDR submissions generate escalation notifications to the regulatory affairs function before the reporting deadline passes.

For MedWatch reporting under the adverse drug experience program, eLeaP’s adverse experience complaint record captures the Form FDA 3500A mandatory fields: the patient information, the adverse event description and outcome, the suspect drug including dosage, route, and indication, the concomitant drugs, the reporter information, and the suspect drug manufacturer information. The completed MedWatch record generates the submission documentation from the captured data. Expedited 15-day reports for serious unexpected adverse experiences are tracked against the 15-calendar-day window from the receipt date documented in the complaint record.

Complaint Investigation and CAPA Linkage: A Single Traceable Record Chain

Every complaint that requires investigation and reveals a quality system failure should generate a CAPA. In practice, that connection depends on a quality professional remembering to initiate the CAPA, linking it to the complaint record, and maintaining the connection as both records progress. In a system where complaint records and CAPA records live in different applications, that connection is frequently lost — the complaint closes, the CAPA is opened separately, and six months later nobody can reconstruct the chain from the customer complaint to the systemic corrective action taken.

eLeaP creates the complaint-to-CAPA link structurally. When a complaint investigation concludes that the complaint represents a quality system failure — a manufacturing defect, a process control gap, a supplier quality failure — the CAPA is initiated directly from within the complaint record. The complaint description, the investigation findings, and the identified quality system failure carry forward into the CAPA record as the originating input. The complaint record shows the linked CAPA status in real time. The CAPA record references the complaint as its originating input.

The traceability chain is complete in both directions. A regulatory inspector reviewing the complaint record can see the investigation findings and navigate to the CAPA without leaving the complaint record view. A quality manager reviewing the CAPA can see the originating complaint, the patient or user impact reported, and the product identification without navigating away from the CAPA record. This bidirectional traceability satisfies what ISO 13485 Clause 8.2.2 and 21 CFR § 820.35 together require, and it is available as a native capability in eLeaP rather than as a manually maintained cross-reference.

Complaint trending is a native analytical function in eLeaP’s complaint management module. When multiple complaints reference the same device model, the same drug product lot family, the same failure mode, or the same complaint type, the trend surfaces in the complaint trending dashboard. Complaint trends indicating a systemic product quality issue generate notifications for quality management review and, where the trend meets the CAPA threshold, can initiate a CAPA directly from the trending view with all contributing complaint records linked. A manufacturer that waits for a regulatory inspection to identify a complaint trend has missed the signal that the quality system should have surfaced proactively.

Evaluating Complaint Management Software for Regulated Industries: Five Questions

Complaint management software ranges from general customer service platforms to regulated-industry quality tools with the specific workflow depth that QMSR § 820.35, ISO 13485 Clause 8.2.2, 21 CFR Part 211.198, and 21 CFR Part 803 require. Many general-purpose complaint platforms — including broad compliance platforms built on CRM infrastructure — approach complaint management from a customer service frame: intake, routing, and resolution tracking. The questions below test the regulatory workflow depth that a quality team in a medical device or pharmaceutical company actually needs.

eLeaP’s answers to all five questions are yes, demonstrable in a scoped walkthrough configured for the buyer’s product type and regulatory framework. The demo covers the intake-through-MDR-evaluation workflow for a medical device malfunction complaint and the complaint-to-CAPA linkage for a drug product quality complaint.

Frequently Asked Questions

What is complaint management software for regulated industries?

Complaint management software for regulated industries is a quality system application that manages the full complaint handling process — from intake through investigation, regulatory reporting evaluation, and CAPA linkage — in compliance with the applicable regulatory framework. For medical device manufacturers, the governing requirements are ISO 13485 Clause 8.2.2 and 21 CFR § 820.35 under QMSR. For pharmaceutical manufacturers, the governing requirement is 21 CFR Part 211.198. General customer service complaint tools satisfy neither framework — they track complaint resolution but do not enforce the intake fields, investigation requirements, MDR evaluation workflow, or CAPA connection that regulated manufacturers must maintain.

What is the difference between a complaint and a nonconformance in a QMS?

A nonconformance is a failure to meet a specified requirement detected within the manufacturer’s quality system — typically identified at incoming inspection, in-process testing, or final release. A complaint is a report of an alleged deficiency in the identity, quality, durability, reliability, safety, effectiveness, or performance of a product that has reached the market and is in the hands of a customer, patient, or healthcare professional. The key regulatory distinction is that complaints carry external reporting obligations — MDR under 21 CFR Part 803 for medical devices, MedWatch under applicable adverse experience reporting regulations for drugs — that nonconformances do not. Both may generate CAPAs, but the complaint investigation has additional regulatory dimensions that a nonconformance investigation does not.

What does 21 CFR Part 820.198 say about complaint handling under QMSR?

21 CFR Part 820.198 was eliminated when FDA restructured 21 CFR Part 820 under the Quality Management System Regulation (QMSR), effective February 2, 2026. Medical device complaint handling requirements now map to ISO 13485:2016 Clause 8.2.2, which is incorporated by reference into Part 820 under QMSR. FDA retained specific complaint record content requirements in 21 CFR § 820.35, which specifies the fields that must be documented in complaint files and investigation records. Device manufacturers transitioning from QSR to QMSR should update their complaint handling SOPs to reference Clause 8.2.2 and § 820.35 rather than the superseded § 820.198.

When is an MDR required for a medical device complaint?

A Medical Device Report is required under 21 CFR Part 803 when a manufacturer becomes aware that a device it manufactures may have caused or contributed to a death or serious injury, or when a device malfunctioned and would be likely to cause or contribute to a death or serious injury if the malfunction were to recur. The standard reporting window is 30 days from the date the manufacturer received or otherwise became aware of information that reasonably suggests a reportable event occurred. A five-day window applies to events requiring remedial action to prevent an unreasonable risk to public health. The MDR obligation is triggered at the point of awareness — not at the point of investigation completion.

What does 21 CFR Part 211.198 require for pharmaceutical complaint handling?

21 CFR Part 211.198 requires that pharmaceutical manufacturers establish written procedures for handling all written and oral complaints about drug products. Any complaint indicating a possible failure to meet specifications must be investigated. The written complaint record must include the drug product name and strength, lot number, complainant name, nature of the complaint, reply to the complainant, investigation findings, and any follow-up. Critically, any complaint requiring investigation must be reviewed with respect to the possibility of a product recall — the quality control unit must evaluate whether the potential defect extends to distributed lots. This recall evaluation obligation is absent from general-purpose complaint tools.

How does complaint management software connect to CAPA?

In a system without structural complaint-to-CAPA linkage, the connection between a complaint investigation finding and the corrective action taken depends on manual steps: a quality professional initiates a CAPA separately, cross-references the complaint record number, and maintains the link as both records progress. When complaint and CAPA systems are separate applications, this connection is frequently lost or incomplete — creating the traceability gap that regulators identify when they ask to see the corrective action taken in response to a specific complaint. Complaint management software with native CAPA integration creates this link structurally: the CAPA is initiated from within the complaint record, the complaint inputs carry forward into the CAPA, and both records maintain bidirectional visibility of each other’s status.

What complaint trending capabilities should regulated manufacturers require?

Complaint trending is a post-market surveillance obligation, not just an analytics feature. ISO 13485 Clause 8.2.1 requires that manufacturers collect and analyze data from post-production activities to monitor product safety and performance. Complaint trends — patterns by failure mode, device model, lot family, or complaint type — are the primary signal that post-market quality monitoring is designed to detect. Complaint management software should surface these patterns automatically rather than requiring manual analysis of complaint exports. When a trend indicates a systemic product quality issue, the system should support direct initiation of a CAPA from the trending view with all contributing complaint records linked — preserving the traceability from the market signal to the corrective action.

See eLeaP Complaint Management in a Scoped Demo

The demo covers the intake-through-MDR-evaluation workflow for a medical device malfunction complaint and the complaint-to-CAPA linkage for a drug product quality complaint — configured for your product type and regulatory framework.

Request a scoped evaluation at quality.eleapsoftware.com/get-free-demo/

Related resources: