Skip to content
BENIBIX Learn

Data Completeness

Also known as Completeness (Data Quality), Missing Data

Whether all the rows and fields that should be there are there.

Think of it like

A puzzle with three pieces missing. You can see the picture, but not all of it.

Example

A daily load brings 9,800 orders when it usually brings 10,000. A missing file from one shop explains the gap.

Why it matters

Gaps make every total too small, and no one sees it. A report can look fine while a whole region is gone.

Definition

Data completeness is whether all the data that should be there is there. It looks at blank fields, such as a missing email. It also looks at missing rows, such as a day with no orders at all. A field can be allowed to be blank, so the rule must say which ones are required. Completeness is usually given as a percentage.

Example code

sql
SELECT COUNT(*) AS total,
       COUNT(email) AS with_email,
       100.0 * COUNT(email) / COUNT(*) AS pct_complete
FROM customers;
COUNT(email) skips blanks, so the two counts give the share of customers with an email.
Completeness is the second tile. A required field is blank.

Common mistake

Only counting blanks. A load that skips a whole file has no blanks at all, just fewer rows.

Key takeaways

  1. 1
    No blanks. Required fields are filled in.
  2. 2
    No missing rows. Every expected record arrived.
  3. 3
    A percentage. Measured as a share of the total.