ISO 9001 Customer Satisfaction and Feedback Procedure Template and Guide

Your satisfaction score probably looks fine. The question worth asking is what it is a score of.

Clause 9.1.2 asks for the customer's perception of the degree to which their needs and expectations have been fulfilled. Fulfillment is relative to something, and the standard does not say what. Most organizations never decide. The survey asks about the last delivery, the score comes back high, and nobody has established what the customer was promised in the first place — so the number moves for reasons the organization cannot name.

The second half is who answered. A score built from a low response rate describes the people who replied, and the people most likely to reply are the ones with either a relationship or a grievance. The quiet middle is missing, and the quiet middle is where accounts are lost without a complaint ever being filed.

This procedure requires the comparison basis and the response population to be stated before a method is chosen. It treats the operational data you already hold — warranty claims, returns, on-time delivery, compliments — as evidence of perception rather than as a substitute for asking. And it handles complaints, comments, compliments and survey responses through one process, because a customer does not categorize before speaking.

What is actually in the document

• Complete Clause 9.1.2 and 9.1.3 procedure — 32 pages, editable Word
• Channel-enumerated trigger — ten routes feedback arrives by, including the remark made to a driver that never enters the system
• Section 5.1, the comparison basis — four questions that decide what every number this process produces actually means
• Section 5.2 methods table — eight methods with what each is good at and what each hides, mapped to the Clause 9.1.2 NOTE
• Section 5.3 population and response — a stated response-rate floor and what happens below it
• Nine stated thresholds with owners — acknowledgment, resolution, closure, escalation, repeat-complaint and score-movement criteria
• Records table with no blanks — nine records, each with creator, location, retention and clause
• Process interaction map — every process this one receives from and delivers to, shipped as an editable SVG as well as inside the document
• Seven key performance indicators, each with a target, a method, an owner and a reporting route
• Maturity ladder — eight elements, four levels each, described as observable behavior and scoreable as a self-assessment
• Full clause cross-reference — twelve requirements mapped to where each is addressed
• Appendix A — feedback and complaint record, built so four fields gate closure
• Appendix B — feedback and complaint log, with the channel column the analysis needs
• Appendix C — desk-level work instruction plus two worked examples
• Appendix D — determination worksheet, the record that Clause 9.1.2 determination happened

Who it is for

Quality managers, operations leaders, and consultants at ISO 9001 certified or certifying organizations. Particularly useful where complaints sit with one function and surveys with another, where an inherited survey has never been revisited, or where satisfaction reporting has become a number nobody can interrogate.

What it changes

Stop rewriting from a blank page. The hard decisions — comparison basis, escalation criteria, response-rate floors, retention — are already made and explained. Change what does not fit.

Find out what your score is a score of. Section 5.1 forces the comparison basis into writing and into the document control block, where changing it becomes a recorded decision rather than a quiet edit to a survey question.

Use the data you already hold. Warranty claims, returns, on-time performance and compliments are named in the Clause 9.1.2 NOTE and sit unused in finance, service and sales at most organizations.

Make the record the gate, not the paperwork. A complaint record cannot close until the cause code is confirmed, the customer has been told the outcome, and either a corrective action reference or a stated reason none was needed is present.

Catch the complaint that never gets filed. Section 2.3 enumerates the informal routes and Section 12.0 sets the two-minute logging competence that makes them real.

Specification

About MSI. Management Systems International has spent 28 years helping organizations build management systems that work in practice rather than only on paper. We have supported 80+ certifications, attended 200+ audits alongside our clients, and trained 600+ professionals across manufacturing, technology, medical device, government, healthcare, and other regulated industries. MSI is veteran-owned and female-owned, founded in 1998.

Perennia Corp and Perennia Healthcare are fictional organizations used for illustration throughout the templates, and are not connected with any real organization of the same or a similar name. This is a template and guide, not certification or legal advice.

© 2026 Management Systems International, LLC · All rights reserved. · msi-international.com · 760-434-9141