Quality complaint process flowchart template
A quality complaint process flowchart across five lanes: logging and acknowledgement, safety and reportability checks, investigation, remedy, CAPA and closure.
How it works
Rename the lanes to your organisation
Replace the five role lanes with the functions that actually exist for you. Small manufacturers often merge Quality and Technical investigation into one lab lane; regulated sites usually keep Regulatory separate because the reporting decision is not Quality's to make.
Set the acknowledgement and closure targets
Put your real timings on the receipt and closure steps, for example acknowledge within one working day and close within thirty calendar days. If the target differs by criticality grade, say so in the label or in the note on the assessment step.
Define the criticality grades and the safety trigger
Decide what counts as critical, major and minor, and write down exactly what makes a complaint a potential safety risk. The "Potential safety risk?" decision is only as good as that definition, and it is the box people argue about after the fact.
Confirm the reportability rule with your regulatory lead
Name the regulation, the deadline and the person authorised to decide on the "Reportable to the authority?" branch. Record the decision not to report with its rationale, not just the reports you file - the negative decision is what gets questioned in an inspection.
Agree when a complaint raises a CAPA
Set the threshold for the "Systemic or recurring issue?" decision: a repeat on the same batch, a trend across a line or supplier, or any safety-related confirmation. A one-off with a clear cause and effective containment can close on correction alone.
Publish the map alongside the procedure
Keep the diagram under the same version control as the written procedure, so the approved version and the picture on the wall do not drift apart. Review it whenever the trending data shows the flow is being worked around.
Frequently asked questions
What is the difference between a quality complaint and a customer service complaint?
A quality complaint alleges a defect in the product: contamination, damage, wrong specification, a failure in use. A service complaint concerns how the organisation behaved - a late delivery, a billing error, poor communication. The distinction matters because a quality complaint pulls in physical evidence, batch traceability, a technical investigation and possibly a report to a regulator, while a service complaint is resolved by the service function. That is why the template puts a triage decision immediately after logging: everything that is not a product defect leaves for the service complaint process before it reaches the quality register.
Who should own the quality complaint process?
Split ownership by activity, not by department politics. Customer service normally owns intake, acknowledgement and all communication with the customer, because that relationship already exists. Quality owns the record itself, the criticality grading, the investigation decisions, the remedy and closure. Regulatory owns the reportability decision. The common failure is letting the function that answers the customer also decide whether the complaint is confirmed - the answer then gets shaped by what is commercially easiest to say.
When does a quality complaint become reportable to an authority?
That depends entirely on your sector and jurisdiction - medical device vigilance, pharmaceutical quality defects, food safety and consumer product safety all have their own criteria and deadlines. The general shape is consistent: a complaint that indicates a potential risk of harm, or a defect that affects product already released, triggers an assessment against the reporting criteria, and the deadline usually runs from the date the organisation first became aware rather than the date the investigation concludes. Agree the criteria with your regulatory lead in advance and record both outcomes, including the decision not to report.
Does every confirmed complaint need a CAPA?
No, and raising one every time is a reliable way to build a backlog nobody works. A single confirmed defect with a known cause and effective containment can be closed on the correction alone. Raise a CAPA where the cause is systemic: repeats on the same batch, line or supplier, a trend visible in the complaint data, or anything with a safety dimension. Close the CAPA on evidence that it worked, not on the action being marked done - which is what the effectiveness check in the closure lane is for.