Why quality reporting is different
Most manufacturing reports are backward-looking scorecards: how much did we make, how much did we sell. Quality reports have a harder job. They must simultaneously drive a decision (which defect to attack, which gauge to recall, which supplier to challenge) and answer an audit question (prove your measuring equipment is calibrated, prove your parts are approved, prove your corrective actions closed). A quality report that does one but not the other is only half a report.
The trap is to build a wall of dashboards that look impressive and change nothing. The discipline is to keep only the reports that map to a real question — an operational one you act on this week, or a compliance one an auditor will ask in your next surveillance visit. This guide walks the handful of reports that earn their place, and the KPI behind each.
Reports as a by-product of daily work
The single biggest determinant of whether your quality reporting is trustworthy is where the numbers come from. If reports are compiled at month-end by copying figures out of inspection sheets, calibration registers and rejection books into a spreadsheet, they are late, error-prone and impossible to drill into. If they are generated live from the same records the inspector, the calibration owner and the line supervisor already created, they are current, reconciled and traceable to the source.
This is the core idea behind an integrated QMS: the records an IATF 16949 or ISO 9001 audit demands should be a by-product of daily work, not a pre-audit scramble. When incoming inspection is booked against the goods receipt, when every rejection carries a defect code, when each gauge has a calibration due-date and each PPAP element a controlled-document status, the reports below are not built — they are simply read. In Fast Quality every dashboard is rendered live from the transactional data, with export to PDF for the audit file.
Rejection Pareto and PPM
The most actionable quality report in any plant is the rejection Pareto — defects ranked by frequency or cost, so the biggest contributor sits first. The Pareto principle holds stubbornly in manufacturing: a small number of defect codes usually account for the majority of rejections, and attacking them in order is the fastest route to a lower reject rate.
A single Pareto is not enough, though — you need the same rejection data sliced three ways, because each slice points at a different owner:
- By defect — which failure mode costs you most; the entry point for an 8D.
- By process / work centre — where in the route the loss happens; the entry point for process improvement.
- By part — which product bleeds quality; the entry point for a control-plan review.
The headline KPI on top of the Pareto is rejection PPM (parts per million) — the industry-standard way automotive customers express defect rate. Tracking PPM as a trend, not a single month, is what shows whether your corrective actions are actually working. In Fast Quality, the process rejection MIS delivers the Pareto by defect, process and part directly off the coded rejection data.
Inspection acceptance by supplier
The mirror image of the rejection report is the inspection acceptance rate — the proportion of inspected lots dispositioned AC, sliced by item, supplier and period. Read by supplier, it is your real supplier scorecard: it reflects what a supplier actually ships, not what their certificate of conformance claims. A supplier whose acceptance rate is drifting down is a problem arriving in slow motion, and the report is what lets you see it before it becomes a line stoppage.
Read by item and period, the acceptance rate is a leading indicator of process health: a characteristic that is starting to fail more often at inspection is usually a process drifting toward the tolerance edge — the same signal SPC catches on the capability chart. Because the inspection data and the specification limits live in one system, the acceptance report and the SPC capability view are two readings of the same underlying data. In Fast Quality this is the inspection MIS and quality inspection reports, giving acceptance and rejection rates by item, supplier and period.
The calibration register
No quality report is asked for more predictably in an audit than the calibration register. IATF 16949 and ISO 9001 clause 7.1.5 require measuring equipment to be calibrated against traceable standards on a defined frequency, with records — and the register is the evidence. A good calibration report is not a list; it is a live status view that answers the auditor’s real question: “are any gauges overdue, and how do you know?”
The register that survives an audit shows, for every gauge: its type, range/least count, location, last-calibration date, frequency, derived next-due date, current status, and — the number that matters most — the overdue count. The associated KPIs are the count of gauges due within the next window and the count already overdue; a well-run metrology function keeps the overdue count at zero, driven by alerts that fire before a gauge falls due rather than a report that notices afterwards. In Fast Quality, the gauge calibration MIS is the audit-ready register, and calibration follow-up raises the due/overdue alerts.
Would your calibration register survive a surprise audit today?
See a live gauge register with overdue counts, a rejection Pareto by defect and process, and PPAP completeness per item — generated from daily work, in 30 minutes.
PPAP completeness and APQP progress
Two more reports earn their place for anyone running new-part introductions to an automotive customer. PPAP completeness per item answers “is this part actually ready to submit?” — it shows, for each part, which PPAP elements are complete, which are missing, and whether the package has reached Accepted. Because every PPAP element is a controlled document with an approval status, the completeness report is simply a roll-up of those statuses rather than a manually maintained checklist.
APQP program progress answers “will this launch be on time?” — it shows every open part by current stage, percentage complete, overdue gates and the owner responsible. The value is early warning: an overdue gate visible on a dashboard is a launch problem you can still fix, versus one discovered at the customer’s run-at-rate. In Fast Quality these are the PPAP dashboard, the item document-status dashboard, and the APQP dashboard, all rendered live from the same records the engineers maintain.
The essential KPI set
Strip quality reporting to its core and a compact set of KPIs remains — each tied to the report that produces it and the question it answers.
| KPI | Report behind it | Question it answers |
|---|---|---|
| Rejection PPM | Rejection Pareto (defect / process / part) | How much are we losing, and to which defect? |
| Inspection acceptance % | Inspection MIS by item / supplier | Which supplier or part is drifting? |
| Gauges overdue | Calibration register / MIS | Is our measurement compliant with clause 7.1.5? |
| PPAP completeness % | PPAP dashboard / document status | Is this part ready to submit? |
| APQP overdue gates | APQP dashboard | Will this launch land on time? |
| Rework volume & yield | Rework process report | What is rework actually costing us? |
| 8D / CAPA closure | Corrective-action tracking | Are our root causes actually being closed? |
Notice what is not on the list: vanity metrics with no owner and no action. Every KPI here either drives a specific decision or produces specific audit evidence — and each is generated from the transactional records rather than assembled by hand. That is the test a report must pass to be worth keeping.
One screen, five decisions
A quality head opens the plant’s quality dashboards for the weekly review. The rejection Pareto puts “casting porosity” at the top by cost — that becomes this week’s 8D. The inspection acceptance view shows one supplier’s rate has slipped three months running — that becomes a supplier challenge with the scorecard attached. The calibration register shows two gauges due next week — the metrology owner schedules them before they go overdue. The PPAP dashboard shows a new part is 80 % complete but missing its MSA study — the engineer is chased. And the APQP dashboard flags one overdue design-validation gate — the owner is called. Five decisions from records nobody had to compile, each traceable back to the source and each ready to show an auditor.
How Fast Quality reports quality
Fast Quality Software, built by Improsys in Pune on the shared Fast Suite platform, ships the reports above as live dashboards rather than spreadsheets to maintain:
Because every dashboard reads the same transactional records the team already creates, the reports are current, reconciled and traceable. For the full closed loop these reports sit inside, see the pillar guide on what quality management software is.
Frequently asked questions
What are the most important quality KPIs for a manufacturer?
A compact core set covers most needs: rejection PPM (defect rate expressed in parts per million), inspection acceptance percentage by supplier and item, gauges overdue against calibration, PPAP completeness per part, APQP overdue gates, rework volume and yield, and 8D/CAPA closure. Each should map to a specific decision you act on or a specific audit question you must answer — vanity metrics with no owner and no action are the ones to delete. The test a KPI must pass is that it either drives a decision or produces audit evidence.
What is a rejection Pareto and why does it matter?
A rejection Pareto ranks defects by frequency or cost so the biggest contributor sits first. It matters because the Pareto principle holds in manufacturing — a small number of defect codes usually account for most rejections — so attacking them in order is the fastest route to a lower reject rate. The most useful version slices the same coded rejection data three ways: by defect (the entry point for an 8D), by process or work centre (the entry point for process improvement), and by part (the entry point for a control-plan review). A monthly reject total tells you that you have a problem; the Pareto tells you which one.
What should a calibration register show for an audit?
For every gauge it should show the type, range or least count, location, last-calibration date, frequency, derived next-due date, current status and — most importantly — the overdue count. IATF 16949 and ISO 9001 clause 7.1.5 require measuring equipment to be calibrated against traceable standards on a defined frequency with records, so the register is the evidence. The best registers are live status views backed by alerts that fire before a gauge falls due, so the overdue count stays at zero, rather than a static list that notices lateness after the fact.
Should quality reports be built manually or generated by the system?
Generated by the system, always. If reports are compiled at month-end by copying figures out of inspection sheets, calibration registers and rejection books, they are late, error-prone and impossible to drill into. If they are read live from the same records the inspector, calibration owner and line supervisor already created, they are current, reconciled and traceable to the source. The whole idea of an integrated QMS is that audit-ready records are a by-product of daily work — the reports are not built, they are simply read and exported.
What is PPAP completeness reporting?
PPAP completeness per item answers “is this part ready to submit?” It shows, for each part, which PPAP elements are complete, which are missing and whether the package has reached Accepted. Because every PPAP element is a controlled document carrying an approval status, the completeness report is a roll-up of those statuses rather than a manually maintained checklist. Paired with the APQP progress dashboard — which flags overdue gates and owners on open launches — it gives early warning on new-part introductions instead of a nasty surprise at the customer’s run-at-rate.