What this template is — and who it is for
If you make or service a physical product, complaints are not just messages to reply to. A part fails in the field, a customer sends back a rejected batch, a warranty claim lands — and each one needs a real fix, not just an apology. This free complaint register is the simplest place to start: one row per complaint, with the columns that push it all the way from “logged” to “fixed and verified”.
It is built for manufacturing and quality teams — quality engineers, plant heads, service managers and owner-operators of small and mid-size factories. The whole flow it supports is complaint → root cause → corrective action (CAPA), verified before close. It is deliberately not a B2C support helpdesk sheet: if you handle thousands of consumer chat tickets a day, a ticketing tool suits you better. This register is for the smaller number of complaints that must end in a permanent fix and leave an audit trail.
Complaint Register + CAPA Tracker (.xlsx)
12 ready-made columns, a bold frozen header, Severity and Status dropdowns and one worked sample row. Opens in Excel, Google Sheets or LibreOffice Calc.
Download free Excel templateCAPA and 8D, in plain words
The template uses two terms that sound like jargon but are simple once unpacked.
CAPA stands for Corrective and Preventive Action. Corrective means fixing the root cause of a problem so that exact complaint does not come back. Preventive means spreading that fix so the same mistake never shows up on a similar part or line either. A complaint register without a CAPA column just records that something went wrong; with one, it records how you made sure it stays fixed.
8D is the eight-disciplines problem-solving report that big customers — especially in automotive and engineering — expect when something fails. In plain steps it means: form a team, describe the problem, contain it, find the root cause, choose and apply the corrective action, verify it worked, prevent it recurring, and close. A one-line register cannot hold a full 8D, but this template captures its backbone — the complaint, the confirmed root cause, the corrective action, the owner, and the verification — so you are already thinking the 8D way. When you need the full method, the best CAPA software in India guide walks through it.
The 12 columns, explained
Every column earns its place. Here is what each one is for, so your whole team fills the sheet the same way.
| Column | What goes in it |
|---|---|
| Complaint No | A unique reference for the complaint, e.g. CMP-2026-001. Give every complaint one so nothing is confused or lost. |
| Date | The date the complaint was received — the clock that ageing and response time are measured against. |
| Customer | The customer or party who raised it. Later this lets you see which accounts complain most. |
| Product/Part | The exact product, part number or order the complaint is about — the key to spotting a repeat-offender item. |
| Complaint Description | What actually happened, in the customer's words plus what you observed. Be specific: “oil leak from shaft seal within 3 weeks” beats “faulty”. |
| Severity | How serious it is — Low, Medium, High or Critical (a dropdown in the sheet). Drives what you tackle first. |
| Root Cause | The real underlying reason, confirmed by investigation or a fishbone — not the symptom. Fill this only once you actually know it. |
| Corrective Action (CAPA) | The fix at the root cause, plus the preventive spread to similar parts or lines. This is the heart of the register. |
| Responsible | The single named owner of the corrective action. Actions without one owner do not get done. |
| Target Date | The date the corrective action is due. What you check overdue items against. |
| Status | Where it stands — Open, In Progress, Root Cause Done, CAPA Implemented, Verified or Closed (a dropdown). |
| Verified By | The name of whoever confirmed the fix worked. Leave it blank until someone other than the handler signs off — that is verify-before-close. |
The header row is bold, coloured and frozen, so it stays on screen as you scroll down a long list. The one sample row is clearly marked “SAMPLE” — delete it or type over it once you have the idea.
How to use it — five steps
Open the file in Excel, Google Sheets or LibreOffice Calc. Nothing to install and no macros to enable.
Fill Complaint No, Date, Customer, Product/Part and Complaint Description as soon as it arrives, then set Severity from the dropdown.
Investigate before you write in the Root Cause column. Ask “why” until you reach the underlying reason, not the first symptom.
Write the corrective and preventive action, name a single Responsible owner and set a Target Date so it cannot drift.
Move Status along as work progresses. Only mark it Closed after someone confirms the fix held and enters their name in Verified By.
Where a spreadsheet quietly starts to fail
This template is genuinely useful, and for a handful of complaints a month it may be all you need. But every growing team hits the same walls with a shared sheet:
Want this automatic instead of a spreadsheet?
If you want complaints to auto-escalate into a full 8D / CAPA, remind owners before a target date is missed, and require a supervisor to verify before a complaint can close — that is exactly what Fast Complaint Software does. Same columns you see here, but live: numbered tickets, fishbone root cause, horizontal deployment across sister lines, and a dated verification trail an auditor will accept.
It runs standalone or alongside the rest of the Fast Suite, cloud or on-premise, with on-site support in India. No pressure — keep the spreadsheet as long as it works for you. When it stops, we are here.