Principle

Check records and fields separately

Filled fields cannot account for missing records.

About 1 min read

Before you use it

Use when
  • A migration reports a high field-completion rate, but some expected customers may be missing.

Keep this limit in mind

  • A populated value may still be wrong. Set explicit rules for fields that do not apply before scoring.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Check which expected records arrived, then check required fields within those records. A field-completion rate among arrived records leaves out records that never arrived. Report the two questions separately so a good rate for one cannot hide a gap in the other.

Steps

  1. Compare expected and arrived record identities within the same scope.
  2. Check required fields for the arrived records and label that denominator.

An example

In this example, 450 of 500 expected accounts arrive. Of those 450, 420 have the required country code. Record coverage is 90%; country-code completion among arrived accounts is about 93.3%.

Check your result

Report 450/500 accounts present and 420/450 arrived accounts with a country code. If the task needs every expected account with that field, report 420/500: 84%.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingCheck records and fields separately

Evidence and sources
Supports

Completeness covers both the presence of expected records and the population of essential values within records; populated values may still be inaccurate.

Claim limit: A framework definition, not a universal field list or proof that the adapted checks diagnose a particular migration failure. Required records and values depend on the task. Source reading history: selected_passages; 2026-10-11; Six dimensions and user needs; Completeness definition and distinction from accuracy. Official page was opened on 2026-10-10 and identified sections inspected. This verifies a narrow reference basis, not the effectiveness or completeness of independently drafted practice steps. On 2026-10-11 the Completeness definition and its distinction from accuracy were read again for cards 9721/9725; this is selected-passage screening, not independent review. Agent release review: PostgreSQL 18 table expressions, NULL comparisons and aggregates, the UK Government Data Quality Framework and Microsoft Power Query profiling documentation were checked at the cited sections. The original examples and scope limits remain attached.

The Government Data Quality Framework · Data quality dimensions: Completeness, definition and distinction from accuracy

All sources (1)
Edition and review

Version 0.1.0 · Published

Edition checked · 2026-11-12

Read this idea as JSON · Release details