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

Playbooks Level: Practitioner

Capability playbooks

Activities and templates for the capabilities beyond governance, cataloguing and quality that the DAM Policy depends on: strategy, tools, risk, suppliers, skills, culture, maturity, investment, assurance, legacy, handover, benefits and exit.

  • 13 capabilities
  • 40 activities
  • 16 templates
  • As of 2026-11-17

In brief

  • 13 capabilities, 40 activities and 16 templates.
  • Each capability has activities for before your first return, before your second, and for business as usual.
  • Each links to the same capability in the capability model, the knowledge areas, the data portals compass and the asset governance explorer.

Draft. Draft by this portal for review by the professions that own each capability. Not government guidance.

The DAM Policy names three capabilities, but meeting it rests on more: strategy, tools, risk, suppliers, skills, culture, maturity, investment, assurance, legacy, handover, benefits and exit. Each capability below has activities for before your first return, before your second, and for business as usual, with a template to start from.

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.

New to this, or leading it? Start with what to aim for in your first year, then come back to the capabilities you need.

Three stages

  1. Start: before your first returnWhat the DAM Policy needs now, so the return is complete and true.
  2. Build: before your second returnMakes the next return easier, and makes critical assets safer to reuse.
  3. Embed: business as usualKeeps the work going without a project, and prepares critical assets for AI and wider sharing.

All activities at a glance

Capability playbook activities by stage
CapabilityStart: before your first returnBuild: before your second returnEmbed: business as usual
Data strategy and prioritisation by reuse value
Business as usual and change
Rank critical assets by what they make possiblePut the ranking into the data strategyRe-rank every year with the return
Catalogue and quality tooling
Business as usual and change
Map the tools you have against what the policy needsRun a request for information with ready-made requirements
Prove it with your own data before you sign
Check before every renewal
Data risk management
Business as usual and change
Record the main risk to each critical assetSet risk appetite for dataReview data risks with the asset review
Third-party and supplier data
Business as usual and change
Find the critical assets held or supplied by third partiesPut data terms in every new contractTest the return of data before contracts end
Data skills, capability and literacy
Business as usual
Check what each data role needs to knowBuild data roles into jobs and objectivesKeep a community of practice going
Data culture and engagement with users
Business as usual
Find out who uses each critical asset and what gets in their wayTell people what changed because of their feedbackMake data work visible to leaders
Maturity assessment and continuous improvement
Business as usual
Take a baselineSet targets and an improvement planReassess every year
Investment, business cases and value
Change programmes
Name the critical assets in every business caseMake the case for investing in data assetsFund the yearly cycle in business as usual
Integration with programmes, spend control and assurance
Change programmes
Add data asset questions to existing checkpointsPut data checkpoints into the assurance planLearn from checkpoint findings
Legacy migration and decommissioning
Change programmes
List the critical assets in each legacy systemMigrate with reconciliationSwitch off safely
Ownership transition and handover to business as usual
Change programmes
Name the business-as-usual owner earlyHand over with a checklistCheck six months after handover
Benefits realisation and evaluation
Change programmes
Pick a few measures and record the baselineTrack and report the benefitsEvaluate after a year
Avoiding future legacy: open standards, portability and exit
Business as usual and change
Ask three questions of every new systemWrite and cost the exit planTest the exit every year

Governance, cataloguing and quality have their own playbooks. Data management areas are on Knowledge areas. The capability model shows all 32 capabilities and where each is covered.

Download every activity as CSV.

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