Frameworks Level: Practitioner
Perspectives
What the DAM Policy means for data, digital, cyber, technology and commercial teams, and for tackling legacy, with what each should ask and do.
In brief
- Find your own community's lens.
- Each lens gives questions, actions for each capability, pitfalls and verified sources.
- A coverage assessment shows where the portal is strong and where it is still thin.
The DAM Policy is written from a data point of view, but delivering it depends on digital, cyber, technology and commercial teams. Each lens below says what the policy means for that community, what they should ask and do for each capability, and where this portal and the rulebook help.
Coverage assessment
How well this portal covers each capability through each lens, judged against the questions and actions each community needsO: This playbook's own synthesis of published guidance. Where a rating changed in this release, the earlier rating is shown.
| Lens | Data governance | Data cataloguing | Data quality |
|---|---|---|---|
| Data | Strong | Strong | Strong |
| Digital and service | Strong (was Partial) | Strong (was Partial) | Strong (was Partial) |
| Cyber and security | Strong (was Partial) | Partial (was Gap) | Partial (was Gap) |
| Technology and architecture | Strong (was Partial) | Strong (was Partial) | Strong (was Partial) |
| Commercial and suppliers | Strong (was Partial) | Partial (was Gap) | Partial (was Gap) |
| Legacy and technical debt | Strong (was Partial) | Strong (was Partial) | Strong (was Partial) |
Strong: questions, actions and verified sources for every capability. Partial: covered in general terms or for some capabilities. Gap: not covered.
Lens
Data
The policy's home lens: identify, describe, own and improve critical data assets, and report them.O: This playbook's own synthesis of published guidance
Questions to ask
- Which of our assets are critical, and do we agree why?
- Can someone outside our team find, understand and trust each asset from its catalogue entry?
- Who decides what good enough means for each asset?
What to do, by capability
Data governance
- Name an owner and steward for every critical asset.
- Run a data governance board that records decisions.
Data cataloguing
- Record the core metadata in a catalogue and report it to GDS.
- Use the cross-government Metadata Exchange Model terms.
Data quality
- Write a DQAP for every asset and log issues with priorities.
- Publish quality statements users can read.
Pitfalls
- Treating the return as the goal rather than better-managed data.
- Describing assets nobody owns.
Where to go next
Capabilities: CR-05 Identify and scope critical data assets CR-06 Data cataloguing and metadata management CR-07 Data ownership and stewardship CR-08 Data quality management through action plans
Practices: CH-11 Keep the yearly cycle running in business as usual CH-12 Assess maturity and set a target
Professions: Government Digital and Data Profession Analysis Function Knowledge and Information Management
Rulebook
- Data Maturity Assessment for Government: FrameworkV: Verified against the primary source on 2026-11-05
- Making government datasets ready for AIV: Verified against the primary source on 2026-11-05
Coverage: Covered across the three playbooks, the capability model and the sector supplements.
Lens
Digital and service
Services create, change and consume critical data. Service teams decide what is collected, how it is validated and what users see.O: This playbook's own synthesis of published guidance
Questions to ask
- Which critical assets does our service create or depend on?
- Do our forms and validation stop bad data at the point of collection?
- Are data services such as APIs documented, catalogued and owned like the data behind them?
What to do, by capability
Data governance
- Name the data owner as a stakeholder of the service from discovery.
- Show DAM evidence at service assessments.
Data cataloguing
- Catalogue data services and APIs alongside the data sets they expose.
- Publish API documentation that follows the government API standards.
Data quality
- Turn quality rules into form validation and API contract tests.
- Design forms so people can describe themselves accurately.
Pitfalls
- Collecting data the catalogue shows another service already holds.
- Treating an API as technical plumbing with no owner.
Where to go next
Capabilities: CR-12 Data architecture and data services CR-22 Data culture and engagement with users CR-25 Integration with programmes, spend control and assurance
Practices: CH-02 Use spend control and service assessments as checkpoints CH-13 Share and reuse safely across organisations
Professions: Government Digital and Data Profession
Rulebook
- Service StandardV: Verified against the primary source on 2026-11-05
- Service assessments and applying the Service StandardV: Verified against the primary source on 2026-11-05
- API technical and data standardsV: Verified against the primary source on 2026-11-05
- Retiring your serviceV: Verified against the primary source on 2026-11-05
Coverage: Strengthened in 1.6 with data service and API actions; user research with service teams is still to do (OR-04).
Lens
Cyber and security
Critical data assets are among the things most worth protecting. Security teams need to know which they are, and data teams need to know an asset can be recovered and trusted after an incident.O: This playbook's own synthesis of published guidance
Questions to ask
- Do our asset inventory and incident plans include every critical data asset?
- What is the recovery point and recovery time for each one, and who agreed it?
- After a restore, how do we know the data is complete and correct?
What to do, by capability
Data governance
- Link each critical asset to its CAF outcomes and to the SIRO's risk register.
- Agree recovery objectives with each data owner.
Data cataloguing
- Record classification, handling caveats and access rights accurately; scope depends on them.
- Keep the catalogue itself access-controlled where entries reveal sensitive holdings.
Data quality
- After any restore or suspected tampering, rerun the DQAP rules before the asset is used again.
- Treat unexplained quality drops as a possible security signal.
Pitfalls
- Assuming OFFICIAL means low risk; aggregation can raise sensitivity.
- A catalogue that becomes a map for attackers.
Where to go next
Capabilities: CR-16 Security classification and protective controls CR-19 Data risk management CR-31 Cyber resilience and incident response for data assets
Practices: CH-07 Manage data asset risk on the same registers CH-15 Prepare for a cyber incident affecting a critical asset
Professions: Government Cyber Profession Government Security Profession
Rulebook
- Cyber Assessment Framework (CAF)V: Verified against the primary source on 2026-11-05
- Government Cyber Security Strategy: 2022 to 2030V: Verified against the primary source on 2026-11-05
- Government Functional Standard GovS 007: SecurityV: Verified against the primary source on 2026-11-05
- Secure by designV: Verified against the primary source on 2026-11-05
- 10 Steps to Cyber SecurityV: Verified against the primary source on 2026-11-05
- Incident managementV: Verified against the primary source on 2026-11-05
- Government Security ClassificationsV: Verified against the primary source on 2026-11-05
Coverage: Was the thinnest lens. 1.6 adds a cyber resilience capability, an incident practice and seven verified security sources. Needs review by a security professional.
Lens
Technology and architecture
Platforms, integration and tooling decide whether critical data can be found, joined, checked and moved. Architecture choices made now set the cost of the next migration.O: This playbook's own synthesis of published guidance
Questions to ask
- Which systems and platforms hold each critical asset?
- Can metadata be harvested automatically rather than typed in?
- Are quality checks automated in the pipeline, or done by hand?
What to do, by capability
Data governance
- Record the system of record and data platform for each asset.
- Apply the Technology Code of Practice and Cloud First when assets move.
Data cataloguing
- Harvest metadata from platforms into the catalogue using DCAT and the Metadata Exchange Model.
- Expose catalogue entries through an API so central discovery services can collect them.
Data quality
- Run quality rules automatically in data pipelines and publish results.
- Version schemas and test changes against the DQAP rules before release.
Pitfalls
- Buying a catalogue tool before agreeing ownership and metadata.
- Bespoke integrations that only one supplier understands.
Where to go next
Capabilities: CR-11 Interoperability, data standards and identifiers CR-12 Data architecture and data services CR-13 Catalogue and quality tooling CR-14 Reference data, master data and authoritative sources
Practices: CH-04 Plan legacy exits from the asset register CH-14 Design out future legacy and lock-in
Professions: Government Digital and Data Profession
Rulebook
- The Technology Code of PracticeV: Verified against the primary source on 2026-11-05
- Government Cloud First policyV: Verified against the primary source on 2026-11-05
- API technical and data standardsV: Verified against the primary source on 2026-11-05
- Develop your data and APIs using a reference architectureV: Verified against the primary source on 2026-11-05
- Open standards for governmentV: Verified against the primary source on 2026-11-05
- Cloud security guidanceV: Verified against the primary source on 2026-11-05
Coverage: Strengthened in 1.6 with architecture, platform and automation actions and verified sources.
Lens
Commercial and suppliers
Many critical assets are held or processed by suppliers, and most tools are bought. Contracts decide who owns the data, what metadata and quality evidence the supplier must provide, and whether the data can leave.O: This playbook's own synthesis of published guidance
Questions to ask
- Which critical assets are held or processed by a supplier?
- Does each contract name the data owner and require metadata, quality reporting and full data return?
- When does each contract end, and is the exit plan tested?
What to do, by capability
Data governance
- Map contracts to the critical assets they touch, with end dates.
- Use model contract schedules for data, security and exit.
Data cataloguing
- Make catalogue-ready metadata a contract deliverable, in the government's terms.
- Require suppliers to keep catalogue entries current when they change the data.
Data quality
- Turn DQAP targets into service levels with credits.
- Require suppliers to report quality against the agreed rules.
Pitfalls
- Supplier terms that treat government data as the supplier's product.
- Exit plans that are never tested until the contract ends.
Where to go next
Capabilities: CR-20 Third-party and supplier data CR-24 Investment, business cases and value CR-32 Avoiding future legacy: open standards, portability and exit
Practices: CH-06 Build DAM into contracts CH-16 Use the buying routes and contract terms that protect data CH-01 Put data assets in the business case
Professions: Government Commercial Function Project Delivery
Rulebook
- The Sourcing PlaybookV: Verified against the primary source on 2026-11-05
- The Digital, Data and Technology PlaybookV: Verified against the primary source on 2026-11-05
- Model Services ContractV: Verified against the primary source on 2026-11-05
- The Mid-Tier Contract: Schedule 20 (Processing Data)V: Verified against the primary source on 2026-11-05
- PPN 020: Guidance on data protection legislationV: Verified against the primary source on 2026-11-05
- Procurement Act 2023V: Verified against the primary source on 2026-11-05
- Procurement Act 2023: guidance documentsV: Verified against the primary source on 2026-11-05
- G-Cloud 15 frameworkV: Verified against the primary source on 2026-11-05
- Set up a commercial or digital and technology spend controls pipelineV: Verified against the primary source on 2026-11-05
Coverage: Was thin, with one practice. 1.6 adds a buying-routes practice and verified commercial sources. Needs review by a commercial professional.
Lens
Legacy and technical debt
Legacy systems concentrate critical data that is hard to find, understand or trust, and that blocks better services. Getting data out safely, and not creating the next legacy, are both DAM work.O: This playbook's own synthesis of published guidance
Questions to ask
- Where are our largest concentrations of critical data in legacy systems?
- Which of them block outcomes for the people who most need services?
- What will stop the replacement becoming legacy in its turn?
What to do, by capability
Data governance
- Prioritise exits where legacy risk, value and inequality overlap.
- Keep ownership in step as assets migrate.
Data cataloguing
- Start every exit from the data asset register, as the legacy guidance asks.
- Record schemas and lineage before the old system goes.
Data quality
- Profile quality before migration and reconcile counts, totals and keys after.
- Use migration as the moment to fix root causes, not copy them.
Pitfalls
- Migrating data without its meaning or quality history.
- Replacing one closed system with another.
Where to go next
Capabilities: CR-26 Legacy migration and decommissioning CR-32 Avoiding future legacy: open standards, portability and exit CR-15 Records, retention and disposal
Practices: CH-04 Plan legacy exits from the asset register CH-05 Target legacy where it blocks outcomes and widens inequalities CH-14 Design out future legacy and lock-in
Professions: Government Digital and Data Profession Project Delivery
Rulebook
- Managing legacy technologyV: Verified against the primary source on 2026-11-05
- Prevent technical debt and legacyV: Verified against the primary source on 2026-11-05
- Retiring your serviceV: Verified against the primary source on 2026-11-05
- Information management guidanceV: Verified against the primary source on 2026-11-05
- Open standards for governmentV: Verified against the primary source on 2026-11-05
Coverage: Covered by the delivery and change practices; 1.6 adds future-legacy prevention.
Was this page useful? Tell us Tell us privately, without GitHub