Why an audit programme needs KPIs
An internal-audit programme produces two things: assurance and evidence. But neither is visible unless the programme is measured. A quality manager who cannot say, on any given day, how many audits are due this month, how many were actually conducted, how many non-conformances are open and how many are overdue is not running a programme — they are hoping one is running itself. Audit KPIs turn that hope into a number, and an audit status report turns the number into something a plant head or a certification body can read.
The distinction that matters is between activity and closure. Counting how many audits you ran is activity; it feels like progress but proves nothing. Counting how many findings were driven to verified closure, and how quickly, is the measure that a registrar and a customer actually care about. Good audit reporting keeps both in view, so a programme cannot look busy while quietly leaving a backlog of open NCs to rot until the next surveillance visit. This guide covers the KPIs worth tracking, the reports that carry them, and how audit management software generates them from the same data an auditor already enters.
The core audit KPIs worth tracking
A manufacturer certified to ISO 9001, IATF 16949 or ISO 14001/45001 does not need dozens of metrics. It needs a small set that together answer one question: is the programme on plan, and is it closing what it finds?
| KPI | What it measures | How to read it |
|---|---|---|
| Plan adherence | Audits conducted versus audits planned for the period | Below 100% means the calendar is slipping — the first thing a registrar checks against clause 9.2 |
| Audit completion rate | Answered questions versus total questions per audit | A half-answered audit is not a conducted audit; this catches rushed or abandoned checklists |
| Open NC count | Findings raised but not yet closed, by area and type | The live backlog; watch the trend, not just the number |
| NC by category | Major versus minor non-conformances | A rising major count signals systemic problems, not isolated slips |
| On-time closure rate | NCs closed within their due date versus total closed | The single best measure of whether corrective action is real |
| NC ageing | How long open findings have been open | Anything past due, and especially anything past the next audit cycle, needs escalation |
| Repeat-NC rate | Findings flagged repetitive versus fresh | High repetition means corrective action is treating symptoms, not causes |
| Auditor coverage | Audits and areas covered per authorised auditor | Reveals over-reliance on one person and gaps in competency |
Notice that only two of these — plan adherence and completion rate — are about doing audits. The other six are about what happens to findings. That balance is deliberate: the value of an audit lives in its findings and their closure, so most of your reporting should point there. A programme that scores 100% on plan adherence but has a growing pile of overdue NCs is failing, and only closure-side KPIs will tell you.
The audit status report: planned vs conducted vs closed
The backbone report of any audit programme is the status report: for each plant, audit type and period, how many audits are planned, how many have been conducted, and how many are fully closed. Because every audit moves through a defined lifecycle — created at draft, released so it appears on the auditor’s worklist, checked as findings are actioned, and finally closed — the status report is simply a count of audits at each stage. That single view answers the plan-adherence and backlog questions at once, and it is the report a plant quality head opens first.
Underneath it sits the answered-versus-total progress figure, drawn straight from checklist entry. Each audit section shows how many questions have been answered against how many exist, so a conducted audit that is only 60% answered is visibly incomplete rather than silently passed. This is the metric that stops an audit being marked “done” when half the checklist was skipped.
Can you see planned-vs-conducted-vs-closed on one screen?
We can show your own audit calendar, answered-versus-total progress and the live NC register in a 30-minute demo — on your standards, not a sample dataset.
The NC summary register
If the status report is the programme’s heartbeat, the NC summary register is its evidence file. It lists every non-conformance with the fields an auditor and a registrar actually ask for: the audit number and date, the audit type and department, the requirement and clause number, the discrepancy observed, whether the finding is fresh or repetitive, the auditee and auditor names, and the closure status for each sign-off role. Add a prepared-by and approved-by line and a revision block, and the register is a standalone document you can hand to a customer or certification body without any preparation.
Two columns on this register do disproportionate work. The fresh-versus-repetitive flag is what surfaces the repeat-NC rate — the clearest sign that corrective action is failing — and the per-role closure status is what proves the finding was verified by someone other than the person who fixed it. Together they turn a list of problems into a defensible record of how each was resolved. For the mechanics of how findings are graded and closed, see the guide on NC closure follow-up and the Findings, NC & CAPA feature.
Dashboards for each role
Reports are for review; dashboards are for daily action. A capable system gives each role a landing page that shows only what they must act on, so the KPI stops being a monthly ritual and becomes an everyday nudge.
Auditee dashboard
The auditee’s open actions and due audits — pending HOD sign-offs, QMS-pending items, actions to submit before an audit executes and audit-summary items still open.
My open actionsAuditor dashboard
The auditor’s assigned and pending audits, with answered-versus-total progress and the open findings awaiting their verification before closure.
My audits & findingsHOD / quality-head view
The programme roll-up — plan adherence, open and overdue NCs, and closure ageing across plants, types and periods, so the person accountable sees the backlog before a registrar does.
Programme roll-upA KPI only changes behaviour when it lands on the person who can act on it. A single organisation-wide dashboard tells the quality head everything and the auditee nothing useful; role dashboards put the overdue action in front of the auditee who owns it and the unverified finding in front of the auditor who must close it. See Dashboards & Audit Reports.
How to build audit KPI reporting that lasts
Whether you configure a system or start with a disciplined spreadsheet, the same principles separate reporting that survives an audit programme from reporting that is abandoned by March.
What good audit reporting looks like on the floor
Picture an IATF 16949 supplier running system, process and product audits across three plants. The quality head opens one status view: 42 audits planned this quarter, 39 conducted, 3 slipping at Plant 2; 61 NCs raised, 11 still open, 4 of them overdue and one repetitive on the same clause as last quarter. Every figure comes straight from checklist entry and the closure history — nothing was re-keyed. From that one screen the head knows where to push — chase Plant 2, escalate the overdue actions, treat the repeat NC as systemic. That is the difference reporting makes.
How Fast Audit Software reports each KPI
Fast Audit Software generates all of this from the data an auditor already enters, with no separate reporting step. The dashboards and reports give each role their view; the status of every audit drives the planned-versus-conducted-versus-closed roll-up; the answered-versus-total figure comes directly from checklist entry; and the NC summary register carries clause, discrepancy, the fresh-versus-repetitive flag and per-role closure status ready to hand to a customer or registrar. Product and process audits add their own formatted report with parameter checks, samples and defects.
Because it runs on the shared Fast Suite platform, the same reporting can feed Dhruv AI for NC-trend summaries and closure-ageing insight, while a major finding can escalate into Fast Quality’s 8D / CAPA workflow without re-keying. INR pricing depends on users, plants and whether Fast Audit is licensed standalone or with the suite — see indicative pricing and confirm the report set your certification body expects. To see where these numbers come from end to end, start with the pillar guide on what audit management software is.
Frequently asked questions
What are the most important audit KPIs?
The most important audit KPIs measure closure, not just activity. Track plan adherence (audits conducted versus planned), audit completion rate (answered versus total questions), open NC count by area and type, NCs by category (major versus minor), on-time closure rate, NC ageing, repeat-NC rate (fresh versus repetitive), and auditor coverage. Together they answer whether the programme is on plan and whether it closes what it finds. On-time closure rate and NC ageing are the headline numbers, because a programme can look busy while leaving a backlog of open non-conformances until the next surveillance audit.
What is an audit status report?
An audit status report shows, for each plant, audit type and period, how many audits are planned, how many have been conducted, and how many are fully closed. Because every audit moves through a defined lifecycle from draft to released to in-closure to closed, the status report is a count of audits at each stage. It answers plan adherence and backlog at once and is usually the first report a quality head opens. Underneath it sits the answered-versus-total progress figure, so a conducted audit that is only partly answered is visibly incomplete rather than silently passed.
What should an NC summary register contain?
An NC summary register should list every non-conformance with the audit number and date, audit type and department, the requirement and clause number, the discrepancy observed, whether the finding is fresh or repetitive, the auditee and auditor names, and the closure status for each sign-off role, plus prepared-by and approved-by lines and a revision block. The fresh-versus-repetitive flag surfaces the repeat-NC rate, and the per-role closure status proves each finding was verified by someone other than the person who fixed it. Kept this way, the register is a standalone document you can hand to a customer or certification body without preparation.
How do audit dashboards differ from audit reports?
Audit reports are for periodic review; dashboards are for daily action. A report such as the status report or NC register rolls up figures across a period for the quality head or a registrar. A dashboard shows each role only what they must act on now: the auditee sees their open actions and due audits, the auditor sees assigned audits and findings awaiting their verification, and the HOD sees the programme roll-up of plan adherence and overdue NCs. Splitting the view by role matters because a KPI only changes behaviour when it lands on the person who can act on it.
Can Fast Audit Software generate these reports automatically?
Yes. Fast Audit Software generates its status report, answered-versus-total progress, NC summary register and role dashboards from the same data auditors enter during checklist entry, with no separate reporting step. Product and process audits add a formatted report with parameter checks, samples and defects. Because it runs on the shared Fast Suite platform, the same data can feed Dhruv AI for NC-trend and closure-ageing insight, and a major finding can escalate into Fast Quality's 8D and CAPA workflow without re-keying. Indicative INR pricing depends on users, plants and whether Fast Audit is licensed standalone or with the suite.