Playbooks Level: Practitioner
Capability playbooks
Activities and templates for the capabilities beyond governance, cataloguing and quality that the DAM Policy depends on: strategy, tools, risk, suppliers, skills, culture, maturity, investment, assurance, legacy, handover, benefits and exit.
In brief
- 13 capabilities, 40 activities and 16 templates.
- Each capability has activities for before your first return, before your second, and for business as usual.
- Each links to the same capability in the capability model, the knowledge areas, the data portals compass and the asset governance explorer.
Draft. Draft by this portal for review by the professions that own each capability. Not government guidance.
The DAM Policy names three capabilities, but meeting it rests on more: strategy, tools, risk, suppliers, skills, culture, maturity, investment, assurance, legacy, handover, benefits and exit. Each capability below has activities for before your first return, before your second, and for business as usual, with a template to start from.
Names and email addresses. Your own working copies can name the people who hold each role and give their work email addresses, handled under your organisation's data protection rules. Do not publish them: anything you put on GitHub or anywhere public should name roles only.
New to this, or leading it? Start with what to aim for in your first year, then come back to the capabilities you need.
Three stages
- Start: before your first returnWhat the DAM Policy needs now, so the return is complete and true.
- Build: before your second returnMakes the next return easier, and makes critical assets safer to reuse.
- Embed: business as usualKeeps the work going without a project, and prepares critical assets for AI and wider sharing.
All activities at a glance
Governance, cataloguing and quality have their own playbooks. Data management areas are on Knowledge areas. The capability model shows all 32 capabilities and where each is covered.
Download every activity as CSV.
CR-02 · Direction and oversight · Implicit in the policy · 3 activities
Data strategy and prioritisation by reuse value
Business as usual and change
See this capability in: Capability model · Capability playbook · Knowledge area activities (1) · Data portals compass · Asset governance explorer
Why it matters for the DAM Policy: The policy asks you to identify critical data assets, but not which to improve first. A short, published way of ranking them by reuse value, outcomes and risk turns the list into a plan and shows why some assets come first.O: This playbook's own synthesis of published guidance
Usually led by: Chief data officer. Content owner: The chief data officer, with strategy and portfolio teams.
Already in the knowledge areas
Delivery and change actions this takes further
STR-1 · Start: before your first return
Rank critical assets by what they make possible
Goal: You can say which critical assets matter most and why, in one page.O: This playbook's own synthesis of published guidance
Steps
- List the critical assets you are reporting.
- Score each on reuse value, the outcomes it supports, the people affected and the risk if it fails, using the scorecard.
- Note where legacy systems, poor quality or missing ownership hold an asset back.
- Agree the top ten with the data governance board and record the decision.
- You produce
- Prioritisation scorecard
- Board decision on the top ten
- Evidence it is done
- The board's decision log records the ranking and the reasons.
- Measure
- Share of critical assets scored.
- Who does what
- Accountable: Chief data officer
- Responsible (does the work): Lead policy coordinator
- Consulted: Data owner, Data governance board
- DAM Policy requirements it supports
- DAM-R14, DAM-R11
- Capabilities it builds
- Data strategy and prioritisation by reuse value, Identify and scope critical data assets
- Templates
- Critical data asset prioritisation scorecard
- Standards and guidance
- A blueprint for modern digital governmentV: Verified against the primary source on 2026-11-05
- National Data LibraryV: Verified against the primary source on 2026-11-05
STR-2 · Build: before your second return
Put the ranking into the data strategy
Goal: The data strategy names the assets it depends on and the outcomes they serve.O: This playbook's own synthesis of published guidance
Steps
- Link each strategic objective to the critical assets it needs.
- Set a target for each top asset, such as owner in post, metadata complete or quality in range.
- Publish the ranking method with the strategy so teams can apply it to new assets.
- You produce
- Data strategy with named assets and targets
- Evidence it is done
- The strategy names critical assets and targets for them.
- Measure
- Strategic objectives that name the assets they depend on.
- Who does what
- Accountable: Chief data officer
- Responsible (does the work): Lead policy coordinator
- Consulted: Data governance board
- Informed: Data owner
- DAM Policy requirements it supports
- DAM-R08
- Capabilities it builds
- Data strategy and prioritisation by reuse value, Investment, business cases and value
- Standards and guidance
- A blueprint for modern digital governmentV: Verified against the primary source on 2026-11-05
- A roadmap for modern digital government 2025 to 2030V: Verified against the primary source on 2026-11-05
STR-3 · Embed: business as usual
Re-rank every year with the return
Goal: Priorities follow what changed, not what was decided once.O: This playbook's own synthesis of published guidance
Steps
- Re-score assets during the annual review, using the same scorecard.
- Show what moved up or down and why.
- Feed the changes into investment and business planning.
- You produce
- Updated ranking
- Evidence it is done
- Each year's ranking is kept with the reasons for changes.
- Measure
- Years with a re-ranking on record.
- Who does what
- Accountable: Chief data officer
- Responsible (does the work): Lead policy coordinator
- Consulted: Data owner, Data governance board
- DAM Policy requirements it supports
- DAM-R04
- Capabilities it builds
- Data strategy and prioritisation by reuse value, Performance measurement and annual review
- Standards and guidance
- Data Maturity Assessment for Government: FrameworkV: Verified against the primary source on 2026-11-05
Templates
Working copies may name people; anything published uses roles. Why.
Critical data asset prioritisation scorecard (T-STR-1)
Business as usual and change
- Asset identifier
- Asset title
- Reuse value (1 to 5)
- Outcomes supported
- People affected
- Effect on inequality if it fails
- Legacy or technical debt risk (1 to 5)
- Quality risk (1 to 5)
- Ownership in place (yes or no)
- Total score
- Rank
- Reason
- Agreed by (role or forum)
- Date
CR-13 · Data management enablers · Implicit in the policy · 4 activities
Catalogue and quality tooling
Business as usual and change
See this capability in: Capability model · Capability playbook · Data portals compass · Asset governance explorer
Why it matters for the DAM Policy: Catalogues, quality checks, lineage and master data need tools, and a tool chosen badly locks data in. The ready-made requirements and procurement templates on the Tools and interoperability page let you ask for what the policy needs and test it before you sign.O: This playbook's own synthesis of published guidance
Usually led by: Commercial lead. Content owner: Commercial, digital and data teams together.
Delivery and change actions this takes further
TOOL-1 · Start: before your first return
Map the tools you have against what the policy needs
Goal: You know which capabilities your tools cover, which they miss and when contracts end.O: This playbook's own synthesis of published guidance
Steps
- List the tools used for cataloguing, quality, lineage, master data, governance workflow and records.
- Record the owner, contract end date and how each connects to the others.
- Mark each against the functional requirements for its kind of tool, Musts first.
- Note gaps the next return would expose.
- You produce
- Tool inventory and gap list
- Evidence it is done
- Each tool has an owner, a contract end date and a gap assessment.
- Measure
- Tools assessed against the Must requirements.
- Who does what
- Accountable: Chief data officer
- Responsible (does the work): Design authority or solution architect, Commercial lead
- Consulted: Catalogue manager, Data quality lead or analyst
- DAM Policy requirements it supports
- DAM-R02, DAM-R16
- Capabilities it builds
- Catalogue and quality tooling, Data architecture and data services
- Templates
- Tool requirements schedule
- Standards and guidance
- The Technology Code of PracticeV: Verified against the primary source on 2026-11-05
- Choosing technology: an introductionV: Verified against the primary source on 2026-11-05
TOOL-2 · Build: before your second return
Run a request for information with ready-made requirements
Goal: Suppliers answer the same questions, so answers can be compared.O: This playbook's own synthesis of published guidance
Steps
- Choose the kinds of tool you need and copy their requirements into the schedule.
- Change priorities to suit, and agree them with your commercial team.
- Publish the RFI through your usual route, and search Find a Tender and G-Cloud for how others specified similar tools.
- Score the answers, then shortlist for a proof of concept.
- You produce
- RFI pack
- Scored responses
- Shortlist
- Evidence it is done
- Every response is scored against the same requirements.
- Measure
- Requirements answered with evidence.
- Who does what
- Accountable: Commercial lead
- Responsible (does the work): Design authority or solution architect
- Consulted: Catalogue manager, Data quality lead or analyst, Data steward
- DAM Policy requirements it supports
- DAM-R16
- Capabilities it builds
- Catalogue and quality tooling, Avoiding future legacy: open standards, portability and exit
- Templates
- Request for information response form
- Standards and guidance
- 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
- Find a TenderV: Verified against the primary source on 2026-11-05
- The Sourcing PlaybookV: Verified against the primary source on 2026-11-05
TOOL-3 · Build: before your second return
Prove it with your own data before you sign
Goal: The tool does what the supplier says, with your data and your other tools.O: This playbook's own synthesis of published guidance
Steps
- Load test copies of two of your critical assets.
- Export everything and import it into another product or an empty instance; record what is lost.
- Show quality results in the catalogue through an open route, and capture lineage from a pipeline you own.
- Score each requirement on what you saw.
- You produce
- Proof of concept test log
- Evaluation scores
- Evidence it is done
- A test log with a result for every Must.
- Measure
- Must requirements proved, not only claimed.
- Who does what
- Accountable: Design authority or solution architect
- Responsible (does the work): Catalogue manager, Data quality lead or analyst
- Consulted: Commercial lead
- DAM Policy requirements it supports
- DAM-R16
- Capabilities it builds
- Catalogue and quality tooling, Avoiding future legacy: open standards, portability and exit
- Templates
- Evaluation and moderation sheet, Proof of concept test log
- Standards and guidance
- Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05
- Choosing technology: an introductionV: Verified against the primary source on 2026-11-05
TOOL-4 · Embed: business as usual
Check before every renewal
Goal: You can still leave, and the tool still meets the policy.O: This playbook's own synthesis of published guidance
Steps
- Repeat the full export test each year before renewal.
- Re-score the Must requirements, and record any that have slipped.
- Decide to renew, renegotiate or replace, and record the decision.
- You produce
- Renewal check
- Evidence it is done
- An export test and a decision before each renewal.
- Measure
- Renewals with an export test on record.
- Who does what
- Accountable: Commercial lead
- Responsible (does the work): Design authority or solution architect
- Consulted: Catalogue manager
- DAM Policy requirements it supports
- DAM-R04
- Capabilities it builds
- Catalogue and quality tooling, Avoiding future legacy: open standards, portability and exit
- Standards and guidance
- Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05
- Technology Code of Practice point 11: define your purchasing strategyV: Verified against the primary source on 2026-11-05
Templates
Working copies may name people; anything published uses roles. Why.
Tool requirements schedule (T-PRC-1)
Business as usual and change
Functional requirements tab (12 fields)
- Requirement ID
- Kind of tool
- Requirement
- Priority (MoSCoW)
- Weight
- How to prove it
- Capability
- DAM Policy requirement
- Supplier response
- Supplier evidence
- Score (0 to 4)
- Evaluator notes
Non-functional requirements tab (10 fields)
- Requirement ID
- Theme
- Requirement
- Priority (MoSCoW)
- Weight
- How to prove it
- Supplier response
- Supplier evidence
- Score (0 to 4)
- Evaluator notes
Contract clauses tab (6 fields)
- Clause ID
- Clause
- What to include
- Why it matters
- Agreed by commercial (yes or no)
- Notes
Download the workbook (OpenDocument spreadsheet, 3 tabs) · Functional requirements (CSV) · Non-functional requirements (CSV) · Contract clauses (CSV) · All templates (CSV)
Request for information response form (T-PRC-2)
Change programmes
- Section
- Question ID
- Question
- Supplier answer
- Meets now or partly or roadmap (with date) or no
- Evidence offered
- Clarification asked
- Score (0 to 4)
- Evaluator notes
Evaluation and moderation sheet (T-PRC-3)
Change programmes
- Supplier
- Requirement ID
- Priority (MoSCoW)
- Must met (pass or fail)
- Evaluator 1 score
- Evaluator 2 score
- Moderated score
- Weight
- Weighted score
- Reason for moderated score
- Moderated by (role)
- Date
Proof of concept test log (T-PRC-4)
Change programmes
- Test ID
- Requirement ID
- Test carried out
- Data used (test copy)
- Expected result
- Actual result
- Pass or fail
- Content lost on export
- Tested by (role)
- Date
- Evidence location
CR-19 · Protection, ethics and trust · Explicit in the policy · 3 activities
Data risk management
Business as usual and change
See this capability in: Capability model · Capability playbook · Knowledge area activities (3) · Data portals compass · Asset governance explorer
Why it matters for the DAM Policy: A critical data asset that is lost, wrong or misused is a risk to services and people. Recording those risks on the same registers as other risks puts them in front of the people who decide.O: This playbook's own synthesis of published guidance
Usually led by: Data owner. Content owner: Data owners, with the risk and assurance teams.
Already in the knowledge areas
Delivery and change actions this takes further
RISK-1 · Start: before your first return
Record the main risk to each critical asset
Goal: Every critical asset has at least one risk on a register someone reviews.O: This playbook's own synthesis of published guidance
Steps
- For each critical asset, ask what would happen if it was unavailable, wrong, exposed or not kept.
- Record the worst credible risk on the corporate or programme risk register, with the owner as risk owner.
- Score it with your organisation's risk method, and link it to the asset's catalogue record.
- You produce
- Data risks on the register
- Evidence it is done
- Each critical asset has a linked risk with an owner.
- Measure
- Critical assets with a recorded risk.
- Who does what
- Accountable: Data owner
- Responsible (does the work): Data steward
- Consulted: Lead policy coordinator
- Informed: Data governance board
- DAM Policy requirements it supports
- DAM-R05
- Capabilities it builds
- Data risk management
- Templates
- Data risk register entry
- Standards and guidance
- The Orange Book: management of riskV: Verified against the primary source on 2026-11-05
RISK-2 · Build: before your second return
Set risk appetite for data
Goal: Owners know how much risk they can accept and when to escalate.O: This playbook's own synthesis of published guidance
Steps
- Agree a risk appetite statement for data with the board, for availability, accuracy, privacy and retention.
- Set escalation thresholds and who they go to.
- Use exceptions, with an expiry date, for risks accepted outside appetite.
- You produce
- Data risk appetite statement
- Evidence it is done
- The board has approved a data risk appetite.
- Measure
- Risks outside appetite with an action or a dated exception.
- Who does what
- Accountable: Data governance board
- Responsible (does the work): Chief data officer
- Consulted: Data owner, Data protection officer
- DAM Policy requirements it supports
- DAM-R08
- Capabilities it builds
- Data risk management, Accountable leadership and policy oversight
- Standards and guidance
- The Orange Book: management of riskV: Verified against the primary source on 2026-11-05
RISK-3 · Embed: business as usual
Review data risks with the asset review
Goal: Risks stay current as assets and systems change.O: This playbook's own synthesis of published guidance
Steps
- Review each asset's risks in its annual review.
- Close risks that have gone and add new ones from quality issues, incidents and audits.
- Report the top data risks to the board each quarter.
- You produce
- Reviewed risks
- Quarterly board report
- Evidence it is done
- Each risk shows a review date in the last year.
- Measure
- Data risks reviewed in the last 12 months.
- Who does what
- Accountable: Data owner
- Responsible (does the work): Data steward
- Informed: Data governance board
- DAM Policy requirements it supports
- DAM-R04
- Capabilities it builds
- Data risk management, Performance measurement and annual review
- Standards and guidance
- The Orange Book: management of riskV: Verified against the primary source on 2026-11-05
Templates
Working copies may name people; anything published uses roles. Why.
Data risk register entry (T-RSK-1)
Business as usual and change
- Risk ID
- Asset identifier
- Risk (cause, event, effect)
- Kind (availability, accuracy, privacy, security, retention, supplier)
- Risk owner (role)
- Likelihood
- Impact
- Score
- Within appetite (yes or no)
- Controls in place
- Actions
- Action owner (role)
- Due date
- Exception reference
- Last reviewed
CR-20 · Protection, ethics and trust · Implicit in the policy · 3 activities
Third-party and supplier data
Business as usual and change
See this capability in: Capability model · Capability playbook · Knowledge area activities (1) · Data portals compass · Asset governance explorer
Why it matters for the DAM Policy: Many critical assets sit with suppliers or come from them. If the contract does not say who owns the data and how it comes back, the organisation can lose the asset or its history.O: This playbook's own synthesis of published guidance
Usually led by: Commercial lead. Content owner: Commercial teams with data owners.
Already in the knowledge areas
Delivery and change actions this takes further
SUPP-1 · Start: before your first return
Find the critical assets held or supplied by third parties
Goal: You know which critical assets depend on a supplier, and on which contract.O: This playbook's own synthesis of published guidance
Steps
- For each critical asset, record any supplier that holds, processes or provides it.
- Name the contract, its end date and whether it covers data ownership, processing and return.
- Mark gaps for the next renewal.
- You produce
- Third-party data register
- Evidence it is done
- Every critical asset held by a supplier names the contract.
- Measure
- Supplier-held critical assets with ownership and return covered in the contract.
- Who does what
- Accountable: Data owner
- Responsible (does the work): Commercial lead
- Consulted: Data protection officer, Catalogue manager
- DAM Policy requirements it supports
- DAM-R01, DAM-R02
- Capabilities it builds
- Third-party and supplier data, Data protection and lawful sharing
- Templates
- Third-party data register entry
- Standards and guidance
- The Mid-Tier Contract: Schedule 20 (Processing Data)V: Verified against the primary source on 2026-11-05
- Model Services ContractV: Verified against the primary source on 2026-11-05
SUPP-2 · Build: before your second return
Put data terms in every new contract
Goal: New contracts protect critical data from the start.O: This playbook's own synthesis of published guidance
Steps
- Use the contract clauses on the Tools and interoperability page as a checklist.
- Include a data processing schedule wherever personal data is processed.
- Require metadata to be supplied with the data, in the government format.
- You produce
- Contract clause checklist completed
- Evidence it is done
- New contracts that touch critical assets include the clauses.
- Measure
- New contracts with the data clauses.
- Who does what
- Accountable: Commercial lead
- Consulted: Data owner, Data protection officer, Design authority or solution architect
- DAM Policy requirements it supports
- DAM-R16
- Capabilities it builds
- Third-party and supplier data, Avoiding future legacy: open standards, portability and exit
- Standards and guidance
- 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
SUPP-3 · Embed: business as usual
Test the return of data before contracts end
Goal: Data comes back complete when a contract ends.O: This playbook's own synthesis of published guidance
Steps
- A year before a contract ends, ask for a test return of the data and its metadata.
- Check completeness and format against what the contract says.
- Fix gaps before the exit, not after.
- You produce
- Return test result
- Evidence it is done
- A test return before each relevant contract ends.
- Measure
- Contracts ending with a successful test return.
- Who does what
- Accountable: Data owner
- Responsible (does the work): Commercial lead, Data custodian
- Consulted: Data quality lead or analyst
- DAM Policy requirements it supports
- DAM-R10
- Capabilities it builds
- Third-party and supplier data, Legacy migration and decommissioning
- Standards and guidance
- Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05
Templates
Working copies may name people; anything published uses roles. Why.
Third-party data register entry (T-SUP-1)
Business as usual and change
- Asset identifier
- Supplier
- Role (holds, processes, provides)
- Contract reference
- Contract end date
- Data ownership stated (yes or no)
- Data processing schedule in place (yes or no)
- Return of data and metadata stated (yes or no)
- Last test return date
- Gaps
- Action owner (role)
- Renewal decision due
CR-21 · People and culture · Implicit in the policy · 3 activities
Data skills, capability and literacy
Business as usual
See this capability in: Capability model · Capability playbook · Data portals compass · Asset governance explorer
Why it matters for the DAM Policy: Owners, stewards and catalogue managers are often new to the role and doing it part time. Knowing what each role needs to know, and giving them a short route to it, is what makes the other capabilities work.O: This playbook's own synthesis of published guidance
Usually led by: Chief data officer. Content owner: The chief data officer with learning and development teams.
Delivery and change actions this takes further
SKILL-1 · Start: before your first return
Check what each data role needs to know
Goal: Everyone named in a data role knows what is expected of them.O: This playbook's own synthesis of published guidance
Steps
- List everyone named as owner, steward, custodian or catalogue manager.
- Ask each to rate themselves against the learning outcomes for their role on the Learning page.
- Point each to the modules that close their gaps.
- You produce
- Skills assessment
- Learning plan per person
- Evidence it is done
- Every named role holder has a learning plan.
- Measure
- Named role holders who have completed their core modules.
- Who does what
- Accountable: Chief data officer
- Responsible (does the work): Lead policy coordinator
- Informed: Data owner, Data steward
- DAM Policy requirements it supports
- DAM-R05, DAM-R14
- Capabilities it builds
- Data skills, capability and literacy, Data ownership and stewardship
- Templates
- Data role skills assessment and learning plan
- Standards and guidance
- Data skills for allV: Verified against the primary source on 2026-11-05
- Government Digital and Data Profession Capability FrameworkV: Verified against the primary source on 2026-11-05
SKILL-2 · Build: before your second return
Build data roles into jobs and objectives
Goal: Data roles are part of the job, not extra to it.O: This playbook's own synthesis of published guidance
Steps
- Add data ownership and stewardship to job descriptions and objectives where they apply.
- Map specialist roles to the Digital and Data Capability Framework.
- Give time for the role, and recognise it in performance reviews.
- You produce
- Updated objectives and job descriptions
- Evidence it is done
- Named role holders have the role in their objectives.
- Measure
- Role holders with the role in their objectives.
- Who does what
- Accountable: Chief data officer
- Responsible (does the work): Lead policy coordinator
- Consulted: Data owner
- DAM Policy requirements it supports
- DAM-R05
- Capabilities it builds
- Data skills, capability and literacy, Data culture and engagement with users
- Standards and guidance
- Government Digital and Data Profession Capability FrameworkV: Verified against the primary source on 2026-11-05
- Success ProfilesV: Verified against the primary source on 2026-11-05
SKILL-3 · Embed: business as usual
Keep a community of practice going
Goal: People in data roles learn from each other, inside and across organisations.O: This playbook's own synthesis of published guidance
Steps
- Run a regular session for owners and stewards to share problems and fixes.
- Join the cross-government data management community and its boards.
- Induct new role holders within a month of appointment.
- You produce
- Community sessions
- Induction for new role holders
- Evidence it is done
- New role holders are inducted within a month.
- Measure
- Days from appointment to induction.
- Who does what
- Accountable: Lead policy coordinator
- Responsible (does the work): Data steward
- Informed: Data owner
- DAM Policy requirements it supports
- DAM-R10
- Capabilities it builds
- Data skills, capability and literacy, Cross-boundary collaboration
- Standards and guidance
- Data skills for allV: Verified against the primary source on 2026-11-05
- Government Knowledge and Information Management ProfessionV: Verified against the primary source on 2026-11-05
Templates
Working copies may name people; anything published uses roles. Why.
Data role skills assessment and learning plan (T-SKL-1)
Business as usual
- Person (role in published copies)
- Data role
- Learning outcome
- Self-rating (1 to 4)
- Gap
- Module or course
- Due date
- Completed date
- Line manager agreed (yes or no)
CR-22 · People and culture · Implicit in the policy · 3 activities
Data culture and engagement with users
Business as usual
See this capability in: Capability model · Capability playbook · Data portals compass · Asset governance explorer
Why it matters for the DAM Policy: People use data well when they can find it, trust it and see why it matters. Talking to the people who use and are described by critical data shows what to fix first and keeps the work grounded.O: This playbook's own synthesis of published guidance
Usually led by: Chief data officer. Content owner: The chief data officer with communications and user research.
CULT-1 · Start: before your first return
Find out who uses each critical asset and what gets in their way
Goal: Owners know their users and their main problems.O: This playbook's own synthesis of published guidance
Steps
- For each top critical asset, list the teams and services that use it.
- Ask a few users what stops them using it well, and record the answers.
- Feed the main problems into the quality plan and the catalogue record.
- You produce
- User list and problems per asset
- Evidence it is done
- Top critical assets have a list of users and their problems.
- Measure
- Top assets with user feedback in the last year.
- Who does what
- Accountable: Data owner
- Responsible (does the work): Data steward
- Consulted: Data users
- DAM Policy requirements it supports
- DAM-R04, DAM-R06
- Capabilities it builds
- Data culture and engagement with users, Data quality management through action plans
- Templates
- Data user feedback log
- Standards and guidance
- Service StandardV: Verified against the primary source on 2026-11-05
- Service Manual: finding participants for user researchV: Verified against the primary source on 2026-11-05
CULT-2 · Build: before your second return
Tell people what changed because of their feedback
Goal: Users see that raising a problem leads to a fix.O: This playbook's own synthesis of published guidance
Steps
- Publish a short note each quarter on what was fixed and what is planned.
- Name the owner and the way to raise new problems.
- Include the people the data describes where the asset is about them.
- You produce
- Quarterly note
- Evidence it is done
- A note published each quarter.
- Measure
- Problems raised that have a response.
- Who does what
- Accountable: Lead policy coordinator
- Responsible (does the work): Data owner, Data steward
- Informed: People the data describes
- DAM Policy requirements it supports
- DAM-R04
- Capabilities it builds
- Data culture and engagement with users, Equality and inclusion in data
- Standards and guidance
- Writing to GOV.UK standards - style guidesV: Verified against the primary source on 2026-11-05
- Data and AI Ethics FrameworkV: Verified against the primary source on 2026-11-05
CULT-3 · Embed: business as usual
Make data work visible to leaders
Goal: Leaders ask about data assets as they ask about money and people.O: This playbook's own synthesis of published guidance
Steps
- Report the state of critical assets to the executive board with other corporate measures.
- Include one story a quarter of a decision or service improved by better data.
- Thank people in data roles publicly.
- You produce
- Board report
- Stories of use
- Evidence it is done
- Critical assets appear in executive reporting.
- Measure
- Executive board meetings that discuss data assets.
- Who does what
- Accountable: Chief data officer
- Responsible (does the work): Lead policy coordinator
- Informed: Data governance board
- DAM Policy requirements it supports
- DAM-R08
- Capabilities it builds
- Data culture and engagement with users, Accountable leadership and policy oversight
- Standards and guidance
- Data Maturity Assessment for Government: FrameworkV: Verified against the primary source on 2026-11-05
Templates
Working copies may name people; anything published uses roles. Why.
Data user feedback log (T-ENG-1)
Business as usual
- Date
- Asset identifier
- User group
- Problem or request
- Effect on their work
- Owner (role)
- Action
- Status
- Response sent (date)
CR-23 · People and culture · Implicit in the policy · 3 activities
Maturity assessment and continuous improvement
Business as usual
See this capability in: Capability model · Capability playbook · Data portals compass · Asset governance explorer
Why it matters for the DAM Policy: Maturity assessment shows where you are, sets a realistic target and shows progress to leaders and the centre. Using the government framework means your results can be compared and built on.O: This playbook's own synthesis of published guidance
Usually led by: Chief data officer. Content owner: The chief data officer and the lead policy coordinator.
Delivery and change actions this takes further
MAT-1 · Start: before your first return
Take a baseline
Goal: You know your starting level for each strand of data asset management.O: This playbook's own synthesis of published guidance
Steps
- Use the self-assessment on the Capability model page for a first view.
- Where you can, run the Data Maturity Assessment for Government with the people who do the work.
- Record the level for each strand, with the evidence for it.
- You produce
- Baseline levels with evidence
- Evidence it is done
- A baseline with evidence for each level.
- Measure
- Strands with an evidenced baseline.
- Who does what
- Accountable: Chief data officer
- Responsible (does the work): Lead policy coordinator
- Consulted: Data owner, Data steward
- DAM Policy requirements it supports
- DAM-R14
- Capabilities it builds
- Maturity assessment and continuous improvement
- Templates
- Maturity baseline and improvement plan
- Standards and guidance
- Data Maturity Assessment for Government: FrameworkV: Verified against the primary source on 2026-11-05
- Government data maturity hubV: Verified against the primary source on 2026-11-05
MAT-2 · Build: before your second return
Set targets and an improvement plan
Goal: Each strand has a target level, a date and the actions to reach it.O: This playbook's own synthesis of published guidance
Steps
- Set a target level for each strand, starting with the level the DAM Policy needs for critical assets.
- Choose the actions from the playbooks that move each strand up.
- Agree owners and dates with the board.
- You produce
- Improvement plan
- Evidence it is done
- The board has approved targets and a plan.
- Measure
- Plan actions on track.
- Who does what
- Accountable: Data governance board
- Responsible (does the work): Chief data officer, Lead policy coordinator
- DAM Policy requirements it supports
- DAM-R08
- Capabilities it builds
- Maturity assessment and continuous improvement, Data strategy and prioritisation by reuse value
- Standards and guidance
- Data Maturity Assessment for Government: FrameworkV: Verified against the primary source on 2026-11-05
MAT-3 · Embed: business as usual
Reassess every year
Goal: Progress is measured, not assumed.O: This playbook's own synthesis of published guidance
Steps
- Repeat the assessment each year, with the same method.
- Compare with the baseline and explain changes.
- Reset targets and actions.
- You produce
- Annual reassessment
- Evidence it is done
- An assessment each year with evidence.
- Measure
- Strands that moved up a level.
- Who does what
- Accountable: Chief data officer
- Responsible (does the work): Lead policy coordinator
- Informed: Data governance board
- DAM Policy requirements it supports
- DAM-R04
- Capabilities it builds
- Maturity assessment and continuous improvement, Performance measurement and annual review
- Standards and guidance
- Data Maturity Assessment for Government: FrameworkV: Verified against the primary source on 2026-11-05
- Capability Maturity Model Integration (CMMI)V: Verified against the primary source on 2026-11-05
Templates
Working copies may name people; anything published uses roles. Why.
Maturity baseline and improvement plan (T-MAT-1)
Business as usual and change
- Strand
- Baseline level
- Evidence for baseline
- Target level
- Target date
- Actions (playbook activity IDs)
- Action owner (role)
- Checkpoint level at 6 months
- Checkpoint level at 12 months
- Notes
CR-24 · Delivery, change and value · Explicit in the policy · 3 activities
Investment, business cases and value
Change programmes
See this capability in: Capability model · Capability playbook · Knowledge area activities (1) · Data portals compass · Asset governance explorer
Why it matters for the DAM Policy: Data work competes for money. A business case that names the critical assets, the benefits and the cost of doing nothing gets funded; one that talks about data in general does not.O: This playbook's own synthesis of published guidance
Usually led by: Senior responsible owner. Content owner: Senior responsible owners and finance business partners.
Already in the knowledge areas
Delivery and change actions this takes further
INV-1 · Start: before your first return
Name the critical assets in every business case
Goal: Business cases say which critical assets they create, change or depend on.O: This playbook's own synthesis of published guidance
Steps
- Add a data assets section to your business case template.
- For each asset, state its owner, its catalogue record and what the change does to it.
- Ask for this at the first approval point.
- You produce
- Data assets section in business cases
- Evidence it is done
- Business cases list the critical assets they affect.
- Measure
- Business cases approved with the section completed.
- Who does what
- Accountable: Senior responsible owner
- Responsible (does the work): Programme or project manager
- Consulted: Data owner, Chief data officer
- DAM Policy requirements it supports
- DAM-R01, DAM-R05
- Capabilities it builds
- Investment, business cases and value, Integration with programmes, spend control and assurance
- Templates
- Data assets section for a business case
- Standards and guidance
- The Green Book and accompanying guidanceV: Verified against the primary source on 2026-11-05
INV-2 · Build: before your second return
Make the case for investing in data assets
Goal: Investment in data assets is argued with costs, benefits and the cost of doing nothing.O: This playbook's own synthesis of published guidance
Steps
- Use the five cases of the Green Book business case structure.
- Count the cost of the current state, such as manual cleansing, duplicate collection and failed sharing.
- Show benefits as measures you will track, with an owner for each.
- You produce
- Business case for data investment
- Evidence it is done
- A business case with measurable benefits and owners.
- Measure
- Benefits with an owner and a baseline.
- Who does what
- Accountable: Senior responsible owner
- Responsible (does the work): Programme or project manager
- Consulted: Chief data officer
- DAM Policy requirements it supports
- DAM-R08
- Capabilities it builds
- Investment, business cases and value, Benefits realisation and evaluation
- Standards and guidance
- The Green Book and accompanying guidanceV: Verified against the primary source on 2026-11-05
- The Magenta BookV: Verified against the primary source on 2026-11-05
INV-3 · Embed: business as usual
Fund the yearly cycle in business as usual
Goal: The annual review, catalogue and quality work have a budget that does not end with a project.O: This playbook's own synthesis of published guidance
Steps
- Cost the yearly cycle: reviews, catalogue upkeep, quality checks and the return.
- Put it in the business-as-usual budget of the teams that own the assets.
- Review the cost each year with the ranking of assets.
- You produce
- Business-as-usual budget line
- Evidence it is done
- A budget line for the yearly cycle.
- Measure
- Owning teams with a budget for the cycle.
- Who does what
- Accountable: Chief data officer
- Responsible (does the work): Data owner
- Consulted: Senior responsible owner
- DAM Policy requirements it supports
- DAM-R04
- Capabilities it builds
- Investment, business cases and value, Ownership transition and handover to business as usual
- Standards and guidance
- The Green Book and accompanying guidanceV: Verified against the primary source on 2026-11-05
Templates
Working copies may name people; anything published uses roles. Why.
Data assets section for a business case (T-INV-1)
Change programmes
- Asset identifier
- Asset title
- Created or changed or depends on
- Owner (role)
- Catalogue record
- Current cost of the problem
- Benefit expected
- Measure
- Baseline
- Target
- Benefit owner (role)
- Risk if not done
CR-25 · Delivery, change and value · Inferred in the policy · 3 activities
Integration with programmes, spend control and assurance
Change programmes
See this capability in: Capability model · Capability playbook · Knowledge area activities (1) · Data portals compass · Asset governance explorer
Why it matters for the DAM Policy: Programmes create and retire critical assets. Asking three questions at existing checkpoints, which assets, who owns them and are they catalogued, catches problems before they become legacy.O: This playbook's own synthesis of published guidance
Usually led by: Programme office and assurance. Content owner: Programme offices, spend control and assurance teams.
Already in the knowledge areas
Delivery and change actions this takes further
ASSR-1 · Start: before your first return
Add data asset questions to existing checkpoints
Goal: Spend control, gate reviews and service assessments ask about critical data.O: This playbook's own synthesis of published guidance
Steps
- Add three questions to internal spend control and gate review templates.
- Agree with the assessment team that service assessments will look for the evidence.
- Brief programme managers on what good evidence looks like.
- You produce
- Updated checkpoint templates
- Evidence it is done
- Checkpoint templates include the questions.
- Measure
- Checkpoints that asked the questions this year.
- Who does what
- Accountable: Programme office and assurance
- Responsible (does the work): Lead policy coordinator
- Consulted: Design authority or solution architect
- Informed: Senior responsible owner
- DAM Policy requirements it supports
- DAM-R05, DAM-R02
- Capabilities it builds
- Integration with programmes, spend control and assurance
- Templates
- Data asset checkpoint questions
- Standards and guidance
- Set up a commercial or digital and technology spend controls pipelineV: 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
- Implementing integrated assurance for major projectsV: Verified against the primary source on 2026-11-05
ASSR-2 · Build: before your second return
Put data checkpoints into the assurance plan
Goal: Large programmes plan their data assurance from the start.O: This playbook's own synthesis of published guidance
Steps
- Add data asset checkpoints to the integrated assurance and approval plan.
- Name who gives the assurance and what evidence they need.
- Record findings and actions with the other assurance findings.
- You produce
- Assurance plan with data checkpoints
- Evidence it is done
- Major programmes have data checkpoints in their assurance plans.
- Measure
- Programmes with data checkpoints planned.
- Who does what
- Accountable: Senior responsible owner
- Responsible (does the work): Programme office and assurance
- Consulted: Chief data officer
- DAM Policy requirements it supports
- DAM-R08
- Capabilities it builds
- Integration with programmes, spend control and assurance, Data risk management
- Standards and guidance
- Implementing integrated assurance for major projectsV: Verified against the primary source on 2026-11-05
- Government Functional Standard GovS 002: Project DeliveryV: Verified against the primary source on 2026-11-05
ASSR-3 · Embed: business as usual
Learn from checkpoint findings
Goal: Common problems are fixed in guidance, not found again and again.O: This playbook's own synthesis of published guidance
Steps
- Collect findings about data assets from all checkpoints each quarter.
- Spot repeated problems and fix the guidance or templates.
- Share the lessons with programme managers.
- You produce
- Quarterly lessons
- Evidence it is done
- A quarterly summary of findings and fixes.
- Measure
- Repeated findings falling over time.
- Who does what
- Accountable: Programme office and assurance
- Responsible (does the work): Lead policy coordinator
- Consulted: Design authority or solution architect
- DAM Policy requirements it supports
- DAM-R04
- Capabilities it builds
- Integration with programmes, spend control and assurance, Maturity assessment and continuous improvement
- Standards and guidance
- Government Functional Standard GovS 002: Project DeliveryV: Verified against the primary source on 2026-11-05
Templates
Working copies may name people; anything published uses roles. Why.
Data asset checkpoint questions (T-ASR-1)
Change programmes
- Checkpoint (spend control or gate or service assessment)
- Programme
- Critical assets created or changed or retired
- Owner named for each (yes or no)
- Catalogue record for each (yes or no)
- Quality plan for each (yes or no)
- Migration and exit planned (yes or no)
- Evidence seen
- Finding
- Action
- Action owner (role)
- Due date
CR-26 · Delivery, change and value · Inferred in the policy · 3 activities
Legacy migration and decommissioning
Change programmes
See this capability in: Capability model · Capability playbook · Knowledge area activities (2) · Data portals compass · Asset governance explorer
Why it matters for the DAM Policy: Legacy systems hold critical data that is hard to get out. A migration that does not reconcile the data, or a switch-off that forgets an asset, loses data the organisation must keep.O: This playbook's own synthesis of published guidance
Usually led by: Data migration lead. Content owner: Data migration leads with data owners.
Already in the knowledge areas
Delivery and change actions this takes further
LEG-1 · Start: before your first return
List the critical assets in each legacy system
Goal: You know what data each legacy system holds before anyone plans to replace it.O: This playbook's own synthesis of published guidance
Steps
- For each system with a planned end, list the critical assets it holds or feeds.
- Record what depends on them downstream.
- Mark data that must be kept for records or legal reasons.
- You produce
- Legacy data asset register
- Evidence it is done
- Each system with a planned end has its assets listed.
- Measure
- Legacy systems with an asset register.
- Who does what
- Accountable: Data owner
- Responsible (does the work): Data migration lead, Data custodian
- Consulted: Catalogue manager
- DAM Policy requirements it supports
- DAM-R01, DAM-R12
- Capabilities it builds
- Legacy migration and decommissioning, Identify and scope critical data assets
- Templates
- Legacy exit and migration plan
- Standards and guidance
- 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
LEG-2 · Build: before your second return
Migrate with reconciliation
Goal: Data arrives complete and correct, and you can prove it.O: This playbook's own synthesis of published guidance
Steps
- Agree mapping and transformation rules with the owner before migration.
- Reconcile counts, totals and samples between old and new, and record differences.
- Fix or accept differences, with the owner's decision recorded.
- You produce
- Migration plan
- Reconciliation report
- Evidence it is done
- A signed-off reconciliation for each migrated asset.
- Measure
- Migrated assets with a signed-off reconciliation.
- Who does what
- Accountable: Data owner
- Responsible (does the work): Data migration lead, Data quality lead or analyst
- Consulted: Data custodian
- DAM Policy requirements it supports
- DAM-R06
- Capabilities it builds
- Legacy migration and decommissioning, Data quality management through action plans
- Standards and guidance
- Managing legacy technologyV: Verified against the primary source on 2026-11-05
LEG-3 · Embed: business as usual
Switch off safely
Goal: Nothing needed is lost when a system is turned off.O: This playbook's own synthesis of published guidance
Steps
- Check every asset on the register is migrated, archived or disposed of under the schedule.
- Update the catalogue records, marking retired assets and what replaced them.
- Get the owner's sign-off before switch-off.
- You produce
- Decommissioning sign-off
- Evidence it is done
- The owner signs off before switch-off.
- Measure
- Switch-offs with owner sign-off.
- Who does what
- Accountable: Data owner
- Responsible (does the work): Data migration lead, Catalogue manager, Data custodian
- DAM Policy requirements it supports
- DAM-R04
- Capabilities it builds
- Legacy migration and decommissioning, Records, retention and disposal
- Standards and guidance
- Retiring your serviceV: Verified against the primary source on 2026-11-05
- Manage information: guidance for governmentV: Verified against the primary source on 2026-11-05
Templates
Working copies may name people; anything published uses roles. Why.
Legacy exit and migration plan (T-LEG-1)
Change programmes
Assets in the system tab (7 fields)
- Asset identifier
- Asset title
- Owner (role)
- Downstream dependants
- Must be kept (records or legal)
- Disposition (migrate, archive, dispose)
- Target system
Reconciliation tab (8 fields)
- Asset identifier
- Check
- Old value
- New value
- Difference
- Decision
- Decided by (role)
- Date
Switch-off checklist tab (5 fields)
- Item
- Done (yes or no)
- Evidence
- Signed off by (role)
- Date
Download the workbook (OpenDocument spreadsheet, 3 tabs) · Assets in the system (CSV) · Reconciliation (CSV) · Switch-off checklist (CSV) · All templates (CSV)
CR-27 · Delivery, change and value · Implicit in the policy · 3 activities
Ownership transition and handover to business as usual
Change programmes
See this capability in: Capability model · Capability playbook · Data portals compass · Asset governance explorer
Why it matters for the DAM Policy: Projects create assets and then close. If no one in business as usual takes over ownership, stewardship and the yearly cycle, the asset decays and becomes the next legacy problem.O: This playbook's own synthesis of published guidance
Usually led by: Senior responsible owner. Content owner: Senior responsible owners and the receiving business owners.
Delivery and change actions this takes further
HAND-1 · Start: before your first return
Name the business-as-usual owner early
Goal: Every asset a project creates has an owner who will be there after the project.O: This playbook's own synthesis of published guidance
Steps
- At the start of delivery, name the business-as-usual owner and steward for each new asset.
- Involve them in design decisions about the data.
- Record them in the catalogue from the first release.
- You produce
- Named owners for new assets
- Evidence it is done
- New assets have a business-as-usual owner in the catalogue.
- Measure
- New assets with a named business-as-usual owner.
- Who does what
- Accountable: Senior responsible owner
- Responsible (does the work): Programme or project manager, Data owner
- DAM Policy requirements it supports
- DAM-R05
- Capabilities it builds
- Ownership transition and handover to business as usual, Data ownership and stewardship
- Templates
- Handover to business as usual checklist
- Standards and guidance
- Role of the senior responsible ownerV: Verified against the primary source on 2026-11-05
- What each role does in a service teamV: Verified against the primary source on 2026-11-05
HAND-2 · Build: before your second return
Hand over with a checklist
Goal: Business as usual receives everything needed to run the asset.O: This playbook's own synthesis of published guidance
Steps
- Use the handover checklist: owner, steward, catalogue record, quality plan, risks, contracts, documentation and budget.
- Walk through it with the receiving owner.
- Do not close the project until the owner signs.
- You produce
- Signed handover checklist
- Evidence it is done
- A signed checklist for each asset.
- Measure
- Projects closed with signed handovers.
- Who does what
- Accountable: Senior responsible owner
- Responsible (does the work): Programme or project manager, Data owner
- Consulted: Programme office and assurance
- DAM Policy requirements it supports
- DAM-R05, DAM-R06
- Capabilities it builds
- Ownership transition and handover to business as usual
- Standards and guidance
- Government Functional Standard GovS 002: Project DeliveryV: Verified against the primary source on 2026-11-05
HAND-3 · Embed: business as usual
Check six months after handover
Goal: The asset is still owned, catalogued and checked after the project team has gone.O: This playbook's own synthesis of published guidance
Steps
- Six months after handover, check the owner, catalogue record and quality plan are current.
- Record and fix any gaps.
- Share lessons with the programme office.
- You produce
- Post-handover check
- Evidence it is done
- A check six months after each handover.
- Measure
- Handovers still complete at six months.
- Who does what
- Accountable: Lead policy coordinator
- Responsible (does the work): Data owner
- Informed: Programme office and assurance
- DAM Policy requirements it supports
- DAM-R04
- Capabilities it builds
- Ownership transition and handover to business as usual, Maturity assessment and continuous improvement
- Standards and guidance
- Government Functional Standard GovS 002: Project DeliveryV: Verified against the primary source on 2026-11-05
Templates
Working copies may name people; anything published uses roles. Why.
Handover to business as usual checklist (T-HND-1)
Change programmes
- Asset identifier
- Business-as-usual owner (role)
- Steward (role)
- Catalogue record current (yes or no)
- Quality plan in place (yes or no)
- Risks transferred (yes or no)
- Contracts and licences transferred (yes or no)
- Documentation and runbooks (location)
- Budget for the yearly cycle (yes or no)
- Open issues
- Signed by receiving owner (role)
- Date
CR-29 · Delivery, change and value · Inferred in the policy · 3 activities
Benefits realisation and evaluation
Change programmes
See this capability in: Capability model · Capability playbook · Knowledge area activities (1) · Data portals compass · Asset governance explorer
Why it matters for the DAM Policy: Showing what better data asset management achieved keeps funding and support. Benefits that are named, measured and owned can be evaluated; general claims cannot.O: This playbook's own synthesis of published guidance
Usually led by: Senior responsible owner. Content owner: Benefit owners, with analysts.
Already in the knowledge areas
Delivery and change actions this takes further
BEN-1 · Start: before your first return
Pick a few measures and record the baseline
Goal: You can show change, because you know where you started.O: This playbook's own synthesis of published guidance
Steps
- Choose three to five measures, such as reuse requests met, duplicate collections stopped or time spent cleansing.
- Record today's value for each, and how you measured it.
- Name an owner for each benefit.
- You produce
- Benefits register with baselines
- Evidence it is done
- Each measure has a baseline and an owner.
- Measure
- Benefits with a recorded baseline.
- Who does what
- Accountable: Senior responsible owner
- Responsible (does the work): Programme or project manager
- Consulted: Data owner
- DAM Policy requirements it supports
- DAM-R08
- Capabilities it builds
- Benefits realisation and evaluation
- Templates
- Benefits register
- Standards and guidance
- The Magenta BookV: Verified against the primary source on 2026-11-05
BEN-2 · Build: before your second return
Track and report the benefits
Goal: Leaders see progress against the baseline each quarter.O: This playbook's own synthesis of published guidance
Steps
- Measure each benefit on its schedule, the same way as the baseline.
- Report progress to the board with the other data measures.
- Explain changes, including those not caused by the work.
- You produce
- Quarterly benefits report
- Evidence it is done
- Benefits reported each quarter against the baseline.
- Measure
- Benefits on track.
- Who does what
- Accountable: Senior responsible owner
- Responsible (does the work): Programme or project manager
- Informed: Data governance board
- DAM Policy requirements it supports
- DAM-R04
- Capabilities it builds
- Benefits realisation and evaluation, Performance measurement and annual review
- Standards and guidance
- The Magenta BookV: Verified against the primary source on 2026-11-05
- The AQuA BookV: Verified against the primary source on 2026-11-05
BEN-3 · Embed: business as usual
Evaluate after a year
Goal: You know what worked, what did not and why.O: This playbook's own synthesis of published guidance
Steps
- Plan a proportionate evaluation using the Magenta Book.
- Compare results with the business case.
- Publish the lessons for other organisations.
- You produce
- Evaluation report
- Evidence it is done
- An evaluation within a year of the main change.
- Measure
- Lessons published.
- Who does what
- Accountable: Senior responsible owner
- Responsible (does the work): Programme or project manager
- Consulted: Chief data officer
- DAM Policy requirements it supports
- DAM-R08
- Capabilities it builds
- Benefits realisation and evaluation, Maturity assessment and continuous improvement
- Standards and guidance
- The Magenta BookV: Verified against the primary source on 2026-11-05
Templates
Working copies may name people; anything published uses roles. Why.
Benefits register (T-BEN-1)
Business as usual and change
- Benefit ID
- Benefit
- Measure
- How measured
- Baseline
- Baseline date
- Target
- Target date
- Measurement frequency
- Latest value
- Benefit owner (role)
- Assets involved
- Notes
CR-32 · Delivery, change and value · Inferred in the policy · 3 activities
Avoiding future legacy: open standards, portability and exit
Business as usual and change
See this capability in: Capability model · Capability playbook · Knowledge area activities (2) · Data portals compass · Asset governance explorer
Why it matters for the DAM Policy: Today's new system is tomorrow's legacy. Requiring open formats, documented schemas and a tested exit at the start keeps critical data movable for as long as it is needed.O: This playbook's own synthesis of published guidance
Usually led by: Design authority or solution architect. Content owner: Design authorities and commercial teams.
Already in the knowledge areas
Delivery and change actions this takes further
EXIT-1 · Start: before your first return
Ask three questions of every new system
Goal: No new system holds critical data you cannot get out.O: This playbook's own synthesis of published guidance
Steps
- Ask whether the data can be exported in full, in an open format, with a published schema.
- Ask whether the export has been tested.
- Ask what leaving would cost and how long it would take.
- You produce
- Answers recorded at design review
- Evidence it is done
- Design reviews record the three answers.
- Measure
- New systems with recorded answers.
- Who does what
- Accountable: Design authority or solution architect
- Consulted: Commercial lead, Data owner
- DAM Policy requirements it supports
- DAM-R16
- Capabilities it builds
- Avoiding future legacy: open standards, portability and exit, Interoperability, data standards and identifiers
- Templates
- Exit and portability plan
- Standards and guidance
- Prevent technical debt and legacyV: Verified against the primary source on 2026-11-05
- Open standards for governmentV: Verified against the primary source on 2026-11-05
EXIT-2 · Build: before your second return
Write and cost the exit plan
Goal: Leaving is planned and costed before you sign.O: This playbook's own synthesis of published guidance
Steps
- Write an exit plan for each system holding critical data, with the formats, steps and time it would take.
- Cost it and put the cost in the business case.
- Put the plan in the contract.
- You produce
- Exit plan
- Evidence it is done
- Systems holding critical data have a costed exit plan.
- Measure
- Systems with a costed exit plan.
- Who does what
- Accountable: Design authority or solution architect
- Responsible (does the work): Commercial lead
- Consulted: Data owner
- DAM Policy requirements it supports
- DAM-R16
- Capabilities it builds
- Avoiding future legacy: open standards, portability and exit, Third-party and supplier data
- Standards and guidance
- Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05
- Model Services ContractV: Verified against the primary source on 2026-11-05
EXIT-3 · Embed: business as usual
Test the exit every year
Goal: The exit plan still works.O: This playbook's own synthesis of published guidance
Steps
- Run a full export each year and check it against the plan.
- Record anything lost or changed.
- Update the plan and raise any gap with the supplier.
- You produce
- Annual exit test
- Evidence it is done
- An exit test each year.
- Measure
- Systems with an exit test in the last year.
- Who does what
- Accountable: Design authority or solution architect
- Responsible (does the work): Data custodian
- Consulted: Commercial lead
- DAM Policy requirements it supports
- DAM-R04
- Capabilities it builds
- Avoiding future legacy: open standards, portability and exit
- Standards and guidance
- Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05
Templates
Working copies may name people; anything published uses roles. Why.
Exit and portability plan (T-EXT-1)
Business as usual and change
- System
- Critical assets held
- Export formats
- Schema published (location)
- Last full export test
- Content lost in test
- Steps to exit
- Time to exit
- Cost to exit
- In contract (yes or no)
- Owner (role)
- Next test due
Was this page useful? Tell us Tell us privately, without GitHub