The Repeat Complaint: trace a recurring quality issue before the auditor arrives
A closed CAPA, the same complaint back again, and an audit on Monday. Answer the auditor's four questions the usual way, then with connected evidence.
One complaint, one week. Your plant has hundreds.
In Uncountable's QMS, complaints, CAPAs, SOP changes, training and supplier actions can link to the batches, lots and tests behind them, so a repeat issue starts from evidence.
How the game works
You run quality at a specialty coatings plant. Three months ago, a CAPA closed on blistering epoxy primer. This morning the same complaint came back, and the auditor arrives on Monday. You play the same week twice.
Round 1: the usual week
The evidence sits in an inbox, spreadsheets, ERP, a shared drive, an email thread and a lab system. Each record costs working time on an 8 am to 6 pm clock.
You can retrain the night shift and close the complaint early. The auditor will still ask all four questions.
Round 2: the connected week
The same records, linked from the complaint in a quality management system (QMS). Bodie, Uncountable's AI agent, suggests values for selected CAPA fields from the attached supplier report. A person checks each value before adding it to the CAPA. Bodie also compares past complaints to surface possible correlations.
The results compare both weeks and show the same record from four views: executive, quality manager, operator and auditor.
The four stall points
The ID mismatch: one batch, a different ID in each system. The version question: the current SOP is easy to find; the one effective on the day isn't.
The missing link: training isn't tied to the SOP version it covers. The dropped follow-up: a supplier action agreed in a CAPA never reaches the record that tracks it.
What the game does not show
This is a simplified, illustrative scenario, not a customer story. Times are set by the game, not measured, and real investigations vary. Round 2 shows a configured workflow, and Bodie's suggestions are fixed examples rather than live output.
Worked example: why it came back
CAPA-0189 blamed the mixing step and revised SOP-112. But batch 7731 was made under version 3, six days before version 4 took effect, by a night-shift operator who was never retrained. The resin supplier accepted a corrective action request that nobody verified, and all five similar complaints used resin lots from one supplier site with moisture near the upper limit.
- The usual week: answering all four questions takes until Friday lunchtime, about 33 working hours, including a two-day wait on the supplier and a full day matching past complaints by hand.
- The connected week: following links from the complaint answers all four by mid-morning on Tuesday.
Same complaint, same people, same week. The connected record changed where the investigation started.
From the game to Uncountable
- Complaints and CAPA: link a complaint to its batch and lots, with root cause, actions and effectiveness check on one record.
- Document control and training: see which SOP version was effective on a date and, in a configured workflow, who is certified on it.
- Supplier qualification: in this configured workflow, link the supplier lot to its CoA and qualification, and track the supplier action with status and due date.
- Platform context and Bodie: open the batch, raw-material and test data behind a complaint. Bodie suggests CAPA field values and possible correlations, and your team checks each one.
See how it works on the QMS page.
Disclaimer
The Repeat Complaint is a free teaching tool built on a simplified, illustrative scenario. Results are illustrations, not measurements or quality, regulatory or professional advice, so do not use them to run a real investigation.
We have taken care over the model, but the tool is provided as is. To the extent the law allows, Uncountable gives no warranty that the results are accurate, complete or suitable for any purpose, and accepts no liability for any loss that results from using them.
