Protocol

Replay examples before changing a data rule

Stricter can still be wrong.

About 1 min read

Before you use it

Use when
  • You change a data-quality rule after discovering errors or exceptions.

Keep this limit in mind

  • These cases support a regression check, not acceptance of the whole dataset. This is editorial testing practice; no optimal sample size or privacy guarantee is claimed.

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

Choose normal, erroneous and boundary cases. For each, record the intended accept/reject result and why it fits the agreed data requirements. Old pass/fail labels are comparison data, not the answer key. Run both rule versions on the same cases and explain every changed result.

Steps

  1. Use invented or redacted examples that preserve the condition under test. Retain only the fields needed; follow local handling rules if real records are necessary.
  2. Keep both rule versions, expected results and reasons. Mark uncertain cases for review instead of guessing a label.

An example

An agreed local code list permits ABC and ABCD. A three-letter-only check rejects ABCD but still accepts forbidden ZZZ. The examples expose both defects.

Check your result

The intended errors are caught and justified valid cases remain accepted. Every changed result matches an agreed requirement or remains an explicit review item.

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 readingReplay examples before changing a data rule

Evidence and sources
Supports

The issues framework recommends defining a data purpose, quality rules and targets before measuring performance, then prioritising below-target issues using purpose importance, failure impact and performance.

Claim limit: Practical prioritisation guidance, not evidence that its suggested scores or tolerances are universally optimal. Its date-range example is labelled accuracy; this source supports prioritisation here, not the validity/accuracy distinction set out in the companion guidance. Explicit denominators and regression examples are authored adaptations, not requirements established by this page. Source reading history: selected_passages; 2026-10-11; Rules and purpose, importance/impact, targets and priority; 16 April 2026 update. 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 these prioritisation sections were read again. The date-range example uses accuracy where the companion guidance distinguishes validity; this limited source use does not adopt that example’s terminology. 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.

Data quality issues framework · What data quality rules and issues are; Determine importance and impact; Set targets; Assign priority

Supports

The action-plan guide advises keeping measurement criteria current, reviewing and refining assessment criteria, and comparing data quality before, during and after significant changes.

Claim limit: Governance guidance, not experimental proof of this adapted regression procedure. Expected-case labels, synthetic/redacted cases and minimal retained fields are editorial testing choices; this source establishes no optimal sample size or privacy guarantee. Source reading history: selected_passages; 2026-10-11; Steps 3–5 and 7: assessment, ownership, target timeframe/review date, cause investigation and monitoring; steps 2 and 7: current/refined criteria and before/during/after change comparison. 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 these sections were read again for the owned-action correction. No empirical effectiveness, independent or production acceptance is inferred. On 2026-10-11 steps 2 and 7, including Plan for and manage changes, were read for card 9732; its regression examples and data minimisation are authored practice, not empirical or privacy certification. 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.

Implementing a data quality action plan · Step 2: Identify data quality rules; Step 7: Repeat measure over time, Plan for and manage changes

All sources (2)
Edition and review

Version 0.1.0 · Published

Edition checked · 2026-11-12

Read this idea as JSON · Release details