Complaints and recalls
Complaints and suspected quality defects must be recorded, investigated for product and patient impact, trended, and escalated to a recall and to the competent authority where the defect could affect patient safety.
Complaints and suspected quality defects must be recorded, investigated for product and patient impact, trended, and escalated to a recall and to the competent authority where the defect could affect patient safety.
Plain-English explanation, then the primary regulation it comes from.
Understanding complaints and recalls
Chapter 8 treats complaints, quality defects and recalls as one connected subject, because they are stages of the same escalation. A complaint may reveal a quality defect; a quality defect may require a recall; a recall requires notification to the competent authority. Sites that handle them under separate procedures tend to lose time at exactly the transitions where time matters.
Every complaint needs an assessment of whether other batches are affected — the same question that gets skipped in deviation handling, and for the same reason. A complaint about one batch that turns out to reflect a process weakness affects everything made under that weakness, and the trend data usually shows it before the individual investigation does.
Recall decisions run on a clock and cannot wait for a complete investigation. The judgement is about potential patient risk on the information available, not certainty. Recall procedures should be tested periodically — a mock recall that establishes whether you can actually reconcile distribution records within the time available is worth considerably more than a procedure nobody has exercised.
Complaint trending is the underused part. Complaints are the only routine signal that comes from outside your own system, which makes them the least self-confirming data you hold. A rising trend in a minor complaint category is frequently the earliest visible sign of a process drifting.
- Recorded and investigated
- With a designated responsible person and sufficient trained staff to handle them.
- Impact beyond the complaint batch
- Assess whether other batches share the cause.
- Recall capability tested
- Procedures exercised periodically, including out-of-hours contactability.
- Authority notification
- Competent authorities are informed where a defect may result in a recall or restriction of supply.
- Trended and reviewed
- Complaint data feeds trending, the product quality review and management review.
Common failure modes
- Complaint handling owned by commercial rather than quality, so technical complaints are closed as customer-service matters.
- No assessment of whether other batches share the cause.
- Recall procedure never tested, so nobody knows whether distribution records reconcile at speed.
- Trending performed annually for the PQR only, far too late to act as an early-warning signal.
Where this is written down
- European CommissionEudraLex Volume 4 — EU GMP guidelines
Part I, Chapter 8 — Complaints, Quality Defects and Product Recalls
- EMAEMA — Good manufacturing practice
EU procedures for handling quality defects and rapid alerts
Read next
Deviations
ReadQualityCAPA
ReadQualityBatch release
ReadQualityQuality management system (QMS)
ReadLooking for a definition rather than an explanation? The GMP glossary covers the abbreviations in one line each.
Knowing the requirement is not the same as closing the gap
If you want to know where your site actually stands against this, the readiness score covers seven quality-system domains in twenty questions, and takes about ten minutes.