ISO 10002 provides guidance on complaints handling within organisations. It can help teams develop a coherent process for receiving, assessing, responding to and learning from complaints. The guidance complements QMS activities but does not mean that every suggested implementation detail is automatically an ISO 9001 requirement.
The Quality Management Standards Explained: ISO 9001, ISO 9004 and Related Frameworks places this topic in its wider QMS context. The public record identifies ISO 10002:2018. Determine actual contractual and other obligations separately, including any applicable complaint response conditions.
Define the decision and its boundary
Complaints handling concerns the customer’s expressed issue and the organisation’s response. A workable process makes intake, assessment, communication and decision ownership clear. It also allows the organisation to learn from recurring mechanisms. Keep the immediate customer remedy distinct from a later corrective action, because resolving one case may not address the cause of similar failures.
Make reporting accessible without promising outcomes the organisation cannot authorise. Staff receiving a complaint need to know what they can resolve and when to escalate. Preserve the customer account accurately while verifying relevant facts. Use proportionate access controls for personal or commercially sensitive information. Improvement should make the process more dependable for customers and staff, rather than focus only on reducing the number of recorded complaints.
Put the method into practice
Design intake around the channels customers actually use. Staff should know how to identify a complaint, preserve its meaning and route it to an authorised owner. Avoid forcing customers to repeat information merely because several teams share the issue. Where facts are disputed, investigate them while maintaining appropriate communication and making the next decision responsibility clear.
-
Define accessible intake and responsible assessment routes.
-
Communicate and resolve cases through authorised decisions.
-
Analyse patterns and evaluate the complaints process itself.
Worked example
A fictional distributor receives complaints through sales, email and a web form. Different routes produce inconsistent tracking and customers repeat the same account to several teams.
The distributor introduces a common case reference and clear ownership. Later review examines response reliability, unresolved cases and customer experience across channels.
The distributor’s common reference improves continuity across channels, but the reference alone is not the result. Check whether the customer receives a coherent response and whether unresolved matters reach someone able to decide. A case can be administratively closed while the customer remains confused or a recurring cause remains unaddressed. The review should distinguish those conditions.
Useful evidence and records
Retain the issue, relevant facts, assessment, authorised response and communication history proportionately. Sensitive information should remain appropriately controlled. Link a complaint to related investigations without assuming they all share one cause. If a decision changes after new evidence appears, preserve enough history to understand the sequence rather than silently rewrite the original conclusion.
| Comparison element | Distinct purpose |
|---|---|
| Intake | Issue, channel and acknowledgement |
| Assessment | Facts, consequence and responsibility |
| Response | Authorised decision and communication |
| Learning | Patterns and process effectiveness |
Check the result and avoid a common mistake
Closing a complaint record does not prove that the customer understood the response or that a recurring mechanism was addressed. Keep those questions distinct.
Trace complaints through different channels and inspect unresolved or reopened cases. Compare the recorded conclusion with communication and any linked corrective action.
Analyse access and reporting changes before interpreting complaint counts. A simpler channel can reveal previously unreported dissatisfaction. Fewer recorded cases can reflect improved service, reduced business or barriers to reporting. Combine counts with context, consequence and case review. Do not reward a reduction that results from reclassification or discouraging customers from raising a legitimate concern.
Connect the next decision
Use complaints information in broader review and improvement without treating every complaint as proof of an identical system failure. Investigate the relevant requirement and mechanism. Confirm response conditions through applicable obligations and commitments, not an invented global deadline. Evaluate the complaints process itself by examining reliability, clarity and learning as well as how quickly a status changes to closed.
For a related comparison, see ISO 10004 Customer Satisfaction Monitoring Explained. The related guide to complaint trend analysis explains the wider process dependency.
Practical question
Does ISO 10002 prescribe one universal response deadline? Do not infer a single deadline from a general guide. Applicable obligations and commitments may set specific conditions. Establish suitable local targets, monitor actual performance and explain exceptions while checking the requirements relevant to the organisation and complaint type.
Provide a route for cases that cross departments or cannot be resolved at the first contact. The customer should not have to understand the organisation’s internal structure to obtain a coherent response. Assign coordination responsibility and keep the next communication clear. Review whether escalation works for difficult cases rather than test only straightforward complaints that one employee can resolve immediately.