The audit trail
that builds
itself.
Quality management and analytics on one system, where every record knows what it is attached to and why. Running in production today. Public release next.
Quality data you can
actually ask a question.
-- which root causes keep coming back? select rc.label, count(*) as capas, sum(case when nc.recurred then 1 else 0 end) as recurred from capa c join root_cause rc on rc.id = c.root_cause_id join nonconformance nc on nc.id = c.addresses_id group by rc.label order by recurred desc;
| Root cause | CAPAs | Recurred | Rate |
|---|---|---|---|
| Operator handover | 11 | 6 | 55% |
| Supplier lot variation | 9 | 2 | 22% |
| Calibration drift | 7 | 1 | 14% |
| Fixture wear | 14 | 1 | 7% |
In this sample, six of eleven handover CAPAs came back. A folder of documents can't tell you that. It takes a stored link between each corrective action and the nonconformance it addressed. Ask it in SQL, Python or R, on your own records.
Every record knows
what it is attached to.
Most systems store the records and lose the relationships between them. The relationship is the evidence, so Kanso stores it as a named link: a CAPA addresses a nonconformance instead of sitting near it in a folder.
That is what lets you query the chain, keep it when people change jobs, and pull it up when an auditor asks, instead of rebuilding it from email the week before.