Heuristic
Prioritise errors by their impact
The busiest quality dashboard is not necessarily the safest system.
Before you use it
- Use when
- The team can validate dozens of fields but has little repair capacity.
Keep this limit in mind
- The UK guide offers one prioritisation approach, not universal numeric thresholds.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Tie each rule to a business purpose and the consequence of failure. Prioritise a wrong payment destination or invalid legal identifier differently from an optional marketing field. Set acceptable thresholds with the relevant owner rather than copying universal numbers.
Steps
- Name the action or decision the field supports.
- Agree impact, threshold and escalation owner.
An example
A missing optional preference and a wrong bank account are both one failed cell but not comparable risks.
Check your result
The quality backlog ranks issues by consequence and intended use.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingPrioritise errors by their impact
From this idea
This idea is useful withInspect failed data checks
Evidence and sources
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
All sources (1)
Edition and review
Version 0.1.0 · Published
Edition checked · 2026-11-12