--- url: https://www.qualityweb360.com/how-to-handle-customer-complaints-in-3-steps/ title: "Customer Complaint Management in ISO 9001: Process and Log" language: en kind: post generated: 2026-09-22T07:00:12Z source: https://www.qualityweb360.com/ --- # Customer Complaint Management in ISO 9001: Process and Log - [Home](https://www.qualityweb360.com) - [Quality Management 360](https://www.qualityweb360.com/quality-management-360/) - Customer Complaint Management in ISO 9001: Process and Log # Customer Complaint Management in ISO 9001: Process and Log Almost every guide on customer complaints lands in the same place: listen, apologise, resolve. That works for the conversation in front of you, but it is not what an auditor will ask for. In an ISO 9001 system a complaint is not only a customer service issue: it is **a mandatory input to your improvement process**, and it has to leave a trail. **The short version:** ISO 9001 complaint management has five steps that actually produce evidence: log the complaint with complete data, respond to the customer within a defined time, analyse the root cause, run the corrective action, and verify it worked before closing. Clause 9.1.2 requires you to monitor customer perception, and clause 10.2 requires every nonconformity, complaints included, to be handled with documented action. Below you will find the full process, the fields your complaint log needs, when a complaint formally becomes a nonconformity, and the metrics to track it. That is the part almost no customer service guide covers. Table of Contents - [What counts as a complaint under ISO 9001 (and what does not)](#What_counts_as_a_complaint_under_ISO_9001_and_what_does_not) - [The complaint management process in 5 steps](#The_complaint_management_process_in_5_steps) - [The fields your complaint log needs](#The_fields_your_complaint_log_needs) - [When a complaint becomes a nonconformity](#When_a_complaint_becomes_a_nonconformity) - [How to measure complaint management: 5 metrics](#How_to_measure_complaint_management_5_metrics) - [The mistakes that cost you an audit finding](#The_mistakes_that_cost_you_an_audit_finding) - [Turn every complaint into a documented improvement](#Turn_every_complaint_into_a_documented_improvement) - [Frequently asked questions about ISO 9001 complaint management](#Frequently_asked_questions_about_ISO_9001_complaint_management) - [Does ISO 9001 require a complaints procedure?](#Does_ISO_9001_require_a_complaints_procedure) - [What is the difference between a correction and a corrective action on a complaint?](#What_is_the_difference_between_a_correction_and_a_corrective_action_on_a_complaint) - [How quickly should you respond to a customer complaint?](#How_quickly_should_you_respond_to_a_customer_complaint) - [Do you have to log every complaint, even minor ones?](#Do_you_have_to_log_every_complaint_even_minor_ones) - [How does ISO 10002 relate to ISO 9001?](#How_does_ISO_10002_relate_to_ISO_9001) - [How do you prove in an audit that complaint management works?](#How_do_you_prove_in_an_audit_that_complaint_management_works) ## What counts as a complaint under ISO 9001 (and what does not) A complaint is any expression of dissatisfaction from a customer about your product, your service or the handling process itself, where a response is expected. The channel is irrelevant: email, phone, web form, public review, or the remark a customer made to your sales rep during a visit. Three things worth separating, because they usually get mixed up: - **Complaint:** the customer expresses dissatisfaction and expects a response. Always logged. - **Claim:** a complaint that also requests specific compensation (replacement, credit note, re-performance of the service). Logged, and usually triggers a corrective action. - **Suggestion or comment:** the customer proposes an improvement without expressing dissatisfaction. Not a complaint, but a valuable input for the management review. The distinction matters because the auditor will check your criteria, not theirs. If your procedure defines what counts as a complaint and that criterion is applied consistently, you are covered. The problem starts when the criterion only lives in the head of whoever answers the phone. ## The complaint management process in 5 steps 1. **Log it.** Every complaint enters the same log, whatever channel it came from. Date, customer, channel, description in the customer’s own words, product or service affected, and assigned owner. This is the most skipped step and the most expensive one: what is not logged does not exist in an audit, and it never shows up in your metrics either. 2. **Respond within the defined time.** Acknowledge within 24 hours and give a realistic resolution timeline. Everything you know about service applies here: let the customer finish explaining, acknowledge the problem in their own words, and do not start justifying too early. What separates this from an informal process is that the timeline is written down and can be measured. 3. **Analyse the root cause.** The symptom is “it arrived damaged”. The root cause might be the packaging, the carrier, how it was stacked, or a badly written work instruction. Five whys or a cause-and-effect diagram is enough for most cases. Skip this step and you are only firefighting, and the same complaint returns in two months. 4. **Run the correction and the corrective action.** These are two different things and the standard separates them: the _correction_ fixes this customer’s case (you replace the product); the _corrective action_ attacks the cause so it does not recur (you change the packaging, update the instruction, train the team). With an owner and a committed date. 5. **Verify and close.** After a set period, check whether the action worked: did complaints of that type go down? If yes, close with the evidence. If not, reopen. A complaint opened and closed on the same day with no verification is a red flag for any auditor. ## The fields your complaint log needs The log is the evidence. These are the minimum fields for it to work both operationally and in an audit: FieldWhat it is for**Reference number and date received**Traceability and response time calculation.**Customer and entry channel**Reveals which channels were feeding complaints you never logged.**Description in the customer’s words**Stops the problem being reinterpreted on its way into the system.**Product, service or process affected**Lets you group by origin and see patterns.**Classification and severity**Defines which complaints escalate to a formal nonconformity.**Assigned owner**With no owner, the complaint sits and waits.**Acknowledgement date and response date**The two service metrics you can actually measure.**Root cause identified**The first thing an auditor reads after the description.**Correction applied and corrective action opened**Kept separate, each with its reference number.**Effectiveness verification and closing date**Closes the loop. Without it the complaint is “attended to”, not resolved.If you are documenting the procedure and the form from scratch, the [Corrective Actions Winning Method™](https://www.qualityweb360.com/guides/corrective-actions-winning-method/) guide covers the part that gets stuck most often: how to go from a complaint to a corrective action an auditor accepts as closed. ## When a complaint becomes a nonconformity Not every complaint opens a formal corrective action, and pretending otherwise floods the system. A sensible criterion, which belongs in writing in your procedure: - **Escalate to a nonconformity** when the complaint points to an actual failure to meet a requirement (customer, legal or your own system), when the same type of complaint repeats, when the impact is high (safety, significant cost, risk of losing the account), or when it affects product or a batch already shipped. - **Handle and close without a corrective action** when it is an isolated case with no failed requirement (a misunderstanding about a date, an expectation that was never in the contract). It still gets logged, with a note explaining why it did not escalate. That “still gets logged” is the whole point. Complaints that do not escalate still count towards your metrics and towards the trend analysis you take into the [management review](https://www.qualityweb360.com/iso-9001-management-review-clause-9-3/). ## How to measure complaint management: 5 metrics - **Number of complaints per period**, segmented by product, process or customer. A rise early on is usually good news: it means they are finally being logged. - **Average acknowledgement time.** From receipt to the first response to the customer. - **Average resolution time.** From receipt to verified closure, not to “I already replied”. - **Percentage of complaints with a documented root cause.** This is the metric that separates a real process from a decorative one. - **Recurrence rate.** Same-type complaints after a corrective action was closed. If it does not fall, the root cause was wrong. Those five feed clause 9.1.2 directly, alongside your satisfaction surveys. For the measurement side in detail, here is [how to measure customer satisfaction under ISO 9001](https://www.qualityweb360.com/3-ways-to-measure-customer-satisfaction/). ## The mistakes that cost you an audit finding - **Complaints that live in someone’s inbox.** If they are not in the log, they do not exist. And auditors spot it by cross-checking with what the sales team says. - **Every complaint closed on the day it opened.** A sign that logging happens at the end, once it is already solved, instead of on arrival. - **Root cause that just restates the symptom.** “Cause: the product arrived damaged” is not a cause, it is the complaint written again. - **Corrective actions with no effectiveness check.** The field exists on the form and is empty in 90 % of records. - **Complaints that never reach the management review.** Clause 9.3 explicitly asks for customer feedback as an input. ## Turn every complaint into a documented improvement Logging the complaint, assigning it, linking it to its corrective action, tracking the times and closing with evidence is what the [QualityWeb 360 complaint management module](https://www.qualityweb360.com/complaints/) does, with the full audit trail behind it. The complaint stops being a forwarded email and becomes an input to your system. ## Frequently asked questions about ISO 9001 complaint management ### Does ISO 9001 require a complaints procedure? ISO 9001:2015 does not require a documented procedure under that name, but it does require monitoring customer perception (clause 9.1.2) and handling nonconformities with documented action (clause 10.2). In practice, demonstrating both in an audit without a complaints procedure and its log is close to impossible. ### What is the difference between a correction and a corrective action on a complaint? The correction fixes this customer’s specific case: you replace the product, redo the service, issue the credit note. The corrective action attacks the root cause so the situation does not recur: you change the packaging, fix the work instruction, adjust the process. ISO 9001 requires the second one when the complaint reveals a real failure to meet a requirement. ### How quickly should you respond to a customer complaint? The standard sets no deadline: you define it in your procedure and the auditor checks that you meet it. Common practice is acknowledging within the first 24 hours and giving a resolution timeline of 48 to 72 hours, extendable if the case requires it, always keeping the customer informed. ### Do you have to log every complaint, even minor ones? Yes. Logging all of them is what lets you see trends and catch recurrence. Whether each complaint escalates to a formal corrective action is a separate question, decided by the severity criteria you define in writing. Always log; escalate by criteria. ### How does ISO 10002 relate to ISO 9001? ISO 10002 is the dedicated complaint management standard and gives detailed guidance on the process. It is not required for ISO 9001 certification, but it works as a reference when designing your procedure. If you already meet 9.1.2 and 10.2 with a solid log, you are covering the essentials of its approach. ### How do you prove in an audit that complaint management works? Three things: the complete log for the period, a sample of complaints traced end to end (receipt, root cause, action, verification, closure) and the metrics presented in the management review. If you can pick a complaint at random and follow its full path with evidence, the process works. **Part of:** [Clause 10 of ISO 9001: Improvement](https://www.qualityweb360.com/iso-9001-clause-10-improvement/). ### Share your love ### About The Author [#### Gabriel Salles ](https://www.qualityweb360.com/author/gsalles/)Founder and CEO of QualityWeb 360. With over 15 years managing, auditing, and implementing ISO 9001 Quality Management Systems across industries, he built QualityWeb 360 so any organization can run their QMS simply — no spreadsheets, no chaos. [← Previous Post](https://www.qualityweb360.com/this-is-how-qualityweb-360-manages-quality-risks-visualization-alerts-and-total-control/ "This is how QualityWeb 360 manages quality risks: visualization, alerts and total control.") [Next Post →](https://www.qualityweb360.com/10-quality-management-software-in-english/ "10 Quality Management Software in English") ## Related Posts [ Nov 27 2020 ](https://www.qualityweb360.com/5-keys-to-implement-the-norm-iso-9001/) ### [5 Keys To Implement The Norm ISO 9001](https://www.qualityweb360.com/5-keys-to-implement-the-norm-iso-9001/) The implementation of a quality management system based on the norm ISO 9001 standard has many benefits, that’s why more \[…\] [Read More »](https://www.qualityweb360.com/5-keys-to-implement-the-norm-iso-9001/) [ Nov 28 2020 ](https://www.qualityweb360.com/impact-of-a-quality-management-system/) ### [Impact of a Quality Management System](https://www.qualityweb360.com/impact-of-a-quality-management-system/) When you are looking for a quality management system certification based on the ISO 9001 standard, the first thing you \[…\] [Read More »](https://www.qualityweb360.com/impact-of-a-quality-management-system/)