How do you calculate data quality defect rate?

Divide the count of records that fail validation by the total records validated and multiply by 100. With 8 failing records out of 250, the defect rate is 3.2%, a 91.8-point gap from a 95% target.

What is a good data quality defect rate?

Lower is better; mature programs hold defect rates under 2% on mandatory rules. Note that if your target is expressed as a quality threshold of 95%, a defect rate is read inversely — you want it small, not large.

What is the difference between defect rate and completeness rate?

Completeness checks whether fields are filled; defect rate checks whether filled values pass validation rules. A record can be complete but defective if, say, its lead time is negative.

How do I interpret the gap to target here?

The 91.8-point gap reflects the arithmetic difference between the 3.2% result and the 95% reference. Treat the reference as your quality threshold and the defect rate as the count of records that violate it.

What causes a high defect rate?

Missing or weak validation at entry, legacy free-text data, copy-paste record creation, and unit-of-measure or classification errors that bulk loads never checked.

How often should I measure defect rate?

Run it on every bulk load and before any defect-sensitive process like an MRP run or financial close, plus a monthly trend for the governance scorecard.

Manufacturing Master Data & Data Governance calculator

Data Quality Defect Rate Calculator

Data Quality Defect Rate is the percentage of master data records that fail one or more validation rules — invalid UOM, out-of-range lead time, a vendor with no payment terms. Data stewards and governance leads track it to quantify how much of their data is actively wrong rather than merely incomplete, since a defective record can pass a completeness check yet still break a transaction. It is the workhorse KPI for remediation programs because it ties directly to downstream failures: every defect is a potential blocked order, mis-plan, or failed posting. Trending it down is the most direct evidence that data quality rules and steward effort are paying off.

What this calculator does

Estimate data quality defect rate for manufacturing master data and data governance using production-ready inputs so teams can track KPI performance and decide whether corrective action is needed.
Use it when data quality defect rate in manufacturing master data and data governance needs a clean rate and gap-to-target you can put on a tier board.
It computes the percentage of validated records that fail at least one quality rule, and the gap in points between that defect rate and your target.

Formula used

Data quality defect rate = data quality defect rate count ÷ total data quality defect rate population × 100
Data quality defect rate gap to target = data quality defect rate - target data quality defect rate

Inputs explained

Records failing a data quality validation rule:
Total master data records validated:
Target data quality defect rate:

How to use the result

Use it after running validation rules over a dataset, during periodic governance scorecards, or to verify remediation before a critical process like MRP run or month-end.
The defect rate is only as good as the rules behind it — weak or missing validations will under-report true defects, so a low rate can be falsely reassuring.

Common questions

How do you calculate data quality defect rate? Divide the count of records that fail validation by the total records validated and multiply by 100. With 8 failing records out of 250, the defect rate is 3.2%, a 91.8-point gap from a 95% target.
What is a good data quality defect rate? Lower is better; mature programs hold defect rates under 2% on mandatory rules. Note that if your target is expressed as a quality threshold of 95%, a defect rate is read inversely — you want it small, not large.
What is the difference between defect rate and completeness rate? Completeness checks whether fields are filled; defect rate checks whether filled values pass validation rules. A record can be complete but defective if, say, its lead time is negative.
How do I interpret the gap to target here? The 91.8-point gap reflects the arithmetic difference between the 3.2% result and the 95% reference. Treat the reference as your quality threshold and the defect rate as the count of records that violate it.
What causes a high defect rate? Missing or weak validation at entry, legacy free-text data, copy-paste record creation, and unit-of-measure or classification errors that bulk loads never checked.

Last reviewed 2026-05-12.