Frameworks Level: Practitioner
Working together
How data, records and information, security, digital, technology, analysis, commercial and delivery professionals can act on the same critical assets.
In brief
- Ten practical recommendations, each with an action, an outcome and a measure.
- Communities and networks to join, filtered by role.
- A map of which professions contribute to which capabilities.
Recommendations
Data asset management needs data, records and information, security, digital, technology, analysis, commercial and delivery professionals to act on the same assets. These recommendations turn that into shared artefacts, routines and networks, each with a tangible outcome you can check.O: This playbook's own synthesis of published guidance
- 01
J-01
Keep one register of assets
Do: Reconcile the critical data asset list with the information asset register so each asset has one record, with the data owner and information asset owner linked.
Outcome: One list used by data, records and security teams; no asset is reported twice or missed.
Measure: Assets on both lists without a shared identifier: zero.
Who: Lead policy coordinator Information asset owner Catalogue manager
- 02
J-02
Use one glossary
Do: Publish one organisation glossary for data, records and security terms, linked to the cross-government vocabulary, and point catalogue entries to it.
Outcome: The same word means the same thing in a catalogue entry, a file plan and a risk register.
Measure: Critical assets whose key items link to glossary terms.
- 03
J-03
Run one board for data, information and security risk
Do: Bring the data governance board, information assurance and the senior information risk owner together, quarterly, with one agenda covering critical assets.
Outcome: Decisions on an asset consider data, records and security together.
Measure: Decisions recorded per quarter that cite more than one discipline.
Who: Chief data officer Data governance board Information asset owner
- 04
J-04
Put DAM checkpoints in every programme
Do: Agree with the programme office a standard set of DAM checks for business cases, gates and handover, and give programmes a named data contact.
Outcome: Programmes stop creating unowned, uncatalogued assets.
Measure: Programmes closing with every in-scope asset owned, catalogued and quality-planned.
Who: Chief data officer Programme office and assurance Senior responsible owner
- 05
J-05
Align retention with the data life cycle
Do: Map retention schedules to critical assets and record retention and disposal in catalogue entries.
Outcome: Data is kept as long as needed and no longer, with evidence.
Measure: Critical assets with a recorded retention rule.
- 06
J-06
Learn together
Do: Run a shared induction for owners, stewards, information asset owners and programme leads, using the recommended curriculum and this portal's modules.
Outcome: People in different professions use the same method and language.
Measure: Owners and stewards who completed the shared induction.
- 07
J-07
Join the right communities
Do: Give each role one community to join and one to watch, from the list on this page, and share what you learn at the board.
Outcome: Practice spreads across organisations instead of being reinvented.
Measure: Roles with a named community; lessons shared per quarter.
Who: Lead policy coordinator Data steward Data quality lead or analyst Catalogue manager
- 08
J-08
Rehearse an incident together
Do: Run a joint exercise where a critical asset is corrupted or exposed, involving security, records, data quality and the owner.
Outcome: Everyone knows their part in recovering and re-trusting an asset.
Measure: Critical assets covered by a tested recovery and quality check.
Who: Data owner Data custodian Data quality lead or analyst Data protection officer
- 09
J-09
Share contract clauses
Do: Keep a shared library of data, metadata, quality and exit clauses with the commercial team and reuse it in every relevant procurement.
Outcome: Suppliers face the same data obligations everywhere.
Measure: New contracts touching critical assets that use the shared clauses.
- 10
J-10
Report one set of measures
Do: Combine catalogue completeness, DQAP status, records compliance and security assurance for critical assets into one quarterly view.
Outcome: Leaders see one picture of how well critical assets are managed.
Measure: Quarterly view produced and discussed at the board.
Communities and networks
- Chief Data Officer CouncilV: Verified against the primary source on 2026-11-05Oversees implementation of the DAM Policy across government. For: Chief data officer
- Government Data Quality HubV: Verified against the primary source on 2026-11-05Data quality guidance, tools and support from the Office for National Statistics. For: Data quality lead or analyst, Data steward
- Government Data Quality CommunityV: Verified against the primary source on 2026-11-05Cross-government community for people working on data quality. For: Data quality lead or analyst, Data steward
- Data Standards AuthorityV: Verified against the primary source on 2026-11-05Sets and promotes government data standards. For: Catalogue manager or data custodian, Data steward
- Knowledge and Information Management profession groupV: Verified against the primary source on 2026-11-05Community for records, information and knowledge managers. For: Lead policy coordinator, Catalogue manager or data custodian
- Data engineering communityV: Verified against the primary source on 2026-11-05Cross-government community for data engineers. For: Data quality lead or analyst, Catalogue manager or data custodian
- Performance and data analysis communityV: Verified against the primary source on 2026-11-05Community for performance analysts and data analysts. For: Data quality lead or analyst
- API communityV: Verified against the primary source on 2026-11-05Community for people building and running government APIs. For: Catalogue manager or data custodian, Programme or project lead
- Technical architecture communityV: Verified against the primary source on 2026-11-05Community for technical and data architects. For: Programme or project lead, Catalogue manager or data custodian
- Data and AI ethics communityV: Verified against the primary source on 2026-11-05Community for data and AI ethics practitioners. For: Data owner, Data steward
- AI for government knowledge and information management communityV: Verified against the primary source on 2026-11-05Where KIM professionals discuss AI and information. For: Lead policy coordinator, Catalogue manager or data custodian
- Digital buying communityV: Verified against the primary source on 2026-11-05Community for people buying digital, data and technology. For: Programme or project lead
- Standards and assurance communityV: Verified against the primary source on 2026-11-05Community for service assessors and assurance practitioners. For: Programme or project lead
- Product and service communityV: Verified against the primary source on 2026-11-05Community for product managers and service owners. For: Programme or project lead, Data owner
- Analysis FunctionV: Verified against the primary source on 2026-11-05The cross-government network for analysts, including statisticians. For: Data quality lead or analyst
Who contributes to what
Professions that contribute to each capability, from the capability model. Use it to decide who to bring to the table for each asset.
See also Perspectives for what each community should ask and do, and Professions and skills for career routes.
Was this page useful? Tell us Tell us privately, without GitHub