A finding isn't done when it's written down — it's done when it's fixed and verified. Each non-compliant answer becomes a finding with a clause, an NC grade and a fresh-vs-repetitive flag, then works through an append-only closure history signed off by the auditee, the system co-ordinator and the auditor before the audit can close.
A finding is born during checklist entry — everything after is closure. Corrective action is tracked as an append-only history, verified by three roles, before the audit can move to closed.
An NC scribbled as "issue at store" helps nobody. Here every non-compliant answer becomes a finding that carries the clause it failed, the discrepancy or observation the auditor recorded, the NC category that grades it, and a fresh-vs-repetitive flag — attributed to both the auditee responsible and the auditor who raised it. Nothing is re-typed from the checklist; the finding is the same record the auditor answered.
Corrective action is tracked as an append-only history per finding. Every entry records a status, who updated it, when, a due date, a remark and the auditee's remark — and nothing is overwritten, only added. So the story of how a non-conformance was closed reads back in order: what was proposed, what was done, what was checked, and by whom. That is the audit-ready evidence a certification body actually asks to see.
An NC that the auditee marks "done" and no one checks is how repeat findings are born. Here closure is a three-role sign-off: the auditee proposes and implements, the system co-ordinator verifies it is complete, and the auditor verifies it is effective. Each role advances its own status independently, and reminder emails chase whichever role is overdue — so nothing sits open quietly until the next audit finds it again.
When every finding is actioned and verified, audit closure moves the audit from released to checked, then closed, and issues the NC summary register — audit number, date and type, clause, discrepancy, fresh/repetitive, auditee, auditor and per-role closure status, with prepared-by and approved-by. And when a major NC needs deeper problem-solving, it escalates to Fast Quality's 8D / CAPA when that module is licensed — same document engine, no re-keying.
Each non-compliant answer becomes a finding automatically, carrying its clause, discrepancy, NC category and auditee/auditor attribution.
The NC category grades every finding by severity, so a systemic breakdown is treated differently from an isolated lapse.
Every finding is flagged fresh or repetitive, so NCs that earlier fixes failed to kill become visible instead of anecdotal.
A closure trail per finding that is only ever added to — status, updater, date, due date and remarks retained, never overwritten.
Auditee, system co-ordinator and auditor each verify in turn, so no finding closes on a single person's word.
Reminder emails chase overdue closures, and audit closure issues the NC summary and emails the report to the plant quality head.
Most audit systems store a resolution note. A note is not a verified closure, and it prevents nothing. Here is the difference — and for the wider picture, read what is audit management software?
A finding is a checklist answer whose conformance verdict is not complied. It is created automatically during checklist entry and carries the clause number, the discrepancy or observation, the NC category that grades it, and a fresh-vs-repetitive flag, attributed to both the auditee and the auditor. Every finding becomes a line in the NC summary register and the anchor for its own corrective-action history.
Each finding carries an NC category, and that category grades the non-conformance as major or minor. A minor NC is an isolated lapse against a requirement; a major NC is a systemic breakdown or a repeated minor. The grade, together with the fresh-vs-repetitive flag, decides how urgently the corrective action is chased and whether the finding is a candidate to escalate to a formal 8D / CAPA.
Corrective and preventive action is tracked as an append-only history per finding. Each entry records a status, who updated it, when, a due date, a remark and the auditee's remark — so the closure trail is never overwritten, only added to. The auditee submits the action plan and evidence, the system co-ordinator and the auditor verify, and the finding advances through role-wise statuses until it is released and closed.
Closure is a multi-role sign-off. The same finding shows an auditee status, a system co-ordinator status and an auditor status, each advancing independently. The auditee proposes and implements the fix, the co-ordinator checks it is complete, and the auditor verifies effectiveness before the finding closes. Reminder emails chase whichever role is overdue, and audit closure issues the NC summary.
Yes. When Fast Quality is licensed, a major NC is the natural entry point to a formal 8D / CAPA / NCR document — both sit on the same document and status engine, so the finding escalates without re-keying. In a standalone Fast Audit deployment the finding still closes inside the audit module's own NC-closure history, so the escalation is an upsell, not a dependency.
Live demo of the findings-to-CAPA path — grading, append-only history, multi-role sign-off and the NC summary — on an NC like yours. Cloud or on-premise, no generic slideshow.
