Principle

Do not mistake a valid format for a true value

Well-formed wrong data is still wrong.

About 1 min read

Before you use it

Use when
  • A data feed passes every format and range check.

Keep this limit in mind

  • A reference can itself be stale or biased; do not claim ground truth merely because two systems agree.

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

Validity asks whether a value fits rules such as allowed codes and date formats. Accuracy asks whether it corresponds to the real-world entity. Test plausibility and, for high-impact data, compare with a trustworthy reference where available.

Steps

  1. List format rules separately from factual verification controls.
  2. Mark fields where no independent reference exists.

An example

A syntactically valid postcode can still belong to another customer.

Check your result

The report distinguishes what was format-checked from what was independently corroborated.

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 readingDo not mistake a valid format for a true value

Evidence and sources
Supports

Completeness, uniqueness, consistency, timeliness, validity and accuracy are distinct data-quality dimensions and must be prioritized according to intended use.

Claim limit: The UK government framework is practical guidance, not experimental evidence for the effectiveness of the adapted cards. Apply its dimensions and reporting advice to the specific data use, risk and local governance. 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 · Six quality dimensions, user needs and trade-offs

All sources (1)
Edition and review

Version 0.1.0 · Published

Edition checked · 2026-11-12

Read this idea as JSON · Release details