SOP: Product Complaint Handling, Intake to Closure

This is a ready-to-use SOP for handling product quality complaints from the moment one arrives to the moment the file is closed. Replace every <<FILL: ...>> placeholder with your own specifics, set your document numbers and dates, and route it through your normal document control, review, and approval. A worked filled specimen follows the template so you can see how a completed record reads.

This document is educational. It is written to be adapted, not adopted as-is. Reporting obligations depend on your products, your markets, your authorisations, and the commitments you have made to your health authorities. Confirm every cited regulation against the current published source, and confirm every clock with your own regulatory affairs and pharmacovigilance functions, before you rely on any of it. Issuing this procedure does not by itself create compliance; it only structures work your quality system still has to do.

Document control header

1. Purpose

This procedure defines how <<FILL: COMPANY NAME>> receives, records, classifies, investigates, reports, and closes product quality complaints for marketed and, where stated, investigational product. The objectives are to capture every complaint faithfully, to recognise the ones that carry a safety or reporting obligation before the deadline passes, to investigate at a depth proportionate to risk, and to leave a record from which a reviewer can reconstruct what was decided and why.

A complaint is the only quality input that originates outside your control. It is often the first visible edge of a defect that has already reached patients. Handling it as an administrative task rather than a quality event is the failure mode this procedure is written to prevent.

2. Scope

This procedure applies to all written, electronic, and oral communications alleging a deficiency in the identity, quality, purity, potency, stability, safety, performance, packaging, or labelling of product placed into distribution by <<FILL: COMPANY NAME>>, received through any channel, in any market listed in the header. It covers drug products, licensed biological products, cell and gene therapy products, and the drug or biologic constituent parts of combination products.

In scope:

• Complaints received from patients, caregivers, healthcare professionals, pharmacies, hospitals, wholesalers, distributors, contract partners, regulators, and internal staff including sales and medical affairs.
• Complaints received about product manufactured or packaged on your behalf by a contract organisation.
• Complaints arising from returned goods inspection where the return alleges a defect.

Out of scope, but interfacing with this procedure:

• Adverse event case processing and expedited safety reporting, which run under <<FILL: pharmacovigilance SOP-ID>>. This procedure defines only the screening and handoff.
• Recall and field action execution, which runs under <<FILL: recall SOP-ID or plan-ID>>. See the recall and field action plan.
• Internal deviations and out-of-specification results, which run under <<FILL: deviation SOP-ID>> and <<FILL: OOS SOP-ID>>.
• Non-complaint enquiries such as storage questions, certificate of analysis requests, pricing, or supply questions, which are logged under <<FILL: customer enquiry procedure>>. Where the distinction is not obvious, log it as a complaint and let triage decide.

3. Responsibilities

The separation that matters most: intake captures, QA classifies. The person who answers the phone must not be the person who decides the complaint is not real. Merging those two roles is how genuine complaints disappear before anyone qualified sees them, and it is a structural finding an inspector can identify from your org chart alone.

4. Definitions

• Product quality complaint: any written, electronic, or oral communication alleging a deficiency related to the identity, quality, durability, reliability, safety, effectiveness, or performance of a product after it has been released for distribution.
• Adverse event: an untoward medical occurrence in a person who received the product, whether or not it is considered related to the product. A complaint and an adverse event are independent things that frequently arrive in the same phone call.
• Verbatim account: the complainant’s own description of what happened, recorded in their words before any structured questioning or categorisation is applied.
• Date of awareness: the date any employee, agent, contractor, or affiliate of the company first receives the information. Reporting clocks generally run from awareness, not from the date the complaint is logged in the system and not from the date the investigation concludes.
• Confirmed complaint: the alleged defect was reproduced, demonstrated, or otherwise established by objective evidence.
• Unconfirmed complaint: the alleged defect could not be established, either because no sample was available or because the evidence did not support it. Unconfirmed is a conclusion, not a reason to stop investigating.
• Reportability: the determination of whether the facts of a complaint trigger a submission to a health authority, and under which regulation and clock.
• Complaint rate: complaints of a defined type divided by units distributed over a defined period, normally expressed per 10,000 or per 100,000 units.

5. Procedure

5.1 Intake and verbatim capture

1. Record the complaint at the moment of contact. For an oral complaint, write it down during or immediately after the call. 21 CFR 211.198(a) requires written procedures covering written and oral complaints, so “it was only a phone call” is not an acceptable reason for the absence of a record.
2. Capture the complainant’s account verbatim before you ask structured questions. Structured questions bias the description toward your categories and can bury the detail that later turns out to matter. The verbatim text is preserved in the file permanently; category codes supplement it, they never replace it.
3. Capture reporter identity, reporter type, and contact details, and record consent to be contacted for follow-up. Record “declined” or “anonymous” explicitly rather than leaving the field blank.
4. Capture product name, strength, presentation, batch or lot number, expiry date, and quantity affected. Pursue the lot number actively. Without it you cannot reach the batch record, the reserve sample, or the other complaints on that lot. Where the complainant cannot provide it, record what was asked, what was offered instead (carton photograph, dispensing record, pharmacy contact), and the outcome of the attempt.
5. Determine whether a sample can be returned and, if so, arrange the return during the first contact. Physical evidence obtained on day one is frequently unobtainable on day ten.
6. Acknowledge receipt to the complainant within <<FILL: acknowledgement target, e.g. 2 business days>> where a response is expected.
7. Route the complete record to QA triage. Intake staff have no authority to close, merge, downgrade, or reclassify a complaint.

Use the product quality complaint intake and triage form as the intake record for this step.

5.2 Adverse event screening at intake

This screen runs at intake, on every complaint, before triage, and its answers are recorded whether they are positive or negative. A blank screen is treated as a screen not performed.

If any answer is Yes or Unclear, refer the case to pharmacovigilance the same working day, record the date, time, recipient, and the safety case reference, and obtain acknowledgement. The referral is made on the facts as received; the intake handler does not assess seriousness, expectedness, or causality, and does not wait for the quality investigation.

The safety route never waits on the quality route. The laboratory result does not change whether a patient was hospitalised, and the expedited clock started on the date of awareness regardless of what the laboratory eventually finds.

5.3 Complaint numbering

1. Assign a unique complaint number at first contact, before triage, using the format <<FILL: numbering convention, e.g. CMP-YYYY-NNNN>>. Numbers are issued sequentially by <<FILL: system or register>> and are never reused, reissued, or voided.
2. If a complaint is later found to duplicate an existing one, keep both numbers and cross-reference them. Do not delete the duplicate; record the linkage and the reason.
3. If a single contact reports defects in more than one product or more than one lot, <<FILL: state your convention, e.g. open a separate complaint number per product/lot combination and cross-reference them>>. Whichever convention you choose, apply it consistently, because trending depends on the unit of count being stable.
4. Where a complaint carries a suspected adverse event, record the safety case reference in the complaint file and the complaint number in the safety case, so the two records point at each other.

5.4 Triage and severity classification

Triage assigns severity, sets investigation depth and timeline, and determines whether escalation is immediate. Classify on the potential consequence of the alleged defect if it is real and if it is present across the lot, not on the outcome that happened to occur in the one unit reported, and not on the commercial cost.

Rules that keep classification reproducible:

1. Where two dimensions disagree, take the higher. A cosmetic-looking defect on a sterile product is not Minor if it raises a container closure question.
2. Severity is assigned on the alleged defect, not the confirmed defect. You classify before you know. Reclassification after investigation is permitted, but the original classification, the new classification, the reason, and the approver are all recorded. Silent downgrades are the single most damaging habit in a complaint system, because they corrupt the trend as well as the file.
3. Absence of reported harm does not lower severity. Suspected contamination of an injectable is Critical whether or not anyone was hurt.
4. Multiple Minor complaints on one lot are a trend question, not a severity question. Do not inflate individual severity to force attention; escalate through the threshold mechanism in the complaint trending and threshold log.

Record the assigned severity, the specific facts that drove it, the person who assigned it, the date, and QA concurrence. A severity with no recorded basis is a checkbox, and an inspector will read it as one. For the wider event triage logic across deviations, complaints, and other quality events, see quality event classification and triage.

5.5 Reportability assessment

Every complaint receives a documented reportability assessment, including complaints assessed as not reportable. The assessment names the regulation considered, the conclusion, the rationale, the decision maker, and the date. “Not reportable” with no rationale is indistinguishable from “never assessed”.

Run the assessment against the complaint reportability decision matrix, which sets out the branches and clocks in detail. In outline:

Three rules that prevent the most common failure:

1. The clock runs from awareness, not from confirmation. A pending investigation does not pause a deadline.
2. Assess reportability before the investigation concludes, and revisit it when the investigation concludes. Two assessments, both recorded, is correct. One assessment at closure is late.
3. You can withdraw or close out a report as not required with a documented rationale. You cannot recover a missed deadline. When the assessment is genuinely borderline and the deadline is near, escalate rather than deliberate.

5.6 Investigation

1. Decide whether an investigation is required, and record the decision either way. Where the decision is not to investigate, record the justification and the name and role of the person who made it. A no-investigation decision that is unattributed or unjustified is one of the most frequently cited complaint-file findings.
2. Assemble the file. Batch record, certificate of analysis, reserve or retention sample location, in-process and release data, environmental monitoring data where relevant, deviations and out-of-specification results on the lot, change records in the relevant window, and every prior complaint on the same lot and the same defect type.
3. Receive and examine any returned sample. Photograph it on receipt before handling. Document condition on arrival, packaging integrity, and shipping conditions. Confirm identity, that it is your product and the lot claimed, before any testing.
4. Test against the release specification. The comparison an inspector expects is: does the returned unit meet the specification the lot was released against. Where the alleged defect is not covered by a release test, define and justify the additional testing.
5. Review the batch record and the deviation history for anything that correlates with the defect, including marginal or trending results that passed. Link to the deviation management and out-of-specification investigation records where they exist.
6. Run the cluster and trend check on the lot and the defect type. One complaint is an anecdote. The query result, including a nil result, is recorded in the file.
7. Determine root cause using a method proportionate to severity. See root cause analysis techniques. Where root cause cannot be determined, record what was ruled out and why, not simply that it was not found.
8. Assess product impact and the need for field action explicitly, including when the answer is none. Where the defect could affect distributed stock, escalate under the recall procedure. See recall management and field actions.
9. Record the conclusion: confirmed, unconfirmed, or not determinable, with the evidence that supports it.
10. Revisit the reportability assessment in light of the conclusion and record the result.

Use the complaint investigation report form as the investigation record.

The unconfirmed complaint. Where no sample is returned or the returned sample meets specification, the investigation continues: reserve sample examination, batch record and deviation review, plausibility assessment against the process as run, cluster check on the lot and defect type, and an assessment of whether product design, labelling, or instructions for use make the reported experience likely. “No sample, no investigation” and “sample passed, file closed” are both closure shortcuts rather than conclusions, and both are routinely cited. An unconfirmed complaint is still trended, and a run of unconfirmed complaints on one defect type is itself a signal.

5.7 CAPA linkage decision

Not every complaint becomes a CAPA. Forcing one-to-one linkage floods the CAPA system and slows the actions that matter. The decision is made and recorded on every complaint.

Open or link a CAPA where any of the following applies:

• The complaint is confirmed and a correctable root cause has been identified.
• The complaint is Critical, whether or not it is confirmed and whether or not it is a single event.
• A pre-defined trend threshold has been crossed for that defect type, product, or lot.
• The investigation exposed a systemic weakness, for example an ambiguous label, an error-prone instruction for use, a supplier or contract manufacturer control gap, or a process capability limitation.
• A field action was taken.

Do not open a CAPA where the complaint is Minor, unconfirmed, non-recurring, and no systemic weakness was exposed. Record that reasoning; “no CAPA required because” is a decision, “CAPA: no” alone is not.

Where a CAPA is opened from a trend, link every contributing complaint to it, so that effectiveness can be measured against that population rather than against a single record. Effectiveness verification checks whether the complaint rate for that defect actually fell after the action was implemented. See what is a CAPA and CAPA effectiveness verification.

5.8 Closure and reply to complainant

A complaint closes only when all of the following are true:

1. The investigation is complete and the conclusion is recorded with supporting evidence.
2. The reportability assessment is documented, and any required report has been submitted with its reference recorded in the file.
3. The pharmacovigilance route, where one was opened, is acknowledged and its case reference is recorded.
4. The CAPA decision is recorded, and any CAPA raised is referenced.
5. Any field action decision is recorded.
6. The returned sample has been dispositioned and the disposition recorded.
7. A reply has gone to the complainant where one was due, or the reason none was due is recorded.
8. QA has approved closure.

Reply to the complainant. Where the complainant is contactable and expects a response, provide one that states that the complaint was investigated, the outcome in plain terms, and any action taken or advice given (for example, how to obtain replacement product, or how to handle remaining stock). Do not disclose confidential investigation detail, other complainants, other patients, or commercial information. Where the complaint carried a suspected adverse event, coordinate the wording with pharmacovigilance and medical so that the quality reply does not make a clinical statement it is not qualified to make. Record the date, method, and a summary of what was said.

5.9 Timelines

Set each target from your product risk, your resourcing, and any market commitments, then hold yourself to it. The regulatory clocks in the shaded rows are fixed by regulation and are not yours to set; confirm each against the current source and with regulatory affairs.

Regulatory clocks that this procedure must not breach, verify each against the current source:

An extension is a decision, not a lapse. Record the reason, the revised date, and the approval, and record it before the original target passes. A file that closes 40 days late with an extension approved on day 39 is a managed file. The same file with no extension record is a timeliness finding.

5.10 Trending interface

Complaint data is aggregated and reviewed on the cadence set in section 5.9, by defect type, by lot, by product and presentation, and over time, with rates normalised to units distributed. Thresholds are defined in advance so that escalation is objective rather than discretionary. Threshold crossings feed CAPA, the annual product review, and management review. The mechanics, the normalisation calculation, the threshold definitions, and the review record live in the complaint trending and threshold log. See also annual product review and PQR and management review under Q10.

6. Acceptance criteria

The complaint system is operating acceptably when all of the following can be demonstrated from the records:

• Every contact alleging a product deficiency received a complaint number, including those later assessed as unfounded, user related, or duplicate.
• The adverse event screen is answered and recorded on 100 percent of complaints, and every positive or unclear screen has a same-day pharmacovigilance referral with a recorded case reference.
• Severity is recorded with the specific facts that drove it, and any reclassification carries an original value, a new value, a reason, and an approver.
• The lot number is present, or the file records what was done to obtain it.
• Reportability is assessed and documented on every complaint including those assessed as not reportable, with the regulation considered, the rationale, the decision maker, and the date.
• No report was submitted outside its regulatory clock, and every submitted report has its reference recorded in the complaint file.
• Investigation depth is proportionate to severity, and the proportionality decision is recorded.
• Every decision not to investigate carries a justification and the name and role of the responsible person.
• Every unconfirmed conclusion shows what was still done: reserve sample, batch record review, cluster check, plausibility assessment.
• The CAPA decision is recorded on every complaint, with reasoning, in both directions.
• Complaints closed within the procedural target, or with an extension approved before the target passed, at a rate of at least <<FILL: e.g. 90 percent>>.
• Open complaint backlog older than <<FILL: e.g. 60 days>> does not exceed <<FILL: e.g. 5 percent>> of open files.
• Trending is performed on the defined cadence with normalised rates and pre-defined thresholds, and every threshold crossing is traceable to an action.
• Files are retrievable for inspection within <<FILL: e.g. 15 minutes>> of request.

7. Records generated

Retention for complaint records under 21 CFR 211.198(b) is at least 1 year after the expiration date of the drug product, or 1 year after the date the complaint was received, whichever is longer; for certain over-the-counter products without expiration dating the regulation provides for 3 years after distribution. Cell and gene therapy products, combination products, and other markets carry their own and frequently longer retention obligations. Set <<FILL: retention period>> to the longest applicable to your products and markets, and confirm it with regulatory affairs rather than assuming the shortest.

Complaint records are GxP records. They are subject to ALCOA+ expectations: the verbatim capture must be contemporaneous, changes to the record must be traceable, and the reportability and severity decisions must be attributable to a named, qualified person. Where the complaint system is a computerised system, it falls under 21 CFR Part 11 and EU Annex 11.

8. References

21 CFR 211.198, Complaint files. Requires written procedures describing the handling of all written and oral complaints regarding a drug product, review of complaints involving a possible failure of the drug product to meet any of its specifications, a determination of the need for an investigation under 21 CFR 211.192, and a determination whether the complaint represents a serious and unexpected adverse drug experience requiring a report to FDA. 21 CFR 211.192, Production record review, for the investigation requirement it invokes. 21 CFR 211.180, General requirements for records and reports, for retention. 21 CFR 314.80 and 21 CFR 600.80, Postmarketing reporting of adverse drug or adverse experiences, for the 15 calendar day Alert report for serious and unexpected experiences and the 15 calendar day follow-up. 21 CFR 310.305, Records and reports concerning adverse drug experiences on marketed prescription drugs for human use without approved new drug applications. 21 CFR 314.81(b)(1), NDA Field Alert Report, within 3 working days. 21 CFR 600.14, Reporting of biological product deviations by licensed manufacturers, not to exceed 45 calendar days. 21 CFR Part 4 Subpart B, Postmarketing safety reporting for combination products, where a combination product is involved. See combination products and cGMP under Part 4. 21 CFR Part 7, Enforcement policy, for recalls arising from a complaint. EU GMP Chapter 8, Complaints, Quality Defects and Product Recalls, including the expectation that quality risk management principles are applied to the investigation and assessment of quality defects and to the decisions that follow. EU GVP modules, in particular Module VI on the collection, management, and submission of reports of suspected adverse reactions, for the 15 day serious and 90 day non-serious submission timelines to EudraVigilance. Note that the serious obligation extends to cases occurring in third countries while the non-serious obligation is limited to cases occurring in the EU. ICH E2A, Clinical Safety Data Management: Definitions and Standards for Expedited Reporting, for the seriousness criteria used in the adverse event screen. ICH E2B(R3), for the individual case safety report data elements and message specification used for electronic case exchange. ICH E2D, Post-Approval Safety Data Management, for post-approval case handling definitions. ICH Q7 section 15, Complaints and Recalls, where active pharmaceutical ingredients are in scope. ICH Q9(R1), Quality Risk Management, and ICH Q10, Pharmaceutical Quality System, for the risk-based investigation depth and the management review interface.

Confirm the current version, clause numbering, and applicability of every reference above before issue. ICH guidelines are copyrighted; obtain them from the official source rather than reproducing their text in your procedure.

9. Revision history

10. Approvals

Filled specimen

The following shows how one complaint reads when the procedure has been followed. The company, product, people, and numbers are illustrative.

Complaint summary record, CMP-2026-0731

Adverse event screen (section 5.2)

Referred to pharmacovigilance 6 July 2026 at 14:48 to Drug Safety duty officer. Safety case PV-2026-0902 opened, acknowledgement received 6 July 2026. Seriousness, expectedness, and causality assessment owned by pharmacovigilance; the quality investigation did not gate the referral.

Triage and severity (section 5.4)

Reportability assessment (section 5.5)

Investigation (section 5.6)

CAPA linkage and closure (sections 5.7 and 5.8)

The point of the specimen is the sequence, not the outcome. Within two hours of the call the company had a complaint number, a recorded verbatim account, an adverse event referral on the safety clock, a Critical severity with facts behind it, and a reportability assessment naming three regulations and dismissing one of them with a reason. The laboratory result eleven days later changed the conclusion but changed none of the deadlines, because none of them had been waiting on it. Note also that the two earlier complaints on lot LB-4417 had been closed as unconfirmed with no sample: they were correct as individual conclusions and wrong as a system outcome, which is exactly why unconfirmed complaints are trended rather than filed away.

Common inspection findings this SOP prevents

• Contacts alleging a defect are recorded as enquiries or handled by customer service without ever receiving a complaint number.
• An adverse event sits inside a quality complaint with no evidence it ever reached pharmacovigilance, so an expedited report was never made.
• The adverse event screen exists on the form but is blank on a material share of files, so it cannot be shown to have been performed.
• Severity is assigned with no recorded basis, or the same defect is classified differently by different handlers, corrupting the trend.
• A complaint is downgraded after intake with no record of the original classification, the reason, or the approver.
• No lot number was obtained and no evidence exists that one was pursued, so the batch record, the reserve sample, and the cluster on that lot were never reached.
• Reportability is undocumented, so an inspector cannot tell whether the decision was sound, or made at all.
• A report was filed outside its regulatory clock because the company waited for the investigation to conclude before assessing reportability.
• A complaint was closed without investigation and with no justification and no responsible name attached to that decision.
• “Could not confirm” is used as a closure shortcut: no reserve sample examined, no batch record reviewed, no cluster check performed.
• Recurrent complaints are closed as user error without ever asking whether the labelling, the instructions for use, or the device constituent design invites the error.
• Complaints sit open months past the procedural target with no approved extension.
• Complaints, deviations, CAPA, and safety records do not cross-reference, so the same defect is investigated three times and the connection between them is invisible.
• Trending is by raw count rather than by rate normalised to units distributed, so a real rate increase is masked by growth in sales.

How to adapt this SOP

1. Set the document number, owner, approvers, effective date, and next review date in the header, and set the scope to the actual sites, affiliates, products, and markets you cover.
2. Fill every timeline in section 5.9 with numbers you can actually meet, then check the last twelve months of complaint records against them before you commit. A target you miss routinely is worse than a longer target you hold.
3. Rewrite the severity examples in section 5.4 using your own products, presentations, and real historical defects. The anchoring only works if a coordinator recognises the example. Keep the anchored definitions and the tie-breaking rules.
4. Localise section 5.5 and the reportability matrix to every market in which you distribute, and have regulatory affairs confirm each clock. The US and EU rows here are a starting point, not a complete set of obligations.
5. Point every cross-reference to your real procedures: pharmacovigilance, recall, deviation, out-of-specification, CAPA, customer enquiry, and document retention.
6. Where product is manufactured by a contract organisation, align the complaint notification and response timelines in section 3 with the quality agreement, and check that the agreement actually names them.
7. If your complaint system is electronic, name it, reference its validation record, and confirm that the audit trail captures severity and reportability changes with reason and identity.
8. For combination products, add the device constituent reporting branch and confirm the constituent-part obligations under 21 CFR Part 4 Subpart B with regulatory affairs. Keep the drug and biologic obligations primary if that is what your product is.
9. Set retention in section 7 to the longest applicable across your products and markets, not the shortest.
10. Confirm every regulation in section 8 against the current published version before issue, and repeat that check at each periodic review.