Blog · Board and management reporting · Manufacturing
A quality assurance dashboard compares inspection failures, rework, scrap, and unresolved exceptions. Follow a worked US manufacturing example, reconcile every unit, and separate quality performance from changes in labor cost.
A quality assurance dashboard compares inspection failures, rework, scrap, and unresolved quality exceptions from the same inspected population. Its most useful check is simple: every failed unit must have a recorded disposition or remain visibly open. Counts show the workload; rates make sites with different inspection volumes comparable.
Use the initial inspection register as the starting file. Keep a unique unit identifier, site, product family, inspection timestamp, first-pass result, and defect code. A separate disposition export can supply rework completion, scrap, or hold status, linked back to that same identifier.
The distinction between a defective unit and a defect matters. NIST distinguishes nonconforming items from individual nonconformities: a unit can have more than one recorded problem. Counting every defect-code row as a failed unit would inflate the failure rate.
For this dashboard, a failed unit is a unique unit that did not pass its initial inspection. Count that identifier once in the failure numerator. Use defect events in a separate breakdown when investigating what went wrong.
First-pass failure rate = Unique units failing initial inspection / Unique units initially inspected
First-pass yield = Units passing initial inspection / Unique units initially inspected
NIST defines the proportion nonconforming as nonconforming items divided by the relevant item population. Here, that population is the inspected cohort, rather than all production at the plant.
Consider an illustrative US manufacturer of metal housings. Its Ohio and Indiana plants inspect completed units during the week ending October 16, 2026. The dashboard freezes disposition status at the weekly review. All successful rework shown below has passed reinspection; units still awaiting a result remain on hold.
| Site | Initially inspected | First-pass failures | Passed after rework | Scrapped | Still on hold |
|---|---|---|---|---|---|
| Ohio | 4,000 | 160 | 120 | 30 | 10 |
| Indiana | 2,000 | 140 | 80 | 50 | 10 |
| Total | 6,000 | 300 | 200 | 80 | 20 |
First-pass successes are inspected units minus failures. The calculation and the resulting rates are:
| Site | First-pass successes | Failure-rate calculation | Failure rate | First-pass yield | Rework completions / inspected |
|---|---|---|---|---|---|
| Ohio | 4,000 − 160 = 3,840 | 160 / 4,000 | 4.00% | 96.00% | 3.00% |
| Indiana | 2,000 − 140 = 1,860 | 140 / 2,000 | 7.00% | 93.00% | 4.00% |
| Total | 5,700 | 300 / 6,000 | 5.00% | 95.00% | 3.33% |
Percentages are rounded to two decimal places after calculation. Rework completion share uses the same inspected-unit denominator: Ohio is 120 / 4,000, Indiana is 80 / 2,000, and the combined result is 200 / 6,000.
Indiana has fewer failures in absolute terms, but a higher failure rate. That makes it the priority for investigating first-pass performance. Ohio still has the larger completed rework volume, so it may need more rework capacity even while its failure rate is lower.
For the workbook implementation of these measures, use the separate spreadsheet quality dashboard guide.
The first check closes each site's failed population:
| Check | Ohio | Indiana | Combined |
|---|---|---|---|
| Failed units = reworked + scrapped + held | 160 = 120 + 30 + 10 | 140 = 80 + 50 + 10 | 300 = 200 + 80 + 20 |
| Inspected = first-pass successes + failures | 4,000 = 3,840 + 160 | 2,000 = 1,860 + 140 | 6,000 = 5,700 + 300 |
The combined accepted population at the cutoff is 5,700 first-pass successes plus 200 successful reworks, or 5,900 units. Its share of inspected units is 5,900 / 6,000 = 98.33%. Label it accepted by cutoff, because the 20 held units have no final result yet.
The broader reconciliation is 6,000 = 5,900 accepted + 80 scrapped + 20 held. A held unit cannot simultaneously appear in accepted output. If a disposition export contains successive status updates, select the latest valid status at the cutoff rather than summing the history.
Errors in identifiers and joins need their own data-quality dashboard; they should not appear as manufacturing defects.
The same company records rework labor at a fully loaded hourly rate supplied by finance. Scrap cost below is the recorded carrying cost written off, with no recovery proceeds in this example.
| Site | Rework hours | Labor rate (USD/hour) | Rework labor (USD) | Scrap cost (USD) | Tracked failure cost (USD) |
|---|---|---|---|---|---|
| Ohio | 60 | 35 | 60 × 35 = 2,100 | 240 | 2,340 |
| Indiana | 50 | 35 | 50 × 35 = 1,750 | 400 | 2,150 |
| Total | 110 | 35 | 3,850 | 640 | 4,490 |
Tracked failure cost is rework labor plus scrap cost: 3,850 + 640 = $4,490. This is a defined subtotal. Inspection overhead, customer returns, freight, and other costs are outside the example. See the separate quality-cost dashboard example for a wider cost review.
Now change one input: increase the common labor rate from $35 to $42 per hour. Keep hours, failures, rework completions, scrap, and holds unchanged. Rework labor becomes 110 × 42 = $4,620; tracked failure cost becomes 4,620 + 640 = $5,260. The increase is 110 × (42 − 35) = $770.
The failure rate remains 5.00%. The cost increase comes entirely from the labor rate, so the dashboard should not describe it as deteriorating inspection performance.
Let the quality manager own inspection definitions and exception disposition. Site leaders own the investigation of recurring failures. Finance owns labor rates and scrap valuation. Keep each hold linked to its unit or lot, current reason, accountable role, and next review date.
For a trend, repeat the same cohort calculation for each closed week. Show the inspected count beside the failure rate and retain the cutoff convention. A recent cohort with more unresolved holds is less mature than an older one, even when its first-pass result is already complete.
Bring an inspection export and the matching disposition and cost records to Covirage. Covirage maps the columns; its tools compute and check the figures, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account, then set up your business and bring a sample of your own data.
See Covirage for industrial manufacturers for the manufacturing context.
Start with unique units inspected, first-pass failures, first-pass yield, completed rework, scrapped units, and unresolved holds. Add rework hours and recorded scrap cost when reliable cost records exist. Keep defect events separate from failed units because one unit can have several recorded problems.
No. A unit that fails its initial inspection remains a first-pass failure even if rework makes it acceptable later. Record its successful rework as a separate disposition. That preserves visibility into the extra labor and delay needed to obtain acceptable output.
Choose a cadence that matches the inspection process and the decisions being made. A site team may review completed shifts, while a company review uses weekly cohorts. Always display the inspection window and disposition cutoff so unresolved units are interpreted consistently.