What this is
What is a customer complaint record?
What is a customer complaint record?
A customer complaint record is the intake record of a complaint received from a customer, capturing who they are, what they experienced in their own words, the product involved, and the immediate handling that followed. It is opened at first contact and carries a case ID through investigation and response.
What counts as a reportable event on this record?
An illness or injury reported by the complainant, or regulator involvement, either of which triggers obligations beyond internal quality process. Both are captured as explicit flags on the record rather than left to be inferred from the complaint category.
Why does severity get assigned this early?
Severity drives what happens next, how fast it is escalated, whether stock is held, whether an investigation is opened, so it has to be assigned at intake rather than after investigation. The trade-off is that an early severity judgement is provisional and should be revisited once more is known, not treated as final.
Scope
When is a customer complaint record required?
This record is the intake step in a longer complaints programme. Using it to also capture the investigation or the response produces a record that tries to do three jobs and does none of them well.
Use this template when
- A complaint has been received directly from a consumer, retail customer, foodservice customer, distributor or regulator
- A new case is needed; each one gets its own ID in the form CASE-2026-000
- The complaint needs to be assessed for severity and any immediate handling, such as a stock hold, decided
- An illness, injury or regulator contact has been reported and needs to be flagged and escalated
- A linked investigation or response record needs this case to exist first
Do not use it for
- Complaint Investigation Record, which traces the complaint back to the batch, line and shift that made the product.
- Complaint Response Record, which records what was said back to the customer, when and by whom.
- Complaint Trend Review, which pulls together complaints over a period to show the pattern behind them.
- Root Cause Analysis, which determines why the defect occurred once the investigation has narrowed the cause.
- Anything outside KnowQuality, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 9001 cl.9.1.2 requirements does this satisfy?
The obligation behind this record splits across a management-system requirement to monitor customer perception and a dedicated standard for how a complaint should actually be handled, and the two are easy to conflate.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.9.1.2 | Monitoring of customer perception of the degree to which requirements have been met, with complaints as a defined input | Header |
| ISO 10002 cl.7 | Receipt, initial assessment and acknowledgement of a complaint, recorded and tracked to a decision | Immediate handling |
| ISO 9001 cl.8.7 | Identification and control of nonconforming outputs where a complaint indicates product already released is affected | Immediate handling |
| ISO 9001 cl.10.2 | Reaction to nonconformity and evaluation of the need for corrective action to eliminate the cause | Immediate handling |
| ISO 9001 cl.8.5.2 | Identification and traceability of outputs, linking a complaint to the batch and production date it concerns | Product details |
| FDA 21 CFR Part 117, Preventive Controls for Human Food | Hazard analysis reassessed when new information, including a reported illness, indicates it may no longer be adequate | What they experienced |
What it does not cover
- Complaint Investigation Record, which traces the complaint back to the batch, line and shift that made the product.
- Complaint Response Record, which records what was said back to the customer, when and by whom.
- Complaint Trend Review, which looks for the pattern across complaints rather than the single event.
- Root Cause Analysis, which determines why the defect occurred once the investigation has narrowed the cause.
- Hold and Release Record, which manages the disposition of stock once product is placed on hold.
Global
Customer Complaint Record requirements by country
The duty to have a complaints process is close to universal under quality standards; what varies is whether a complaint of a particular kind also triggers a duty to notify someone outside the organisation.
FDA Reportable Food Registry and 21 CFR Part 117
An illness or injury complaint tied to a specific food product can trigger a mandatory reporting obligation distinct from internal quality handling.
The illness flag is not a severity label, it is the trigger for a regulatory decision that internal process alone does not satisfy.
Food Safety Act 1990 and BRCGS Global Standard Food Safety Issue 9
Retailer certification audits sample complaint records specifically to test whether illness and allergen complaints escalate correctly.
A record where the category masks an illness signal is one of the more common findings in a retailer audit, and it lands here first.
ISO 10002:2018
Defines the complaints-handling framework, receipt, assessment, acknowledgement, investigation, response and closure, that this record broadly follows.
Auditors expect each stage evidenced, acknowledgement time recorded rather than assumed, and a link to investigation or response beyond a minor complaint.
How to complete it
How to complete a customer complaint record, step by step
Most of this record is filled in from what the customer already said. The judgement is in how that account gets translated into the fields that decide what happens next.
What Happened In Their Words should be read in full before Illness Or Injury Reported and Regulator Involved are answered, not after Complaint Category is chosen. The category is a filing decision made for speed; the flags gate escalation and need to be answered from the account, not the category.
Same Batch Still In Stock and Stock Affected By This Batch should come from an actual stock check, not the complaint's apparent severity. A minor-sounding complaint about a widely distributed batch is a bigger exposure than a critical one about stock that sold out weeks ago.
Acknowledgement To Complainant and Acknowledgement Time Hours should reflect when contact actually happened, not when it was supposed to. A record completed at day's end with an assumed time is not evidence of a timely response, whatever the target is.
Escalation and the investigation link should follow from what the complaint indicates, not how busy customer service is that day. A critical or major complaint with no investigation ID attached is an open case dressed as a closed one.
What auditors find
Most common customer complaint record findings
Findings here concern the gap between what was recorded and what the narrative actually said, more often than a missing field.
| Finding | Clause | What fixes it |
|---|---|---|
| Illness or injury described in the narrative but the flag left at no. | ISO 10002 cl.7 | Require the narrative to be reviewed against the illness flag before the record can be saved. |
| Stock affected by this batch marked no with no record of an actual stock check. | ISO 9001 cl.8.7 | Require a stock check reference or note before the field is answered either way. |
| Severity set to critical or major with no investigation ID attached. | ISO 9001 cl.10.2 | Route severity above minor automatically to open an investigation record. |
| Acknowledgement marked complete with no acknowledgement time recorded. | ISO 10002 cl.7 | Capture the actual contact timestamp rather than accepting a yes with a blank hours field. |
| Regulator involvement left blank on a complaint whose narrative describes a reportable symptom. | FDA 21 CFR Part 117 | Cross-check the narrative against the regulator flag as part of initial assessment, not after the fact. |
| Case closed with no linked response record showing what was told to the customer. | ISO 10002 cl.7 | Require a response ID before the case status can move to closed. |
Case in point
Case in point: the complaint that was coded before it was read
A customer contacted a dairy producer about a tub of cream cheese, describing an unusual grainy texture. Customer service coded it Texture, severity Minor, and moved on; the narrative also noted, in passing, that the customer's throat had felt tight after eating it, but the call was already filed under a category that prompted no one to check further.
Four days later a second complaint arrived about the same batch, this time clearly describing an allergic reaction. The investigation found the first narrative had described the same symptom in softer language, and that the batch was never checked against stock because Stock Affected By This Batch had been answered no on the strength of the Texture category, not an actual look. By then the batch had reached other customers. The lesson was not that severity had been misjudged, it was that the narrative was never checked against the illness flag at all.
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.
5 sections
- Reference
- QUA-023
- Archetype
- Record
- Record ID
- CASE-2026-000
- Scoring
- Severity band
- Direction
- High is bad
- Singleton
- No
- Basis
- ISO 9001 cl.9.1.2
- Links
- Feeds RCA, CAPA
- Tags
- Quality, Customer
- Sections
- 5
- Fields
- 40
- Follow up fields
- 5
- Repeating sections
- 0
- Links out
- 4
Header
6 fieldsCase ID*
Auto sequence. Format CASE-2026-00000.
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
Who complained
5 fieldsComplaint Source*
Consumer, retail customer, foodservice customer, distributor or regulator.
Customer Or Consumer Name
Contact Method*
Contact Details
Permission To Contact
What they experienced
7 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
Complaint Severity*
- Critical0 pts
- Major1 pt
- Minor2 pts
- Comment3 pts
What Happened In Their Words*
Illness Or Injury Reported*
Any reported illness or injury escalates immediately and may be reportable.
- No3 pts
- Yes0 pts
Medical Attention Sought
Number Of People Affected
Regulator Involved
- No3 pts
- Yes0 pts
Product details
9 fieldsBatch Number
Numeric key joining to your ERP batch record.
Links to External system reference
Product
Production Date
Date Code On Pack
Where Purchased
Storage Since Purchase
Product Or Sample Available*
- Yes3 pts
- No0 pts
Photograph Provided
Return Record ID
Links to QUA-008 Case ID
Immediate handling
13 fieldsAcknowledged To Complainant*
- Yes3 pts
- No0 pts
Acknowledgement Time Hours*
Same Batch Still In Stock*
Stock Affected By This Batch*
- No3 pts
- Yes0 pts
Quantity Affected
Hold ID
Raise the hold record, then enter its reference.
Links to QUA-003 Hold ID
Product Location
Where the affected product physically is right now.
Investigation ID
Links to QUA-024 Investigation ID
Escalated To Senior Management*
Logged By*
Signature*
Quality*
Second Signature*
QUA-023 · record IDs look like CASE-2026-000 · Feeds RCA, CAPA
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The record itself is a short intake form. What actually fails is what happens between the narrative being written and anyone checking it against the flags that matter.
Holds the case against its investigation and response records, and flags severity above minor with no linked investigation ID.
Reads the narrative against the illness and regulator flags, surfaces a mismatch for review, and holds any escalation for approval before it is raised.
Tracks reportable events against notification obligations, so an illness or regulator flag does not stay an internal decision alone.
Checks the batch against current stock location the moment stock affected is answered, rather than leaving it an assumption.
This template lives in KnowQuality — quality and food safety. HACCP, nonconformance, traceability, laboratory and customer complaints.
Meet KnowQuality→Glossary
Customer Complaint Record definitions and key terms
- Case
- The complaint record and its ID, opened at first contact and carried through investigation and response rather than closed and reopened at each stage.
- Severity band
- The provisional rating of how serious a complaint is, assigned at intake to decide urgency and escalation, and open to revision once more is known.
- Complaint category
- The taxonomy a complaint is filed under for routing and reporting, chosen quickly and not a substitute for reading the full narrative.
- Reportable event
- An illness, injury or regulator contact reported by the complainant, which triggers obligations beyond the internal quality process regardless of the assigned severity.
- Immediate handling
- The decisions taken at intake before investigation is complete: acknowledgement, stock check, hold, and escalation.
FAQ
Frequently asked questions about customer complaint record
Should severity be assigned before or after investigation?+
Before, provisionally. Severity at intake decides how fast the case moves and whether stock is checked; waiting for the investigation to finish first defeats the purpose. Revisit it once the investigation reports back.
What counts as a reportable event?+
An illness or injury the complainant reports, or contact from a regulator, either of which is flagged and escalated regardless of what category was chosen. Neither should be inferred from the category alone.
What if the customer will not give permission to be contacted?+
The complaint is still recorded and assessed on the information given; permission to contact affects whether an update reaches the complainant directly, not whether the internal process runs.
How fast should acknowledgement happen?+
Fast enough that the hours field reflects a genuinely prompt response, not a target retrofitted at day's end. What counts as prompt depends on severity: a critical complaint should be acknowledged far sooner than a comment.
What happens if the same batch is still in stock?+
It should trigger an actual check against Stock Affected By This Batch, with a hold record raised where the batch is confirmed present, rather than the question being answered from assumption.
Does every complaint need an investigation record?+
Not every one, but anything above minor severity should link to one; the absence of that link on a critical or major case is one of the clearest signs the case was closed before it was handled.
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
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
Complaint Trend Review
Pulls together complaints over a period to show the patterns behind them
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 8.5.2, 8.7, 9.1.2 and 10.2
- ISO 10002:2018, Quality management — Customer satisfaction — Guidelines for complaints handling in organizations
- FDA 21 CFR Part 117, Preventive Controls for Human Food
- BRCGS Global Standard Food Safety, Issue 9
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.