Complaints, KPIs, Customer Satisfaction: learning from nonconformities without an 8D report

14 modules · about 73 minutes · final test with 33 questions, 27 correct to pass · certificate of participation as PDF

What this course is about

Every company has complaints – the question is what it does with them. ISO 9001 requires in 8.7 the control of the nonconforming output, in 10.2 the cause analysis and corrective action with evaluation of effectiveness, in 9.1 KPIs and in 9.1.2 the evaluation of customer satisfaction.

No registration needed. We only ask for your name and e-mail address before the final test – just for your certificate. Your progress is saved in this browser. You can stop at any time and continue later.

Module 1 of 14

Why complaints are the best thing that can happen to a QMS

No sentence makes auditors more suspicious than “We had no complaints last year.” Not because it could not be true — but because it almost always means: there were some, but nobody wrote them down. The company that shows three documented complaints with cause and action gets a strength in the report; the one with “none” gets the question how it knows that.

The standard chains three clauses together that are a single flow in a small company:

The three errors of small companies — and what they cost:

1. Not recorded. The complaint is dealt with on the phone, the spare part goes out, done. Consequence: no record (8.7.2, 10.2.2), no rate, no learning. Nonconformity in the audit.
2. Cause assumed. “The apprentice did not pay attention.” Consequence: action “apprentice admonished”, the error comes back because the cause (no checklist, unclear drawing) is not removed. Nonconformity against 10.2.1 b.
3. Satisfaction felt. “Our customers are satisfied, otherwise they would not come back.” Consequence: no evaluation by method (9.1.2), no input to the management review. Nonconformity.

The way of this course: one sheet (complaint sheet with six steps), one list (defect tally sheet), five numbers (KPI sheet) and one table a year (customer satisfaction). A company of up to 50 employees needs no more paper — and with less it stands out in the audit.

📄 The six steps of the complaint with clause, deadline, document and the auditor's question (German – English version to follow)

The benefit beyond the audit: after three months a defect tally sheet shows where the money disappears — rework, credit notes, double trips. Empirical value from small companies: two to five per cent of turnover. Anyone who stops the three most frequent repeaters has paid for the certification.

Module 2 of 14

The complaint in six steps on one sheet

Six steps, one sheet, two deadlines. The complaint sheet is at the same time the nonconformity sheet for internal nonconformities and supplier nonconformities — one form for all three origins, so that the defect tally sheet becomes complete.

The sheet: one page, six blocks, at the top the number (C-2026-07), at the bottom the status (open / correction done / action running / closed). Number and status go into the defect tally sheet; the sheet into tab 7 of the order file and into the folder “Complaints year”.

📄 Complaint sheet with six steps — for customer complaints, internal nonconformities and supplier nonconformities (German – English version to follow)

Responsibility: anyone may record; the person with authority per organisation chart decides (steps 2, 3); cause and action (4, 5) MD or quality manager with those involved; effectiveness (6) quality manager. Escalation: complaint with damage above … (your threshold) or safety relevance or from a key customer → immediately to the MD. One line in the manual.

Not every complaint is a nonconformity: the customer expected something different from what was ordered (exclusion in the quotation was missing) — then the cause is in sales, not in the workshop. That is also on the sheet: step 4 answers whether the nonconformity lay with the company, and if so, where.

What auditors ask: “Show me your last complaint from receipt to completion: how long was it between the report and your reaction, what was the cause, and what did you do so that it does not happen again?” — one sheet answers all four sub-questions.

Module 3 of 14

Correction or corrective action: the difference auditors check

Two words that sound almost the same and in the audit make the difference between “passed” and “nonconformity”:

When a corrective action is appropriate — the standard says “appropriate to the effects” (10.2.1); in a small company that means when at least one applies:

• Repetition: the nonconformity is already in the defect tally sheet once (or similar).
• Damage: costs above a threshold (e.g. 500 in your currency), order lost, customer relationship strained.
• Safety, law: product safety, data protection, occupational safety affected.
• Customer demands it: key customer requires an action report.

If none applies — a one-off typo on an invoice, a parcel lost by the parcel service — then the correction is the whole answer, and the sheet says at step 5: “No corrective action — isolated case, monitoring via defect tally sheet.” That conforms to the standard and is honest. Anyone who invents a corrective action for every complaint has thirty actions after a year that nobody tracks.

What is not a corrective action: “employee admonished”, “team reminded”, “pay more attention in future”, “employee trained” without content. Those are appeals; they remove no cause. The auditor recognises them at once and asks: “And what prevents the next employee from making the same mistake?”

Typical effective corrective actions in a small company: check point or checklist added · template changed (mandatory field, exclusion text) · briefing with record on exactly this point · drawing or work instruction corrected · supplier changed or inspection level raised · deputy arranged · fixture, colour coding, scanner (against human error, 8.5.1 g) · rule in the manual.

Every corrective action gets a responsible person and a deadline and is in the action plan (source: complaint C-2026-07) — not only on the sheet. One-plan rule.

Module 4 of 14

Finding the cause: five whys in ten minutes — without a culprit

The cause analysis is the step the standard requires most clearly (10.2.1 b: “determine the causes of the nonconformity”) and that small companies skip most often — because the answer seems obvious: “The fitter stored the top wrongly.” That is the trigger, not the cause. The cause is what made the nonconformity possible — and that is almost always something in the system, not in the person.

Five whys — the example from the course “Order”:

Cause: missing rule for customer property. Corrective action: line in V1, shelf “customer property”, marking at receipt. Not: “warehouse worker admonished.”

Five rules for the ten minutes:

1. On site, with those involved — not at the desk about them. Whoever made the error usually knows the cause.
2. Without blame. The first sentence of the talk: “We are looking for what made the error possible, not for who made it.” Otherwise the truth stops at the second why.
3. Down to the system cause — a rule, a template, a check point, a qualification, a supplier. There something can be changed.
4. Not down to the theory of everything. “Why no rule? — Because the boss has too little time. — Why? — Because business is poor” — stop at the first why that yields a feasible action.
5. Write it down — the chain goes in step 4 of the complaint sheet. That is the record under 10.2.2.

The five cause fields — almost every cause in a small company lies in one of them (and that helps with the questions):

Checking similar cases (10.2.1 b 3): after the whys a look into the defect tally sheet — “Has this happened before? Can it happen elsewhere too (second location, other customer, other machine)?” One sentence on the sheet.

Ishikawa (fishbone with man, machine, material, method, environment, measurement) pays off for repeaters that have not disappeared after two rounds of five whys — then with the team at the board, 30 minutes. For the usual complaint five whys are enough.

📄 Five-whys sheet with rules, cause fields and two completed examples (German – English version to follow)

Module 5 of 14

The defect tally sheet: source of repeaters and of the cost of poor quality

The defect tally sheet is the list small companies underestimate most — and that after three months says more about the company than any customer survey. One row per nonconformity, wherever it comes from: internal nonconformities from the workshop, supplier nonconformities from goods receipt, customer complaints. All three origins in one list — otherwise nobody sees that the supplier nonconformity of May was the customer complaint of July.

Estimate costs, do not calculate them: rework hours × hourly rate, replacement material, credit note, express freight, double trip. One number in two minutes. After a year a sum stands at the bottom that explains to the MD the investment in the check point — typically two to five per cent of turnover.

Quarterly evaluation (15 minutes before the team meeting):

1. Top 3 types by number and by costs — usually not the same.
2. Repeaters: same type twice in six months → corrective action mandatory (10.2.1 b 3).
3. By origin: share supplier → supplier evaluation; share internal → inspection/qualification; share customer → complaint rate.

The three numbers go into the team meeting (awareness 7.3: “That cost us 1,200 this quarter”), into the KPI sheet (complaints, cost of poor quality) and into the management review (9.3.2 c 3: process performance and conformity; 9.3.2 c 4: nonconformities and corrective actions).

Who enters: whoever finds the nonconformity — with the number from the complaint sheet. Rule: no nonconformity sheet without a row in the list, no row without a sheet (for nonconformities below 50 the row is enough).

📄 Defect tally sheet (Excel) with origin, cause field, costs, repeater marking and quarterly evaluation (German – English version to follow)

What auditors ask: “Show me a complaint of the last three months that has repeated itself: what did you do?” — The list shows the repeater, the complaint sheet the action, the action plan the status. Without a list the company cannot recognise repeaters — and that is exactly the nonconformity.

Module 6 of 14

Evaluating effectiveness: the step everyone forgets (10.2.1 d)

Of the six steps, step 6 is the one auditors most often find as a gap: the action was implemented, marked as “done” — and nobody checked whether it worked. The standard requires it expressly (10.2.1 d: “review the effectiveness of any corrective action taken”), and it means something simple: has the nonconformity recurred since then?

When: three months after implementation — long enough for the nonconformity to have had the opportunity, short enough that nobody forgets. For rare transactions (free-issue item twice a year) at the next comparable order. The date is on the complaint sheet and in the action plan.

With what:

Three outcomes:

• Effective: nonconformity has not recurred, rule is applied → close the sheet, status in list and action plan “closed, effective (date, initials)”.
• Partly: nonconformity rarer but present → sharpen the action, new deadline.
• Not effective: nonconformity as before → the cause was wrong. Back to step 4 with new five whys — not a failure but the normal way with complex causes.

Record (10.2.2 b: “the results of any corrective action”): one sentence with date and initials on the sheet. Without this sentence the action counts in the audit as “not evaluated”.

Updating risks and system (10.2.1 e, f): if the complaint shows a risk that was not in the analysis (single supplier, knowledge drain), a row is added. If the action changes a process (new step in V1), the manual gets a new status. Two boxes on the sheet: “risk analysis updated ☐”, “manual / process changed ☐”.

The time effort: ten minutes per action, four to eight times a year. The cheapest clause of the standard — and the one with the highest hit rate in the audit.

Module 7 of 14

Five KPIs every company has — without a new count (9.1.1)

9.1.1 requires determining what is monitored and measured, by which methods, when it is measured and when evaluated — and retaining the results. Small companies rarely fail at this for lack of numbers but for too many that nobody collects. The rule: every KPI comes from data the company has anyway. Everyone has five of them:

Plus one to three sector-specific — from the process list (one KPI per process): tickets within 8 h (IT), site checks without complaint (services), availability from stock (retail), rework rate (manufacturing), acceptances without defects (construction). And cost of poor quality from the defect tally sheet as a sixth if the company estimates it.

The KPI sheet: one page, KPIs in the rows, months in the columns, target value in the first column, traffic light. Anyone who fills in the sheet monthly (15 minutes) has 9.1.1, the actual values for the objectives (6.2.1 e) and the input 9.3.2 c for the management review.

What is not a KPI: “quality”, “customer satisfaction high”, “few complaints” — without number, source, frequency. And: a KPI nobody collects. If the sheet says “rework rate” and the columns are empty, that is a nonconformity against 9.1.1 — better delete the row.

Evaluate, not only measure (9.1.1 last paragraph and 9.1.3): monthly in the team meeting one sentence per red number — why, what do we do. Minutes line. That is the analysis and evaluation the standard means; nobody needs statistics software.

📄 KPI sheet (Excel): five standard KPIs plus three free ones, monthly columns, target value, traffic light, annual average (German – English version to follow)

Guide values are empirical values from small companies — your own target value comes from the previous year plus a realistic improvement (course “Objectives, Risks, Opportunities”), not from the table.

Module 8 of 14

Customer satisfaction without a questionnaire: four sources and one table (9.1.2)

9.1.2 is the clause most often answered with “We have to do a customer survey” — and then not done, because the response rate in small companies is below ten per cent. The standard requires no survey. It requires monitoring customers' perception and determining the method; the note names surveys, feedback, meetings, market share, compliments, warranty claims. Every small company has four sources:

The rating table — once a year for the main customers, on a grade scale, three criteria from the customer's point of view (how he experienced the company): flexibility · reliability · delivery performance. Default value 2, not applicable X, action from 4, alternative from 5 (with customers: seek a talk, clarify conditions). Columns action/remark, responsible/deadline, status/result. The table summarises the four sources per customer and is the input 9.3.2 c 1 of the management review.

Evaluation period in the heading: documents January to June → whole previous year; July to December → first half of the current year (rule from the course Objectives).

When a survey makes sense after all: for maintenance and long-term contracts (services, IT) with few key customers — one talk per quarter with three questions and a note is worth more than a questionnaire to 200 addresses. Anyone doing an online survey: five questions, grade 1 to 6, free text, once a year, document the response rate.

Negative feedback = complaint: grade 4 to 6 in the talk after delivery triggers a complaint sheet, even without a formal complaint. That is the link from 9.1.2 to 10.2 — and the reason why satisfaction rises in companies with this system.

📄 Customer satisfaction (Excel): rating table on a grade scale, talk guide after delivery, annual evaluation (German – English version to follow)

What auditors ask: “How do you learn whether your customers are satisfied — and what did you specifically change after the last negative or mediocre feedback?” Table, cover sheet grades, one complaint sheet with action. Three documents.

Module 9 of 14

Complaints in six sectors: typical types, response time, correction

The flow is the same everywhere; the types, response times and corrections are not. What is typical in six sectors — as a starting point for your own defect tally sheet and the escalation rule:

Response time means: the customer knows that his complaint has arrived and what happens now — not that it is resolved. The time is a rule in the manual or in process S4 and is a KPI (response time ≤ 24 h in 100 % of cases).

Warranty and notice of defects are the legal framework: the customer gives notice, the company remedies (work) or delivers again (sale). The complaint sheet is at the same time the file for a dispute; deadlines (under commercial law a notice of defects between businesses often has to be given promptly — check the law of your country) are in the list of standards and laws.

Passing on to your own supplier: if the cause lies with the supplier (batch, transport, subcontractor), the complaint is passed on to him with evidence — origin “supplier” in the defect tally sheet, entry in the supplier evaluation. Towards the customer the company remains responsible; “that was our supplier” is no answer to the customer.

📄 Complaint types, response times, corrections and corrective actions for six sectors — with sample escalation rule (German – English version to follow)

Module 10 of 14

Continual improvement (10.1, 10.3): three sources, one plan, no suggestion scheme

Clause 10 is called “Improvement”, and 10.3 requires continually improving the suitability, adequacy and effectiveness of the QMS — from the results of analysis, evaluation and management review. No suggestion scheme, no kaizen board, no improvement quota. What is required is that the company derives improvements from its numbers and nonconformities and implements them.

Three sources a small company has anyway with this course:

Plus the management review (annually, decisions) and the internal audit (observations and strengths).

Improvement is not corrective action: the corrective action reacts to a nonconformity (10.2); the improvement makes something better that was not wrong (10.3) — faster, cheaper, more pleasant for the customer. In the action plan the column “source” distinguishes: complaint / audit / risk / objective / management review / improvement. Three to six improvements a year are realistic and sufficient for a small company.

The evidence for the auditor: action plan with source “improvement”, minutes lines of the team meeting, change register of the manual (a living system changes), management review section “opportunities for improvement” (9.3.3 a). The question “What did you improve last year that was not triggered by a nonconformity?” should be answerable with two examples.

What is not required: a company suggestion scheme with bonuses, CIP workshops, improvement targets in per cent. Anyone who wants that may do it — the standard only requires that improvement takes place and is visible.

The smallest effective mechanism: in every team meeting a fixed item “What do we do better?” — five minutes, one idea, one responsible person, one row in the action plan. After a year twelve rows are there, half of them implemented. That is continual improvement in a small company.

Module 11 of 14

What the auditor asks about complaints, KPIs and satisfaction

Auditors check clause 10 with one sentence: “Show me your last complaint from receipt to completion.” And then they follow the chain — not the manual:

Typical questions (from real audits, anonymised):

• “Show me the last customer complaint: how long was it between dispatch, receipt of the complaint and your reaction, and what did you tell the customer?”
• “Let's take a complaint that repeated itself: what did you do, and how do you see that it worked?”
• “Let's take your last complaint that was escalated beyond the case handler: who decided when?”
• “Let's take your last order that was delivered late: what was the cause, and what did you change?”
• “How do you learn whether your customers are satisfied, and what did you change after the last mediocre feedback?”
• “Which KPIs do you keep, who looks at them when, and what happened last time one was below target?”

The five most frequent nonconformities: complaints not recorded (8.7.2, 10.2.2) · cause not determined or only blame (10.2.1 b) · effectiveness not evaluated (10.2.1 d) · customer satisfaction not evaluated by a determined method (9.1.2) · KPIs determined but not collected (9.1.1).

📄 Twenty-five audit questions on complaints, KPIs and customer satisfaction with evidence (German – English version to follow)

Answer in five minutes: complaints folder of the year, defect tally sheet, KPI sheet, customer satisfaction rating table, action plan. Five documents, one chain.

Module 12 of 14

Case study: Nordlicht IT Service — three complaints, one KPI sheet

Nordlicht IT Service (fictitious) in Flensburg, Germany, looks after about 60 small companies with nine employees — network, servers, workstations, hotline, maintenance contracts. In the third quarter of 2026 there were four complaints. The first — C-2026-04, the cloud disruption of 14 July — is already recorded (processed in the course “Procedures and Work Instructions”); the three in September management “dealt with” — nobody wrote them down. You catch up on that.

Complaint 1 — disruption after update: customer (tax practice, 12 workstations) reports on Monday 8:10 that after the weekend update the practice software does not start. Technician on site at 9:30, rollback by 11:00. The technician had installed the update on Friday without a test because the test environment “was not running just then”. In the defect tally sheet there is a similar case from May (other customer, same software).

Complaint 2 — hotline not reachable: customer (trade business) calls three times on Thursday, hotline busy, no call back; on Friday he complains to the managing director. The hotline employee was ill, the deputy (team 1) on a project. First case of this kind in the year.

Complaint 3 — data loss after migration: after the server migration of a customer (medical practice), documents of one week are missing. Cause: the data backup before the migration was incomplete (one drive not in the backup job), the project checklist was not fully ticked off. Restore from the customer's backup, two days of work. Customer annoyed, customer property (8.5.3) affected, personal data.

Your task (90 minutes):

1. Per complaint one complaint sheet with all six steps — response time, correction with re-verification, five whys, decision corrective action yes/no with reasoning, effectiveness check (when, with what).
2. Defect tally sheet with the three cases plus the May case (the July disruption N-2026-09 is already in it); mark repeaters; estimate costs.
3. KPI sheet for Nordlicht: five standard KPIs plus two sector-specific with source and frequency; actual values Q3 from the data in the download.
4. Customer satisfaction: rating table for the five main customers (data in the download).

📄 Nordlicht: the three complaints with all data, defect tally sheet May, KPI raw data Q3, five main customers (German – English version to follow)

📄 Nordlicht: model solution — three complaint sheets, defect tally sheet, KPI sheet, customer satisfaction (German – English version to follow)

Where most deviate: complaint 2 needs no corrective action under 10.2 — but the cause (deputy) is already objective O2 in the manual: reference instead of new action · complaint 1 is a repeater (May) — corrective action mandatory, and the cause is not “technician did not test” but “change approval without test is possible” · complaint 3 additionally triggers the report under 8.5.3 and the data protection check (reporting deadline under the law of your country, in the EU 72 hours) — two more boxes on the sheet.

Time balance Nordlicht: three sheets 90 minutes (retrospectively; routinely 20 minutes each), defect tally sheet 15 minutes, KPI sheet 30 minutes, customer satisfaction 20 minutes. In the surveillance audit clause 10 was checked on complaint 1 in twelve minutes — with the strength “repeater recognised, system cause removed”.

Module 13 of 14

Records: the complaints folder, the list, the sheet — and what goes into the management review

Five documents — and a fixed date for each:

The annual calendar: monthly KPI sheet and action status in the team meeting (minutes line). Quarterly evaluate the defect tally sheet (top 3, repeaters, costs). December: evaluate customer satisfaction, annual sum of cost of poor quality, everything into the management review. Total: under 20 hours a year for clauses 8.7, 9.1 and 10 — for a company with 20 complaints.

Retention: complaint sheets 10 years (product liability, warranty); defect tally sheet and KPI sheets 10 years (trend across certification cycles); customer satisfaction 10 years.

📄 Checklist: complaint handling, defect tally sheet, KPIs and customer satisfaction in 15 criteria (German – English version to follow)

Below 18 of 30 points: implement modules 2 to 8 in your own company, rate again after three months. From 24: clause 10 audit-proof.

What follows: the management review — the course “Management Review and Year End” shows how KPIs, customer satisfaction, defect tally sheet and action plan become the annual report in two hours, from which the objectives of the next year come.

Module 14 of 14

Procedure in our company

Your company completes this module. The general part of the training ends here; what follows, only your company knows:

Companies with a company account of the Academy receive this module with their own details; participants then see the names, dates and filing locations of their company. Without customisation: ask your management or your quality manager where these details are laid down in your company — usually in the quality manual.

Final test

33 questions, one correct answer each. You need 27 correct answers to pass (80 %). Scoring happens on the server — there is no answer key on this page.

Your result