description

SOP Feedback and Complaint Management

Use this SOP Feedback and Complaint Management template to systematically document, classify, and resolve feedback and customer complaints related to your medical device products. This template is essential for regulatory compliance, ensuring all feedback—including customer complaints, support requests, and negative product events—is properly monitored, evaluated, and recorded; it should be filled out whenever feedback is received from any source, especially after product release. Completing this SOP supports post-market surveillance, risk management, and continuous product improvement, meeting key requirements under MDR/IVDR, ISO 13485, and IEC 62304.
Generate ->

SOP Feedback and Complaint Management

ID: Sed ut perspiciatis unde omnis iste natus error sit voluptatem.

1. Purpose

This SOP describes how feedback and customer complaints will be received, monitored, examined, documented, and resolved.

2. Scope

This SOP covers all products that have been released by the manufacturer but can include feedback that occurs during the development process. Feedback received can initiate other processes including the potential to impact change control, vigilance and reporting, corrective and preventive actions (CAPAs), risk management, and customer support.

3. Related Documents

  • SOP Vigilance
  • SOP Corrective and Preventive Action
  • SOP Change Management
  • SOP Software Problem Resolution

4. Feedback and Complaint Data

4.1 Customer Support

Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam.

4.2 Feedback

Feedback can be related to released products or products still under development. Feedback can originate from employees of the company, current or future customers or users, experts in the field, or other sources deemed relevant. Feedback includes information relating to whether customer requirements have been met and includes data captured through the customer support channel.

Feedback is captured at regular intervals through the post-market surveillance process (see SOP Post-Market Surveillance). However, feedback identified outside of the post-market surveillance process can also be deemed relevant if subjected to the feedback and complaint management system processes.

Feedback captured outside of the normal post-market surveillance procedures and the customer complaint system can come from the following sources, or others as determined to be relevant:

  • Social media posts
  • Surveys of users or patients
  • Customer complaints
  • Scientific literature
  • Word of mouth
  • Focus groups (internal or external to company)

5. Feedback Handling Procedures

5.1 Classification of Feedback

All feedback (including customer complaints) is classified into the following categories.

A serious deterioration of the state of health is defined as being at least one of the following:

  • life-threatening illness,
  • permanent impairment of a body function or permanent damage to a body structure,
  • a condition which requires medical or surgical intervention to prevent one of the above,
  • any indirect harm as a consequence of an incorrect diagnostic result when used within manufacturer's instructions for use.

Incident means any malfunction or deterioration in the characteristics or performance of a device made available on the market, including use-error due to ergonomic features, as well as any inadequacy in the information supplied by the manufacturer and any undesirable side-effect. (MDR, Article 2)

5.2 Evaluation of Feedback

A member of the business team, quality team, or a dedicated feedback and complaint team member classifies the feedback according to the categories above.
Depending on classification, the feedback is either recorded in the Complaint Log or directed to the appropriate internal team for action.

  • Customer Complaints: Logged in the Complaint Log and processed according to appropriate processes below
  • Negative Product Events: Logged in the Complaint Log and processed according to SOP Vigilance.
  • General Feedback & Customer Support: Managed informally, unless they escalate into complaints and require further investigation.

Each type of feedback may result in a Change Request per SOP Change Management, if applicable. Additional information for processes associated with each type of feedback are described in more detail in the following sections.

5.2.1 General Feedback

  • No formal logging required unless an issue requires further investigation.
  • If the feedback identifies a potential software issue, it is forwarded to the product team per SOP Problem Resolution.
  • If the feedback indicates a potential compliance risk, it is forwarded to the quality team for CAPA Qualification per SOP Corrective and Preventive Actions (CAPA).

A problem is defined as an actual or potential behavior of a software that a user or other interested person believes to be unsafe, inappropriate for the intended use or contrary to its specification. (IEC 62304:2006)

5.2.2 Customer Support

  • Customer support issues do not require formal logging in the Complaint Log unless they escalate into complaints (if so, refer to section 5.2.3).
  • A designated team member handles support requests and may track common issues internally for future process improvements.

5.2.3 Customer Complaint

The complaint is logged in the complaint log by a business team member, quality team, or a dedicated feedback and complaint team member. Include the following information:

  • Complaint ID
  • Customer ID
  • Date the feedback was received
  • Relevant product and version (if applicable)
  • Source of complaint
  • Complaint description
  • Impact of the issue on performance and/or safety (if applicable)
  • Resolution process
  • Action taken (or justification if no action taken)
  • Date Closed

Action taken for each complaint will depend on the nature and description of the complaint. The following processes will be used for resolving complaints:

Customer complaints are reviewed annually as part of the SOP Post-Market Surveillance, including any potential trends.

5.2.4 Negative Product Event

The negative product even is logged in the complaint log by a business team member, quality team member, or a dedicated feedback and complaint team member that contains the following information:

  • Complaint ID
  • Customer ID
  • Date the feedback was received
  • Relevant product and version
  • Source of event
  • Event description
  • Impact of the issue on performance and/or safety
  • Resolution process
  • Action taken
  • Date Closed

The quality team shall be notified about any negative product events within 2 business days of determining that the feedback was a negative product event. Negative product events then undergo processes outlined in the SOP Vigilance for proper reporting and should undergo CAPA Qualification according to SOP Corrective and Preventive Action.

5.3 Feedback Resolution

The business team, quality team, or a dedicated feedback and complaint team member proactively monitors the status of the complaint log that is updated in response to feedback in order to validate that required actions are executed.

Complaint closure is dependent on the type of feedback that the event is related to. Closure procedures for feedback resolution include the following:

  • Customer Complaint: The customer complaint ticket is closed upon entering all required information into the Complaint Log. Customer complaint tickets can be reviewed by teams at any time and don't require a resolution step.
  • Negative Product Event: The negative product event ticket is closed when the information is entered into the complaint log and the quality team is notified of the event. At this point, the quality team is required to undergo reporting requirements according to SOP Vigilance and/or SOP Corrective and Preventive Action as required by the ticket.

If an investigation determines activities outside the organization contributed to the complaint, relevant information shall be exchanged between the organization and the external party involved as needed.

Mapping of Requirements

RegulationsSectionRegulation 2017/745 (MDR)Art. 83-88ISO 13485:20168.2.1 / 8.2.2IEC 62304:20066.2.1