Frameworks Level: Advanced
Capability model
Everything the DAM Policy and its related guidance need an organisation to be able to do, how each need is stated, and how mature you are.
In brief
- 15 capabilities are explicit in the policy, 11 implicit and 6 inferred.
- Every flag points to the section of GOV.UK guidance it comes from.
- Assess yourself against the government maturity model and four DAM strands.
The DAM Policy names three core capabilities, but meeting it depends on more. This model sets out 32 capabilities the policy, its guidance and adjacent rulebooks need, grouped in six clusters. Each is flagged by how the DAM Policy itself treats it.
- Explicit: The text names this as a requirement or responsibility. The text names this as a requirement or responsibility. (15)
- Implicit: The text depends on it to meet an explicit requirement but does not name it as one. The text depends on it to meet an explicit requirement but does not name it as one. (11)
- Inferred: Not in the text. This portal's judgement from good practice and adjacent rulebooks. Not in the text. This portal's judgement from good practice and adjacent rulebooks. (6)
Direction and oversight 4
- CR-01Accountable leadership and policy oversightE: The text names this as a requirement or responsibility.
- CR-02Data strategy and prioritisation by reuse valueI: The text depends on it to meet an explicit requirement but does not name it as one.
- CR-03Central reporting, assurance and arm's length body coordinationE: The text names this as a requirement or responsibility.
- CR-04Performance measurement and annual reviewE: The text names this as a requirement or responsibility.
Core DAM capabilities 5
- CR-05Identify and scope critical data assetsE: The text names this as a requirement or responsibility.
- CR-06Data cataloguing and metadata managementE: The text names this as a requirement or responsibility.
- CR-07Data ownership and stewardshipE: The text names this as a requirement or responsibility.
- CR-08Data quality management through action plansE: The text names this as a requirement or responsibility.
- CR-09Data quality issue managementI: The text depends on it to meet an explicit requirement but does not name it as one.
Data management enablers 6
- CR-10Data life cycle managementE: The text names this as a requirement or responsibility.
- CR-11Interoperability, data standards and identifiersE: The text names this as a requirement or responsibility.
- CR-12Data architecture and data servicesI: The text depends on it to meet an explicit requirement but does not name it as one.
- CR-13Catalogue and quality toolingI: The text depends on it to meet an explicit requirement but does not name it as one.
- CR-14Reference data, master data and authoritative sourcesI: The text depends on it to meet an explicit requirement but does not name it as one.
- CR-15Records, retention and disposalN: Not in the text. This portal's judgement from good practice and adjacent rulebooks.
Protection, ethics and trust 7
- CR-16Security classification and protective controlsE: The text names this as a requirement or responsibility.
- CR-17Data protection and lawful sharingE: The text names this as a requirement or responsibility.
- CR-18AI readiness and data and AI ethicsE: The text names this as a requirement or responsibility.
- CR-19Data risk managementE: The text names this as a requirement or responsibility.
- CR-20Third-party and supplier dataI: The text depends on it to meet an explicit requirement but does not name it as one.
- CR-30Equality and inclusion in dataN: Not in the text. This portal's judgement from good practice and adjacent rulebooks.
- CR-31Cyber resilience and incident response for data assetsI: The text depends on it to meet an explicit requirement but does not name it as one.
People and culture 3
- CR-21Data skills, capability and literacyI: The text depends on it to meet an explicit requirement but does not name it as one.
- CR-22Data culture and engagement with usersI: The text depends on it to meet an explicit requirement but does not name it as one.
- CR-23Maturity assessment and continuous improvementI: The text depends on it to meet an explicit requirement but does not name it as one.
Delivery, change and value 7
- CR-24Investment, business cases and valueE: The text names this as a requirement or responsibility.
- CR-25Integration with programmes, spend control and assuranceN: Not in the text. This portal's judgement from good practice and adjacent rulebooks.
- CR-26Legacy migration and decommissioningN: Not in the text. This portal's judgement from good practice and adjacent rulebooks.
- CR-27Ownership transition and handover to business as usualI: The text depends on it to meet an explicit requirement but does not name it as one.
- CR-28Cross-boundary collaborationE: The text names this as a requirement or responsibility.
- CR-29Benefits realisation and evaluationN: Not in the text. This portal's judgement from good practice and adjacent rulebooks.
- CR-32Avoiding future legacy: open standards, portability and exitN: Not in the text. This portal's judgement from good practice and adjacent rulebooks.
Not yet accounted for elsewhere. 0 capabilities are new in this release and are covered on the delivery and change, professions and skills and this page: .
Grouping and flags are this portal's own analysisO: This playbook's own synthesis of published guidance; every clause they point to was checked on 2026-11-05V: Verified against the primary source on 2026-11-05.
Filter by cluster, by how the policy treats the capability, or by how far this portal covers it. Download the map as CSV.
-
Explicit: The text names this as a requirement or responsibility.
CR-01 · Direction and oversight
Accountable leadership and policy oversight
Each organisation's chief data officer is responsible for implementing the policy; the Chief Data Officer Council oversees it.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Oversight and implementation of the policy
- Signposts
- E: The text names this as a requirement or responsibility. Chief data officer role (Data ownership model)
- E: The text names this as a requirement or responsibility. Executive leadership roles (Data ownership model)
- Maturity topics
- 9. Setting your data direction 10. Taking responsibility for data
- Skills
- Data governance leadership, Strategic data planning (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data governance. DCAM: Data management strategy and business case; Data governance.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Governance
See this capability in: Capability model · Data portals compass · Asset governance explorer
Check this flag Think CR-01 should be flagged differently? Tell us why.
-
Implicit: The text depends on it to meet an explicit requirement but does not name it as one.
CR-02 · Direction and oversight
Data strategy and prioritisation by reuse value
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.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Oversight and implementation of the policy
- Signposts
- E: The text names this as a requirement or responsibility. Prioritise your DQAPs (Data quality action plan implementation guide)
- I: The text depends on it to meet an explicit requirement but does not name it as one. Realising our data ambitions (Data asset management policy in government)
- Maturity topics
- 9. Setting your data direction
- Skills
- Strategic data planning, Strategic thinking (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data governance. DCAM: Data management strategy and business case.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Capability playbooks
See this capability in: Capability model · Capability playbook · Knowledge area activities (1) · Data portals compass · Asset governance explorer
Check this flag Think CR-02 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-03 · Direction and oversight
Central reporting, assurance and arm's length body coordination
Departments report their assets to GDS and coordinate and assure the returns of their arm's length bodies.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Identifying and reporting data assets
- Signposts
- E: The text names this as a requirement or responsibility. Organisational and administrative scope (Data asset management policy in government)
- E: The text names this as a requirement or responsibility. Record your critical data assets (Identifying and recording critical data assets)
- Maturity topics
- 10. Taking responsibility for data
- Skills
- Data governance, Metadata management (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession Knowledge and Information Management
- Industry models
- DAMA-DMBOK: Metadata management; Data governance. DCAM: Data governance; Data control environment.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Cataloguing
See this capability in: Capability model · Data portals compass · Asset governance explorer
Check this flag Think CR-03 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-04 · Direction and oversight
Performance measurement and annual review
Returns must be maintained and reviewed every year; the guidance adds measures for ownership and quality.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Identifying and reporting data assets
- Signposts
- E: The text names this as a requirement or responsibility. Measuring the success of data ownership initiatives (Data ownership model)
- E: The text names this as a requirement or responsibility. Create a data quality dashboard (Data quality action plan implementation guide)
- Maturity topics
- 5. Making decisions with data 10. Taking responsibility for data
- Skills
- Performance measurement, Data maturity (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession Analysis Function
- Industry models
- DAMA-DMBOK: Data governance; Data quality; Data warehousing and business intelligence. DCAM: Data governance; Data quality management.K: General knowledge, not checked against a source in this release
- In this portal
- Partial: Joined up
See this capability in: Capability model · Knowledge area activities (3) · Data portals compass · Asset governance explorer
Check this flag Think CR-04 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-05 · Core DAM capabilities
Identify and scope critical data assets
Only assets classified OFFICIAL are in scope, and the critical-asset guidance defines which assets count.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Data assets in scope
- Signposts
- E: The text names this as a requirement or responsibility. Identify your critical data assets (Identifying and recording critical data assets)
- E: The text names this as a requirement or responsibility. Purposes that critical data assets support (Identifying and recording critical data assets)
- E: The text names this as a requirement or responsibility. Defining a data asset (Data asset management policy in government)
- Maturity topics
- 4. Knowing the data you have
- Skills
- Data management, Data governance (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession Knowledge and Information Management
- Industry models
- DAMA-DMBOK: Metadata management; Data governance. DCAM: Business and data architecture.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Cataloguing
See this capability in: Capability model · Knowledge area activities (1) · Data portals compass · Asset governance explorer
Check this flag Think CR-05 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-06 · Core DAM capabilities
Data cataloguing and metadata management
Metadata about in-scope assets must be held in a data catalogue; the quality guide also assumes a catalogue exists.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Identifying and reporting data assets
- Signposts
- E: The text names this as a requirement or responsibility. Where to record and store your metadata (Recording metadata to describe critical data assets)
- E: The text names this as a requirement or responsibility. Metadata you should record (Recording metadata to describe critical data assets)
- E: The text names this as a requirement or responsibility. Making your metadata machine-readable (Recording metadata to describe critical data assets)
- I: The text depends on it to meet an explicit requirement but does not name it as one. Build a data catalogue (inside the quality guide) (Data quality action plan implementation guide)
- Maturity topics
- 4. Knowing the data you have 7. Managing your data
- Skills
- Metadata management, Data standards (Digital and Data capability framework)
- Professions
- Knowledge and Information Management Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Metadata management. DCAM: Business and data architecture; Data and technology architecture.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Cataloguing
See this capability in: Capability model · Knowledge area activities (4) · Data portals compass · Asset governance explorer
Check this flag Think CR-06 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-07 · Core DAM capabilities
Data ownership and stewardship
Every identified asset must have a named data owner, as set out in the data ownership model.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Data ownership
- Signposts
- E: The text names this as a requirement or responsibility. Data ownership roles and responsibilities (Data ownership model)
- E: The text names this as a requirement or responsibility. A checklist for your organisation (Data ownership model)
- E: The text names this as a requirement or responsibility. Data owners and information asset owners (Data ownership model)
- Maturity topics
- 10. Taking responsibility for data
- Skills
- Data governance, Stakeholder relationship management (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession Knowledge and Information Management
- Industry models
- DAMA-DMBOK: Data governance. DCAM: Data governance.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Governance
See this capability in: Capability model · Knowledge area activities (3) · Data portals compass · Asset governance explorer
Check this flag Think CR-07 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-08 · Core DAM capabilities
Data quality management through action plans
Every identified asset must have a data quality action plan or an equivalent that covers all 7 steps.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Data quality action plans
- Signposts
- E: The text names this as a requirement or responsibility. The 7 DQAP steps (Data quality action plan implementation guide)
- E: The text names this as a requirement or responsibility. Data quality principles (The Government Data Quality Framework)
- E: The text names this as a requirement or responsibility. Set a data quality target (Data quality issues framework)
- Maturity topics
- 7. Managing your data
- Skills
- Quality assurance of data and analysis, Data management (Digital and Data capability framework)
- Professions
- Analysis Function Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data quality. DCAM: Data quality management.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Quality
See this capability in: Capability model · Knowledge area activities (2) · Data portals compass · Asset governance explorer
Check this flag Think CR-08 should be flagged differently? Tell us why.
-
Implicit: The text depends on it to meet an explicit requirement but does not name it as one.
CR-09 · Core DAM capabilities
Data quality issue management
The policy points to the issues framework to support resource decisions; logging and prioritising issues is how plans turn into action.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Data quality action plans
- Signposts
- E: The text names this as a requirement or responsibility. Assign a priority to an issue (Data quality issues framework)
- E: The text names this as a requirement or responsibility. Allocate time and resources (Data quality issues framework)
- E: The text names this as a requirement or responsibility. Identify and log issues (Data quality action plan implementation guide)
- Maturity topics
- 7. Managing your data
- Skills
- Problem management, Quality assurance of data and analysis (Digital and Data capability framework)
- Professions
- Analysis Function
- Industry models
- DAMA-DMBOK: Data quality. DCAM: Data quality management.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Quality
See this capability in: Capability model · Knowledge area activities (1) · Data portals compass · Asset governance explorer
Check this flag Think CR-09 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-10 · Data management enablers
Data life cycle management
The policy sets out life cycle controls; the ownership model makes life cycle management a principle.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Realising our data ambitions
- Signposts
- E: The text names this as a requirement or responsibility. Data is managed throughout its life cycle (Data ownership model)
- E: The text names this as a requirement or responsibility. Assess quality throughout the life cycle (The Government Data Quality Framework)
- E: The text names this as a requirement or responsibility. The data life cycle (Data quality action plan implementation guide)
- Maturity topics
- 7. Managing your data
- Skills
- Data life cycle (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession Knowledge and Information Management
- Industry models
- DAMA-DMBOK: Data governance; Data storage and operations. DCAM: Data control environment.K: General knowledge, not checked against a source in this release
- In this portal
- Partial: Joined up
See this capability in: Capability model · Knowledge area activities (4) · Data portals compass · Asset governance explorer
Check this flag Think CR-10 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-11 · Data management enablers
Interoperability, data standards and identifiers
The policy sets minimum requirements for interoperability; standards and shared identifiers are how they are met.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Realising our data ambitions
- Signposts
- E: The text names this as a requirement or responsibility. Data is standardised (Data ownership model)
- E: The text names this as a requirement or responsibility. Using 'identifier' (Recording metadata to describe critical data assets)
- E: The text names this as a requirement or responsibility. Open standards for government (Open standards for government)
- Maturity topics
- 7. Managing your data 3. Having the right systems
- Skills
- Data standards, Data integration design (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data integration and interoperability; Reference and master data. DCAM: Data and technology architecture.K: General knowledge, not checked against a source in this release
- In this portal
- Partial: Sectors
See this capability in: Capability model · Knowledge area activities (12) · Data portals compass · Asset governance explorer
Check this flag Think CR-11 should be flagged differently? Tell us why.
-
Implicit: The text depends on it to meet an explicit requirement but does not name it as one.
CR-12 · Data management enablers
Data architecture and data services
A data asset includes the data services (such as APIs) used to reach it, so someone must design and run those services.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Defining a data asset
- Signposts
- E: The text names this as a requirement or responsibility. Data platforms and services (Data ownership model)
- E: The text names this as a requirement or responsibility. Merged data sets and data services (Data ownership model)
- Maturity topics
- 3. Having the right systems
- Skills
- Data architecture, Data modelling (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data architecture; Data modelling and design. DCAM: Business and data architecture; Data and technology architecture.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Knowledge areas
See this capability in: Capability model · Knowledge area activities (11) · Data portals compass · Asset governance explorer
Check this flag Think CR-12 should be flagged differently? Tell us why.
-
Implicit: The text depends on it to meet an explicit requirement but does not name it as one.
CR-13 · Data management enablers
Catalogue and quality tooling
Catalogues and automated quality checks need platforms; GDS will build a central discovery service.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Identifying and reporting data assets
- Signposts
- E: The text names this as a requirement or responsibility. Automate assessments (Data quality action plan implementation guide)
- E: The text names this as a requirement or responsibility. Technology Code of Practice (The Technology Code of Practice)
- Maturity topics
- 3. Having the right systems
- Skills
- Programming and build (data and analytics engineering), Metadata management (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Metadata management; Data quality. DCAM: Data and technology architecture.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Capability playbooks
See this capability in: Capability model · Capability playbook · Data portals compass · Asset governance explorer
Check this flag Think CR-13 should be flagged differently? Tell us why.
-
Implicit: The text depends on it to meet an explicit requirement but does not name it as one.
CR-14 · Data management enablers
Reference data, master data and authoritative sources
Reducing duplicate collection depends on agreeing which source is authoritative; the policy states the aim, the ownership model the principle.O: This playbook's own synthesis of published guidance
- Policy clause
- Not stated in the DAM Policy
- Signposts
- E: The text names this as a requirement or responsibility. Data is authoritative (Data ownership model)
- E: The text names this as a requirement or responsibility. Process owners and enterprise data owners (Data ownership model)
- Maturity topics
- 7. Managing your data
- Skills
- Data management, Data modelling (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Reference and master data. DCAM: Business and data architecture.K: General knowledge, not checked against a source in this release
- In this portal
- Partial: Sectors
See this capability in: Capability model · Knowledge area activities (8) · Data portals compass · Asset governance explorer
Check this flag Think CR-14 should be flagged differently? Tell us why.
-
Inferred: Not in the text. This portal's judgement from good practice and adjacent rulebooks.
CR-15 · Data management enablers
Records, retention and disposal
Not mentioned in the policy, but an asset's life cycle ends in retention, transfer or disposal, which records law governs.O: This playbook's own synthesis of published guidance
- Policy clause
- Not stated in the DAM Policy
- Signposts
- E: The text names this as a requirement or responsibility. The National Archives information management guidance (Information management guidance)
- E: The text names this as a requirement or responsibility. Retiring your service: protecting information (Retiring your service)
- I: The text depends on it to meet an explicit requirement but does not name it as one. Data ownership in context (Data ownership model)
- Maturity topics
- 7. Managing your data 8. Protecting your data
- Skills
- Data life cycle, Data compliance and security (Digital and Data capability framework)
- Professions
- Knowledge and Information Management
- Industry models
- DAMA-DMBOK: Document and content management; Data storage and operations. DCAM: Data control environment.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Knowledge areas
See this capability in: Capability model · Knowledge area activities (4) · Data portals compass · Asset governance explorer
Check this flag Think CR-15 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-16 · Protection, ethics and trust
Security classification and protective controls
Scope depends on classification (OFFICIAL only), so classification must be right before an asset is recorded.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Data assets in scope
- Signposts
- E: The text names this as a requirement or responsibility. Data is secure (Data ownership model)
- E: The text names this as a requirement or responsibility. Government Security Classifications (Government Security Classifications)
- Maturity topics
- 8. Protecting your data
- Skills
- Data compliance and security, Data risk management (Digital and Data capability framework)
- Professions
- Government Security Profession Government Cyber Profession
- Industry models
- DAMA-DMBOK: Data security. DCAM: Data control environment.K: General knowledge, not checked against a source in this release
- In this portal
- Partial: Sectors
See this capability in: Capability model · Knowledge area activities (3) · Data portals compass · Asset governance explorer
Check this flag Think CR-16 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-17 · Protection, ethics and trust
Data protection and lawful sharing
The policy keeps every legal and data protection obligation in place and does not force sharing.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Data assets in scope
- Signposts
- E: The text names this as a requirement or responsibility. Data protection roles (Data ownership model)
- E: The text names this as a requirement or responsibility. Data Sharing Governance Framework (Data Sharing Governance Framework)
- E: The text names this as a requirement or responsibility. ICO data sharing code (ICO data sharing code of practice)
- Maturity topics
- 8. Protecting your data 1. Engaging with others
- Skills
- Data ethics and privacy, Data compliance and security (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession Knowledge and Information Management
- Industry models
- DAMA-DMBOK: Data security; Data governance. DCAM: Data control environment.K: General knowledge, not checked against a source in this release
- In this portal
- Partial: Sectors
See this capability in: Capability model · Knowledge area activities (4) · Data portals compass · Asset governance explorer
Check this flag Think CR-17 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-18 · Protection, ethics and trust
AI readiness and data and AI ethics
The policy names AI readiness as a reason for quality plans; ethics is not named, so it is inferred from the AI guidance.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Data quality action plans
- Signposts
- E: The text names this as a requirement or responsibility. Making government datasets ready for AI (Making government datasets ready for AI)
- E: The text names this as a requirement or responsibility. Data and AI Ethics Framework (Data and AI Ethics Framework)
- E: The text names this as a requirement or responsibility. Algorithmic Transparency Recording Standard (Algorithmic Transparency Recording Standard hub)
- Maturity topics
- 6. Managing and using data ethically
- Skills
- Data ethics and privacy, Analysis and synthesis for data and AI ethics (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data governance; Data quality. DCAM: Analytics management.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Sectors
See this capability in: Capability model · Knowledge area activities (2) · Data portals compass · Asset governance explorer
Check this flag Think CR-18 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-19 · Protection, ethics and trust
Data risk management
The policy cites risk controls and understanding cross-public sector dependencies to manage risk; how is left to each organisation.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Realising our data ambitions
- Signposts
- E: The text names this as a requirement or responsibility. Senior information risk owner (Data ownership model)
- E: The text names this as a requirement or responsibility. The Orange Book (The Orange Book: management of risk)
- Maturity topics
- 8. Protecting your data 10. Taking responsibility for data
- Skills
- Data risk management, Enabling and informing risk-based decisions (Digital and Data capability framework)
- Professions
- Government Security Profession Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data governance; Data security. DCAM: Data control environment.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Capability playbooks
See this capability in: Capability model · Capability playbook · Knowledge area activities (3) · Data portals compass · Asset governance explorer
Check this flag Think CR-19 should be flagged differently? Tell us why.
-
Implicit: The text depends on it to meet an explicit requirement but does not name it as one.
CR-20 · Protection, ethics and trust
Third-party and supplier data
Many critical assets are held or processed by suppliers; ownership, metadata and quality duties must reach into contracts.O: This playbook's own synthesis of published guidance
- Policy clause
- Not stated in the DAM Policy
- Signposts
- E: The text names this as a requirement or responsibility. Data from a third party (Data ownership model)
- E: The text names this as a requirement or responsibility. Data licensing impact on data owners (Data ownership model)
- E: The text names this as a requirement or responsibility. The Sourcing Playbook (The Sourcing Playbook)
- Maturity topics
- 1. Engaging with others
- Skills
- Stakeholder relationship management, Data compliance and security (Digital and Data capability framework)
- Professions
- Government Commercial Function Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data governance. DCAM: Data governance.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Capability playbooks
See this capability in: Capability model · Capability playbook · Knowledge area activities (1) · Data portals compass · Asset governance explorer
Check this flag Think CR-20 should be flagged differently? Tell us why.
-
Implicit: The text depends on it to meet an explicit requirement but does not name it as one.
CR-21 · People and culture
Data skills, capability and literacy
The policy assigns new responsibilities; the guidance lists the skills and training those people need.O: This playbook's own synthesis of published guidance
- Policy clause
- Not stated in the DAM Policy
- Signposts
- E: The text names this as a requirement or responsibility. Skills that data owners need (Data ownership model)
- E: The text names this as a requirement or responsibility. Relevant training modules (Data quality action plan implementation guide)
- E: The text names this as a requirement or responsibility. Build data quality capability (The Government Data Quality Framework)
- Maturity topics
- 2. Having the right data skills and knowledge
- Skills
- Data literacy improvement, Capability building for digital, data and technology (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession Analysis Function Knowledge and Information Management
- Industry models
- DAMA-DMBOK: Data governance. DCAM: Data management program and funding.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Capability playbooks
See this capability in: Capability model · Capability playbook · Data portals compass · Asset governance explorer
Check this flag Think CR-21 should be flagged differently? Tell us why.
-
Implicit: The text depends on it to meet an explicit requirement but does not name it as one.
CR-22 · People and culture
Data culture and engagement with users
Ownership and quality only last where people value data and know who uses it.O: This playbook's own synthesis of published guidance
- Policy clause
- Not stated in the DAM Policy
- Signposts
- E: The text names this as a requirement or responsibility. Promoting a culture of data ownership (Data ownership model)
- E: The text names this as a requirement or responsibility. Know your users and their needs (The Government Data Quality Framework)
- Maturity topics
- 1. Engaging with others
- Skills
- Stakeholder relationship management, Communicating between the technical and non-technical (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data governance. DCAM: Data governance.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Capability playbooks
See this capability in: Capability model · Capability playbook · Data portals compass · Asset governance explorer
Check this flag Think CR-22 should be flagged differently? Tell us why.
-
Implicit: The text depends on it to meet an explicit requirement but does not name it as one.
CR-23 · People and culture
Maturity assessment and continuous improvement
The policy recognises different levels of data maturity; the government maturity framework is the shared way to measure them.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Oversight and implementation of the policy
- Signposts
- E: The text names this as a requirement or responsibility. Data Maturity Assessment for Government (Data Maturity Assessment for Government: Framework)
- E: The text names this as a requirement or responsibility. Focus on continuous improvement (The Government Data Quality Framework)
- Maturity topics
- 1. Engaging with others 2. Having the right data skills and knowledge 3. Having the right systems 4. Knowing the data you have 5. Making decisions with data 6. Managing and using data ethically 7. Managing your data 8. Protecting your data 9. Setting your data direction 10. Taking responsibility for data
- Skills
- Data maturity (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data governance. DCAM: Data management strategy and business case.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Capability playbooks
See this capability in: Capability model · Capability playbook · Data portals compass · Asset governance explorer
Check this flag Think CR-23 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-24 · Delivery, change and value
Investment, business cases and value
The policy says data must be properly valued and invested in; funding comes through business cases.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Realising our data ambitions
- Signposts
- E: The text names this as a requirement or responsibility. The Green Book and the five case model (The Green Book and accompanying guidance)
- E: The text names this as a requirement or responsibility. Evaluate costs and benefits (Data quality action plan implementation guide)
- Maturity topics
- 9. Setting your data direction
- Skills
- Delivering business impact through data, Strategic data planning (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession Analysis Function
- Industry models
- DAMA-DMBOK: Data governance. DCAM: Data management program and funding; Data management strategy and business case.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Capability playbooks
See this capability in: Capability model · Capability playbook · Knowledge area activities (1) · Data portals compass · Asset governance explorer
Check this flag Think CR-24 should be flagged differently? Tell us why.
-
Inferred: Not in the text. This portal's judgement from good practice and adjacent rulebooks.
CR-25 · Delivery, change and value
Integration with programmes, spend control and assurance
Not in the policy text. Most new and replacement data assets arrive through change programmes, so the controls must be built into them.O: This playbook's own synthesis of published guidance
- Policy clause
- Not stated in the DAM Policy
- Signposts
- E: The text names this as a requirement or responsibility. GovS 002: Project Delivery (Government Functional Standard GovS 002: Project Delivery)
- E: The text names this as a requirement or responsibility. Integrated assurance for major projects (Implementing integrated assurance for major projects)
- E: The text names this as a requirement or responsibility. Service assessments (Service assessments and applying the Service Standard)
- E: The text names this as a requirement or responsibility. Plan for and manage changes (Data quality action plan implementation guide)
- Maturity topics
- 3. Having the right systems 9. Setting your data direction
- Skills
- Managing a data project, Stakeholder relationship management (Digital and Data capability framework)
- Professions
- Project Delivery Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data governance. DCAM: Data management program and funding.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Capability playbooks
See this capability in: Capability model · Capability playbook · Knowledge area activities (1) · Data portals compass · Asset governance explorer
Check this flag Think CR-25 should be flagged differently? Tell us why.
-
Inferred: Not in the text. This portal's judgement from good practice and adjacent rulebooks.
CR-26 · Delivery, change and value
Legacy migration and decommissioning
Not in the policy. The legacy guidance makes a data asset register its second principle; migrations are where quality is most at risk.O: This playbook's own synthesis of published guidance
- Policy clause
- Not stated in the DAM Policy
- Signposts
- E: The text names this as a requirement or responsibility. Build a register of your data assets (Managing legacy technology)
- E: The text names this as a requirement or responsibility. Issues that stop legacy migration (Managing legacy technology)
- E: The text names this as a requirement or responsibility. Protecting information when retiring a service (Retiring your service)
- Maturity topics
- 3. Having the right systems 7. Managing your data
- Skills
- Data integration design, Data preparation and linkage (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession Knowledge and Information Management
- Industry models
- DAMA-DMBOK: Data integration and interoperability; Data storage and operations. DCAM: Data and technology architecture.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Capability playbooks
See this capability in: Capability model · Capability playbook · Knowledge area activities (2) · Data portals compass · Asset governance explorer
Check this flag Think CR-26 should be flagged differently? Tell us why.
-
Implicit: The text depends on it to meet an explicit requirement but does not name it as one.
CR-27 · Delivery, change and value
Ownership transition and handover to business as usual
A named owner must survive staff moves and the end of the project that created the asset.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Data ownership
- Signposts
- E: The text names this as a requirement or responsibility. Steps to transition ownership (Data ownership model)
- E: The text names this as a requirement or responsibility. How often ownership should be reviewed (Data ownership model)
- Maturity topics
- 10. Taking responsibility for data
- Skills
- Data governance, Stakeholder relationship management (Digital and Data capability framework)
- Professions
- Project Delivery Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data governance. DCAM: Data governance.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Capability playbooks
See this capability in: Capability model · Capability playbook · Data portals compass · Asset governance explorer
Check this flag Think CR-27 should be flagged differently? Tell us why.
-
Explicit: The text names this as a requirement or responsibility.
CR-28 · Delivery, change and value
Cross-boundary collaboration
Departments coordinate with their arm's length bodies, and data passed to devolved administrations can stay in scope.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Organisational and administrative scope
- Signposts
- E: The text names this as a requirement or responsibility. Devolved administrations (Data quality action plan implementation guide)
- E: The text names this as a requirement or responsibility. Shared data sets across organisations (Data ownership model)
- Maturity topics
- 1. Engaging with others
- Skills
- Stakeholder relationship management (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data governance. DCAM: Data governance.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Sectors
See this capability in: Capability model · Knowledge area activities (2) · Data portals compass · Asset governance explorer
Check this flag Think CR-28 should be flagged differently? Tell us why.
-
Inferred: Not in the text. This portal's judgement from good practice and adjacent rulebooks.
CR-29 · Delivery, change and value
Benefits realisation and evaluation
The policy lists benefits such as less duplication and cleansing; showing they happened needs an evaluation plan.O: This playbook's own synthesis of published guidance
- Policy clause
- Not stated in the DAM Policy
- Signposts
- E: The text names this as a requirement or responsibility. The Magenta Book (The Magenta Book)
- I: The text depends on it to meet an explicit requirement but does not name it as one. Measuring success of ownership (Data ownership model)
- Maturity topics
- 5. Making decisions with data
- Skills
- Performance measurement, Delivering business impact through data (Digital and Data capability framework)
- Professions
- Analysis Function
- Industry models
- DAMA-DMBOK: Data governance; Data warehousing and business intelligence. DCAM: Data management program and funding.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Capability playbooks
See this capability in: Capability model · Capability playbook · Knowledge area activities (1) · Data portals compass · Asset governance explorer
Check this flag Think CR-29 should be flagged differently? Tell us why.
-
Inferred: Not in the text. This portal's judgement from good practice and adjacent rulebooks.
CR-30 · Protection, ethics and trust
Equality and inclusion in data
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.O: This playbook's own synthesis of published guidance
- Policy clause
- Not stated in the DAM Policy
- Signposts
- E: The text names this as a requirement or responsibility. Public sector equality duty (Public sector equality duty)
- E: The text names this as a requirement or responsibility. Equality Act 2010 (Equality Act 2010)
- Maturity topics
- 6. Managing and using data ethically
- Skills
- Applied empathy and inclusivity, Data ethics and privacy (Digital and Data capability framework)
- Professions
- Analysis Function Government Digital and Data Profession
- Industry models
- DAMA-DMBOK: Data governance; Data quality. DCAM: Data governance.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Inclusion
See this capability in: Capability model · Knowledge area activities (1) · Data portals compass · Asset governance explorer
Check this flag Think CR-30 should be flagged differently? Tell us why.
-
Implicit: The text depends on it to meet an explicit requirement but does not name it as one.
CR-31 · Protection, ethics and trust
Cyber resilience and incident response for data assets
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.O: This playbook's own synthesis of published guidance
- Policy clause
- DAM Policy: Data assets in scope
- Signposts
- E: The text names this as a requirement or responsibility. Data is secure (Data ownership model)
- E: The text names this as a requirement or responsibility. Cyber Assessment Framework (Cyber Assessment Framework (CAF))
- E: The text names this as a requirement or responsibility. NCSC incident management (Incident management)
- E: The text names this as a requirement or responsibility. GovS 007: Security (Government Functional Standard GovS 007: Security)
- Maturity topics
- 8. Protecting your data
- Skills
- Data compliance and security, Data risk management (Digital and Data capability framework)
- Professions
- Government Cyber Profession Government Security Profession
- Industry models
- DAMA-DMBOK: Data security. DCAM: Data control environment.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Knowledge areas
See this capability in: Capability model · Knowledge area activities (4) · Data portals compass · Asset governance explorer
Check this flag Think CR-31 should be flagged differently? Tell us why.
-
Inferred: Not in the text. This portal's judgement from good practice and adjacent rulebooks.
CR-32 · Delivery, change and value
Avoiding future legacy: open standards, portability and exit
Not in the policy. Without open formats, documented schemas and exit terms, every new system becomes the next concentration of hard-to-reach data.O: This playbook's own synthesis of published guidance
- Policy clause
- Not stated in the DAM Policy
- Signposts
- E: The text names this as a requirement or responsibility. Open standards for government (Open standards for government)
- E: The text names this as a requirement or responsibility. Prevent technical debt and legacy (Prevent technical debt and legacy)
- E: The text names this as a requirement or responsibility. Choosing technology (Choosing technology: an introduction)
- E: The text names this as a requirement or responsibility. Model Services Contract (Model Services Contract)
- Maturity topics
- 3. Having the right systems 7. Managing your data
- Skills
- Data standards, Data architecture (Digital and Data capability framework)
- Professions
- Government Digital and Data Profession Project Delivery
- Industry models
- DAMA-DMBOK: Data architecture; Data integration and interoperability. DCAM: Data and technology architecture.K: General knowledge, not checked against a source in this release
- In this portal
- Covered: Capability playbooks
See this capability in: Capability model · Capability playbook · Knowledge area activities (2) · Data portals compass · Asset governance explorer
Check this flag Think CR-32 should be flagged differently? Tell us why.
Government's shared model is the Data Maturity Assessment for GovernmentV: Verified against the primary source on 2026-11-05: 10 topics, each split into rows that belong to one of 6 themes, and every row described at 5 levels. Select a topic to read its rows on GOV.UK.
| Topic | Uses | Data | Leadership | Culture | Tools | Skills | Rows |
|---|---|---|---|---|---|---|---|
| 1. Engaging with others | none | none | none | 7 rows | none | 1 rows | 8 |
| 2. Having the right data skills and knowledge | 1 rows | 1 rows | 4 rows | 1 rows | none | 7 rows | 14 |
| 3. Having the right systems | none | none | 1 rows | none | 9 rows | none | 10 |
| 4. Knowing the data you have | none | 4 rows | none | none | none | none | 4 |
| 5. Making decisions with data | 7 rows | none | 3 rows | none | none | none | 10 |
| 6. Managing and using data ethically | none | 2 rows | 2 rows | 5 rows | 1 rows | 1 rows | 11 |
| 7. Managing your data | none | 11 rows | 1 rows | 3 rows | none | none | 15 |
| 8. Protecting your data | none | 2 rows | none | 4 rows | 2 rows | 2 rows | 10 |
| 9. Setting your data direction | 1 rows | 1 rows | 4 rows | 1 rows | none | none | 7 |
| 10. Taking responsibility for data | none | 1 rows | 2 rows | 3 rows | 1 rows | 1 rows | 8 |
The six themes
- Uses: Getting value from data: decisions, evidence of impact, better services.
- Data: The technical side of managing data: assets, collection, quality, interoperability.
- Leadership: How senior and business leaders engage with data: strategy, responsibility, oversight, investment.
- Culture: Attitudes to data across the organisation: awareness, openness, security.
- Tools: The systems and tools used to store, share and work with data.
- Skills: The data skills and knowledge of staff at every level.
Themes summarised in this portal's wordsO: This playbook's own synthesis of published guidance.
Licence. The framework is published under CC BY-NC-SA 4.0, which does not allow commercial reuse and requires adaptations to be shared alike. This portal therefore links to it and records only its structure (names and row counts). It does not copy the level descriptions. For use inside government, the framework asks organisations to contact the Central Digital and Data Office.
What each level looks like for the DAM Policy
Indicators for four DAM strands, written for this portalO: This playbook's own synthesis of published guidance to sit alongside the government framework. They are not part of it.
| Strand | 1. Beginning | 2. Emerging | 3. Learning | 4. Developing | 5. Mastering |
|---|---|---|---|---|---|
| Ownership and governance | Few assets have a named owner; decisions about data are made by whoever holds it. | Owners named for some critical assets, often by job title only; no regular review. | Every reported critical asset has a named owner who knows the role; a board meets and records decisions. | Owners review their assets each year, escalate risks and are covered when people move; ownership is in objectives. | Ownership is routine across the organisation and its bodies; owners shape investment and sharing decisions. |
| Cataloguing and reporting | No list of critical assets; knowledge sits with individuals. | A spreadsheet of assets exists, with gaps in the core metadata. | All in-scope assets are in a catalogue with the core metadata and reported to GDS on time. | Metadata is machine-readable, checked automatically and updated when assets change; arm's length body returns are assured. | The catalogue is the first place people look; metadata flows to central discovery services without rework. |
| Quality management | Quality problems are found by users and fixed one by one. | Some rules exist for some assets; quality is measured occasionally. | Every critical asset has a DQAP covering all 7 steps, with targets and an issue log. | Checks run automatically, root causes are fixed upstream and results are published to users. | Quality is designed in at collection; trends drive investment and prevent new issues. |
| Change and investment | Projects create and retire data without telling anyone responsible for it. | Some programmes ask about data at business case stage, inconsistently. | Business cases, spend control and service assessments ask for DAM evidence; migrations reconcile data. | Assurance plans include DAM checkpoints; benefits are tracked; legacy exits start from the asset register. | Portfolio choices are driven by data asset risk and value, including effects on outcomes for different groups. |
The Data Management Body of Knowledge (DAMA-DMBOK) arranges data management as knowledge areas around data governance. This view places the DAM Policy, the capability model and the government maturity model on that wheel, so each role can see which areas it shapes and how the policy fits a wider enterprise data management capability.
Knowledge area names follow DAMA-DMBOKK: General knowledge, not checked against a source in this release; this wheel, its descriptions and the role guidance are this portal's ownO: This playbook's own synthesis of published guidance. See DAMA-DMBOK: Data Management Body of KnowledgeV: Verified against the primary source on 2026-11-05.
Darker segments are touched by more DAM capabilities. Select a segment to read about it.
Choosing a role opens "How each role uses it" in every area and highlights your row.
| Knowledge area | Capabilities |
|---|---|
| Data governance | 20 |
| Data architecture | 2 |
| Data modelling and design | 1 |
| Data storage and operations | 3 |
| Data security | 4 |
| Data integration and interoperability | 3 |
| Document and content management | 1 |
| Reference and master data | 2 |
| Data warehousing and business intelligence | 2 |
| Metadata management | 4 |
| Data quality | 6 |
Data governance
Decision rights, accountability and policy for data across the organisation.O: This playbook's own synthesis of published guidance
- DAM capabilities
- CR-01 Accountable leadership and policy oversight CR-02 Data strategy and prioritisation by reuse value CR-03 Central reporting, assurance and arm's length body coordination CR-04 Performance measurement and annual review CR-05 Identify and scope critical data assets CR-07 Data ownership and stewardship CR-10 Data life cycle management CR-17 Data protection and lawful sharing CR-18 AI readiness and data and AI ethics CR-19 Data risk management CR-20 Third-party and supplier data CR-21 Data skills, capability and literacy CR-22 Data culture and engagement with users CR-23 Maturity assessment and continuous improvement CR-24 Investment, business cases and value CR-25 Integration with programmes, spend control and assurance CR-27 Ownership transition and handover to business as usual CR-28 Cross-boundary collaboration CR-29 Benefits realisation and evaluation CR-30 Equality and inclusion in data
- Maturity topics
- 1. Engaging with others 2. Having the right data skills and knowledge 3. Having the right systems 4. Knowing the data you have 5. Making decisions with data 6. Managing and using data ethically 7. Managing your data 8. Protecting your data 9. Setting your data direction 10. Taking responsibility for data
- Drill down
Data governance playbook: 5 steps, each with its tasks, roles, templates and standards.
- Records and information counterpart
- Information governance and the information asset owner role.
How each role uses it
| Role | Use |
|---|---|
| Chief data officer | Set the mandate and board; hold owners to account |
| Lead policy coordinator | Run the governance cycle and the return |
| Data owner | Make and record decisions for your assets |
| Data steward | Prepare decisions and keep definitions agreed |
| Catalogue manager or data custodian | Apply governance decisions in the catalogue |
| Data quality lead or analyst | Escalate quality risks to owners |
| Programme or project lead | Bring programme decisions into the governance cycle |
| Commercial or technology lead | Write data ownership and decision rights into contracts |
Data architecture
The blueprint of data across the organisation: where data lives, how it flows and which source is authoritative.O: This playbook's own synthesis of published guidance
- DAM capabilities
- CR-12 Data architecture and data services CR-32 Avoiding future legacy: open standards, portability and exit
- Maturity topics
- 3. Having the right systems 7. Managing your data
- Drill down
Data architecture and models supplement: extra rules for critical assets.
Knowledge area activities: 5 activities, each with steps, outputs, evidence and who does what.
- Records and information counterpart
- Information architecture and file plans.
How each role uses it
| Role | Use |
|---|---|
| Chief data officer | Sponsor a target data architecture |
| Lead policy coordinator | Use it to find candidate assets |
| Data owner | Agree the authoritative source for your data |
| Data steward | Map flows and dependencies |
| Catalogue manager or data custodian | Link catalogue entries to systems |
| Data quality lead or analyst | Trace quality problems to where data enters |
| Programme or project lead | Approve designs against it |
| Commercial or technology lead | Check tools fit the target architecture before you buy |
Data modelling and design
Defining the structure, meaning and relationships of data.O: This playbook's own synthesis of published guidance
- DAM capabilities
- CR-12 Data architecture and data services
- Maturity topics
- 3. Having the right systems
- Drill down
Data architecture and models supplement: extra rules for critical assets.
Knowledge area activities: 4 activities, each with steps, outputs, evidence and who does what.
- Records and information counterpart
- Records classification schemes.
How each role uses it
| Role | Use |
|---|---|
| Chief data officer | Expect agreed definitions for critical assets |
| Lead policy coordinator | Collect definitions for the return |
| Data owner | Approve the meaning of key data items |
| Data steward | Maintain definitions and the glossary |
| Catalogue manager or data custodian | Publish schemas with entries |
| Data quality lead or analyst | Write rules from the model |
| Programme or project lead | Require documented models from suppliers |
| Commercial or technology lead | Require suppliers to hand over documented data models |
Data storage and operations
Running the platforms that store data: backup, recovery, performance and retention.O: This playbook's own synthesis of published guidance
- DAM capabilities
- CR-10 Data life cycle management CR-15 Records, retention and disposal CR-26 Legacy migration and decommissioning
- Maturity topics
- 3. Having the right systems 7. Managing your data 8. Protecting your data
- Drill down
Knowledge area activities: 4 activities, each with steps, outputs, evidence and who does what.
- Records and information counterpart
- Storage, preservation and disposal of records.
How each role uses it
| Role | Use |
|---|---|
| Chief data officer | Fund resilient platforms for critical data |
| Lead policy coordinator | Know which platform holds each asset |
| Data owner | Agree recovery objectives |
| Data steward | Check retention is applied |
| Catalogue manager or data custodian | Record system of record and location |
| Data quality lead or analyst | Check data after restore |
| Programme or project lead | Plan platform moves and decommissioning |
| Commercial or technology lead | Agree availability and recovery targets in service levels |
Data security
Protecting data from unauthorised access, change and loss, in line with classification.O: This playbook's own synthesis of published guidance
- DAM capabilities
- CR-16 Security classification and protective controls CR-17 Data protection and lawful sharing CR-19 Data risk management CR-31 Cyber resilience and incident response for data assets
- Maturity topics
- 1. Engaging with others 8. Protecting your data 10. Taking responsibility for data
- Drill down
Knowledge area activities: 5 activities, each with steps, outputs, evidence and who does what.
- Records and information counterpart
- Protective marking and access to records.
How each role uses it
| Role | Use |
|---|---|
| Chief data officer | Link critical assets to cyber risk |
| Lead policy coordinator | Confirm classification is right before reporting |
| Data owner | Accept residual risk for your assets |
| Data steward | Apply handling rules |
| Catalogue manager or data custodian | Record classification and access rights |
| Data quality lead or analyst | Treat odd quality drops as security signals |
| Programme or project lead | Build security in from the start |
| Commercial or technology lead | Require security that matches the classification, and incident notice |
Data integration and interoperability
Moving and joining data between systems and organisations using shared standards.O: This playbook's own synthesis of published guidance
- DAM capabilities
- CR-11 Interoperability, data standards and identifiers CR-26 Legacy migration and decommissioning CR-32 Avoiding future legacy: open standards, portability and exit
- Maturity topics
- 3. Having the right systems 7. Managing your data
- Drill down
Knowledge area activities: 4 activities, each with steps, outputs, evidence and who does what.
- Records and information counterpart
- Records exchange and transfer formats.
How each role uses it
| Role | Use |
|---|---|
| Chief data officer | Back open standards and shared identifiers |
| Lead policy coordinator | Track sharing arrangements |
| Data owner | Approve sharing of your data |
| Data steward | Map data to shared standards |
| Catalogue manager or data custodian | Catalogue APIs and data services |
| Data quality lead or analyst | Check data after each integration |
| Programme or project lead | Avoid bespoke, closed integrations |
| Commercial or technology lead | Ask for open standards and documented APIs at every boundary |
Document and content management
Managing unstructured information: documents, content and records.O: This playbook's own synthesis of published guidance
- DAM capabilities
- CR-15 Records, retention and disposal
- Maturity topics
- 7. Managing your data 8. Protecting your data
- Drill down
Knowledge area activities: 3 activities, each with steps, outputs, evidence and who does what.
- Records and information counterpart
- The core of records management: capture, classification, retention and disposal.
How each role uses it
| Role | Use |
|---|---|
| Chief data officer | Align data and records strategies |
| Lead policy coordinator | Reconcile the asset register with the information asset register |
| Data owner | Own records and data consistently |
| Data steward | Apply retention schedules |
| Catalogue manager or data custodian | Record retention and disposal in entries |
| Data quality lead or analyst | Check documents behind key data items |
| Programme or project lead | Plan records transfer when systems retire |
| Commercial or technology lead | Make sure tools apply your retention schedule |
Reference and master data
Agreeing and maintaining the shared, authoritative versions of key entities and code lists.O: This playbook's own synthesis of published guidance
- DAM capabilities
- CR-11 Interoperability, data standards and identifiers CR-14 Reference data, master data and authoritative sources
- Maturity topics
- 3. Having the right systems 7. Managing your data
- Drill down
Knowledge area activities: 7 activities, each with steps, outputs, evidence and who does what.
- Records and information counterpart
- Authority files and controlled vocabularies.
How each role uses it
| Role | Use |
|---|---|
| Chief data officer | Sponsor shared reference data |
| Lead policy coordinator | Spot duplicate assets |
| Data owner | Own the master version of key entities |
| Data steward | Maintain code lists and identifiers |
| Catalogue manager or data custodian | Link assets that share reference data |
| Data quality lead or analyst | Check codes against the reference list |
| Programme or project lead | Reuse existing reference data, do not copy it |
| Commercial or technology lead | Buy master data tools whose rules and data can be exported |
Data warehousing and business intelligence
Bringing data together for analysis, reporting and decisions.O: This playbook's own synthesis of published guidance
- DAM capabilities
- CR-04 Performance measurement and annual review CR-29 Benefits realisation and evaluation
- Maturity topics
- 5. Making decisions with data 10. Taking responsibility for data
- Drill down
Knowledge area activities: 4 activities, each with steps, outputs, evidence and who does what.
- Records and information counterpart
- Retention of reports and derived records.
How each role uses it
| Role | Use |
|---|---|
| Chief data officer | Use quality statements in decisions |
| Lead policy coordinator | Report progress from catalogue data |
| Data owner | Know where your data is reused |
| Data steward | Record derived data sets |
| Catalogue manager or data custodian | Catalogue analytical products that are critical |
| Data quality lead or analyst | Publish quality alongside reports |
| Programme or project lead | Plan reporting needs early |
| Commercial or technology lead | Make sure reporting tools read data through open routes |
Metadata management
Describing data so people and machines can find, understand and trust it.O: This playbook's own synthesis of published guidance
- DAM capabilities
- CR-03 Central reporting, assurance and arm's length body coordination CR-05 Identify and scope critical data assets CR-06 Data cataloguing and metadata management CR-13 Catalogue and quality tooling
- Maturity topics
- 3. Having the right systems 4. Knowing the data you have 7. Managing your data 10. Taking responsibility for data
- Drill down
Data cataloguing playbook: 8 steps, each with its tasks, roles, templates and standards.
- Mobilise
- Discover candidates
- Test and designate
- Confirm ownership
- Describe
- Catalogue and expose
- Report to GDS
- Maintain and review
Knowledge area activities: 2 activities, each with steps, outputs, evidence and who does what.
- Records and information counterpart
- Records metadata (ISO 23081) and the information asset register.
How each role uses it
| Role | Use |
|---|---|
| Chief data officer | Require complete metadata for the return |
| Lead policy coordinator | Build the return from catalogue records |
| Data owner | Approve entries for your assets |
| Data steward | Keep descriptions accurate |
| Catalogue manager or data custodian | Run the catalogue and harvest metadata |
| Data quality lead or analyst | Record quality metadata |
| Programme or project lead | Make metadata a delivery output |
| Commercial or technology lead | Test a full catalogue export and re-import before you sign |
Data quality
Defining, measuring and improving how fit data is for its purposes.O: This playbook's own synthesis of published guidance
- DAM capabilities
- CR-04 Performance measurement and annual review CR-08 Data quality management through action plans CR-09 Data quality issue management CR-13 Catalogue and quality tooling CR-18 AI readiness and data and AI ethics CR-30 Equality and inclusion in data
- Maturity topics
- 3. Having the right systems 5. Making decisions with data 6. Managing and using data ethically 7. Managing your data 10. Taking responsibility for data
- Drill down
Data quality playbook: 8 steps, each with its tasks, roles, templates and standards.
- Identify critical data
- Define rules and targets
- Measure a baseline
- Prioritise and set goals
- Fix causes at source
- Report openly
- Repeat and sustain
- Review every year
Knowledge area activities: 1 activities, each with steps, outputs, evidence and who does what.
- Records and information counterpart
- Integrity and authenticity of records.
How each role uses it
| Role | Use |
|---|---|
| Chief data officer | Fund fixes where quality blocks outcomes |
| Lead policy coordinator | Collate DQAP status |
| Data owner | Set targets and accept risks |
| Data steward | Run checks and log issues |
| Catalogue manager or data custodian | Show quality in entries |
| Data quality lead or analyst | Run the DQAP |
| Programme or project lead | Profile and reconcile in migrations |
| Commercial or technology lead | Require quality rules you can read, export and run elsewhere |
Data and records life cycles side by side
| Data life cycle | Records life cycle | Where DAM acts | Who |
|---|---|---|---|
| Plan and design | Plan what records are needed | Identify critical assets; design metadata and rules | Owner, architect, records manager |
| Acquire or create | Create and capture | Validate at collection; catalogue on creation | Service owner, steward |
| Store and secure | Store and protect | Record classification, location and recovery objectives | Custodian, security |
| Use and share | Use and provide access | Publish quality; record sharing arrangements | Owner, data protection officer |
| Maintain and improve | Review and update | Annual review of entries and DQAP | Steward, data quality lead |
| Archive or dispose | Appraise, transfer or destroy | Close or update entries; transfer where the Public Records Act applies | Records manager, owner |
Records and information management frameworks and standards
- Information management guidanceV: Verified against the primary source on 2026-11-05
- Manage information: guidance for governmentV: Verified against the primary source on 2026-11-05
- Digital records transferV: Verified against the primary source on 2026-11-05
- Public Records Act 1958V: Verified against the primary source on 2026-11-05
- 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
- ISO 23081-1:2017 Metadata for records: principlesS: Found by web search; the site blocked automated checking, so open it before relying on it
- Government Knowledge and Information Management ProfessionV: 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
Drilling down from the wheel: what it would takeO: This playbook's own synthesis of published guidance
Today a slice opens the card for its knowledge area further down this page, and the three areas the DAM Policy covers list their playbook steps. A full drill-down would take every reader from a knowledge area to its activities, and from an activity to its tasks, roles, templates, measures and standards, as the three DAM playbooks already do. This is an assessment by this portal, not a commitment.
| Level | What exists now | What is needed |
|---|---|---|
| 1. Knowledge area | Built for all 11 areas: DAM capabilities, maturity topics, the records counterpart and how each role uses it. | Nothing more for the MVP. |
| 2. Activities | Built for all 11 areas. Governance, metadata and data quality list their playbook steps; the other 8 areas have activities on the Knowledge areas page, staged from first return to business as usual (version 1.14.0). | Review of each area's activities by the profession that owns it. |
| 3. Tasks and products | Built: every activity has steps, outputs, evidence, a measure, who does what, the requirements it supports and the standards that apply. Templates exist for the three DAM playbooks and are linked where they fit. | Templates and learning modules for the new areas, starting with data architecture (BL-36). |
| 4. Standards and evidence | Built: the rulebook, the standards that apply at each step of the three DAM playbooks, and the standards for each of the 36 activities on the Knowledge areas page (version 1.14.0). | Expert review of the standards mapped to the new activities. |
For every knowledge area
- Done in version 1.14.0: the Knowledge areas page is generated from its own content file, so a change to an area needs content rather than code.
- The same route without the picture: each slice links to its area, and a list beside the wheel gives keyboard and screen reader users every area, activity and task.
- An owner for each area from the profession that does the work (security, records, architecture, integration, analysis). This is the largest dependency.
- Copyright: DAMA-DMBOK is DAMA International's copyrighted work. The portal can name the knowledge areas and link to DAMA, but activity lists must be written fresh or licensed.
- Edition risk: DAMA International started a 3.0 edition in 2025. Its project page gives no publication date, and secondary sources say 2027. The areas may change, so their names stay in the content file, not in code.
- Remaining effort: expert review of each area's activities by the profession that owns it, and, where an area needs it, templates and learning like the three DAM playbooks.
Data architecture as a fourth capability playbook
Data architecture can become a fourth capability playbook, built the same way as the other three. The data architecture and models supplement and the entity and relationship list (T-CAT-4) were a start. Version 1.14.0 added five data architecture activities, each with steps, a measure, who does what and the standards that apply. What is left is mostly people: review and ownership by architecture leads, then templates and learning.
| Part | What exists now | What is needed | Effort |
|---|---|---|---|
| Purpose and scope | The supplement's summary | The question the playbook answers, what is in and out of scope, and how it relates to the DAM Policy, which does not require it | S |
| Step by step | 5 activities on the Knowledge areas page (version 1.14.0): map where critical assets live, name authoritative sources, draw data flows, set a target architecture, make architecture review a gate in change | Review by architecture leads, then promotion to playbook steps | S |
| Roles and who does what | A RACI for each of the 5 activities, led by the architect role | Check the roles against the architect roles in the Government Digital and Data Profession Capability Framework | S |
| Templates | T-CAT-4, the entity and relationship list; activities reuse T-CAT-1, T-CAT-2, T-GOV-3 and T-GOV-6 | Templates for a target architecture and architecture decision records | M |
| Measures and escalation | A measure for each activity, such as the share of critical assets with a named authoritative source | Escalation through the governance ladder | S |
| Standards | Standards for each of the 5 activities, from the rulebook | Checked by architecture leads | S |
| Learning | None | At least one learning module with an exercise | M |
| Checks and tests | The supplement's checks | Build validation, a site check and deliberate-break tests, as for the other playbooks | S |
| Ownership and review | None | Architecture leads, such as a design authority or the architecture community, agree to own and review it. This portal cannot set architecture standards. | L |
Effort: S is days, M is one to two weeks, L depends on other teams. These are this portal's estimates, not measured.
When
After the MVP. Phase 1 and the January 2027 baseline return need only governance, metadata and data quality. Start with data architecture in Phase 2, from January 2027, because the policy's source data test already links it to the DAM Policy. Add other areas only where the profession that owns them agrees to own the content.
Risks
- Scope creep away from the DAM Policy, adding burden for organisations that only need to make the return.
- Guidance in areas other teams own may conflict with theirs. Signpost first, and write only with them.
- Every new playbook adds content to review each year.
On the backlog
A quick first pass, not a substitute for a full assessment. Choose the description closest to your organisation today. Answers are kept in this browser only and nothing is sent anywhere.
DAM strands
Government maturity topics
Read each topic's rows on GOV.UK first, then choose the level most rows match.
How the government model lines up with widely used industry models. These are approximate alignments made for this portalO: This playbook's own synthesis of published guidance, using general knowledge of the industry modelsK: General knowledge, not checked against a source in this release; the owners of those models have not checked them.
| Government level | CMMI level | ISO 8000-61 process view | Note |
|---|---|---|---|
| Beginning | Initial | Processes performed ad hoc | Little defined practice. |
| Emerging | Managed | Processes performed and managed in places | Practice depends on individuals. |
| Learning | Defined | Processes defined and repeatable | The DAM Policy minimum sits around here for critical assets. |
| Developing | Quantitatively managed | Processes measured | Measures drive decisions. |
| Mastering | Optimising | Processes continually improved | Improvement is systematic. |
| Knowledge area | Capabilities |
|---|---|
| Data architecture | CR-12 CR-32 |
| Data governance | CR-01 CR-02 CR-03 CR-04 CR-05 CR-07 CR-10 CR-17 CR-18 CR-19 CR-20 CR-21 CR-22 CR-23 CR-24 CR-25 CR-27 CR-28 CR-29 CR-30 |
| Data integration and interoperability | CR-11 CR-26 CR-32 |
| Data modelling and design | CR-12 |
| Data quality | CR-04 CR-08 CR-09 CR-13 CR-18 CR-30 |
| Data security | CR-16 CR-17 CR-19 CR-31 |
| Data storage and operations | CR-10 CR-15 CR-26 |
| Data warehousing and business intelligence | CR-04 CR-29 |
| Document and content management | CR-15 |
| Metadata management | CR-03 CR-05 CR-06 CR-13 |
| Reference and master data | CR-11 CR-14 |
| Component | Capabilities |
|---|---|
| Analytics management | CR-18 |
| Business and data architecture | CR-05 CR-06 CR-12 CR-14 |
| Data and technology architecture | CR-06 CR-11 CR-12 CR-13 CR-26 CR-32 |
| Data control environment | CR-03 CR-10 CR-15 CR-16 CR-17 CR-19 CR-31 |
| Data governance | CR-01 CR-03 CR-04 CR-07 CR-20 CR-22 CR-27 CR-28 CR-30 |
| Data management program and funding | CR-21 CR-24 CR-25 CR-29 |
| Data management strategy and business case | CR-01 CR-02 CR-23 CR-24 |
| Data quality management | CR-04 CR-08 CR-09 |
Model owners: 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; Capability Maturity Model Integration (CMMI)V: Verified against the primary source on 2026-11-05.
Was this page useful? Tell us Tell us privately, without GitHub