Resources/Glossary/
Defects Per Unit
Lean Metrics and Measurement

Defects Per Unit

Counting how many things went wrong, not just how many parts went out.

Updated
·
4
min read
Definition

What is Defects Per Unit?

Defects per unit, or DPU, is the average number of defects found per unit produced or inspected, calculated by dividing total defects by total units. A line that inspected 200 units and found 50 defects has a DPU of 0.25. Unlike scrap rate, DPU counts every defect, including multiple defects on the same unit. It is the metric of choice when a part can fail in more than one way at once.

Defects per unit is the metric that catches what pass/fail misses. A part can have three small defects and still ship. A part can fail one critical check and never ship. Scrap rate and first-pass yield treat both as binary; DPU counts the defects themselves. On complex products with many features, this difference matters. The conversation about quality is much different when you can see that the average unit has 0.4 defects than when you only know that 96 percent of units passed.

"Pass-fail counts the parts. DPU counts what went wrong with them."

How defects per unit works

The arithmetic is total defects divided by total units. The interesting questions live in the count of defects and the choice of inspection point.

The choices that shape the number

  • Inspection scope. All inspections during the process, or just final inspection? Process-wide DPU captures the rework loop; final-only DPU captures what escapes.
  • Defect taxonomy. A clear list of defect modes is required. "Defect" without modes is unactionable.
  • Same unit, multiple defects. DPU counts them all. This is the metric's signature feature and the reason it differs from yield.
  • Sample versus full count. Many shops inspect a sample. DPU based on samples is a statistical estimate; full inspection gives a clean count but costs more.

DPU also serves as the bridge between operator-visible defect counts and the more abstract Six Sigma metrics. The defect log that produces DPU is also the data feed for DPMO and for pareto analysis of failure modes. A shop that has clean DPU tracking has the foundation for any quality improvement project that follows.

Where defects per unit fits on the shop floor

Imagine a 20-person sheet metal fab shop building enclosures for an industrial controls customer. The enclosures have about fifteen quality-critical features each: weld joints, painted surfaces, dimensional tolerances, and threaded holes. The shop reports a 96 percent final yield and considers quality acceptable.

The customer asks for DPU data as part of an audit. The shop sets up a defect log at final inspection with fifteen defect modes derived from the quality plan. The first month of data shows DPU at 0.4. The 96 percent yield number was correct: most units shipped. But on average, every shipped unit had close to half a defect found and corrected before it left the dock. The hidden rework cell handling those corrections is six labor-hours a day.

The Pareto on the defect log is even more useful than the headline DPU. Two modes (paint flow and one threaded-hole burr issue) account for 70 percent of defects. A spray-booth tuning project and a deburring fixture revision drop those two modes by 80 percent over the next quarter. DPU falls from 0.4 to 0.12. The rework cell shrinks to less than two hours a day. None of this was visible in the 96 percent yield headline. DPU surfaced the work.

Common mistakes with defects per unit

  • Reporting the headline without modes. A DPU number alone is just a thermometer reading. The defect-mode breakdown is what tells you where to operate.
  • Comparing across product complexity. A 0.5 DPU on a 20-feature product is different from 0.5 DPU on a 5-feature product. Without complexity normalization the comparison is unreliable.
  • Counting only formal inspection defects. Operator-fixed defects that never appear on a log are invisible to the metric. Capture them or accept that DPU understates.
  • Using sample-based DPU as if it were a full count. Sampling produces an estimate. Treat it as one and report the confidence interval where it matters.
  • Treating DPU as a target. It is a result of process control. Pushing the number without fixing the failure modes leads to under-reporting, not better quality.

Defects per unit and related Lean tools

Defects per unit is the count-based companion to scrap rate, which measures the share of unrecoverable output. DPU normalizes for unit volume but not for product complexity; defects per million opportunities adds the complexity normalization for cross-product comparison, and parts per million is the customer-facing defective-parts view. Together with first-pass yield, these metrics give a shop a complete view of where defects are happening and how to prioritize the work to remove them.

Common questions

The questions we hear most about this term.

How does defects per unit work as a calculation?
You count every defect found, divide by the total number of units inspected, and report the result as a decimal. A line that inspected 1,000 units and found 320 defects has a DPU of 0.32. If three defects show up on one unit and zero on another, that is still three defects across two units, or 1.5 DPU. The metric captures every failure mode, not just whether a unit passes or fails. That is its strength on multi-feature products and the reason it differs from scrap rate.
How is defects per unit different from scrap rate?
Scrap rate counts unrecoverable parts as a percentage of production. DPU counts defects regardless of whether the part is recoverable. A part with three minor defects that all get reworked counts as three defects in DPU and as zero in scrap rate. A part with one defect so severe it cannot be saved counts as one defect in DPU and one scrap unit. DPU is more sensitive to total quality cost; scrap rate is more sensitive to material loss. They tell different stories about the same process.
What are common mistakes with defects per unit?
The biggest is reporting DPU without a defect-mode breakdown. The headline number tells you the line has problems; the breakdown tells you what to fix. The second is comparing DPU across products with different complexity. A complex part with twenty features will almost always have higher DPU than a simple part with three, regardless of process quality. DPMO normalizes for this; plain DPU does not. The third is counting only formal inspection defects, ignoring the small fixes operators handle quietly without logging.
When should I use defects per unit versus other quality metrics?
Use DPU when parts can have multiple defects at once and you care about total defect volume, not just pass/fail. Use scrap rate when material loss is the main concern. Use first-pass yield when you want a single-process pass/fail measure. Use DPMO when you need to compare quality across products of different complexity. DPU sits in the middle of the family: more informative than pass/fail, simpler than DPMO, and well-suited to multi-feature products where defects co-occur.
What does good DPU tracking look like?
A simple defect log at each inspection point with two columns: unit number and defect mode. Daily roll-up to a DPU number by line. A Pareto chart of defect modes by frequency, refreshed weekly, showing the top three. A trend chart on the floor visible to the team that catches and reports the defects. The metric exists to direct improvement work; the breakdown is what makes it actionable. A single DPU number on a dashboard with no mode breakdown is decoration.
From the blog

Go deeper

Long-form guides that pick up where this definition leaves off, written for manufacturers running Arda today.

No items found.

Ditch the whiteboards and spreadsheets.

Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.