ISO 9001 complaint handling in India — clauses 8.2.1, 9.1.2 & 10.2 in practice

Why complaint handling is where audits get real

Every ISO 9001:2015 surveillance and recertification audit in India eventually arrives at the same moment. The auditor sets aside the manual and the policy statements and says some version of: show me a recent customer complaint, and walk me through everything that happened after it. This is where a quality system proves it is real or reveals that it is paperwork. An organisation with a controlled complaint process answers in minutes. An organisation running complaints through WhatsApp and a shared inbox spends the afternoon reconstructing a story — and the auditor notices.

Complaint handling matters to ISO 9001 because a complaint is the customer doing your quality monitoring for you, unprompted and unflattering. The standard therefore weaves complaints through several clauses rather than parking them in one. Understanding which clause asks for what — and what a NABCB-accredited certification body auditor expects to see against each — is the difference between a clean audit and a nonconformity raised on your own nonconformity process.

The four clauses that govern complaints

Complaints are not confined to a single requirement. Four clauses of ISO 9001:2015 apply, and a strong process satisfies all of them from one record.

Clause 8.2.1 — customer communication

Clause 8.2.1 requires the organisation to communicate with customers, and it names handling enquiries, contracts, orders and their amendments, obtaining customer feedback including customer complaints, and managing customer property. In plain terms: complaints are a defined communication channel you must operate, not accidents you happen to receive. An auditor reads this as a requirement that customers have a known way to raise a complaint and that you have a defined way to receive and acknowledge it. A named intake channel — a phone line that auto-logs, an email box, a WhatsApp number, a portal — with every complaint captured as a dated record is the evidence. The failure mode this clause catches is the complaint that reached a salesperson's personal phone and was never logged anywhere the organisation can see.

Clause 9.1.2 — customer satisfaction

Clause 9.1.2 requires you to monitor customers' perception of the degree to which their needs and expectations have been fulfilled, and it lists complaints among the ways to do so, alongside surveys, praise, warranty claims and dealer reports. This clause is why closing a complaint is not the end of the obligation. You must also gather how the customer feels about the outcome and use it. In practice that means capturing post-resolution feedback and tracking it over time — a Customer Satisfaction Index that trends, and that can be sliced by customer so a quietly slipping key account is visible before it defects. An auditor will look for evidence that complaint data actually feeds a satisfaction review, not that it sits in a folder.

Clause 10.2 — nonconformity and corrective action

This is the heart of the matter, and the clause most complaint processes fail. Clause 10.2 says that when a nonconformity occurs, including any arising from complaints, the organisation shall react to it and take action to control and correct it; evaluate the need for action to eliminate the causes so it does not recur; implement any action needed; review the effectiveness of the corrective action taken; and retain documented information as evidence of the nonconformity, the actions taken, and the results.

Read that carefully, because it is a sequence with teeth. "React and correct" is the immediate fix. "Evaluate the need to eliminate the cause" is root-cause analysis. "Implement action" is the corrective action. "Review effectiveness" means you must come back and prove the fix worked. And "retain documented information" means all of it must be recorded and kept. The common Indian audit finding is a corrective-action register where every entry says "counselled the operator" or "replaced the part" with no root cause, no effectiveness check, and no evidence — corrective action theatre. A genuine 8D and CAPA path, with fishbone analysis and a verified, reviewed fix, is what satisfies this clause and closes it for good.

What Indian auditors ask to see

Certification in India is granted by bodies accredited by the NABCB (National Accreditation Board for Certification Bodies), and their auditors converge on the same evidence trail. When they pick a complaint, they follow it end to end:

Two things impress auditors beyond the individual record: retention (you can retrieve last year's complaints as easily as this month's) and analysis (you can show a Pareto of complaints by category and product driving your improvement plan). Both are trivial with a system and painful with paper. The related discipline of ISO 10002, the guideline standard specifically for complaints handling, points the same way — a defined, resourced, visible complaints process feeding continual improvement.

IATF 16949 — the stricter automotive bar

Auto-component suppliers certified to IATF 16949 live under a tougher regime built on top of ISO 9001. Two additions matter for complaints. Clause 10.2.3 (problem solving) requires a defined process for problem solving — which in the automotive world means a formal method, almost always 8D — with containment, root cause and error-proofing. Clause 10.2.5 (warranty management) requires a warranty-management process and analysis of warranty parts. On top of the standard, the OEMs impose their own customer-specific requirements: rapid containment (often within 24 hours), a full 8D within a set deadline, updates to the PFMEA and control plan, and read-across of the fix to similar parts. For these suppliers a complaint is not a ticket to close — it is a formal investigation with a customer scorecard attached. That reality is covered in depth in the guide to 8D reports for Indian auto suppliers.

How Fast Complaint Software builds the evidence

Fast Complaint Software, built by Improsys in Pune, is designed so the ISO 9001 evidence trail is a by-product of doing the work, not a separate documentation exercise. Every complaint is a numbered ticket raised against the customer with category, priority, owner and dated actions — satisfying the capture and communication expectations of clause 8.2.1. Genuine defects escalate into a structured 8D/CAPA investigation — fishbone diagrams, a Problem Solving Report, cause categorisation, a Past Trouble Database of proven countermeasures and Horizontal Deployment — giving clause 10.2 real root cause and preventive spread instead of a free-text note. Closure is gated by a controlled Release Complaint supervisor verification, so handlers cannot self-close and the effectiveness review has an owner. And post-resolution feedback rolls into a Customer Satisfaction Index, feeding the customer-satisfaction monitoring of clause 9.1.2. Because every ticket is a first-class document, it inherits a full audit trail automatically — which is exactly the "retained documented information" the standard demands.

To go deeper, read the pillar guide to complaint management for the full lifecycle, and see the 8D root cause and CAPA feature for how the corrective-action engine works. When you are ready, book a demo and bring a real complaint to walk through.

Frequently asked questions