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.

Check and assess · Critical data asset baseline

What will it take to report data quality for every critical data asset by your deadline?

An effort model for producing a first data quality baseline for each critical data asset (CDA) in the baseline reporting return. Built from the GOV.UK policy and guidance, not from the earlier AI Mode answers. Every default is an assumption you can change.

In short: a plain English summary
  • This page helps you plan work.
  • It works out how long it takes to check your most important data.
  • You choose your own deadline.
Today 12 Oct 2026   Working days (England and Wales bank holidays removed) Policy published 27 May 2026
Scenario: UK government critical data assets. An effort model for the first data quality baseline under the data asset management policy. Devolved and other public bodies can use it to plan any baseline; see the scenario and legacy and modernisation.
–person-days across government
–full-time people needed for the whole window
–average days per CDA
–of CDAs baselined with the capacity you set

Your assumptions

An example. Enter the number of critical data assets you need to baseline.
Assumes each department builds its own rules, scoring and return.
Tier C takes whatever A and B leave. Default mix reflects the fragmented maturity found in the data management discovery workshops.
Fields or tables that carry the asset's purpose. Rule-writing, measuring and issue logging scale with this.
Stewards, analysts and engineers across departments and ALBs who can work on this.

Effort per CDA, by DQAP activity

Person-days for one CDA at the chosen depth and number of critical data items.

ActivityDQAP stepMain roleABC

Where the total goes

How the tiers are defined

A · Measured

Rules exist for the critical data items and checks run on a schedule. A DQAP or equivalent exists. The work is mapping existing results into the return.

B · Partial

Some rules or ad hoc checks. Known issues are logged somewhere. No agreed targets and no complete baseline across dimensions.

C · Unmeasured

No rules, no profiling, and often unresolved data access, ownership or sharing-agreement questions. Data access is the biggest source of delay.

What each CDA's quality entry should contain

The baseline template itself is not public, so this is the minimum set that the DQAP guide and issues framework support. Compare it with the real template to check the effort model fits.

FieldWhy it is neededSource in GOV.UK guidanceProportionate?
DQAP status (none, in progress, in place, equivalent)Policy requires a DQAP or equivalent for every CDADAM policy; DQAP guideYes
Named data owner and stewardAccountable for meaning, content and qualityIdentify and record CDAs; data ownership modelYes
Number of critical data items measuredShows baseline coverageDQAP step 1 (Data Criticality Matrix)Yes
Dimensions measured, with rule countSix DAMA UK dimensions; not all apply to every assetDQAP step 23 core
Baseline score per dimension (%) and date measuredThe benchmark for every later reportDQAP step 3Yes
Target per rule, from importance × impactTargets come from the combined score, not a flat percentageData quality issues frameworkLater
Open issues by priority (critical, high, medium, low)Drives funding and remediation orderIssues framework, priority scoreYes
Measurement frequency and method (automated or manual)Shows whether the baseline can be repeatedDQAP step 7Yes
Coverage and equality check for personal dataCompleteness can look high while groups are missing or misrecordedNot in the guidance (recommended addition)Add
Confidence in the baseline (high, medium, low)Separates measured results from estimatesNot in the guidance (recommended addition)Yes
Access route (open, restricted, on request, closed)Q-FAIR Accessible: users need to know how to get the dataNot in the guidance (Q-FAIR addition)Yes
Standards it conforms to, and shared identifiers usedQ-FAIR Interoperable: joins up only if formats and identifiers are sharedCDA metadata "conformsTo"; DAM interoperability requirementYes
LicenceQ-FAIR Reusable: no licence means no lawful reuseNot in the guidance (Q-FAIR addition)Yes
Provenance (where it comes from, how it is made)Q-FAIR Reusable: users judge fitness from origin and processingNot in the guidance (Q-FAIR addition)Later
Q-FAIR rating per area: Good, Improving or Attention requiredOne comparable picture across organisations, using the Geospatial Commission's scaleQ-FAIR benchmark (Geospatial Commission, 2022)Yes

Q-FAIR: rate one asset in two minutes

Q-FAIR adds Quality to the FAIR principles (Findable, Accessible, Interoperable, Reusable). The Geospatial Commission uses it to benchmark national geospatial data. Use the same three levels for any critical data asset. The toolkit fills these columns in the CDA return automatically from measured results and the asset record.

The DAM policy does not mention FAIR or Q-FAIR. Only the Geospatial Commission's six partner bodies are publicly known to have used Q-FAIR (2021 to 2022 benchmark). Ratings are an indicator, not an absolute measure.

Inclusion check built into the estimate

Each CDA carries a small allowance for an equality and coverage check. Standard completeness and validity scores can hide exclusion: a record can be complete while sex, ethnicity, disability or language fields are defaulted, or while people with no fixed address or without a digital footprint never appear at all. For CDAs holding personal data, the baseline should report:

  • Completeness of protected-characteristic and need fields, separately from overall completeness
  • Use of default or "unknown" values in those fields
  • Coverage against a reference population where one exists (for example, ONS mid-year estimates)
  • Whether quality differs between groups, such as match rates by age band or postcode type

Assumptions and open questions

Assumed

  • The first return asks for a first baseline, not a complete DQAP across all 7 steps.
  • Per-activity days come from typical DQ assessment work, not from GOV.UK. The guidance gives no time estimates.
  • Rule, measurement and issue effort scale with critical data items at a power of 0.7, because rules get reused across similar fields.
  • Departments do the work; GDS runs guidance, a helpdesk and aggregation (shown as a central line).

To confirm

  • The exact fields in the CDA baseline reporting template and when it reaches departments.
  • How many CDAs were actually submitted, and the split between departments and ALBs.
  • Whether "DQAP in progress" with a dated plan is acceptable for unmeasured (tier C) assets in the first return.
  • Whether CDAs shared by several organisations get one baseline (owner) or one per user.

Where the earlier AI Mode answers differ from GOV.UK

Earlier claimWhat the published guidance says
Flat targets such as 99.5% for critical fields, or sector bands such as 99.99%Targets follow importance × impact (score 1–16), giving ranges from 75% to 100%.
Data owner must be Senior Civil ServiceThe owner is "usually a senior individual". No grade is mandated.
Mandatory metadata: UUID, steward, update frequency, AI readiness tagsNamed fields include creator, created date, title, description, expires, supersededBy, temporal coverage, conformsTo and security classification. Update frequency, AI tags and UUIDs are not required.
Metadata "reported to GDS annually"Returns must be maintained and reviewed every 12 months. No fixed date is published.
Sector calibration matrix and a generated rule-engine fileNot part of the policy. Useful as an idea, but it should not be presented as GOV.UK guidance.

Connections to your other work

GDS DAM portal

The departmental return workspace and its Dataverse schema can take the quality fields above as new columns, and the assurance dashboard can show baseline coverage by organisation.

DQAP implementation playbook

Your Implementation Guide Playbook v1.0 already has a RACI and an implementation checklist that match the activity rows in this model.

National Data Library

Baseline quality scores make CDAs safer to reuse, and are the evidence the NDL needs to decide which assets to prioritise.

Sources