Capability playbook Level: Practitioner
Data cataloguing
What critical data do we hold, is it described well enough to find and reuse, and have we told GDS?
In brief
- Find the data other organisations depend on, and decide which of it is critical.
- Describe each critical data asset well enough for someone outside your team to find and judge it.
- Keep the descriptions in a catalogue, report them to GDS, and review them every year.
Easy read summary
- A data catalogue is a list of your data and what it is about.
- This page shows how to build one and what to record.
- It shows what you must send to the Government Digital Service.
Why it matters
Find the critical data assets, describe each one to the cross-government metadata standard, keep the descriptions in a catalogue that others can harvest, and report them to GDS every year.
Identifying, cataloguing, reporting and annually reviewing metadata are all 'must' requirements (DAM-R01 to DAM-R04).
Before you start
- A named coordinating team, led by your chief data officer
- Access to your data catalogue, information asset register and register of data sharing agreements
- Ownership confirmed, or under way, through the governance Assign recipe
What you will have at the end
- A designation log with reasons
- A catalogue record per asset
- An assured return to GDS
- An annual review record
What the policy requires
| ID | Strength | Requirement |
|---|---|---|
| DAM-R01 | must | Identify the data assets in scope: classified OFFICIAL (including handling markings such as 'personal'), meeting the critical data asset criteria, and inside your own data ownership accountabilities.V: Verified against the primary source |
| DAM-R02 | must | Identify and manage metadata about in-scope assets within your data catalogues.V: Verified against the primary source |
| DAM-R03 | must | Report in-scope assets to GDS. Departments provide metadata on their assets and coordinate and assure the returns of their ALBs.V: Verified against the primary source |
| DAM-R04 | must | Maintain metadata and review it every year.V: Verified against the primary source |
| DAM-R11 | should | Each critical data asset supports at least one of the seven purposes: public service delivery; legislative, legal or contractual requirement; defence, national security and resilience; policy development and evaluation; official statistics; public interest; fraud and error.V: Verified against the primary source |
| DAM-R12 | should | If you designate a particular distribution of a data set, designate its source data set as well.V: Verified against the primary source |
| DAM-R13 | should | Record the metadata properties set out in the metadata guidance, in plain English, with ISO 8601 dates and 'unknown' or 'not applicable' rather than blanks.V: Verified against the primary source |
| DAM-R16 | gap | The policy's introduction promises minimum requirements for interoperability, but the policy body does not state them. Treat the metadata guidance and the MEM as the current interoperability baseline and watch for guidance (open item OR-05).V: Verified against the primary source |
How it joins the other two
- Governance 3: Assign Cataloguing 4: Confirm ownership
The ownership register is the source for the owner and successor on the catalogue record. Record them once. (IL-01) - Cataloguing 4: Confirm ownership Quality 1: Identify critical data
The owner on the catalogue record is the owner who signs off DQAP targets and accepts risks. (IL-02) - Cataloguing 3: Test and designate Quality 1: Identify critical data
The asset boundary set at designation is the scope of the DQAP. No DQAP for fields outside the asset. (IL-03) - Quality 6: Report openly Cataloguing 5: Describe
Quality information is published on the catalogue record, so the record says how good the data is. (IL-04) - Governance 2: Frame Cataloguing 5: Describe
The metadata standard and the classification policy adopted in Frame are what records are checked against. (IL-06) - Cataloguing 8: Maintain and review Quality 8: Review every year
One annual review date per asset covers the record, the owner and the DQAP together. (IL-07) - Cataloguing 7: Report to GDS Governance 5: Assure
The GDS return is part of the governance evidence pack, assembled as you go. (IL-08)
Learn it
- The DAM Policy - what it asks of you Foundation 15 min
- Finding and designating critical data assets Practitioner 25 min
- Describing assets with metadata others can use Practitioner 30 min
- Cataloguing, harvesting and reporting to GDS Practitioner 20 min
- Running the three capabilities as one yearly cycle Advanced 20 min
- Inclusive data practice Foundation 20 min
- Embedding the policy in delivery and change Practitioner 30 min
- What makes a critical data asset AI-ready Foundation 20 min
- From FAIR to AI-ready metadata Practitioner 30 min
- Start from the question the data must answer Practitioner 20 min
- Connecting data to AI with linked data, knowledge graphs and MCP Advanced 35 min
- Leading data asset management - your first year Foundation 25 min
- Buying tools for data asset management without lock-in Practitioner 30 min
Frameworks, methodologies and standards
Frameworks, methodologies and standards that apply to this capability, grouped by kind. Each one links to its publisher. Where this portal applies one to a step, the step says so under How to do it. The publisher's page is the authority.
Legislation and statutory codes 3
- Register of information sharing agreements under the Digital Economy Act 2017S: Found by web search; the site blocked automated checking, so open it before relying on it
- Public Records Act 1958V: Verified against the primary source on 2026-11-05
- Data Protection Act 2018V: Verified against the primary source on 2026-11-05 Step 3
Standards 33
- Service StandardV: Verified against the primary source on 2026-11-05
- The Technology Code of PracticeV: Verified against the primary source on 2026-11-05
- Open standards for governmentV: Verified against the primary source on 2026-11-05
- Identifying property and street information (UPRN and USRN)V: Verified against the primary source on 2026-11-05
- Government Security ClassificationsV: Verified against the primary source on 2026-11-05 Step 3
- Writing to GOV.UK standards - style guidesV: Verified against the primary source on 2026-11-05
- UK GEMINI metadata standardV: Verified against the primary source on 2026-11-05 Step 5
- SDMXV: Verified against the primary source on 2026-11-05
- Data Catalog Vocabulary (DCAT) version 3V: Verified against the primary source on 2026-11-05 Step 5
- Data on the Web Best Practices: Data Quality VocabularyV: Verified against the primary source on 2026-11-05
- Government Functional Standard GovS 005: DigitalV: Verified against the primary source on 2026-11-05
- HL7 FHIR UK CoreS: Found by web search; the site blocked automated checking, so open it before relying on it
- SNOMED CTS: Found by web search; the site blocked automated checking, so open it before relying on it
- Using metadata to describe data assets in a data catalogueS: Found by web search; the site blocked automated checking, so open it before relying on it Step 2 Step 5 Step 7
- API technical and data standardsV: Verified against the primary source on 2026-11-05 Step 6
- ISO 15489-1:2016 Records management: concepts and principlesS: Found by web search; the site blocked automated checking, so open it before relying on it Step 8
- ISO 23081-1:2017 Metadata for records: principlesS: Found by web search; the site blocked automated checking, so open it before relying on it Step 5
- Open Standards principlesV: Verified against the primary source on 2026-11-05
- Technology Code of Practice point 4: make use of open standardsV: Verified against the primary source on 2026-11-05
- Metadata standards for sharing and publishing dataV: Verified against the primary source on 2026-11-05 Step 1 Step 5
- PROV-O: the PROV ontologyV: Verified against the primary source on 2026-11-05 Step 8
- SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05 Step 5
- CSV on the Web (CSVW) primerV: Verified against the primary source on 2026-11-05
- OpenLineageV: Verified against the primary source on 2026-11-05 Step 8
- Open Data Contract Standard (ODCS)V: Verified against the primary source on 2026-11-05
- Open Data Product Standard (ODPS)V: Verified against the primary source on 2026-11-05
- Egeria open metadata and governanceV: Verified against the primary source on 2026-11-05
- OpenAPI SpecificationV: Verified against the primary source on 2026-11-05 Step 6
- Model Context ProtocolV: Verified against the primary source on 2026-11-05
- ISO 8601-1:2019 Date and time: representations for information interchangeV: Verified against the primary source on 2026-11-05
- ISO 3166-1:2020 Country codesV: Verified against the primary source on 2026-11-05
- ISO 4217 Currency codesV: Verified against the primary source on 2026-11-05
- Shapes Constraint Language (SHACL)V: Verified against the primary source on 2026-11-05
Frameworks 3
- Data Maturity Assessment for Government: FrameworkV: Verified against the primary source on 2026-11-05
- SFIA 9: the global skills and competency framework for a digital worldV: Verified against the primary source on 2026-11-05
- Professional Knowledge and Skills Base (PKSB)V: Verified against the primary source on 2026-11-05
Methodologies and bodies of knowledge 7
- The GDS WayV: Verified against the primary source on 2026-11-05
- Service assessments and applying the Service StandardV: Verified against the primary source on 2026-11-05
- The Sourcing PlaybookV: Verified against the primary source on 2026-11-05
- The Digital, Data and Technology PlaybookV: Verified against the primary source on 2026-11-05
- DAMA-DMBOK: Data Management Body of KnowledgeV: Verified against the primary source on 2026-11-05
- DCAM: Data Management Capability Assessment ModelV: Verified against the primary source on 2026-11-05
- Develop your data and APIs using a reference architectureV: Verified against the primary source on 2026-11-05
Guidance and policy 47
- National Data Library (data.gov.uk)V: Verified against the primary source on 2026-11-05
- Making government datasets ready for AIV: Verified against the primary source on 2026-11-05 Step 6
- Report a vulnerability on a GOV.UK domain or subdomainV: Verified against the primary source on 2026-11-05
- Understanding accessibility requirements for public sector bodiesV: Verified against the primary source on 2026-11-05
- Model accessibility statementV: Verified against the primary source on 2026-11-05
- Open Government Licence v3.0V: Verified against the primary source on 2026-11-05 Step 6
- Best practice guidance and tools for managing geospatial dataV: Verified against the primary source on 2026-11-05
- How FAIR are the UK's national geospatial data assets?V: Verified against the primary source on 2026-11-05
- CDMP: Certified Data Management ProfessionalS: Found by web search; the site blocked automated checking, so open it before relying on it
- BCS Practitioner Certificate in Data Management EssentialsS: Found by web search; the site blocked automated checking, so open it before relying on it
- CILIP professional registrationS: Found by web search; the site blocked automated checking, so open it before relying on it
- Set up a commercial or digital and technology spend controls pipelineV: Verified against the primary source on 2026-11-05
- Data saves lives: reshaping health and social care with dataV: Verified against the primary source on 2026-11-05
- Retiring your serviceV: Verified against the primary source on 2026-11-05
- Managing legacy technologyV: Verified against the primary source on 2026-11-05
- A blueprint for modern digital governmentV: Verified against the primary source on 2026-11-05
- National Data LibraryV: Verified against the primary source on 2026-11-05 Step 1 Step 6
- Government professionsV: Verified against the primary source on 2026-11-05
- Government SkillsV: Verified against the primary source on 2026-11-05
- The Civil Service recommended curriculumV: Verified against the primary source on 2026-11-05
- Data skills for allV: Verified against the primary source on 2026-11-05
- Specialist skills from government professionsV: Verified against the primary source on 2026-11-05
- Government Campus prospectusV: Verified against the primary source on 2026-11-05
- Government Knowledge and Information Management ProfessionV: Verified against the primary source on 2026-11-05 Step 4
- Cloud security guidanceV: Verified against the primary source on 2026-11-05
- Government Cloud First policyV: Verified against the primary source on 2026-11-05
- Publish reference data for use across governmentV: Verified against the primary source on 2026-11-05
- G-Cloud 15 frameworkV: Verified against the primary source on 2026-11-05
- Manage information: guidance for governmentV: Verified against the primary source on 2026-11-05 Step 2
- Digital records transferV: Verified against the primary source on 2026-11-05
- Data Standards AuthorityV: Verified against the primary source on 2026-11-05 Step 1
- Technology Code of Practice point 11: define your purchasing strategyV: Verified against the primary source on 2026-11-05
- Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05
- Procurement Policy Note 07/15: open standards for technologyV: Verified against the primary source on 2026-11-05
- Data Standards Authority: Standards CatalogueV: Verified against the primary source on 2026-11-05 Step 7
- Find a TenderV: Verified against the primary source on 2026-11-05
- Digital Marketplace: search G-Cloud servicesV: Verified against the primary source on 2026-11-05
- A roadmap for modern digital government 2025 to 2030V: Verified against the primary source on 2026-11-05
- Service Manual: finding participants for user researchV: Verified against the primary source on 2026-11-05
- Service Manual: getting informed consent for user researchV: Verified against the primary source on 2026-11-05
- Service Manual: managing user research data and participant privacyV: Verified against the primary source on 2026-11-05
- Service Manual: running research sessions with disabled peopleV: Verified against the primary source on 2026-11-05
- data.gov.uk roadmapV: Verified against the primary source on 2026-11-05
- Names and codes listings (GSS geography codes)V: Verified against the primary source on 2026-11-05
- Harmonised standards and guidanceV: Verified against the primary source on 2026-11-05
- What each role does in a service teamV: Verified against the primary source on 2026-11-05 Step 4
- Advice on retentionS: Found by web search; the site blocked automated checking, so open it before relying on it Step 8
The full list, with why each matters, is on the Sources tab and in the rulebook on the policy page.
Eight stagesO: This playbook's own synthesis of published guidance
Eight stages from mobilising the team to the annual review. The sequence is this playbook's synthesis of the policy, the identification guidance and the metadata guidance; each step points to the requirement it meets. The internal Data Cataloguing Playbook (v2.6) is the fuller source and is not yet public (open item OR-01).
-
Step 1: Mobilise
Not startedHave a named lead and a coordinating team before identification starts.
How to do it
Do this
- The CDO (or most senior data official) leads and appoints a coordinating team or person.
- Nominate the lead policy coordinator for the Working Group.
- Agree how the department will coordinate and assure its ALBs' returns.
- Bring in data owners, IAOs, stewards, service owners, analysts and policy makers.
You will have
- Named lead and coordinator
- Contributor list
- ALB coordination plan
Check before you move on
- Coordinator nominated to the Working Group
- Every ALB has a named contact role
Frameworks and standards for this step: National Data LibraryV: Verified against the primary source on 2026-11-05; Data Standards AuthorityV: Verified against the primary source on 2026-11-05; Metadata standards for sharing and publishing dataV: Verified against the primary source on 2026-11-05
-
Step 2: Discover candidates
Not startedBuild a long list of data other organisations depend on.
How to do it
Do this
- Start from what you already have - data catalogues, information asset registers and registers of data sharing agreements.
- Find data you provide to, or acquire from, other organisations for an essential process or purpose.
- Prioritise assets supporting government missions and your services (including Top 75 services).
- Include high-reuse-value assets not yet shared.
You will have
- Candidate list with source of each entry
Check before you move on
- All three starting registers searched
- Both directions covered - data provided and data acquired
Meets: DAM-R01
Frameworks and standards for this step: Manage information: guidance for governmentV: Verified against the primary source on 2026-11-05; Using metadata to describe data assets in a data catalogueS: Found by web search; the site blocked automated checking, so open it before relying on it
-
Step 3: Test and designate
Not startedDecide which candidates are critical data assets, and draw each asset's boundary.
How to do it
Do this
- Apply the policy's scope tests - classified OFFICIAL, meets the critical data asset criteria, within your ownership accountabilities.
- Record which of the seven purposes each asset supports.
- Draw the boundary - only the fields needed for the cross-government purpose form the asset, not the whole system.
- If you designate a distribution, designate its source data set too.
- Record why each candidate was or was not designated.
You will have
- Designation decisions with reasons
- Asset boundary per asset
Check before you move on
- Every asset passes all scope tests
- Every asset has at least one purpose
- Source data sets designated where a distribution is
Meets: DAM-R01 DAM-R11 DAM-R12
Frameworks and standards for this step: Government Security ClassificationsV: Verified against the primary source on 2026-11-05; Data Protection Act 2018V: Verified against the primary source on 2026-11-05
-
Step 4: Confirm ownership
Not startedEvery designated asset has a named, accountable owner before it is described.
How to do it
Do this
- Confirm the owner (data owner or IAO) and steward for each asset with the governance Assign recipe.
- Use a shared team contact point for the asset, never a personal inbox.
- Record a successor so the metadata survives the owner leaving.
You will have
- Owner
- steward and contact point per asset
Check before you move on
- No asset goes forward without a named owner
- Contact point is a team route or form
Frameworks and standards for this step: What each role does in a service teamV: Verified against the primary source on 2026-11-05; Government Knowledge and Information Management ProfessionV: Verified against the primary source on 2026-11-05
-
Step 5: Describe
Not startedDescribe each asset well enough for someone outside your team to find, understand and judge it.
How to do it
Do this
- Record the properties in the metadata guidance (see the metadata tab).
- Write in plain English; expand acronyms; describe the data, and put usage warnings in usage notes.
- Use ISO 8601 dates, IANA media types, and 'unknown' or 'not applicable' rather than blanks.
- Model datasets, data services and distributions as the MEM and DCAT do.
- Add quality information from the DQAP (see data quality, stage 6).
You will have
- Catalogue record per asset
- conforming to the metadata guidance
Check before you move on
- Title and description are plain English
- Access rights, licence and security classification recorded
- Dates in ISO 8601
Frameworks and standards for this step: Data Catalog Vocabulary (DCAT) version 3V: Verified against the primary source on 2026-11-05; Using metadata to describe data assets in a data catalogueS: Found by web search; the site blocked automated checking, so open it before relying on it; Metadata standards for sharing and publishing dataV: Verified against the primary source on 2026-11-05; SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05; UK GEMINI metadata standardV: Verified against the primary source on 2026-11-05; ISO 23081-1:2017 Metadata for records: principlesS: Found by web search; the site blocked automated checking, so open it before relying on it
-
Step 6: Catalogue and expose
Not startedKeep the record in your catalogue in a form others can harvest.
How to do it
Do this
- Store each record in the organisation's catalogue, or an asset register where no catalogue exists yet.
- Expose records in DCAT so portals and the Discoverability Platform can harvest them.
- Make sure every link in a record works from outside your organisation.
- Choose catalogue tools against what any catalogue must expose, not a single vendor.
You will have
- Catalogue entries
- Machine-readable feed
Check before you move on
- Records are reachable by harvest, not only by people
- No record depends on an internal-only link
Frameworks and standards for this step: National Data LibraryV: Verified against the primary source on 2026-11-05; Open Government Licence v3.0V: Verified against the primary source on 2026-11-05; API technical and data standardsV: Verified against the primary source on 2026-11-05; OpenAPI SpecificationV: Verified against the primary source on 2026-11-05; Making government datasets ready for AIV: Verified against the primary source on 2026-11-05
-
Step 7: Report to GDS
Not startedSubmit an assured return on time.
How to do it
Do this
- Prepare the return from catalogue records, not by retyping them.
- Collate and assure ALB returns.
- Check the return before submission so moderation is about judgement, not formatting.
- Submit through the interim template, or the Discoverability Platform when it is live.
You will have
- Assured return
- ALB assurance record
Check before you move on
- Every asset in the return has an owner, a purpose and current metadata
- ALB returns assured by the department
Meets: DAM-R03
Frameworks and standards for this step: Using metadata to describe data assets in a data catalogueS: Found by web search; the site blocked automated checking, so open it before relying on it; Data Standards Authority: Standards CatalogueV: Verified against the primary source on 2026-11-05
-
Step 8: Maintain and review
Not startedRecords stay true.
How to do it
Do this
- Review every record at least every 12 months.
- Update records when the asset changes, and when the owner leaves.
- Retire assets that are no longer critical, with a reason.
- Feed findings into the governance Assure recipe.
You will have
- Annual review record
- Updated catalogue entries
Check before you move on
- Every record reviewed in the last 12 months
- Owner changes reflected within the month
Frameworks and standards for this step: PROV-O: the PROV ontologyV: Verified against the primary source on 2026-11-05; OpenLineageV: Verified against the primary source on 2026-11-05; Advice on retentionS: Found by web search; the site blocked automated checking, so open it before relying on it; ISO 15489-1:2016 Records management: concepts and principlesS: Found by web search; the site blocked automated checking, so open it before relying on it
Metadata properties
From Recording metadata to describe critical data assetsV: Verified against the primary source on 2026-11-05, mapped to the UK Cross-Government Metadata Exchange Model (xGov MEM)V: Verified against the primary source on 2026-11-05. The guidance does not give one mandatory or recommended column, so the obligation follows the wording of each section. "Listed" means it appears in the list of information to record without a stated strength.
| Property | Obligation | MEM slot | How to record it |
|---|---|---|---|
title | must | CataloguedResource.title | Plain English name; avoid acronyms and jargon |
alternativeTitle | optional | CataloguedResource.alternativeTitle | A short name to keep titles concise |
description | must | CataloguedResource.description | Describes the data; usage warnings go elsewhere |
identifier | should | CataloguedResource.identifier | Your own system's identifier or an opaque random one, not sequential |
creator | must | CataloguedResource.creator | The organisation that created the data, from a list of organisations |
dateCreated | should | CataloguedResource.created | ISO 8601 date or date-time |
temporalCoverage | listed | none in MEM (gap) | The period the data applies to |
conformsTo | listed | none in MEM (gap) | The standard or schema the data follows |
accessRights | should | CataloguedResource.accessRights | open, commercial or internal, with any handling caveat |
securityClassification | listed | CataloguedResource.securityClassification | Sensitivity level, OFFICIAL for assets in scope |
licence | should | CataloguedResource.licence | OGL URL for open data; the agreement for restricted data |
mediaType | should | Distribution.mediaType | IANA media type, such as text/csv |
expires | listed | none in MEM (gap) | How long this version is valid |
supersededBy | listed | none in MEM (gap) | The newer version that replaces this one |
See the data dictionary for each property's data type, format, how many values it takes, its controlled value list and an example. For the entities and relationships inside a data asset, use the entity and relationship list.
Proposed terms for the four properties missing from the MEMK: General knowledge, not checked against a source in this release
A proposal to close finding F-04, not an agreed standard (OR-06).
| Property | Proposed term | Note |
|---|---|---|
temporalCoverage | dcterms:temporal | DCAT uses dcterms:temporal with a dcterms:PeriodOfTime (dcat:startDate, dcat:endDate). |
conformsTo | dcterms:conformsTo | Already used by DCAT for a standard or schema a resource conforms to. |
expires | dcterms:valid | Dublin Core 'date (often a range) of validity'; record the end date. No DCAT-specific term exists. |
supersededBy | dcterms:isReplacedBy | Dublin Core relation for a resource that supplants this one; DCAT 3 versioning also offers dcat:previousVersion in the other direction. |
Write in plain English, expand acronyms, use ISO 8601 dates, and use "unknown" or "not applicable" rather than leaving a property blank. Make sure links work from outside your organisation.
Roles
- Chief data officer (CDO)V: Verified against the primary source
Implements the policy in the organisation and leads the identification exercise; sponsors governance. - Lead policy coordinator (COO)P: Practitioner material from cross-government playbooks not yet published
Coordinates identification, collates and assures the return (including ALBs), and is the link to the Working Group. - Data owner (OWN)V: Verified against the primary source
Senior leader accountable for the meaning, content, quality and management of the asset; approves changes and signs off targets and risks. - Information asset owner (IAO)V: Verified against the primary source
Accountable to the SIRO for protecting the whole information asset; may hold data owner duties under the IAO or hybrid option. - Data steward (STW)V: Verified against the primary source
Runs the asset day to day: policies and standards, access, quality processes and documentation such as the business glossary in the catalogue. - Data custodian (CUS)V: Verified against the primary source
Technical expert for the system holding the data: storage, access controls, auditable change and disposal. - Catalogue manager (CAT)O: This playbook's own synthesis of published guidance
Runs the organisation's catalogue, its metadata standard and its harvest feed. - Data users (USR)V: Verified against the primary source
Teams, services and other organisations that rely on the data; say what they need and report problems.
Who does what
| Step | CDO | COO | OWN | IAO | STW | CUS | CAT | USR |
|---|---|---|---|---|---|---|---|---|
| 1. Mobilise | A | R | C | C | C | |||
| 2. Discover candidates | A | R | C | C | R | C | ||
| 3. Test and designate | A | R | R | C | ||||
| 4. Confirm ownership | A | C | R | R | ||||
| 5. Describe | A | R | C | R | ||||
| 6. Catalogue and expose | A | C | R | R | ||||
| 7. Report to GDS | A | R | C | R | ||||
| 8. Maintain and review | C | A | R | R |
Templates
Blank structures to copy into your own tools.
Names and email addresses. Your own working copies can name the people who hold each role and give their work email addresses, handled under your organisation's data protection rules. Do not publish them: anything you put on GitHub or anywhere public should name roles only.
Each template says whether it is for business as usual, change programmes or both. Artefacts that only change programmes need, such as project governance and design authority inputs, are on the Change page.
Candidate and designation log (T-CAT-1)
Business as usual
- Candidate
- Found in (catalogue, IAR or sharing register)
- Provided to or acquired from
- Purpose (one or more of seven)
- Scope tests passed
- Designated (yes or no)
- Reason
- Decided by (role)
- Date
Critical data asset catalogue record (T-CAT-2)
Business as usual
- title
- alternativeTitle
- description
- identifier
- creator
- dateCreated
- temporalCoverage
- conformsTo
- accessRights
- securityClassification
- licence
- mediaType
- expires
- supersededBy
- Owner (role)
- Contact point (team or form)
- Purpose
- Last reviewed
- Next review
- Retention period
- Disposal action
Annual record review (T-CAT-3)
Business as usual
- Asset
- Date
- Still critical (and why)
- Owner and successor confirmed
- Metadata checked against the guidance
- Changes made
- Signed off by (role)
Entity and relationship list (T-CAT-4)
Business as usual and change
A plain list of the entities in a data asset and how they relate, so a relationship diagram can be drawn from it. The Data architecture and models supplement has a worked example and the diagram it produces.
- Entity
- Description
- Key attributes
- Related entity
- Relationship (for example, places)
- Cardinality (one to one, one to many or many to many)
- Optional or mandatory
- Source system
- Data dictionary link
Download this template (CSV) · Worked example: entity and relationship list (CSV) · relationship diagram (Mermaid, opens in Mermaid Live or diagrams.net) · All templates (CSV)
Measures
| Measure | Target |
|---|---|
| Designated assets with a catalogue record | 100% |
| Records reviewed in the last 12 months | 100% |
| Records with access rights, licence and classification | 100% |
| Records harvestable as DCAT | Rising each quarter |
Escalation
Cataloguing issues go up the governance escalation ladder.
Sector supplements for data cataloguing
The method on this page works for any critical data asset. Some kinds of data need more: extra rules, fields or safeguards. Those live in one place, the Sectors section, and are listed here with what each adds to data cataloguing.
Find which supplements apply to your asset
| Supplement | What it covers | What it adds to cataloguing |
|---|---|---|
| Health and care data | For critical data assets that hold patient-level or care records. Adds the health roles, duties and coding standards the core playbooks do not cover. | 4 extra catalogue fields and 2 identifiers |
| Adult and children's social care data | For assets built from council returns, such as adult social care client level data and children's social care census returns, where the source systems sit outside the policy's scope. | 3 extra catalogue fields and 1 identifiers |
| Geospatial and address data | For assets that hold addresses, coordinates or map geometry. Adds geospatial metadata, open identifiers and positional quality. | 4 extra catalogue fields and 3 identifiers |
| Official statistics and administrative sources | For assets used to produce official statistics. Joins the DQAP to quality assurance of administrative data, so quality is reported once for both purposes. | 2 extra catalogue fields and 1 identifiers |
| AI-ready data | For assets used, or likely to be used, for AI or automated decision support. Turns the GOV.UK AI-ready data guidance into checks at the annual review. | 4 extra catalogue fields |
| Justice, policing and national security | For assets in law enforcement, justice, defence or security settings, where only OFFICIAL assets are in scope and metadata itself may be sensitive. | 2 extra catalogue fields |
| Data about people | For any asset that holds records about individual people. Makes sure forms and rules let people describe themselves accurately. | 2 extra catalogue fields |
| Reference data and identifiers | For assets that depend on code lists and identifiers maintained by other organisations, such as area codes, organisation codes and company numbers. | 1 extra catalogue fields and 2 identifiers |
| Data architecture and models | For critical data assets whose structure others build on. Describes the entities, how they relate and which system is the authoritative source, and links them to the catalogue. | 2 extra catalogue fields |
| Devolved governments and local government | For assets that flow to or from the devolved governments or councils, which are not bound by the policy but often depend on it. | 2 extra catalogue fields |
| Environmental, sensor and time-series data | For monitoring and sensor data where readings arrive continuously and gaps, units and drift matter more than missing fields. | 2 extra catalogue fields |
Sources
- Data asset management policy in governmentV: Verified against the primary source on 2026-11-05: The mandate. Mandatory for UK government departments and ALBs; optional for public corporations; not for councils. (Published 27 May 2026; page metadata updated 9 September 2026)
- Data Catalog Vocabulary (DCAT) version 3K: General knowledge, not checked against a source in this release: The base vocabulary named in the metadata guidance and used by the MEM. (W3C Recommendation)
- Public Sector Data Quality Commons (portal and dqkit)P: Practitioner material from cross-government playbooks not yet published: The authoritative home of the data quality tools; this portal links to it and does not copy them. (Repository read 5 November 2026 (v2.0.0))
- Data on the Web Best Practices Data Quality Vocabulary (DQV)K: General knowledge, not checked against a source in this release: How to publish quality measurements alongside a catalogue record. (W3C Working Group Note)
- Identifying and recording critical data assetsV: Verified against the primary source on 2026-11-05: Criticality (provided or acquired), the seven purposes, how to identify, ownership and annual review. (Published and updated 16 April 2026)
- Data manual, data management section (data.gov.uk)V: Verified against the primary source on 2026-11-05: The official index of the guidance above, plus the data maturity hub and capability framework. (Read 5 November 2026)
- Recording metadata to describe critical data assetsV: Verified against the primary source on 2026-11-05: The metadata properties to record for each critical data asset, and formatting rules. (Published 16 April 2026; page metadata updated 9 September 2026)
- UK Cross-Government Metadata Exchange Model (xGov MEM)V: Verified against the primary source on 2026-11-05: LinkML model based on DCAT; classes Dataset, DataService, Distribution, CataloguedResource. Endorsed for implementation by the Data Standards Authority Steering Board. (Repository read 5 November 2026)
Related rulebooks
Service delivery and technology
- Service StandardV: Verified against the primary source on 2026-11-05GDS (GOV.UK Service Manual) · updated 2019-06-07The 14 points any government service is assessed against; used for this portal's self-assessment.
- The Technology Code of PracticeV: Verified against the primary source on 2026-11-05GDS · updated 2026-10-29Make things open, use open standards and make data reusable: the basis for catalogue and tool choices.
- The GDS WayV: Verified against the primary source on 2026-11-05GDSEngineering practice this portal follows, including using GitHub and publishing a vulnerability disclosure route.
- Open standards for governmentV: Verified against the primary source on 2026-11-05GDS · updated 2026-01-29The recommended open standards, including those for metadata, identifiers and data exchange.
- Identifying property and street information (UPRN and USRN)V: Verified against the primary source on 2026-11-05GDS · updated 2026-01-29The open standard for property and street identifiers; the basis for address quality rules.
- Service Manual: finding participants for user researchV: Verified against the primary source on 2026-11-05GDS (GOV.UK Service Manual) · updated 2026-11-05Participants must be actual or likely users, and research must include disabled people.
- Service Manual: getting informed consent for user researchV: Verified against the primary source on 2026-11-05GDS (GOV.UK Service Manual) · updated 2026-11-05Every participant gives informed consent, even colleagues in the same organisation.
- Service Manual: managing user research data and participant privacyV: Verified against the primary source on 2026-11-05GDS (GOV.UK Service Manual) · updated 2026-11-05How to collect, store and delete participants' personal data.
- Service Manual: running research sessions with disabled peopleV: Verified against the primary source on 2026-11-05GDS (GOV.UK Service Manual) · updated 2026-11-05Planning sessions that work for disabled participants and their assistive technology.
Data and AI
- National Data Library (data.gov.uk)V: Verified against the primary source on 2026-11-05GDSThe cross-government gateway to public data; the destination for harvested catalogue records.
- Making government datasets ready for AIV: Verified against the primary source on 2026-11-05GDS · updated 2026-01-19The criteria to assess at the annual review when data is used for AI.
- National Data LibraryV: Verified against the primary source on 2026-11-05Department for Science, Innovation and Technology · updated 2025-07-29Plans for making public sector data easier to find and use; catalogued critical assets are a natural input.
- Data Maturity Assessment for Government: FrameworkV: Verified against the primary source on 2026-11-05Central Digital and Data Office (developed with the ONS Data Quality Hub) · updated 2026-07-2310 topics, 6 themes and 5 levels for assessing data maturity. Licensed CC BY-NC-SA 4.0, so this portal links to it and does not copy its descriptions.
- Data Standards AuthorityV: Verified against the primary source on 2026-11-05Government Digital Service · updated 2026-11-05Sets and promotes the data standards organisations use to make data interoperable.
- Metadata standards for sharing and publishing dataV: Verified against the primary source on 2026-11-05Data Standards Authority · updated 2026-04-22The recommended metadata standards for sharing data within government and for publishing it.
- Data Standards Authority: Standards CatalogueV: Verified against the primary source on 2026-11-05Data Standards Authority · updated 2023-10-25The standards the Data Standards Authority has endorsed, with their status.
- data.gov.uk roadmapV: Verified against the primary source on 2026-11-05Government Digital Service · updated 2026-11-05A public Now, Next, Later roadmap with feedback routes; the model this portal's roadmap follows.
Security
- Government Security ClassificationsV: Verified against the primary source on 2026-11-05Cabinet Office · updated 2024-08-05Defines OFFICIAL and handling markings; the policy covers OFFICIAL assets only.
- Report a vulnerability on a GOV.UK domain or subdomainV: Verified against the primary source on 2026-11-05GDS · updated 2021-03-23The government vulnerability disclosure approach this portal's security.txt follows in spirit.
Accessibility and equality
- Understanding accessibility requirements for public sector bodiesV: Verified against the primary source on 2026-11-05GDS · updated 2024-09-30The accessibility regulations that apply to published records, statements and this portal.
- Model accessibility statementV: Verified against the primary source on 2026-11-05GDS · updated 2024-09-30Mandatory wording used in this portal's accessibility statement.
Content
- Writing to GOV.UK standards - style guidesV: Verified against the primary source on 2026-11-05GDSThe style this portal is written in (the old GOV.UK style guide address redirects here).
- Open Government Licence v3.0V: Verified against the primary source on 2026-11-05The National ArchivesThe licence for open government data and for this portal's content.
Geospatial
- Best practice guidance and tools for managing geospatial dataV: Verified against the primary source on 2026-11-05Geospatial Commission · updated 2022-05-26Guidance on managing and sharing geospatial data in a FAIR way.
- How FAIR are the UK's national geospatial data assets?V: Verified against the primary source on 2026-11-05Geospatial Commission · updated 2022-02-09The Q-FAIR assessment of national geospatial data assets.
- UK GEMINI metadata standardV: Verified against the primary source on 2026-11-05Association for Geographic InformationGeospatial metadata standard named in the GOV.UK metadata guidance; the AGI page says it has moved to GitHub.
- Names and codes listings (GSS geography codes)V: Verified against the primary source on 2026-11-05Office for National StatisticsDefinitive nine-character codes and names for UK statistical and administrative geographies.
Standards
- SDMXV: Verified against the primary source on 2026-11-05SDMX sponsorsStatistical data and metadata exchange standard.
- Data Catalog Vocabulary (DCAT) version 3V: Verified against the primary source on 2026-11-05W3CThe base vocabulary for catalogue records.
- Data on the Web Best Practices: Data Quality VocabularyV: Verified against the primary source on 2026-11-05W3CPublishing quality measurements with catalogue records.
- Using metadata to describe data assets in a data catalogueS: Found by web search; the site blocked automated checking, so open it before relying on itGOV.UK (recommended open standards) · updated 2023-09-28Recommends DCAT version 3 for describing data sets and data services in a catalogue, in support of the UK Cross-Government Metadata Exchange Model.
- PROV-O: the PROV ontologyV: Verified against the primary source on 2026-11-05W3CAn open vocabulary for provenance, used to describe where data came from and what was done to it.
- SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05W3CThe open format for glossaries, thesauri and taxonomies, so business terms can move between tools.
- CSV on the Web (CSVW) primerV: Verified against the primary source on 2026-11-05W3CDescribes the columns, types and constraints of CSV files, so files carry their own data dictionary.
- OpenLineageV: Verified against the primary source on 2026-11-05LF AI & Data Foundation · updated 2026-11-05An open specification for lineage events from running jobs, so lineage can be collected once and read by several tools.
- Open Data Contract Standard (ODCS)V: Verified against the primary source on 2026-11-05Bitol (LF AI & Data Foundation) · updated 2026-11-05An open format for data contracts, including schema, quality rules and service levels, readable by more than one tool.
- Open Data Product Standard (ODPS)V: Verified against the primary source on 2026-11-05Bitol (LF AI & Data Foundation) · updated 2026-11-05An open format describing data products, designed to reference data contracts.
- Egeria open metadata and governanceV: Verified against the primary source on 2026-11-05LF AI & Data Foundation · updated 2026-11-05An open source project for exchanging metadata between tools from different vendors; useful as a reference for open metadata types and connectors.
- OpenAPI SpecificationV: Verified against the primary source on 2026-11-05OpenAPI InitiativeThe open format for describing REST APIs; government API guidance recommends it.
- Model Context ProtocolV: Verified against the primary source on 2026-11-05Model Context Protocol project · updated 2026-11-05An open protocol for connecting AI assistants to tools and data, such as a catalogue.
- ISO 8601-1:2019 Date and time: representations for information interchangeV: Verified against the primary source on 2026-11-05ISOThe date format the metadata guidance asks for, for example 2026-11-12.
- ISO 3166-1:2020 Country codesV: Verified against the primary source on 2026-11-05ISOOne list of country codes across every service, so country fields can be joined.
- ISO 4217 Currency codesV: Verified against the primary source on 2026-11-05ISOThree-letter currency codes for spend and payments data.
- Shapes Constraint Language (SHACL)V: Verified against the primary source on 2026-11-05W3CRules that check linked data, such as catalogue records or vocabularies, before they are published.
Skills and professions
- CDMP: Certified Data Management ProfessionalS: Found by web search; the site blocked automated checking, so open it before relying on itDAMA InternationalDAMA International's certification for data management professionals, based on the DAMA-DMBOK.
- BCS Practitioner Certificate in Data Management EssentialsS: Found by web search; the site blocked automated checking, so open it before relying on itBCSA practitioner certificate in good practice for managing an organisation's data.
- CILIP professional registrationS: Found by web search; the site blocked automated checking, so open it before relying on itCILIPCertification, chartership and knowledge management chartership for information professionals, with yearly revalidation through CPD.
- Government professionsV: Verified against the primary source on 2026-11-05Government Skills · updated 2026-09-30The list of functional and specialist professions every civil servant can join.
- Government SkillsV: Verified against the primary source on 2026-11-05Cabinet Office · updated 2024-07-09Runs the Government Campus, the recommended curriculum and the Government Skills Campus learning platform.
- The Civil Service recommended curriculumV: Verified against the primary source on 2026-11-05Government Skills · updated 2025-05-29Recommended learning for all civil servants, searchable by subject.
- Data skills for allV: Verified against the primary source on 2026-11-05Government Skills · updated 2026-03-31Free data learning at awareness, working and practitioner levels.
- Specialist skills from government professionsV: Verified against the primary source on 2026-11-05Government Skills · updated 2024-08-23Strand 4 of the curriculum: how professions develop specialist skills.
- Government Campus prospectusV: Verified against the primary source on 2026-11-05Government Skills · updated 2026-11-05The online prospectus of courses by strand and subject, including data and analytics.
- Government Knowledge and Information Management ProfessionV: Verified against the primary source on 2026-11-05Government KIM Profession · updated 2025-06-20Information, records and knowledge management; publishes a skills framework and runs communities for records officers.
- SFIA 9: the global skills and competency framework for a digital worldV: Verified against the primary source on 2026-11-05SFIA Foundation · updated 2026-11-05Industry skills framework with data management and governance skills; widely used alongside the government framework.
- Professional Knowledge and Skills Base (PKSB)V: Verified against the primary source on 2026-11-05CILIP · updated 2026-11-05Knowledge and skills for information professionals, including metadata, taxonomy and records.
- DAMA-DMBOK: Data Management Body of KnowledgeV: Verified against the primary source on 2026-11-05DAMA International · updated 2026-11-05The most widely used body of knowledge for data management, with a professional certification (CDMP).
- DCAM: Data Management Capability Assessment ModelV: Verified against the primary source on 2026-11-05EDM Council · updated 2026-11-05An industry capability assessment model for data management, used here only to cross-check coverage.
Delivery, change and investment
- Government Functional Standard GovS 005: DigitalV: Verified against the primary source on 2026-11-05Government Digital Service · updated 2026-10-01The digital and data functional standard that the Data Maturity Assessment and data management practice sit under.
- Set up a commercial or digital and technology spend controls pipelineV: Verified against the primary source on 2026-11-05Government Digital Service · updated 2025-02-18Spend control is the point at which central teams see new digital and technology spend, and so a natural checkpoint for DAM evidence.
- Service assessments and applying the Service StandardV: Verified against the primary source on 2026-11-05GDS (GOV.UK Service Manual) · updated 2025-03-10Alpha, beta and live assessments; teams can show their critical data assets are catalogued, owned and quality-planned.
- Retiring your serviceV: Verified against the primary source on 2026-11-05GDS (GOV.UK Service Manual) · updated 2025-08-26What to do with users and their data when a service closes, including passing data to a new owner.
- Managing legacy technologyV: Verified against the primary source on 2026-11-05Government Digital Service · updated 2026-10-15Its second principle asks organisations to build a complete and accurate register of their data assets before migrating.
- The Sourcing PlaybookV: Verified against the primary source on 2026-11-05Cabinet Office · updated 2026-11-05Outsourcing decisions; contracts should say who owns the data, how metadata is delivered and how data comes back at exit.
- The Digital, Data and Technology PlaybookV: Verified against the primary source on 2026-11-05Cabinet Office · updated 2023-06-20Commercial guidance for buying digital, data and technology products and services.
- A blueprint for modern digital governmentV: Verified against the primary source on 2026-11-05Department for Science, Innovation and Technology · updated 2025-01-21The wider programme of digital reform that the DAM Policy supports.
- A roadmap for modern digital government 2025 to 2030V: Verified against the primary source on 2026-11-05Government Digital Service · updated 2026-10-09The government's action plan to 2030, with six priorities, from joining up public services to transparency and accountability.
Health and care
- HL7 FHIR UK CoreS: Found by web search; the site blocked automated checking, so open it before relying on itNHS England (NHS Standards Directory)API standards that use FHIR Release 4 to exchange health and care data consistently across England, Scotland, Wales and Northern Ireland. UK Core uses SNOMED CT, dm+d and the NHS Data Model and Dictionary for terminology.
- SNOMED CTS: Found by web search; the site blocked automated checking, so open it before relying on itNHS England (NHS Standards Directory)The information standard for clinical terminology (SCCI0034). Record it in conformsTo when an asset holds coded clinical data.
- Data saves lives: reshaping health and social care with dataV: Verified against the primary source on 2026-11-05Department of Health and Social Care · updated 2022-06-15DHSC's data strategy for health and social care in England, which commits to secure data environments as the default way to access NHS data for research and analysis.
Legislation
- Register of information sharing agreements under the Digital Economy Act 2017S: Found by web search; the site blocked automated checking, so open it before relying on itGOV.UK (data.gov.uk)The public register of agreements made under the public service delivery, debt, fraud and civil registration powers in Part 5 of the Act.
Cyber and security
- Cloud security guidanceV: Verified against the primary source on 2026-11-05National Cyber Security Centre · updated 2026-11-05How to choose and configure cloud services securely when critical data moves to them.
Technology and architecture
- Government Cloud First policyV: Verified against the primary source on 2026-11-05Government Digital Service · updated 2023-06-19Public cloud first for new or migrating services; data assets move with them.
- API technical and data standardsV: Verified against the primary source on 2026-11-05Government Digital Service · updated 2026-09-30How to build and document APIs, the data services through which many critical data assets are reached.
- Develop your data and APIs using a reference architectureV: Verified against the primary source on 2026-11-05Government Digital Service · updated 2021-03-22Reference architecture for data and APIs in government.
- Publish reference data for use across governmentV: Verified against the primary source on 2026-11-05Government Digital Service and Central Digital and Data Office · updated 2021-03-11How to publish reference data others can rely on, with a named owner, persistent identifiers, open formats and versioned change.
- Open Standards principlesV: Verified against the primary source on 2026-11-05Cabinet Office · updated 2018-04-05How government selects and uses open standards for software interoperability, data and document formats, including to avoid vendor lock-in.
- Technology Code of Practice point 4: make use of open standardsV: Verified against the primary source on 2026-11-05GDS · updated 2021-03-31What a plan must show about open standards and data to meet point 4, including avoiding lock-in.
- Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05GDS · updated 2026-09-03Types of lock-in, weighing value against portability, and including exit cost and time in business cases.
Commercial and procurement
- G-Cloud 15 frameworkV: Verified against the primary source on 2026-11-05Crown Commercial Service · updated 2026-11-05The main route for buying cloud hosting, software and support, including catalogue and data quality tools.
- Technology Code of Practice point 11: define your purchasing strategyV: Verified against the primary source on 2026-11-05GDS · updated 2026-09-03A purchasing strategy must show commercial and technology aspects and contractual limitations have been considered; it is checked in spend control.
- Procurement Policy Note 07/15: open standards for technologyV: Verified against the primary source on 2026-11-05Cabinet Office · updated 2023-01-31Tells buyers to specify open standards in technology procurements.
- Find a TenderV: Verified against the primary source on 2026-11-05Cabinet Office · updated 2026-11-05Where public procurement notices are published; search it for other bodies' catalogue, data quality and data platform requirements.
- Digital Marketplace: search G-Cloud servicesV: Verified against the primary source on 2026-11-05Crown Commercial Service · updated 2026-11-05Service descriptions on G-Cloud include standards, APIs and how buyers can get their data out at the end of a contract.
Records and information management
- Public Records Act 1958V: Verified against the primary source on 2026-11-05legislation.gov.uk · updated 2026-11-05The legal duty to manage, select and transfer public records, which includes many data assets.
- Manage information: guidance for governmentV: Verified against the primary source on 2026-11-05The National Archives · updated 2026-11-05Guidance on information and records management policy, processes, retention and digital records.
- Digital records transferV: Verified against the primary source on 2026-11-05The National Archives · updated 2026-11-05How digital records, including data, are selected and transferred to The National Archives.
- ISO 15489-1:2016 Records management: concepts and principlesS: Found by web search; the site blocked automated checking, so open it before relying on itInternational Organization for StandardizationThe international records management standard. Its site blocks automated checking.
- ISO 23081-1:2017 Metadata for records: principlesS: Found by web search; the site blocked automated checking, so open it before relying on itInternational Organization for StandardizationRecords metadata principles, the records-management counterpart to catalogue metadata. Its site blocks automated checking.
Statistics
- Harmonised standards and guidanceV: Verified against the primary source on 2026-11-05Government Analysis FunctionShared definitions and questions for topics such as age, sex, ethnicity and language, so statistics are comparable.
Practitioner material behind this playbook
- Data Cataloguing Playbook v2.6 and learner journey (Internal)
- Canonical shared glossary of the data playbook compendium (Internal draft)
Was this page useful? Tell us Tell us privately, without GitHub