Data Asset Management (DAM) capability playbooks
Have your sayHelpSite map

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?

  • 8 steps
  • 8 roles
  • 4 templates
  • 13 learning modules

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

Policy requirements met by data cataloguing
IDStrengthRequirement
DAM-R01mustIdentify 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-R02mustIdentify and manage metadata about in-scope assets within your data catalogues.V: Verified against the primary source
DAM-R03mustReport 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-R04mustMaintain metadata and review it every year.V: Verified against the primary source
DAM-R11shouldEach 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-R12shouldIf you designate a particular distribution of a data set, designate its source data set as well.V: Verified against the primary source
DAM-R13shouldRecord 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-R16gapThe 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

Learn it

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

Standards 33

Frameworks 3

Methodologies and bodies of knowledge 7

Guidance and policy 47

The full list, with why each matters, is on the Sources tab and in the rulebook on the policy page.

Page owner: the portal's service owner (a role) · Published 5 November 2026 · Last updated 2026-11-06 · Next review 2027-02-05

Was this page useful? Tell us Tell us privately, without GitHub