What this is
What is a complaint trend review?
What is a complaint trend review?
A complaint trend review is a periodic analysis of complaints received over a period, aggregated by theme and rate rather than handled one at a time, to identify patterns an individual complaint investigation cannot see: a category rising across months, a concentration on one line, shift or product, or a gap between what customers report and what internal inspection catches.
Who carries out a complaint trend review?
Quality, working with sales and production, since the analysis is only useful if the people who can change a line, a formulation or a supplier see it. A review written by quality alone tends to describe the pattern accurately and change nothing, because the people who own the fix were never in the room.
How is this different from investigating one complaint?
A complaint investigation traces a single case back to the batch, line and shift that produced it. A trend review does not investigate any individual complaint; it looks across a period at volume, category and rate to decide whether the pattern behind many complaints points to a cause that one investigation would never surface.
Scope
When is a complaint trend review required?
This review sits above individual complaint handling, not in place of it. Where a single complaint needs tracing back to its batch or a reply drafted to a customer, this template is the wrong one.
Use this template when
- The review interval has arrived, typically monthly, or a triggering volume or category anomaly has been flagged
- A period of complaints needs aggregating by rate and theme before management review
- A rising category, a line/shift/product concentration, or a detection gap needs surfacing as a systemic finding
- A new review record is needed; each one gets its own ID in the form CTR-2026-000
- Individual complaint records already exist for the period and need rolling up into a pattern
Do not use it for
- Customer Complaint Record, which captures one complaint as it arrives, with what the customer experienced and wants
- Complaint Investigation Record, which traces one complaint back to the batch, line and shift that produced it
- Complaint Response Record, which records what was said back to the customer, when, and by whom
- Corrective and Preventive Action, which this review can trigger but does not itself carry out
- A management review record, since this template only feeds one and does not replace the review meeting itself
Compliance mapping
Which ISO 9001 cl.9.1.3 requirements does this satisfy?
ISO 9001 does not name a trend review as a document, but requires the pieces one is built from: data analysed and evaluated, customer perception monitored, and nonconformity trends fed into corrective action and management review.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.9.1.1 | Determine what needs monitoring and measuring, the methods used, and when results are analysed and evaluated | Header |
| ISO 9001 cl.9.1.2 | Monitor customer perception of the degree to which needs and expectations have been fulfilled | Volume |
| ISO 9001 cl.8.7.1 | Control of nonconforming outputs, including the nature of the nonconformity and any subsequent action | By theme |
| ISO 9001 cl.9.1.3 | Analyse and evaluate data arising from monitoring and measurement, including conformity, customer satisfaction and trends | Analysis |
| ISO 9001 cl.10.2.1 | React to nonconformity and evaluate the need for action to eliminate the cause, so it does not recur or occur elsewhere; feed status into management review | Outcome |
| ISO 9001 cl.8.2.1 | Customer communication to include obtaining customer feedback relating to products and services, including complaints | Related records |
What it does not cover
- Customer Complaint Record, which captures a single complaint as it arrives, not the pattern across a period.
- Complaint Investigation Record, which traces one complaint to the batch, line and shift responsible.
- Complaint Response Record, which is the reply sent back to the customer, not the internal analysis.
- Corrective and Preventive Action, which carries out the systemic action this review can only flag.
- The management review itself, which this record feeds as an input, not replaces as an event.
Global
Complaint Trend Review requirements by country
No jurisdiction mandates a complaint trend review by name. It arrives through certification schemes and the standards behind them, so its reach is set by contract and audit rather than statute.
FDA FSMA preventive controls; GFSI-benchmarked certification (SQF, BRCGS)
No statute names a trend review, but preventive-controls verification and retailer certification schemes expect complaint data analysed for pattern, not only actioned case by case.
A facility can close every complaint correctly and still fail an audit finding for lack of documented trend analysis.
BRCGS Global Standard for Food Safety
The standard requires complaints to be categorised, trended and reviewed at a defined frequency, with the analysis reported to management.
One of the few places the trend review is close to an explicit clause requirement rather than an inference.
ISO 9001:2015; GFSI benchmarking requirements
ISO 9001 requires analysis and evaluation of customer satisfaction data; GFSI-recognised schemes generally require it to be periodic and documented.
Audits examine whether the analysis changed a decision, not only whether a review document exists.
How to complete it
How to complete a complaint trend review, step by step
The template prompts for the count, the theme and the trend direction. What determines whether the review is worth reading is the reasoning that connects them.
Complaints per million units, not the raw count, should drive the trend direction judgement. Production volume moves independently of quality, and a review that reads the count first drafts a conclusion the rate does not support.
One line or product, one shift, one category rising sharply. Each is a distinct question, and answering them after the narrative is written tends to produce answers that fit the narrative rather than the data.
Where complaint themes and internal defect data agree, detection is working and the fix belongs in process control. Where they disagree, something customers experience is passing internal checks undetected.
A trend can turn favourable between reviews for reasons unrelated to any action taken. Deciding and recording the systemic action when the pattern is identified, rather than waiting to see if next month looks better, makes the review an intervention rather than commentary.
What auditors find
Most common complaint trend review findings
The review almost always contains a count and a chart. The findings concern whether the reasoning behind them survives being questioned.
| Finding | Clause | What fixes it |
|---|---|---|
| Trend direction judged on raw complaint count rather than complaints per million units. | ISO 9001 cl.9.1.2 | Require the rate field, compared against the previous period rate, before any narrative is written. |
| Theme categories never compared against internal nonconformance data. | ISO 9001 cl.8.7.1 | Complete the detection gap comparison every review, not only when a category looks anomalous. |
| Concentration tests answered without the underlying breakdown by line, shift or product examined. | ISO 9001 cl.9.1.3 | Require the linked product or line field populated before a concentration answer is accepted. |
| Systemic action marked not required despite a rising category or unresolved detection gap. | ISO 9001 cl.10.2.1 | Treat any rising category or detection gap as a default trigger, requiring a documented reason to override it. |
| Illness or foreign material counts reported only inside the theme table, with no separate escalation. | ISO 9001 cl.8.7.1 | Escalate illness and foreign material complaints on their own thresholds, independent of the headline trend. |
| Review completed but never reported to management review despite a systemic action raised. | ISO 9001 cl.9.3.2 | Make the reported-to-management-review field a closing condition whenever systemic action is required. |
Case in point
Case in point: the trend that hid inside a falling count
A dairy plant's complaint count fell for three consecutive months, and each review concluded the trend was improving. Production volume had fallen over the same period for seasonal reasons, and nobody had recalculated the rate. Read as complaints per million units, the rate had actually risen each month, driven by a packaging category climbing steadily as a share of a shrinking total.
A customer audit four months later flagged repeat seal failures on the same packaging line. The internal defect data for that line showed nothing unusual, because the fault was cosmetic enough to pass visual inspection but frequent enough to generate complaints. The fix was not a better narrative; it was requiring the rate field on every review and treating any category climbing as a share of total, even inside a falling count, as a mandatory concentration check.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
6 sections
- Reference
- QUA-026
- Archetype
- Review
- Record ID
- CTR-2026-000
- Scoring
- Trend direction
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 9001 cl.9.1.3
- Links
- Links Complaints; feeds CAPA
- Tags
- Quality, Analysis
- Sections
- 6
- Fields
- 41
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 3
Header
9 fieldsReview ID*
Auto sequence. Format CTR-2026-0000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Period From*
Period To*
Reviewed By*
Volume
6 fieldsComplaints Received*
Units Sold
Complaints Per Million Units*
Previous Period Rate
Trend Direction*
- Improving3 pts
- Stable2 pts
- Worsening0 pts
Target Rate
By theme
Repeats6 fieldsComplaint Category*
- Foreign material0 pts
- Illness0 pts
- Allergen0 pts
- Off flavour or odour1 pt
- Appearance2 pts
- Texture2 pts
- Packaging2 pts
- Underweight1 pt
- Labelling1 pt
- Shelf life1 pt
- Delivery or service2 pts
Count*
Percent Of Total
Trend Direction*
- Improving3 pts
- Stable2 pts
- Worsening0 pts
Substantiated Percent
Linked Product Or Line
Analysis
9 fieldsTop Three Categories*
Any Category Rising Sharply*
- No3 pts
- Yes0 pts
Concentrated On One Line Or Product*
- No3 pts
- Yes0 pts
Concentrated On One Shift*
- No3 pts
- Yes0 pts
Themes Match Internal Nonconformances*
Where complaints and internal defects agree, the internal detection is working. Where they do not, it is not.
- Yes, detection working3 pts
- Partly1 pt
- No, detection gap0 pts
Detection Gap Identified*
- No3 pts
- Yes0 pts
Illness Complaints This Period*
Foreign Material Complaints*
Response Time Average Days*
Related records
1 fieldComplaint Case ID
A representative complaint in this trend.
Links to QUA-023 Case ID
Outcome
10 fieldsSystemic Action Required*
Raise the action record, then enter its reference here.
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Reported To Management Review*
Next Review Due*
Reviewed By*
Signature*
Quality Manager*
Second Signature*
QUA-026 · record IDs look like CTR-2026-000 · Links Complaints; feeds CAPA
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The review depends on data that lives in other records: the complaint count, the internal nonconformance log, the production volume. What fails is the connection between them, not the arithmetic inside any one review.
Pulls complaint and nonconformance records into the period being reviewed, runs the rate and concentration calculations, and flags when a theme is rising as a share of total even inside a falling count.
Picks up a systemic action the moment it is raised, links it to the CAPA record, and tracks it through to verified effectiveness rather than a closed status.
Connects a systemic finding tied to method or competence to the training records it should update, so the fix reaches the people doing the work.
Watches production volume and nonconformance data alongside the complaint log, and raises the detection gap check before the review is signed rather than after.
This template lives in KnowQuality — quality and food safety. HACCP, nonconformance, traceability, laboratory and customer complaints.
Meet KnowQuality→Glossary
Complaint Trend Review definitions and key terms
- Complaints per million units
- Complaint count normalised against production volume, which a trend direction should actually be judged against rather than the raw count.
- Substantiated complaint
- A complaint confirmed by investigation to have a basis in the product or process, distinct from one where no cause was found.
- Detection gap
- A mismatch between what customer complaints report and what internal nonconformance data catches, indicating inspection is missing something.
- Concentration
- Complaints clustering on one line, shift or product rather than spreading evenly, pointing toward a specific cause rather than a general one.
- Systemic action
- A corrective action raised because a pattern across many complaints, rather than any single one, points to a cause worth eliminating.
FAQ
Frequently asked questions about complaint trend review
What is a complaint trend review?+
A periodic look across a period's complaints by rate and theme, built to surface a pattern, a rising category, a concentration on one line or shift, or a gap between customer reports and internal detection, that no single complaint investigation would reveal.
Why use a rate instead of the complaint count?+
Because count moves with production volume independently of quality. A rate, complaints per million units, describes the process; a count mostly describes how much was made. A review reading the count first can report improvement the same month the rate actually worsened.
What does a detection gap mean in this review?+
A complaint theme is rising or present without a matching rise in internal nonconformance data for the same issue. That is a finding about inspection, because it says internal checks are not catching what is reaching the customer.
How does this differ from a complaint investigation?+
A complaint investigation traces one complaint back to its batch, line and shift. A trend review looks across a period at rate and theme to find a pattern individual investigations, each closed on its own facts, would never connect.
Who should be in the room for this review?+
Quality, plus sales and production. A trend pointing at a line, a formulation or a supplier needs the people who can change those things to see the finding directly, rather than a summary after the decision not to act was already made.
What triggers a systemic action from this review?+
A rising category, a concentration on one line, shift or product, or an unresolved detection gap. Any of the three should default to raising a systemic action, with a documented reason required to override rather than to raise it.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Nonconformance and Complaints
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Product Nonconformance Report
Records product that does not meet specification
Process Deviation Report
Records a process that ran outside its set limits, even where the product still passed
Hold and Release Record
Places suspect product on hold and records the decision to release, rework or scrap it
Rework Authorization
Authorises rework on nonconforming product and sets out exactly what will be done
More in Complaints
Customer Complaint Record
Records a complaint from a customer, with what they experienced and what they want
Complaint Investigation Record
Investigates a complaint back to the batch, line and shift that made the product
Complaint Response Record
Records what was said back to the customer, when, and by whom
Customer Feedback Record
Captures feedback that is not a complaint, including praise, suggestions and survey results
Customer Visit Report
Records a customer visit or audit of your site, including what they looked at and what they raised
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 clauses 9.1.2, 9.1.3, 8.7.1 and 10.2.1
- ISO 9001:2015 clause 9.3.2, management review inputs
- BRCGS Global Standard for Food Safety, complaint handling and trend analysis
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.