Why Data Quality Must Come Before Government AI

Government AI systems are only as reliable as the data behind them. Before departments can deploy AI safely and effectively, they need accurate, complete, and well-governed data — because poor data quality produces unreliable AI outputs regardless of model sophistication. The Artificial Intelligence Playbook for the UK Government identifies data quality as a foundational requirement, yet many departments prioritise AI investment ahead of the data work that makes it trustworthy.

At a glance

The UK Government is racing to adopt artificial intelligence (AI) across public services. But there is a problem that no amount of investment in algorithms can fix: some of the underlying data is not good enough to support it.

— Sara Boltman, Founder & CEO, Butterfly Data

What is data quality in the context of government AI?

Data quality refers to the accuracy, completeness, consistency, timeliness, and provenance of the datasets that train or operate an AI system. In a government context, this typically means records that match across systems, fields that are populated rather than left blank or defaulted, formats that are standardised, and a clear, auditable trail of where each data point originated.

Why can't AI governance alone solve this?

AI governance frameworks address ethical and procedural risk — bias review, explainability requirements, and accountability structures. They don't fix the data itself. A well-governed AI system built on flawed data still produces flawed outputs. Governance and data quality are complementary, not substitutes: governance tells you who is responsible and how decisions get checked; data quality determines whether there's anything trustworthy to check in the first place.

What happens when government AI is built on poor-quality data?

●      Biased outcomes — models trained on unrepresentative or incomplete records replicate and amplify that gap

●      Inaccurate risk scoring — decisions in areas like fraud detection or eligibility assessment inherit the errors in the source records

●      Unreliable predictive models — forecasts degrade in proportion to the noise in the input data

●      Loss of traceability — with data provenance under increasing scrutiny, poor lineage makes it difficult to explain how a decision was reached, which is a growing legal and audit risk, not just a technical one

How should departments sequence this?

1. Data quality audit and remediation — establish the actual state of the data before building on top of it

2. Governance and stewardship structures (DAMA-aligned) — assign ownership and accountability

3. AI/analytics deployment on the now-trustworthy data foundation

4. Ongoing monitoring — data quality isn't a one-off cleansing exercise; it degrades again without continuous checks

FAQ

Does UK government policy require data quality checks before AI deployment?

The AI Playbook for the UK Government identifies data quality as foundational, though it isn't a hard procurement mandate in the way transparency-of-AI-use disclosure is under PPN02/24. It is best-practice guidance — strongly recommended rather than legally required.

What's the difference between data quality and data governance?

Data quality is about the state of the data itself — is it accurate, complete and consistent? Data governance is about the structures and accountability around it — who owns it, who's responsible for maintaining it, and how decisions about it are made. Quality work typically has to come first, or governance frameworks end up managing bad data.

Can AI itself be used to fix data quality problems?

Partially. AI-assisted anomaly detection and pattern analysis can accelerate quality checks, but it can't substitute for the foundational governance and cleansing work — especially where data provenance and lineage need to be established for audit or legal purposes.

‍

This resource builds on our CEO Sara Boltman's piece for UKAuthority, The Missing Prerequisite: Why Data Quality Must Come Before Government AI.