# Data Cleansing Defect Log Worksheet

> Source: https://netray.co/tools/data-cleansing-defect-log-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Log each data quality defect with the affected records, severity, owner, effort and status, and see the total cleanup effort and cost.

## Category

erp-operations

## Audience

- Data steward
- ERP migration lead
- MDM lead

## Tool

**Kind:** worksheet

**Mode:** editable

**Currency:** $

**Columns:**

#### Defect ID

**Key:** id

**Type:** text

#### Domain

**Key:** domain

**Type:** select

**Options:**

- Item
- Vendor
- Customer
- BOM
- Routing
- Finance
- Other

#### Issue

**Key:** issue

**Type:** text

#### Records affected

**Key:** records

**Type:** number

#### Severity

**Key:** severity

**Type:** select

**Options:**

- Critical
- High
- Medium
- Low

#### Owner

**Key:** owner

**Type:** text

#### Found on

**Key:** found

**Type:** date

#### Minutes per record

**Key:** mins

**Type:** number

**Unit:** min

#### Hourly rate

**Key:** rate

**Type:** number

**Format:** currency

#### Fix hours

**Key:** hours

**Type:** number

**Expr:** records * mins / 60

**Format:** number

#### Fix cost

**Key:** cost

**Type:** number

**Expr:** records * mins / 60 * rate

**Format:** currency

#### Status

**Key:** status

**Type:** select

**Options:**

- Open
- In progress
- Fixed, to verify
- Closed

**Rows:**

**Id:** DQ-001

**Domain:** Item

**Issue:** Missing unit of measure on purchased items

**Records:** 220

**Severity:** High

**Owner:** Materials steward

**Found:** 2026-10-05

**Mins:** 3

**Rate:** 40

**Status:** In progress

**Id:** DQ-002

**Domain:** Vendor

**Issue:** Likely duplicate vendors by tax ID

**Records:** 46

**Severity:** Critical

**Owner:** AP lead

**Found:** 2026-10-06

**Mins:** 15

**Rate:** 40

**Status:** Open

**Id:** DQ-003

**Domain:** BOM

**Issue:** Inactive components on active BOMs

**Records:** 85

**Severity:** High

**Owner:** Engineering data lead

**Found:** 2026-10-08

**Mins:** 10

**Rate:** 55

**Status:** Open

**Id:** DQ-004

**Domain:** Customer

**Issue:** Missing ship-to postal codes

**Records:** 310

**Severity:** Medium

**Owner:** Customer service lead

**Found:** 2026-10-09

**Mins:** 2

**Rate:** 35

**Status:** Fixed, to verify

**Id:** DQ-005

**Domain:** Routing

**Issue:** Operations with zero run time

**Records:** 132

**Severity:** Medium

**Owner:** Manufacturing engineer

**Found:** 2026-10-12

**Mins:** 6

**Rate:** 55

**Status:** Open

**Totals:**

#### Records affected

**Key:** records

**Agg:** sum

**Format:** integer

#### Total fix hours

**Key:** hours

**Agg:** sum

**Format:** number

#### Total fix cost

**Key:** cost

**Agg:** sum

**Format:** currency

**Summary:**

#### Average fix cost per defect

**Key:** avg_cost

**Expr:** if(gt(count,0), sum_cost / count, 0)

**Format:** currency

**Notes:** Log a defect once per root cause, not per record, and keep the list of affected record IDs in an attached file. Fix hours and cost use records times minutes per record, and are estimates for planning.

## Content

**Intro:** Data cleansing needs a backlog, owners and a way to size the effort. This defect log records each issue by domain, severity and owner, and totals the estimated hours and cost to fix it.

**Sections:**

#### How to use the log

**Body:** Create one row per root cause. Describe the issue plainly, such as missing unit of measure on purchased items, and enter the number of affected records from your rule run. Set severity by business impact, name an owner, and estimate minutes per record. The worksheet calculates fix hours and cost, so you can plan cleanup sprints before a migration or audit. Update status as work moves from open to closed.

**Bullets:**

- One row per root cause
- Severity reflects business impact
- Estimate minutes by sampling a few records
- Verify fixes with a rerun of the rule

#### Setting severity

**Body:** Critical defects cause financial loss, compliance breach or production stoppage, for example duplicate vendors with the same bank account or missing export classification on controlled parts. High defects break a process regularly, such as missing planning attributes. Medium defects cause rework. Low defects are cosmetic. Agree the scale with the data owners and apply it consistently.

#### Using it for migration

**Body:** Before an ERP migration, a defect log is the usual way to track cleansing in source data. Fix what you can at the source, not in the load file, so the clean data persists. Use the cost total in your project plan, and track closure rates in each mock load. Carrying known defects into the new system is a decision to make explicitly, not by default.

#### Common mistakes

**Body:** Logging every record as its own defect, fixing in the load file only, closing without verification and ignoring the root cause. If the same defect returns each month, add a validation at data entry or a rule in your catalog.

**Cta:** If you have a large backlog, we can build agents that propose fixes for human approval inside your ERP, such as standardized descriptions and duplicate merges.

**Faq:**

#### What is a reasonable minutes per record?

**Answer:** Sample ten records and time the fix. Simple field fills may take one to three minutes. Merging duplicates, which needs checking of open documents, often takes ten to twenty.

#### How do I prioritize the backlog?

**Answer:** Sort by severity first, then by records affected and effort. Fix critical defects regardless of cost, then pick high impact, low effort items for quick wins.

#### Should I log defects found in testing?

**Answer:** Yes if they are data defects. Tag them with the test cycle in the issue text so you can see whether the count falls cycle by cycle.

#### Does cost include system time?

**Answer:** No. It is labor only. Add costs for tools, consulting or downtime in your project budget.

## Search terms

data cleansing log template, data quality issue log excel, data defect tracker, master data cleanup tracker, data cleansing worksheet, erp data cleanup plan, migration data defect log

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json