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

Playbooks Level: Practitioner

Delivery and change

How to make the DAM Policy stick: in the yearly business-as-usual cycle, and inside the programmes and projects that create, change and retire data assets.

  • 16 practices
  • 57 actions
  • 6 life cycle stages

In brief

  • Most critical data assets are created or replaced by change programmes, so controls belong in them.
  • Each item lists actions, evidence, roles and the rules behind it.
  • Tick actions as you go; progress stays in your browser.

What the policy leaves to you

The policy states its requirements briefly. These capabilities are needed to meet it but are only implied, or not stated at all. They are where organisations most often need help.

Implicit and inferred capabilities, and where this page helps
IDCapabilityIn the policyPortal coveragePractices
CR-02Data strategy and prioritisation by reuse valueImplicit: The text depends on it to meet an explicit requirement but does not name it as one.CoveredCH-05
CR-09Data quality issue managementImplicit: The text depends on it to meet an explicit requirement but does not name it as one.CoveredSee the capability model
CR-12Data architecture and data servicesImplicit: The text depends on it to meet an explicit requirement but does not name it as one.CoveredSee the capability model
CR-13Catalogue and quality toolingImplicit: The text depends on it to meet an explicit requirement but does not name it as one.CoveredSee the capability model
CR-14Reference data, master data and authoritative sourcesImplicit: The text depends on it to meet an explicit requirement but does not name it as one.PartialSee the capability model
CR-15Records, retention and disposalInferred: Not in the text. This portal's judgement from good practice and adjacent rulebooks.CoveredCH-04
CR-20Third-party and supplier dataImplicit: The text depends on it to meet an explicit requirement but does not name it as one.CoveredCH-06 CH-16
CR-21Data skills, capability and literacyImplicit: The text depends on it to meet an explicit requirement but does not name it as one.CoveredCH-09
CR-22Data culture and engagement with usersImplicit: The text depends on it to meet an explicit requirement but does not name it as one.CoveredCH-09
CR-23Maturity assessment and continuous improvementImplicit: The text depends on it to meet an explicit requirement but does not name it as one.CoveredCH-12
CR-25Integration with programmes, spend control and assuranceInferred: Not in the text. This portal's judgement from good practice and adjacent rulebooks.CoveredCH-02 CH-03
CR-26Legacy migration and decommissioningInferred: Not in the text. This portal's judgement from good practice and adjacent rulebooks.CoveredCH-04 CH-05 CH-14
CR-27Ownership transition and handover to business as usualImplicit: The text depends on it to meet an explicit requirement but does not name it as one.CoveredCH-08
CR-29Benefits realisation and evaluationInferred: Not in the text. This portal's judgement from good practice and adjacent rulebooks.CoveredCH-10
CR-30Equality and inclusion in dataInferred: Not in the text. This portal's judgement from good practice and adjacent rulebooks.CoveredCH-05
CR-31Cyber resilience and incident response for data assetsImplicit: The text depends on it to meet an explicit requirement but does not name it as one.CoveredCH-15
CR-32Avoiding future legacy: open standards, portability and exitInferred: Not in the text. This portal's judgement from good practice and adjacent rulebooks.CoveredCH-14 CH-16

DAM across the delivery life cycle

Stages follow the GOV.UK Service Manual phases and the project delivery standard. Use it as an overlay on your own programme plan.

  1. Strategy and business case

    • List the critical data assets the change will create, change, depend on or retire.
    • Cost ownership, cataloguing and quality work in the economic and financial cases.
    • Add data asset risks to the programme risk register.

    CH-01 CH-03 CH-05 CH-09 CH-12

  2. Discovery

    • Check the catalogue for assets that already meet the need before collecting new data.
    • Agree who will own each new or changed asset.

    CH-06 CH-13 CH-16

  3. Alpha

    • Design metadata and quality rules alongside the data model.
    • Run a data protection impact assessment where personal data is involved.

    CH-02 CH-14

  4. Beta and build

    • Catalogue new assets before go-live, with the core metadata.
    • Write and test the DQAP; reconcile migrated data against the source.

  5. Live and business as usual

    • Hand ownership, the DQAP and the runbook to named people in business as usual.
    • Report the asset in the next annual return.

    CH-07 CH-08 CH-10 CH-11 CH-15

  6. Migrate or retire

    • Start from the asset register; decide to migrate, archive or dispose of each asset.
    • Update or close catalogue entries and transfer ownership formally.

    CH-04

Programme roles with data responsibilities

Medium and large programmes bring in roles the DAM Policy and its guidance do not name. They decide most of what happens to critical data during change, so each needs explicit data responsibilities. This is this portal's assessment; the policy names only the chief data officer, data owners and the Chief Data Officer Council.O: This playbook's own synthesis of published guidance

Data responsibilities of programme and project roles
RoleData responsibilitiesStagesWorks withRules
Senior responsible owner
  • Make sure every critical asset in scope has an owner and a funded quality plan
  • Accept DAM checkpoints into the assurance plan
  • Sign off handover only when ownership, catalogue and DQAP transfer
Strategy and business case, Live and business as usualData owner Chief data officerRole of the senior responsible ownerV: Verified against the primary source on 2026-11-05; Implementing integrated assurance for major projectsV: Verified against the primary source on 2026-11-05
Programme or project manager
  • Put DAM activities in the plan, the risk register and gate criteria
  • Book data owners' time for decisions
  • Track data asset risks alongside other programme risks
Strategy and business case, Discovery, Beta and build, Live and business as usualData owner Lead policy coordinator Data stewardGovernment Functional Standard GovS 002: Project DeliveryV: Verified against the primary source on 2026-11-05
Service or product owner
  • Check the catalogue before collecting new data
  • Design validation from the quality rules
  • Show DAM evidence at service assessments
Discovery, Alpha, Beta and build, Live and business as usualData owner Catalogue manager Data quality lead or analystWhat each role does in a service teamV: 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
Design authority or solution architect
  • Approve data models against agreed standards and identifiers
  • Require documented schemas, open formats and an exit route
  • Make metadata harvestable from new platforms
Alpha, Beta and buildData custodian Catalogue manager Data stewardThe Technology Code of PracticeV: Verified against the primary source on 2026-11-05; API technical and data standardsV: Verified against the primary source on 2026-11-05; Open standards for governmentV: Verified against the primary source on 2026-11-05
Data migration lead
  • Profile quality before migration and reconcile after
  • Keep catalogue entries and ownership in step as assets move
  • Record lineage from old to new systems
Beta and build, Migrate or retireData owner Data quality lead or analyst Catalogue manager Data custodianManaging legacy technologyV: Verified against the primary source on 2026-11-05; Retiring your serviceV: Verified against the primary source on 2026-11-05
Commercial lead
  • Write data ownership, metadata, quality reporting and exit into contracts
  • Use model contract data and exit schedules
  • Track contract end dates against the assets they touch
Strategy and business case, Discovery, Migrate or retireData owner Data protection officer Lead policy coordinatorModel Services ContractV: Verified against the primary source on 2026-11-05; The Sourcing PlaybookV: Verified against the primary source on 2026-11-05; PPN 020: Guidance on data protection legislationV: Verified against the primary source on 2026-11-05
Programme office and assurance
  • Check DAM checkpoints at each gate
  • Report data asset readiness to the senior responsible owner
  • Feed lessons into the next programme
Strategy and business case, Beta and build, Live and business as usualLead policy coordinator Data governance boardImplementing integrated assurance for major projectsV: Verified against the primary source on 2026-11-05; National Infrastructure and Service Transformation AuthorityV: Verified against the primary source on 2026-11-05

These roles also appear on the roles list, the programme or project lead route and in the practices below.

Service blueprint for a programme

What happens to critical data at each stage, front stage and back stageO: This playbook's own synthesis of published guidance.

Service blueprint: data asset management across a programme
LaneStrategy and business caseDiscoveryAlphaBeta and buildLive and business as usualMigrate or retire
What the programme doesProgramme board agrees scope and business caseTeam explores needs and existing dataTeam designs and tests optionsTeam builds, migrates and goes liveService runs; programme closesOld systems are switched off
What users and boards seeBusiness case names critical assets and costs DAM workCatalogue search before new collectionData model and quality rules designed togetherNew assets catalogued; validation built from rulesQuality published to usersUsers told what happens to their data
Behind the scenesAsset list drawn from the catalogue; risks added to the registerContracts and data sharing options reviewedSchemas, identifiers and exit route approved by design authorityMigration profiled and reconciled; lineage recordedDQAP, runbook and contracts handed overAssets migrated, archived or disposed of under records rules
Data rolesData owners and the chief data officer agree prioritiesOwners confirmed for each asset in scopeStewards agree definitions and targetsOwners sign off quality against targetsBusiness-as-usual owner and steward namedCatalogue entries updated or closed
Support and assuranceAssurance plan includes DAM checkpointsCommercial lead brings data clauses into the route to marketDPIA started where personal data is involvedGate review checks DAM evidenceAsset included in the next annual returnRecords transferred where the Public Records Act applies

Practices

All practices0 of 57 done

Download every action as CSV to load into your own plan or tracker.

Stages, gates and assessments

Service assessments and gate reviews ask whether data management has been thought about, not for every template. Show that the critical data assets the service creates, changes or retires are known, owned, described, of known quality, protected and handed over, and keep the templates as your working evidence.

The Service Standard, service assessments, spend control and NISTA gate reviews are published elsewhere and linked here, not repeated. This section adds the critical data evidence for eachO: This playbook's own synthesis of published guidance. Assessors and reviewers judge against their own published criteria.

Four principles

  1. Stage

    Strategy and business case

    Gates and assessments
    • Spend control
    • Gate 0 strategic assessment (programmes)
    • Gate 1 business justification
    Service Standard points that touch critical data
    Before the Service Standard applies
    What reviewers will want to see about critical data
    • Which critical data assets the programme creates, changes, depends on or retires, and who owns them.
    • The cost of the data work, and of not doing it, in the business case.
    • Data risks on the programme register.
    O: This playbook's own synthesis of published guidance
    Evidence, and where it comes from here
    Common gaps
    • Data appears as an IT cost line with no named assets
    • No owner is consulted before the case is approved
    Read the published guidance
    Set up a commercial or digital and technology spend controls pipelineV: Verified against the primary source on 2026-11-05; Gate Review 0: Strategic AssessmentS: Found by web search; the site blocked automated checking, so open it before relying on it; The Green Book and accompanying guidanceV: Verified against the primary source on 2026-11-05
  2. Stage

    Discovery

    Gates and assessments
    • Discovery peer review, where your organisation runs one
    • Spend control
    Service Standard points that touch critical data
    point 1: Understand users and their needs, point 2: Solve a whole problem for users, point 3: Provide a joined up experience across all channels
    What reviewers will want to see about critical data
    • That the team searched the catalogue for existing data before planning to collect more.
    • Who holds the data the service needs today, inside and outside the organisation, and under what agreements.
    • The people the data describes, and what they would expect.
    O: This playbook's own synthesis of published guidance
    Evidence, and where it comes from here
    Common gaps
    • Data collected again because nobody looked for it
    • Supplier-held data discovered only at contract end
    Read the published guidance
    Service assessments and applying the Service StandardV: Verified against the primary source on 2026-11-05; Service StandardV: Verified against the primary source on 2026-11-05
  3. Stage

    Alpha

    Gates and assessments
    • Alpha service assessment
    • Gate 2 delivery strategy
    • Spend control
    Service Standard points that touch critical data
    point 2: Solve a whole problem for users, point 6: Have a multidisciplinary team, point 9: Create a secure service which protects users' privacy, point 11: Choose the right tools and technology, point 13: Use and contribute to open standards, common components and patterns
    What reviewers will want to see about critical data
    • A data model with entities, relationships, identifiers and authoritative sources.
    • Quality rules and targets agreed with owners before build.
    • Open standards and government identifiers chosen, and how data would leave the chosen tools.
    • Data roles in the team, and the protection and lawful basis for personal data.
    O: This playbook's own synthesis of published guidance
    Evidence, and where it comes from here
    Common gaps
    • Local code lists invented where national ones exist
    • A tool chosen before its export was tested
    Read the published guidance
    Service assessments and applying the Service StandardV: Verified against the primary source on 2026-11-05; Service StandardV: Verified against the primary source on 2026-11-05; Open standards for governmentV: Verified against the primary source on 2026-11-05; API technical and data standardsV: Verified against the primary source on 2026-11-05
  4. Stage

    Beta and build

    Gates and assessments
    • Beta service assessment
    • Gate 3 investment decision
    • Spend control
    Service Standard points that touch critical data
    point 5: Make sure everyone can use the service, point 9: Create a secure service which protects users' privacy, point 10: Define what success looks like and publish performance data, point 13: Use and contribute to open standards, common components and patterns, point 14: Operate a reliable service
    What reviewers will want to see about critical data
    • Catalogue records for every critical asset before go-live, owned and reported.
    • A quality baseline and a data quality action plan, with results the owner has seen.
    • Data protection, sharing agreements and security controls in place for the classification.
    • Migration reconciled and signed off, and the business-as-usual owner named.
    • Contracts that keep the data and metadata yours and let you leave.
    O: This playbook's own synthesis of published guidance
    Evidence, and where it comes from here
    Common gaps
    • Catalogue records written after go-live
    • Quality known only from test data
    • No named owner after the project
    Read the published guidance
    Service assessments and applying the Service StandardV: Verified against the primary source on 2026-11-05; Service StandardV: Verified against the primary source on 2026-11-05; Government Security ClassificationsV: Verified against the primary source on 2026-11-05; Data sharing: a code of practice - data sharing agreementsS: Found by web search; the site blocked automated checking, so open it before relying on it; Understanding accessibility requirements for public sector bodiesV: Verified against the primary source on 2026-11-05
  5. Stage

    Live and business as usual

    Gates and assessments
    • Live service assessment
    • Gate 4 readiness for service
    • Gate 5 operations review and benefits realisation
    Service Standard points that touch critical data
    point 8: Iterate and improve frequently, point 10: Define what success looks like and publish performance data, point 14: Operate a reliable service
    What reviewers will want to see about critical data
    • The yearly cycle running in business as usual: review, catalogue upkeep, quality checks and the return.
    • Handover complete, with budget, and checked after six months.
    • Benefits measured against the baseline, and data risks reviewed.
    • An exit test each year for tools holding critical data.
    O: This playbook's own synthesis of published guidance
    Evidence, and where it comes from here
    Common gaps
    • The project team leaves and nobody reviews the asset
    • Benefits claimed with no baseline
    Read the published guidance
    Service assessments and applying the Service StandardV: Verified against the primary source on 2026-11-05; Gate Review 5: Operations Review and Benefits RealisationS: Found by web search; the site blocked automated checking, so open it before relying on it; The Magenta BookV: Verified against the primary source on 2026-11-05
  6. Stage

    Migrate or retire

    Gates and assessments
    • Retirement decision
    • Gate 5 operations review, where it applies
    Service Standard points that touch critical data
    point 14: Operate a reliable service
    What reviewers will want to see about critical data
    • Every critical asset in the system migrated, archived or disposed of under the retention schedule.
    • Catalogue records marked retired, with what replaced them.
    • The owner's sign-off before switch-off.
    O: This playbook's own synthesis of published guidance
    Evidence, and where it comes from here
    Common gaps
    • Data needed for records or legal reasons lost at switch-off
    • Retired assets vanish from the catalogue
    Read the published guidance
    Retiring your serviceV: Verified against the primary source on 2026-11-05; Manage information: guidance for governmentV: Verified against the primary source on 2026-11-05; Managing legacy technologyV: Verified against the primary source on 2026-11-05

Download the evidence by stage as CSV.

These practices are this portal's synthesisO: This playbook's own synthesis of published guidance of the rulebook entries listed with each one. They add no new requirements; where they differ from your department's own delivery or assurance rules, follow your department.

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