# Data Asset Management (DAM) capability playbooks (full text)

Version 1.10.1, as of 2026-11-06. Prototype. Not an official GOV.UK service or published GDS guidance. Where it repeats GDS guidance, the GOV.UK page is the authority.

## DAM Policy requirements

- 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R01]
- DAM-R02 (must): Identify and manage metadata about in-scope assets within your data catalogues. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R02]
- DAM-R03 (must): Report in-scope assets to GDS. Departments provide metadata on their assets and coordinate and assure the returns of their ALBs. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R03]
- DAM-R04 (must): Maintain metadata and review it every year. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R04]
- DAM-R05 (must): Every identified asset has a named data owner, accountable for decisions about the data. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R05]
- DAM-R06 (must): Every identified asset has a data quality action plan (DQAP) or an equivalent mechanism for managing its quality. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R06]
- DAM-R07 (should): Where you already manage the quality of critical data, review those processes to confirm they cover every step of the DQAP implementation guide. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R07]
- DAM-R08 (must): The chief data officer of each in-scope organisation implements the policy; the Chief Data Officer Council oversees implementation; the minister writes to ministers each year on progress. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R08]
- DAM-R09 (must): Choose an ownership option (keep the IAO model, adopt the data ownership model, or a hybrid) and still meet the mandatory IAO actions, with governance covering accountability, reporting lines, assurance and data quality. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R09]
- DAM-R10 (must): When a data owner leaves, tell the coordinating team, have a successor ready and give the successor's details so the metadata can be updated. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R10]
- 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R11]
- DAM-R12 (should): If you designate a particular distribution of a data set, designate its source data set as well. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R12]
- 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R13]
- DAM-R14 (should): The chief data officer, or the most senior data official, leads identification and appoints a coordinating team or person, drawing in owners, IAOs, stewards, service owners, analysts and policy makers. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R14]
- DAM-R15 (method): Prioritise quality issues with the issues framework: importance of purpose times impact sets the target range; the band below target sets priority. Its resolution timescales (Critical immediately; High, Medium and Low within 1, 3 and 6 measurements) are given as an example. [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R15]
- 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). [https://cyberdudeuk.github.io/dam-capability-playbooks/dam.html#DAM-R16]

## Data governance

Put the authority, roles and routines in place so that every critical data asset has a named, active owner, decisions are made and recorded, and the organisation can evidence its DAM Policy adoption.

1. Mandate: Establish the authority everything else operates under. Confirm the sponsor (the CDO, SIRO or equivalent) who will chair or co-sign the charter. Draft a one-page charter covering purpose, scope, authority and review cadence. State which data, systems and decisions are in scope, and any exclusions. Start narrow, with critical data assets. Route the charter for approval and record the decision and its date. Publish it to every stakeholder found during scoping. [https://cyberdudeuk.github.io/dam-capability-playbooks/governance.html#gov-mandate]
2. Frame: Assemble a proportionate rulebook to make decisions against. List every data policy and standard already in force, however informal. Compare it with the core areas - governance, classification and handling, quality, retention and disposal, access and sharing, metadata, master and reference data, and ethics including AI use. Draft or adopt what is missing, in proportion to the risk. Reuse cross-government guidance before writing your own. Give every policy a named owner (a role) and a review date. Register each policy and make it findable, ideally in the data catalogue. [https://cyberdudeuk.github.io/dam-capability-playbooks/governance.html#gov-frame]
3. Assign: Put a named, accountable owner and an active steward against every critical data asset. Choose your ownership option - IAO model, data ownership model or hybrid - and record the decision. For each critical data asset, propose an owner of matching seniority (SCS for large or complex assets; Grade 6 or 7 for smaller ones), a steward and a custodian. Agree decision rights using the RACI below and any delegated thresholds. Brief role holders and record training (Data Owner and Steward training). Record owner, steward, custodian, effective date and a named successor in the ownership register and the catalogue record. [https://cyberdudeuk.github.io/dam-capability-playbooks/governance.html#gov-assign]
4. Operate: Make governance visible day to day. Set the board's cadence (monthly, at least quarterly) and publish the calendar. Keep a decision log - what, who, why, when and the review trigger. Keep an issue and risk log, with quality issues coming in from the DQAP. Log every deviation from policy as an exception with an owner and an expiry date. Escalate anything unresolved up the ladder. [https://cyberdudeuk.github.io/dam-capability-playbooks/governance.html#gov-operate]
5. Assure: Prove it works and feed the lessons back into the mandate. Re-run the data maturity self-assessment. Compile measures from the live registers - owner coverage, review currency, DQAP coverage, exceptions. Map evidence to the GDS annual return as you go, not at the deadline. Have someone outside the board check the evidence before submission. Submit, then log lessons back into Mandate. [https://cyberdudeuk.github.io/dam-capability-playbooks/governance.html#gov-assure]

## Data cataloguing

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.

1. Mobilise: Have a named lead and a coordinating team before identification starts. 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/cataloguing.html#cat-mobilise]
2. Discover candidates: Build a long list of data other organisations depend on. 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/cataloguing.html#cat-discover]
3. Test and designate: Decide which candidates are critical data assets, and draw each asset's boundary. 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/cataloguing.html#cat-designate]
4. Confirm ownership: Every designated asset has a named, accountable owner before it is described. 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/cataloguing.html#cat-own]
5. Describe: Describe each asset well enough for someone outside your team to find, understand and judge it. 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). [https://cyberdudeuk.github.io/dam-capability-playbooks/cataloguing.html#cat-describe]
6. Catalogue and expose: Keep the record in your catalogue in a form others can harvest. 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/cataloguing.html#cat-publish]
7. Report to GDS: Submit an assured return on time. 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/cataloguing.html#cat-report]
8. Maintain and review: Records stay true. 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/cataloguing.html#cat-maintain]

## Data quality

Know, prove and improve the quality of each critical data asset through a data quality action plan (DQAP), scored with the government issues framework, reported openly and repeated every cycle.

1. Identify critical data: Know which data items in each asset matter most. Name the 5 to 15 data items that drive the most important decisions (critical data elements). Record who uses the data, for what, and who or what it describes. Log known issues in the DQAP issues log. [https://cyberdudeuk.github.io/dam-capability-playbooks/quality.html#dq-identify]
2. Define rules and targets: Turn 'good enough' into rules a computer can test. Choose the dimensions that matter - completeness, uniqueness, consistency, timeliness, validity, accuracy. Write each rule in plain English first, then as a testable rule. Set targets from the issues framework range for importance times impact. Store rules as files (a data contract) so they survive a change of tool or supplier. [https://cyberdudeuk.github.io/dam-capability-playbooks/quality.html#dq-define]
3. Measure a baseline: Know where you are today. Profile the data and run every rule; record the date and data version. Log every failure as an issue with its size and who it affects. Break results down by group where you lawfully can. [https://cyberdudeuk.github.io/dam-capability-playbooks/quality.html#dq-baseline]
4. Prioritise and set goals: Fix what hurts most first. Score each issue with the issues framework. Resolve Critical immediately, High within one cycle, Medium within three and Low within six. Agree the order with the owner and record accepted risks with a review date. [https://cyberdudeuk.github.io/dam-capability-playbooks/quality.html#dq-prioritise]
5. Fix causes at source: Stop problems coming back. Ask why until you reach the cause - people, process, system, supplier or standard. Prefer prevention at entry over downstream cleaning. Put supplier duties and measures into contracts. Re-run the rule to prove the fix worked. [https://cyberdudeuk.github.io/dam-capability-playbooks/quality.html#dq-improve]
6. Report openly: Users know how good the data is and what it should not be used for. Update a plain-English data quality statement - scores, trends, known issues and unsuitable uses. Publish quality information with the catalogue record (W3C DQV) so it travels with the asset. Report the status of all assets to the governance board; quality issues enter the issue and risk log. [https://cyberdudeuk.github.io/dam-capability-playbooks/quality.html#dq-report]
7. Repeat and sustain: Quality stays good without heroics. Run checks automatically on each load or on a fixed cycle. Track trends and alert when a rule drops below target. Escalate with the agreed thresholds. Keep rules, results and the plan in version control. [https://cyberdudeuk.github.io/dam-capability-playbooks/quality.html#dq-sustain]
8. Review every year: Rules and targets still match what users need. Review rules, targets and the plan with the owner and users. Add rules for new uses, including AI. Retire rules that no longer matter; raise targets that are now easy. [https://cyberdudeuk.github.io/dam-capability-playbooks/quality.html#dq-review]

## Capability model

- CR-01 Accountable leadership and policy oversight (Explicit): Each organisation's chief data officer is responsible for implementing the policy; the Chief Data Officer Council oversees it. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-01]
- CR-02 Data strategy and prioritisation by reuse value (Implicit): The policy expects organisations to start with assets of proven reuse value, which needs a way to rank assets that the policy does not spell out. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-02]
- CR-03 Central reporting, assurance and arm's length body coordination (Explicit): Departments report their assets to GDS and coordinate and assure the returns of their arm's length bodies. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-03]
- CR-04 Performance measurement and annual review (Explicit): Returns must be maintained and reviewed every year; the guidance adds measures for ownership and quality. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-04]
- CR-05 Identify and scope critical data assets (Explicit): Only assets classified OFFICIAL are in scope, and the critical-asset guidance defines which assets count. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-05]
- CR-06 Data cataloguing and metadata management (Explicit): Metadata about in-scope assets must be held in a data catalogue; the quality guide also assumes a catalogue exists. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-06]
- CR-07 Data ownership and stewardship (Explicit): Every identified asset must have a named data owner, as set out in the data ownership model. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-07]
- CR-08 Data quality management through action plans (Explicit): Every identified asset must have a data quality action plan or an equivalent that covers all 7 steps. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-08]
- CR-09 Data quality issue management (Implicit): The policy points to the issues framework to support resource decisions; logging and prioritising issues is how plans turn into action. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-09]
- CR-10 Data life cycle management (Explicit): The policy sets out life cycle controls; the ownership model makes life cycle management a principle. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-10]
- CR-11 Interoperability, data standards and identifiers (Explicit): The policy sets minimum requirements for interoperability; standards and shared identifiers are how they are met. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-11]
- CR-12 Data architecture and data services (Implicit): A data asset includes the data services (such as APIs) used to reach it, so someone must design and run those services. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-12]
- CR-13 Catalogue and quality tooling (Implicit): Catalogues and automated quality checks need platforms; GDS will build a central discovery service. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-13]
- CR-14 Reference data, master data and authoritative sources (Implicit): Reducing duplicate collection depends on agreeing which source is authoritative; the policy states the aim, the ownership model the principle. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-14]
- CR-15 Records, retention and disposal (Inferred): Not mentioned in the policy, but an asset's life cycle ends in retention, transfer or disposal, which records law governs. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-15]
- CR-16 Security classification and protective controls (Explicit): Scope depends on classification (OFFICIAL only), so classification must be right before an asset is recorded. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-16]
- CR-17 Data protection and lawful sharing (Explicit): The policy keeps every legal and data protection obligation in place and does not force sharing. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-17]
- CR-18 AI readiness and data and AI ethics (Explicit): The policy names AI readiness as a reason for quality plans; ethics is not named, so it is inferred from the AI guidance. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-18]
- CR-19 Data risk management (Explicit): The policy cites risk controls and understanding cross-public sector dependencies to manage risk; how is left to each organisation. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-19]
- CR-20 Third-party and supplier data (Implicit): Many critical assets are held or processed by suppliers; ownership, metadata and quality duties must reach into contracts. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-20]
- CR-21 Data skills, capability and literacy (Implicit): The policy assigns new responsibilities; the guidance lists the skills and training those people need. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-21]
- CR-22 Data culture and engagement with users (Implicit): Ownership and quality only last where people value data and know who uses it. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-22]
- CR-23 Maturity assessment and continuous improvement (Implicit): The policy recognises different levels of data maturity; the government maturity framework is the shared way to measure them. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-23]
- CR-24 Investment, business cases and value (Explicit): The policy says data must be properly valued and invested in; funding comes through business cases. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-24]
- CR-25 Integration with programmes, spend control and assurance (Inferred): Not in the policy text. Most new and replacement data assets arrive through change programmes, so the controls must be built into them. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-25]
- CR-26 Legacy migration and decommissioning (Inferred): Not in the policy. The legacy guidance makes a data asset register its second principle; migrations are where quality is most at risk. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-26]
- CR-27 Ownership transition and handover to business as usual (Implicit): A named owner must survive staff moves and the end of the project that created the asset. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-27]
- CR-28 Cross-boundary collaboration (Explicit): Departments coordinate with their arm's length bodies, and data passed to devolved administrations can stay in scope. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-28]
- CR-29 Benefits realisation and evaluation (Inferred): The policy lists benefits such as less duplication and cleansing; showing they happened needs an evaluation plan. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-29]
- CR-30 Equality and inclusion in data (Inferred): Not in the policy, but the equality duty applies to decisions about which assets to fix first, and poor data about some groups widens inequality. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-30]
- CR-31 Cyber resilience and incident response for data assets (Implicit): The policy scopes assets by classification and the ownership model makes security a principle, but neither says how to protect a critical asset from, or recover it after, a cyber incident. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-31]
- CR-32 Avoiding future legacy: open standards, portability and exit (Inferred): Not in the policy. Without open formats, documented schemas and exit terms, every new system becomes the next concentration of hard-to-reach data. [https://cyberdudeuk.github.io/dam-capability-playbooks/capability-model.html#CR-32]

## Delivery and change practices

- CH-01 Put data assets in the business case: The policy says data must be valued and invested in; business cases are where that money is decided. Actions: Name each critical data asset in scope of the change in the strategic case. Cost owner, steward and catalogue effort and DQAP remediation in the financial case. Count avoided duplicate collection and cleansing as benefits in the economic case. Name the data owner in the management case. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-01]
- CH-02 Use spend control and service assessments as checkpoints: Spend control and service assessments already stop work that is not ready; adding DAM evidence costs little. Actions: Add three questions to internal spend control: which assets, who owns them, are they catalogued. At alpha, show the planned metadata and quality rules; at beta, the catalogue entry and DQAP. Show the panel that data was considered: who owns each asset, how it is described and quality-planned, the DPIA, and that data professionals and users were involved. You do not need to hand in every template; keep them as your team's working record. Record the answers so the next return reuses them. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-02]
- CH-03 Write DAM into programme assurance: Large programmes have integrated assurance plans; DAM checks in them are reviewed with everything else. Actions: Add DAM checkpoints to the integrated assurance and approval plan. Ask reviewers to check asset ownership, catalogue entries and quality plans at each gate. Give the senior responsible owner a single line on data asset readiness in highlight reports. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-03]
- CH-04 Plan legacy exits from the asset register: Legacy systems hold large concentrations of hard-to-reach data; the legacy guidance asks for an asset register first. Actions: Build or update the register of data assets held in the legacy system. Profile quality before migration and set reconciliation rules for counts, totals and keys. Decide for each asset: migrate, archive under records rules, or dispose. Keep the catalogue and ownership in step as each asset moves. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-04]
- CH-05 Target legacy where it blocks outcomes and widens inequalities: Where poor or locked-in data delays access to services, the people most affected are often those already disadvantaged. Actions: Score each critical asset on legacy risk, quality, reuse value and impact on outcomes. Check whether gaps or errors fall harder on some groups, using the equality duty. Fund fixes first where risk, value and inequality overlap. Report the choice and its reasons to the data governance board. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-05]
- CH-06 Build DAM into contracts: Suppliers often hold or process critical assets; without contract terms the owner cannot meet the policy. Actions: State who owns the data and its metadata. Require metadata in an agreed format and quality reporting against the DQAP. Set data return, format and deletion terms for exit. Include data protection terms from the procurement policy note. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-06]
- CH-07 Manage data asset risk on the same registers: The policy relies on risk controls; separate data risk lists are easy to ignore. Actions: Record risks to critical assets on the corporate or programme register. Link each to the asset, its owner and the senior information risk owner. Review alongside DQAP results each quarter. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-07]
- CH-08 Hand over to business as usual: Assets created by projects lose their owner when the project closes unless handover is planned. Actions: Confirm a named business-as-usual owner and steward before the project closes. Hand over the DQAP, quality rules, runbook and open issues. Use the ownership model's transition steps and set the next review date. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-08]
- CH-09 Plan people change, not just process change: New duties fail when people are not told, trained, given time or recognised for them. Actions: Assess who is affected: owners, stewards, custodians, analysts, suppliers. Put data duties into role descriptions and objectives. Train each role at the right level and give stewards protected time. Communicate why the policy matters in terms of services and people, not compliance. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-09]
- CH-10 Show the benefits: Continued funding depends on evidence that the work changed something. Actions: Agree a few measures before starting, such as reuse requests met, duplicate collections stopped or time spent cleansing. Take a baseline, then measure each year with the return. Use proportionate evaluation methods. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-10]
- CH-11 Keep the yearly cycle running in business as usual: The policy is annual; without a calendar it becomes a scramble before each return. Actions: Set fixed dates for asset review, metadata updates, DQAP review and the board. Track each owner's actions between returns. Feed lessons into the next year's priorities. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-11]
- CH-12 Assess maturity and set a target: A shared maturity measure turns the policy into a plan that can be resourced and tracked. Actions: Run the government data maturity assessment or use the self-assessment here as a first pass. Set a target level for each DAM strand with dates. Repeat every one to two years. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-12]
- CH-13 Share and reuse safely across organisations: Reuse is the point of the policy, but it never removes legal duties or forces sharing. Actions: Check the catalogue for reusable assets before collecting new data. Use the sharing framework and code for agreements. Record sharing arrangements against the asset in the catalogue. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-13]
- CH-14 Design out future legacy and lock-in: Systems bought or built today become tomorrow's legacy unless their data can be moved out without loss or delay. Actions: Require data in open, documented formats with a published schema. Ask suppliers to show how a full export with metadata works before you sign. Prefer open standards and APIs that follow the government API standards. Record each system's exit route against its assets in the catalogue. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-14]
- CH-15 Prepare for a cyber incident affecting a critical asset: A ransomware attack or breach can corrupt or expose a critical asset; quality plans and owners must be ready. Actions: Mark critical data assets in the incident response plan and asset inventory. Agree recovery point and recovery time with each data owner. Test restoring an asset and check its quality afterwards against the DQAP rules. Agree who tells data users when an asset may be affected. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-15]
- CH-16 Use the buying routes and contract terms that protect data: Most catalogue, quality and platform tools are bought; the route and terms decide who controls the data. Actions: Buy through an established framework where one fits, such as G-Cloud. Use the model contract schedules for data, security and exit rather than supplier terms. Make metadata delivery, quality reporting and data return measurable obligations with service credits. Publish transparency information as the Procurement Act requires. [https://cyberdudeuk.github.io/dam-capability-playbooks/change.html#CH-16]

## Sector supplements

- 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-HLT]
- 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-SOC]
- Geospatial and address data: For assets that hold addresses, coordinates or map geometry. Adds geospatial metadata, open identifiers and positional quality. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-GEO]
- 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-STA]
- Data sharing and legal gateways: For every critical data asset that includes personal data, because critical data assets are defined by being shared. Adds a legal gateway record to the governance and catalogue records. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-SHR]
- 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-AI]
- Fraud and error: For assets used to detect fraud or error, where identity matching quality decides who is flagged. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-FRD]
- 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-JUS]
- Data about people: For any asset that holds records about individual people. Makes sure forms and rules let people describe themselves accurately. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-PER]
- 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-REF]
- Records, retention and disposal: For every critical data asset that must be kept, archived or destroyed on a schedule. Joins data asset management to records management. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-REC]
- 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-ARC]
- 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-DEV]
- 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. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-ENV]
- Pupil and learner data: For assets about pupils and learners, which are long-lived and linked across schools, colleges and nations. [https://cyberdudeuk.github.io/dam-capability-playbooks/sectors.html#SUP-EDU]

## Glossary

- Data asset: One or more data sets plus, where relevant, the data services used to access them.
- Data set: A structured collection of data selected and organised for a defined outcome or need. It can be a subset of a larger system.
- Data service: A controlled means of accessing one or more data sets, such as an API or secure access mechanism.
- Distribution: A specific representation of a data set, for example a CSV file or a feed.
- Critical data asset: A data asset shared across government where losing access could stop an organisation from fulfilling important functions. 'Essential shared data asset' is the older term it replaced.
- Provided data: Data one organisation gives to another to support an essential process or purpose the receiver is responsible for.
- Acquired data: Data one organisation obtains from another to support an essential process or purpose it is responsible for.
- Purpose: One of the seven reasons a critical data asset matters, such as public service delivery or official statistics. Each asset supports at least one.
- Scope tests: The conditions an asset must meet to be in scope of the policy: classified OFFICIAL, critical, and within the provider's ownership accountabilities.
- Metadata: Information that describes a data asset so it can be found, understood, validated, reused and shared.
- Data catalogue: A managed collection of metadata records that helps people and systems find, understand and reuse data assets. It holds descriptions, not the data.
- DCAT: The W3C vocabulary for describing data sets and data services in catalogues, so catalogues can be harvested and searched together.
- Metadata Exchange Model: The UK cross-government model, based on DCAT, for the metadata exchanged about data assets.
- Discoverability Platform: The GDS service being scoped to link to departments' own catalogues and make critical data asset metadata discoverable across government.
- Return: An organisation's report of its in-scope assets and their metadata to GDS, assured by the department for its ALBs.
- Data owner: A senior leader accountable for the meaning, content, quality and management of a data asset.
- Information asset owner: The role accountable to the SIRO for protecting the whole information asset. Related to, but not the same as, the data owner.
- Data steward: The role running an asset day to day: standards, access, quality processes and documentation.
- Data custodian: The technical expert for the system holding the data: storage, access controls, auditable change and disposal.
- Data role: A defined set of accountabilities for data. Records name roles, not people.
- Ownership option: The choice between keeping the IAO model, adopting the data ownership model, or a hybrid. Each must still meet the mandatory IAO actions.
- Recipe: One of the five repeatable governance activities: Mandate, Frame, Assign, Operate, Assure.
- Governance charter: A one-page statement of a governance body's purpose, scope, authority and review cadence.
- Decision log: A running record of governance decisions: what, who, why, when and the review trigger.
- Exception: A logged, time-bound deviation from policy with an owner and an expiry date. An exception without an expiry is an undocumented policy change.
- RACI: Responsible, Accountable, Consulted, Informed. One accountable role per activity.
- Data quality action plan: The plan every identified asset must have, or an equivalent mechanism, for managing its quality across seven steps.
- Critical data element: A data item whose quality drives the most important decisions made with the asset.
- Data quality dimension: A measurable aspect of quality. The framework's six are completeness, uniqueness, consistency, timeliness, validity and accuracy.
- Issues framework: The GDS method that scores importance times impact to set targets, and uses the band below target to set priority and time to resolve.
- Data quality statement: A plain-English summary of an asset's quality, known issues and what it should not be used for.
- Data Quality Vocabulary: The W3C vocabulary for publishing quality measurements with a catalogue record.
- Data contract: Quality rules and promises written down as a file that suppliers and users share.
- Data maturity: An organisation's capability around data, self-assessed with the government framework.
- Lead policy coordinator: The person each organisation nominates to coordinate DAM Policy adoption and the return, and to sit on the Working Group.
- MoSCoW: A way of ranking requirements or aims: Must have, Should have, Could have and Won't have this time.
- Request for information: Questions sent to suppliers before a tender to learn what the market offers and how products meet your requirements.
- Tender: The formal invitation to suppliers to bid, with the requirements schedule, how bids will be evaluated and the contract terms.
- Functional requirement: What a tool must do, such as export catalogue records as DCAT.
- Non-functional requirement: How well a tool must do it, such as accessibility, security, availability or the ability to export everything and leave.
- Proof of concept: A short test of a product with your own data, to see whether it does what the supplier says before you buy.
- Exit plan: How you would move your data and content out of a product, with the formats, steps, time and cost, written before you sign and tested each year.
- Continuing professional development: The learning you record to keep your skills current, often required by a professional body to keep a certification or chartered status.
- Data literacy: How well people across an organisation can read, understand, question and use data, and talk about it with confidence.
