Skip to main content

Search the Commons

Type at least 2 letters. Use the arrow keys to move through results, Enter to open, Escape to close.

Ask a question instead: answers drawn from across the Commons, with links to the source. Or browse the site map.

Manage and improve · Buying and suppliers

Make suppliers responsible for the quality of public data

Most public sector data is created, held or changed by suppliers' systems. Without clear obligations, public bodies pay twice: once for the service, and again to find, fix and work around poor data. This page sets out the barriers, the principles, and model clauses, KPIs and tender questions that put the responsibility where it belongs.

In short: a plain English summary
  • This page helps when you buy services from companies.
  • It has words for contracts about data quality.
  • Your own legal team must check them.

Why it matters

Commercial barriers to good data

Each barrier links to the clauses that address it. Select a clause number to add it to the builder.

Principles for every contract that touches public data

Data quality through the life of a contract

Clause builder

Choose the clauses you need. "Must" clauses are the floor for any contract that creates or holds public data. The schedule on the right updates as you choose, ready to copy into a specification or contract schedule for your commercial and legal teams to adapt.

Quick picks
Clauses

Your data quality schedule

Tender questions, with what good looks like

Use these in evaluation. Score each answer 0 to 4; the total shows how ready a bidder is to carry data quality responsibility.

Buying a data catalogue or quality tool? Build an RFI or RFP from 32 integration, portability and lock-in questions, and check a bundle for lock-in risks.

QuestionA good answerScore

Who does what

ActivitySupplierPublic body

Related: legacy and modernisation for exit and migration, interoperability and standards for formats and identifiers, AI inside suppliers' tools, and tooling.

Sources