{
 "meta": {
  "id": "DAMCP",
  "title": "Data Asset Management (DAM) capability playbooks",
  "short_title": "DAM capability playbooks",
  "subtitle": "Step-by-step guidance on data governance, data cataloguing and data quality for critical data assets in UK government",
  "keywords": [
   "data asset management",
   "DAM policy",
   "critical data assets",
   "data governance",
   "data catalogue",
   "metadata",
   "data quality",
   "DQAP",
   "data ownership",
   "UK government"
  ],
  "version": "1.10.1",
  "as_of": "2026-11-06",
  "review": "2027-02-05",
  "verified_on": "2026-11-05",
  "repo": "cyberdudeuk/dam-capability-playbooks",
  "site_url": "https://cyberdudeuk.github.io/dam-capability-playbooks/",
  "contact_form": "https://github.com/cyberdudeuk/dam-capability-playbooks/issues/new/choose",
  "contact_note": "Contact is by form only. Messages are published as issues in the portal's repository, so do not include personal or sensitive information.",
  "licence_content": "Open Government Licence v3.0",
  "licence_content_url": "https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
  "licence_code": "MIT",
  "status": "Prototype. Not an official GOV.UK service or published GDS guidance. Where it repeats GDS guidance, the GOV.UK page is the authority.",
  "profile": "Public sector, UK, UK central government (departments and arm's length bodies), official work. Grade G3 (shared material others will rely on).",
  "grade_reason": "Shared with departments and ALBs, so G3. It holds no personal data and makes no decisions about people, so not G4.",
  "intent": "Identify, consolidate and assemble the playbook material for the three capabilities the Data Asset Management (DAM) Policy rests on (data governance, data cataloguing and data quality) and publish it as one interactive portal on GitHub Pages, so that a lead policy coordinator, a data owner or a data steward has one place to start, can see what the policy requires, and can follow a method for each capability that joins up with the other two."
 },
 "sources": [
  {
   "id": "SRC-DAM",
   "title": "Data asset management policy in government",
   "publisher": "GDS",
   "type": "Policy",
   "url": "https://www.gov.uk/government/publications/data-asset-management-policy-in-government/data-asset-management-policy-in-government",
   "dates": "Published 27 May 2026; page metadata updated 9 September 2026",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "note": "The mandate. Mandatory for UK government departments and ALBs; optional for public corporations; not for councils."
  },
  {
   "id": "SRC-IDC",
   "title": "Identifying and recording critical data assets",
   "publisher": "GDS",
   "type": "Guidance",
   "url": "https://www.gov.uk/government/publications/identify-and-record-critical-data-assets/identifying-and-recording-critical-data-assets",
   "dates": "Published and updated 16 April 2026",
   "prov": "V",
   "caps": [
    "cat",
    "gov"
   ],
   "note": "Criticality (provided or acquired), the seven purposes, how to identify, ownership and annual review."
  },
  {
   "id": "SRC-MD",
   "title": "Recording metadata to describe critical data assets",
   "publisher": "GDS",
   "type": "Guidance",
   "url": "https://www.gov.uk/government/publications/record-metadata-to-describe-critical-data-assets/recording-metadata-to-describe-critical-data-assets",
   "dates": "Published 16 April 2026; page metadata updated 9 September 2026",
   "prov": "V",
   "caps": [
    "cat"
   ],
   "note": "The metadata properties to record for each critical data asset, and formatting rules."
  },
  {
   "id": "SRC-OWN",
   "title": "Data ownership model",
   "publisher": "GDS",
   "type": "Guidance",
   "url": "https://www.gov.uk/government/publications/data-ownership-in-government/data-ownership-model",
   "dates": "Published 16 April 2026; page metadata updated 9 September 2026",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "note": "Data owner, data steward and data custodian; relationship to IAOs and the SIRO; three compliance options."
  },
  {
   "id": "SRC-IAO",
   "title": "The role of information asset owners in government",
   "publisher": "GOV.UK",
   "type": "Guidance",
   "url": "https://www.gov.uk/government/publications/information-asset-owner-role-guidance",
   "dates": "Listed on the data.gov.uk data manual, 5 November 2026",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "note": "Mandatory IAO actions that any ownership option must still meet."
  },
  {
   "id": "SRC-GDQF",
   "title": "The Government Data Quality Framework",
   "publisher": "GOV.UK",
   "type": "Framework",
   "url": "https://www.gov.uk/government/publications/the-government-data-quality-framework/the-government-data-quality-framework",
   "dates": "Published 3 December 2020; page metadata updated 7 January 2026",
   "prov": "V",
   "caps": [
    "dq"
   ],
   "note": "Five principles, six dimensions and the data lifecycle."
  },
  {
   "id": "SRC-DQAP",
   "title": "Data quality action plan implementation guide",
   "publisher": "GDS",
   "type": "Guidance",
   "url": "https://www.gov.uk/government/publications/implement-a-data-quality-action-plan/data-quality-action-plan-implementation-guide",
   "dates": "Published 11 November 2025; updated 16 April 2026",
   "prov": "V",
   "caps": [
    "dq"
   ],
   "note": "The seven DQAP steps, the DQAP template and its RACI matrix."
  },
  {
   "id": "SRC-DQIF",
   "title": "Data quality issues framework",
   "publisher": "GDS",
   "type": "Method",
   "url": "https://www.gov.uk/government/publications/implement-a-data-quality-action-plan/data-quality-issues-framework",
   "dates": "Published 11 November 2025; updated 16 April 2026",
   "prov": "V",
   "caps": [
    "dq"
   ],
   "note": "Importance x impact, target ranges, bands and resolution timescales."
  },
  {
   "id": "SRC-MAN",
   "title": "Data manual, data management section (data.gov.uk)",
   "publisher": "GDS (National Data Library)",
   "type": "Index",
   "url": "https://www.data.gov.uk/data-manual/data-management/",
   "dates": "Read 5 November 2026",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "note": "The official index of the guidance above, plus the data maturity hub and capability framework."
  },
  {
   "id": "SRC-DMA",
   "title": "Data maturity assessment for government",
   "publisher": "GDS",
   "type": "Framework",
   "url": "https://www.gov.uk/government/collections/data-maturity-assessment-for-government",
   "dates": "Listed on the data manual, 5 November 2026",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "note": "The self-assessment used to show maturity across all three capabilities."
  },
  {
   "id": "SRC-MEM",
   "title": "UK Cross-Government Metadata Exchange Model (xGov MEM)",
   "publisher": "co-cddo on GitHub",
   "type": "Standard",
   "url": "https://co-cddo.github.io/ukgov-metadata-exchange-model/",
   "dates": "Repository read 5 November 2026",
   "prov": "V",
   "caps": [
    "cat"
   ],
   "note": "LinkML model based on DCAT; classes Dataset, DataService, Distribution, CataloguedResource. Endorsed for implementation by the Data Standards Authority Steering Board."
  },
  {
   "id": "SRC-DCAT",
   "title": "Data Catalog Vocabulary (DCAT) version 3",
   "publisher": "W3C",
   "type": "Standard",
   "url": "https://www.w3.org/TR/vocab-dcat-3/",
   "dates": "W3C Recommendation",
   "prov": "K",
   "caps": [
    "cat"
   ],
   "note": "The base vocabulary named in the metadata guidance and used by the MEM."
  },
  {
   "id": "SRC-DQV",
   "title": "Data on the Web Best Practices Data Quality Vocabulary (DQV)",
   "publisher": "W3C",
   "type": "Standard",
   "url": "https://www.w3.org/TR/vocab-dqv/",
   "dates": "W3C Working Group Note",
   "prov": "K",
   "caps": [
    "dq",
    "cat"
   ],
   "note": "How to publish quality measurements alongside a catalogue record."
  },
  {
   "id": "SRC-ODCS",
   "title": "Open Data Contract Standard",
   "publisher": "Bitol (Linux Foundation AI and Data)",
   "type": "Standard",
   "url": "https://bitol-io.github.io/open-data-contract-standard/latest/",
   "dates": "Referenced by the Data Quality Commons",
   "prov": "K",
   "caps": [
    "dq"
   ],
   "note": "Quality rules written as a data contract that survives a change of tool or supplier."
  },
  {
   "id": "SRC-DQC",
   "title": "Public Sector Data Quality Commons (portal and dqkit)",
   "publisher": "Open-source prototype on GitHub (not an official product)",
   "type": "Toolkit",
   "url": "https://cyberdudeuk.github.io/dq-commons/",
   "dates": "Repository read 5 November 2026 (v2.0.0)",
   "prov": "P",
   "caps": [
    "dq",
    "cat"
   ],
   "note": "The authoritative home of the data quality tools; this portal links to it and does not copy them."
  }
 ],
 "requirements": [
  {
   "id": "DAM-R01",
   "cap": "cat",
   "strength": "must",
   "src": "SRC-DAM",
   "prov": "V",
   "text": "Identify the data assets in scope: classified OFFICIAL (including handling markings such as 'personal'), meeting the critical data asset criteria, and inside your own data ownership accountabilities."
  },
  {
   "id": "DAM-R02",
   "cap": "cat",
   "strength": "must",
   "src": "SRC-DAM",
   "prov": "V",
   "text": "Identify and manage metadata about in-scope assets within your data catalogues."
  },
  {
   "id": "DAM-R03",
   "cap": "cat",
   "strength": "must",
   "src": "SRC-DAM",
   "prov": "V",
   "text": "Report in-scope assets to GDS. Departments provide metadata on their assets and coordinate and assure the returns of their ALBs."
  },
  {
   "id": "DAM-R04",
   "cap": "cat",
   "strength": "must",
   "src": "SRC-DAM",
   "prov": "V",
   "text": "Maintain metadata and review it every year."
  },
  {
   "id": "DAM-R05",
   "cap": "gov",
   "strength": "must",
   "src": "SRC-DAM",
   "prov": "V",
   "text": "Every identified asset has a named data owner, accountable for decisions about the data."
  },
  {
   "id": "DAM-R06",
   "cap": "dq",
   "strength": "must",
   "src": "SRC-DAM",
   "prov": "V",
   "text": "Every identified asset has a data quality action plan (DQAP) or an equivalent mechanism for managing its quality."
  },
  {
   "id": "DAM-R07",
   "cap": "dq",
   "strength": "should",
   "src": "SRC-DAM",
   "prov": "V",
   "text": "Where you already manage the quality of critical data, review those processes to confirm they cover every step of the DQAP implementation guide."
  },
  {
   "id": "DAM-R08",
   "cap": "gov",
   "strength": "must",
   "src": "SRC-DAM",
   "prov": "V",
   "text": "The chief data officer of each in-scope organisation implements the policy; the Chief Data Officer Council oversees implementation; the minister writes to ministers each year on progress."
  },
  {
   "id": "DAM-R09",
   "cap": "gov",
   "strength": "must",
   "src": "SRC-OWN",
   "prov": "V",
   "text": "Choose an ownership option (keep the IAO model, adopt the data ownership model, or a hybrid) and still meet the mandatory IAO actions, with governance covering accountability, reporting lines, assurance and data quality."
  },
  {
   "id": "DAM-R10",
   "cap": "gov",
   "strength": "must",
   "src": "SRC-IDC",
   "prov": "V",
   "text": "When a data owner leaves, tell the coordinating team, have a successor ready and give the successor's details so the metadata can be updated."
  },
  {
   "id": "DAM-R11",
   "cap": "cat",
   "strength": "should",
   "src": "SRC-IDC",
   "prov": "V",
   "text": "Each critical data asset supports at least one of the seven purposes: public service delivery; legislative, legal or contractual requirement; defence, national security and resilience; policy development and evaluation; official statistics; public interest; fraud and error."
  },
  {
   "id": "DAM-R12",
   "cap": "cat",
   "strength": "should",
   "src": "SRC-IDC",
   "prov": "V",
   "text": "If you designate a particular distribution of a data set, designate its source data set as well."
  },
  {
   "id": "DAM-R13",
   "cap": "cat",
   "strength": "should",
   "src": "SRC-MD",
   "prov": "V",
   "text": "Record the metadata properties set out in the metadata guidance, in plain English, with ISO 8601 dates and 'unknown' or 'not applicable' rather than blanks."
  },
  {
   "id": "DAM-R14",
   "cap": "gov",
   "strength": "should",
   "src": "SRC-IDC",
   "prov": "V",
   "text": "The chief data officer, or the most senior data official, leads identification and appoints a coordinating team or person, drawing in owners, IAOs, stewards, service owners, analysts and policy makers."
  },
  {
   "id": "DAM-R15",
   "cap": "dq",
   "strength": "method",
   "src": "SRC-DQIF",
   "prov": "V",
   "text": "Prioritise quality issues with the issues framework: importance of purpose times impact sets the target range; the band below target sets priority. Its resolution timescales (Critical immediately; High, Medium and Low within 1, 3 and 6 measurements) are given as an example."
  },
  {
   "id": "DAM-R16",
   "cap": "cat",
   "strength": "gap",
   "src": "SRC-DAM",
   "prov": "V",
   "text": "The policy's introduction promises minimum requirements for interoperability, but the policy body does not state them. Treat the metadata guidance and the MEM as the current interoperability baseline and watch for guidance (open item OR-05)."
  }
 ],
 "timeline": [
  {
   "when": "Apr to Jun 2026",
   "what": "Launch",
   "kind": "phase",
   "prov": "P"
  },
  {
   "when": "Jul to Dec 2026",
   "what": "Phase 1: internal transformation",
   "kind": "phase",
   "prov": "P"
  },
  {
   "when": "Jan 2027",
   "what": "Baseline return",
   "kind": "return",
   "prov": "P"
  },
  {
   "when": "Feb 2027",
   "what": "Baseline adoption report",
   "kind": "report",
   "prov": "P"
  },
  {
   "when": "Jan to Oct 2027",
   "what": "Phase 2: implementation",
   "kind": "phase",
   "prov": "P"
  },
  {
   "when": "Oct 2027",
   "what": "Policy adoption return",
   "kind": "return",
   "prov": "P"
  },
  {
   "when": "Nov 2027",
   "what": "Adoption report",
   "kind": "report",
   "prov": "P"
  },
  {
   "when": "Nov 2027 onwards",
   "what": "Phase 3: reporting and maintenance",
   "kind": "phase",
   "prov": "P"
  },
  {
   "when": "End Mar 2028",
   "what": "Annual returns",
   "kind": "return",
   "prov": "P"
  },
  {
   "when": "Apr 2028",
   "what": "Annual reports",
   "kind": "report",
   "prov": "P"
  }
 ],
 "support": [
  {
   "name": "DAM Policy Coordinators Working Group",
   "detail": "Launched 30 July 2026 with agreed terms of reference; monthly to the end of 2026; one lead policy coordinator per organisation.",
   "prov": "P"
  },
  {
   "name": "Show and tells",
   "detail": "Regular sessions on the policy and its guidance.",
   "prov": "P"
  },
  {
   "name": "Cross-government data management community",
   "detail": "On Knowledge Hub, with recordings and materials.",
   "prov": "P"
  },
  {
   "name": "One-to-one support in tranches",
   "detail": "Tranche 1 August 2026, Tranche 2 June 2027, Tranche 3 December 2027, prioritised by volume and complexity of critical data assets; doubles as peer review.",
   "prov": "P"
  },
  {
   "name": "Data Owner and Data Steward training",
   "detail": "Role-based training for the ownership model the policy assumes (Q3 2026).",
   "prov": "P"
  },
  {
   "name": "Catalogue pilot",
   "detail": "A catalogue pilot with HM Treasury and a cloud vendor, with learning shared across government.",
   "prov": "P"
  },
  {
   "name": "Discoverability Platform",
   "detail": "GDS is scoping a platform that links to departments' own catalogues (update due December 2026). Interim template returns are used meanwhile.",
   "prov": "P"
  }
 ],
 "roles": [
  {
   "code": "CDO",
   "name": "Chief data officer",
   "text": "Implements the policy in the organisation and leads the identification exercise; sponsors governance.",
   "src": "SRC-DAM",
   "prov": "V"
  },
  {
   "code": "COO",
   "name": "Lead policy coordinator",
   "text": "Coordinates identification, collates and assures the return (including ALBs), and is the link to the Working Group.",
   "src": "SRC-IDC",
   "prov": "P"
  },
  {
   "code": "BRD",
   "name": "Data governance board",
   "text": "Sets policy direction, resolves escalations and sees every asset's status. Chaired by the CDO, SIRO or equivalent.",
   "src": null,
   "prov": "P"
  },
  {
   "code": "OWN",
   "name": "Data owner",
   "text": "Senior leader accountable for the meaning, content, quality and management of the asset; approves changes and signs off targets and risks.",
   "src": "SRC-OWN",
   "prov": "V"
  },
  {
   "code": "IAO",
   "name": "Information asset owner",
   "text": "Accountable to the SIRO for protecting the whole information asset; may hold data owner duties under the IAO or hybrid option.",
   "src": "SRC-OWN",
   "prov": "V"
  },
  {
   "code": "STW",
   "name": "Data steward",
   "text": "Runs the asset day to day: policies and standards, access, quality processes and documentation such as the business glossary in the catalogue.",
   "src": "SRC-OWN",
   "prov": "V"
  },
  {
   "code": "CUS",
   "name": "Data custodian",
   "text": "Technical expert for the system holding the data: storage, access controls, auditable change and disposal.",
   "src": "SRC-OWN",
   "prov": "V"
  },
  {
   "code": "CAT",
   "name": "Catalogue manager",
   "text": "Runs the organisation's catalogue, its metadata standard and its harvest feed.",
   "src": null,
   "prov": "O"
  },
  {
   "code": "DQL",
   "name": "Data quality lead or analyst",
   "text": "Methods, profiling, tooling and reporting for data quality.",
   "src": "SRC-DQAP",
   "prov": "V"
  },
  {
   "code": "DPO",
   "name": "Data protection officer",
   "text": "Independent advice on lawful basis, DPIAs and data subject rights.",
   "src": null,
   "prov": "K"
  },
  {
   "code": "USR",
   "name": "Data users",
   "text": "Teams, services and other organisations that rely on the data; say what they need and report problems.",
   "src": "SRC-DQAP",
   "prov": "V"
  },
  {
   "code": "PUB",
   "name": "People the data describes",
   "text": "Citizens, communities and their representatives; help spot exclusion and test whether quality information is understandable.",
   "src": null,
   "prov": "P"
  },
  {
   "code": "SRO",
   "name": "Senior responsible owner",
   "text": "Accountable for a programme or project meeting its objectives. Makes sure data assets the change creates, alters or retires have owners, budgets and assurance, and signs off handover to business as usual.",
   "prov": "O"
  },
  {
   "code": "PDM",
   "name": "Programme or project manager",
   "text": "Plans and runs the change. Builds DAM activities into the plan, the risk register and gate criteria, and makes sure data owners are consulted at each stage.",
   "prov": "O"
  },
  {
   "code": "SVO",
   "name": "Service or product owner",
   "text": "Owns the service the change delivers. Decides what data the service collects and exposes, and shows DAM evidence at service assessments.",
   "prov": "O"
  },
  {
   "code": "ARC",
   "name": "Design authority or solution architect",
   "text": "Approves data models, platforms and integrations. Checks new designs use open standards, documented schemas and an exit route, so they do not become future legacy.",
   "prov": "O"
  },
  {
   "code": "MIG",
   "name": "Data migration lead",
   "text": "Plans and runs data migration. Profiles quality before moving data, reconciles after, and keeps catalogue entries and ownership in step.",
   "prov": "O"
  },
  {
   "code": "CML",
   "name": "Commercial lead",
   "text": "Runs procurement and manages contracts. Writes data ownership, metadata delivery, quality reporting and exit into contracts.",
   "prov": "O"
  },
  {
   "code": "PMO",
   "name": "Programme office and assurance",
   "text": "Tracks delivery and organises assurance reviews. Checks DAM checkpoints are met at each gate and reports gaps to the senior responsible owner.",
   "prov": "O"
  }
 ],
 "capabilities": [
  {
   "id": "gov",
   "in_brief": [
    "Every critical data asset needs a named data owner. Governance is how you appoint them and keep them active.",
    "Run five recipes in order the first time, then as a yearly loop.",
    "Record decisions, issues and exceptions as you go, so your evidence for GDS builds itself."
   ],
   "before_you_start": [
    "Agreement from your chief data officer to lead adoption",
    "A list of the data policies you already have, however informal",
    "Your organisation's choice, or shortlist, of ownership option"
   ],
   "you_get": [
    "A one-page charter",
    "An ownership register",
    "Live decision and exception logs",
    "An evidence pack for the GDS return"
   ],
   "name": "Data governance",
   "short": "Governance",
   "colour": "#1d70b8",
   "icon": "shield-check",
   "question": "Who decides, by what authority, and how do we know it is working?",
   "purpose": "Put the authority, roles and routines in place so that every critical data asset has a named, active owner, decisions are made and recorded, and the organisation can evidence its DAM Policy adoption.",
   "why": "The policy requires a named data owner for every asset (DAM-R05), an ownership option that still meets the mandatory IAO actions (DAM-R09), and CDO-led implementation under CDO Council oversight (DAM-R08).",
   "method_name": "Five recipes",
   "method_intro": "Five repeatable recipes: Mandate, Frame, Assign, Operate and Assure. Run them in order the first time, then as a loop, with Assure feeding lessons back into Mandate. The sequence comes from the cross-government Data Governance Playbook (practitioner draft); the requirements it meets come from GDS guidance.",
   "method_prov": "P",
   "stages": [
    {
     "n": 1,
     "id": "mandate",
     "name": "Mandate",
     "goal": "Establish the authority everything else operates under.",
     "trigger": "A new governance need, the start of DAM Policy adoption, or the annual refresh.",
     "steps": [
      "Confirm the sponsor (the CDO, SIRO or equivalent) who will chair or co-sign the charter.",
      "Draft a one-page charter covering purpose, scope, authority and review cadence.",
      "State which data, systems and decisions are in scope, and any exclusions. Start narrow, with critical data assets.",
      "Route the charter for approval and record the decision and its date.",
      "Publish it to every stakeholder found during scoping."
     ],
     "outputs": [
      "Governance charter",
      "Board terms of reference",
      "Scope statement with exclusions",
      "Sign-off record"
     ],
     "checklist": [
      "Sponsor confirmed in writing",
      "Scope covers every critical data asset the organisation owns",
      "Sign-off obtained and dated",
      "Review date set, at least annual"
     ],
     "raci": {
      "CDO": "A",
      "BRD": "R",
      "COO": "R",
      "OWN": "C",
      "STW": "I",
      "DPO": "C"
     },
     "reqs": [
      "DAM-R08",
      "DAM-R14"
     ],
     "tip": "A charter that tries to cover everything is approved slowly or not at all. Widen scope at the annual refresh once the model works."
    },
    {
     "n": 2,
     "id": "frame",
     "name": "Frame",
     "goal": "Assemble a proportionate rulebook to make decisions against.",
     "trigger": "The charter is approved and policy gaps are known.",
     "steps": [
      "List every data policy and standard already in force, however informal.",
      "Compare it with the core areas - governance, classification and handling, quality, retention and disposal, access and sharing, metadata, master and reference data, and ethics including AI use.",
      "Draft or adopt what is missing, in proportion to the risk. Reuse cross-government guidance before writing your own.",
      "Give every policy a named owner (a role) and a review date.",
      "Register each policy and make it findable, ideally in the data catalogue."
     ],
     "outputs": [
      "Policy and standards register",
      "Gap assessment",
      "Policy owner list with review dates"
     ],
     "checklist": [
      "Gap assessment against the core areas done",
      "Every policy has an owner role and a review date",
      "The register is published and findable"
     ],
     "raci": {
      "CDO": "A",
      "BRD": "A",
      "COO": "R",
      "OWN": "C",
      "STW": "C",
      "DPO": "C"
     },
     "reqs": [
      "DAM-R09"
     ],
     "tip": "Adopting a cross-government template keeps you consistent with other departments and makes shared assurance easier."
    },
    {
     "n": 3,
     "id": "assign",
     "name": "Assign",
     "goal": "Put a named, accountable owner and an active steward against every critical data asset.",
     "trigger": "Policies are adopted and critical assets lack named owners.",
     "steps": [
      "Choose your ownership option - IAO model, data ownership model or hybrid - and record the decision.",
      "For each critical data asset, propose an owner of matching seniority (SCS for large or complex assets; Grade 6 or 7 for smaller ones), a steward and a custodian.",
      "Agree decision rights using the RACI below and any delegated thresholds.",
      "Brief role holders and record training (Data Owner and Steward training).",
      "Record owner, steward, custodian, effective date and a named successor in the ownership register and the catalogue record."
     ],
     "outputs": [
      "Ownership option decision",
      "Data ownership register",
      "RACI per asset or asset class",
      "Succession plan"
     ],
     "checklist": [
      "Every critical data asset has a named owner",
      "Every role has a named deputy or successor",
      "The catalogue record shows the owner role and a contact point that is a team or form, never a personal inbox",
      "Mandatory IAO actions still covered whichever option you chose"
     ],
     "raci": {
      "CDO": "A",
      "BRD": "C",
      "COO": "R",
      "OWN": "R",
      "STW": "R",
      "CUS": "C",
      "IAO": "C"
     },
     "reqs": [
      "DAM-R05",
      "DAM-R09",
      "DAM-R10"
     ],
     "tip": "A single point of failure in accountability is the most common finding when this step is audited. Name a backup for every owner and steward."
    },
    {
     "n": 4,
     "id": "operate",
     "name": "Operate",
     "goal": "Make governance visible day to day.",
     "trigger": "Owners are in place and governance moves into business as usual.",
     "steps": [
      "Set the board's cadence (monthly, at least quarterly) and publish the calendar.",
      "Keep a decision log - what, who, why, when and the review trigger.",
      "Keep an issue and risk log, with quality issues coming in from the DQAP.",
      "Log every deviation from policy as an exception with an owner and an expiry date.",
      "Escalate anything unresolved up the ladder."
     ],
     "outputs": [
      "Decision log",
      "Issue and risk log",
      "Exception register",
      "Board minutes"
     ],
     "checklist": [
      "Decision log active and current",
      "Every exception has an expiry date",
      "Escalations tracked to resolution",
      "Minutes published within five working days"
     ],
     "raci": {
      "CDO": "I",
      "BRD": "A",
      "OWN": "R",
      "STW": "R",
      "CUS": "C",
      "DQL": "C",
      "DPO": "C"
     },
     "reqs": [
      "DAM-R05"
     ],
     "tip": "An empty decision log after three months is a warning, not efficiency. Decisions are being made off the record."
    },
    {
     "n": 5,
     "id": "assure",
     "name": "Assure",
     "goal": "Prove it works and feed the lessons back into the mandate.",
     "trigger": "A reporting cycle, the annual return or an audit is due.",
     "steps": [
      "Re-run the data maturity self-assessment.",
      "Compile measures from the live registers - owner coverage, review currency, DQAP coverage, exceptions.",
      "Map evidence to the GDS annual return as you go, not at the deadline.",
      "Have someone outside the board check the evidence before submission.",
      "Submit, then log lessons back into Mandate."
     ],
     "outputs": [
      "Maturity score and narrative",
      "Measures pack",
      "Evidence pack mapped to the GDS return",
      "Lessons note"
     ],
     "checklist": [
      "Evidence collected continuously during Operate",
      "Independent check done before submission",
      "Return submitted on time",
      "Lessons logged to Mandate"
     ],
     "raci": {
      "CDO": "A",
      "BRD": "R",
      "COO": "R",
      "OWN": "C",
      "STW": "C",
      "DQL": "C"
     },
     "reqs": [
      "DAM-R03",
      "DAM-R08"
     ],
     "tip": "Keep an evidence folder updated every time a decision is logged, so the return is collation, not reconstruction."
    }
   ],
   "roles": [
    "CDO",
    "BRD",
    "COO",
    "OWN",
    "IAO",
    "STW",
    "CUS",
    "DPO"
   ],
   "escalation_note": "The ladder and its timescales are this playbook's recommendation, not a GOV.UK requirement.",
   "escalation": [
    {
     "level": "Tier 1",
     "who": "Steward or custodian",
     "trigger": "Working-level query or minor exception",
     "when": "2 working days"
    },
    {
     "level": "Tier 2",
     "who": "Data owner",
     "trigger": "Access, quality or sharing decision within remit",
     "when": "5 working days"
    },
    {
     "level": "Tier 3",
     "who": "Data governance board",
     "trigger": "Cross-owner conflict, policy exception or high risk",
     "when": "10 working days"
    },
    {
     "level": "Tier 4",
     "who": "CDO, SIRO or accounting officer",
     "trigger": "Unresolved board decision or legal or reputational risk",
     "when": "As required"
    }
   ],
   "measures": [
    {
     "name": "Critical data assets with a named owner",
     "target": "100%"
    },
    {
     "name": "Owners and stewards with a named successor",
     "target": "100%"
    },
    {
     "name": "Policies with an owner and an in-date review",
     "target": "100%"
    },
    {
     "name": "Open exceptions past their expiry date",
     "target": "0"
    }
   ],
   "templates": [
    {
     "id": "T-GOV-1",
     "mode": "Both",
     "name": "Governance charter",
     "fields": [
      "Purpose",
      "Scope and exclusions",
      "Authority and sponsor",
      "Membership",
      "Decision rights",
      "Review cadence",
      "Sign-off (role and date)"
     ]
    },
    {
     "id": "T-GOV-2",
     "mode": "BAU",
     "name": "Data ownership register entry",
     "fields": [
      "Asset identifier",
      "Asset title",
      "Ownership option (IAO, data owner or hybrid)",
      "Data owner (role)",
      "Information asset owner (role)",
      "Data steward (role)",
      "Data custodian (role)",
      "Successor (role)",
      "Effective date",
      "Training completed",
      "Next review",
      "Retention schedule reference",
      "Retention period",
      "Disposal action (destroy, review or transfer to archive)",
      "Retention review date",
      "Longer retention approved by (role)"
     ]
    },
    {
     "id": "T-GOV-3",
     "mode": "Both",
     "name": "Decision log entry",
     "fields": [
      "Decision ID",
      "Date",
      "Decision",
      "Decided by (role or forum)",
      "Rationale",
      "Assets affected",
      "Review trigger"
     ]
    },
    {
     "id": "T-GOV-4",
     "mode": "Both",
     "name": "Exception register entry",
     "fields": [
      "Exception ID",
      "Policy deviated from",
      "Rationale",
      "Owner (role)",
      "Risk accepted by (role)",
      "Start date",
      "Expiry date",
      "Review outcome"
     ]
    },
    {
     "id": "T-GOV-5",
     "mode": "Both",
     "name": "Day-to-day management workbook",
     "note": "One workbook with a tab for each log, for teams that manage risks, assumptions, issues, dependencies, decisions, actions and exceptions together. Each tab keeps the fields of its own log, so you can still report each one on its own.",
     "sheets": [
      {
       "name": "Risks",
       "fields": [
        "Risk ID",
        "Date raised",
        "Description",
        "Cause",
        "Effect",
        "Likelihood (1-5)",
        "Impact (1-5)",
        "Score",
        "Owner (role)",
        "Response",
        "Status",
        "Review date"
       ]
      },
      {
       "name": "Assumptions",
       "fields": [
        "Assumption ID",
        "Date raised",
        "Assumption",
        "Why we believe it",
        "How and when we will test it",
        "Owner (role)",
        "Status"
       ]
      },
      {
       "name": "Issues",
       "fields": [
        "Issue ID",
        "Date raised",
        "Description",
        "Impact",
        "Priority",
        "Owner (role)",
        "Action",
        "Target date",
        "Status"
       ]
      },
      {
       "name": "Dependencies",
       "fields": [
        "Dependency ID",
        "Date raised",
        "We depend on",
        "For what",
        "Needed by",
        "Owner (role)",
        "Status"
       ]
      },
      {
       "name": "Decisions",
       "from": "T-GOV-3",
       "fields": [
        "Decision ID",
        "Date",
        "Decision",
        "Decided by (role or forum)",
        "Rationale",
        "Assets affected",
        "Review trigger"
       ]
      },
      {
       "name": "Actions",
       "fields": [
        "Action ID",
        "Date raised",
        "Action",
        "From (meeting, decision or issue)",
        "Owner (role)",
        "Due date",
        "Status"
       ]
      },
      {
       "name": "Exceptions",
       "from": "T-GOV-4",
       "fields": [
        "Exception ID",
        "Policy deviated from",
        "Rationale",
        "Owner (role)",
        "Risk accepted by (role)",
        "Start date",
        "Expiry date",
        "Review outcome"
       ]
      }
     ],
     "fields": [
      "Risks: Risk ID",
      "Risks: Date raised",
      "Risks: Description",
      "Risks: Cause",
      "Risks: Effect",
      "Risks: Likelihood (1-5)",
      "Risks: Impact (1-5)",
      "Risks: Score",
      "Risks: Owner (role)",
      "Risks: Response",
      "Risks: Status",
      "Risks: Review date",
      "Assumptions: Assumption ID",
      "Assumptions: Date raised",
      "Assumptions: Assumption",
      "Assumptions: Why we believe it",
      "Assumptions: How and when we will test it",
      "Assumptions: Owner (role)",
      "Assumptions: Status",
      "Issues: Issue ID",
      "Issues: Date raised",
      "Issues: Description",
      "Issues: Impact",
      "Issues: Priority",
      "Issues: Owner (role)",
      "Issues: Action",
      "Issues: Target date",
      "Issues: Status",
      "Dependencies: Dependency ID",
      "Dependencies: Date raised",
      "Dependencies: We depend on",
      "Dependencies: For what",
      "Dependencies: Needed by",
      "Dependencies: Owner (role)",
      "Dependencies: Status",
      "Decisions: Decision ID",
      "Decisions: Date",
      "Decisions: Decision",
      "Decisions: Decided by (role or forum)",
      "Decisions: Rationale",
      "Decisions: Assets affected",
      "Decisions: Review trigger",
      "Actions: Action ID",
      "Actions: Date raised",
      "Actions: Action",
      "Actions: From (meeting, decision or issue)",
      "Actions: Owner (role)",
      "Actions: Due date",
      "Actions: Status",
      "Exceptions: Exception ID",
      "Exceptions: Policy deviated from",
      "Exceptions: Rationale",
      "Exceptions: Owner (role)",
      "Exceptions: Risk accepted by (role)",
      "Exceptions: Start date",
      "Exceptions: Expiry date",
      "Exceptions: Review outcome"
     ]
    },
    {
     "id": "T-GOV-6",
     "mode": "Both",
     "name": "Data sharing agreement",
     "note": "The questions the ICO's data sharing code says an agreement should answer. Your organisation may call it an information sharing agreement or protocol. It does not replace legal advice or a DPIA.",
     "fields": [
      "Agreement reference",
      "Parties",
      "Controller at each stage, including after sharing",
      "Data protection officer or responsible contact for each party (role)",
      "Purpose and specific aims",
      "Why sharing is necessary to meet them",
      "Benefits to people or society",
      "Lawful basis for each party",
      "Legal gateway or power",
      "Data items shared (data specification)",
      "Formats and standards (for example, how dates of birth are recorded)",
      "Access and security arrangements",
      "How people's rights are met",
      "How accuracy is checked and errors corrected",
      "Retention and deletion of shared data",
      "Ending the sharing (deletion or return of data)",
      "Review date and review triggers (for example, a complaint or breach)",
      "Freedom of information publication scheme entry",
      "DPIA reference",
      "Catalogue record of the shared asset"
     ]
    }
   ]
  },
  {
   "id": "cat",
   "in_brief": [
    "Find the data other organisations depend on, and decide which of it is critical.",
    "Describe each critical data asset well enough for someone outside your team to find and judge it.",
    "Keep the descriptions in a catalogue, report them to GDS, and review them every year."
   ],
   "before_you_start": [
    "A named coordinating team, led by your chief data officer",
    "Access to your data catalogue, information asset register and register of data sharing agreements",
    "Ownership confirmed, or under way, through the governance Assign recipe"
   ],
   "you_get": [
    "A designation log with reasons",
    "A catalogue record per asset",
    "An assured return to GDS",
    "An annual review record"
   ],
   "name": "Data cataloguing",
   "short": "Cataloguing",
   "colour": "#00703c",
   "icon": "library-big",
   "question": "What critical data do we hold, is it described well enough to find and reuse, and have we told GDS?",
   "purpose": "Find the critical data assets, describe each one to the cross-government metadata standard, keep the descriptions in a catalogue that others can harvest, and report them to GDS every year.",
   "why": "Identifying, cataloguing, reporting and annually reviewing metadata are all 'must' requirements (DAM-R01 to DAM-R04).",
   "method_name": "Eight stages",
   "method_intro": "Eight stages from mobilising the team to the annual review. The sequence is this playbook's synthesis of the policy, the identification guidance and the metadata guidance; each step points to the requirement it meets. The internal Data Cataloguing Playbook (v2.6) is the fuller source and is not yet public (open item OR-01).",
   "method_prov": "O",
   "stages": [
    {
     "n": 1,
     "id": "mobilise",
     "name": "Mobilise",
     "goal": "Have a named lead and a coordinating team before identification starts.",
     "trigger": "Policy adoption begins, or a new reporting cycle opens.",
     "steps": [
      "The CDO (or most senior data official) leads and appoints a coordinating team or person.",
      "Nominate the lead policy coordinator for the Working Group.",
      "Agree how the department will coordinate and assure its ALBs' returns.",
      "Bring in data owners, IAOs, stewards, service owners, analysts and policy makers."
     ],
     "outputs": [
      "Named lead and coordinator",
      "Contributor list",
      "ALB coordination plan"
     ],
     "checklist": [
      "Coordinator nominated to the Working Group",
      "Every ALB has a named contact role"
     ],
     "raci": {
      "CDO": "A",
      "COO": "R",
      "OWN": "C",
      "IAO": "C",
      "STW": "C"
     },
     "reqs": [
      "DAM-R14",
      "DAM-R03"
     ]
    },
    {
     "n": 2,
     "id": "discover",
     "name": "Discover candidates",
     "goal": "Build a long list of data other organisations depend on.",
     "trigger": "The team is mobilised.",
     "steps": [
      "Start from what you already have - data catalogues, information asset registers and registers of data sharing agreements.",
      "Find data you provide to, or acquire from, other organisations for an essential process or purpose.",
      "Prioritise assets supporting government missions and your services (including Top 75 services).",
      "Include high-reuse-value assets not yet shared."
     ],
     "outputs": [
      "Candidate list with source of each entry"
     ],
     "checklist": [
      "All three starting registers searched",
      "Both directions covered - data provided and data acquired"
     ],
     "raci": {
      "CDO": "A",
      "COO": "R",
      "CAT": "R",
      "STW": "C",
      "OWN": "C",
      "USR": "C"
     },
     "reqs": [
      "DAM-R01"
     ]
    },
    {
     "n": 3,
     "id": "designate",
     "name": "Test and designate",
     "goal": "Decide which candidates are critical data assets, and draw each asset's boundary.",
     "trigger": "The candidate list is complete.",
     "steps": [
      "Apply the policy's scope tests - classified OFFICIAL, meets the critical data asset criteria, within your ownership accountabilities.",
      "Record which of the seven purposes each asset supports.",
      "Draw the boundary - only the fields needed for the cross-government purpose form the asset, not the whole system.",
      "If you designate a distribution, designate its source data set too.",
      "Record why each candidate was or was not designated."
     ],
     "outputs": [
      "Designation decisions with reasons",
      "Asset boundary per asset"
     ],
     "checklist": [
      "Every asset passes all scope tests",
      "Every asset has at least one purpose",
      "Source data sets designated where a distribution is"
     ],
     "raci": {
      "CDO": "A",
      "COO": "R",
      "OWN": "R",
      "STW": "C",
      "DPO": "C"
     },
     "reqs": [
      "DAM-R01",
      "DAM-R11",
      "DAM-R12"
     ]
    },
    {
     "n": 4,
     "id": "own",
     "name": "Confirm ownership",
     "goal": "Every designated asset has a named, accountable owner before it is described.",
     "trigger": "Assets are designated.",
     "steps": [
      "Confirm the owner (data owner or IAO) and steward for each asset with the governance Assign recipe.",
      "Use a shared team contact point for the asset, never a personal inbox.",
      "Record a successor so the metadata survives the owner leaving."
     ],
     "outputs": [
      "Owner",
      "steward and contact point per asset"
     ],
     "checklist": [
      "No asset goes forward without a named owner",
      "Contact point is a team route or form"
     ],
     "raci": {
      "CDO": "A",
      "OWN": "R",
      "STW": "R",
      "COO": "C"
     },
     "reqs": [
      "DAM-R05",
      "DAM-R10"
     ]
    },
    {
     "n": 5,
     "id": "describe",
     "name": "Describe",
     "goal": "Describe each asset well enough for someone outside your team to find, understand and judge it.",
     "trigger": "The asset has an owner.",
     "steps": [
      "Record the properties in the metadata guidance (see the metadata tab).",
      "Write in plain English; expand acronyms; describe the data, and put usage warnings in usage notes.",
      "Use ISO 8601 dates, IANA media types, and 'unknown' or 'not applicable' rather than blanks.",
      "Model datasets, data services and distributions as the MEM and DCAT do.",
      "Add quality information from the DQAP (see data quality, stage 6)."
     ],
     "outputs": [
      "Catalogue record per asset",
      "conforming to the metadata guidance"
     ],
     "checklist": [
      "Title and description are plain English",
      "Access rights, licence and security classification recorded",
      "Dates in ISO 8601"
     ],
     "raci": {
      "OWN": "A",
      "STW": "R",
      "CAT": "R",
      "CUS": "C",
      "DQL": "C"
     },
     "reqs": [
      "DAM-R02",
      "DAM-R13"
     ]
    },
    {
     "n": 6,
     "id": "publish",
     "name": "Catalogue and expose",
     "goal": "Keep the record in your catalogue in a form others can harvest.",
     "trigger": "Records are complete.",
     "steps": [
      "Store each record in the organisation's catalogue, or an asset register where no catalogue exists yet.",
      "Expose records in DCAT so portals and the Discoverability Platform can harvest them.",
      "Make sure every link in a record works from outside your organisation.",
      "Choose catalogue tools against what any catalogue must expose, not a single vendor."
     ],
     "outputs": [
      "Catalogue entries",
      "Machine-readable feed"
     ],
     "checklist": [
      "Records are reachable by harvest, not only by people",
      "No record depends on an internal-only link"
     ],
     "raci": {
      "OWN": "A",
      "CAT": "R",
      "CUS": "R",
      "STW": "C"
     },
     "reqs": [
      "DAM-R02",
      "DAM-R16"
     ]
    },
    {
     "n": 7,
     "id": "report",
     "name": "Report to GDS",
     "goal": "Submit an assured return on time.",
     "trigger": "A return window opens (baseline January 2027).",
     "steps": [
      "Prepare the return from catalogue records, not by retyping them.",
      "Collate and assure ALB returns.",
      "Check the return before submission so moderation is about judgement, not formatting.",
      "Submit through the interim template, or the Discoverability Platform when it is live."
     ],
     "outputs": [
      "Assured return",
      "ALB assurance record"
     ],
     "checklist": [
      "Every asset in the return has an owner, a purpose and current metadata",
      "ALB returns assured by the department"
     ],
     "raci": {
      "CDO": "A",
      "COO": "R",
      "CAT": "R",
      "OWN": "C",
      "BRD": "I"
     },
     "reqs": [
      "DAM-R03"
     ]
    },
    {
     "n": 8,
     "id": "maintain",
     "name": "Maintain and review",
     "goal": "Records stay true.",
     "trigger": "Every 12 months, and whenever an asset or its owner changes.",
     "steps": [
      "Review every record at least every 12 months.",
      "Update records when the asset changes, and when the owner leaves.",
      "Retire assets that are no longer critical, with a reason.",
      "Feed findings into the governance Assure recipe."
     ],
     "outputs": [
      "Annual review record",
      "Updated catalogue entries"
     ],
     "checklist": [
      "Every record reviewed in the last 12 months",
      "Owner changes reflected within the month"
     ],
     "raci": {
      "OWN": "A",
      "STW": "R",
      "CAT": "R",
      "COO": "C"
     },
     "reqs": [
      "DAM-R04",
      "DAM-R10"
     ]
    }
   ],
   "roles": [
    "CDO",
    "COO",
    "OWN",
    "IAO",
    "STW",
    "CUS",
    "CAT",
    "USR"
   ],
   "metadata": [
    {
     "prop": "title",
     "mem": "CataloguedResource.title",
     "obligation": "must",
     "rule": "Plain English name; avoid acronyms and jargon"
    },
    {
     "prop": "alternativeTitle",
     "mem": "CataloguedResource.alternativeTitle",
     "obligation": "optional",
     "rule": "A short name to keep titles concise"
    },
    {
     "prop": "description",
     "mem": "CataloguedResource.description",
     "obligation": "must",
     "rule": "Describes the data; usage warnings go elsewhere"
    },
    {
     "prop": "identifier",
     "mem": "CataloguedResource.identifier",
     "obligation": "should",
     "rule": "Your own system's identifier or an opaque random one, not sequential"
    },
    {
     "prop": "creator",
     "mem": "CataloguedResource.creator",
     "obligation": "must",
     "rule": "The organisation that created the data, from a list of organisations"
    },
    {
     "prop": "dateCreated",
     "mem": "CataloguedResource.created",
     "obligation": "should",
     "rule": "ISO 8601 date or date-time"
    },
    {
     "prop": "temporalCoverage",
     "mem": "none in MEM (gap)",
     "obligation": "listed",
     "rule": "The period the data applies to"
    },
    {
     "prop": "conformsTo",
     "mem": "none in MEM (gap)",
     "obligation": "listed",
     "rule": "The standard or schema the data follows"
    },
    {
     "prop": "accessRights",
     "mem": "CataloguedResource.accessRights",
     "obligation": "should",
     "rule": "open, commercial or internal, with any handling caveat"
    },
    {
     "prop": "securityClassification",
     "mem": "CataloguedResource.securityClassification",
     "obligation": "listed",
     "rule": "Sensitivity level, OFFICIAL for assets in scope"
    },
    {
     "prop": "licence",
     "mem": "CataloguedResource.licence",
     "obligation": "should",
     "rule": "OGL URL for open data; the agreement for restricted data"
    },
    {
     "prop": "mediaType",
     "mem": "Distribution.mediaType",
     "obligation": "should",
     "rule": "IANA media type, such as text/csv"
    },
    {
     "prop": "expires",
     "mem": "none in MEM (gap)",
     "obligation": "listed",
     "rule": "How long this version is valid"
    },
    {
     "prop": "supersededBy",
     "mem": "none in MEM (gap)",
     "obligation": "listed",
     "rule": "The newer version that replaces this one"
    }
   ],
   "metadata_detail": [
    {
     "prop": "title",
     "type": "Text",
     "format": "Plain English, up to about 100 characters",
     "card": "1",
     "example": "Outpatient attendances, England"
    },
    {
     "prop": "alternativeTitle",
     "type": "Text",
     "format": "Plain text",
     "card": "0 or more",
     "example": "OPA monthly"
    },
    {
     "prop": "description",
     "type": "Text",
     "format": "Plain English paragraphs",
     "card": "1",
     "example": "Monthly counts of outpatient attendances by provider and specialty."
    },
    {
     "prop": "identifier",
     "type": "Text",
     "format": "Your system's identifier, or a random UUID",
     "card": "0 or 1",
     "example": "3f6c1d2e-8a4b-4c1e-9d7f-2b5a6e0c9a41"
    },
    {
     "prop": "creator",
     "type": "Organisation",
     "format": "Link to an organisation in a published list",
     "card": "1 or more",
     "values": "organisations",
     "example": "https://www.gov.uk/government/organisations/department-of-health-and-social-care"
    },
    {
     "prop": "dateCreated",
     "type": "Date",
     "format": "ISO 8601 date (YYYY-MM-DD) or date and time",
     "card": "0 or 1",
     "example": "2024-04-01"
    },
    {
     "prop": "temporalCoverage",
     "type": "Period of time",
     "format": "ISO 8601 start and end dates, written start/end",
     "card": "0 or more",
     "example": "2024-04-01/2025-03-31"
    },
    {
     "prop": "conformsTo",
     "type": "Standard",
     "format": "Link to the standard or schema",
     "card": "0 or more",
     "example": "A link to the NHS data set specification the extract follows"
    },
    {
     "prop": "accessRights",
     "type": "Controlled value",
     "format": "One value from the list",
     "card": "0 or 1",
     "values": "access-rights",
     "example": "internal"
    },
    {
     "prop": "securityClassification",
     "type": "Controlled value",
     "format": "One value from the list",
     "card": "1",
     "values": "classification",
     "example": "OFFICIAL"
    },
    {
     "prop": "licence",
     "type": "Licence",
     "format": "Link to the licence or agreement",
     "card": "0 or 1",
     "example": "https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/"
    },
    {
     "prop": "mediaType",
     "type": "Media type",
     "format": "IANA media type",
     "card": "0 or 1 for each distribution",
     "values": "media-types",
     "example": "text/csv"
    },
    {
     "prop": "expires",
     "type": "Date",
     "format": "ISO 8601 date (YYYY-MM-DD)",
     "card": "0 or 1",
     "example": "2026-03-31"
    },
    {
     "prop": "supersededBy",
     "type": "Link",
     "format": "Link to the record that replaces this one",
     "card": "0 or 1",
     "example": "A link to the 2026 version's catalogue record"
    }
   ],
   "value_lists": [
    {
     "id": "access-rights",
     "name": "Access rights",
     "prov": "V",
     "values": [
      "open",
      "commercial",
      "internal"
     ],
     "note": "From the GOV.UK metadata guidance. Add any handling caveat in the description."
    },
    {
     "id": "classification",
     "name": "Security classification",
     "prov": "K",
     "values": [
      "OFFICIAL",
      "SECRET",
      "TOP SECRET"
     ],
     "note": "The Government Security Classifications. Assets in scope of the DAM Policy are OFFICIAL.",
     "url": "https://www.gov.uk/government/publications/government-security-classifications"
    },
    {
     "id": "organisations",
     "name": "Organisations",
     "prov": "K",
     "values": [],
     "note": "Use a published list of organisations, such as the GOV.UK organisations list, and link to the organisation's page.",
     "url": "https://www.gov.uk/government/organisations"
    },
    {
     "id": "media-types",
     "name": "Media types",
     "prov": "K",
     "values": [
      "text/csv",
      "application/json",
      "application/vnd.oasis.opendocument.spreadsheet",
      "text/turtle"
     ],
     "note": "Use the IANA register of media types. The values shown are common examples.",
     "url": "https://www.iana.org/assignments/media-types/media-types.xhtml"
    }
   ],
   "measures": [
    {
     "name": "Designated assets with a catalogue record",
     "target": "100%"
    },
    {
     "name": "Records reviewed in the last 12 months",
     "target": "100%"
    },
    {
     "name": "Records with access rights, licence and classification",
     "target": "100%"
    },
    {
     "name": "Records harvestable as DCAT",
     "target": "Rising each quarter"
    }
   ],
   "templates": [
    {
     "id": "T-CAT-1",
     "mode": "BAU",
     "name": "Candidate and designation log",
     "fields": [
      "Candidate",
      "Found in (catalogue, IAR or sharing register)",
      "Provided to or acquired from",
      "Purpose (one or more of seven)",
      "Scope tests passed",
      "Designated (yes or no)",
      "Reason",
      "Decided by (role)",
      "Date"
     ]
    },
    {
     "id": "T-CAT-2",
     "mode": "BAU",
     "name": "Critical data asset catalogue record",
     "fields": [
      "title",
      "alternativeTitle",
      "description",
      "identifier",
      "creator",
      "dateCreated",
      "temporalCoverage",
      "conformsTo",
      "accessRights",
      "securityClassification",
      "licence",
      "mediaType",
      "expires",
      "supersededBy",
      "Owner (role)",
      "Contact point (team or form)",
      "Purpose",
      "Last reviewed",
      "Next review",
      "Retention period",
      "Disposal action"
     ]
    },
    {
     "id": "T-CAT-3",
     "mode": "BAU",
     "name": "Annual record review",
     "fields": [
      "Asset",
      "Date",
      "Still critical (and why)",
      "Owner and successor confirmed",
      "Metadata checked against the guidance",
      "Changes made",
      "Signed off by (role)"
     ]
    },
    {
     "id": "T-CAT-4",
     "mode": "Both",
     "examples": [
      "templates/T-CAT-4-example.csv",
      "templates/T-CAT-4-example.mmd"
     ],
     "name": "Entity and relationship list",
     "note": "A plain list of the entities in a data asset and how they relate, so a relationship diagram can be drawn from it. The Data architecture and models supplement has a worked example and the diagram it produces.",
     "fields": [
      "Entity",
      "Description",
      "Key attributes",
      "Related entity",
      "Relationship (for example, places)",
      "Cardinality (one to one, one to many or many to many)",
      "Optional or mandatory",
      "Source system",
      "Data dictionary link"
     ]
    }
   ]
  },
  {
   "id": "dq",
   "in_brief": [
    "Every critical data asset needs a data quality action plan (DQAP) or an equivalent.",
    "Agree what 'good enough' means with users, test it with rules, and fix the causes of failures.",
    "Publish how good the data is, including what it should not be used for."
   ],
   "before_you_start": [
    "A designated asset with a named data owner",
    "Agreement from at least two user teams on what the data is used for",
    "The DQAP template from GOV.UK, or the Data Quality Commons tools"
   ],
   "you_get": [
    "A rule catalogue with targets",
    "A baseline and issue log",
    "A prioritised action plan",
    "A plain-English data quality statement"
   ],
   "name": "Data quality",
   "short": "Quality",
   "colour": "#b45f06",
   "icon": "gauge",
   "question": "Is the data good enough for what it is used for, and are we fixing what is not?",
   "purpose": "Know, prove and improve the quality of each critical data asset through a data quality action plan (DQAP), scored with the government issues framework, reported openly and repeated every cycle.",
   "why": "Every identified asset must have a DQAP or equivalent (DAM-R06), and existing processes should cover all seven DQAP steps (DAM-R07).",
   "method_name": "Eight stages over the seven DQAP steps",
   "method_intro": "Eight stages taken from the Data Quality Commons playbook, which follows the seven steps of the GDS DQAP implementation guide and adds an annual review. Use the Commons for the tools - rule checking, issue scoring and DQAP workbooks; this page is the method and how it joins governance and cataloguing.",
   "method_prov": "P",
   "stages": [
    {
     "n": 1,
     "id": "identify",
     "name": "Identify critical data",
     "dqap": "Step 1",
     "goal": "Know which data items in each asset matter most.",
     "trigger": "The asset is designated and has an owner.",
     "steps": [
      "Name the 5 to 15 data items that drive the most important decisions (critical data elements).",
      "Record who uses the data, for what, and who or what it describes.",
      "Log known issues in the DQAP issues log."
     ],
     "outputs": [
      "Criticality matrix",
      "User and purpose map"
     ],
     "checklist": [
      "Critical data elements agreed with at least two user teams",
      "You know which groups the data might miss"
     ],
     "raci": {
      "OWN": "A",
      "STW": "R",
      "USR": "C",
      "DQL": "C",
      "PUB": "I"
     },
     "reqs": [
      "DAM-R06"
     ]
    },
    {
     "n": 2,
     "id": "define",
     "name": "Define rules and targets",
     "dqap": "Step 2",
     "goal": "Turn 'good enough' into rules a computer can test.",
     "trigger": "Critical data elements are agreed.",
     "steps": [
      "Choose the dimensions that matter - completeness, uniqueness, consistency, timeliness, validity, accuracy.",
      "Write each rule in plain English first, then as a testable rule.",
      "Set targets from the issues framework range for importance times impact.",
      "Store rules as files (a data contract) so they survive a change of tool or supplier."
     ],
     "outputs": [
      "Rule catalogue",
      "Targets",
      "Data contract"
     ],
     "checklist": [
      "Every critical data element has at least one rule",
      "Targets come from user impact, not from what the data already achieves"
     ],
     "raci": {
      "OWN": "A",
      "STW": "R",
      "DQL": "R",
      "USR": "C"
     },
     "reqs": [
      "DAM-R06",
      "DAM-R15"
     ]
    },
    {
     "n": 3,
     "id": "baseline",
     "name": "Measure a baseline",
     "dqap": "Step 3",
     "goal": "Know where you are today.",
     "trigger": "Rules and targets are agreed.",
     "steps": [
      "Profile the data and run every rule; record the date and data version.",
      "Log every failure as an issue with its size and who it affects.",
      "Break results down by group where you lawfully can."
     ],
     "outputs": [
      "Baseline results",
      "Issue log"
     ],
     "checklist": [
      "Results are reproducible",
      "Group differences looked for and recorded"
     ],
     "raci": {
      "OWN": "A",
      "STW": "R",
      "DQL": "R",
      "CUS": "C"
     },
     "reqs": [
      "DAM-R06"
     ]
    },
    {
     "n": 4,
     "id": "prioritise",
     "name": "Prioritise and set goals",
     "dqap": "Step 4",
     "goal": "Fix what hurts most first.",
     "trigger": "The baseline is recorded.",
     "steps": [
      "Score each issue with the issues framework.",
      "Resolve Critical immediately, High within one cycle, Medium within three and Low within six.",
      "Agree the order with the owner and record accepted risks with a review date."
     ],
     "outputs": [
      "Prioritised issue list",
      "Goals in the DQAP",
      "Risk acceptances"
     ],
     "checklist": [
      "Every issue has a priority and a timescale",
      "Issues affecting some groups more than others are not ranked down as 'small'"
     ],
     "raci": {
      "OWN": "A",
      "STW": "R",
      "BRD": "I",
      "DQL": "C"
     },
     "reqs": [
      "DAM-R15"
     ]
    },
    {
     "n": 5,
     "id": "improve",
     "name": "Fix causes at source",
     "dqap": "Step 5",
     "goal": "Stop problems coming back.",
     "trigger": "Goals are agreed.",
     "steps": [
      "Ask why until you reach the cause - people, process, system, supplier or standard.",
      "Prefer prevention at entry over downstream cleaning.",
      "Put supplier duties and measures into contracts.",
      "Re-run the rule to prove the fix worked."
     ],
     "outputs": [
      "Root cause records",
      "Actions with owners",
      "Evidence of fixes"
     ],
     "checklist": [
      "Every fix proved by re-running the rule",
      "Any downstream cleaning is recorded and temporary"
     ],
     "raci": {
      "OWN": "A",
      "STW": "R",
      "CUS": "R",
      "DQL": "C"
     },
     "reqs": [
      "DAM-R06"
     ]
    },
    {
     "n": 6,
     "id": "report",
     "name": "Report openly",
     "dqap": "Step 6",
     "goal": "Users know how good the data is and what it should not be used for.",
     "trigger": "Each measurement cycle.",
     "steps": [
      "Update a plain-English data quality statement - scores, trends, known issues and unsuitable uses.",
      "Publish quality information with the catalogue record (W3C DQV) so it travels with the asset.",
      "Report the status of all assets to the governance board; quality issues enter the issue and risk log."
     ],
     "outputs": [
      "Data quality statement",
      "Quality metadata on the catalogue record",
      "Board report"
     ],
     "checklist": [
      "Statement says what the data is not fit for",
      "Quality information sits on the catalogue record"
     ],
     "raci": {
      "OWN": "A",
      "STW": "R",
      "CAT": "R",
      "BRD": "I",
      "USR": "I"
     },
     "reqs": [
      "DAM-R06"
     ]
    },
    {
     "n": 7,
     "id": "sustain",
     "name": "Repeat and sustain",
     "dqap": "Step 7",
     "goal": "Quality stays good without heroics.",
     "trigger": "After the first cycle.",
     "steps": [
      "Run checks automatically on each load or on a fixed cycle.",
      "Track trends and alert when a rule drops below target.",
      "Escalate with the agreed thresholds.",
      "Keep rules, results and the plan in version control."
     ],
     "outputs": [
      "Automated checks",
      "Trend record",
      "Escalation log"
     ],
     "checklist": [
      "Checks run without manual effort",
      "The steward has a named deputy"
     ],
     "raci": {
      "OWN": "A",
      "STW": "R",
      "DQL": "R",
      "CUS": "R"
     },
     "reqs": [
      "DAM-R06",
      "DAM-R07"
     ]
    },
    {
     "n": 8,
     "id": "review",
     "name": "Review every year",
     "dqap": "Added by the Commons",
     "goal": "Rules and targets still match what users need.",
     "trigger": "Every 12 months, on the same date as the catalogue record review.",
     "steps": [
      "Review rules, targets and the plan with the owner and users.",
      "Add rules for new uses, including AI.",
      "Retire rules that no longer matter; raise targets that are now easy."
     ],
     "outputs": [
      "Annual review note",
      "Next year's goals"
     ],
     "checklist": [
      "Reviewed with the catalogue record, not separately",
      "New uses assessed against the AI-ready data guidance"
     ],
     "raci": {
      "OWN": "A",
      "STW": "R",
      "USR": "C",
      "PUB": "C"
     },
     "reqs": [
      "DAM-R04",
      "DAM-R07"
     ]
    }
   ],
   "roles": [
    "OWN",
    "STW",
    "CUS",
    "DQL",
    "USR",
    "BRD",
    "CAT",
    "PUB"
   ],
   "principles": [
    {
     "name": "Commit to data quality",
     "src": "SRC-GDQF"
    },
    {
     "name": "Know your users and their needs",
     "src": "SRC-GDQF"
    },
    {
     "name": "Assess quality throughout the data lifecycle",
     "src": "SRC-GDQF"
    },
    {
     "name": "Communicate data quality clearly and effectively",
     "src": "SRC-GDQF"
    },
    {
     "name": "Anticipate changes affecting data quality",
     "src": "SRC-GDQF"
    }
   ],
   "dimensions": [
    {
     "name": "Completeness",
     "text": "How fully records are present, including whether essential values are filled in"
    },
    {
     "name": "Uniqueness",
     "text": "Whether each thing is recorded once, without duplication"
    },
    {
     "name": "Consistency",
     "text": "Whether values agree with other values about the same thing, within or across data sets"
    },
    {
     "name": "Timeliness",
     "text": "Whether data is up to date for its use, with an acceptable lag"
    },
    {
     "name": "Validity",
     "text": "Whether data is in the expected range and format"
    },
    {
     "name": "Accuracy",
     "text": "How closely data matches reality"
    }
   ],
   "escalation_note": "Timescales from the GDS issues framework, which presents them as an example; triggers from the Data Quality Commons.",
   "escalation": [
    {
     "level": "Critical",
     "who": "Data owner, with the board informed",
     "trigger": "A critical data element in the lowest band, or wrong data could harm people or break the law",
     "when": "Immediately"
    },
    {
     "level": "High",
     "who": "Data owner",
     "trigger": "More than one band below target",
     "when": "Within one cycle"
    },
    {
     "level": "Medium",
     "who": "Steward",
     "trigger": "One band below target",
     "when": "Within three cycles"
    },
    {
     "level": "Low",
     "who": "Steward",
     "trigger": "Slightly below target with low impact",
     "when": "Within six cycles"
    }
   ],
   "measures": [
    {
     "name": "Critical data assets with a current DQAP",
     "target": "100%"
    },
    {
     "name": "Critical data elements with at least one rule",
     "target": "100%"
    },
    {
     "name": "Critical issues resolved within timescale",
     "target": "100%"
    },
    {
     "name": "Assets with quality information on the catalogue record",
     "target": "100%"
    }
   ],
   "templates": [
    {
     "id": "T-DQ-1",
     "mode": "Both",
     "name": "Data quality rule",
     "fields": [
      "Rule ID",
      "Data element",
      "Plain-English rule",
      "Dimension",
      "Test",
      "Importance (1-4)",
      "Impact (1-4)",
      "Combined score",
      "Target (%)",
      "Owner (role)",
      "Date agreed"
     ]
    },
    {
     "id": "T-DQ-2",
     "mode": "Both",
     "name": "Issue log entry",
     "fields": [
      "Issue ID",
      "Date found",
      "Rule ID",
      "Records affected",
      "Users or groups affected",
      "Performance and target",
      "Band",
      "Priority",
      "Target resolution date",
      "Root cause",
      "Action and owner (role)",
      "Status"
     ]
    },
    {
     "id": "T-DQ-3",
     "mode": "BAU",
     "name": "Data quality statement",
     "fields": [
      "Asset and version",
      "Date",
      "Summary in plain English",
      "Scores by dimension and trend",
      "Known issues",
      "Quality by group where lawful",
      "Fit for",
      "Not fit for",
      "How to report a problem (form)"
     ]
    }
   ],
   "tools": [
    {
     "name": "Check a CSV file in the browser",
     "url": "https://cyberdudeuk.github.io/dq-commons/check.html"
    },
    {
     "name": "Score issues with the issues framework",
     "url": "https://cyberdudeuk.github.io/dq-commons/guidance.html"
    },
    {
     "name": "Full data quality management playbook",
     "url": "https://cyberdudeuk.github.io/dq-commons/playbook.html"
    },
    {
     "name": "Size a critical data asset baseline",
     "url": "https://cyberdudeuk.github.io/dq-commons/baseline.html"
    }
   ]
  }
 ],
 "interlocks": [
  {
   "id": "IL-01",
   "from": "gov.assign",
   "to": "cat.own",
   "what": "The ownership register is the source for the owner and successor on the catalogue record. Record them once."
  },
  {
   "id": "IL-02",
   "from": "cat.own",
   "to": "dq.identify",
   "what": "The owner on the catalogue record is the owner who signs off DQAP targets and accepts risks."
  },
  {
   "id": "IL-03",
   "from": "cat.designate",
   "to": "dq.identify",
   "what": "The asset boundary set at designation is the scope of the DQAP. No DQAP for fields outside the asset."
  },
  {
   "id": "IL-04",
   "from": "dq.report",
   "to": "cat.describe",
   "what": "Quality information is published on the catalogue record, so the record says how good the data is."
  },
  {
   "id": "IL-05",
   "from": "dq.report",
   "to": "gov.operate",
   "what": "Quality issues above Medium enter the board's issue and risk log."
  },
  {
   "id": "IL-06",
   "from": "gov.frame",
   "to": "cat.describe",
   "what": "The metadata standard and the classification policy adopted in Frame are what records are checked against."
  },
  {
   "id": "IL-07",
   "from": "cat.maintain",
   "to": "dq.review",
   "what": "One annual review date per asset covers the record, the owner and the DQAP together."
  },
  {
   "id": "IL-08",
   "from": "cat.report",
   "to": "gov.assure",
   "what": "The GDS return is part of the governance evidence pack, assembled as you go."
  },
  {
   "id": "IL-09",
   "from": "gov.assure",
   "to": "gov.mandate",
   "what": "Lessons from assurance refresh the mandate for the next cycle."
  }
 ],
 "cycle": [
  {
   "when": "Before the window",
   "gov": "Confirm the mandate and owners",
   "cat": "Mobilise and refresh candidates",
   "dq": "Agree rules for any new assets"
  },
  {
   "when": "Through the year",
   "gov": "Operate the logs",
   "cat": "Describe and keep records current",
   "dq": "Measure each cycle and fix at source"
  },
  {
   "when": "Quarterly",
   "gov": "Board sees measures and exceptions",
   "cat": "Check harvest and record currency",
   "dq": "Update the action plan and statement"
  },
  {
   "when": "Annual review date",
   "gov": "Assure and refresh the mandate",
   "cat": "Review every record and submit the return",
   "dq": "Review rules and targets"
  }
 ],
 "library": [
  {
   "id": "LIB-01",
   "title": "Data asset management policy in government",
   "cap": [
    "gov",
    "cat",
    "dq"
   ],
   "type": "Policy",
   "status": "Published",
   "audience": "All",
   "src": "SRC-DAM",
   "prov": "V"
  },
  {
   "id": "LIB-02",
   "title": "Identifying and recording critical data assets",
   "cap": [
    "cat",
    "gov"
   ],
   "type": "Guidance",
   "status": "Published",
   "audience": "Coordinators",
   "src": "SRC-IDC",
   "prov": "V"
  },
  {
   "id": "LIB-03",
   "title": "Recording metadata to describe critical data assets",
   "cap": [
    "cat"
   ],
   "type": "Guidance",
   "status": "Published",
   "audience": "Stewards and catalogue managers",
   "src": "SRC-MD",
   "prov": "V"
  },
  {
   "id": "LIB-04",
   "title": "Data ownership model",
   "cap": [
    "gov"
   ],
   "type": "Guidance",
   "status": "Published",
   "audience": "Owners and CDOs",
   "src": "SRC-OWN",
   "prov": "V"
  },
  {
   "id": "LIB-05",
   "title": "The role of information asset owners in government",
   "cap": [
    "gov"
   ],
   "type": "Guidance",
   "status": "Published",
   "audience": "IAOs and SIROs",
   "src": "SRC-IAO",
   "prov": "V"
  },
  {
   "id": "LIB-06",
   "title": "The Government Data Quality Framework",
   "cap": [
    "dq"
   ],
   "type": "Framework",
   "status": "Published",
   "audience": "All",
   "src": "SRC-GDQF",
   "prov": "V"
  },
  {
   "id": "LIB-07",
   "title": "Data quality action plan implementation guide and template",
   "cap": [
    "dq"
   ],
   "type": "Guidance",
   "status": "Published",
   "audience": "Stewards",
   "src": "SRC-DQAP",
   "prov": "V"
  },
  {
   "id": "LIB-08",
   "title": "Data quality issues framework",
   "cap": [
    "dq"
   ],
   "type": "Method",
   "status": "Published",
   "audience": "Stewards and analysts",
   "src": "SRC-DQIF",
   "prov": "V"
  },
  {
   "id": "LIB-09",
   "title": "Data maturity assessment for government",
   "cap": [
    "gov"
   ],
   "type": "Framework",
   "status": "Published",
   "audience": "CDOs",
   "src": "SRC-DMA",
   "prov": "V"
  },
  {
   "id": "LIB-10",
   "title": "UK Cross-Government Metadata Exchange Model",
   "cap": [
    "cat"
   ],
   "type": "Standard",
   "status": "Published",
   "audience": "Catalogue managers",
   "src": "SRC-MEM",
   "prov": "V"
  },
  {
   "id": "LIB-11",
   "title": "DCAT version 3",
   "cap": [
    "cat"
   ],
   "type": "Standard",
   "status": "Published",
   "audience": "Catalogue managers",
   "src": "SRC-DCAT",
   "prov": "K"
  },
  {
   "id": "LIB-12",
   "title": "W3C Data Quality Vocabulary",
   "cap": [
    "dq",
    "cat"
   ],
   "type": "Standard",
   "status": "Published",
   "audience": "Catalogue managers",
   "src": "SRC-DQV",
   "prov": "K"
  },
  {
   "id": "LIB-13",
   "title": "Open Data Contract Standard",
   "cap": [
    "dq"
   ],
   "type": "Standard",
   "status": "Published",
   "audience": "Analysts and engineers",
   "src": "SRC-ODCS",
   "prov": "K"
  },
  {
   "id": "LIB-14",
   "title": "Public Sector Data Quality Commons (tools and playbook)",
   "cap": [
    "dq",
    "cat"
   ],
   "type": "Toolkit",
   "status": "Prototype",
   "audience": "Stewards and analysts",
   "src": "SRC-DQC",
   "prov": "P"
  },
  {
   "id": "LIB-15",
   "title": "Data manual, data management section",
   "cap": [
    "gov",
    "cat",
    "dq"
   ],
   "type": "Index",
   "status": "Published",
   "audience": "All",
   "src": "SRC-MAN",
   "prov": "V"
  },
  {
   "id": "LIB-16",
   "title": "Data Cataloguing Playbook v2.6 and learner journey",
   "cap": [
    "cat"
   ],
   "type": "Playbook",
   "status": "Internal",
   "audience": "Coordinators",
   "src": null,
   "prov": "P",
   "note": "Held internally; not public. Its content is what the cataloguing stages here should be checked against (OR-01)."
  },
  {
   "id": "LIB-17",
   "title": "Data Governance Playbook suite (main manual, toolkit, templates, pocket guides, assessment, Command Centre)",
   "cap": [
    "gov"
   ],
   "type": "Playbook",
   "status": "Internal draft",
   "audience": "Owners, stewards and boards",
   "src": null,
   "prov": "P",
   "note": "The source of the five recipes. Decks in the suite stay outside this repository."
  },
  {
   "id": "LIB-18",
   "title": "Canonical shared glossary of the data playbook compendium",
   "cap": [
    "gov",
    "cat",
    "dq"
   ],
   "type": "Vocabulary",
   "status": "Internal draft",
   "audience": "All",
   "src": null,
   "prov": "P",
   "note": "The terms here reconcile with it; eight conflicts it logged are tracked in the open register."
  },
  {
   "id": "LIB-19",
   "title": "Data Maturity and Transformation suite (MAT-01 to MAT-05) and crosswalk spine",
   "cap": [
    "gov"
   ],
   "type": "Playbook",
   "status": "Internal draft",
   "audience": "CDOs",
   "src": null,
   "prov": "P",
   "note": "Spine indicators S04, S08, S09 and S10 map to the three capabilities."
  },
  {
   "id": "LIB-20",
   "title": "DQAP template workbook",
   "cap": [
    "dq"
   ],
   "type": "Template",
   "status": "Published",
   "audience": "Stewards",
   "src": "SRC-DQAP",
   "prov": "V",
   "note": "Downloadable from the DQAP guide; the Commons can produce a filled one from rule results."
  }
 ],
 "concepts": [
  {
   "id": "data-asset",
   "term": "Data asset",
   "alt": [],
   "broader": null,
   "caps": [
    "cat",
    "gov"
   ],
   "src": "SRC-DAM",
   "prov": "V",
   "def": "One or more data sets plus, where relevant, the data services used to access them."
  },
  {
   "id": "data-set",
   "term": "Data set",
   "alt": [
    "dataset"
   ],
   "broader": "data-asset",
   "caps": [
    "cat"
   ],
   "src": "SRC-DAM",
   "prov": "V",
   "def": "A structured collection of data selected and organised for a defined outcome or need. It can be a subset of a larger system."
  },
  {
   "id": "data-service",
   "term": "Data service",
   "alt": [
    "API",
    "access service"
   ],
   "broader": "data-asset",
   "caps": [
    "cat"
   ],
   "src": "SRC-DAM",
   "prov": "V",
   "def": "A controlled means of accessing one or more data sets, such as an API or secure access mechanism."
  },
  {
   "id": "distribution",
   "term": "Distribution",
   "alt": [
    "representation"
   ],
   "broader": "data-set",
   "caps": [
    "cat"
   ],
   "src": "SRC-MEM",
   "prov": "V",
   "def": "A specific representation of a data set, for example a CSV file or a feed."
  },
  {
   "id": "cda",
   "term": "Critical data asset",
   "alt": [
    "CDA",
    "essential shared data asset",
    "ESDA"
   ],
   "broader": "data-asset",
   "caps": [
    "cat",
    "gov",
    "dq"
   ],
   "src": "SRC-IDC",
   "prov": "V",
   "def": "A data asset shared across government where losing access could stop an organisation from fulfilling important functions. 'Essential shared data asset' is the older term it replaced."
  },
  {
   "id": "provided",
   "term": "Provided data",
   "alt": [],
   "broader": "cda",
   "caps": [
    "cat"
   ],
   "src": "SRC-IDC",
   "prov": "V",
   "def": "Data one organisation gives to another to support an essential process or purpose the receiver is responsible for."
  },
  {
   "id": "acquired",
   "term": "Acquired data",
   "alt": [],
   "broader": "cda",
   "caps": [
    "cat"
   ],
   "src": "SRC-IDC",
   "prov": "V",
   "def": "Data one organisation obtains from another to support an essential process or purpose it is responsible for."
  },
  {
   "id": "purpose",
   "term": "Purpose",
   "alt": [
    "the seven purposes"
   ],
   "broader": "cda",
   "caps": [
    "cat"
   ],
   "src": "SRC-IDC",
   "prov": "V",
   "def": "One of the seven reasons a critical data asset matters, such as public service delivery or official statistics. Each asset supports at least one."
  },
  {
   "id": "scope-tests",
   "term": "Scope tests",
   "alt": [],
   "broader": "cda",
   "caps": [
    "cat",
    "gov"
   ],
   "src": "SRC-DAM",
   "prov": "V",
   "def": "The conditions an asset must meet to be in scope of the policy: classified OFFICIAL, critical, and within the provider's ownership accountabilities."
  },
  {
   "id": "metadata",
   "term": "Metadata",
   "alt": [
    "data about data"
   ],
   "broader": null,
   "caps": [
    "cat"
   ],
   "src": "SRC-MD",
   "prov": "V",
   "def": "Information that describes a data asset so it can be found, understood, validated, reused and shared."
  },
  {
   "id": "catalogue",
   "term": "Data catalogue",
   "alt": [
    "catalog",
    "metadata catalogue"
   ],
   "broader": null,
   "caps": [
    "cat"
   ],
   "src": "SRC-DAM",
   "prov": "O",
   "def": "A managed collection of metadata records that helps people and systems find, understand and reuse data assets. It holds descriptions, not the data."
  },
  {
   "id": "dcat",
   "term": "DCAT",
   "alt": [
    "Data Catalog Vocabulary"
   ],
   "broader": "metadata",
   "caps": [
    "cat"
   ],
   "src": "SRC-DCAT",
   "prov": "K",
   "def": "The W3C vocabulary for describing data sets and data services in catalogues, so catalogues can be harvested and searched together."
  },
  {
   "id": "mem",
   "term": "Metadata Exchange Model",
   "alt": [
    "xGov MEM",
    "MEM"
   ],
   "broader": "metadata",
   "caps": [
    "cat"
   ],
   "src": "SRC-MEM",
   "prov": "V",
   "def": "The UK cross-government model, based on DCAT, for the metadata exchanged about data assets."
  },
  {
   "id": "discoverability",
   "term": "Discoverability Platform",
   "alt": [
    "discovery service"
   ],
   "broader": "catalogue",
   "caps": [
    "cat"
   ],
   "src": null,
   "prov": "P",
   "def": "The GDS service being scoped to link to departments' own catalogues and make critical data asset metadata discoverable across government."
  },
  {
   "id": "return",
   "term": "Return",
   "alt": [
    "CDA return",
    "baseline return",
    "annual return"
   ],
   "broader": null,
   "caps": [
    "cat",
    "gov"
   ],
   "src": "SRC-DAM",
   "prov": "O",
   "def": "An organisation's report of its in-scope assets and their metadata to GDS, assured by the department for its ALBs."
  },
  {
   "id": "data-owner",
   "term": "Data owner",
   "alt": [],
   "broader": "role",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "src": "SRC-OWN",
   "prov": "V",
   "def": "A senior leader accountable for the meaning, content, quality and management of a data asset."
  },
  {
   "id": "iao",
   "term": "Information asset owner",
   "alt": [
    "IAO"
   ],
   "broader": "role",
   "caps": [
    "gov"
   ],
   "src": "SRC-OWN",
   "prov": "V",
   "def": "The role accountable to the SIRO for protecting the whole information asset. Related to, but not the same as, the data owner."
  },
  {
   "id": "data-steward",
   "term": "Data steward",
   "alt": [],
   "broader": "role",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "src": "SRC-OWN",
   "prov": "V",
   "def": "The role running an asset day to day: standards, access, quality processes and documentation."
  },
  {
   "id": "data-custodian",
   "term": "Data custodian",
   "alt": [],
   "broader": "role",
   "caps": [
    "gov",
    "cat"
   ],
   "src": "SRC-OWN",
   "prov": "V",
   "def": "The technical expert for the system holding the data: storage, access controls, auditable change and disposal."
  },
  {
   "id": "role",
   "term": "Data role",
   "alt": [],
   "broader": null,
   "caps": [
    "gov"
   ],
   "src": "SRC-OWN",
   "prov": "O",
   "def": "A defined set of accountabilities for data. Records name roles, not people."
  },
  {
   "id": "ownership-option",
   "term": "Ownership option",
   "alt": [
    "IAO model",
    "hybrid model"
   ],
   "broader": "data-owner",
   "caps": [
    "gov"
   ],
   "src": "SRC-OWN",
   "prov": "V",
   "def": "The choice between keeping the IAO model, adopting the data ownership model, or a hybrid. Each must still meet the mandatory IAO actions."
  },
  {
   "id": "recipe",
   "term": "Recipe",
   "alt": [
    "governance recipe"
   ],
   "broader": null,
   "caps": [
    "gov"
   ],
   "src": null,
   "prov": "P",
   "def": "One of the five repeatable governance activities: Mandate, Frame, Assign, Operate, Assure."
  },
  {
   "id": "charter",
   "term": "Governance charter",
   "alt": [
    "charter"
   ],
   "broader": "recipe",
   "caps": [
    "gov"
   ],
   "src": null,
   "prov": "P",
   "def": "A one-page statement of a governance body's purpose, scope, authority and review cadence."
  },
  {
   "id": "decision-log",
   "term": "Decision log",
   "alt": [],
   "broader": "recipe",
   "caps": [
    "gov"
   ],
   "src": null,
   "prov": "P",
   "def": "A running record of governance decisions: what, who, why, when and the review trigger."
  },
  {
   "id": "exception",
   "term": "Exception",
   "alt": [
    "policy exception"
   ],
   "broader": "recipe",
   "caps": [
    "gov"
   ],
   "src": null,
   "prov": "P",
   "def": "A logged, time-bound deviation from policy with an owner and an expiry date. An exception without an expiry is an undocumented policy change."
  },
  {
   "id": "raci",
   "term": "RACI",
   "alt": [
    "decision rights"
   ],
   "broader": null,
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "src": "SRC-DQAP",
   "prov": "O",
   "def": "Responsible, Accountable, Consulted, Informed. One accountable role per activity."
  },
  {
   "id": "dqap",
   "term": "Data quality action plan",
   "alt": [
    "DQAP"
   ],
   "broader": null,
   "caps": [
    "dq"
   ],
   "src": "SRC-DAM",
   "prov": "V",
   "def": "The plan every identified asset must have, or an equivalent mechanism, for managing its quality across seven steps."
  },
  {
   "id": "cde",
   "term": "Critical data element",
   "alt": [
    "CDE"
   ],
   "broader": "dqap",
   "caps": [
    "dq",
    "cat"
   ],
   "src": "SRC-DQC",
   "prov": "P",
   "def": "A data item whose quality drives the most important decisions made with the asset."
  },
  {
   "id": "dimension",
   "term": "Data quality dimension",
   "alt": [
    "dimension"
   ],
   "broader": "dqap",
   "caps": [
    "dq"
   ],
   "src": "SRC-GDQF",
   "prov": "V",
   "def": "A measurable aspect of quality. The framework's six are completeness, uniqueness, consistency, timeliness, validity and accuracy."
  },
  {
   "id": "issues-framework",
   "term": "Issues framework",
   "alt": [
    "data quality issues framework"
   ],
   "broader": "dqap",
   "caps": [
    "dq"
   ],
   "src": "SRC-DQIF",
   "prov": "V",
   "def": "The GDS method that scores importance times impact to set targets, and uses the band below target to set priority and time to resolve."
  },
  {
   "id": "dq-statement",
   "term": "Data quality statement",
   "alt": [
    "quality statement"
   ],
   "broader": "dqap",
   "caps": [
    "dq",
    "cat"
   ],
   "src": "SRC-DQC",
   "prov": "P",
   "def": "A plain-English summary of an asset's quality, known issues and what it should not be used for."
  },
  {
   "id": "dqv",
   "term": "Data Quality Vocabulary",
   "alt": [
    "DQV"
   ],
   "broader": "metadata",
   "caps": [
    "dq",
    "cat"
   ],
   "src": "SRC-DQV",
   "prov": "K",
   "def": "The W3C vocabulary for publishing quality measurements with a catalogue record."
  },
  {
   "id": "data-contract",
   "term": "Data contract",
   "alt": [
    "ODCS"
   ],
   "broader": "dqap",
   "caps": [
    "dq"
   ],
   "src": "SRC-ODCS",
   "prov": "K",
   "def": "Quality rules and promises written down as a file that suppliers and users share."
  },
  {
   "id": "maturity",
   "term": "Data maturity",
   "alt": [
    "DMA"
   ],
   "broader": null,
   "caps": [
    "gov"
   ],
   "src": "SRC-DMA",
   "prov": "V",
   "def": "An organisation's capability around data, self-assessed with the government framework."
  },
  {
   "id": "coordinator",
   "term": "Lead policy coordinator",
   "alt": [
    "policy coordinator"
   ],
   "broader": "role",
   "caps": [
    "gov",
    "cat"
   ],
   "src": null,
   "prov": "P",
   "def": "The person each organisation nominates to coordinate DAM Policy adoption and the return, and to sit on the Working Group."
  },
  {
   "id": "moscow",
   "term": "MoSCoW",
   "alt": [
    "Must Should Could Won't",
    "priority"
   ],
   "broader": null,
   "caps": [
    "gov"
   ],
   "src": null,
   "prov": "O",
   "def": "A way of ranking requirements or aims: Must have, Should have, Could have and Won't have this time."
  },
  {
   "id": "rfi",
   "term": "Request for information",
   "alt": [
    "RFI"
   ],
   "broader": null,
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "src": null,
   "prov": "O",
   "def": "Questions sent to suppliers before a tender to learn what the market offers and how products meet your requirements."
  },
  {
   "id": "tender",
   "term": "Tender",
   "alt": [
    "invitation to tender",
    "ITT",
    "request for proposal",
    "RFP"
   ],
   "broader": null,
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "src": null,
   "prov": "O",
   "def": "The formal invitation to suppliers to bid, with the requirements schedule, how bids will be evaluated and the contract terms."
  },
  {
   "id": "functional-req",
   "term": "Functional requirement",
   "alt": [
    "FR"
   ],
   "broader": null,
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "src": null,
   "prov": "O",
   "def": "What a tool must do, such as export catalogue records as DCAT."
  },
  {
   "id": "nonfunctional-req",
   "term": "Non-functional requirement",
   "alt": [
    "NFR"
   ],
   "broader": null,
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "src": null,
   "prov": "O",
   "def": "How well a tool must do it, such as accessibility, security, availability or the ability to export everything and leave."
  },
  {
   "id": "poc",
   "term": "Proof of concept",
   "alt": [
    "PoC"
   ],
   "broader": null,
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "src": null,
   "prov": "O",
   "def": "A short test of a product with your own data, to see whether it does what the supplier says before you buy."
  },
  {
   "id": "exit-plan",
   "term": "Exit plan",
   "alt": [
    "exit strategy"
   ],
   "broader": null,
   "caps": [
    "gov"
   ],
   "src": null,
   "prov": "O",
   "def": "How you would move your data and content out of a product, with the formats, steps, time and cost, written before you sign and tested each year."
  },
  {
   "id": "cpd",
   "term": "Continuing professional development",
   "alt": [
    "CPD"
   ],
   "broader": null,
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "src": null,
   "prov": "O",
   "def": "The learning you record to keep your skills current, often required by a professional body to keep a certification or chartered status."
  },
  {
   "id": "data-literacy",
   "term": "Data literacy",
   "alt": [
    "data skills"
   ],
   "broader": null,
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "src": null,
   "prov": "O",
   "def": "How well people across an organisation can read, understand, question and use data, and talk about it with confidence."
  }
 ],
 "open_register": [
  {
   "id": "OR-01",
   "reader": "The cataloguing method is built from public guidance",
   "item": "The internal Data Cataloguing Playbook v2.6 is not public. The cataloguing stages here are a synthesis of GOV.UK guidance and need checking against it, or replacing with it once cleared.",
   "who": "Service owner"
  },
  {
   "id": "OR-02",
   "reader": "How long private feedback is kept is not yet confirmed",
   "item": "Added on 5 November 2026: a private Microsoft Forms route, so people without a GitHub account can give feedback. Set on 8 November 2026: anyone can respond without signing in, names and accounts are not recorded, and every page and test task opens it with the page or task filled in. Contact details are optional and asked for only to reply or send a copy of the answers; Microsoft Forms cannot email an automatic receipt to people who do not sign in, so copies are sent by the maintainers. Still to confirm with the data protection officer: the data controller, how long responses and contact details are kept, and whether the privacy wording on the About page is enough.",
   "who": "Service owner, with the data protection officer"
  },
  {
   "id": "OR-03",
   "reader": "Not cleared as official guidance",
   "item": "Not cleared as official guidance. Clearance, and a move to an official GitHub organisation, are needed before departments are told to rely on it.",
   "who": "Service owner"
  },
  {
   "id": "OR-04",
   "reader": "Not yet tested with users",
   "item": "No research with real users yet. A research plan with questions, methods, hypotheses and falsification conditions is now published on the Service design page; it needs participants through the Working Group.",
   "who": "Service owner, with the Working Group"
  },
  {
   "id": "OR-05",
   "reader": "Interoperability requirements are not yet stated",
   "item": "The policy promises minimum interoperability requirements that its body does not state. The Tools and interoperability page proposes open standards for each boundary between tools; these are this portal's synthesis until GDS publishes requirements.",
   "who": "GDS Data Frameworks and Standards"
  },
  {
   "id": "OR-06",
   "reader": "Proposed metadata terms are not agreed",
   "item": "Four metadata properties in the guidance have no slot in the published MEM. A crosswalk to DCAT and Dublin Core terms is proposed on the cataloguing page (finding F-04) and needs agreement.",
   "who": "Metadata standards owner"
  },
  {
   "id": "OR-07",
   "reader": "Some dates come from material that is not public",
   "item": "Dates for the rollout phases, returns and support offer come from practitioner material, not a public page. Confirm before external use.",
   "who": "Service owner"
  },
  {
   "id": "OR-08",
   "reader": "Escalation timescales are a recommendation",
   "item": "The governance escalation timescales are this playbook's recommendation. Each organisation should set its own.",
   "who": "Each organisation's board"
  },
  {
   "id": "OR-09",
   "reader": "Not yet tested with disabled people",
   "item": "Not tested with disabled users or assistive technology users in person; automated checks only.",
   "who": "Service owner"
  },
  {
   "id": "OR-10",
   "item": "Data owner versus information asset owner is resolved by the GOV.UK data ownership model (three options). The two maturity models and the remaining glossary conflicts are not resolved here.",
   "who": "Service owner"
  },
  {
   "id": "OR-12",
   "reader": "Sector supplements need review by sector experts",
   "item": "All 14 sector themes now have supplements on the Sectors page, signposted from each capability playbook. Each supplement is this portal's synthesis and needs review by subject experts from its sector before organisations rely on it.",
   "who": "Service owner, with sector data leads"
  },
  {
   "id": "OR-13",
   "item": "Done on 5 November 2026: description, homepage, topics, Discussions, private vulnerability reporting, Dependabot, secret push protection and approval for workflows from all external contributors. Still to do: a ruleset on main that blocks force pushes and deletion and requires the 'Build, check and publish' check.",
   "who": "Repository owner"
  },
  {
   "id": "OR-14",
   "reader": "The maturity framework is linked, not copied",
   "item": "The Data Maturity Assessment framework is CC BY-NC-SA 4.0 and asks government users to contact CDDO. Confirm whether its level descriptions may be shown inside this portal; until then it is linked, not copied (F-05).",
   "who": "Service owner"
  },
  {
   "id": "OR-15",
   "reader": "Capability flags are this portal''s reading of the policy",
   "item": "The explicit, implicit and inferred flags on the capability model are this portal's reading of the policy. Ask the GDS data policy team to confirm them, especially the inferred ones.",
   "who": "Service owner, with GDS Data Frameworks and Standards"
  },
  {
   "id": "OR-16",
   "item": "Done on 5 November 2026: Pages publishes the built site from the gh-pages branch. Still to do: set the default workflow token to read-only and stop GitHub Actions creating or approving pull requests; every workflow already declares the permissions it needs. Narrow installed GitHub Apps to the repositories each needs.",
   "who": "Repository owner"
  },
  {
   "id": "OR-17",
   "item": "Decide whether to rewrite the four commits credited to the unrelated 'noreply' account (D-021). It removes the false credit but changes their identifiers and needs a force push to main.",
   "who": "Repository owner"
  },
  {
   "id": "OR-18",
   "item": "Decide which glossary is master. The compendium glossary (LIB-18), this portal's knowledge layer and the cross-portfolio shared glossary kept with the data asset register define overlapping terms, and the shared glossary logs six conflicts of its own. A scan on 11 November 2026 proposes the shared glossary as master, with this portal publishing only its public subset. Until decided, terms here reconcile with LIB-18 only.",
   "who": "Service owner, with the shared glossary's owner"
  },
  {
   "id": "OR-11",
   "item": "Verified on GOV.UK: Table 4 of the issues framework contradicts its own rule for a 97.5% target (finding F-01). Raise with the GDS data quality team; tracked as a repository issue.",
   "who": "Service owner"
  }
 ],
 "defects": [
  {
   "id": "D-001",
   "found": "Prior governance suite (September 2026)",
   "defect": "DQAP was expanded with the wrong middle word, as an 'assurance' plan.",
   "cause": "Expansion written from memory, not from the policy text.",
   "check": "C-06 bans the wrong expansion anywhere in content or pages."
  },
  {
   "id": "D-002",
   "found": "Prior governance suite (September 2026)",
   "defect": "Evidence was mapped to a policy annex that does not exist.",
   "cause": "An assumed reporting template was presented as fact.",
   "check": "C-07 bans references to the non-existent annex."
  },
  {
   "id": "D-003",
   "found": "This build, source reading",
   "defect": "The identification guidance page prints a team email address; copying source text risks putting it on the portal.",
   "cause": "Source text carries contact details.",
   "check": "C-04 fails the build on any email address in content or published files."
  },
  {
   "id": "D-004",
   "found": "This build, first browser run",
   "defect": "Focusing a tab panel, table region or the graph filled the whole block with the yellow focus colour.",
   "cause": "One focus rule targeted every element with a tabindex, including large containers.",
   "check": "B-03 focuses each container type and fails if its background becomes the focus colour."
  },
  {
   "id": "D-005",
   "found": "This build, vaccination tests",
   "defect": "The provenance check passed even when a requirement lost its label, because the source cell's own label satisfied it.",
   "cause": "The check looked for a label anywhere in the row, not in the requirement cell.",
   "check": "C-08 now inspects the requirement cell alone; its vaccination test removes that label and must fail."
  },
  {
   "id": "D-006",
   "found": "This build, first browser run",
   "defect": "Every page scrolled sideways on 320 and 390 pixel screens.",
   "cause": "The colophon barcode had a fixed pixel width.",
   "check": "B-02 checks overflow at six widths from 320 to 1920 pixels."
  },
  {
   "id": "D-007",
   "found": "This build, first browser run",
   "defect": "Links in the 'Met by' column were smaller than the 24 pixel target size.",
   "cause": "Plain inline links set side by side in a table cell.",
   "check": "B-01 runs axe with the WCAG 2.2 AA target-size rule in light and dark modes."
  },
  {
   "id": "D-008",
   "found": "This build (version 1.1), content review",
   "defect": "A bulk rename of the portal's owner in the open register also renamed the data owner in the quality escalation table.",
   "cause": "A pattern replacement matched role names inside the playbook methods.",
   "check": "The build refuses any escalation row that names the portal's service owner; a vaccination test proves it."
  },
  {
   "id": "D-009",
   "found": "This build (version 1.1), first browser run",
   "defect": "Module outcomes and persona goals containing commas were split into fragments such as 'Frame' and 'Assign'.",
   "cause": "Unquoted commas inside YAML flow lists.",
   "check": "The build refuses list items under three words; a vaccination test proves it."
  },
  {
   "id": "D-010",
   "found": "This build (version 1.1), static checks",
   "defect": "The external-assets check treated canonical links as remote loads.",
   "cause": "The check looked at every link element, not only ones the browser fetches.",
   "check": "C-05 now ignores canonical and alternate links; its existing vaccination still fails on a remote script."
  },
  {
   "id": "D-011",
   "found": "This build (version 1.1), screenshot review",
   "defect": "The contact form's first error link pointed to a radio button with no id, so it went nowhere.",
   "cause": "The error summary is written by script, so the static link check could not see it.",
   "check": "B-09 now checks every error summary link resolves to a field."
  },
  {
   "id": "D-012",
   "found": "First CI run on GitHub (version 1.1)",
   "defect": "The health step failed before running because its output folder did not exist on a fresh runner.",
   "cause": "The build folder is ignored by git, so it exists locally but not in CI.",
   "check": "The workflow creates the folder first; the CI run itself is the check and blocks publishing when it fails."
  },
  {
   "id": "D-013",
   "found": "First external link check (version 1.2)",
   "defect": "The health run reported a working GOV.UK organisation page as broken (HTTP 406).",
   "cause": "Page checks asked for JSON before HTML, which some GOV.UK pages refuse.",
   "check": "A unit test proves page checks ask for HTML first; it fails when the old header is restored."
  },
  {
   "id": "D-014",
   "found": "Browser checks (version 1.2)",
   "defect": "Stopping all table row headings from wrapping made the library, knowledge and policy pages scroll sideways on phones, and placed feature links too close together.",
   "cause": "A global no-wrap rule applied to long titles as well as short identifiers.",
   "check": "B-02 (sideways scrolling at six widths) and B-01 (target size) caught it; no-wrap now applies only to identifiers. A second cause was screen-reader-only labels inside wide tables escaping their scroll region; scroll regions are now positioned so they contain them."
  },
  {
   "id": "D-015",
   "found": "Browser checks (version 1.3)",
   "defect": "On the sectors page at 320 pixels, a filter drop-down sized itself to its longest option and pushed the page sideways.",
   "cause": "Flex items in the filter bar kept their minimum content width.",
   "check": "B-02 caught it before release; filter controls may now shrink to the screen width."
  },
  {
   "id": "D-016",
   "found": "Vaccination tests (version 1.4)",
   "defect": "The new check that every capability shows its explicit, implicit or inferred flag passed even when the flag was removed.",
   "cause": "Signpost badges inside the card use the same style, so the check found those instead.",
   "check": "C-22 now looks only in the card heading; the vaccination test that exposed it stays in the suite."
  },
  {
   "id": "D-017",
   "found": "Self-review before release 1.4",
   "defect": "The repository's CITATION.cff was published empty in release 1.2.0, so GitHub showed no citation.",
   "cause": "A version bump rewrote the file with a pattern that matched nothing and wrote back an empty result; no check looked at the file.",
   "check": "C-23 now checks the citation file is complete and names the portal's version; two vaccination tests prove it fails on a blank file and on version drift."
  },
  {
   "id": "D-018",
   "found": "Release 1.4 deployment",
   "defect": "Every workflow run since release 1.2.0 stopped before starting, so releases 1.2.0 to 1.4.0 were not published to GitHub Pages and CodeQL did not run.",
   "cause": "The repository only allows actions owned by its owner and pinned to a full commit SHA; the workflows used GitHub's own actions by version tag. Confirmed from the run annotation.",
   "check": "Workflows now use plain commands only (git checkout, the runner's Python and Node.js, the CodeQL command-line bundle checked against GitHub's published digest, and a push to the gh-pages branch). C-24 fails the build on any action the policy would refuse."
  },
  {
   "id": "D-019",
   "found": "Continuous integration after release 1.4",
   "defect": "A single 504 from github.com was recorded as a broken link. The Status page then printed the repository address, which contains the owner's account name, so the personal-details check failed the build and blocked publishing.",
   "cause": "The link check treated one server error as proof of a broken link, and the Status page quoted addresses verbatim.",
   "check": "The link check retries three times and only counts 404 and 410 as broken; other failures are 'temporarily unavailable'. The Status page names the portal's repository by role. Two tests prove both. CodeQL's bundle download also retries."
  },
  {
   "id": "D-020",
   "found": "Review of repository settings after release 1.4",
   "defect": "A suggested Jekyll workflow was added and Pages was set to publish from main, which would have published the raw repository files instead of the built portal.",
   "cause": "GitHub's Pages settings offer a Jekyll starter workflow by default; nothing in the repository explained that the built site lives on gh-pages.",
   "check": "C-24 refused the workflow (unpinned third-party actions) and the build failed safely. The workflow is removed, Pages publishes from gh-pages, and C-25 now fails if any workflow other than the three expected ones appears, or if any workflow publishes from the repository root."
  },
  {
   "id": "D-021",
   "found": "Owner report after release 1.4",
   "defect": "GitHub listed an unrelated account called 'noreply' (location China) as a contributor. It never acted on the repository; four early commits were credited to it.",
   "cause": "Automated build sessions committed with GitHub's generic noreply address under the username 'noreply', which GitHub links to the account with that username.",
   "check": "C-26 fails the build if the latest commit uses any identity outside an allow-list of the owner, GitHub's bots and the named assistant. Removing the credit on GitHub itself needs those four commits rewritten (OR-17)."
  },
  {
   "id": "D-022",
   "found": "Owner report on the live portal (version 1.4)",
   "defect": "The Playbooks and Frameworks menus opened but showed nothing and could not be clicked, on desktop and inside the More menu on phones.",
   "cause": "The top bar hid overflow so it could measure when to fold items into More, and that also cut off the drop-down menus positioned inside it. No browser check opened the menus.",
   "check": "The top bar no longer hides overflow; folding still works because it measures scroll width. B-14 opens every grouped menu at 1440 and 390 pixels, checks its first link can be hit and clicked, and follows it; a deliberate break that restores the clipping proves it fails."
  },
  {
   "id": "D-023",
   "found": "Browser checks (version 1.7, before release)",
   "defect": "The DAMA wheel's segment links had spoken names that did not match their visible labels, and the wheel's area cards pushed the page sideways at 320 pixels.",
   "cause": "Segment names were set separately from the visible text, and the card grid had a fixed minimum column width wider than a small phone.",
   "check": "B-01 (axe label and name match) and B-02 (sideways scrolling) caught both before release. Segment names now come from the visible label with the detail in a title, and the grid columns shrink to the screen."
  },
  {
   "id": "D-024",
   "found": "Browser checks (version 1.8, before release)",
   "defect": "Search found nothing on any page and Escape stopped closing it.",
   "cause": "The new guided tour script declared a step counter called idx in the same scope as the search index, so the index was replaced by the number 0.",
   "check": "B-05 (search finds results and Escape closes it) caught it before release. The tour counter is renamed and commented; B-16 now runs every tour and B-05 runs in the same browser session."
  },
  {
   "id": "D-025",
   "found": "Browser checks (version 1.8, before release)",
   "defect": "Keyboard shortcut hints in the header failed colour contrast in light mode, and the example configuration on the Use and reuse page pushed the page sideways on phones.",
   "cause": "A general style for keyboard keys overrode the header's own style, and the code block had no scrolling of its own.",
   "check": "B-01 (axe colour contrast) and B-02 (sideways scrolling) caught both. Key styles now apply only inside the main content and code blocks scroll within themselves."
  },
  {
   "id": "D-026",
   "found": "Comparison with the sister portals (version 1.8.0, after release)",
   "defect": "The new Tools and interoperability page covered the same ground as the Data Quality Commons Catalogues page released earlier the same day, which goes further, with named products, a lock-in checker, an RFI builder and a test script.",
   "cause": "The page was written without first looking at what the sister portals already offer.",
   "check": "The runbook now starts every new topic with a search of the sister portals. The tooling page keeps what the DAM Policy adds and signposts the Commons and the catalogue; C-34 checks those signposts go only to the sister portals and name them and their status."
  },
  {
   "id": "D-027",
   "found": "Continuous integration (version 1.8.2, before publishing)",
   "defect": "The search vaccination crashed instead of running, so the release stopped before publishing.",
   "cause": "Every deliberate-break script runs on every page. Adding the compass page, which has none of this portal's own objects, exposed a break script that assumed the search index exists. Only the new compass break was re-run locally after the page was added.",
   "check": "Every break script now does nothing where its target is absent, and a test runs each one on an empty page (D-027 in tests). All break modes are run locally before a push that adds a page to the browser checks."
  },
  {
   "id": "D-028",
   "found": "Continuous integration (version 1.8.3, before publishing)",
   "defect": "The Status page printed the owner's account name when the health run found a broken link to a sister portal.",
   "cause": "The D-019 fix only replaced this portal's own repository address. Version 1.8.3 linked to a Commons page that was committed but not yet published, so the health run quoted the Commons address in full.",
   "check": "Every address in the owner's account or Pages site is now named by what it is (this portal, the Commons, the catalogue), keeping the page name. A test feeds the Status page sister-portal problems and runs C-17 on it."
  },
  {
   "id": "D-029",
   "found": "Development (version 1.9.0)",
   "defect": "Re-running the icon vendoring script would have dropped 11 icons the site uses, including the compass and tools page icons.",
   "cause": "Icons added in versions 1.8.0 to 1.8.2 were written into site_src/icons.json directly, not added to the script's list.",
   "check": "The script's list now covers every icon, and a test fails if any icon the site uses is missing from it."
  },
  {
   "id": "D-030",
   "found": "Visual inspection (version 1.10.0)",
   "defect": "The Open data page said '1 files' and offered downloads for only a few datasets, because it was built before the data files were written.",
   "cause": "The page filters each dataset's files by whether they exist, and the data files are written after the pages.",
   "check": "The page is built again after the data files are written. C-28 now fails if any file in the catalogue has no download link on the Open data page."
  },
  {
   "id": "D-031",
   "found": "Visual inspection (version 1.10.0)",
   "defect": "What's new showed raw Markdown backticks around file names, such as `research.html`.",
   "cause": "Changelog lines were escaped as plain text.",
   "check": "Backticks are shown as code on What's new and in the releases feed. C-37 fails if a backtick appears in the visible text of What's new."
  },
  {
   "id": "D-032",
   "found": "Form set-up review (version 1.10.2)",
   "defect": "The private Microsoft feedback form opened blank from every page and test task, so a response could not be traced to the page or task it was about, and the portal said the form might ask people to sign in when it does not.",
   "cause": "Links used the bare form address, pre-filled answers were switched off in Microsoft Forms, and the form note was written before the response setting was chosen.",
   "check": "Pre-filled answers are on, and every link is built with the page or task filled in. C-33 now fails if any page lacks a link with that page filled in, if any test task is not filled in as task feedback, if a pre-fill question id is malformed, if a form link goes elsewhere or if the privacy wording is missing from About; the build rejects an unknown topic."
  },
  {
   "id": "D-033",
   "found": "Development (version 1.11.0, before publishing)",
   "defect": "A data dictionary format with a comma in it was split into a stray key with no value, so the title's format lost its second half without any error.",
   "cause": "Unquoted commas inside a YAML flow mapping start a new key.",
   "check": "The build now rejects any dictionary entry with unexpected or empty keys and says to quote values that contain a comma; a test proves it."
  },
  {
   "id": "D-037",
   "found": "Estate compass sync (12 November 2026)",
   "defect": "Every compass link to DCAT-AP-UK, and the DAM pages' Related link to it, returned 404 after the profile's site moved from dcat-uk-ap to dcat-ap-uk.",
   "cause": "Links into the other portals were only checked by hand; nothing re-read them when a portal changed.",
   "check": "tools/compass_sync.py reads every compass link into the other portals daily in CI, hides any that are gone, and opens a compass-sync issue; tests prove it finds a gone page and a missing anchor and treats an unreachable portal as unchecked."
  },
  {
   "id": "D-038",
   "found": "Visual inspection (compass 1.3)",
   "defect": "Opening the compass with no address jumped down the page to the first tab and outlined it.",
   "cause": "The pathway wrote the address while the page was still loading, so the browser then scrolled to that fragment and focused it.",
   "check": "The compass never writes the address while loading or to say what is already shown. C-35 checks the guard and B-17 checks that the page stays at the top with an empty address."
  },
  {
   "id": "D-034",
   "found": "Backlog work (version 1.12.0)",
   "defect": "Five template fields had been split in two since they were written, for example 'Ownership option (IAO' and 'data owner or hybrid)' in the ownership register, so downloads and the Library showed broken fields and inflated field counts.",
   "cause": "The same as D-033: unquoted commas in YAML flow lists start a new item.",
   "check": "Fields are quoted, and the build rejects any template field whose brackets do not balance; a test proves it. The C-39 health check also first missed a removed step because the reference titles repeat the words; it now looks for the steps themselves."
  },
  {
   "id": "D-035",
   "found": "Tooltip work (version 1.13.0)",
   "defect": "The menu links to the Governance, Cataloguing and Quality playbooks showed an empty tooltip on every page.",
   "cause": "Menu tooltips come from page descriptions, and the three playbook pages had none, so the grouped menu fell back to empty text.",
   "check": "Menu tooltips now fall back to the capability's purpose. C-40 fails any page with an empty tooltip; a test proves it."
  },
  {
   "id": "D-036",
   "found": "Pull request 24 (11 November 2026)",
   "defect": "The build failed twice before any check ran, because the runner could not reach Ubuntu's package mirror while installing the browser's system packages.",
   "cause": "One attempt, with no retry or fallback, at a step that depends on an outside mirror.",
   "check": "The workflow retries three times a minute apart, each attempt capped at 10 minutes after one ran for over 90 minutes without finishing, then installs the browser alone; the browser checks still fail if it cannot start. C-25 fails if the retry or the time limits go; two tests prove it."
  },
  {
   "id": "D-039",
   "found": "Visual inspection, owner report (compass 2.0, 13 November 2026)",
   "defect": "Six of the nine professions on the By profession tab showed no icon.",
   "cause": "The compass icon set was built only from icons named in the page template and a few lists; icons named only in the data, such as each profession's, were left out, so the browser drew empty symbols.",
   "check": "The build now takes every icon the data names. C-35 fails if any icon named in the data or the page has no symbol, and B-17 checks every profession card shows a drawn icon."
  },
  {
   "id": "D-040",
   "found": "Code review (13 November 2026)",
   "defect": "Defect numbers D-034 and D-035 were each used twice, by two sessions working at the same time.",
   "cause": "Defect ids were not checked for uniqueness, and sessions pick the next number from their own copy.",
   "check": "The build now rejects a duplicate defect id. The compass entries were renumbered D-037 and D-038; the earlier D-034 and D-035 keep their numbers."
  },
  {
   "id": "D-041",
   "found": "Visual inspection (13 November 2026)",
   "defect": "The compass's own self-check said the Repos Asset Catalogue facts were 36 days old, and one figure in them (25,981 projects) could no longer be reproduced from that catalogue's data.",
   "cause": "The 30-day freshness test ran only in the browser; nothing in CI or the daily sync looked at it.",
   "check": "The daily sync now lists portal facts older than 30 days and opens an issue for them. The facts were rechecked against the catalogue's repository and the unreproducible figure replaced with its README's own wording."
  },
  {
   "id": "D-042",
   "found": "Taking over pull request 33 (13 November 2026)",
   "defect": "The DAMA drill-down assessment still said eight areas had no activities and that data architecture had no steps, measures or standards, after the Knowledge areas page had added them.",
   "cause": "Two pieces of work changed the same area in parallel; the assessment was written as text, with nothing tying it to the activities it describes.",
   "check": "C-40 now fails if the assessment says areas have no activities, or that data architecture has no steps, measures or standards, while the Knowledge areas content has them. A test proves it."
  },
  {
   "id": "D-043",
   "found": "Development of the AI-ready pathway (version 1.15.0, before publishing)",
   "defect": "A check-of-understanding option, 'Someone owns quality, drift and bias monitoring', was split into two options, so the marked answer would have pointed at a fragment.",
   "cause": "The same class as D-009 and D-033: an unquoted comma in a YAML flow list starts a new item. D-009's guard covered outcomes and lists but not check options.",
   "check": "The build now rejects any check option that starts with a lower-case letter, the sign of a split, and says to quote it; a test proves it."
  },
  {
   "id": "D-044",
   "found": "Browser checks (version 1.15.0, before publishing)",
   "defect": "The new pathway card faded in, and axe reported every caption and line inside it as failing colour contrast in light and dark modes; two module links in the alignment table were also below the 24 pixel target size.",
   "cause": "An opacity animation lowers contrast while it runs and axe reads the page mid-animation; adjacent inline links in a narrow cell had no minimum size.",
   "check": "Motion on the card now moves without fading and the links have a 24 pixel minimum. C-44 fails if any keyframes animate opacity, with a test, and B-01 (axe) keeps checking contrast and target size."
  },
  {
   "id": "D-045",
   "found": "Health run issue 42 (13 November 2026)",
   "defect": "The health run reported the EU Data Act link on EUR-Lex as broken (404), although the address is the one the European Commission itself publishes. Locally the same check passed it with a 202, for a made-up law as well as the real one.",
   "cause": "EUR-Lex answers automated checks with an AWS WAF bot challenge instead of the page: 202 to some clients, 404 to others. The checker read the status alone, so a challenge counted as ok or as broken depending on the runner, and never as unchecked.",
   "check": "A response carrying a bot challenge header (x-amzn-waf-action or cf-mitigated), or a 202, is now blocked: listed for a person to check, not counted as ok or broken. Three tests prove a challenge is blocked whether it comes as 202 or 404, and that a plain 404 is still broken."
  },
  {
   "id": "D-046",
   "found": "Screenshot review of the data portals compass (version 1.15.0, before publishing)",
   "defect": "A compass route step title, 'What AI use adds to governance, cataloguing and quality', showed only up to the first comma. A new guard then found the same fault already published in 68 more values: the compass card 'Describe it once, the same way', and 67 values across playbooks.yaml (42) and frameworks.yaml (25), cut into 79 fragments, such as a facilitation option that lost ', magnifier or voice control' and escalation triggers that lost half their wording.",
   "cause": "In a YAML flow mapping an unquoted comma ends the value and turns the rest into a key with an empty value, which the build ignored. D-009 and D-043 guarded outcomes, lists and check options only.",
   "check": "The build now reads every flow mapping in playbooks.yaml, frameworks.yaml and areas.yaml by node position and rejects a key with an implicit empty value, naming the line; the compass rejects the same signature and unknown route-step keys. All 69 values were rejoined; a script proved that only the 79 empty fragments were removed and that every changed value starts with its old text. Four tests make deliberate breaks, and one proves an explicit null is still allowed."
  },
  {
   "id": "D-047",
   "found": "Applying the secure development standard (15 November 2026)",
   "defect": "No linter ran in CI. Ruff and ESLint found 51 findings in the tools, tests and site script. In the site script, the supplier wizard's and the DAMA role selector's name tables were both declared as the same variable (var names), so on a page carrying both, the role names would overwrite the supplier names and the wizard would list raw identifiers; it has not happened only because the two sit on different pages. A comment beginning \"global\" was read by the linter as a directive. In the build, six variables were computed and never used, including a role-guidance table the cards already render another way; the browser checks' error listeners captured the loop's list instead of binding it; and a build error hid the error that caused it.",
   "cause": "Lint was never part of the checks.",
   "check": "Ruff (Python) and ESLint (site_src JavaScript) run in Build, check and publish and fail on any finding. The DAMA table is now roleNames; dead code removed; listeners bind their own list; the build error chains its cause; the null-safety test asserts the exact Playwright error. tests/test_lint.py fails if either linter step or its pinned version goes missing."
  },
  {
   "id": "D-048",
   "found": "Code scanning (15 November 2026)",
   "defect": "Five places decided what a link was by searching for text inside it: the contact form sent people to whatever address its data-target attribute held, and the build and the research-page check treated any address containing github.com or .github.io as GitHub. A crafted address such as https://evil.example/?x=.github.io/ would have been shown as GitHub Pages, and the contact form had no allow-list.",
   "cause": "Substring tests instead of comparing the parsed host name; no allow-list on a navigation target.",
   "check": "The build and check_site compare the parsed host name; the contact form follows only a GitHub issue form address and does nothing otherwise. tests/test_hosts.py runs the allow-list against five addresses and fails against the previous site script. The built pages are unchanged apart from the build stamp."
  },
  {
   "id": "D-049",
   "found": "Licence review (15 November 2026)",
   "defect": "The licence note and the credits said the Public Sector Data Quality Commons' content was OGL v3.0. The Commons moved its own content to CC BY 4.0 in its release 2.16.1.",
   "cause": "Another portal's licence was copied once and never re-checked when that portal changed.",
   "check": "tests/test_licences.py checks the Commons credit and the licence note name CC BY 4.0, and fails against the previous text."
  },
  {
   "id": "D-050",
   "found": "Owner instruction (15 November 2026)",
   "defect": "One strategy entry still gave the Government Data Directorate's former name, and an internal backlog note named the owner's team.",
   "cause": "The directorate was restructured and renamed, and the rule never to name the team covered only what readers see on the site, not the source and documentation files.",
   "check": "C-17 now fails on the former name, its abbreviation or the team's name in any page, the README, the changelog, the content and compass files and docs. A test proves it."
  },
  {
   "id": "D-051",
   "found": "Weekly operations digest, issue 51 (17 November 2026)",
   "defect": "Build run 121 failed because one page of DCAT-AP-UK was missing from the compass directory, although the page was fine.",
   "cause": "The daily sync drops a page it cannot reach and flags it, but C-35 required every registered page to be in the directory, so one failed fetch on another website failed the whole build.",
   "check": "C-35 accepts a missing page only when the sync reported it gone. Two tests prove a page dropped without that report still fails, and one the sync reported does not."
  },
  {
   "id": "D-052",
   "found": "Reuse scan, issue 50 (17 November 2026)",
   "defect": "The release workflow failed if a person had already made the release, so the site zip was never attached.",
   "cause": "The step always ran gh release create, with no check for an existing release.",
   "check": "The step now attaches the files to an existing release. tests/test_release.py runs the step with a stand-in gh, and a deliberate break proves the old step is caught."
  },
  {
   "id": "D-053",
   "found": "Check C-45 on its first run (17 November 2026)",
   "defect": "The capability model said data architecture, records and cyber resilience had no guidance in this portal, although the knowledge area activities cover them.",
   "cause": "Coverage was typed by hand when the capability model was written and never updated when later releases added activities.",
   "check": "C-45 fails if any capability is still marked New, or has no activity in a playbook, a capability playbook or a knowledge area. A test proves it."
  },
  {
   "id": "D-054",
   "found": "Release checks (17 November 2026)",
   "defect": "Browser check B-17 failed now and then with a term has no tooltip, though the tooltip worked.",
   "cause": "The check waited a fixed 150 milliseconds after hovering; under load the tooltip took longer to appear.",
   "check": "B-17 now waits for the tooltip itself, for up to two seconds, so it fails only when the tooltip does not appear. Its deliberate break (compass) still fails it."
  },
  {
   "id": "D-055",
   "found": "Code scanning on pull request 55 (17 November 2026)",
   "defect": "The tailoring built link addresses partly from form values and stored choices, so a crafted value could have become a javascript address.",
   "cause": "A new script reused the link pattern without the allowlist that D-048 added elsewhere.",
   "check": "Links in the tailoring must be a page of this portal with an optional anchor, and stored choices must match known values. C-49 fails if the allowlist is removed, and a test proves it."
  }
 ],
 "adversarial": [
  {
   "challenge": "Another portal adds to the scatter it claims to fix. Practitioners already describe the playbooks as 'published, none joined'.",
   "answer": "It holds no second copy of anything with a master elsewhere. GOV.UK pages, the MEM and the Data Quality Commons are linked, not copied. What it adds is the join: the requirements matrix, one role model and the interlocks."
  },
  {
   "challenge": "Readers will mistake this playbook's stage sequences for GOV.UK requirements.",
   "answer": "Every requirement carries its source and strength (must, should, method, gap); stages are labelled as synthesis; provenance badges sit on every fact."
  },
  {
   "challenge": "Base rate: catalogue programmes commonly stall on adoption rather than on tooling (K, a lead not a measured fact).",
   "answer": "The method puts ownership before description and reporting from catalogue records, so effort lands where adoption fails. Whether that is enough is untested (OR-04)."
  },
  {
   "challenge": "It is built before learning from users.",
   "answer": "Named as a risk (OR-04). The journeys say they are assumed needs."
  },
  {
   "challenge": "It is hosted outside an official organisation and is not cleared.",
   "answer": "Stated on every page and in OR-03. The content is OGL and the code MIT, so it can move to an official organisation unchanged."
  }
 ],
 "pages": {
  "personas": {
   "lede": "Choose the role closest to yours. Each route shows what you need to learn, what to do and in what order, and tracks your progress as you go.",
   "audience": "Everyone using the playbooks"
  },
  "learning": {
   "lede": "Short modules that build from the basics of the policy to running all three capabilities as one yearly cycle. Each module lists what you will be able to do, the activities, and a quick check of understanding.",
   "audience": "Anyone new to the policy or to a role in it"
  },
  "inclusion": {
   "lede": "How the playbooks help you meet equality, diversity, inclusion and accessibility duties in your data work, and how this portal is designed so that everyone can use it.",
   "audience": "Everyone, especially data owners, stewards and governance boards"
  },
  "contact": {
   "lede": "Ask a question, report a problem or suggest an improvement.",
   "audience": "Everyone"
  }
 },
 "personas": [
  {
   "id": "cdo",
   "title": "Chief data officer",
   "icon": "building-2",
   "role": "CDO",
   "summary": "You are accountable for adopting the policy across your organisation and, in a department, its arm's length bodies.",
   "context": "You have little time, decide on resourcing and report progress to the Chief Data Officer Council. You need summaries first and detail on request.",
   "goals": [
    "Adopt the policy once, without the three capabilities duplicating effort",
    "Know your organisation's position at any time",
    "Show credible progress to the CDO Council"
   ],
   "needs": [
    {
     "need": "see what the policy requires and who does what",
     "so": "I can assign the work with confidence"
    },
    {
     "need": "a short, current view of progress",
     "so": "I can unblock problems before the return is due"
    }
   ],
   "pains": [
    "Governance, cataloguing and quality run by different teams record the same facts in different places",
    "Evidence is assembled in a rush at the deadline"
   ],
   "design_for": [
    "Reads on a phone between meetings",
    "Wants the summary before the detail"
   ],
   "success": "Every critical data asset has a named owner, a current catalogue record and a DQAP, and the return goes in on time.",
   "modules": [
    "M01",
    "M02",
    "M03",
    "M09",
    "M10",
    "M12",
    "M18"
   ],
   "journey": [
    {
     "stage": "Learn",
     "tasks": [
      {
       "m": "M01"
      },
      {
       "m": "M02"
      }
     ]
    },
    {
     "stage": "Prepare",
     "tasks": [
      {
       "p": "gov.mandate",
       "label": "Agree the mandate and scope"
      },
      {
       "p": "cat.mobilise",
       "label": "Appoint the coordinating team"
      }
     ]
    },
    {
     "stage": "Do",
     "tasks": [
      {
       "p": "gov.assign",
       "label": "Confirm owners for every critical asset"
      },
      {
       "p": "cat.designate",
       "label": "Approve designation decisions"
      }
     ]
    },
    {
     "stage": "Report",
     "tasks": [
      {
       "p": "cat.report",
       "label": "Sign off the return to GDS"
      }
     ]
    },
    {
     "stage": "Improve",
     "tasks": [
      {
       "p": "gov.assure",
       "label": "Review assurance and refresh the mandate"
      },
      {
       "m": "M09"
      },
      {
       "m": "M18"
      },
      {
       "a": "MAT-1"
      },
      {
       "a": "STR-1"
      }
     ]
    }
   ]
  },
  {
   "id": "coo",
   "title": "Lead policy coordinator",
   "icon": "clipboard-list",
   "role": "COO",
   "summary": "You coordinate adoption day to day, collate and assure the return, and represent your organisation at the Working Group.",
   "context": "You work across many teams, often alongside another role. You need one route from start to return and templates you can reuse.",
   "goals": [
    "Get the baseline return right first time",
    "Avoid retyping information that already exists",
    "Keep arm's length bodies in step"
   ],
   "needs": [
    {
     "need": "one ordered route from mobilising to an assured return",
     "so": "nothing is missed and nothing is done twice"
    },
    {
     "need": "templates that match what GDS asks for",
     "so": "the return is collation, not reconstruction"
    }
   ],
   "pains": [
    "Requests arrive from several directions with different deadlines",
    "Owners change and nobody updates the record"
   ],
   "design_for": [
    "Works compressed or part-time hours and picks tasks up after gaps",
    "New to data management"
   ],
   "success": "An assured return goes in on time, built from catalogue records rather than retyped.",
   "modules": [
    "M01",
    "M02",
    "M04",
    "M06",
    "M09",
    "M10",
    "M12",
    "M18"
   ],
   "journey": [
    {
     "stage": "Learn",
     "tasks": [
      {
       "m": "M01"
      },
      {
       "m": "M04"
      }
     ]
    },
    {
     "stage": "Prepare",
     "tasks": [
      {
       "p": "cat.mobilise",
       "label": "Set up the team and ALB contacts"
      },
      {
       "p": "cat.discover",
       "label": "Build the candidate list"
      }
     ]
    },
    {
     "stage": "Do",
     "tasks": [
      {
       "p": "cat.designate",
       "label": "Run designation"
      },
      {
       "p": "cat.own",
       "label": "Confirm owners and contact points"
      },
      {
       "p": "cat.describe",
       "label": "Get records completed"
      }
     ]
    },
    {
     "stage": "Report",
     "tasks": [
      {
       "p": "cat.report",
       "label": "Prepare and assure the return"
      }
     ]
    },
    {
     "stage": "Improve",
     "tasks": [
      {
       "p": "cat.maintain",
       "label": "Schedule the annual review"
      },
      {
       "m": "M09"
      },
      {
       "a": "SKILL-1"
      },
      {
       "a": "ASSR-1"
      }
     ]
    }
   ]
  },
  {
   "id": "own",
   "title": "Data owner",
   "icon": "key-round",
   "role": "OWN",
   "summary": "You are the senior leader accountable for the meaning, content, quality and management of one or more critical data assets.",
   "context": "Data ownership is one of several responsibilities. You make decisions and sign off; others do the day-to-day work.",
   "goals": [
    "Understand exactly what you are accountable for",
    "Make decisions quickly with the right evidence",
    "Name a successor so the asset is never orphaned"
   ],
   "needs": [
    {
     "need": "a clear list of the decisions that are mine",
     "so": "I can sign off with confidence"
    },
    {
     "need": "to see how good my data is and what it should not be used for",
     "so": "I can accept or reject risks knowingly"
    }
   ],
   "pains": [
    "Unclear difference between data owner and information asset owner",
    "Asked to sign things without the context"
   ],
   "design_for": [
    "Uses screen magnification at 200 per cent",
    "Prefers checklists to long text"
   ],
   "success": "You can explain your assets' purpose, quality and risks, and your successor is named.",
   "modules": [
    "M01",
    "M02",
    "M07",
    "M10",
    "M12",
    "M14"
   ],
   "journey": [
    {
     "stage": "Learn",
     "tasks": [
      {
       "m": "M01"
      },
      {
       "m": "M02"
      }
     ]
    },
    {
     "stage": "Prepare",
     "tasks": [
      {
       "p": "gov.assign",
       "label": "Accept the role and name a successor"
      }
     ]
    },
    {
     "stage": "Do",
     "tasks": [
      {
       "p": "dq.define",
       "label": "Agree quality targets"
      },
      {
       "p": "dq.prioritise",
       "label": "Decide priorities and accept risks"
      }
     ]
    },
    {
     "stage": "Report",
     "tasks": [
      {
       "p": "dq.report",
       "label": "Approve the data quality statement"
      }
     ]
    },
    {
     "stage": "Improve",
     "tasks": [
      {
       "p": "dq.review",
       "label": "Hold the annual review"
      },
      {
       "m": "M07"
      },
      {
       "a": "RISK-1"
      },
      {
       "a": "SUPP-1"
      }
     ]
    }
   ]
  },
  {
   "id": "stw",
   "title": "Data steward",
   "icon": "user-cog",
   "role": "STW",
   "summary": "You run critical data assets day to day - their standards, access, metadata and quality processes.",
   "context": "You do the detailed work and keep the records current. You need step-by-step methods and templates.",
   "goals": [
    "Keep the catalogue record and the DQAP current without heroics",
    "Find problems before users do",
    "Hand over cleanly when you move on"
   ],
   "needs": [
    {
     "need": "step-by-step instructions with templates",
     "so": "I can do the work consistently across assets"
    },
    {
     "need": "one place to record each fact once",
     "so": "the catalogue, the DQAP and the register always agree"
    }
   ],
   "pains": [
    "The same owner and review date recorded in three places",
    "Quality rules kept only in one tool"
   ],
   "design_for": [
    "Dyslexic and prefers short steps",
    "Uses a screen reader for long documents"
   ],
   "success": "Every asset you steward has a current record, rules with targets, and a quality statement users understand.",
   "modules": [
    "M01",
    "M05",
    "M07",
    "M08",
    "M10",
    "M12",
    "M13",
    "M14",
    "M17"
   ],
   "journey": [
    {
     "stage": "Learn",
     "tasks": [
      {
       "m": "M05"
      },
      {
       "m": "M07"
      }
     ]
    },
    {
     "stage": "Prepare",
     "tasks": [
      {
       "p": "dq.identify",
       "label": "Agree critical data elements"
      },
      {
       "p": "cat.describe",
       "label": "Complete the catalogue record"
      }
     ]
    },
    {
     "stage": "Do",
     "tasks": [
      {
       "p": "dq.define",
       "label": "Write rules and targets"
      },
      {
       "p": "dq.baseline",
       "label": "Measure a baseline"
      },
      {
       "p": "dq.improve",
       "label": "Fix causes at source"
      }
     ]
    },
    {
     "stage": "Report",
     "tasks": [
      {
       "p": "dq.report",
       "label": "Publish the quality statement"
      }
     ]
    },
    {
     "stage": "Improve",
     "tasks": [
      {
       "p": "dq.sustain",
       "label": "Automate checks"
      },
      {
       "m": "M08"
      },
      {
       "a": "CULT-1"
      }
     ]
    }
   ]
  },
  {
   "id": "cat",
   "title": "Catalogue manager or data custodian",
   "icon": "database",
   "role": "CAT",
   "summary": "You run the catalogue and the systems behind it, so records can be found, harvested and kept accurate.",
   "context": "You work with tools and standards. You need to know what any catalogue must expose, whatever the product.",
   "goals": [
    "Records that machines can harvest, not only people",
    "Conform to the cross-government metadata standard",
    "Avoid lock-in to one product"
   ],
   "needs": [
    {
     "need": "the exact metadata properties and how they map to the standard",
     "so": "records conform first time"
    },
    {
     "need": "to know what the Discoverability Platform will expect",
     "so": "we do not rebuild the feed later"
    }
   ],
   "pains": [
    "Guidance and model do not list the same properties",
    "Internal-only links break outside the organisation"
   ],
   "design_for": [
    "Works mainly by keyboard",
    "English is an additional language"
   ],
   "success": "Every critical data asset record is complete, conforms to the standard and can be harvested as DCAT.",
   "modules": [
    "M01",
    "M05",
    "M06",
    "M10",
    "M13",
    "M15",
    "M19"
   ],
   "journey": [
    {
     "stage": "Learn",
     "tasks": [
      {
       "m": "M05"
      },
      {
       "m": "M06"
      }
     ]
    },
    {
     "stage": "Prepare",
     "tasks": [
      {
       "p": "cat.discover",
       "label": "Search existing registers"
      }
     ]
    },
    {
     "stage": "Do",
     "tasks": [
      {
       "p": "cat.describe",
       "label": "Configure record fields"
      },
      {
       "p": "cat.publish",
       "label": "Expose records as DCAT"
      }
     ]
    },
    {
     "stage": "Report",
     "tasks": [
      {
       "p": "cat.report",
       "label": "Produce the return from records"
      }
     ]
    },
    {
     "stage": "Improve",
     "tasks": [
      {
       "p": "cat.maintain",
       "label": "Keep records current"
      },
      {
       "a": "TOOL-1"
      },
      {
       "m": "M19"
      }
     ]
    }
   ]
  },
  {
   "id": "dql",
   "title": "Data quality lead or analyst",
   "icon": "chart-line",
   "role": "DQL",
   "summary": "You bring methods and tools for measuring and improving quality across many assets.",
   "context": "You support several stewards. You need a consistent scoring method and tools that work without installing anything.",
   "goals": [
    "Score issues the same way across assets",
    "Automate measurement across assets",
    "Show quality fairly for every group the data describes"
   ],
   "needs": [
    {
     "need": "the government scoring method and tools that apply it",
     "so": "priorities are consistent and defensible"
    },
    {
     "need": "checks that break results down by group",
     "so": "poor quality for some people is not averaged away"
    }
   ],
   "pains": [
    "Every team scores issues differently",
    "Quality reported as one average"
   ],
   "design_for": [
    "Colour-blind, so charts must not rely on colour alone",
    "Works across several devices"
   ],
   "success": "Every critical data asset has scored issues, automated checks and quality reported by group where lawful.",
   "modules": [
    "M01",
    "M07",
    "M08",
    "M09",
    "M10",
    "M12",
    "M17",
    "M19"
   ],
   "journey": [
    {
     "stage": "Learn",
     "tasks": [
      {
       "m": "M07"
      },
      {
       "m": "M08"
      }
     ]
    },
    {
     "stage": "Prepare",
     "tasks": [
      {
       "p": "dq.define",
       "label": "Build the rule library"
      }
     ]
    },
    {
     "stage": "Do",
     "tasks": [
      {
       "p": "dq.baseline",
       "label": "Run baselines"
      },
      {
       "p": "dq.prioritise",
       "label": "Score and rank issues"
      }
     ]
    },
    {
     "stage": "Report",
     "tasks": [
      {
       "p": "dq.report",
       "label": "Publish quality metadata"
      }
     ]
    },
    {
     "stage": "Improve",
     "tasks": [
      {
       "p": "dq.sustain",
       "label": "Automate and monitor"
      },
      {
       "m": "M10"
      },
      {
       "a": "TOOL-3"
      }
     ]
    }
   ]
  },
  {
   "id": "prg",
   "title": "Programme or project lead",
   "icon": "construction",
   "role": "SRO",
   "summary": "You lead a medium or large change programme or project that creates, changes, migrates or retires critical data assets.",
   "context": "Your programme has its own governance, gates, budget and suppliers. Data asset management can feel like someone else's job until a gate review, a migration or handover exposes the gaps.",
   "goals": [
    "Pass assurance gates without late data surprises",
    "Hand over assets with owners and quality plans in place",
    "Avoid creating the next legacy system"
   ],
   "needs": [
    {
     "need": "to know which DAM duties apply to my programme and when",
     "so": "they are planned and funded from the business case"
    },
    {
     "need": "clear data roles inside my programme team",
     "so": "nobody assumes someone else is doing it"
    }
   ],
   "pains": [
    "Data owners sit outside the programme and are hard to reach",
    "Migration quality problems surface only at cutover"
   ],
   "design_for": [
    "Reads on the move between meetings",
    "Needs a one-page view to share with the programme board"
   ],
   "success": "Every critical asset the programme touches has an owner, a catalogue entry and a quality plan before the programme closes.",
   "modules": [
    "M01",
    "M02",
    "M11",
    "M09",
    "M18",
    "M19"
   ],
   "journey": [
    {
     "stage": "Learn",
     "tasks": [
      {
       "m": "M01"
      },
      {
       "m": "M11"
      }
     ]
    },
    {
     "stage": "Prepare",
     "tasks": [
      {
       "p": "gov.assign",
       "label": "Confirm data owners for every asset in scope of the programme"
      },
      {
       "p": "cat.discover",
       "label": "List the critical assets the programme creates, changes or retires"
      }
     ]
    },
    {
     "stage": "Do",
     "tasks": [
      {
       "p": "dq.define",
       "label": "Agree quality rules and targets with owners before build"
      },
      {
       "p": "cat.describe",
       "label": "Catalogue new assets before go-live"
      },
      {
       "a": "LEG-2"
      }
     ]
    },
    {
     "stage": "Report",
     "tasks": [
      {
       "p": "gov.assure",
       "label": "Show DAM evidence at each gate review"
      },
      {
       "a": "ASSR-1"
      }
     ]
    },
    {
     "stage": "Improve",
     "tasks": [
      {
       "p": "dq.sustain",
       "label": "Hand over the DQAP and ownership to business as usual"
      },
      {
       "m": "M09"
      },
      {
       "a": "HAND-2"
      },
      {
       "a": "BEN-1"
      }
     ]
    }
   ]
  },
  {
   "id": "buy",
   "title": "Commercial or technology lead",
   "icon": "handshake",
   "role": "CML",
   "summary": "You choose, buy or build the tools that catalogue, check and govern critical data, and you write the contracts that keep the data yours.",
   "context": "You are asked to find a catalogue, quality or master data tool quickly, often with a supplier's suite already on the table. You need requirements you can use, not a lecture on data management.",
   "goals": [
    "Buy what the DAM Policy actually needs",
    "Prove a tool works with our data before signing",
    "Keep the option to leave"
   ],
   "needs": [
    {
     "need": "ready-made requirements for each kind of tool, with priorities",
     "so": "I can run a request for information without starting from a blank page"
    },
    {
     "need": "contract clauses that protect our data",
     "so": "we are not locked in when the contract ends"
    }
   ],
   "pains": [
    "Supplier demonstrations use their data and not ours",
    "Bundled suites make it hard to price or leave one part"
   ],
   "design_for": [
    "Works to procurement deadlines",
    "Needs downloads that open in a spreadsheet"
   ],
   "success": "The tool chosen meets every Must requirement in a proof of concept with your own data, and the contract includes export, exit and data processing terms.",
   "modules": [
    "M01",
    "M11",
    "M19"
   ],
   "journey": [
    {
     "stage": "Learn",
     "tasks": [
      {
       "m": "M01"
      },
      {
       "m": "M19"
      }
     ]
    },
    {
     "stage": "Prepare",
     "tasks": [
      {
       "a": "TOOL-1"
      },
      {
       "a": "SUPP-1"
      }
     ]
    },
    {
     "stage": "Do",
     "tasks": [
      {
       "a": "TOOL-2"
      },
      {
       "a": "TOOL-3"
      },
      {
       "a": "SUPP-2"
      }
     ]
    },
    {
     "stage": "Report",
     "tasks": [
      {
       "a": "EXIT-2"
      }
     ]
    },
    {
     "stage": "Improve",
     "tasks": [
      {
       "a": "TOOL-4"
      },
      {
       "a": "EXIT-3"
      },
      {
       "m": "M11"
      }
     ]
    }
   ]
  }
 ],
 "modules": [
  {
   "id": "M01",
   "title": "The DAM Policy - what it asks of you",
   "level": "Foundation",
   "minutes": 15,
   "icon": "landmark",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "outcomes": [
    "Explain who the policy applies to and what is in scope",
    "Name the core duties: identify and catalogue assets, report them, name an owner and manage quality",
    "Find the requirement behind any step in these playbooks"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read the summary of who the policy applies to and what is in scope.",
     "link": "dam.html#scope"
    },
    {
     "id": "a2",
     "type": "Read",
     "text": "Scan the requirements table. Filter it to 'must' to see the core duties.",
     "link": "dam.html#requirements"
    },
    {
     "id": "a3",
     "type": "Do",
     "text": "Note which of the reporting dates applies to your organisation first.",
     "link": "dam.html#timeline"
    },
    {
     "id": "a4",
     "type": "Reflect",
     "text": "Which of the three capabilities is least developed in your organisation today?"
    }
   ],
   "check": [
    {
     "q": "Which organisations must follow the policy?",
     "options": [
      "All public bodies including councils",
      "UK government departments and their arm's length bodies",
      "Only departments that publish open data"
     ],
     "answer": 1,
     "why": "It applies to UK government departments and their ALBs. It is optional for public corporations and does not apply to councils."
    },
    {
     "q": "What must every identified data asset have?",
     "options": [
      "A named data owner and a DQAP or equivalent",
      "An open data licence",
      "A dedicated catalogue product"
     ],
     "answer": 0,
     "why": "The policy requires a named data owner and a data quality action plan, or an equivalent mechanism, for every identified asset."
    }
   ]
  },
  {
   "id": "M02",
   "title": "Roles and accountability",
   "level": "Foundation",
   "minutes": 15,
   "icon": "users-round",
   "caps": [
    "gov"
   ],
   "outcomes": [
    "Describe the data owner, data steward and data custodian roles",
    "Explain how the data owner relates to the information asset owner",
    "Choose between the three ownership options"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read the role model shared by all three playbooks.",
     "link": "together.html#roles"
    },
    {
     "id": "a2",
     "type": "Read",
     "text": "Read the Assign recipe and its checklist.",
     "link": "governance.html#gov-assign"
    },
    {
     "id": "a3",
     "type": "Do",
     "text": "List your critical data assets and the role that should own each one."
    },
    {
     "id": "a4",
     "type": "Reflect",
     "text": "Does every owner in your list have a named successor?"
    }
   ],
   "check": [
    {
     "q": "Which role is accountable for an asset's meaning, content and quality?",
     "options": [
      "Data custodian",
      "Data steward",
      "Data owner"
     ],
     "answer": 2,
     "why": "The data owner is the senior leader accountable. The steward runs the asset day to day; the custodian runs the technical system."
    },
    {
     "q": "What must happen when a data owner leaves?",
     "options": [
      "The asset is retired",
      "A successor is ready and the metadata is updated",
      "The steward becomes owner automatically"
     ],
     "answer": 1,
     "why": "The guidance asks you to tell the coordinating team, have a successor ready and update the metadata."
    }
   ]
  },
  {
   "id": "M03",
   "title": "Setting up governance with five recipes",
   "level": "Practitioner",
   "minutes": 30,
   "icon": "shield-check",
   "caps": [
    "gov"
   ],
   "outcomes": [
    "Run the Mandate, Frame, Assign, Operate and Assure recipes in order",
    "Set up a decision log and an exception register",
    "Collect evidence continuously for the GDS return"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Work through the five recipes step by step.",
     "link": "governance.html#method"
    },
    {
     "id": "a2",
     "type": "Do",
     "text": "Draft a one-page charter using the template.",
     "link": "governance.html#T-GOV-1"
    },
    {
     "id": "a3",
     "type": "Do",
     "text": "Set up a decision log and an exception register using the templates.",
     "link": "governance.html#T-GOV-3"
    },
    {
     "id": "a4",
     "type": "Reflect",
     "text": "Where will your evidence folder live, and who keeps it current?"
    }
   ],
   "check": [
    {
     "q": "What makes an exception different from a policy change?",
     "options": [
      "It has an owner and an expiry date",
      "It is approved by the minister",
      "It applies to all assets"
     ],
     "answer": 0,
     "why": "An exception is time-bound with an owner and an expiry date. Without an expiry it is an undocumented policy change."
    },
    {
     "q": "When should you assemble evidence for the return?",
     "options": [
      "In the month before the deadline",
      "Continuously during Operate",
      "Only after an audit"
     ],
     "answer": 1,
     "why": "Collecting evidence each time a decision is logged turns the return into collation rather than reconstruction."
    }
   ]
  },
  {
   "id": "M04",
   "title": "Finding and designating critical data assets",
   "level": "Practitioner",
   "minutes": 25,
   "icon": "search",
   "caps": [
    "cat"
   ],
   "outcomes": [
    "Build a candidate list from existing registers",
    "Apply the scope tests and the seven purposes",
    "Draw an asset's boundary and record why"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read stages 1 to 3 of the cataloguing method.",
     "link": "cataloguing.html#method"
    },
    {
     "id": "a2",
     "type": "Do",
     "text": "Start a candidate log using the designation template.",
     "link": "cataloguing.html#T-CAT-1"
    },
    {
     "id": "a3",
     "type": "Do",
     "text": "For one candidate, record which of the seven purposes it supports.",
     "link": "dam.html#DAM-R11"
    },
    {
     "id": "a4",
     "type": "Reflect",
     "text": "Have you looked at data you acquire from others, not only data you provide?"
    }
   ],
   "check": [
    {
     "q": "If you designate a distribution of a data set, what else should you designate?",
     "options": [
      "Nothing else",
      "Its source data set",
      "Every system that uses it"
     ],
     "answer": 1,
     "why": "The guidance asks you to designate the source data set as well."
    },
    {
     "q": "Which of these is one of the seven purposes?",
     "options": [
      "Marketing",
      "Official statistics",
      "Staff training"
     ],
     "answer": 1,
     "why": "Official statistics is one of the seven. The statistics themselves are not designated, only the data used to produce them."
    }
   ]
  },
  {
   "id": "M05",
   "title": "Describing assets with metadata others can use",
   "level": "Practitioner",
   "minutes": 30,
   "icon": "pencil-line",
   "caps": [
    "cat"
   ],
   "outcomes": [
    "Record the metadata properties in the GOV.UK guidance",
    "Write titles and descriptions in plain English",
    "Map properties to the Metadata Exchange Model"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read the metadata properties and how to record each one.",
     "link": "cataloguing.html#metadata"
    },
    {
     "id": "a2",
     "type": "Do",
     "text": "Complete a catalogue record for one asset using the template.",
     "link": "cataloguing.html#T-CAT-2"
    },
    {
     "id": "a3",
     "type": "Do",
     "text": "Ask someone outside your team to read the record and say what the data is for."
    },
    {
     "id": "a4",
     "type": "Reflect",
     "text": "Which properties did you have to mark 'unknown'? Who could supply them?"
    }
   ],
   "check": [
    {
     "q": "How should you record a date in a catalogue record?",
     "options": [
      "As written in the source system",
      "In ISO 8601 format",
      "In words"
     ],
     "answer": 1,
     "why": "The guidance asks for ISO 8601, for example 2020-07-14."
    },
    {
     "q": "What should you put when a property has no value?",
     "options": [
      "Leave it blank",
      "'unknown' or 'not applicable'",
      "A dash"
     ],
     "answer": 1,
     "why": "Use 'unknown' or 'not applicable' rather than leaving a blank."
    }
   ]
  },
  {
   "id": "M06",
   "title": "Cataloguing, harvesting and reporting to GDS",
   "level": "Practitioner",
   "minutes": 20,
   "icon": "share-2",
   "caps": [
    "cat"
   ],
   "outcomes": [
    "Expose records so others can harvest them",
    "Produce the return from catalogue records",
    "Plan the annual review"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read stages 6 to 8 of the cataloguing method.",
     "link": "cataloguing.html#cat-publish"
    },
    {
     "id": "a2",
     "type": "Do",
     "text": "Check that every link in one record works from outside your network."
    },
    {
     "id": "a3",
     "type": "Do",
     "text": "Put the annual review date in the same diary entry as the DQAP review.",
     "link": "together.html#cycle"
    }
   ],
   "check": [
    {
     "q": "How often must metadata be reviewed?",
     "options": [
      "Every 3 years",
      "At least every 12 months",
      "Only when the asset changes"
     ],
     "answer": 1,
     "why": "The policy asks for metadata to be maintained and reviewed annually."
    },
    {
     "q": "Who assures the returns of arm's length bodies?",
     "options": [
      "GDS",
      "Their department",
      "Each ALB alone"
     ],
     "answer": 1,
     "why": "Departments coordinate and assure the returns of their ALBs."
    }
   ]
  },
  {
   "id": "M07",
   "title": "Data quality foundations",
   "level": "Foundation",
   "minutes": 15,
   "icon": "gauge",
   "caps": [
    "dq"
   ],
   "outcomes": [
    "Name the five principles and six dimensions of the Government Data Quality Framework",
    "Explain what a DQAP is for",
    "Recognise when quality differs between groups of people"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read the principles and dimensions.",
     "link": "quality.html#principles"
    },
    {
     "id": "a2",
     "type": "Read",
     "text": "Read the overview of the quality playbook.",
     "link": "quality.html#overview"
    },
    {
     "id": "a3",
     "type": "Reflect",
     "text": "Which dimension matters most for your most important decision?"
    }
   ],
   "check": [
    {
     "q": "Which is one of the six dimensions?",
     "options": [
      "Popularity",
      "Timeliness",
      "Size"
     ],
     "answer": 1,
     "why": "The six are completeness, uniqueness, consistency, timeliness, validity and accuracy."
    },
    {
     "q": "Why break quality results down by group?",
     "options": [
      "To make reports longer",
      "So poor quality for some people is not averaged away",
      "Because the law always requires it"
     ],
     "answer": 1,
     "why": "An average can hide poor quality for some groups, which can exclude them from services."
    }
   ]
  },
  {
   "id": "M08",
   "title": "Building a DQAP and scoring issues",
   "level": "Practitioner",
   "minutes": 35,
   "icon": "list-ordered",
   "caps": [
    "dq"
   ],
   "outcomes": [
    "Write rules with targets from the issues framework",
    "Measure a baseline and log issues",
    "Prioritise issues and set resolution dates"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Work through the eight quality stages step by step.",
     "link": "quality.html#method"
    },
    {
     "id": "a2",
     "type": "Do",
     "text": "Write three rules for one critical data element using the template.",
     "link": "quality.html#T-DQ-1"
    },
    {
     "id": "a3",
     "type": "Do",
     "text": "Score an issue with the issues framework calculator.",
     "link": "https://cyberdudeuk.github.io/dq-commons/guidance.html"
    },
    {
     "id": "a4",
     "type": "Reflect",
     "text": "Which issue would you fix at source rather than clean downstream?"
    }
   ],
   "check": [
    {
     "q": "How does the issues framework set a rule's target range?",
     "options": [
      "From what the data already achieves",
      "From importance of purpose times impact",
      "From the size of the data set"
     ],
     "answer": 1,
     "why": "Importance of purpose multiplied by impact gives a combined score, which sets the target range."
    },
    {
     "q": "In the framework's example timescales, when is a critical issue resolved?",
     "options": [
      "Immediately",
      "Within three measurements",
      "Within six measurements"
     ],
     "answer": 0,
     "why": "The framework's example gives Critical as immediate; High, Medium and Low within 1, 3 and 6 measurements."
    }
   ]
  },
  {
   "id": "M09",
   "title": "Running the three capabilities as one yearly cycle",
   "level": "Advanced",
   "minutes": 20,
   "icon": "refresh-cw",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "outcomes": [
    "Use the hand-offs so each fact is recorded once",
    "Plan one annual review per asset",
    "Feed assurance lessons into the next mandate"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read the hand-offs between the capabilities.",
     "link": "together.html#interlocks"
    },
    {
     "id": "a2",
     "type": "Read",
     "text": "Read the joined-up year.",
     "link": "together.html#cycle"
    },
    {
     "id": "a3",
     "type": "Do",
     "text": "Pick one asset and check the owner is the same in the register, the record and the DQAP."
    }
   ],
   "check": [
    {
     "q": "Where should the owner and successor for an asset be recorded first?",
     "options": [
      "In the DQAP",
      "In the ownership register, then reused",
      "Separately in each tool"
     ],
     "answer": 1,
     "why": "The ownership register is the source; the catalogue record and the DQAP reuse it (IL-01, IL-02)."
    }
   ]
  },
  {
   "id": "M10",
   "title": "Inclusive data practice",
   "level": "Foundation",
   "minutes": 20,
   "icon": "heart-handshake",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "outcomes": [
    "Apply equality and inclusion checks in each capability",
    "Make data quality statements and records accessible",
    "Involve people the data describes"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read the inclusion checks for each capability.",
     "link": "inclusion.html#checks"
    },
    {
     "id": "a2",
     "type": "Do",
     "text": "Run the inclusion questions against one of your assets.",
     "link": "inclusion.html#questions"
    },
    {
     "id": "a3",
     "type": "Reflect",
     "text": "Whose voice is missing when you decide what 'good enough' means?"
    }
   ],
   "check": [
    {
     "q": "Which duty asks public bodies to consider equality in their work?",
     "options": [
      "The public sector equality duty",
      "The Freedom of Information Act",
      "The Statistics and Registration Service Act"
     ],
     "answer": 0,
     "why": "The public sector equality duty in the Equality Act 2010 applies to public authorities in their functions."
    }
   ]
  },
  {
   "id": "M11",
   "title": "Embedding the policy in delivery and change",
   "level": "Practitioner",
   "minutes": 30,
   "icon": "construction",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "outcomes": [
    "Name the capabilities the policy relies on but does not state",
    "Build DAM checkpoints into a business case and an assurance plan",
    "Plan a legacy exit and a handover to business as usual"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read what the policy leaves to you and the life cycle overlay.",
     "link": "change.html#gaps"
    },
    {
     "id": "a2",
     "type": "Do",
     "text": "Take one programme you know and tick the actions that already happen, then list the gaps.",
     "link": "change.html#practices"
    },
    {
     "id": "a3",
     "type": "Do",
     "text": "Run the self-assessment for your organisation and download the result.",
     "link": "capability-model.html#cm-self"
    },
    {
     "id": "a4",
     "type": "Reflect",
     "text": "Which critical asset would be left without an owner if its project closed tomorrow?"
    }
   ],
   "check": [
    {
     "q": "Which guidance makes a register of data assets its second principle?",
     "options": [
      "Managing legacy technology",
      "The Magenta Book",
      "The Service Standard"
     ],
     "answer": 0,
     "why": "The GOV.UK guidance on managing legacy technology asks organisations to build a complete and accurate register of their data assets."
    },
    {
     "q": "How does the capability model flag a need the DAM Policy text does not state at all?",
     "options": [
      "Inferred",
      "Implicit",
      "Explicit"
     ],
     "answer": 0,
     "why": "Inferred means the need is not in the text and comes from good practice and adjacent rulebooks."
    }
   ]
  },
  {
   "id": "M12",
   "title": "What makes a critical data asset AI-ready",
   "level": "Foundation",
   "minutes": 20,
   "icon": "sparkles",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "pathway": "ai-ready",
   "outcomes": [
    "Name the four pillars in the GDS guidelines on AI-ready datasets",
    "Decide whether an asset needs the AI-ready supplement",
    "Explain why AI-readiness is a stewardship question as well as a technical one"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read the executive summary and the four pillars of the GDS guidelines on making government datasets ready for AI.",
     "link": "https://www.gov.uk/government/publications/making-government-datasets-ready-for-ai/guidelines-and-best-practices-for-making-government-datasets-ready-for-ai"
    },
    {
     "id": "a2",
     "type": "Do",
     "text": "Answer the 'which supplements apply' questions for one asset. Note whether it is used, or may be used, for AI.",
     "link": "sectors.html#which"
    },
    {
     "id": "a3",
     "type": "Read",
     "text": "Read the AI-ready data supplement: what governance, cataloguing and quality each add.",
     "link": "sectors.html#SUP-AI"
    },
    {
     "id": "a4",
     "type": "Reflect",
     "text": "If someone asked tomorrow to train a model on your most important asset, who would say yes or no, and on what evidence?"
    }
   ],
   "check": [
    {
     "q": "Which of these is one of the four pillars of AI-ready data in the GDS guidelines?",
     "options": [
      "Data and metadata quality",
      "Cloud hosting",
      "Open source code"
     ],
     "answer": 0,
     "why": "The four pillars are technical optimisation; data and metadata quality; organisation and infrastructure context; and legal, security and ethical compliance."
    },
    {
     "q": "When does the AI-ready supplement ask you to publish an algorithmic transparency record?",
     "options": [
      "For every data set",
      "Where a tool supports decisions about people",
      "Only when a supplier asks"
     ],
     "answer": 1,
     "why": "The supplement asks for a record where an algorithmic tool supports decisions about people, using the Algorithmic Transparency Recording Standard."
    }
   ]
  },
  {
   "id": "M13",
   "title": "From FAIR to AI-ready metadata",
   "level": "Practitioner",
   "minutes": 30,
   "icon": "badge-check",
   "caps": [
    "cat"
   ],
   "pathway": "ai-ready",
   "outcomes": [
    "Explain the four FAIR principles in plain English",
    "Add the AI-ready catalogue fields to a record",
    "See how the proposed DCAT-AP-UK profile extends the xGov MEM for AI use"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read the FAIR Guiding Principles paper (Wilkinson and others, 2016) and note what each letter asks of metadata.",
     "link": "https://doi.org/10.1038/sdata.2016.18"
    },
    {
     "id": "a2",
     "type": "Read",
     "text": "Read the metadata properties this portal asks for, and the proposals to the Metadata Exchange Model.",
     "link": "cataloguing.html#metadata"
    },
    {
     "id": "a3",
     "type": "Do",
     "text": "For one record, add permitted AI uses, sensitive fields, provenance and version, as the AI-ready supplement lists.",
     "link": "sectors.html#t-cat-SUP-AI"
    },
    {
     "id": "a4",
     "type": "Read",
     "text": "Read the AI-ready metadata page of the proposed DCAT-AP-UK profile. It is proposed, not endorsed.",
     "link": "https://cyberdudeuk.github.io/dcat-ap-uk/ai-ready.html"
    },
    {
     "id": "a5",
     "type": "Do",
     "text": "Build your first record with the DCAT-AP-UK tutorial, then compare it with the endorsed xGov MEM.",
     "link": "https://cyberdudeuk.github.io/dcat-ap-uk/tutorials.html"
    }
   ],
   "check": [
    {
     "q": "What do the letters FAIR stand for?",
     "options": [
      "Findable, accessible, interoperable, reusable",
      "Fair, accurate, inclusive, responsible",
      "Federated, auditable, indexed, recorded"
     ],
     "answer": 0,
     "why": "The FAIR Guiding Principles (Wilkinson and others, 2016) are findability, accessibility, interoperability and reusability, for people and for machines."
    },
    {
     "q": "Why does the AI-ready supplement ask for a version on the record?",
     "options": [
      "To set the price",
      "So a training set can be reconstructed exactly",
      "Because DCAT forbids records without one"
     ],
     "answer": 1,
     "why": "The supplement asks for dcat:version so a training set can be reconstructed exactly."
    },
    {
     "q": "Which metadata model is endorsed for UK government today?",
     "options": [
      "DCAT-AP-UK",
      "The xGov MEM",
      "Schema.org"
     ],
     "answer": 1,
     "why": "The UK Cross-Government Metadata Exchange Model (xGov MEM) is endorsed by the Data Standards Authority Steering Board. DCAT-AP-UK is a proposal for review."
    }
   ]
  },
  {
   "id": "M14",
   "title": "Start from the question the data must answer",
   "level": "Practitioner",
   "minutes": 20,
   "icon": "crosshair",
   "caps": [
    "gov",
    "cat"
   ],
   "pathway": "ai-ready",
   "outcomes": [
    "Write down the decision or question an AI use of an asset serves",
    "Test that question against the seven purposes in the policy",
    "Record out-of-scope uses before anyone asks for them"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read the seven purposes that make a data asset critical.",
     "link": "dam.html#DAM-R11"
    },
    {
     "id": "a2",
     "type": "Do",
     "text": "For one asset, write one sentence each: the decision it informs, who makes it, and what goes wrong if the data is wrong."
    },
    {
     "id": "a3",
     "type": "Do",
     "text": "Fill in the purpose and legitimacy checks from the AI-ready supplement: the task, whether outputs affect individuals, and out-of-scope uses.",
     "link": "sectors.html#SUP-AI"
    },
    {
     "id": "a4",
     "type": "Do",
     "text": "Log the decision about which AI uses are allowed in your decision log.",
     "link": "governance.html#T-GOV-3"
    },
    {
     "id": "a5",
     "type": "Reflect",
     "text": "Who outside your team, including the people the data describes, should help frame the question?"
    }
   ],
   "check": [
    {
     "q": "What does the AI-ready supplement ask you to state before AI use begins?",
     "options": [
      "The model's vendor",
      "The task, whether outputs affect individuals and which uses are out of scope",
      "The size of the training set"
     ],
     "answer": 1,
     "why": "Its first governance check is to record the AI task, whether outputs affect individuals and which uses are out of scope, such as automated decisions."
    },
    {
     "q": "Which of these is one of the seven purposes?",
     "options": [
      "Official statistics",
      "Advertising",
      "Staff appraisal"
     ],
     "answer": 0,
     "why": "Official statistics is one of the seven purposes in the policy."
    }
   ]
  },
  {
   "id": "M15",
   "title": "Connecting data to AI with linked data, knowledge graphs and MCP",
   "level": "Advanced",
   "minutes": 35,
   "icon": "network",
   "caps": [
    "cat"
   ],
   "pathway": "ai-ready",
   "outcomes": [
    "Explain the RDF triple and why linked data helps machines read metadata",
    "Find and reuse this portal's knowledge graph and vocabulary files",
    "Describe how an MCP server lets an AI assistant check metadata against the xGov MEM"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read the W3C RDF 1.1 Primer, sections on triples and vocabularies.",
     "link": "https://www.w3.org/TR/rdf11-primer/"
    },
    {
     "id": "a2",
     "type": "Do",
     "text": "Open this portal's knowledge graph, then download the same vocabulary as Turtle from the open data page.",
     "link": "knowledge.html#graph-tab"
    },
    {
     "id": "a3",
     "type": "Read",
     "text": "Read how an assistant reads a catalogue through an open protocol, and this portal's own reference MCP server.",
     "link": "reuse.html#mcp"
    },
    {
     "id": "a4",
     "type": "Read",
     "text": "Read what the NDL PubSec MCP server does: search data.gov.uk, describe a data set and validate a record against the xGov MEM. It is an alpha prototype.",
     "link": "https://cyberdudeuk.github.io/ndl-pubsec-mcp/"
    },
    {
     "id": "a5",
     "type": "Read",
     "text": "Browse the knowledge graph and thesaurus of the proposed DCAT-AP-UK profile.",
     "link": "https://cyberdudeuk.github.io/dcat-ap-uk/knowledge.html"
    },
    {
     "id": "a6",
     "type": "Reflect",
     "text": "Which of your catalogue's fields would an assistant need to answer 'can I use this for training?' without guessing?"
    }
   ],
   "check": [
    {
     "q": "What are the three parts of an RDF triple?",
     "options": [
      "Subject, predicate and object",
      "Table, row and column",
      "Key, value and type"
     ],
     "answer": 0,
     "why": "The RDF 1.1 Primer describes every statement as a triple of subject, predicate and object."
    },
    {
     "q": "What does the NDL PubSec MCP tool metadata_validate do?",
     "options": [
      "Publishes a record to data.gov.uk",
      "Checks a metadata record against the xGov MEM and lists errors and warnings",
      "Trains a model on catalogue records"
     ],
     "answer": 1,
     "why": "Its README says it checks any metadata record against xGov MEM and lists errors and warnings with their paths. All its tools are read-only."
    }
   ]
  },
  {
   "id": "M16",
   "title": "Making public data AI-ready together",
   "level": "Practitioner",
   "minutes": 25,
   "icon": "users",
   "caps": [
    "gov",
    "dq"
   ],
   "pathway": "ai-ready",
   "outcomes": [
    "Look for existing work before building, across public sector code and catalogues",
    "Involve the people the data describes when you judge whether it is fit for AI",
    "Use the shared assurance and community routes rather than working alone"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Do",
     "text": "Search the GitHub Repos Asset Catalogue for public code that already uses your catalogue platform or metadata standard.",
     "link": "https://cyberdudeuk.github.io/github-repos-asset-catalogue/"
    },
    {
     "id": "a2",
     "type": "Do",
     "text": "Run the inclusion questions against one asset you might use for AI.",
     "link": "inclusion.html#questions"
    },
    {
     "id": "a3",
     "type": "Read",
     "text": "Read how the Data Quality Commons assures collections for the National Data Library.",
     "link": "https://cyberdudeuk.github.io/dq-commons/ndl-assurance.html"
    },
    {
     "id": "a4",
     "type": "Do",
     "text": "Pick one way to take part, from testing a page to joining a community.",
     "link": "involve.html#ways"
    },
    {
     "id": "a5",
     "type": "Reflect",
     "text": "Whose consent, trust or voice would change your answer to 'is this asset AI-ready'?"
    }
   ],
   "check": [
    {
     "q": "What does the GitHub Repos Asset Catalogue ask you to do first?",
     "options": [
      "Build a new tool",
      "Look for work that already exists before you build",
      "Buy a catalogue product"
     ],
     "answer": 1,
     "why": "Its motto is 'Before you build it, look for it': find public sector code that already exists and decide whether you can reuse it."
    },
    {
     "q": "Where should harvested catalogue records from government end up?",
     "options": [
      "On each department's intranet only",
      "The National Data Library gateway at data.gov.uk",
      "In a supplier's private catalogue"
     ],
     "answer": 1,
     "why": "data.gov.uk is the cross-government gateway to public data and the destination for harvested catalogue records."
    }
   ]
  },
  {
   "id": "M17",
   "title": "Governing AI use of critical data in practice",
   "level": "Advanced",
   "minutes": 30,
   "icon": "scale",
   "caps": [
    "gov",
    "dq"
   ],
   "pathway": "ai-ready",
   "outcomes": [
    "Run the AI-ready quality rules on a sample file",
    "Apply the transparency and ethics duties that go with AI use",
    "Plan who monitors drift and bias once AI use begins"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Do",
     "text": "Run the AI-ready rules (AI-01 to AI-04) on a synthetic sample in the Data Quality Commons checker. Nothing is uploaded.",
     "link": "https://cyberdudeuk.github.io/dq-commons/check.html"
    },
    {
     "id": "a2",
     "type": "Read",
     "text": "Read the operating model checks in the AI-ready supplement: drift, re-approval and reconstruction.",
     "link": "sectors.html#t-rules-SUP-AI"
    },
    {
     "id": "a3",
     "type": "Read",
     "text": "Read the Algorithmic Transparency Recording Standard hub and the Data and AI Ethics Framework.",
     "link": "https://www.gov.uk/government/collections/algorithmic-transparency-recording-standard-hub"
    },
    {
     "id": "a4",
     "type": "Read",
     "text": "Use the AI capability governance toolkit for the controls, assurance and human oversight around AI-assisted work.",
     "link": "https://cyberdudeuk.github.io/ai-capability-governance/"
    },
    {
     "id": "a5",
     "type": "Read",
     "text": "Read how AI for data quality can be used safely in the Data Quality Commons.",
     "link": "https://cyberdudeuk.github.io/dq-commons/ai.html"
    },
    {
     "id": "a6",
     "type": "Reflect",
     "text": "If a model trained on your asset started giving worse answers for one group, how would you find out, and who would act?"
    }
   ],
   "check": [
    {
     "q": "Why does rule AI-03 check that each record appears once?",
     "options": [
      "To save storage",
      "So training and test sets do not overlap",
      "Because duplicates are illegal"
     ],
     "answer": 1,
     "why": "AI-03 is a uniqueness rule: each record appears once, so training and test sets do not overlap."
    },
    {
     "q": "Which operating model check does the AI-ready supplement include?",
     "options": [
      "Someone owns quality, drift and bias monitoring",
      "The model is retrained weekly",
      "The data is deleted after training"
     ],
     "answer": 0,
     "why": "Its operating model checks include that someone owns quality, drift and bias monitoring, and that training sets can be reconstructed exactly."
    }
   ]
  },
  {
   "id": "M18",
   "title": "Leading data asset management - your first year",
   "level": "Foundation",
   "minutes": 25,
   "icon": "compass",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "outcomes": [
    "Set Must, Should and Could aims for your organisation and the outcomes each brings",
    "Plan the first 30, 60 and 90 days and the 6 and 12 month checkpoints",
    "Choose the maturity model that fits each aim and measure progress against a baseline"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read who the leader route is for and the six things to know first.",
     "link": "leading.html#who"
    },
    {
     "id": "a2",
     "type": "Do",
     "text": "Take a first maturity baseline with the self-assessment.",
     "link": "capability-model.html#cm-self"
    },
    {
     "id": "a3",
     "type": "Do",
     "text": "Fill in the aims and outcomes tabs of the first year capability plan.",
     "link": "leading.html#T-LDR-1"
    },
    {
     "id": "a4",
     "type": "Reflect",
     "text": "Which strand would you most need to move by the six-month checkpoint, and what would stop it?"
    }
   ],
   "check": [
    {
     "q": "Which aim is a Must for every organisation in scope?",
     "options": [
      "Every critical asset is identified, owned, catalogued, has a quality plan and is reported",
      "Every data asset in the organisation is quality-managed",
      "Critical assets are ready for AI"
     ],
     "answer": 0,
     "why": "The DAM Policy asks this of critical data assets. Covering every asset is a later aim, and AI readiness is a Could."
    },
    {
     "q": "Around which maturity level does the DAM Policy minimum for critical assets sit?",
     "options": [
      "Beginning",
      "Learning",
      "Mastering"
     ],
     "answer": 1,
     "why": "The crosswalk places the policy minimum around Learning: processes defined and repeatable for critical assets."
    }
   ]
  },
  {
   "id": "M19",
   "title": "Buying tools for data asset management without lock-in",
   "level": "Practitioner",
   "minutes": 30,
   "icon": "plug",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "outcomes": [
    "Pick the requirements that fit the kinds of tool you need, with priorities",
    "Run a request for information and a proof of concept with your own data",
    "Ask for contract clauses that keep your data movable"
   ],
   "activities": [
    {
     "id": "a1",
     "type": "Read",
     "text": "Read the ready-made requirements and the not-advice notice.",
     "link": "tooling.html#buy"
    },
    {
     "id": "a2",
     "type": "Do",
     "text": "Download the pre-filled requirements schedule and remove what you do not need.",
     "link": "tooling.html#buy"
    },
    {
     "id": "a3",
     "type": "Do",
     "text": "Plan a proof of concept that includes a full export and re-import.",
     "link": "capabilities.html#TOOL-3"
    },
    {
     "id": "a4",
     "type": "Reflect",
     "text": "If your current tool's contract ended next month, could you take everything with you?"
    }
   ],
   "check": [
    {
     "q": "How should a Must requirement be treated when scoring responses?",
     "options": [
      "Pass or fail",
      "Scored 0 to 4 like the rest",
      "Ignored if the price is low"
     ],
     "answer": 0,
     "why": "A response that does not meet a Must fails, however it scores elsewhere."
    },
    {
     "q": "What is the best evidence that a tool will let you leave?",
     "options": [
      "A full export and re-import in the proof of concept",
      "A list of connectors",
      "The supplier's statement that it supports open standards"
     ],
     "answer": 0,
     "why": "A round trip with your own data shows what is lost; a list or a statement does not."
    }
   ]
  }
 ],
 "pathways": [
  {
   "id": "ai-ready",
   "title": "AI-ready data stewardship",
   "icon": "brain",
   "summary": "Six modules for owners, stewards and catalogue managers who are asked whether a critical data asset can be used for AI. They build from what AI-ready means, through metadata and linked data, to governing AI use, and join this portal to five sister projects so you do not have to find them yourself.",
   "modules": [
    "M12",
    "M13",
    "M14",
    "M15",
    "M16",
    "M17"
   ],
   "checked": "2026-11-14",
   "alignment": {
    "course": "Data Stewardship at a Time of AI, a deep-dive series",
    "by": "Data Stewards Academy (The Data Tank and The GovLab)",
    "url": "https://datastewards.net/offerings/data-stewardship-at-a-time-of-ai-deep-dive-series",
    "when": "Five weekly live sessions of 90 minutes, Wednesdays 10 March to 7 April 2027, as published on 14 November 2026",
    "note": "An independent course, not connected with this portal. The rows below show where this pathway prepares you for, or follows up, each session. Check dates and details on the course page.",
    "rows": [
     {
      "theme": "What does 'AI-ready' actually mean?",
      "modules": [
       "M12"
      ],
      "cover": "Strong",
      "note": "Grounded in the GDS guidelines and the AI-ready supplement."
     },
     {
      "theme": "From FAIR to AI-ready",
      "modules": [
       "M13",
       "M14"
      ],
      "cover": "Partial",
      "note": "FAIR and metadata are covered well. Demand-led problem definition is only started in M14."
     },
     {
      "theme": "Connecting data to AI: MCP and knowledge graphs",
      "modules": [
       "M15"
      ],
      "cover": "Strong",
      "note": "Uses working tools: this portal's graph and MCP server, NDL PubSec MCP and DCAT-AP-UK."
     },
     {
      "theme": "Making public data AI-ready",
      "modules": [
       "M16"
      ],
      "cover": "Partial",
      "note": "Discoverability and assurance are covered. Participatory and community-led stewardship is a gap."
     },
     {
      "theme": "AI-ready data in action",
      "modules": [
       "M17"
      ],
      "cover": "Strong",
      "note": "Runnable rules, transparency duties and the AI governance toolkit."
     }
    ]
   },
   "gaps": [
    {
     "id": "PG-01",
     "title": "Participatory and community-led stewardship",
     "status": "Open",
     "text": "No project in this estate yet gives guidance on data cooperatives, community charters or involving the public in decisions about AI use of their data. M16 points to the inclusion questions only."
    },
    {
     "id": "PG-02",
     "title": "Questions-led demand for data",
     "status": "Started",
     "text": "M14 asks you to write down the question an AI use serves. There is no method yet for gathering and prioritising questions from users and the public."
    },
    {
     "id": "PG-03",
     "title": "International comparison",
     "status": "Open",
     "text": "The pathway is UK-focused. It does not yet compare how other governments prepare public data for AI."
    }
   ],
   "against": {
    "case": "Another learning route spreads people thin. Stewards could go straight to the GDS guidelines and an external course, and a pathway that links to five prototypes inherits their churn and their unendorsed status.",
    "answer": "The pathway adds no new guidance of its own. It reuses the GDS guidelines, the existing AI-ready supplement and sister projects, labels each one's status, and keeps the checks of understanding to facts you can trace. If a sister project moves or closes, the weekly health run reports the broken link."
   },
   "resources": [
    {
     "name": "Making government datasets ready for AI",
     "by": "GDS",
     "url": "https://www.gov.uk/government/publications/making-government-datasets-ready-for-ai",
     "status": "Published guidance"
    },
    {
     "name": "UK Cross-Government Metadata Exchange Model (xGov MEM)",
     "by": "Data Standards Authority",
     "url": "https://co-cddo.github.io/ukgov-metadata-exchange-model/",
     "status": "Endorsed for implementation"
    },
    {
     "name": "DCAT Application Profile for the UK (DCAT-AP-UK)",
     "by": "Sister project",
     "url": "https://cyberdudeuk.github.io/dcat-ap-uk/",
     "status": "Proposed, not endorsed"
    },
    {
     "name": "NDL PubSec MCP",
     "by": "Sister project",
     "url": "https://cyberdudeuk.github.io/ndl-pubsec-mcp/",
     "status": "Alpha prototype"
    },
    {
     "name": "Public Sector Data Quality Commons",
     "by": "Community project",
     "url": "https://cyberdudeuk.github.io/dq-commons/",
     "status": "Community project"
    },
    {
     "name": "GitHub Repos Asset Catalogue",
     "by": "Sister project",
     "url": "https://cyberdudeuk.github.io/github-repos-asset-catalogue/",
     "status": "Working tool"
    },
    {
     "name": "AI Capability Governance and Implementation",
     "by": "Sister project",
     "url": "https://cyberdudeuk.github.io/ai-capability-governance/",
     "status": "Prototype"
    },
    {
     "name": "The Knowledge Web",
     "by": "Sister project",
     "url": "https://github.com/cyberdudeuk/knowledge-web",
     "status": "Prototype"
    },
    {
     "name": "The FAIR Guiding Principles",
     "by": "Wilkinson and others, Scientific Data, 2016",
     "url": "https://doi.org/10.1038/sdata.2016.18",
     "status": "Peer-reviewed paper"
    },
    {
     "name": "Model Context Protocol specification",
     "by": "Model Context Protocol project",
     "url": "https://modelcontextprotocol.io/specification/latest",
     "status": "Open specification"
    }
   ]
  }
 ],
 "inclusion": {
  "duties": [
   {
    "name": "Public sector equality duty (Equality Act 2010)",
    "text": "Have due regard to eliminating discrimination, advancing equality of opportunity and fostering good relations, across the protected characteristics.",
    "prov": "K"
   },
   {
    "name": "Public Sector Bodies Accessibility Regulations 2018",
    "text": "Websites and documents you publish, including data quality statements and catalogue pages, must meet accessibility requirements.",
    "prov": "K"
   },
   {
    "name": "UK GDPR accuracy principle",
    "text": "Personal data must be accurate and, where necessary, kept up to date. Inaccuracy can fall harder on some groups.",
    "prov": "P"
   },
   {
    "name": "Welsh Language Standards and devolved duties",
    "text": "Where your organisation is subject to them, statements and records meant for the public must meet them.",
    "prov": "K"
   }
  ],
  "checks": [
   {
    "cap": "gov",
    "items": [
     "Include equality considerations in the charter and the board's terms of reference",
     "Make sure owners and stewards have accessible training and materials",
     "Record decisions that affect groups differently, with the equality analysis behind them",
     "Invite representatives of people the data describes when the board sets priorities"
    ]
   },
   {
    "cap": "cat",
    "items": [
     "Write titles and descriptions in plain English and expand acronyms",
     "Record known gaps in coverage - people, places or periods the data misses",
     "Check address, name and identifier fields work for all four UK nations and overseas",
     "Make sure catalogue pages and records meet accessibility requirements"
    ]
   },
   {
    "cap": "dq",
    "items": [
     "Break quality results down by group where you lawfully can",
     "Record poorer quality for a group as its own issue, so it is not averaged away",
     "Fix forms that force wrong answers, such as no 'prefer not to say' or one-line names",
     "Test quality statements with people outside the data team, and offer accessible formats"
    ]
   }
  ],
  "questions": [
   "Does the data cover everyone it should? Compare its coverage with an independent count by group and place.",
   "Is missing or wrong data worse for some groups?",
   "Can people describe themselves accurately in the forms and systems that create the data?",
   "Do rules and records work for all four UK nations, and for Welsh language users where required?",
   "Are the outputs (records, statements, reports) accessible and in plain English?",
   "Have people the data describes, or their representatives, had a say?",
   "If the data feeds automated decisions or AI, has bias been assessed?"
  ],
  "portal": [
   "Plain English, short sections, sentence case and a summary at the top of every page",
   "Works with a keyboard, screen readers and magnification; tested automatically against WCAG 2.2 AA",
   "Light and dark modes, larger text and wider line spacing, chosen in display options",
   "No information conveyed by colour alone; every chart and graph has a table equivalent",
   "Pages still work with scripts turned off; progress tracking is an optional extra",
   "Progress is kept only in your own browser; nothing about you is collected"
  ]
 },
 "domain_depth": [
  {
   "id": "DD-01",
   "theme": "Health and care data",
   "sectors": [
    "NHS England and health bodies",
    "Department of Health and Social Care ALBs"
   ],
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "moscow": "Must",
   "why": "Health bodies hold many critical data assets about people, often with legal duties beyond the DAM Policy. Quality failures here fall hardest on people who already face health inequalities.",
   "needed": [
    "Map data owner and steward roles to Caldicott guardians, SIROs and clinical safety officers",
    "Quality rules for clinical coding (SNOMED CT, ICD-10, OPCS-4) and NHS number validity",
    "Read-across to the NHS Data Security and Protection Toolkit and the national data opt-out",
    "A worked example of a DQAP for a patient-level data set"
   ],
   "leads": [
    "NHS Data Quality Maturity Index",
    "NHS Data Dictionary",
    "Data Security and Protection Toolkit",
    "DCB0129 and DCB0160 clinical safety standards",
    "Caldicott principles"
   ]
  },
  {
   "id": "DD-02",
   "theme": "Adult and children's social care data",
   "sectors": [
    "Local authorities (voluntary adoption)",
    "Department of Health and Social Care",
    "Department for Education"
   ],
   "caps": [
    "cat",
    "dq"
   ],
   "moscow": "Should",
   "why": "Social care data flows from councils to central government, so critical data assets depend on systems outside the policy's scope, often legacy case management systems.",
   "needed": [
    "Guidance for assets acquired from councils that are not bound by the policy",
    "Quality rules for client level data returns and outcomes frameworks",
    "Handling legacy system exports and cross-boundary records"
   ],
   "leads": [
    "Adult social care client level data",
    "Adult Social Care Outcomes Framework",
    "Children in need census",
    "Children looked after return"
   ]
  },
  {
   "id": "DD-03",
   "theme": "Geospatial and address data",
   "sectors": [
    "Geospatial Commission",
    "Ordnance Survey",
    "HM Land Registry",
    "environment bodies"
   ],
   "caps": [
    "cat",
    "dq"
   ],
   "moscow": "Must",
   "why": "The metadata guidance names GEMINI for geospatial data, and most critical data assets carry an address or location that needs a shared identifier.",
   "needed": [
    "GEMINI metadata alongside the core properties, with a crosswalk",
    "Rules for UPRN and USRN validity and match rates",
    "Positional and thematic accuracy checks (ISO 19157)",
    "Q-FAIR quality ratings in catalogue records"
   ],
   "leads": [
    "UK GEMINI metadata standard",
    "UPRN and USRN open identifiers",
    "ISO 19157 geographic data quality",
    "Geospatial Commission Q-FAIR"
   ]
  },
  {
   "id": "DD-04",
   "theme": "Official statistics and administrative data",
   "sectors": [
    "Office for National Statistics",
    "departmental statistics teams",
    "Office for Statistics Regulation"
   ],
   "caps": [
    "dq",
    "cat"
   ],
   "moscow": "Should",
   "why": "Official statistics is one of the seven purposes. The data used to produce statistics is designated, and its quality is also judged under the Code of Practice for Statistics.",
   "needed": [
    "Read-across between the DQAP and quality assurance of administrative data (QAAD)",
    "Statistical metadata (SDMX) alongside DCAT",
    "How to report quality once for both the DAM return and statistical quality reports"
   ],
   "leads": [
    "Code of Practice for Statistics",
    "Quality assurance of administrative data (QAAD)",
    "SDMX"
   ]
  },
  {
   "id": "DD-05",
   "theme": "Data sharing and legal gateways",
   "sectors": [
    "All departments"
   ],
   "caps": [
    "gov"
   ],
   "moscow": "Must",
   "why": "Critical data assets are defined by being shared. Owners need to know the legal basis for each flow, which changed with the Data (Use and Access) Act 2025.",
   "needed": [
    "A legal gateway field and decision record in the governance templates",
    "Read-across to data sharing agreements and the ICO data sharing code",
    "What the Data (Use and Access) Act 2025 changes for owners"
   ],
   "leads": [
    "Data (Use and Access) Act 2025",
    "Digital Economy Act 2017 data sharing powers",
    "ICO data sharing code of practice"
   ]
  },
  {
   "id": "DD-06",
   "theme": "AI-ready data",
   "sectors": [
    "All departments using data for AI or automated decision support"
   ],
   "caps": [
    "dq",
    "gov",
    "cat"
   ],
   "moscow": "Must",
   "why": "The annual review asks whether new uses include AI. Owners need criteria, not just a prompt.",
   "needed": [
    "An AI-readiness checklist mapped to quality dimensions and catalogue fields",
    "When an algorithmic transparency record is needed",
    "Bias and representativeness rules for training data"
   ],
   "leads": [
    "GDS guidelines on making government datasets ready for AI",
    "Algorithmic Transparency Recording Standard",
    "ISO/IEC 5259 data quality for analytics and machine learning"
   ]
  },
  {
   "id": "DD-07",
   "theme": "Tax, benefits and fraud and error",
   "sectors": [
    "HMRC",
    "DWP",
    "Public Sector Fraud Authority"
   ],
   "caps": [
    "gov",
    "dq"
   ],
   "moscow": "Should",
   "why": "Fraud and error is one of the seven purposes. These assets combine high volume, personal data and decisions about people.",
   "needed": [
    "Quality rules for identity matching and false positives",
    "Governance for data used in fraud detection, including review of automated flags"
   ],
   "leads": [
    "Public Sector Fraud Authority guidance",
    "Digital Economy Act 2017 fraud powers"
   ]
  },
  {
   "id": "DD-08",
   "theme": "Justice, policing and national security",
   "sectors": [
    "Ministry of Justice",
    "Home Office",
    "police",
    "defence"
   ],
   "caps": [
    "gov",
    "cat"
   ],
   "moscow": "Could",
   "why": "Only OFFICIAL assets are in scope, and law enforcement processing follows Part 3 of the Data Protection Act 2018. Owners need to know where the line falls.",
   "needed": [
    "How to describe an asset whose metadata is itself sensitive",
    "Handling markings in catalogue records",
    "Roles where vetting applies"
   ],
   "leads": [
    "Data Protection Act 2018 Part 3",
    "Government Security Classifications Policy"
   ]
  },
  {
   "id": "DD-09",
   "theme": "Person, identity and vulnerability data standards",
   "sectors": [
    "All departments holding data about people"
   ],
   "caps": [
    "cat",
    "dq"
   ],
   "moscow": "Should",
   "why": "Draft cross-government standards for person and vulnerability data affect how assets are described and checked.",
   "needed": [
    "Link catalogue fields and quality rules to the person data standard when it is published",
    "Inclusive rules for names, sex and gender questions and 'prefer not to say' options"
   ],
   "leads": [
    "Person data standard (alpha)",
    "Vulnerabilities data standard (alpha)",
    "ONS harmonised standards"
   ]
  },
  {
   "id": "DD-10",
   "theme": "Reference and master data",
   "sectors": [
    "All departments"
   ],
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "moscow": "Should",
   "why": "Code lists and authoritative identifiers make assets interoperable, but the policy does not yet list which to use (OR-05).",
   "needed": [
    "A register of recommended identifiers and code lists by domain",
    "Ownership patterns for shared reference data"
   ],
   "leads": [
    "Open Standards Board recommended standards",
    "GOV.UK registers and code lists"
   ]
  },
  {
   "id": "DD-11",
   "theme": "Records, retention and disposal",
   "sectors": [
    "All departments; knowledge and information management teams"
   ],
   "caps": [
    "gov"
   ],
   "moscow": "Should",
   "why": "The Frame recipe lists retention and disposal, but owners need the link between data assets and records management schedules.",
   "needed": [
    "Retention fields in the ownership register",
    "Read-across to The National Archives guidance"
   ],
   "leads": [
    "The National Archives information management guidance"
   ]
  },
  {
   "id": "DD-12",
   "theme": "Devolved governments and local government",
   "sectors": [
    "Scottish Government",
    "Welsh Government",
    "Northern Ireland Executive",
    "local authorities"
   ],
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "moscow": "Should",
   "why": "The policy does not bind them, but many critical data assets flow to or from them. Pan-UK assets need each nation's view.",
   "needed": [
    "A four-nations view of equivalent policies and standards",
    "Bilingual (Welsh) catalogue and quality statement guidance where it applies",
    "Voluntary adoption route for councils"
   ],
   "leads": [
    "Scottish Government data standards",
    "Welsh Language Standards",
    "Local Digital Declaration"
   ]
  },
  {
   "id": "DD-13",
   "theme": "Environment, agriculture and land",
   "sectors": [
    "Defra group",
    "environment agencies"
   ],
   "caps": [
    "cat",
    "dq"
   ],
   "moscow": "Could",
   "why": "Large holders of shared spatial and monitoring data, with sensor and time-series quality issues the core rules do not cover.",
   "needed": [
    "Timeliness and completeness rules for sensor and time-series data",
    "Metadata aligned with INSPIRE"
   ],
   "leads": [
    "INSPIRE metadata",
    "ISO 19157"
   ]
  },
  {
   "id": "DD-15",
   "theme": "Data architecture and models",
   "sectors": [
    "All departments; design authorities and data architects"
   ],
   "caps": [
    "cat",
    "gov"
   ],
   "moscow": "Should",
   "why": "Raised by a pilot team (Project Compass, 11 November 2026): critical data assets need their entities, relationships and authoritative sources described, and relationship diagrams linked to the catalogue and data dictionary.",
   "needed": [
    "An entity and relationship list linked to catalogue records",
    "A relationship diagram produced from the list, in an open text format"
   ],
   "leads": [
    "DAMA-DMBOK data architecture and data modelling and design knowledge areas"
   ]
  },
  {
   "id": "DD-14",
   "theme": "Education and skills",
   "sectors": [
    "Department for Education and its ALBs"
   ],
   "caps": [
    "dq"
   ],
   "moscow": "Could",
   "why": "Pupil and learner records are long-lived and linked across services.",
   "needed": [
    "Quality rules for unique pupil and learner identifiers",
    "Coverage checks across school types and nations"
   ],
   "leads": [
    "School census",
    "Learning Records Service"
   ]
  }
 ],
 "standards": [
  {
   "id": "SR03",
   "name": "Self-describing",
   "moscow": "Must",
   "status": "Met",
   "how": "Artefact meta tags, JSON-LD on every page, DCAT catalogue, SKOS vocabulary, sitemap"
  },
  {
   "id": "SR07",
   "name": "Self-testing",
   "moscow": "Must",
   "status": "Met",
   "how": "Static and browser checks on every change; each check proved to fail on a deliberate break; release blocked on failure"
  },
  {
   "id": "SR18",
   "name": "Self-degrading",
   "moscow": "Must",
   "status": "Met",
   "how": "Declared shed order in app.js; every page readable with scripts off (browser check B-07)"
  },
  {
   "id": "SR26",
   "name": "Self-updating",
   "moscow": "Must",
   "status": "Met",
   "how": "Weekly health run re-checks every source date through the GOV.UK Content API and every external link, and reports changes on the Status page"
  },
  {
   "id": "SR09",
   "name": "Self-reviewing",
   "moscow": "Must",
   "status": "Met",
   "how": "Weekly health run fails when the review date has passed and opens an issue"
  },
  {
   "id": "SR33",
   "name": "Self-reporting",
   "moscow": "Must",
   "status": "Met",
   "how": "status.json and the Status page publish health, coverage and open problems; failures open a GitHub issue"
  },
  {
   "id": "SR32",
   "name": "Self-limiting",
   "moscow": "Must",
   "status": "Met",
   "how": "Automation only reads, builds and opens issues. A person merges, tags releases and changes settings"
  },
  {
   "id": "SR23",
   "name": "Self-securing",
   "moscow": "Must",
   "status": "Partly",
   "how": "Content Security Policy, CodeQL, Dependabot alerts and secret scanning. Branch protection to be switched on by the repository owner"
  },
  {
   "id": "SR34",
   "name": "Self-costing",
   "moscow": "Must",
   "status": "Met",
   "how": "Health run measures page weight against a 1.5 MB per page envelope; CI minutes are free for public repositories"
  },
  {
   "id": "SR02",
   "name": "Self-reconciling",
   "moscow": "Should",
   "status": "Met",
   "how": "Build refuses broken references between requirements, steps, roles, modules and sources; counts are computed, never typed"
  },
  {
   "id": "SR04",
   "name": "Self-documenting",
   "moscow": "Should",
   "status": "Met",
   "how": "What's new page generated from the changelog; release notes generated by GitHub releases"
  },
  {
   "id": "SR10",
   "name": "Self-profiling",
   "moscow": "Should",
   "status": "Partly",
   "how": "Page weight measured; no measurement of where users wait, because no analytics are collected"
  },
  {
   "id": "SR31",
   "name": "Self-explaining",
   "moscow": "Should",
   "status": "Met",
   "how": "Search ranking rule and progress rules explained on the About page; every fact carries a provenance label"
  },
  {
   "id": "SR29",
   "name": "Self-calibrating",
   "moscow": "Could",
   "status": "Not yet",
   "how": "Learning time estimates are not yet compared with real completion times"
  },
  {
   "id": "OP01",
   "name": "Architecture decisions recorded",
   "moscow": "Must",
   "status": "Met",
   "how": "docs/adr"
  },
  {
   "id": "OP05",
   "name": "Protected main branch with review",
   "moscow": "Must",
   "status": "Partly",
   "how": "Pull request template and CODEOWNERS in place; the owner must switch on branch protection"
  },
  {
   "id": "OP06",
   "name": "Negative tests prove each check",
   "moscow": "Must",
   "status": "Met",
   "how": "tests/test_checks.py and browser vaccinations in CI"
  },
  {
   "id": "OP07",
   "name": "Accessibility tested automatically",
   "moscow": "Must",
   "status": "Met",
   "how": "axe-core, WCAG 2.2 AA, light and dark, six widths"
  },
  {
   "id": "OP08",
   "name": "Dependencies pinned and updated on a clock",
   "moscow": "Should",
   "status": "Met",
   "how": "Exact pins; Dependabot weekly; GitHub dependency graph provides the bill of materials"
  },
  {
   "id": "OP10",
   "name": "Continuous integration on every change",
   "moscow": "Must",
   "status": "Met",
   "how": "Build, check and publish workflow"
  },
  {
   "id": "OP11",
   "name": "Release train and checklist",
   "moscow": "Must",
   "status": "Met",
   "how": "Tag-triggered release workflow and the release checklist in docs/RUNBOOK.md"
  },
  {
   "id": "OP13",
   "name": "Scheduled health run with alert",
   "moscow": "Must",
   "status": "Met",
   "how": "Weekly health workflow; failures open or update a labelled issue"
  },
  {
   "id": "OP16",
   "name": "Runbooks",
   "moscow": "Must",
   "status": "Met",
   "how": "docs/RUNBOOK.md"
  },
  {
   "id": "OP20",
   "name": "No single person or account the portal depends on",
   "moscow": "Must",
   "status": "Not yet",
   "how": "Hosted on one personal account; move to an official organisation (OR-03)"
  },
  {
   "id": "OP21",
   "name": "Static-first delivery",
   "moscow": "Must",
   "status": "Met",
   "how": "Static pages on GitHub Pages; no server code"
  },
  {
   "id": "OP24",
   "name": "Personal data kept out",
   "moscow": "Must",
   "status": "Met",
   "how": "No analytics, no cookies; progress stays in the browser; the contact form warns against personal data"
  },
  {
   "id": "OP30",
   "name": "Algorithmic transparency",
   "moscow": "Should",
   "status": "Met",
   "how": "Not applicable: no automated decisions about people. Recorded here as the decision"
  },
  {
   "id": "OP32",
   "name": "Service Standard self-assessment",
   "moscow": "Should",
   "status": "Partly",
   "how": "Self-assessment against all 14 points on the Service design page; no service assessment yet"
  },
  {
   "id": "OP33",
   "name": "Horizon scanning",
   "moscow": "Must",
   "status": "Met",
   "how": "Weekly source checks flag changed GOV.UK guidance for review"
  }
 ],
 "rulebook": [
  {
   "id": "RB-SVC",
   "group": "Service delivery and technology",
   "title": "Service Standard",
   "publisher": "GDS (GOV.UK Service Manual)",
   "url": "https://www.gov.uk/service-manual/service-standard",
   "updated": "2019-06-07",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "The 14 points any government service is assessed against; used for this portal's self-assessment."
  },
  {
   "id": "RB-TCOP",
   "group": "Service delivery and technology",
   "title": "The Technology Code of Practice",
   "publisher": "GDS",
   "url": "https://www.gov.uk/guidance/the-technology-code-of-practice",
   "updated": "2026-10-29",
   "prov": "V",
   "caps": [
    "cat",
    "gov"
   ],
   "why": "Make things open, use open standards and make data reusable: the basis for catalogue and tool choices."
  },
  {
   "id": "RB-GDSWAY",
   "group": "Service delivery and technology",
   "title": "The GDS Way",
   "publisher": "GDS",
   "url": "https://gds-way.digital.cabinet-office.gov.uk/",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "Engineering practice this portal follows, including using GitHub and publishing a vulnerability disclosure route."
  },
  {
   "id": "RB-OPEN",
   "group": "Service delivery and technology",
   "title": "Open standards for government",
   "publisher": "GDS",
   "url": "https://www.gov.uk/government/publications/open-standards-for-government",
   "updated": "2026-01-29",
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "The recommended open standards, including those for metadata, identifiers and data exchange."
  },
  {
   "id": "RB-UPRN",
   "group": "Service delivery and technology",
   "title": "Identifying property and street information (UPRN and USRN)",
   "publisher": "GDS",
   "url": "https://www.gov.uk/government/publications/open-standards-for-government/identifying-property-and-street-information",
   "updated": "2026-01-29",
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "The open standard for property and street identifiers; the basis for address quality rules."
  },
  {
   "id": "RB-DDAT",
   "group": "Service delivery and technology",
   "title": "Government Digital and Data Profession Capability Framework",
   "publisher": "GDS",
   "url": "https://ddat-capability-framework.service.gov.uk/",
   "updated": null,
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Role and skill definitions for data governance and data roles."
  },
  {
   "id": "RB-NDL",
   "group": "Data and AI",
   "title": "National Data Library (data.gov.uk)",
   "publisher": "GDS",
   "url": "https://www.data.gov.uk/",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "The cross-government gateway to public data; the destination for harvested catalogue records."
  },
  {
   "id": "RB-ETH",
   "group": "Data and AI",
   "title": "Data and AI Ethics Framework",
   "publisher": "GDS",
   "url": "https://www.gov.uk/government/publications/data-ethics-framework",
   "updated": "2025-12-18",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Ethical questions for new or higher-risk uses of data, including AI."
  },
  {
   "id": "RB-AIREADY",
   "group": "Data and AI",
   "title": "Making government datasets ready for AI",
   "publisher": "GDS",
   "url": "https://www.gov.uk/government/publications/making-government-datasets-ready-for-ai",
   "updated": "2026-01-19",
   "prov": "V",
   "caps": [
    "dq",
    "cat",
    "gov"
   ],
   "why": "The criteria to assess at the annual review when data is used for AI."
  },
  {
   "id": "RB-AIPLAY",
   "group": "Data and AI",
   "title": "AI Playbook for the UK Government",
   "publisher": "GDS",
   "url": "https://www.gov.uk/government/publications/ai-playbook-for-the-uk-government",
   "updated": "2025-02-10",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Safe and effective use of AI in government."
  },
  {
   "id": "RB-ATRS",
   "group": "Data and AI",
   "title": "Algorithmic Transparency Recording Standard hub",
   "publisher": "GDS",
   "url": "https://www.gov.uk/government/collections/algorithmic-transparency-recording-standard-hub",
   "updated": "2025-05-08",
   "prov": "V",
   "caps": [
    "gov",
    "dq"
   ],
   "why": "Transparency records for algorithmic tools that support decisions about people."
  },
  {
   "id": "RB-DUAA",
   "group": "Legislation",
   "title": "Data (Use and Access) Act 2025",
   "publisher": "legislation.gov.uk",
   "url": "https://www.legislation.gov.uk/ukpga/2025/18/contents",
   "updated": null,
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Amends UK GDPR and the Data Protection Act 2018; affects the lawful basis for sharing."
  },
  {
   "id": "RB-DPA",
   "group": "Legislation",
   "title": "Data Protection Act 2018",
   "publisher": "legislation.gov.uk",
   "url": "https://www.legislation.gov.uk/ukpga/2018/12/contents",
   "updated": null,
   "prov": "V",
   "caps": [
    "gov",
    "dq"
   ],
   "why": "Data protection law, including Part 3 for law enforcement processing."
  },
  {
   "id": "RB-DEA",
   "group": "Legislation",
   "title": "Digital Economy Act 2017",
   "publisher": "legislation.gov.uk",
   "url": "https://www.legislation.gov.uk/ukpga/2017/30/contents",
   "updated": null,
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Data sharing powers for public authorities, including for fraud and debt."
  },
  {
   "id": "RB-EQA",
   "group": "Legislation",
   "title": "Equality Act 2010",
   "publisher": "legislation.gov.uk",
   "url": "https://www.legislation.gov.uk/ukpga/2010/15/contents",
   "updated": null,
   "prov": "V",
   "caps": [
    "gov",
    "dq"
   ],
   "why": "Includes the public sector equality duty."
  },
  {
   "id": "RB-ICOSHARE",
   "group": "Legislation",
   "title": "ICO data sharing code of practice",
   "publisher": "Information Commissioner's Office",
   "url": "https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-sharing/data-sharing-a-code-of-practice/",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov"
   ],
   "why": "Statutory code on sharing personal data between controllers (in force since October 2021, according to search results)."
  },
  {
   "id": "RB-GSC",
   "group": "Security",
   "title": "Government Security Classifications",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/publications/government-security-classifications",
   "updated": "2024-08-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "Defines OFFICIAL and handling markings; the policy covers OFFICIAL assets only."
  },
  {
   "id": "RB-VDP",
   "group": "Security",
   "title": "Report a vulnerability on a GOV.UK domain or subdomain",
   "publisher": "GDS",
   "url": "https://www.gov.uk/help/report-vulnerability",
   "updated": "2021-03-23",
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "The government vulnerability disclosure approach this portal's security.txt follows in spirit."
  },
  {
   "id": "RB-ACC",
   "group": "Accessibility and equality",
   "title": "Understanding accessibility requirements for public sector bodies",
   "publisher": "GDS",
   "url": "https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps",
   "updated": "2024-09-30",
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "The accessibility regulations that apply to published records, statements and this portal."
  },
  {
   "id": "RB-MODEL",
   "group": "Accessibility and equality",
   "title": "Model accessibility statement",
   "publisher": "GDS",
   "url": "https://www.gov.uk/guidance/model-accessibility-statement",
   "updated": "2024-09-30",
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "Mandatory wording used in this portal's accessibility statement."
  },
  {
   "id": "RB-PSED",
   "group": "Accessibility and equality",
   "title": "Public sector equality duty",
   "publisher": "GOV.UK",
   "url": "https://www.gov.uk/government/publications/public-sector-equality-duty",
   "updated": "2012-07-06",
   "prov": "V",
   "caps": [
    "gov",
    "dq"
   ],
   "why": "How public bodies have due regard to equality in their functions, including data work."
  },
  {
   "id": "RB-STYLE",
   "group": "Content",
   "title": "Writing to GOV.UK standards - style guides",
   "publisher": "GDS",
   "url": "https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/style-guides/",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "The style this portal is written in (the old GOV.UK style guide address redirects here)."
  },
  {
   "id": "RB-COP",
   "group": "Statistics",
   "title": "Code of Practice for Statistics",
   "publisher": "Office for Statistics Regulation",
   "url": "https://code.statisticsauthority.gov.uk/",
   "updated": null,
   "prov": "V",
   "caps": [
    "dq"
   ],
   "why": "Trustworthiness, quality and value for official statistics; read across to DQAPs for statistical sources."
  },
  {
   "id": "RB-QAAD",
   "group": "Statistics",
   "title": "Quality assurance of administrative data",
   "publisher": "Office for Statistics Regulation",
   "url": "https://osr.statisticsauthority.gov.uk/guidance/administrative-data-and-official-statistics/",
   "updated": null,
   "prov": "S",
   "caps": [
    "dq"
   ],
   "why": "How statistics producers assure administrative data; the site blocked automated checking."
  },
  {
   "id": "RB-TNA",
   "group": "Records",
   "title": "Information management guidance",
   "publisher": "The National Archives",
   "url": "https://www.nationalarchives.gov.uk/information-management/",
   "updated": null,
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Records management, retention and disposal for public records."
  },
  {
   "id": "RB-OGL",
   "group": "Content",
   "title": "Open Government Licence v3.0",
   "publisher": "The National Archives",
   "url": "https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "The licence for open government data and for this portal's content."
  },
  {
   "id": "RB-DSPT",
   "group": "Health and care",
   "title": "Data Security and Protection Toolkit",
   "publisher": "NHS England",
   "url": "https://www.dsptoolkit.nhs.uk/",
   "updated": null,
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Annual self-assessment against data security standards for organisations with access to NHS patient data."
  },
  {
   "id": "RB-CALD",
   "group": "Health and care",
   "title": "The Caldicott Principles",
   "publisher": "National Data Guardian",
   "url": "https://www.gov.uk/government/publications/the-caldicott-principles",
   "updated": "2020-12-08",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Principles for using confidential information about patients and service users."
  },
  {
   "id": "RB-CLD",
   "group": "Health and care",
   "title": "Adult social care client level data, England: background quality and methodology",
   "publisher": "Department of Health and Social Care",
   "url": "https://www.gov.uk/government/publications/adult-social-care-client-level-data-england-background-quality-and-methodology",
   "updated": "2026-01-15",
   "prov": "V",
   "caps": [
    "dq"
   ],
   "why": "Quality and coverage of the national adult social care client level data collection."
  },
  {
   "id": "RB-ASCOF",
   "group": "Health and care",
   "title": "Adult social care outcomes framework: handbook of definitions",
   "publisher": "Department of Health and Social Care",
   "url": "https://www.gov.uk/government/publications/adult-social-care-outcomes-framework-handbook-of-definitions",
   "updated": "2026-03-10",
   "prov": "V",
   "caps": [
    "dq"
   ],
   "why": "Definitions of measures derived from client level data."
  },
  {
   "id": "RB-CDM",
   "group": "Health and care",
   "title": "Care data matters: a roadmap for better adult social care data",
   "publisher": "Department of Health and Social Care",
   "url": "https://www.gov.uk/government/publications/care-data-matters-a-roadmap-for-better-adult-social-care-data",
   "updated": "2023-12-20",
   "prov": "V",
   "caps": [
    "gov",
    "dq"
   ],
   "why": "The roadmap for adult social care data, including client level data."
  },
  {
   "id": "RB-CIN",
   "group": "Children and education",
   "title": "Children in need census: guide to submitting data",
   "publisher": "Department for Education",
   "url": "https://www.gov.uk/guidance/children-in-need-census",
   "updated": "2026-11-03",
   "prov": "V",
   "caps": [
    "dq"
   ],
   "why": "Specification and validation for children in need data returns."
  },
  {
   "id": "RB-GEOBP",
   "group": "Geospatial",
   "title": "Best practice guidance and tools for managing geospatial data",
   "publisher": "Geospatial Commission",
   "url": "https://www.gov.uk/government/collections/best-practice-guidance-and-tools-for-geospatial-data-managers",
   "updated": "2022-05-26",
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "Guidance on managing and sharing geospatial data in a FAIR way."
  },
  {
   "id": "RB-QFAIR",
   "group": "Geospatial",
   "title": "How FAIR are the UK's national geospatial data assets?",
   "publisher": "Geospatial Commission",
   "url": "https://www.gov.uk/government/publications/how-fair-are-the-uks-geospatial-assets",
   "updated": "2022-02-09",
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "The Q-FAIR assessment of national geospatial data assets."
  },
  {
   "id": "RB-GEMINI",
   "group": "Geospatial",
   "title": "UK GEMINI metadata standard",
   "publisher": "Association for Geographic Information",
   "url": "https://www.agi.org.uk/uk-gemini/",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "Geospatial metadata standard named in the GOV.UK metadata guidance; the AGI page says it has moved to GitHub."
  },
  {
   "id": "RB-PSFA",
   "group": "Fraud and error",
   "title": "Public Sector Fraud Authority",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/organisations/public-sector-fraud-authority",
   "updated": "2025-02-06",
   "prov": "V",
   "caps": [
    "gov",
    "dq"
   ],
   "why": "Counter-fraud standards and support for the fraud and error purpose."
  },
  {
   "id": "RB-LDD",
   "group": "Local government",
   "title": "Local Digital Declaration",
   "publisher": "Local Digital",
   "url": "https://www.localdigital.gov.uk/declaration/",
   "updated": null,
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Shared commitments for councils, which can adopt the policy voluntarily."
  },
  {
   "id": "RB-SDMX",
   "group": "Standards",
   "title": "SDMX",
   "publisher": "SDMX sponsors",
   "url": "https://sdmx.org/",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "Statistical data and metadata exchange standard."
  },
  {
   "id": "RB-DCAT",
   "group": "Standards",
   "title": "Data Catalog Vocabulary (DCAT) version 3",
   "publisher": "W3C",
   "url": "https://www.w3.org/TR/vocab-dcat-3/",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "The base vocabulary for catalogue records."
  },
  {
   "id": "RB-DQV",
   "group": "Standards",
   "title": "Data on the Web Best Practices: Data Quality Vocabulary",
   "publisher": "W3C",
   "url": "https://www.w3.org/TR/vocab-dqv/",
   "updated": null,
   "prov": "V",
   "caps": [
    "dq",
    "cat"
   ],
   "why": "Publishing quality measurements with catalogue records."
  },
  {
   "id": "RB-GATE0",
   "group": "Delivery, change and investment",
   "title": "Gate Review 0: Strategic Assessment",
   "publisher": "National Infrastructure and Service Transformation Authority",
   "url": "https://www.gov.uk/government/publications/gate-review-0-strategic-assessment",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov"
   ],
   "why": "NISTA's workbook for the strategic assessment of a programme."
  },
  {
   "id": "RB-GATE5",
   "group": "Delivery, change and investment",
   "title": "Gate Review 5: Operations Review and Benefits Realisation",
   "publisher": "National Infrastructure and Service Transformation Authority",
   "url": "https://www.gov.uk/government/publications/gate-review-5-operations-review-and-benefit-realisation",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov"
   ],
   "why": "NISTA's workbook for confirming benefits are being realised and the service is running smoothly."
  },
  {
   "id": "RB-CDMP",
   "group": "Skills and professions",
   "title": "CDMP: Certified Data Management Professional",
   "publisher": "DAMA International",
   "url": "https://cdmp.info/",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "DAMA International's certification for data management professionals, based on the DAMA-DMBOK."
  },
  {
   "id": "RB-BCSDME",
   "group": "Skills and professions",
   "title": "BCS Practitioner Certificate in Data Management Essentials",
   "publisher": "BCS",
   "url": "https://www.bcs.org/qualifications-and-certifications/certifications-for-professionals/business-analysis/practitioner-certificate-in-data-management-essentials/",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "A practitioner certificate in good practice for managing an organisation's data."
  },
  {
   "id": "RB-CILIPREG",
   "group": "Skills and professions",
   "title": "CILIP professional registration",
   "publisher": "CILIP",
   "url": "https://www.cilip.org.uk/learn-develop/professional-registration/",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "Certification, chartership and knowledge management chartership for information professionals, with yearly revalidation through CPD."
  },
  {
   "id": "RB-GREEN",
   "group": "Delivery, change and investment",
   "title": "The Green Book and accompanying guidance",
   "publisher": "HM Treasury",
   "url": "https://www.gov.uk/government/collections/the-green-book-and-accompanying-guidance-and-documents",
   "updated": "2026-10-06",
   "prov": "V",
   "caps": [
    "gov",
    "dq"
   ],
   "why": "Appraisal and the five case business case model; where the cost of owning, cataloguing and improving data assets belongs in a programme business case."
  },
  {
   "id": "RB-GOVS002",
   "group": "Delivery, change and investment",
   "title": "Government Functional Standard GovS 002: Project Delivery",
   "publisher": "Government Project Delivery function",
   "url": "https://www.gov.uk/government/publications/project-delivery-functional-standard",
   "updated": "2025-09-17",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "The life cycle, governance and roles every portfolio, programme and project must follow; data deliverables and data owners fit into it."
  },
  {
   "id": "RB-GOVS005",
   "group": "Delivery, change and investment",
   "title": "Government Functional Standard GovS 005: Digital",
   "publisher": "Government Digital Service",
   "url": "https://www.gov.uk/government/publications/government-functional-standard-govs-005-digital",
   "updated": "2026-10-01",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "The digital and data functional standard that the Data Maturity Assessment and data management practice sit under."
  },
  {
   "id": "RB-IAAP",
   "group": "Delivery, change and investment",
   "title": "Implementing integrated assurance for major projects",
   "publisher": "National Infrastructure and Service Transformation Authority",
   "url": "https://www.gov.uk/government/publications/implementing-integrated-assurance-for-major-projects",
   "updated": "2026-08-20",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "How major projects plan assurance; DAM checks can be written into the integrated assurance and approval plan."
  },
  {
   "id": "RB-NISTA",
   "group": "Delivery, change and investment",
   "title": "National Infrastructure and Service Transformation Authority",
   "publisher": "HM Treasury and Cabinet Office",
   "url": "https://www.gov.uk/government/organisations/national-infrastructure-and-service-transformation-authority",
   "updated": "2026-08-20",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "The centre of expertise for major projects and service transformation, including the Government Major Projects Portfolio."
  },
  {
   "id": "RB-GMPP",
   "group": "Delivery, change and investment",
   "title": "Government Major Projects Portfolio",
   "publisher": "National Infrastructure and Service Transformation Authority",
   "url": "https://www.gov.uk/government/publications/government-major-projects-portfolio",
   "updated": "2026-03-31",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "The largest and riskiest projects; many create or replace critical data assets."
  },
  {
   "id": "RB-SPEND",
   "group": "Delivery, change and investment",
   "title": "Set up a commercial or digital and technology spend controls pipeline",
   "publisher": "Government Digital Service",
   "url": "https://www.gov.uk/guidance/set-up-a-commercial-or-digital-and-technology-spend-controls-pipeline",
   "updated": "2025-02-18",
   "prov": "V",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "Spend control is the point at which central teams see new digital and technology spend, and so a natural checkpoint for DAM evidence."
  },
  {
   "id": "RB-FHIRUK",
   "group": "Health and care",
   "title": "HL7 FHIR UK Core",
   "publisher": "NHS England (NHS Standards Directory)",
   "url": "https://data.standards.nhs.uk/published-standards/hl7-fhir-uk-core",
   "updated": null,
   "prov": "S",
   "caps": [
    "cat"
   ],
   "why": "API standards that use FHIR Release 4 to exchange health and care data consistently across England, Scotland, Wales and Northern Ireland. UK Core uses SNOMED CT, dm+d and the NHS Data Model and Dictionary for terminology."
  },
  {
   "id": "RB-SNOMED",
   "group": "Health and care",
   "title": "SNOMED CT",
   "publisher": "NHS England (NHS Standards Directory)",
   "url": "https://data.standards.nhs.uk/current-standards/snomed-ct",
   "updated": null,
   "prov": "S",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "The information standard for clinical terminology (SCCI0034). Record it in conformsTo when an asset holds coded clinical data."
  },
  {
   "id": "RB-DCB0129",
   "group": "Health and care",
   "title": "DCB0129: Clinical risk management in the manufacture of health IT systems",
   "publisher": "NHS England (NHS Standards Directory)",
   "url": "https://data.standards.nhs.uk/current-standards/nhsd-clinical-risk-management-its-application-in-the-manufacture-of-health-it-systems",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov"
   ],
   "why": "Clinical risk management that suppliers of health IT must follow, including a clinical safety officer. Under national review with DCB0160."
  },
  {
   "id": "RB-DCB0160",
   "group": "Health and care",
   "title": "DCB0160: Clinical risk management in the deployment and use of health IT systems",
   "publisher": "NHS England (NHS Standards Directory)",
   "url": "https://standards.nhs.uk/published-standards/clinical-risk-management-its-application-in-the-deployment-and-use-of-health-it-systems",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov"
   ],
   "why": "Clinical risk management that health and care organisations must follow when they deploy and use health IT. A national review consulted until 11 September 2026."
  },
  {
   "id": "RB-TNARET",
   "group": "Records and information management",
   "title": "Advice on retention",
   "publisher": "The National Archives",
   "url": "https://www.nationalarchives.gov.uk/information-management/manage-information/policy-process/disposal/advice-on-retention/",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov"
   ],
   "why": "Sets out short (up to two years), medium (up to eight years) and long retention categories, and says the model retention schedules are no longer maintained. Each organisation sets its own schedule."
  },
  {
   "id": "RB-DCATGOV",
   "group": "Standards",
   "title": "Using metadata to describe data assets in a data catalogue",
   "publisher": "GOV.UK (recommended open standards)",
   "url": "https://www.gov.uk/government/publications/recommended-open-standards-for-government/using-metadata-to-describe-data-assets-in-a-data-catalogue",
   "updated": "2023-09-28",
   "prov": "S",
   "caps": [
    "cat"
   ],
   "why": "Recommends DCAT version 3 for describing data sets and data services in a catalogue, in support of the UK Cross-Government Metadata Exchange Model."
  },
  {
   "id": "RB-DEAREG",
   "group": "Legislation",
   "title": "Register of information sharing agreements under the Digital Economy Act 2017",
   "publisher": "GOV.UK (data.gov.uk)",
   "url": "https://www.digital-economy-act-register.data.gov.uk/",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "The public register of agreements made under the public service delivery, debt, fraud and civil registration powers in Part 5 of the Act."
  },
  {
   "id": "RB-ICODSA",
   "group": "Data protection",
   "title": "Data sharing: a code of practice - data sharing agreements",
   "publisher": "Information Commissioner's Office",
   "url": "https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-sharing/data-sharing-a-code-of-practice/data-sharing-agreements/",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov"
   ],
   "why": "Says a data sharing agreement is good practice and lists what it should cover, including the parties, purpose, lawful basis, data items, formats, rights, retention, ending the sharing and review."
  },
  {
   "id": "RB-S251",
   "group": "Health and care",
   "title": "Confidential patient information and section 251",
   "publisher": "Health Research Authority",
   "url": "https://www.hra.nhs.uk/about-us/committees-and-services/confidentiality-advisory-group/confidential-patient-information-and-regulations/",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov"
   ],
   "why": "Section 251 of the NHS Act 2006 and the Health Service (Control of Patient Information) Regulations 2002 let the common law duty of confidentiality be set aside for medical purposes, with Confidentiality Advisory Group support. Data protection law still applies."
  },
  {
   "id": "RB-UKMDR",
   "group": "Health and care",
   "title": "The Medical Devices Regulations 2002",
   "publisher": "legislation.gov.uk",
   "url": "https://www.legislation.gov.uk/uksi/2002/618/contents/made",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov"
   ],
   "why": "Govern medical devices in Great Britain, including software and AI used for a medical purpose. The MHRA is reforming them."
  },
  {
   "id": "RB-MHRASW",
   "group": "Health and care",
   "title": "Medical devices: software applications (apps)",
   "publisher": "Medicines and Healthcare products Regulatory Agency",
   "url": "https://www.gov.uk/government/publications/medical-devices-software-applications-apps",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov"
   ],
   "why": "Helps decide whether software, including an app or AI, is a medical device. A product is a medical device only if its manufacturer intends a medical purpose."
  },
  {
   "id": "RB-DSL",
   "group": "Health and care",
   "title": "Data saves lives: reshaping health and social care with data",
   "publisher": "Department of Health and Social Care",
   "url": "https://www.gov.uk/government/publications/data-saves-lives-reshaping-health-and-social-care-with-data",
   "updated": "2022-06-15",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "DHSC's data strategy for health and social care in England, which commits to secure data environments as the default way to access NHS data for research and analysis."
  },
  {
   "id": "RB-SDE",
   "group": "Health and care",
   "title": "Secure data environment for NHS health and social care data - policy guidelines",
   "publisher": "Department of Health and Social Care",
   "url": "https://www.gov.uk/government/publications/secure-data-environment-policy-guidelines",
   "updated": "2022-12-23",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Twelve guidelines that organisations hosting NHS health and social care data for research and analysis must adopt."
  },
  {
   "id": "RB-DAPU",
   "group": "Health and care",
   "title": "Data access policy update",
   "publisher": "Department of Health and Social Care",
   "url": "https://www.gov.uk/government/publications/data-access-policy-update",
   "updated": null,
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Builds on the secure data environment guidelines with the policy decisions made so far on 'data access as default' for secondary uses of NHS data."
  },
  {
   "id": "RB-SVCASSESS",
   "group": "Delivery, change and investment",
   "title": "Service assessments and applying the Service Standard",
   "publisher": "GDS (GOV.UK Service Manual)",
   "url": "https://www.gov.uk/service-manual/service-assessments",
   "updated": "2025-03-10",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Alpha, beta and live assessments; teams can show their critical data assets are catalogued, owned and quality-planned."
  },
  {
   "id": "RB-RETIRE",
   "group": "Delivery, change and investment",
   "title": "Retiring your service",
   "publisher": "GDS (GOV.UK Service Manual)",
   "url": "https://www.gov.uk/service-manual/agile-delivery/retiring-your-service",
   "updated": "2025-08-26",
   "prov": "V",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "What to do with users and their data when a service closes, including passing data to a new owner."
  },
  {
   "id": "RB-LEGACY",
   "group": "Delivery, change and investment",
   "title": "Managing legacy technology",
   "publisher": "Government Digital Service",
   "url": "https://www.gov.uk/guidance/managing-legacy-technology",
   "updated": "2026-10-15",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Its second principle asks organisations to build a complete and accurate register of their data assets before migrating."
  },
  {
   "id": "RB-TECHDEBT",
   "group": "Delivery, change and investment",
   "title": "Prevent technical debt and legacy",
   "publisher": "Government Digital Service",
   "url": "https://www.gov.uk/guidance/prevent-technical-debt-and-legacy",
   "updated": "2024-10-23",
   "prov": "V",
   "caps": [
    "gov",
    "dq"
   ],
   "why": "Stops new systems becoming the next concentration of hard-to-use data."
  },
  {
   "id": "RB-ORANGE",
   "group": "Delivery, change and investment",
   "title": "The Orange Book: management of risk",
   "publisher": "HM Treasury",
   "url": "https://www.gov.uk/government/publications/orange-book",
   "updated": "2026-07-29",
   "prov": "V",
   "caps": [
    "gov",
    "dq"
   ],
   "why": "Principles for managing risk; data asset risks belong on the same registers as other risks."
  },
  {
   "id": "RB-MAGENTA",
   "group": "Delivery, change and investment",
   "title": "The Magenta Book",
   "publisher": "HM Treasury",
   "url": "https://www.gov.uk/government/publications/the-magenta-book",
   "updated": "2026-05-15",
   "prov": "V",
   "caps": [
    "gov",
    "dq"
   ],
   "why": "Evaluation in government; how to show whether DAM work delivered its intended benefits."
  },
  {
   "id": "RB-AQUA",
   "group": "Delivery, change and investment",
   "title": "The AQuA Book",
   "publisher": "HM Treasury and the Analysis Function",
   "url": "https://www.gov.uk/guidance/the-aqua-book",
   "updated": "2025-07-30",
   "prov": "V",
   "caps": [
    "dq"
   ],
   "why": "Quality assurance of analysis and models; analysis is only as reliable as the data quality plans behind it."
  },
  {
   "id": "RB-SOURCING",
   "group": "Delivery, change and investment",
   "title": "The Sourcing Playbook",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/publications/the-sourcing-and-consultancy-playbooks",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "Outsourcing decisions; contracts should say who owns the data, how metadata is delivered and how data comes back at exit."
  },
  {
   "id": "RB-DDATPB",
   "group": "Delivery, change and investment",
   "title": "The Digital, Data and Technology Playbook",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/publications/the-digital-data-and-technology-playbook",
   "updated": "2023-06-20",
   "prov": "V",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "Commercial guidance for buying digital, data and technology products and services."
  },
  {
   "id": "RB-PPN020",
   "group": "Delivery, change and investment",
   "title": "PPN 020: Guidance on data protection legislation",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/publications/ppn-020-guidance-on-data-protection-legislation",
   "updated": "2025-04-24",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Data protection terms in public contracts."
  },
  {
   "id": "RB-DSGF",
   "group": "Data and AI",
   "title": "Data Sharing Governance Framework",
   "publisher": "Central Digital and Data Office",
   "url": "https://www.gov.uk/government/publications/data-sharing-governance-framework",
   "updated": "2022-05-23",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Cross-government principles for sharing data; the DAM Policy does not force sharing but expects safe reuse."
  },
  {
   "id": "RB-BLUEPRINT",
   "group": "Delivery, change and investment",
   "title": "A blueprint for modern digital government",
   "publisher": "Department for Science, Innovation and Technology",
   "url": "https://www.gov.uk/government/publications/a-blueprint-for-modern-digital-government",
   "updated": "2025-01-21",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "The wider programme of digital reform that the DAM Policy supports."
  },
  {
   "id": "RB-NDLPUB",
   "group": "Data and AI",
   "title": "National Data Library",
   "publisher": "Department for Science, Innovation and Technology",
   "url": "https://www.gov.uk/government/publications/national-data-library",
   "updated": "2025-07-29",
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "Plans for making public sector data easier to find and use; catalogued critical assets are a natural input."
  },
  {
   "id": "RB-DMAF",
   "group": "Data and AI",
   "title": "Data Maturity Assessment for Government: Framework",
   "publisher": "Central Digital and Data Office (developed with the ONS Data Quality Hub)",
   "url": "https://www.gov.uk/government/publications/data-maturity-assessment-for-government-framework",
   "updated": "2026-07-23",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "10 topics, 6 themes and 5 levels for assessing data maturity. Licensed CC BY-NC-SA 4.0, so this portal links to it and does not copy its descriptions."
  },
  {
   "id": "RB-DMAHUB",
   "group": "Data and AI",
   "title": "Government data maturity hub",
   "publisher": "Central Digital and Data Office",
   "url": "https://www.gov.uk/government/collections/data-maturity-assessment-for-government",
   "updated": "2026-07-23",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "The framework plus guidance on delivering an assessment."
  },
  {
   "id": "RB-PROFS",
   "group": "Skills and professions",
   "title": "Government professions",
   "publisher": "Government Skills",
   "url": "https://www.gov.uk/government/publications/government-professions/government-professions",
   "updated": "2026-09-30",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "The list of functional and specialist professions every civil servant can join."
  },
  {
   "id": "RB-GSKILLS",
   "group": "Skills and professions",
   "title": "Government Skills",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/organisations/government-skills",
   "updated": "2024-07-09",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Runs the Government Campus, the recommended curriculum and the Government Skills Campus learning platform."
  },
  {
   "id": "RB-CURRIC",
   "group": "Skills and professions",
   "title": "The Civil Service recommended curriculum",
   "publisher": "Government Skills",
   "url": "https://www.gov.uk/government/collections/the-civil-service-recommended-curriculum",
   "updated": "2025-05-29",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Recommended learning for all civil servants, searchable by subject."
  },
  {
   "id": "RB-DSFA",
   "group": "Skills and professions",
   "title": "Data skills for all",
   "publisher": "Government Skills",
   "url": "https://www.gov.uk/guidance/data-skills-for-all",
   "updated": "2026-03-31",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Free data learning at awareness, working and practitioner levels."
  },
  {
   "id": "RB-SPECIALIST",
   "group": "Skills and professions",
   "title": "Specialist skills from government professions",
   "publisher": "Government Skills",
   "url": "https://www.gov.uk/guidance/specialist-skills",
   "updated": "2024-08-23",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Strand 4 of the curriculum: how professions develop specialist skills."
  },
  {
   "id": "RB-PROSPECTUS",
   "group": "Skills and professions",
   "title": "Government Campus prospectus",
   "publisher": "Government Skills",
   "url": "https://prospectus.governmentcampus.co.uk/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "The online prospectus of courses by strand and subject, including data and analytics."
  },
  {
   "id": "RB-NSG",
   "group": "Skills and professions",
   "title": "National School of Government",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/organisations/national-school-of-government",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Opened in October 2026 to train civil servants and public sector leaders, including in AI."
  },
  {
   "id": "RB-AFCAREER",
   "group": "Skills and professions",
   "title": "Analysis Function career framework",
   "publisher": "Analysis Function",
   "url": "https://analysisfunction.civilservice.gov.uk/careers/career-framework/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "dq"
   ],
   "why": "Career framework and learning pathways for the analytical professions, including statistics."
  },
  {
   "id": "RB-AFROLES",
   "group": "Skills and professions",
   "title": "Analysis Function role profiles and career pathways",
   "publisher": "Analysis Function",
   "url": "https://analysisfunction.civilservice.gov.uk/careers/role-profiles-and-career-pathways/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "dq"
   ],
   "why": "Role profiles for analysts, statisticians, economists, social researchers, operational researchers and geographers."
  },
  {
   "id": "RB-GSS",
   "group": "Skills and professions",
   "title": "Government Statistical Service and Statistician Group",
   "publisher": "Analysis Function",
   "url": "https://analysisfunction.civilservice.gov.uk/government-statistical-service-and-statistician-group/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "dq"
   ],
   "why": "The statistics profession, closest to data quality work on official statistics."
  },
  {
   "id": "RB-KIM",
   "group": "Skills and professions",
   "title": "Government Knowledge and Information Management Profession",
   "publisher": "Government KIM Profession",
   "url": "https://www.gov.uk/government/organisations/civil-service-government-knowledge-information-management-profession/about",
   "updated": "2025-06-20",
   "prov": "V",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "Information, records and knowledge management; publishes a skills framework and runs communities for records officers."
  },
  {
   "id": "RB-SECPROF",
   "group": "Skills and professions",
   "title": "Government Security Profession",
   "publisher": "Government Security Group",
   "url": "https://www.gov.uk/government/organisations/government-security-profession",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Security roles that work alongside data owners and the senior information risk owner."
  },
  {
   "id": "RB-CYBERPROF",
   "group": "Skills and professions",
   "title": "Government Cyber Profession",
   "publisher": "Government Cyber Profession",
   "url": "https://www.gov.uk/government/organisations/government-cyber-profession",
   "updated": "2026-03-26",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Cyber security careers aligned to the digital function."
  },
  {
   "id": "RB-SUCCESS",
   "group": "Skills and professions",
   "title": "Success Profiles",
   "publisher": "Civil Service HR",
   "url": "https://www.gov.uk/government/publications/success-profiles",
   "updated": "2025-01-29",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "The recruitment framework; data responsibilities can be written into role descriptions and behaviours."
  },
  {
   "id": "RB-SFIA",
   "group": "Skills and professions",
   "title": "SFIA 9: the global skills and competency framework for a digital world",
   "publisher": "SFIA Foundation",
   "url": "https://sfia-online.org/en/sfia-9",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Industry skills framework with data management and governance skills; widely used alongside the government framework."
  },
  {
   "id": "RB-PKSB",
   "group": "Skills and professions",
   "title": "Professional Knowledge and Skills Base (PKSB)",
   "publisher": "CILIP",
   "url": "https://www.cilip.org.uk/page/PKSB",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "Knowledge and skills for information professionals, including metadata, taxonomy and records."
  },
  {
   "id": "RB-RSS",
   "group": "Skills and professions",
   "title": "Royal Statistical Society professional development",
   "publisher": "Royal Statistical Society",
   "url": "https://www.rss.org.uk/membership/professional-development/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "dq"
   ],
   "why": "Professional accreditation for statisticians and data scientists."
  },
  {
   "id": "RB-APPDA",
   "group": "Skills and professions",
   "title": "Data analyst apprenticeship standard",
   "publisher": "Skills England",
   "url": "https://www.instituteforapprenticeships.org/apprenticeship-standards/data-analyst-v1-1",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "dq"
   ],
   "why": "An entry route into data roles that public bodies can fund through the apprenticeship levy."
  },
  {
   "id": "RB-DAMA",
   "group": "Skills and professions",
   "title": "DAMA-DMBOK: Data Management Body of Knowledge",
   "publisher": "DAMA International",
   "url": "https://www.dama.org/cpages/body-of-knowledge",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "The most widely used body of knowledge for data management, with a professional certification (CDMP)."
  },
  {
   "id": "RB-DCAM",
   "group": "Skills and professions",
   "title": "DCAM: Data Management Capability Assessment Model",
   "publisher": "EDM Council",
   "url": "https://edmcouncil.org/frameworks/dcam/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "An industry capability assessment model for data management, used here only to cross-check coverage."
  },
  {
   "id": "RB-CMMI",
   "group": "Skills and professions",
   "title": "Capability Maturity Model Integration (CMMI)",
   "publisher": "ISACA (CMMI Institute)",
   "url": "https://cmmiinstitute.com/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "The origin of the five-level maturity pattern most data maturity models use."
  },
  {
   "id": "RB-CAF",
   "group": "Cyber and security",
   "title": "Cyber Assessment Framework (CAF)",
   "publisher": "National Cyber Security Centre",
   "url": "https://www.ncsc.gov.uk/collection/cyber-assessment-framework",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Outcome-based framework government uses to assess the cyber resilience of essential functions and the systems holding critical data."
  },
  {
   "id": "RB-GCSS",
   "group": "Cyber and security",
   "title": "Government Cyber Security Strategy: 2022 to 2030",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/publications/government-cyber-security-strategy-2022-to-2030",
   "updated": "2026-01-06",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Sets the aim for government organisations to be resilient to known vulnerabilities and attack methods, using the CAF."
  },
  {
   "id": "RB-GOVS007",
   "group": "Cyber and security",
   "title": "Government Functional Standard GovS 007: Security",
   "publisher": "Government Security Group",
   "url": "https://www.gov.uk/government/publications/government-functional-standard-govs-007-security",
   "updated": "2021-09-13",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "The security functional standard, including information and cyber security, that data owners and the SIRO work within."
  },
  {
   "id": "RB-SBD",
   "group": "Cyber and security",
   "title": "Secure by design",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/collections/secure-by-design",
   "updated": "2024-12-05",
   "prov": "V",
   "caps": [
    "gov",
    "dq"
   ],
   "why": "Building security into digital services from the start, including the systems that create and hold critical data assets."
  },
  {
   "id": "RB-NCSC10",
   "group": "Cyber and security",
   "title": "10 Steps to Cyber Security",
   "publisher": "National Cyber Security Centre",
   "url": "https://www.ncsc.gov.uk/collection/10-steps",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Practical cyber risk management areas, including asset management and incident management."
  },
  {
   "id": "RB-NCSCIR",
   "group": "Cyber and security",
   "title": "Incident management",
   "publisher": "National Cyber Security Centre",
   "url": "https://www.ncsc.gov.uk/collection/incident-management",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "dq"
   ],
   "why": "Planning and handling cyber incidents, including those that corrupt or expose critical data."
  },
  {
   "id": "RB-NCSCCLOUD",
   "group": "Cyber and security",
   "title": "Cloud security guidance",
   "publisher": "National Cyber Security Centre",
   "url": "https://www.ncsc.gov.uk/collection/cloud",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "How to choose and configure cloud services securely when critical data moves to them."
  },
  {
   "id": "RB-SECINFO",
   "group": "Cyber and security",
   "title": "Securing information in your service",
   "publisher": "GDS (GOV.UK Service Manual)",
   "url": "https://www.gov.uk/service-manual/technology/securing-your-information",
   "updated": "2024-10-17",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "How service teams protect the information their service holds."
  },
  {
   "id": "RB-AICODE",
   "group": "Cyber and security",
   "title": "AI, open code and vulnerability risk in the public sector",
   "publisher": "Government Digital Service",
   "url": "https://www.gov.uk/guidance/ai-open-code-and-vulnerability-risk-in-the-public-sector",
   "updated": "2026-05-14",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Risks when AI tools are used on open code, relevant to data pipelines and quality tooling."
  },
  {
   "id": "RB-CLOUD",
   "group": "Technology and architecture",
   "title": "Government Cloud First policy",
   "publisher": "Government Digital Service",
   "url": "https://www.gov.uk/guidance/government-cloud-first-policy",
   "updated": "2023-06-19",
   "prov": "V",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "Public cloud first for new or migrating services; data assets move with them."
  },
  {
   "id": "RB-API",
   "group": "Technology and architecture",
   "title": "API technical and data standards",
   "publisher": "Government Digital Service",
   "url": "https://www.gov.uk/guidance/gds-api-technical-and-data-standards",
   "updated": "2026-09-30",
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "How to build and document APIs, the data services through which many critical data assets are reached."
  },
  {
   "id": "RB-REFARCH",
   "group": "Technology and architecture",
   "title": "Develop your data and APIs using a reference architecture",
   "publisher": "Government Digital Service",
   "url": "https://www.gov.uk/guidance/develop-your-data-and-apis-using-a-reference-architecture",
   "updated": "2021-03-22",
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "Reference architecture for data and APIs in government."
  },
  {
   "id": "RB-REFDATA",
   "group": "Technology and architecture",
   "title": "Publish reference data for use across government",
   "publisher": "Government Digital Service and Central Digital and Data Office",
   "url": "https://www.gov.uk/guidance/publish-reference-data-for-use-across-government",
   "updated": "2021-03-11",
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "How to publish reference data others can rely on, with a named owner, persistent identifiers, open formats and versioned change."
  },
  {
   "id": "RB-A11YREQ",
   "group": "Technology and architecture",
   "title": "Understanding accessibility requirements for public sector bodies",
   "publisher": "Government Digital Service and Central Digital and Data Office",
   "url": "https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps",
   "updated": "2024-09-30",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "The accessibility regulations apply to the public sector's own websites and apps, including the interfaces staff use in data tools."
  },
  {
   "id": "RB-CHOOSE",
   "group": "Technology and architecture",
   "title": "Choosing technology: an introduction",
   "publisher": "GDS (GOV.UK Service Manual)",
   "url": "https://www.gov.uk/service-manual/technology/choosing-technology-an-introduction",
   "updated": "2024-10-15",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "How to choose technology that avoids lock-in and stays maintainable."
  },
  {
   "id": "RB-OPENSRC",
   "group": "Technology and architecture",
   "title": "Be open and use open source",
   "publisher": "Government Digital Service",
   "url": "https://www.gov.uk/guidance/be-open-and-use-open-source",
   "updated": "2021-03-31",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Point 3 of the Technology Code of Practice; open code and open formats reduce future legacy."
  },
  {
   "id": "RB-MSC",
   "group": "Commercial and procurement",
   "title": "Model Services Contract",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/publications/model-services-contract",
   "updated": "2025-11-24",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "The model contract for complex services, including schedules on data, security and exit."
  },
  {
   "id": "RB-MTC20",
   "group": "Commercial and procurement",
   "title": "The Mid-Tier Contract: Schedule 20 (Processing Data)",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/publications/the-mid-tier-contract-schedule-20-processing-data",
   "updated": "2025-02-21",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Standard data processing terms for mid-tier contracts."
  },
  {
   "id": "RB-PA23",
   "group": "Commercial and procurement",
   "title": "Procurement Act 2023",
   "publisher": "legislation.gov.uk",
   "url": "https://www.legislation.gov.uk/ukpga/2023/54/contents",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "The law governing public procurement, including transparency notices that suppliers and buyers publish."
  },
  {
   "id": "RB-PA23G",
   "group": "Commercial and procurement",
   "title": "Procurement Act 2023: guidance documents",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/collections/procurement-act-2023-guidance-documents",
   "updated": "2026-02-04",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Guidance for each phase of a procurement under the Act."
  },
  {
   "id": "RB-GCLOUD",
   "group": "Commercial and procurement",
   "title": "G-Cloud 15 framework",
   "publisher": "Crown Commercial Service",
   "url": "https://www.crowncommercial.gov.uk/agreements/RM1557.15",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "The main route for buying cloud hosting, software and support, including catalogue and data quality tools."
  },
  {
   "id": "RB-COMMFN",
   "group": "Skills and professions",
   "title": "Government Commercial Function",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/organisations/government-commercial-function",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "The commercial profession, which buys the services and tools that hold critical data assets."
  },
  {
   "id": "RB-SRO",
   "group": "Delivery, change and investment",
   "title": "Role of the senior responsible owner",
   "publisher": "National Infrastructure and Service Transformation Authority",
   "url": "https://www.gov.uk/government/publications/the-role-of-the-senior-responsible-owner",
   "updated": "2026-02-23",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "What a senior responsible owner is accountable for; data assets the programme touches fall within it."
  },
  {
   "id": "RB-SMROLES",
   "group": "Delivery, change and investment",
   "title": "What each role does in a service team",
   "publisher": "GDS (GOV.UK Service Manual)",
   "url": "https://www.gov.uk/service-manual/the-team/what-each-role-does-in-service-team",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Service team roles, including the service owner and product manager who decide what data a service collects."
  },
  {
   "id": "RB-PDPROF",
   "group": "Skills and professions",
   "title": "How to join the Project Delivery Profession",
   "publisher": "Government Project Delivery",
   "url": "https://www.gov.uk/guidance/how-to-join-the-project-delivery-profession",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "The profession for programme and project leaders."
  },
  {
   "id": "RB-PRA",
   "group": "Records and information management",
   "title": "Public Records Act 1958",
   "publisher": "legislation.gov.uk",
   "url": "https://www.legislation.gov.uk/ukpga/Eliz2/6-7/51/contents",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "The legal duty to manage, select and transfer public records, which includes many data assets."
  },
  {
   "id": "RB-TNAIM",
   "group": "Records and information management",
   "title": "Manage information: guidance for government",
   "publisher": "The National Archives",
   "url": "https://www.nationalarchives.gov.uk/information-management/manage-information/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "Guidance on information and records management policy, processes, retention and digital records."
  },
  {
   "id": "RB-TNATRANS",
   "group": "Records and information management",
   "title": "Digital records transfer",
   "publisher": "The National Archives",
   "url": "https://www.nationalarchives.gov.uk/information-management/manage-information/digital-records-transfer/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "How digital records, including data, are selected and transferred to The National Archives."
  },
  {
   "id": "RB-ISO15489",
   "group": "Records and information management",
   "title": "ISO 15489-1:2016 Records management: concepts and principles",
   "publisher": "International Organization for Standardization",
   "url": "https://www.iso.org/standard/62542.html",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov",
    "cat"
   ],
   "why": "The international records management standard. Its site blocks automated checking."
  },
  {
   "id": "RB-ISO23081",
   "group": "Records and information management",
   "title": "ISO 23081-1:2017 Metadata for records: principles",
   "publisher": "International Organization for Standardization",
   "url": "https://www.iso.org/standard/73172.html",
   "updated": null,
   "prov": "S",
   "caps": [
    "cat"
   ],
   "why": "Records metadata principles, the records-management counterpart to catalogue metadata. Its site blocks automated checking."
  },
  {
   "id": "RB-DSA",
   "group": "Data and AI",
   "title": "Data Standards Authority",
   "publisher": "Government Digital Service",
   "url": "https://www.gov.uk/government/groups/data-standards-authority",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "Sets and promotes the data standards organisations use to make data interoperable."
  },
  {
   "id": "RB-DQHUB",
   "group": "Data and AI",
   "title": "Government Data Quality Hub",
   "publisher": "Office for National Statistics",
   "url": "https://www.gov.uk/government/organisations/government-data-quality-hub",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "dq"
   ],
   "why": "Cross-government centre for data quality guidance, tools and support."
  },
  {
   "id": "RB-OSP",
   "group": "Technology and architecture",
   "title": "Open Standards principles",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles",
   "updated": "2018-04-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "How government selects and uses open standards for software interoperability, data and document formats, including to avoid vendor lock-in."
  },
  {
   "id": "RB-TCOP4",
   "group": "Technology and architecture",
   "title": "Technology Code of Practice point 4: make use of open standards",
   "publisher": "GDS",
   "url": "https://www.gov.uk/guidance/make-use-of-open-standards",
   "updated": "2021-03-31",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "What a plan must show about open standards and data to meet point 4, including avoiding lock-in."
  },
  {
   "id": "RB-TCOP11",
   "group": "Commercial and procurement",
   "title": "Technology Code of Practice point 11: define your purchasing strategy",
   "publisher": "GDS",
   "url": "https://www.gov.uk/guidance/define-your-purchasing-strategy",
   "updated": "2026-09-03",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "A purchasing strategy must show commercial and technology aspects and contractual limitations have been considered; it is checked in spend control."
  },
  {
   "id": "RB-LOCKIN",
   "group": "Technology and architecture",
   "title": "Managing technical lock-in in the cloud",
   "publisher": "GDS",
   "url": "https://www.gov.uk/guidance/managing-technical-lock-in-in-the-cloud",
   "updated": "2026-09-03",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Types of lock-in, weighing value against portability, and including exit cost and time in business cases."
  },
  {
   "id": "RB-PPN0715",
   "group": "Commercial and procurement",
   "title": "Procurement Policy Note 07/15: open standards for technology",
   "publisher": "Cabinet Office",
   "url": "https://www.gov.uk/government/publications/procurement-policy-note-0715-open-standards-for-technology",
   "updated": "2023-01-31",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Tells buyers to specify open standards in technology procurements."
  },
  {
   "id": "RB-METASTD",
   "group": "Data and AI",
   "title": "Metadata standards for sharing and publishing data",
   "publisher": "Data Standards Authority",
   "url": "https://www.gov.uk/government/collections/metadata-standards-for-sharing-and-publishing-data",
   "updated": "2026-04-22",
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "The recommended metadata standards for sharing data within government and for publishing it."
  },
  {
   "id": "RB-DSACAT",
   "group": "Data and AI",
   "title": "Data Standards Authority: Standards Catalogue",
   "publisher": "Data Standards Authority",
   "url": "https://www.gov.uk/government/publications/data-standards-authority-standards-catalogue",
   "updated": "2023-10-25",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "The standards the Data Standards Authority has endorsed, with their status."
  },
  {
   "id": "RB-CMACLOUD",
   "group": "Commercial and procurement",
   "title": "Cloud services market investigation",
   "publisher": "Competition and Markets Authority",
   "url": "https://www.gov.uk/cma-cases/cloud-services-market-investigation",
   "updated": "2025-07-31",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "The CMA's final decision on public cloud infrastructure, covering egress fees, interoperability and software licensing."
  },
  {
   "id": "RB-CMAPKG",
   "group": "Commercial and procurement",
   "title": "CMA announces package of actions on business software and cloud services",
   "publisher": "Competition and Markets Authority",
   "url": "https://www.gov.uk/government/news/cma-announces-package-of-actions-on-business-software-and-cloud-services",
   "updated": "2026-03-31",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Follow-up actions to the cloud investigation, including commitments on egress fees and interoperability and a planned investigation into business software licensing."
  },
  {
   "id": "RB-EUDA",
   "group": "Legislation",
   "title": "EU Data Act (Regulation (EU) 2023/2854)",
   "publisher": "European Union",
   "url": "https://eur-lex.europa.eu/eli/reg/2023/2854/oj",
   "updated": null,
   "prov": "S",
   "caps": [
    "gov"
   ],
   "why": "Switching rules for cloud and other data processing services supplied into the EU, phasing out switching charges. Applies to services supplied into the EU, not to UK law."
  },
  {
   "id": "RB-FTS",
   "group": "Commercial and procurement",
   "title": "Find a Tender",
   "publisher": "Cabinet Office",
   "url": "https://www.find-tender.service.gov.uk/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Where public procurement notices are published; search it for other bodies' catalogue, data quality and data platform requirements."
  },
  {
   "id": "RB-GCSEARCH",
   "group": "Commercial and procurement",
   "title": "Digital Marketplace: search G-Cloud services",
   "publisher": "Crown Commercial Service",
   "url": "https://www.applytosupply.digitalmarketplace.service.gov.uk/g-cloud/search",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Service descriptions on G-Cloud include standards, APIs and how buyers can get their data out at the end of a contract."
  },
  {
   "id": "RB-PROVO",
   "group": "Standards",
   "title": "PROV-O: the PROV ontology",
   "publisher": "W3C",
   "url": "https://www.w3.org/TR/prov-o/",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "An open vocabulary for provenance, used to describe where data came from and what was done to it."
  },
  {
   "id": "RB-SKOS",
   "group": "Standards",
   "title": "SKOS: Simple Knowledge Organization System reference",
   "publisher": "W3C",
   "url": "https://www.w3.org/TR/skos-reference/",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat",
    "gov"
   ],
   "why": "The open format for glossaries, thesauri and taxonomies, so business terms can move between tools."
  },
  {
   "id": "RB-CSVW",
   "group": "Standards",
   "title": "CSV on the Web (CSVW) primer",
   "publisher": "W3C",
   "url": "https://www.w3.org/TR/tabular-data-primer/",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "Describes the columns, types and constraints of CSV files, so files carry their own data dictionary."
  },
  {
   "id": "RB-OLINEAGE",
   "group": "Standards",
   "title": "OpenLineage",
   "publisher": "LF AI & Data Foundation",
   "url": "https://openlineage.io/docs/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "An open specification for lineage events from running jobs, so lineage can be collected once and read by several tools."
  },
  {
   "id": "RB-ODCS",
   "group": "Standards",
   "title": "Open Data Contract Standard (ODCS)",
   "publisher": "Bitol (LF AI & Data Foundation)",
   "url": "https://bitol-io.github.io/open-data-contract-standard/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "An open format for data contracts, including schema, quality rules and service levels, readable by more than one tool."
  },
  {
   "id": "RB-ODPS",
   "group": "Standards",
   "title": "Open Data Product Standard (ODPS)",
   "publisher": "Bitol (LF AI & Data Foundation)",
   "url": "https://bitol-io.github.io/open-data-product-standard/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "An open format describing data products, designed to reference data contracts."
  },
  {
   "id": "RB-EGERIA",
   "group": "Standards",
   "title": "Egeria open metadata and governance",
   "publisher": "LF AI & Data Foundation",
   "url": "https://egeria-project.org/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "cat",
    "gov"
   ],
   "why": "An open source project for exchanging metadata between tools from different vendors; useful as a reference for open metadata types and connectors."
  },
  {
   "id": "RB-OAS",
   "group": "Standards",
   "title": "OpenAPI Specification",
   "publisher": "OpenAPI Initiative",
   "url": "https://spec.openapis.org/oas/latest.html",
   "updated": null,
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "The open format for describing REST APIs; government API guidance recommends it."
  },
  {
   "id": "RB-MCPSPEC",
   "group": "Standards",
   "title": "Model Context Protocol",
   "publisher": "Model Context Protocol project",
   "url": "https://modelcontextprotocol.io/",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "An open protocol for connecting AI assistants to tools and data, such as a catalogue."
  },
  {
   "id": "RB-RMDG",
   "group": "Delivery, change and investment",
   "title": "A roadmap for modern digital government 2025 to 2030",
   "publisher": "Government Digital Service",
   "url": "https://roadmap-for-modern-digital-government.campaign.gov.uk",
   "updated": "2026-10-09",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "The government's action plan to 2030, with six priorities, from joining up public services to transparency and accountability."
  },
  {
   "id": "RB-SMUR",
   "group": "Service delivery and technology",
   "title": "Service Manual: finding participants for user research",
   "publisher": "GDS (GOV.UK Service Manual)",
   "url": "https://www.gov.uk/service-manual/user-research/find-user-research-participants",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Participants must be actual or likely users, and research must include disabled people."
  },
  {
   "id": "RB-SMCONSENT",
   "group": "Service delivery and technology",
   "title": "Service Manual: getting informed consent for user research",
   "publisher": "GDS (GOV.UK Service Manual)",
   "url": "https://www.gov.uk/service-manual/user-research/getting-users-consent-for-research",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Every participant gives informed consent, even colleagues in the same organisation."
  },
  {
   "id": "RB-SMPRIVACY",
   "group": "Service delivery and technology",
   "title": "Service Manual: managing user research data and participant privacy",
   "publisher": "GDS (GOV.UK Service Manual)",
   "url": "https://www.gov.uk/service-manual/user-research/managing-user-research-data-participant-privacy",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "How to collect, store and delete participants' personal data."
  },
  {
   "id": "RB-SMDISABLED",
   "group": "Service delivery and technology",
   "title": "Service Manual: running research sessions with disabled people",
   "publisher": "GDS (GOV.UK Service Manual)",
   "url": "https://www.gov.uk/service-manual/user-research/running-research-sessions-with-people-with-disabilities",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "gov",
    "cat",
    "dq"
   ],
   "why": "Planning sessions that work for disabled participants and their assistive technology."
  },
  {
   "id": "RB-DGUROADMAP",
   "group": "Data and AI",
   "title": "data.gov.uk roadmap",
   "publisher": "Government Digital Service",
   "url": "https://data.gov.uk/roadmap",
   "updated": "2026-11-05",
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "A public Now, Next, Later roadmap with feedback routes; the model this portal's roadmap follows."
  },
  {
   "id": "RB-ISO8601",
   "group": "Standards",
   "title": "ISO 8601-1:2019 Date and time: representations for information interchange",
   "publisher": "ISO",
   "url": "https://www.iso.org/standard/70907.html",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "The date format the metadata guidance asks for, for example 2026-11-12."
  },
  {
   "id": "RB-ISO3166",
   "group": "Standards",
   "title": "ISO 3166-1:2020 Country codes",
   "publisher": "ISO",
   "url": "https://www.iso.org/standard/72482.html",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "One list of country codes across every service, so country fields can be joined."
  },
  {
   "id": "RB-ISO4217",
   "group": "Standards",
   "title": "ISO 4217 Currency codes",
   "publisher": "ISO",
   "url": "https://www.iso.org/iso-4217-currency-codes.html",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "Three-letter currency codes for spend and payments data."
  },
  {
   "id": "RB-ONSGEO",
   "group": "Geospatial",
   "title": "Names and codes listings (GSS geography codes)",
   "publisher": "Office for National Statistics",
   "url": "https://www.ons.gov.uk/methodology/geography/geographicalproducts/namescodesandlookups/namesandcodeslistings",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "Definitive nine-character codes and names for UK statistical and administrative geographies."
  },
  {
   "id": "RB-GSSHARM",
   "group": "Statistics",
   "title": "Harmonised standards and guidance",
   "publisher": "Government Analysis Function",
   "url": "https://analysisfunction.civilservice.gov.uk/government-statistical-service-and-statistician-group/gss-support/gss-harmonisation-support/harmonised-standards-and-guidance/",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat",
    "dq"
   ],
   "why": "Shared definitions and questions for topics such as age, sex, ethnicity and language, so statistics are comparable."
  },
  {
   "id": "RB-SHACL",
   "group": "Standards",
   "title": "Shapes Constraint Language (SHACL)",
   "publisher": "W3C",
   "url": "https://www.w3.org/TR/shacl/",
   "updated": null,
   "prov": "V",
   "caps": [
    "cat"
   ],
   "why": "Rules that check linked data, such as catalogue records or vocabularies, before they are published."
  },
  {
   "id": "RB-NCSCPQC",
   "group": "Cyber and security",
   "title": "Timelines for migration to post-quantum cryptography",
   "publisher": "National Cyber Security Centre",
   "url": "https://www.ncsc.gov.uk/guidance/pqc-migration-timelines",
   "updated": "2025-03-20",
   "prov": "V",
   "caps": [
    "gov"
   ],
   "why": "Discovery and an initial plan by 2028, priority migration by 2031 and all systems by 2035. Knowing which critical assets depend on cryptography is the discovery step."
  }
 ],
 "depth_refs": {
  "DD-01": [
   "RB-DSPT",
   "RB-CALD"
  ],
  "DD-02": [
   "RB-CLD",
   "RB-ASCOF",
   "RB-CDM",
   "RB-CIN"
  ],
  "DD-03": [
   "RB-UPRN",
   "RB-GEMINI",
   "RB-QFAIR",
   "RB-GEOBP"
  ],
  "DD-04": [
   "RB-COP",
   "RB-QAAD",
   "RB-SDMX"
  ],
  "DD-05": [
   "RB-DUAA",
   "RB-DEA",
   "RB-ICOSHARE",
   "RB-ICODSA"
  ],
  "DD-06": [
   "RB-AIREADY",
   "RB-ATRS",
   "RB-AIPLAY",
   "RB-ETH"
  ],
  "DD-07": [
   "RB-PSFA",
   "RB-DEA"
  ],
  "DD-08": [
   "RB-DPA",
   "RB-GSC"
  ],
  "DD-10": [
   "RB-OPEN"
  ],
  "DD-11": [
   "RB-TNA",
   "RB-TNARET"
  ],
  "DD-12": [
   "RB-LDD"
  ],
  "DD-15": [
   "RB-DCATGOV"
  ]
 },
 "erd_example": [
  {
   "id": "PERSON",
   "entity": "Person",
   "desc": "Someone the service supports"
  },
  {
   "id": "CASE",
   "entity": "Case",
   "desc": "A piece of work about one person",
   "to": "PERSON",
   "rel": "is about",
   "card": "many to one"
  },
  {
   "id": "APPOINTMENT",
   "entity": "Appointment",
   "desc": "A meeting held for a case",
   "to": "CASE",
   "rel": "is held for",
   "card": "many to one"
  },
  {
   "id": "OUTCOME",
   "entity": "Outcome",
   "desc": "What an appointment recorded",
   "to": "APPOINTMENT",
   "rel": "records",
   "card": "one to one"
  }
 ],
 "governance_layers": [
  {
   "n": 1,
   "name": "Direction",
   "roles": [
    "BRD",
    "CDO"
   ],
   "may": [
    "Set data policy, standards and risk appetite",
    "Resolve escalations between owners",
    "Approve exceptions above an owner's authority"
   ],
   "may_not": [
    "Edit records or quality rules directly"
   ]
  },
  {
   "n": 2,
   "name": "Asset accountability",
   "roles": [
    "OWN",
    "IAO"
   ],
   "may": [
    "Approve classification, access policy and sharing",
    "Approve changes to the meaning of data items",
    "Accept risks and approve exceptions for their assets",
    "Approve retention and disposal"
   ],
   "may_not": [
    "Change systems or data directly, without the custodian"
   ]
  },
  {
   "n": 3,
   "name": "Stewardship",
   "roles": [
    "STW",
    "CAT",
    "DQL"
   ],
   "may": [
    "Maintain catalogue records, glossary definitions and metadata",
    "Set and run quality rules within the owner's targets",
    "Propose changes to meaning, access or classification"
   ],
   "may_not": [
    "Change classification or approve sharing",
    "Change a definition's meaning without the owner"
   ]
  },
  {
   "n": 4,
   "name": "Custody and operation",
   "roles": [
    "CUS"
   ],
   "may": [
    "Run storage, backups and technical access controls",
    "Carry out approved access changes, fixes and disposal"
   ],
   "may_not": [
    "Grant access without approval",
    "Change what data means"
   ]
  },
  {
   "n": 5,
   "name": "Use",
   "roles": [
    "USR"
   ],
   "may": [
    "Use the data for the agreed purpose",
    "Report problems and request access or changes"
   ],
   "may_not": [
    "Change master data",
    "Share the data on without approval"
   ]
  }
 ],
 "governance_advisers": [
  {
   "roles": [
    "DPO"
   ],
   "text": "Advises every layer on lawful basis, DPIAs and rights; has no change rights."
  },
  {
   "roles": [
    "PUB"
   ],
   "text": "Tests whether decisions are fair and understandable to the people the data describes."
  }
 ],
 "findings": [
  {
   "id": "F-01",
   "title": "Issues framework Table 4 contradicts its own rule for a 97.5% target",
   "detail": "The framework says the High band starts halfway between the Middle band start and the target. For a 97.5% target the Middle band starts at 95%, so the High band should start at 96.25%. Table 4 shows 96.75%. The other four rows follow the rule.",
   "src": "SRC-DQIF",
   "verified": "2026-11-05",
   "action": "This portal follows the stated rule. Raise with the GDS data quality team; tracked as a repository issue."
  },
  {
   "id": "F-02",
   "title": "The Data Ethics Framework is now the Data and AI Ethics Framework",
   "detail": "The GOV.UK page at the Data Ethics Framework address is titled 'Data and AI Ethics Framework' (updated 18 December 2025).",
   "src": null,
   "verified": "2026-11-05",
   "action": "Use the new name. Earlier practitioner material that cites the old name should be updated."
  },
  {
   "id": "F-03",
   "title": "The GOV.UK style guide has moved",
   "detail": "The style guide and 'writing for GOV.UK' addresses on GOV.UK now redirect to guidance.publishing.service.gov.uk.",
   "src": null,
   "verified": "2026-11-05",
   "action": "Link to the new address."
  },
  {
   "id": "F-05",
   "title": "The government data maturity framework uses a licence this portal cannot carry",
   "detail": "The Data Maturity Assessment for Government framework is published under CC BY-NC-SA 4.0, not the Open Government Licence, and asks government users to contact CDDO. Its level descriptions cannot be copied into OGL content.",
   "src": "SRC-DMA",
   "verified": "2026-11-05",
   "action": "The capability model links to each topic and level and records only names and row counts. Check C-21 stops its text being copied (OR-14)."
  },
  {
   "id": "F-06",
   "title": "Legacy technology guidance asks for a data asset register but does not mention the DAM Policy",
   "detail": "The second principle of 'Managing legacy technology' (updated 15 October 2026) is to build a complete and accurate register of your data assets. The DAM Policy and its guidance do not refer to it, so legacy programmes may build a second, separate register.",
   "rb": "RB-LEGACY",
   "verified": "2026-11-05",
   "action": "Delivery and change practice CH-04 starts legacy exits from the DAM catalogue. Suggest GDS cross-refers the two."
  },
  {
   "id": "F-07",
   "title": "The government learning platform is not yet fully accessible",
   "detail": "The Government Skills Campus accessibility statement (last updated 14 April 2026) says some parts do not meet WCAG 2.2 AA, with compliance aimed for by the end of 2026.",
   "url": "https://www.gov.uk/government/publications/accessibility-statement-for-the-government-skills-campus-gsc",
   "url_title": "Accessibility statement for the Government Skills Campus",
   "verified": "2026-11-05",
   "action": "The learning routes point to public GOV.UK pages first; organisations should check that learners with access needs can use the platform or have an alternative."
  },
  {
   "id": "F-04",
   "title": "Four metadata properties have no slot in the Metadata Exchange Model",
   "detail": "temporalCoverage, conformsTo, expires and supersededBy appear in the GOV.UK metadata guidance but not in the published MEM classes.",
   "src": "SRC-MD",
   "verified": "2026-11-05",
   "action": "Proposed crosswalk below, to be agreed by the metadata standards owner (OR-06)."
  }
 ],
 "mem_proposal": [
  {
   "prop": "temporalCoverage",
   "term": "dcterms:temporal",
   "note": "DCAT uses dcterms:temporal with a dcterms:PeriodOfTime (dcat:startDate, dcat:endDate)."
  },
  {
   "prop": "conformsTo",
   "term": "dcterms:conformsTo",
   "note": "Already used by DCAT for a standard or schema a resource conforms to."
  },
  {
   "prop": "expires",
   "term": "dcterms:valid",
   "note": "Dublin Core 'date (often a range) of validity'; record the end date. No DCAT-specific term exists."
  },
  {
   "prop": "supersededBy",
   "term": "dcterms:isReplacedBy",
   "note": "Dublin Core relation for a resource that supplants this one; DCAT 3 versioning also offers dcat:previousVersion in the other direction."
  }
 ],
 "design": {
  "theory_of_change": {
   "problem": "Departments must adopt the DAM Policy, but guidance for its three capabilities is spread across many pages and practitioner packs, so the same facts are recorded several times and returns are assembled late.",
   "chain": [
    {
     "id": "TOC-IN",
     "stage": "Inputs",
     "items": [
      "Published GOV.UK guidance behind the policy",
      "Practitioner playbooks for governance and quality",
      "Open standards (DCAT, MEM, DQV)",
      "GitHub for hosting, contact and automation"
     ]
    },
    {
     "id": "TOC-ACT",
     "stage": "Activities",
     "items": [
      "Join the three capabilities into one method with one set of roles",
      "Give each role a route and a learning journey",
      "Check sources, accessibility and links automatically every week"
     ]
    },
    {
     "id": "TOC-OUT",
     "stage": "Outputs",
     "items": [
      "One portal with step-by-step methods, templates and modules",
      "Open data versions of every requirement, template and term",
      "A public record of defects, open items and health"
     ]
    },
    {
     "id": "TOC-OC",
     "stage": "Outcomes",
     "items": [
      "Owners, records and DQAPs are set up once and reused",
      "Returns are built from catalogue records, not retyped",
      "Practitioners know which requirement each step meets"
     ]
    },
    {
     "id": "TOC-IMP",
     "stage": "Impact",
     "items": [
      "Critical data assets are owned, findable and fit for use across government",
      "Services that rely on shared data, and the people they serve, are less affected by poor data"
     ]
    }
   ],
   "assumptions": [
    "Practitioners will use a single portal if it saves them effort (untested, OR-04)",
    "Hand-offs between capabilities reduce duplicate recording (untested)",
    "GOV.UK guidance remains the authority and changes are caught weekly"
   ]
  },
  "research": {
   "questions": [
    "Can each role find the steps that apply to them in under two minutes?",
    "Do the hand-offs match how departments actually organise ownership, cataloguing and quality?",
    "Which sector supplements (DD-01 to DD-14) are needed first?",
    "Can people with access needs complete a route without help?"
   ],
   "methods": [
    "Moderated usability sessions with 5 to 8 people per role, including people who use assistive technology",
    "Tree test of the navigation",
    "A survey through the Working Group",
    "Analysis of feedback received through the contact and feedback forms"
   ],
   "hypotheses": [
    {
     "id": "H-01",
     "statement": "Routes by role reduce time to find the right step.",
     "falsified_if": "Median time to find a step is not lower on a route than through search alone."
    },
    {
     "id": "H-02",
     "statement": "Recording the owner once and reusing it reduces mismatches.",
     "falsified_if": "Owner mismatches between register, record and DQAP do not fall after adoption."
    },
    {
     "id": "H-03",
     "statement": "Learning modules improve confidence for new owners and stewards.",
     "falsified_if": "Self-rated confidence does not rise after completing the role's modules."
    }
   ],
   "ethics": "Participants give informed consent, can withdraw at any time, and are recorded only with permission. Notes name roles, not people. No session collects data above OFFICIAL."
  },
  "blueprint": [
   {
    "id": "BP-1",
    "stage": "Find",
    "user": "Searches or follows a link to the portal",
    "front": "Home page, role cards, search",
    "back": "GitHub Pages hosting; sitemap and metadata for search engines",
    "support": "Weekly health run keeps pages current"
   },
   {
    "id": "BP-2",
    "stage": "Learn",
    "user": "Works through modules for their role",
    "front": "Learning page, checks of understanding, progress",
    "back": "Progress kept in the reader's browser only",
    "support": "Content reviewed against GOV.UK sources each release"
   },
   {
    "id": "BP-3",
    "stage": "Do",
    "user": "Follows step-by-step methods and copies templates",
    "front": "Capability pages, templates, open data downloads",
    "back": "Content file generates every page and export",
    "support": "Build refuses broken references"
   },
   {
    "id": "BP-4",
    "stage": "Report",
    "user": "Builds the return and evidence pack",
    "front": "Policy spine, joined-up year, templates",
    "back": "Requirements and templates as CSV",
    "support": "Release notes record changes that affect returns"
   },
   {
    "id": "BP-5",
    "stage": "Improve",
    "user": "Reports a problem or suggests a change",
    "front": "Contact form, page feedback, Discussions",
    "back": "GitHub issue forms and Discussions",
    "support": "A person triages issues; fixes include a new check"
   }
  ],
  "requirements": [
   {
    "id": "FR-01",
    "kind": "Functional",
    "moscow": "Must",
    "text": "Show every DAM Policy requirement with its strength, source and the step that meets it.",
    "features": [
     "dam"
    ],
    "checks": [
     "C-03",
     "C-08"
    ]
   },
   {
    "id": "FR-02",
    "kind": "Functional",
    "moscow": "Must",
    "text": "Give a step-by-step method for each capability with roles, templates and measures.",
    "features": [
     "governance",
     "cataloguing",
     "quality"
    ],
    "checks": [
     "C-10",
     "B-06"
    ]
   },
   {
    "id": "FR-03",
    "kind": "Functional",
    "moscow": "Must",
    "text": "Offer a route and learning journey for each role, with progress the reader controls.",
    "features": [
     "personas",
     "learning"
    ],
    "checks": [
     "B-10"
    ]
   },
   {
    "id": "FR-04",
    "kind": "Functional",
    "moscow": "Must",
    "text": "Let anyone get in touch without an email address being published.",
    "features": [
     "contact"
    ],
    "checks": [
     "C-04",
     "C-14",
     "B-09"
    ]
   },
   {
    "id": "FR-05",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Let readers search everything and filter every list.",
    "features": [
     "index",
     "library",
     "knowledge"
    ],
    "checks": [
     "B-05",
     "B-08"
    ]
   },
   {
    "id": "FR-06",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Publish the vocabulary, requirements and templates as open data.",
    "features": [
     "library",
     "knowledge"
    ],
    "checks": [
     "C-11"
    ]
   },
   {
    "id": "NFR-01",
    "kind": "Non-functional",
    "moscow": "Must",
    "text": "Meet WCAG 2.2 AA in light and dark modes, from 320 to 1920 pixels wide.",
    "features": [
     "all"
    ],
    "checks": [
     "B-01",
     "B-02",
     "B-03"
    ]
   },
   {
    "id": "NFR-02",
    "kind": "Non-functional",
    "moscow": "Must",
    "text": "Work with scripts turned off and load nothing from other sites.",
    "features": [
     "all"
    ],
    "checks": [
     "C-05",
     "C-12",
     "B-07"
    ]
   },
   {
    "id": "NFR-03",
    "kind": "Non-functional",
    "moscow": "Must",
    "text": "Label every fact with its provenance and keep sources current.",
    "features": [
     "all"
    ],
    "checks": [
     "C-08",
     "HL-01"
    ]
   },
   {
    "id": "NFR-04",
    "kind": "Non-functional",
    "moscow": "Must",
    "text": "Name roles, never people, and hold no personal data.",
    "features": [
     "all"
    ],
    "checks": [
     "C-04",
     "C-17"
    ]
   },
   {
    "id": "NFR-05",
    "kind": "Non-functional",
    "moscow": "Should",
    "text": "Be findable by search engines with accurate descriptions.",
    "features": [
     "all"
    ],
    "checks": [
     "C-16"
    ]
   },
   {
    "id": "TR-01",
    "kind": "Technical",
    "moscow": "Must",
    "text": "Generate every page from one content file and refuse to build on a broken reference.",
    "features": [
     "all"
    ],
    "checks": [
     "T-VAL"
    ]
   },
   {
    "id": "FR-07",
    "kind": "Functional",
    "moscow": "Must",
    "text": "Show every capability the policy and adjacent guidance need, flagged explicit, implicit or inferred, with a signpost to the section it comes from.",
    "features": [
     "capability-model"
    ],
    "checks": [
     "C-22",
     "HL-02"
    ]
   },
   {
    "id": "FR-08",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Let organisations assess their maturity against the government model and DAM strands, keep the answers privately and download them.",
    "features": [
     "capability-model"
    ],
    "checks": [
     "B-13",
     "C-21"
    ]
   },
   {
    "id": "FR-09",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Link each role in the policy to government professions, framework roles, skills and learning routes.",
    "features": [
     "professions"
    ],
    "checks": [
     "C-03",
     "HL-01"
    ]
   },
   {
    "id": "FR-10",
    "kind": "Functional",
    "moscow": "Must",
    "text": "Help organisations embed the policy in business as usual and in change programmes, with actions they can track.",
    "features": [
     "change"
    ],
    "checks": [
     "B-08",
     "B-10"
    ]
   },
   {
    "id": "FR-11",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Help readers find which sector supplements apply to an asset.",
    "features": [
     "sectors"
    ],
    "checks": [
     "B-12",
     "T-VAL"
    ]
   },
   {
    "id": "FR-12",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Help readers find their way: a share menu on every page, a site map, a user guide with guided tours and tutorials.",
    "features": [
     "guide",
     "site-map"
    ],
    "checks": [
     "C-31",
     "B-16"
    ]
   },
   {
    "id": "FR-13",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Let organisations reuse the content through links, embedding, open data, AI assistants and an MCP server.",
    "features": [
     "reuse",
     "data"
    ],
    "checks": [
     "C-28",
     "C-31",
     "C-32"
    ]
   },
   {
    "id": "FR-14",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Help organisations connect and buy data management tools without lock-in, with open standards and RFI questions.",
    "features": [
     "tooling"
    ],
    "checks": [
     "C-33"
    ]
   },
   {
    "id": "FR-15",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Signpost the sister portals where they help, naming each and its status, without merging their journeys or copying their content.",
    "features": [
     "quality",
     "tooling",
     "reuse"
    ],
    "checks": [
     "C-34"
    ]
   },
   {
    "id": "FR-16",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Help people who work across the three portals choose where to start, in what order and why, without merging the portals.",
    "features": [
     "reuse"
    ],
    "checks": [
     "C-35",
     "B-17"
    ]
   },
   {
    "id": "FR-17",
    "kind": "Functional",
    "moscow": "Must",
    "text": "Let users take part in research privately, suggest and vote for ideas, and see the roadmap, backlog and how each item is prioritised against government strategy, in the open.",
    "features": [
     "research"
    ],
    "checks": [
     "C-36",
     "C-04",
     "B-01"
    ]
   },
   {
    "id": "FR-18",
    "kind": "Functional",
    "moscow": "Must",
    "text": "Let teams name people and work email addresses in their own copies of templates, and keep them out of anything published.",
    "features": [
     "governance",
     "cataloguing",
     "quality",
     "library"
    ],
    "checks": [
     "C-38",
     "C-04"
    ]
   },
   {
    "id": "FR-19",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Say whether each template is for business as usual, change or both, offer each template on its own, and offer logs used together as one tabbed workbook.",
    "features": [
     "governance",
     "cataloguing",
     "quality",
     "library",
     "data"
    ],
    "checks": [
     "C-38",
     "C-28"
    ]
   },
   {
    "id": "FR-20",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Give the data type, format, cardinality, controlled values and an example for every catalogue record property.",
    "features": [
     "knowledge",
     "cataloguing"
    ],
    "checks": [
     "C-38",
     "T-VAL"
    ]
   },
   {
    "id": "FR-21",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Group each sector supplement's legislation, standards and frameworks by kind, and show how sector standards meet the catalogue standard.",
    "features": [
     "sectors",
     "knowledge"
    ],
    "checks": [
     "C-38"
    ]
   },
   {
    "id": "FR-22",
    "kind": "Functional",
    "moscow": "Could",
    "text": "Describe a critical data asset's entities, relationships and authoritative source, with a relationship diagram drawn from the list (issue 18).",
    "features": [
     "sectors",
     "cataloguing",
     "data"
    ],
    "checks": [
     "C-39"
    ]
   },
   {
    "id": "FR-23",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Record retention schedule, period and disposal action in the ownership register and catalogue record, from the organisation's own schedule (issue 19).",
    "features": [
     "governance",
     "cataloguing",
     "sectors"
    ],
    "checks": [
     "C-39"
    ]
   },
   {
    "id": "FR-24",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Give a data sharing agreement template covering lawful basis, legal gateway, retention and ending the sharing, and signpost the gateways (issue 20).",
    "features": [
     "governance",
     "sectors"
    ],
    "checks": [
     "C-39"
    ]
   },
   {
    "id": "FR-25",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Show governance layers with the roles in each and what each may and may not change (issue 21).",
    "features": [
     "governance",
     "data"
    ],
    "checks": [
     "C-39"
    ]
   },
   {
    "id": "FR-26",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Signpost health confidentiality gateways and medical device rules in the health and care supplement (issue 22).",
    "features": [
     "sectors"
    ],
    "checks": [
     "C-39"
    ]
   },
   {
    "id": "FR-27",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Give glossary terms and named frameworks, methodologies and standards a tooltip and a link where they are first mentioned on any page, outside headings and existing links.",
    "features": [
     "knowledge"
    ],
    "checks": [
     "C-40"
    ]
   },
   {
    "id": "FR-28",
    "kind": "Functional",
    "moscow": "Should",
    "text": "List each capability's frameworks, methodologies and standards by kind on its Overview, and name the ones that apply at every step.",
    "features": [
     "governance",
     "cataloguing",
     "quality"
    ],
    "checks": [
     "C-40"
    ]
   },
   {
    "id": "FR-29",
    "kind": "Functional",
    "moscow": "Could",
    "text": "Drill down from each slice of the DAMA wheel to its activities and tasks where the portal has them, and publish what a fuller drill-down and a data architecture playbook would take (BL-35, BL-36).",
    "features": [
     "capability-model"
    ],
    "checks": [
     "C-40"
    ]
   },
   {
    "id": "FR-30",
    "kind": "Functional",
    "moscow": "Must",
    "text": "Take every capability in the capability model down to activities with steps, outputs, evidence, measures, who does what and a template.",
    "features": [
     "capability-model",
     "change"
    ],
    "checks": [
     "C-45"
    ]
   },
   {
    "id": "FR-31",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Give people new to data asset management, or leading it, aims by priority, outcomes with indicators, and a plan for 30, 60 and 90 days with 6 and 12 month checkpoints against maturity levels.",
    "features": [
     "personas"
    ],
    "checks": [
     "C-46"
    ]
   },
   {
    "id": "FR-32",
    "kind": "Functional",
    "moscow": "Must",
    "text": "Reach the data portals compass and the asset governance explorer from every page, and keep the capabilities they show the same as the capability model.",
    "features": [
     "all",
     "capability-model"
    ],
    "checks": [
     "C-47"
    ]
   },
   {
    "id": "FR-33",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Give ready-made functional and non-functional requirements for each kind of tool, with a request for information, a requirements schedule, an evaluation method and contract clauses.",
    "features": [
     "tooling",
     "data"
    ],
    "checks": [
     "C-48"
    ]
   },
   {
    "id": "FR-34",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Help learners learn, keep and share what they learn, link it to roles, careers and certifications, and download a learning record to use as CPD evidence.",
    "features": [
     "learning"
    ],
    "checks": [
     "C-48"
    ]
   },
   {
    "id": "FR-35",
    "kind": "Functional",
    "moscow": "Should",
    "text": "Recommend modules, activities and the next checkpoint by role, profession, organisation maturity and data literacy, reading the self-assessment where there is one.",
    "features": [
     "personas"
    ],
    "checks": [
     "C-49"
    ]
   },
   {
    "id": "FR-36",
    "kind": "Functional",
    "moscow": "Should",
    "text": "For every stage of designing and delivering a service, show the gates and assessments, the Service Standard points that touch critical data, what reviewers want to see and where the evidence comes from, linking to published guidance rather than repeating it.",
    "features": [
     "change",
     "personas"
    ],
    "checks": [
     "C-50"
    ]
   },
   {
    "id": "IR-01",
    "kind": "Integration",
    "moscow": "Must",
    "text": "Use only GitHub services (Pages, issue forms, Discussions, Actions and releases), plus an optional Microsoft Forms route for private feedback.",
    "features": [
     "contact",
     "status",
     "whats-new"
    ],
    "checks": [
     "C-05",
     "C-33",
     "HL-01"
    ]
   }
  ],
  "architecture": {
   "components": [
    {
     "id": "AC-01",
     "name": "Content file",
     "detail": "content/playbooks.yaml: requirements, methods, roles, personas, modules, sources and registers."
    },
    {
     "id": "AC-02",
     "name": "Generator",
     "detail": "tools/build.py: validates references, writes static pages, open data, sitemap, images."
    },
    {
     "id": "AC-03",
     "name": "Front end",
     "detail": "Static HTML and CSS with one progressive-enhancement script; no external assets; strict Content Security Policy."
    },
    {
     "id": "AC-04",
     "name": "Checks",
     "detail": "tools/check_site.py (static), tools/check_browser.py (Playwright with axe-core), tests/ (vaccinations)."
    },
    {
     "id": "AC-05",
     "name": "Health run",
     "detail": "tools/health.py: GOV.UK Content API source dates, review date and page weight; results on the Status page."
    },
    {
     "id": "AC-06",
     "name": "GitHub services",
     "detail": "Actions (build, check, publish, weekly health, CodeQL, release), Pages, issue forms, Discussions, Dependabot."
    }
   ],
   "flows": [
    "Change: pull request -> build -> static checks -> vaccinations -> browser checks -> review -> merge -> Pages",
    "Weekly: health run -> Status page -> issue labelled health if something needs a person",
    "Contact: contact form -> pre-filled GitHub issue form -> person sends it -> triage"
   ],
   "data": "No personal data is held. Browser storage keeps progress and display choices on the reader's device only."
  },
  "service_standard": [
   {
    "n": 1,
    "point": "Understand users and their needs",
    "rating": "Partly",
    "evidence": "Roles and needs drawn from practitioner material; research plan written, not yet run (OR-04)."
   },
   {
    "n": 2,
    "point": "Solve a whole problem for users",
    "rating": "Partly",
    "evidence": "Joins three capabilities and the return; depends on GOV.UK guidance and departmental catalogues."
   },
   {
    "n": 3,
    "point": "Provide a joined up experience across all channels",
    "rating": "Partly",
    "evidence": "Links to GOV.UK, the Working Group and the Data Quality Commons; offline support not covered."
   },
   {
    "n": 4,
    "point": "Make the service simple to use",
    "rating": "Met",
    "evidence": "Routes by role, step by step, plain English, search; not yet tested with users."
   },
   {
    "n": 5,
    "point": "Make sure everyone can use the service",
    "rating": "Partly",
    "evidence": "Automated WCAG 2.2 AA checks pass; no testing with disabled users yet (OR-09)."
   },
   {
    "n": 6,
    "point": "Have a multidisciplinary team",
    "rating": "Not yet",
    "evidence": "Built by one practitioner with AI assistance; no dedicated team (OP20)."
   },
   {
    "n": 7,
    "point": "Use agile ways of working",
    "rating": "Met",
    "evidence": "Small releases, public changelog, issues and pull requests."
   },
   {
    "n": 8,
    "point": "Iterate and improve frequently",
    "rating": "Met",
    "evidence": "Weekly health run; feedback routes on every page."
   },
   {
    "n": 9,
    "point": "Create a secure service which protects users' privacy",
    "rating": "Met",
    "evidence": "No personal data, strict CSP, CodeQL, Dependabot, security.txt."
   },
   {
    "n": 10,
    "point": "Define what success looks like and publish performance data",
    "rating": "Partly",
    "evidence": "Success measures defined per capability; no usage data collected by design."
   },
   {
    "n": 11,
    "point": "Choose the right tools and technology",
    "rating": "Met",
    "evidence": "Static site on GitHub Pages; open standards; ADRs recorded."
   },
   {
    "n": 12,
    "point": "Make new source code open",
    "rating": "Met",
    "evidence": "Public repository under MIT; content under OGL."
   },
   {
    "n": 13,
    "point": "Use and contribute to open standards, components and patterns",
    "rating": "Met",
    "evidence": "DCAT, SKOS, DQV, JSON-LD; GOV.UK Design System patterns."
   },
   {
    "n": 14,
    "point": "Operate a reliable service",
    "rating": "Partly",
    "evidence": "Static hosting and health checks; single account dependency (OR-03)."
   }
  ]
 },
 "notices": [
  {
   "id": "N-01",
   "title": "Not official guidance",
   "text": "This portal is a prototype. It is not an official GOV.UK service, is not published or endorsed by GDS or any department, and does not change what the DAM Policy requires. Where it repeats GDS guidance, the GOV.UK page is the authority."
  },
  {
   "id": "N-02",
   "title": "Not legal advice",
   "text": "Nothing here is legal advice. For questions about data protection, data sharing powers or equality duties, ask your data protection officer or legal adviser."
  },
  {
   "id": "N-03",
   "title": "Accuracy and currency",
   "text": "Facts carry a provenance label and sources are re-checked weekly. Guidance changes; check the date on each source and the Status page before relying on a detail."
  },
  {
   "id": "N-04",
   "title": "Information above OFFICIAL",
   "text": "Do not enter information classified above OFFICIAL, or personal data, into this portal, its forms or its GitHub repository. Everything submitted through GitHub is public."
  },
  {
   "id": "N-05",
   "title": "Use of artificial intelligence",
   "text": "An AI assistant (Claude, by Anthropic) helped research, write and build this portal. A person directed the work and reviews each release. Automated checks and source verification are described on the About page."
  },
  {
   "id": "N-06",
   "title": "External links",
   "text": "Links to other sites are provided for reference. We are not responsible for their content or availability; the weekly health run reports links that stop working."
  },
  {
   "id": "N-07",
   "title": "Re-use",
   "text": "You can re-use the content under the Open Government Licence v3.0 and the code under the MIT licence. Third-party material keeps its own licence, listed under credits."
  },
  {
   "id": "N-08",
   "title": "Cookies and tracking",
   "text": "The portal sets no cookies and uses no analytics. Progress and display choices are kept in your own browser and can be cleared at any time."
  }
 ],
 "attribution_statement": "Contains public sector information licensed under the Open Government Licence v3.0.",
 "credits": [
  {
   "who": "Government Digital Service and the teams behind the GOV.UK guidance cited here",
   "what": "The DAM Policy and its guidance, the data quality framework, action plan guide and issues framework, and the GOV.UK Design System patterns",
   "licence": "Crown copyright, Open Government Licence v3.0 (content); MIT (Design System code patterns)"
  },
  {
   "who": "Contributors to the UK Cross-Government Metadata Exchange Model and the Metadata Implementation Working Group",
   "what": "The metadata model used for the cataloguing data dictionary",
   "licence": "Open Government Licence v3.0 (per the repository licence file)"
  },
  {
   "who": "Contributors to the Public Sector Data Quality Commons",
   "what": "The eight-stage data quality playbook, requirements register and tools linked from the quality pages",
   "licence": "MIT (code), CC BY 4.0 (content, from 2.16.1; OGL v3.0 before)"
  },
  {
   "who": "W3C",
   "what": "DCAT and the Data Quality Vocabulary",
   "licence": "W3C Document License (linked, not reproduced)"
  },
  {
   "who": "Lucide Icons and contributors",
   "what": "Icons",
   "licence": "ISC"
  },
  {
   "who": "Deque Systems (axe-core)",
   "what": "Accessibility testing in the build, not shipped",
   "licence": "MPL 2.0"
  },
  {
   "who": "Microsoft (Playwright)",
   "what": "Browser testing in the build, not shipped",
   "licence": "Apache 2.0"
  },
  {
   "who": "segno, python-barcode, Pillow and PyYAML maintainers",
   "what": "QR code, barcode, image generation and content parsing at build time",
   "licence": "BSD (segno), MIT (python-barcode, PyYAML), MIT-CMU (Pillow)"
  }
 ],
 "applicability": [
  {
   "id": "Q-PEOPLE",
   "text": "It holds records about individual people",
   "sups": [
    "SUP-PER",
    "SUP-SHR"
   ]
  },
  {
   "id": "Q-HEALTH",
   "text": "It holds health or care records",
   "sups": [
    "SUP-HLT",
    "SUP-SOC"
   ]
  },
  {
   "id": "Q-PLACE",
   "text": "It holds addresses, locations or map geometry",
   "sups": [
    "SUP-GEO"
   ]
  },
  {
   "id": "Q-STATS",
   "text": "It is used to produce official statistics",
   "sups": [
    "SUP-STA"
   ]
  },
  {
   "id": "Q-AI",
   "text": "It is used, or may be used, for AI, machine learning or automated decision support",
   "sups": [
    "SUP-AI"
   ]
  },
  {
   "id": "Q-SHARE",
   "text": "Personal data in it is shared with, or acquired from, another organisation",
   "sups": [
    "SUP-SHR"
   ]
  },
  {
   "id": "Q-FRAUD",
   "text": "It is used to detect fraud or error",
   "sups": [
    "SUP-FRD"
   ]
  },
  {
   "id": "Q-JUSTICE",
   "text": "It supports law enforcement, justice, defence or security",
   "sups": [
    "SUP-JUS"
   ]
  },
  {
   "id": "Q-LOCAL",
   "text": "It flows to or from councils or the devolved governments",
   "sups": [
    "SUP-DEV",
    "SUP-SOC"
   ]
  },
  {
   "id": "Q-CODES",
   "text": "It relies on code lists or identifiers maintained by other organisations",
   "sups": [
    "SUP-REF"
   ]
  },
  {
   "id": "Q-RECORDS",
   "text": "It must be kept, archived or destroyed on a schedule",
   "sups": [
    "SUP-REC"
   ]
  },
  {
   "id": "Q-MODEL",
   "text": "Other systems or teams build on its structure, or it has a formal data model",
   "sups": [
    "SUP-ARC"
   ]
  },
  {
   "id": "Q-SENSOR",
   "text": "It is time-series or sensor data, such as environmental monitoring",
   "sups": [
    "SUP-ENV"
   ]
  },
  {
   "id": "Q-LEARNERS",
   "text": "It holds records about pupils or learners",
   "sups": [
    "SUP-EDU"
   ]
  }
 ],
 "supplements": [
  {
   "id": "SUP-HLT",
   "dd": "DD-01",
   "title": "Health and care data",
   "icon": "heart-handshake",
   "summary": "For critical data assets that hold patient-level or care records. Adds the health roles, duties and coding standards the core playbooks do not cover.",
   "gov": [
    "Map the data owner and steward to the Caldicott Guardian, the SIRO and, for health IT, the clinical safety officer. Record who holds each role for every asset.",
    "Record the legal basis for each use, the common law duty of confidentiality position and whether the national data opt-out applies.",
    "Check the organisation's latest Data Security and Protection Toolkit assessment covers the systems that hold the asset.",
    "Apply the Caldicott principles when deciding what each user of the asset needs: the minimum necessary, justified for each purpose.",
    "Record the clinical terminology and exchange standards the asset follows, such as SNOMED CT, dm+d and HL7 FHIR UK Core, in conformsTo, so the MEM record points to the sector standard.",
    "Where a health IT system holds the asset, record its clinical safety position: DCB0129 for the supplier and DCB0160 for the organisation that deploys it.",
    "If confidential patient information is used without consent, record the legal basis that sets aside the duty of confidentiality, such as section 251 support, separately from the data protection lawful basis.",
    "If software or AI that uses the asset has a medical purpose, check whether it is a medical device under the Medical Devices Regulations 2002, using the MHRA's guidance.",
    "If NHS health and social care data in the asset is used for research or analysis beyond direct care, give access through a secure data environment, as DHSC's secure data environment policy guidelines require, and record which environment in the catalogue record."
   ],
   "cat": [
    {
     "prop": "legalBasis",
     "term": "dpv:hasLegalBasis",
     "rule": "The lawful basis and, for health data, the special category condition"
    },
    {
     "prop": "optOutApplied",
     "term": "local extension",
     "rule": "Whether the national data opt-out has been applied to this distribution (yes, no or not applicable)"
    },
    {
     "prop": "deidentification",
     "term": "local extension",
     "rule": "Identifiable, pseudonymised or anonymised, and the method used"
    },
    {
     "prop": "conformsTo",
     "term": "dcterms:conformsTo",
     "rule": "The NHS data set or Data Dictionary standard the data follows"
    }
   ],
   "rules": [
    {
     "id": "HLT-01",
     "element": "NHS number",
     "rule": "NHS number is recorded",
     "dimension": "completeness",
     "check": "not_null",
     "params": {
      "column": "nhs_number"
     }
    },
    {
     "id": "HLT-02",
     "element": "NHS number",
     "rule": "NHS number is 10 digits with a valid modulus 11 check digit",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "nhs_number",
      "scheme": "nhs_number"
     }
    },
    {
     "id": "HLT-03",
     "element": "Date of birth",
     "rule": "Date of birth is not in the future",
     "dimension": "validity",
     "check": "not_future",
     "params": {
      "column": "date_of_birth"
     }
    },
    {
     "id": "HLT-04",
     "element": "Organisation code",
     "rule": "Provider organisation code is in ODS format",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "provider_code",
      "scheme": "ods_code"
     }
    },
    {
     "id": "HLT-05",
     "element": "Diagnosis",
     "rule": "Primary diagnosis is in ICD-10 code format",
     "dimension": "validity",
     "check": "regex",
     "params": {
      "column": "primary_diagnosis",
      "pattern": "[A-Z][0-9]{2}(\\.?[0-9X])?"
     }
    },
    {
     "id": "HLT-06",
     "element": "Ethnicity",
     "rule": "Ethnic category is not unknown or not stated",
     "dimension": "completeness",
     "check": "not_unknown",
     "params": {
      "column": "ethnic_category"
     }
    },
    {
     "id": "HLT-07",
     "element": "NHS number by group",
     "rule": "NHS number completeness does not differ by more than 5 points between ethnic groups",
     "dimension": "completeness",
     "check": "group_disparity",
     "params": {
      "group": "ethnic_category",
      "tolerance": 5,
      "inner": {
       "check": "not_null",
       "column": "nhs_number"
      }
     }
    }
   ],
   "identifiers": [
    {
     "name": "NHS number",
     "format": "10 digits; the last is a modulus 11 check digit",
     "prov": "K"
    },
    {
     "name": "ODS code",
     "format": "3 to 6 letters and digits identifying an NHS or care organisation",
     "prov": "K"
    }
   ],
   "example": "Illustrative, synthetic: an outpatient activity extract shared with a central department. Critical data elements are NHS number, provider code, attendance date and primary diagnosis. Baseline shows NHS number completeness of 97% overall but 91% for one ethnic group; HLT-07 records that as its own issue so it is not averaged away.",
   "risks": [
    "Pseudonymised data is still personal data; access controls and agreements still apply.",
    "Opt-outs and local suppression can bias coverage for some groups; check coverage against an independent count.",
    "Clinical codes can be valid in format but wrong in meaning; format checks do not replace clinical coding audit."
   ],
   "checklist": [
    "Caldicott Guardian, SIRO and clinical safety officer roles are recorded for the asset",
    "Legal basis, confidentiality position and opt-out status are recorded on the catalogue record",
    "NHS number validity and completeness rules are in the DQAP",
    "Quality is broken down by ethnic group where lawful",
    "Access for research and analysis goes through a secure data environment, recorded on the catalogue record"
   ],
   "refs": [
    "RB-CALD",
    "RB-DSPT",
    "RB-DPA",
    "RB-FHIRUK",
    "RB-SNOMED",
    "RB-DCB0129",
    "RB-DCB0160",
    "RB-S251",
    "RB-UKMDR",
    "RB-MHRASW",
    "RB-DSL",
    "RB-SDE",
    "RB-DAPU"
   ]
  },
  {
   "id": "SUP-SOC",
   "dd": "DD-02",
   "title": "Adult and children's social care data",
   "icon": "users",
   "summary": "For assets built from council returns, such as adult social care client level data and children's social care census returns, where the source systems sit outside the policy's scope.",
   "gov": [
    "Record which councils supply the data and that they are not bound by the DAM Policy; agree quality expectations through the collection's own guidance.",
    "Name the owner for the national asset and a contact route for suppliers, not individuals.",
    "Record changes to collection specifications as decisions, because they change what the asset means."
   ],
   "cat": [
    {
     "prop": "spatial",
     "term": "dcterms:spatial",
     "rule": "The councils and nations covered, using GSS codes"
    },
    {
     "prop": "accrualPeriodicity",
     "term": "dcterms:accrualPeriodicity",
     "rule": "The submission cycle, for example quarterly"
    },
    {
     "prop": "conformsTo",
     "term": "dcterms:conformsTo",
     "rule": "The collection specification and its version"
    }
   ],
   "rules": [
    {
     "id": "SOC-01",
     "element": "Council code",
     "rule": "Supplying council is a valid GSS code",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "la_code",
      "scheme": "gss_code"
     }
    },
    {
     "id": "SOC-02",
     "element": "NHS number",
     "rule": "NHS number is valid where present, so care and health records can be linked",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "nhs_number",
      "scheme": "nhs_number"
     }
    },
    {
     "id": "SOC-03",
     "element": "Event date",
     "rule": "Event dates are not in the future",
     "dimension": "validity",
     "check": "not_future",
     "params": {
      "column": "event_start_date"
     }
    },
    {
     "id": "SOC-04",
     "element": "Submission",
     "rule": "Each council's latest submission is no more than one quarter and 30 days old",
     "dimension": "timeliness",
     "check": "freshness",
     "params": {
      "column": "submission_date",
      "expected": "P3M",
      "lag": "P30D"
     }
    },
    {
     "id": "SOC-05",
     "element": "Person and event",
     "rule": "Each event is recorded once for each person",
     "dimension": "uniqueness",
     "check": "unique",
     "params": {
      "columns": [
       "person_id",
       "event_id"
      ]
     }
    }
   ],
   "identifiers": [
    {
     "name": "GSS code",
     "format": "One letter (E, K, L, M, N, S or W) followed by 8 digits",
     "prov": "K"
    }
   ],
   "example": "Illustrative, synthetic: a quarterly client level data asset. SOC-04 shows two councils have not submitted for two quarters; the owner records the gap in the quality statement rather than imputing it.",
   "risks": [
    "Councils use different case management systems, so the same field can be captured differently.",
    "Late or missing submissions make national figures look better or worse than they are.",
    "Linking to health data depends on NHS number quality in council systems."
   ],
   "checklist": [
    "Supplying organisations and the collection specification are recorded",
    "Timeliness by supplier is measured and reported",
    "NHS number validity is checked where linkage is planned"
   ],
   "refs": [
    "RB-CLD",
    "RB-ASCOF",
    "RB-CDM",
    "RB-CIN"
   ]
  },
  {
   "id": "SUP-GEO",
   "dd": "DD-03",
   "title": "Geospatial and address data",
   "icon": "map",
   "summary": "For assets that hold addresses, coordinates or map geometry. Adds geospatial metadata, open identifiers and positional quality.",
   "gov": [
    "Record the licence for any third-party geospatial data the asset depends on, and who may use derived data.",
    "Use the open identifiers for property and street (UPRN and USRN) as the join between assets.",
    "Apply the Geospatial Commission's guidance on ethical use of location data when location could identify people."
   ],
   "cat": [
    {
     "prop": "spatial",
     "term": "dcterms:spatial",
     "rule": "The area covered, by GSS code or bounding box"
    },
    {
     "prop": "crs",
     "term": "local extension (GEMINI spatial reference system)",
     "rule": "The coordinate reference system, for example British National Grid (EPSG:27700)"
    },
    {
     "prop": "lineage",
     "term": "dcterms:provenance",
     "rule": "How the geometry was captured and processed"
    },
    {
     "prop": "conformsTo",
     "term": "dcterms:conformsTo",
     "rule": "UK GEMINI where the asset is geospatial"
    }
   ],
   "rules": [
    {
     "id": "GEO-01",
     "element": "UPRN",
     "rule": "UPRN is recorded",
     "dimension": "completeness",
     "check": "not_null",
     "params": {
      "column": "uprn"
     }
    },
    {
     "id": "GEO-02",
     "element": "UPRN",
     "rule": "UPRN is 1 to 12 digits",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "uprn",
      "scheme": "uprn"
     }
    },
    {
     "id": "GEO-03",
     "element": "Postcode",
     "rule": "Postcode is in Royal Mail format",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "postcode",
      "scheme": "uk_postcode"
     }
    },
    {
     "id": "GEO-04",
     "element": "Easting",
     "rule": "Easting is within the British National Grid range",
     "dimension": "validity",
     "check": "range",
     "params": {
      "column": "easting",
      "min": 0,
      "max": 700000
     }
    },
    {
     "id": "GEO-05",
     "element": "Northing",
     "rule": "Northing is within the British National Grid range",
     "dimension": "validity",
     "check": "range",
     "params": {
      "column": "northing",
      "min": 0,
      "max": 1300000
     }
    },
    {
     "id": "GEO-06",
     "element": "Area code",
     "rule": "Area code is a GSS code",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "area_code",
      "scheme": "gss_code"
     }
    }
   ],
   "identifiers": [
    {
     "name": "UPRN",
     "format": "Unique property reference number, up to 12 digits",
     "prov": "K"
    },
    {
     "name": "USRN",
     "format": "Unique street reference number, up to 8 digits",
     "prov": "K"
    },
    {
     "name": "GSS code",
     "format": "One letter followed by 8 digits",
     "prov": "K"
    }
   ],
   "example": "Illustrative, synthetic: a register of public buildings. GEO-02 passes but 6% of UPRNs do not match the address base used by the receiving department; the owner logs a consistency issue and agrees a match-rate target.",
   "risks": [
    "A valid UPRN format does not prove the property exists or is the right one; check match rates against the authoritative address base.",
    "Coordinates in mixed reference systems silently misplace features.",
    "Small-area location data can identify people even when names are removed."
   ],
   "checklist": [
    "UPRN and USRN are used as join keys where they exist",
    "The coordinate reference system and lineage are on the catalogue record",
    "Positional checks and match rates are in the DQAP",
    "Licences for third-party geospatial inputs are recorded"
   ],
   "refs": [
    "RB-UPRN",
    "RB-GEMINI",
    "RB-QFAIR",
    "RB-GEOBP"
   ]
  },
  {
   "id": "SUP-STA",
   "dd": "DD-04",
   "title": "Official statistics and administrative sources",
   "icon": "chart-column",
   "summary": "For assets used to produce official statistics. Joins the DQAP to quality assurance of administrative data, so quality is reported once for both purposes.",
   "gov": [
    "Record the statistics produced from the asset and the producer responsible for them.",
    "Agree with the statistics producer how supplier changes are communicated before they happen.",
    "Use the DQAP as evidence for the assurance level set under quality assurance of administrative data."
   ],
   "cat": [
    {
     "prop": "isReferencedBy",
     "term": "dcterms:isReferencedBy",
     "rule": "The official statistics that use the asset"
    },
    {
     "prop": "conformsTo",
     "term": "dcterms:conformsTo",
     "rule": "SDMX structure or statistical classification used, where one applies"
    }
   ],
   "rules": [
    {
     "id": "STA-01",
     "element": "Reference period",
     "rule": "Reference period is complete with no missing months",
     "dimension": "completeness",
     "check": "no_gaps",
     "params": {
      "column": "period"
     }
    },
    {
     "id": "STA-02",
     "element": "Counts",
     "rule": "Monthly totals are not implausible outliers",
     "dimension": "accuracy",
     "check": "outlier",
     "params": {
      "column": "total",
      "method": "iqr",
      "k": 3
     }
    },
    {
     "id": "STA-03",
     "element": "Geography",
     "rule": "Area codes are valid GSS codes",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "area_code",
      "scheme": "gss_code"
     }
    },
    {
     "id": "STA-04",
     "element": "Units",
     "rule": "Every measure column names its unit",
     "dimension": "consistency",
     "check": "header_has_unit",
     "params": {}
    }
   ],
   "identifiers": [
    {
     "name": "GSS code",
     "format": "One letter followed by 8 digits",
     "prov": "K"
    }
   ],
   "example": "Illustrative, synthetic: an administrative benefits extract used for quarterly statistics. STA-02 flags a sudden fall in one month that turns out to be a supplier system change; it is logged as a known issue in both the DQAP and the statistical release.",
   "risks": [
    "Operational changes in the supplier's system can look like real-world change.",
    "Two quality reports for the same data drift apart unless one feeds the other."
   ],
   "checklist": [
    "Statistics that depend on the asset are recorded on the catalogue record",
    "A supplier change notice process is agreed",
    "DQAP results are used as evidence for administrative data quality assurance"
   ],
   "refs": [
    "RB-COP",
    "RB-QAAD",
    "RB-SDMX"
   ]
  },
  {
   "id": "SUP-SHR",
   "dd": "DD-05",
   "title": "Data sharing and legal gateways",
   "icon": "share-2",
   "summary": "For every critical data asset that includes personal data, because critical data assets are defined by being shared. Adds a legal gateway record to the governance and catalogue records.",
   "gov": [
    "Keep a sharing decision record for each flow: purpose, lawful basis, any special category condition, legal power or gateway, DPIA reference, agreement reference and review date.",
    "Check each flow against the Data (Use and Access) Act 2025 changes to UK GDPR at the next review.",
    "Use a data sharing agreement for routine sharing, as the ICO code recommends, even where it is not mandatory.",
    "Name the owner on both sides of every flow, by role.",
    "If the flow uses a Part 5 power in the Digital Economy Act 2017, check the agreement is on the published register.",
    "Record the agreement with the data sharing agreement template (T-GOV-6), and name the legal gateway in it and in the catalogue record."
   ],
   "cat": [
    {
     "prop": "accessRights",
     "term": "dcterms:accessRights",
     "rule": "Restricted, with the agreement reference"
    },
    {
     "prop": "legalGateway",
     "term": "local extension",
     "rule": "The statutory power or legal basis for the flow"
    },
    {
     "prop": "rights",
     "term": "dcterms:rights",
     "rule": "Conditions on onward sharing and use"
    }
   ],
   "rules": [
    {
     "id": "SHR-01",
     "element": "Agreement reference",
     "rule": "Every shared extract carries the agreement reference",
     "dimension": "completeness",
     "check": "not_null",
     "params": {
      "column": "agreement_ref"
     }
    },
    {
     "id": "SHR-02",
     "element": "Extract date",
     "rule": "Extracts arrive on the agreed schedule",
     "dimension": "timeliness",
     "check": "freshness",
     "params": {
      "column": "extract_date",
      "expected": "P1M",
      "lag": "P7D"
     }
    },
    {
     "id": "SHR-03",
     "element": "Columns",
     "rule": "Only the columns in the agreement are present",
     "dimension": "validity",
     "check": "required_columns",
     "params": {
      "columns": [
       "person_id",
       "agreement_ref",
       "extract_date"
      ]
     }
    }
   ],
   "identifiers": [],
   "example": "Illustrative, synthetic: a monthly flow of eligibility data between two departments. The sharing decision record names the gateway, the DPIA and the agreement; SHR-03 fails when an extra free-text column appears, which is fixed at source before the next transfer.",
   "risks": [
    "Extra fields creep into extracts over time, beyond what the agreement allows.",
    "Lawful basis recorded once at the start of a flow can go out of date when the law or the purpose changes."
   ],
   "checklist": [
    "A sharing decision record exists for each flow, with a review date",
    "Agreement references appear on the catalogue record and in each extract",
    "Flows were reviewed against the Data (Use and Access) Act 2025 changes"
   ],
   "refs": [
    "RB-DUAA",
    "RB-DEA",
    "RB-DEAREG",
    "RB-ICOSHARE",
    "RB-ICODSA",
    "RB-DPA",
    "RB-S251"
   ]
  },
  {
   "id": "SUP-AI",
   "dd": "DD-06",
   "title": "AI-ready data",
   "icon": "brain",
   "summary": "For assets used, or likely to be used, for AI or automated decision support. Turns the GOV.UK AI-ready data guidance into checks at the annual review.",
   "gov": [
    "Record the AI task the data supports, whether outputs affect individuals, and which uses are out of scope, such as automated decisions.",
    "Name the owner who approves AI uses, and decide what happens if a use changes.",
    "Publish an algorithmic transparency record where a tool supports decisions about people.",
    "Use the Data and AI Ethics Framework for new or higher-risk uses."
   ],
   "cat": [
    {
     "prop": "aiPermittedUses",
     "term": "local extension",
     "rule": "Training, fine-tuning, inference or evaluation: which are allowed"
    },
    {
     "prop": "sensitiveFields",
     "term": "local extension",
     "rule": "Fields that are personal, confidential or special category"
    },
    {
     "prop": "provenance",
     "term": "dcterms:provenance",
     "rule": "Where the data comes from and how it is produced"
    },
    {
     "prop": "version",
     "term": "dcat:version",
     "rule": "Version, so a training set can be reconstructed exactly"
    }
   ],
   "rules": [
    {
     "id": "AI-01",
     "element": "Label",
     "rule": "Training labels are complete",
     "dimension": "completeness",
     "check": "not_null",
     "params": {
      "column": "label"
     }
    },
    {
     "id": "AI-02",
     "element": "Label by group",
     "rule": "Label completeness does not differ by more than 5 points between groups",
     "dimension": "completeness",
     "check": "group_disparity",
     "params": {
      "group": "group",
      "tolerance": 5,
      "inner": {
       "check": "not_null",
       "column": "label"
      }
     }
    },
    {
     "id": "AI-03",
     "element": "Record",
     "rule": "Each record appears once, so training and test sets do not overlap",
     "dimension": "uniqueness",
     "check": "unique",
     "params": {
      "columns": [
       "record_id"
      ]
     }
    },
    {
     "id": "AI-04",
     "element": "Features",
     "rule": "Numeric features have no implausible outliers",
     "dimension": "accuracy",
     "check": "outlier",
     "params": {
      "column": "feature_value",
      "method": "zscore",
      "threshold": 4
     }
    }
   ],
   "identifiers": [],
   "checks_from_guidance": [
    {
     "area": "Purpose and legitimacy",
     "items": [
      "The task the data supports is known",
      "It is known whether outputs affect individuals",
      "Out-of-scope uses are stated",
      "A named owner approves AI uses"
     ]
    },
    {
     "area": "Legal, rights and governance",
     "items": [
      "Permitted uses (training, fine-tuning, inference, evaluation) are known",
      "Sensitive fields are flagged",
      "Permitted working environments are known",
      "There is a plan if the use case changes"
     ]
    },
    {
     "area": "Metadata fitness",
     "items": [
      "Tables and fields are understood",
      "Event time, update frequency and history are clear",
      "Schema changes and versions are tracked",
      "Provenance is known",
      "Known issues and biases are documented",
      "Stable identifiers exist or their absence is stated"
     ]
    },
    {
     "area": "Unstructured data pipelines",
     "items": [
      "Data is machine readable or has an extraction pipeline",
      "Rights, redaction and sensitivity travel with extracted content",
      "Outputs can be traced back to source files",
      "Humans review training data and outputs"
     ]
    },
    {
     "area": "Operating model and sustainability",
     "items": [
      "Someone owns quality, drift and bias monitoring",
      "Breaks, drift and anomalies are detected",
      "Fixes are re-approved",
      "Training sets can be reconstructed exactly",
      "There is a process if AI causes service, cost or trust issues"
     ]
    }
   ],
   "example": "Illustrative, synthetic: a casework text archive proposed for a summarisation tool. The review finds redaction does not travel with extracted text, so the asset is marked not yet AI-ready and a pipeline fix is added to the DQAP.",
   "risks": [
    "Open or available data is not the same as AI-ready data.",
    "Bias in labels or coverage becomes bias in outputs.",
    "Without exact versioning, a model cannot be retrained or audited."
   ],
   "checklist": [
    "AI permitted uses and sensitive fields are on the catalogue record",
    "The five areas of the GOV.UK self-assessment are reviewed at the annual review",
    "Group disparity rules are in the DQAP",
    "A transparency record is published where a tool supports decisions about people"
   ],
   "refs": [
    "RB-AIREADY",
    "RB-ATRS",
    "RB-AIPLAY",
    "RB-ETH"
   ]
  },
  {
   "id": "SUP-FRD",
   "dd": "DD-07",
   "title": "Fraud and error",
   "icon": "crosshair",
   "summary": "For assets used to detect fraud or error, where identity matching quality decides who is flagged.",
   "gov": [
    "Require a person to review every automated flag before action is taken against someone.",
    "Record the legal power used for each fraud data flow.",
    "Measure and report false positives, not only detections."
   ],
   "cat": [
    {
     "prop": "purpose",
     "term": "local extension (one of the seven purposes)",
     "rule": "Fraud and error"
    },
    {
     "prop": "matchingMethod",
     "term": "local extension",
     "rule": "How records are matched, and the known match error rate"
    }
   ],
   "rules": [
    {
     "id": "FRD-01",
     "element": "National Insurance number",
     "rule": "National Insurance number is in a valid format",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "nino",
      "scheme": "nino"
     }
    },
    {
     "id": "FRD-02",
     "element": "Person",
     "rule": "Each person appears once in the matching base",
     "dimension": "uniqueness",
     "check": "unique",
     "params": {
      "columns": [
       "person_id"
      ]
     }
    },
    {
     "id": "FRD-03",
     "element": "Date of birth",
     "rule": "Date of birth is recorded, so matches are not made on name alone",
     "dimension": "completeness",
     "check": "not_null",
     "params": {
      "column": "date_of_birth"
     }
    }
   ],
   "identifiers": [
    {
     "name": "National Insurance number",
     "format": "Two letters, six digits and a letter A to D, with some prefixes not used",
     "prov": "K"
    }
   ],
   "example": "Illustrative, synthetic: a matching exercise between benefit and payroll data. FRD-03 shows date of birth missing for 4% of records; those records are excluded from automated matching and routed to manual review.",
   "risks": [
    "Poor identity data produces false positives that fall on real people.",
    "Names transliterated differently can be missed or mismatched, affecting some communities more than others."
   ],
   "checklist": [
    "Human review of flags is required and recorded",
    "False positive rates are measured",
    "Identity field validity rules are in the DQAP"
   ],
   "refs": [
    "RB-PSFA",
    "RB-DEA"
   ]
  },
  {
   "id": "SUP-JUS",
   "dd": "DD-08",
   "title": "Justice, policing and national security",
   "icon": "lock-keyhole",
   "summary": "For assets in law enforcement, justice, defence or security settings, where only OFFICIAL assets are in scope and metadata itself may be sensitive.",
   "gov": [
    "Confirm the classification of the asset and of its metadata; only OFFICIAL assets are in scope of the policy.",
    "Record whether processing falls under Part 3 of the Data Protection Act 2018 (law enforcement processing).",
    "Restrict catalogue record visibility where the description itself is sensitive, and record the handling marking."
   ],
   "cat": [
    {
     "prop": "securityClassification",
     "term": "local extension (MEM securityClassification)",
     "rule": "OFFICIAL, with any handling marking such as OFFICIAL-SENSITIVE"
    },
    {
     "prop": "accessRights",
     "term": "dcterms:accessRights",
     "rule": "Internal, with the vetting level needed to access the data"
    }
   ],
   "rules": [
    {
     "id": "JUS-01",
     "element": "Classification",
     "rule": "Every record carries a classification marking from the allowed list",
     "dimension": "validity",
     "check": "in_set",
     "params": {
      "column": "classification",
      "values": [
       "OFFICIAL",
       "OFFICIAL-SENSITIVE"
      ]
     }
    },
    {
     "id": "JUS-02",
     "element": "Event date",
     "rule": "Event dates are not in the future",
     "dimension": "validity",
     "check": "not_future",
     "params": {
      "column": "event_date"
     }
    }
   ],
   "identifiers": [],
   "example": "Illustrative, synthetic: a court listings data asset. The catalogue record is visible across government, but the distribution is restricted, and JUS-01 confirms no records carry a higher marking.",
   "risks": [
    "Describing an asset in detail can reveal sensitive capabilities.",
    "Assets above OFFICIAL must not be described in this portal or reported through it."
   ],
   "checklist": [
    "Classification of the asset and its metadata is confirmed",
    "Part 3 processing is identified where it applies",
    "Catalogue record visibility matches the sensitivity of the description"
   ],
   "refs": [
    "RB-DPA",
    "RB-GSC"
   ]
  },
  {
   "id": "SUP-PER",
   "dd": "DD-09",
   "title": "Data about people",
   "icon": "users-round",
   "summary": "For any asset that holds records about individual people. Makes sure forms and rules let people describe themselves accurately.",
   "gov": [
    "Collect only the personal fields the purpose needs, and record why each is needed.",
    "Follow current statistical guidance for questions about sex and gender, ethnicity and disability, and offer 'prefer not to say'.",
    "Watch for the cross-government person data and vulnerability data standards and adopt them when published."
   ],
   "cat": [
    {
     "prop": "personalData",
     "term": "local extension",
     "rule": "Whether the asset holds personal or special category data"
    },
    {
     "prop": "population",
     "term": "local extension",
     "rule": "Who the records describe, and known gaps in coverage"
    }
   ],
   "rules": [
    {
     "id": "PER-01",
     "element": "Name",
     "rule": "Family name is recorded",
     "dimension": "completeness",
     "check": "not_null",
     "params": {
      "column": "family_name"
     }
    },
    {
     "id": "PER-02",
     "element": "Date of birth",
     "rule": "Date of birth is not in the future",
     "dimension": "validity",
     "check": "not_future",
     "params": {
      "column": "date_of_birth"
     }
    },
    {
     "id": "PER-03",
     "element": "Person",
     "rule": "Each person is recorded once",
     "dimension": "uniqueness",
     "check": "unique",
     "params": {
      "columns": [
       "person_id"
      ]
     }
    },
    {
     "id": "PER-04",
     "element": "Ethnicity",
     "rule": "Ethnicity is not unknown, where it is lawfully collected",
     "dimension": "completeness",
     "check": "not_unknown",
     "params": {
      "column": "ethnicity"
     }
    }
   ],
   "identifiers": [],
   "example": "Illustrative, synthetic: a customer contact data set. PER-01 fails for records from a form that forced a single name field; the fix is to change the form, not to clean the data.",
   "risks": [
    "Forms that cannot record names, addresses or identities accurately create bias at source.",
    "Completeness that looks good overall can hide gaps for some groups."
   ],
   "checklist": [
    "Each personal field has a recorded purpose",
    "Forms allow 'prefer not to say' and names in full",
    "Completeness is broken down by group where lawful"
   ],
   "refs": [
    "RB-PSED",
    "RB-EQA",
    "RB-DPA"
   ]
  },
  {
   "id": "SUP-REF",
   "dd": "DD-10",
   "title": "Reference data and identifiers",
   "icon": "tag",
   "summary": "For assets that depend on code lists and identifiers maintained by other organisations, such as area codes, organisation codes and company numbers.",
   "gov": [
    "Name the authoritative source and owner of each code list the asset uses.",
    "Record the version of each code list and how changes are picked up.",
    "Prefer recommended open standards for identifiers."
   ],
   "cat": [
    {
     "prop": "conformsTo",
     "term": "dcterms:conformsTo",
     "rule": "Each code list and its version"
    }
   ],
   "rules": [
    {
     "id": "REF-01",
     "element": "Area code",
     "rule": "Area code is a GSS code",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "area_code",
      "scheme": "gss_code"
     }
    },
    {
     "id": "REF-02",
     "element": "Company number",
     "rule": "Company number is in Companies House format",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "company_number",
      "scheme": "company_number"
     }
    },
    {
     "id": "REF-03",
     "element": "Legal entity identifier",
     "rule": "LEI is valid, including its check digits",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "lei",
      "scheme": "lei"
     }
    },
    {
     "id": "REF-04",
     "element": "Charity number",
     "rule": "Charity number is in a valid format",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "charity_number",
      "scheme": "charity_number"
     }
    }
   ],
   "identifiers": [
    {
     "name": "Company number",
     "format": "8 digits, or 2 letters and 6 digits",
     "prov": "K"
    },
    {
     "name": "LEI",
     "format": "20 characters with 2 check digits (ISO 17442)",
     "prov": "K"
    }
   ],
   "example": "Illustrative, synthetic: a grants register. REF-01 fails after a boundary change because the code list was not updated; the fix is to subscribe to the code list's change notices.",
   "risks": [
    "Code lists change; stale codes pass format checks but point to retired areas or organisations."
   ],
   "checklist": [
    "Every code list has a named source and version",
    "Changes to code lists are picked up on a schedule"
   ],
   "refs": [
    "RB-OPEN",
    "RB-UPRN"
   ]
  },
  {
   "id": "SUP-REC",
   "dd": "DD-11",
   "title": "Records, retention and disposal",
   "icon": "calendar-clock",
   "summary": "For every critical data asset that must be kept, archived or destroyed on a schedule. Joins data asset management to records management.",
   "gov": [
    "Record the retention schedule and disposal action for each asset in the ownership register.",
    "Agree with the records manager when an asset is retired, archived or transferred.",
    "Keep catalogue records for retired assets, marked as retired, so dependants can see what changed.",
    "When an asset needs to be kept longer than its schedule allows, record the reason and who approved it in the exception register (T-GOV-4), with a review date."
   ],
   "cat": [
    {
     "prop": "retention",
     "term": "local extension",
     "rule": "Retention period and disposal action"
    },
    {
     "prop": "isReplacedBy",
     "term": "dcterms:isReplacedBy",
     "rule": "What replaces a retired asset"
    }
   ],
   "rules": [
    {
     "id": "REC-01",
     "element": "Record date",
     "rule": "Records are not older than the retention period in your schedule (this example uses 7 years)",
     "dimension": "timeliness",
     "check": "freshness",
     "params": {
      "column": "created_date",
      "expected": "P7Y",
      "lag": "P30D"
     }
    }
   ],
   "identifiers": [],
   "example": "Illustrative, synthetic: a case management extract kept for seven years. REC-01 flags records past retention, which the owner agrees to dispose of through the records management process.",
   "risks": [
    "Data kept past its retention period is a data protection risk; data destroyed early is a records risk.",
    "There is no single government-wide retention period. The National Archives describes short, medium and long periods and each organisation sets its own schedule, so check yours before using an example such as seven years."
   ],
   "checklist": [
    "Retention and disposal are on the ownership register",
    "Retired assets keep a marked catalogue record",
    "The retention fields in the ownership register (T-GOV-2) and catalogue record (T-CAT-2) are filled in from your organisation's schedule"
   ],
   "refs": [
    "RB-TNA",
    "RB-TNARET",
    "RB-TNAIM",
    "RB-PRA"
   ]
  },
  {
   "id": "SUP-ARC",
   "dd": "DD-15",
   "title": "Data architecture and models",
   "icon": "network",
   "summary": "For critical data assets whose structure others build on. Describes the entities, how they relate and which system is the authoritative source, and links them to the catalogue.",
   "gov": [
    "Name the authoritative source for each entity, and the role that approves changes to its structure (the design authority in a change programme).",
    "Keep the entity and relationship list (T-CAT-4) with the asset, and review it when the data model changes."
   ],
   "cat": [
    {
     "prop": "conformsTo",
     "term": "dcterms:conformsTo",
     "rule": "Link to the published schema or data model"
    },
    {
     "prop": "dataModel",
     "term": "local extension",
     "rule": "Link to the entity and relationship list or diagram"
    }
   ],
   "rules": [
    {
     "id": "ARC-01",
     "element": "Entity key",
     "rule": "Each entity's key is unique",
     "dimension": "uniqueness",
     "check": "unique",
     "params": {
      "column": "entity_id"
     }
    }
   ],
   "identifiers": [],
   "example": "Illustrative, synthetic: a case management asset with people, cases, appointments and outcomes. The worked entity and relationship list and the diagram drawn from it are with the entity and relationship list template (T-CAT-4); ARC-01 checks each entity key is unique.",
   "risks": [
    "Without an agreed authoritative source, two systems can each claim to be the master copy, and returns count assets twice.",
    "Diagrams drawn by hand drift from the real model; keep the list as the source and draw the diagram from it."
   ],
   "checklist": [
    "Every entity has a key, a description and an authoritative source",
    "Relationships state their cardinality",
    "The catalogue record links to the list or diagram"
   ],
   "refs": [
    "RB-DCATGOV"
   ]
  },
  {
   "id": "SUP-DEV",
   "dd": "DD-12",
   "title": "Devolved governments and local government",
   "icon": "landmark",
   "summary": "For assets that flow to or from the devolved governments or councils, which are not bound by the policy but often depend on it.",
   "gov": [
    "Record which nations the asset covers and which bodies supply or receive it.",
    "Where a devolved government or council supplies data, agree quality expectations in the sharing agreement, because the policy does not bind them.",
    "Offer councils the playbooks as a voluntary route to adoption."
   ],
   "cat": [
    {
     "prop": "spatial",
     "term": "dcterms:spatial",
     "rule": "Nations covered, using GSS codes (England E, Scotland S, Wales W, Northern Ireland N)"
    },
    {
     "prop": "language",
     "term": "dcterms:language",
     "rule": "Languages of the data and documentation, including Welsh where it applies"
    }
   ],
   "rules": [
    {
     "id": "DEV-01",
     "element": "Nation",
     "rule": "Nation is recorded from the allowed list",
     "dimension": "validity",
     "check": "in_set",
     "params": {
      "column": "nation",
      "values": [
       "England",
       "Scotland",
       "Wales",
       "Northern Ireland"
      ]
     }
    },
    {
     "id": "DEV-02",
     "element": "Area code",
     "rule": "Area code is a GSS code",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "area_code",
      "scheme": "gss_code"
     }
    }
   ],
   "identifiers": [],
   "four_nations": [
    {
     "nation": "UK government departments and ALBs",
     "position": "Mandatory under the DAM Policy",
     "prov": "V"
    },
    {
     "nation": "Scotland",
     "position": "Not bound by the policy; own approach to data sharing governance",
     "prov": "V"
    },
    {
     "nation": "Wales",
     "position": "Not bound by the policy; own approach to data sharing governance",
     "prov": "V"
    },
    {
     "nation": "Northern Ireland",
     "position": "Not bound by the policy; own approach to data sharing governance",
     "prov": "V"
    },
    {
     "nation": "Councils",
     "position": "Not required; may adopt voluntarily",
     "prov": "V"
    }
   ],
   "example": "Illustrative, synthetic: a UK-wide dataset assembled from four national returns. DEV-01 shows records from one nation coded inconsistently; the fix is agreed with that nation's data team.",
   "risks": [
    "Presenting England-only rules as UK-wide misleads users in other nations.",
    "Differences in definitions between nations break comparability."
   ],
   "checklist": [
    "Nations covered are on the catalogue record",
    "Quality expectations for devolved or council suppliers are in the agreement"
   ],
   "refs": [
    "RB-LDD"
   ]
  },
  {
   "id": "SUP-ENV",
   "dd": "DD-13",
   "title": "Environmental, sensor and time-series data",
   "icon": "activity",
   "summary": "For monitoring and sensor data where readings arrive continuously and gaps, units and drift matter more than missing fields.",
   "gov": [
    "Name who owns calibration of instruments as well as who owns the data.",
    "Record how gaps and suspect readings are flagged and whether they are corrected."
   ],
   "cat": [
    {
     "prop": "temporalResolution",
     "term": "dcat:temporalResolution",
     "rule": "The interval between readings"
    },
    {
     "prop": "spatial",
     "term": "dcterms:spatial",
     "rule": "Monitoring sites and their locations"
    }
   ],
   "rules": [
    {
     "id": "ENV-01",
     "element": "Timestamp",
     "rule": "No gaps in the expected reading interval",
     "dimension": "completeness",
     "check": "no_gaps",
     "params": {
      "column": "reading_time"
     }
    },
    {
     "id": "ENV-02",
     "element": "Units",
     "rule": "Every measure column names its unit",
     "dimension": "consistency",
     "check": "header_has_unit",
     "params": {}
    },
    {
     "id": "ENV-03",
     "element": "Reading",
     "rule": "Readings have no implausible outliers",
     "dimension": "accuracy",
     "check": "outlier",
     "params": {
      "column": "value",
      "method": "iqr",
      "k": 3
     }
    }
   ],
   "identifiers": [],
   "example": "Illustrative, synthetic: river level readings every 15 minutes. ENV-01 finds a six-hour gap from a failed sensor; the gap is flagged, not filled, in the published data.",
   "risks": [
    "Filling gaps silently makes data look complete when it is not.",
    "Sensor drift passes format checks; it needs calibration records."
   ],
   "checklist": [
    "Reading interval and units are on the catalogue record",
    "Gaps and outliers are flagged, not silently corrected"
   ],
   "refs": [
    "RB-GEOBP",
    "RB-DCAT"
   ]
  },
  {
   "id": "SUP-EDU",
   "dd": "DD-14",
   "title": "Pupil and learner data",
   "icon": "graduation-cap",
   "summary": "For assets about pupils and learners, which are long-lived and linked across schools, colleges and nations.",
   "gov": [
    "Record the collection the data comes from and its specification version.",
    "Treat records about children with the extra care data protection law expects."
   ],
   "cat": [
    {
     "prop": "conformsTo",
     "term": "dcterms:conformsTo",
     "rule": "The census or collection specification and version"
    }
   ],
   "rules": [
    {
     "id": "EDU-01",
     "element": "School",
     "rule": "School unique reference number is 6 digits",
     "dimension": "validity",
     "check": "identifier",
     "params": {
      "column": "school_urn",
      "scheme": "school_urn"
     }
    },
    {
     "id": "EDU-02",
     "element": "Pupil",
     "rule": "Each pupil appears once per census",
     "dimension": "uniqueness",
     "check": "unique",
     "params": {
      "columns": [
       "pupil_id",
       "census_date"
      ]
     }
    }
   ],
   "identifiers": [
    {
     "name": "School URN",
     "format": "6 digits",
     "prov": "K"
    }
   ],
   "example": "Illustrative, synthetic: a termly pupil census extract. EDU-02 finds duplicate pupils for dual-registered learners; the rule is refined to count the main registration only.",
   "risks": [
    "Dual registration and moves between schools create apparent duplicates."
   ],
   "checklist": [
    "The collection specification and version are recorded",
    "Duplicate and dual registration rules are agreed"
   ],
   "refs": [
    "RB-DPA"
   ]
  }
 ],
 "capmap": [
  {
   "id": "CR-01",
   "name": "Accountable leadership and policy oversight",
   "cluster": "Direction and oversight",
   "icon": "building-2",
   "flag": "E",
   "dam": "oversight-and-implementation-of-the-policy",
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "chief-data-officer",
     "label": "Chief data officer role",
     "flag": "E"
    },
    {
     "doc": "SRC-OWN",
     "a": "executive-leadership-roles",
     "label": "Executive leadership roles",
     "flag": "E"
    }
   ],
   "playbook": "governance.html",
   "dma": [
    9,
    10
   ],
   "dmbok": [
    "Data governance"
   ],
   "dcam": [
    "Data management strategy and business case",
    "Data governance"
   ],
   "skills": [
    "data-governance-leadership",
    "strategic-data-planning"
   ],
   "profs": [
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "Each organisation's chief data officer is responsible for implementing the policy; the Chief Data Officer Council oversees it.",
   "prov": "O"
  },
  {
   "id": "CR-02",
   "name": "Data strategy and prioritisation by reuse value",
   "cluster": "Direction and oversight",
   "icon": "target",
   "flag": "I",
   "dam": "oversight-and-implementation-of-the-policy",
   "signposts": [
    {
     "doc": "SRC-DQAP",
     "a": "prioritise-your-dqaps",
     "label": "Prioritise your DQAPs",
     "flag": "E"
    },
    {
     "doc": "SRC-DAM",
     "a": "realising-our-data-ambitions",
     "label": "Realising our data ambitions",
     "flag": "I"
    }
   ],
   "playbook": "capabilities.html#CR-02",
   "dma": [
    9
   ],
   "dmbok": [
    "Data governance"
   ],
   "dcam": [
    "Data management strategy and business case"
   ],
   "skills": [
    "strategic-data-planning",
    "strategic-thinking"
   ],
   "profs": [
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "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.",
   "prov": "O"
  },
  {
   "id": "CR-03",
   "name": "Central reporting, assurance and arm's length body coordination",
   "cluster": "Direction and oversight",
   "icon": "send",
   "flag": "E",
   "dam": "identifying-and-reporting-data-assets",
   "signposts": [
    {
     "doc": "SRC-DAM",
     "a": "organisational-and-administrative-scope",
     "label": "Organisational and administrative scope",
     "flag": "E"
    },
    {
     "doc": "SRC-IDC",
     "a": "record-your-critical-data-assets",
     "label": "Record your critical data assets",
     "flag": "E"
    }
   ],
   "playbook": "cataloguing.html",
   "dma": [
    10
   ],
   "dmbok": [
    "Metadata management",
    "Data governance"
   ],
   "dcam": [
    "Data governance",
    "Data control environment"
   ],
   "skills": [
    "data-governance",
    "metadata-management"
   ],
   "profs": [
    "PR-DD",
    "PR-KIM"
   ],
   "coverage": "Covered",
   "note": "Departments report their assets to GDS and coordinate and assure the returns of their arm's length bodies.",
   "prov": "O"
  },
  {
   "id": "CR-04",
   "name": "Performance measurement and annual review",
   "cluster": "Direction and oversight",
   "icon": "chart-column",
   "flag": "E",
   "dam": "identifying-and-reporting-data-assets",
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "measuring-the-success-of-data-ownership-initiatives",
     "label": "Measuring the success of data ownership initiatives",
     "flag": "E"
    },
    {
     "doc": "SRC-DQAP",
     "a": "create-a-data-quality-dashboard",
     "label": "Create a data quality dashboard",
     "flag": "E"
    }
   ],
   "playbook": "together.html",
   "dma": [
    5,
    10
   ],
   "dmbok": [
    "Data governance",
    "Data quality",
    "Data warehousing and business intelligence"
   ],
   "dcam": [
    "Data governance",
    "Data quality management"
   ],
   "skills": [
    "performance-measurement",
    "data-maturity"
   ],
   "profs": [
    "PR-DD",
    "PR-AF"
   ],
   "coverage": "Partial",
   "note": "Returns must be maintained and reviewed every year; the guidance adds measures for ownership and quality.",
   "prov": "O"
  },
  {
   "id": "CR-05",
   "name": "Identify and scope critical data assets",
   "cluster": "Core DAM capabilities",
   "icon": "crosshair",
   "flag": "E",
   "dam": "data-assets-in-scope",
   "signposts": [
    {
     "doc": "SRC-IDC",
     "a": "identify-your-critical-data-assets",
     "label": "Identify your critical data assets",
     "flag": "E"
    },
    {
     "doc": "SRC-IDC",
     "a": "purposes-that-critical-data-assets-support",
     "label": "Purposes that critical data assets support",
     "flag": "E"
    },
    {
     "doc": "SRC-DAM",
     "a": "defining-a-data-asset",
     "label": "Defining a data asset",
     "flag": "E"
    }
   ],
   "playbook": "cataloguing.html",
   "dma": [
    4
   ],
   "dmbok": [
    "Metadata management",
    "Data governance"
   ],
   "dcam": [
    "Business and data architecture"
   ],
   "skills": [
    "data-management",
    "data-governance"
   ],
   "profs": [
    "PR-DD",
    "PR-KIM"
   ],
   "coverage": "Covered",
   "note": "Only assets classified OFFICIAL are in scope, and the critical-asset guidance defines which assets count.",
   "prov": "O"
  },
  {
   "id": "CR-06",
   "name": "Data cataloguing and metadata management",
   "cluster": "Core DAM capabilities",
   "icon": "library-big",
   "flag": "E",
   "dam": "identifying-and-reporting-data-assets",
   "signposts": [
    {
     "doc": "SRC-MD",
     "a": "where-to-record-and-store-your-metadata",
     "label": "Where to record and store your metadata",
     "flag": "E"
    },
    {
     "doc": "SRC-MD",
     "a": "metadata-you-should-record",
     "label": "Metadata you should record",
     "flag": "E"
    },
    {
     "doc": "SRC-MD",
     "a": "making-your-metadata-machine-readable-and-accessible",
     "label": "Making your metadata machine-readable",
     "flag": "E"
    },
    {
     "doc": "SRC-DQAP",
     "a": "build-a-data-catalogue",
     "label": "Build a data catalogue (inside the quality guide)",
     "flag": "I"
    }
   ],
   "playbook": "cataloguing.html",
   "dma": [
    4,
    7
   ],
   "dmbok": [
    "Metadata management"
   ],
   "dcam": [
    "Business and data architecture",
    "Data and technology architecture"
   ],
   "skills": [
    "metadata-management",
    "data-standards"
   ],
   "profs": [
    "PR-KIM",
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "Metadata about in-scope assets must be held in a data catalogue; the quality guide also assumes a catalogue exists.",
   "prov": "O"
  },
  {
   "id": "CR-07",
   "name": "Data ownership and stewardship",
   "cluster": "Core DAM capabilities",
   "icon": "key-round",
   "flag": "E",
   "dam": "data-ownership",
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "data-ownership-roles-and-responsibilities",
     "label": "Data ownership roles and responsibilities",
     "flag": "E"
    },
    {
     "doc": "SRC-OWN",
     "a": "a-checklist-for-your-organisation",
     "label": "A checklist for your organisation",
     "flag": "E"
    },
    {
     "doc": "SRC-OWN",
     "a": "the-relationship-between-data-ownership-and-information-asset-ownership",
     "label": "Data owners and information asset owners",
     "flag": "E"
    }
   ],
   "playbook": "governance.html",
   "dma": [
    10
   ],
   "dmbok": [
    "Data governance"
   ],
   "dcam": [
    "Data governance"
   ],
   "skills": [
    "data-governance",
    "stakeholder-relationship-management"
   ],
   "profs": [
    "PR-DD",
    "PR-KIM"
   ],
   "coverage": "Covered",
   "note": "Every identified asset must have a named data owner, as set out in the data ownership model.",
   "prov": "O"
  },
  {
   "id": "CR-08",
   "name": "Data quality management through action plans",
   "cluster": "Core DAM capabilities",
   "icon": "gauge",
   "flag": "E",
   "dam": "data-quality-action-plans",
   "signposts": [
    {
     "doc": "SRC-DQAP",
     "a": "step-1-identify-critical-data",
     "label": "The 7 DQAP steps",
     "flag": "E"
    },
    {
     "doc": "SRC-GDQF",
     "a": "Data-Quality-Principles",
     "label": "Data quality principles",
     "flag": "E"
    },
    {
     "doc": "SRC-DQIF",
     "a": "set-a-data-quality-target",
     "label": "Set a data quality target",
     "flag": "E"
    }
   ],
   "playbook": "quality.html",
   "dma": [
    7
   ],
   "dmbok": [
    "Data quality"
   ],
   "dcam": [
    "Data quality management"
   ],
   "skills": [
    "quality-assurance-of-data-and-analysis",
    "data-management"
   ],
   "profs": [
    "PR-AF",
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "Every identified asset must have a data quality action plan or an equivalent that covers all 7 steps.",
   "prov": "O"
  },
  {
   "id": "CR-09",
   "name": "Data quality issue management",
   "cluster": "Core DAM capabilities",
   "icon": "triangle-alert",
   "flag": "I",
   "dam": "data-quality-action-plans",
   "signposts": [
    {
     "doc": "SRC-DQIF",
     "a": "assign-a-priority-to-a-data-quality-issue",
     "label": "Assign a priority to an issue",
     "flag": "E"
    },
    {
     "doc": "SRC-DQIF",
     "a": "allocate-time-and-resources",
     "label": "Allocate time and resources",
     "flag": "E"
    },
    {
     "doc": "SRC-DQAP",
     "a": "identify-and-log-data-quality-issues",
     "label": "Identify and log issues",
     "flag": "E"
    }
   ],
   "playbook": "quality.html",
   "dma": [
    7
   ],
   "dmbok": [
    "Data quality"
   ],
   "dcam": [
    "Data quality management"
   ],
   "skills": [
    "problem-management",
    "quality-assurance-of-data-and-analysis"
   ],
   "profs": [
    "PR-AF"
   ],
   "coverage": "Covered",
   "note": "The policy points to the issues framework to support resource decisions; logging and prioritising issues is how plans turn into action.",
   "prov": "O"
  },
  {
   "id": "CR-10",
   "name": "Data life cycle management",
   "cluster": "Data management enablers",
   "icon": "refresh-cw",
   "flag": "E",
   "dam": "realising-our-data-ambitions",
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "data-is-managed-throughout-its-life-cycle",
     "label": "Data is managed throughout its life cycle",
     "flag": "E"
    },
    {
     "doc": "SRC-GDQF",
     "a": "Assess-quality-throughout-the-data-lifecycle",
     "label": "Assess quality throughout the life cycle",
     "flag": "E"
    },
    {
     "doc": "SRC-DQAP",
     "a": "the-data-life-cycle",
     "label": "The data life cycle",
     "flag": "E"
    }
   ],
   "playbook": "together.html",
   "dma": [
    7
   ],
   "dmbok": [
    "Data governance",
    "Data storage and operations"
   ],
   "dcam": [
    "Data control environment"
   ],
   "skills": [
    "data-life-cycle"
   ],
   "profs": [
    "PR-DD",
    "PR-KIM"
   ],
   "coverage": "Partial",
   "note": "The policy sets out life cycle controls; the ownership model makes life cycle management a principle.",
   "prov": "O"
  },
  {
   "id": "CR-11",
   "name": "Interoperability, data standards and identifiers",
   "cluster": "Data management enablers",
   "icon": "ruler",
   "flag": "E",
   "dam": "realising-our-data-ambitions",
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "data-is-standardised",
     "label": "Data is standardised",
     "flag": "E"
    },
    {
     "doc": "SRC-MD",
     "a": "using-identifier",
     "label": "Using 'identifier'",
     "flag": "E"
    },
    {
     "doc": "RB-OPEN",
     "a": null,
     "label": "Open standards for government",
     "flag": "E"
    }
   ],
   "playbook": "sectors.html",
   "dma": [
    7,
    3
   ],
   "dmbok": [
    "Data integration and interoperability",
    "Reference and master data"
   ],
   "dcam": [
    "Data and technology architecture"
   ],
   "skills": [
    "data-standards",
    "data-integration-design"
   ],
   "profs": [
    "PR-DD"
   ],
   "coverage": "Partial",
   "note": "The policy sets minimum requirements for interoperability; standards and shared identifiers are how they are met.",
   "prov": "O"
  },
  {
   "id": "CR-12",
   "name": "Data architecture and data services",
   "cluster": "Data management enablers",
   "icon": "server",
   "flag": "I",
   "dam": "defining-a-data-asset",
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "data-platforms-and-services",
     "label": "Data platforms and services",
     "flag": "E"
    },
    {
     "doc": "SRC-OWN",
     "a": "merged-data-sets-and-data-services",
     "label": "Merged data sets and data services",
     "flag": "E"
    }
   ],
   "playbook": "areas.html#DM-ARC",
   "dma": [
    3
   ],
   "dmbok": [
    "Data architecture",
    "Data modelling and design"
   ],
   "dcam": [
    "Business and data architecture",
    "Data and technology architecture"
   ],
   "skills": [
    "data-architecture",
    "data-modelling"
   ],
   "profs": [
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "A data asset includes the data services (such as APIs) used to reach it, so someone must design and run those services.",
   "prov": "O"
  },
  {
   "id": "CR-13",
   "name": "Catalogue and quality tooling",
   "cluster": "Data management enablers",
   "icon": "wrench",
   "flag": "I",
   "dam": "identifying-and-reporting-data-assets",
   "signposts": [
    {
     "doc": "SRC-DQAP",
     "a": "automate-assessments",
     "label": "Automate assessments",
     "flag": "E"
    },
    {
     "doc": "RB-TCOP",
     "a": null,
     "label": "Technology Code of Practice",
     "flag": "E"
    }
   ],
   "playbook": "capabilities.html#CR-13",
   "dma": [
    3
   ],
   "dmbok": [
    "Metadata management",
    "Data quality"
   ],
   "dcam": [
    "Data and technology architecture"
   ],
   "skills": [
    "programming-and-build-data-and-analytics-engineering",
    "metadata-management"
   ],
   "profs": [
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "Catalogues and automated quality checks need platforms; GDS will build a central discovery service.",
   "prov": "O"
  },
  {
   "id": "CR-14",
   "name": "Reference data, master data and authoritative sources",
   "cluster": "Data management enablers",
   "icon": "badge-check",
   "flag": "I",
   "dam": null,
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "data-is-authoritative",
     "label": "Data is authoritative",
     "flag": "E"
    },
    {
     "doc": "SRC-OWN",
     "a": "process-owners-and-enterprise-data-owners",
     "label": "Process owners and enterprise data owners",
     "flag": "E"
    }
   ],
   "playbook": "sectors.html",
   "dma": [
    7
   ],
   "dmbok": [
    "Reference and master data"
   ],
   "dcam": [
    "Business and data architecture"
   ],
   "skills": [
    "data-management",
    "data-modelling"
   ],
   "profs": [
    "PR-DD"
   ],
   "coverage": "Partial",
   "note": "Reducing duplicate collection depends on agreeing which source is authoritative; the policy states the aim, the ownership model the principle.",
   "prov": "O"
  },
  {
   "id": "CR-15",
   "name": "Records, retention and disposal",
   "cluster": "Data management enablers",
   "icon": "archive",
   "flag": "N",
   "dam": null,
   "signposts": [
    {
     "doc": "RB-TNA",
     "a": null,
     "label": "The National Archives information management guidance",
     "flag": "E"
    },
    {
     "doc": "RB-RETIRE",
     "a": "protecting-information",
     "label": "Retiring your service: protecting information",
     "flag": "E"
    },
    {
     "doc": "SRC-OWN",
     "a": "data-ownership-in-context",
     "label": "Data ownership in context",
     "flag": "I"
    }
   ],
   "playbook": "areas.html#DM-DOC",
   "dma": [
    7,
    8
   ],
   "dmbok": [
    "Document and content management",
    "Data storage and operations"
   ],
   "dcam": [
    "Data control environment"
   ],
   "skills": [
    "data-life-cycle",
    "data-compliance-and-security"
   ],
   "profs": [
    "PR-KIM"
   ],
   "coverage": "Covered",
   "note": "Not mentioned in the policy, but an asset's life cycle ends in retention, transfer or disposal, which records law governs.",
   "prov": "O"
  },
  {
   "id": "CR-16",
   "name": "Security classification and protective controls",
   "cluster": "Protection, ethics and trust",
   "icon": "lock-keyhole",
   "flag": "E",
   "dam": "data-assets-in-scope",
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "data-is-secure",
     "label": "Data is secure",
     "flag": "E"
    },
    {
     "doc": "RB-GSC",
     "a": null,
     "label": "Government Security Classifications",
     "flag": "E"
    }
   ],
   "playbook": "sectors.html",
   "dma": [
    8
   ],
   "dmbok": [
    "Data security"
   ],
   "dcam": [
    "Data control environment"
   ],
   "skills": [
    "data-compliance-and-security",
    "data-risk-management"
   ],
   "profs": [
    "PR-SEC",
    "PR-CYB"
   ],
   "coverage": "Partial",
   "note": "Scope depends on classification (OFFICIAL only), so classification must be right before an asset is recorded.",
   "prov": "O"
  },
  {
   "id": "CR-17",
   "name": "Data protection and lawful sharing",
   "cluster": "Protection, ethics and trust",
   "icon": "scale",
   "flag": "E",
   "dam": "data-assets-in-scope",
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "data-protection-roles",
     "label": "Data protection roles",
     "flag": "E"
    },
    {
     "doc": "RB-DSGF",
     "a": null,
     "label": "Data Sharing Governance Framework",
     "flag": "E"
    },
    {
     "doc": "RB-ICOSHARE",
     "a": null,
     "label": "ICO data sharing code",
     "flag": "E"
    }
   ],
   "playbook": "sectors.html",
   "dma": [
    8,
    1
   ],
   "dmbok": [
    "Data security",
    "Data governance"
   ],
   "dcam": [
    "Data control environment"
   ],
   "skills": [
    "data-ethics-and-privacy",
    "data-compliance-and-security"
   ],
   "profs": [
    "PR-DD",
    "PR-KIM"
   ],
   "coverage": "Partial",
   "note": "The policy keeps every legal and data protection obligation in place and does not force sharing.",
   "prov": "O"
  },
  {
   "id": "CR-18",
   "name": "AI readiness and data and AI ethics",
   "cluster": "Protection, ethics and trust",
   "icon": "brain",
   "flag": "E",
   "dam": "data-quality-action-plans",
   "signposts": [
    {
     "doc": "RB-AIREADY",
     "a": null,
     "label": "Making government datasets ready for AI",
     "flag": "E"
    },
    {
     "doc": "RB-ETH",
     "a": null,
     "label": "Data and AI Ethics Framework",
     "flag": "E"
    },
    {
     "doc": "RB-ATRS",
     "a": null,
     "label": "Algorithmic Transparency Recording Standard",
     "flag": "E"
    }
   ],
   "playbook": "sectors.html",
   "dma": [
    6
   ],
   "dmbok": [
    "Data governance",
    "Data quality"
   ],
   "dcam": [
    "Analytics management"
   ],
   "skills": [
    "data-ethics-and-privacy",
    "analysis-and-synthesis-data-ethics"
   ],
   "profs": [
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "The policy names AI readiness as a reason for quality plans; ethics is not named, so it is inferred from the AI guidance.",
   "prov": "O"
  },
  {
   "id": "CR-19",
   "name": "Data risk management",
   "cluster": "Protection, ethics and trust",
   "icon": "shield-check",
   "flag": "E",
   "dam": "realising-our-data-ambitions",
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "board-level-executive-or-senior-information-risk-owner-siro",
     "label": "Senior information risk owner",
     "flag": "E"
    },
    {
     "doc": "RB-ORANGE",
     "a": null,
     "label": "The Orange Book",
     "flag": "E"
    }
   ],
   "playbook": "capabilities.html#CR-19",
   "dma": [
    8,
    10
   ],
   "dmbok": [
    "Data governance",
    "Data security"
   ],
   "dcam": [
    "Data control environment"
   ],
   "skills": [
    "data-risk-management",
    "enabling-and-informing-risk-based-decisions"
   ],
   "profs": [
    "PR-SEC",
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "The policy cites risk controls and understanding cross-public sector dependencies to manage risk; how is left to each organisation.",
   "prov": "O"
  },
  {
   "id": "CR-20",
   "name": "Third-party and supplier data",
   "cluster": "Protection, ethics and trust",
   "icon": "handshake",
   "flag": "I",
   "dam": null,
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "data-from-a-third-party",
     "label": "Data from a third party",
     "flag": "E"
    },
    {
     "doc": "SRC-OWN",
     "a": "data-licensing-impact-on-data-owners",
     "label": "Data licensing impact on data owners",
     "flag": "E"
    },
    {
     "doc": "RB-SOURCING",
     "a": null,
     "label": "The Sourcing Playbook",
     "flag": "E"
    }
   ],
   "playbook": "capabilities.html#CR-20",
   "dma": [
    1
   ],
   "dmbok": [
    "Data governance"
   ],
   "dcam": [
    "Data governance"
   ],
   "skills": [
    "stakeholder-relationship-management",
    "data-compliance-and-security"
   ],
   "profs": [
    "PR-COM",
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "Many critical assets are held or processed by suppliers; ownership, metadata and quality duties must reach into contracts.",
   "prov": "O"
  },
  {
   "id": "CR-21",
   "name": "Data skills, capability and literacy",
   "cluster": "People and culture",
   "icon": "graduation-cap",
   "flag": "I",
   "dam": null,
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "skills-that-data-owners-need",
     "label": "Skills that data owners need",
     "flag": "E"
    },
    {
     "doc": "SRC-DQAP",
     "a": "relevant-training-modules",
     "label": "Relevant training modules",
     "flag": "E"
    },
    {
     "doc": "SRC-GDQF",
     "a": "build-data-quality-capability",
     "label": "Build data quality capability",
     "flag": "E"
    }
   ],
   "playbook": "capabilities.html#CR-21",
   "dma": [
    2
   ],
   "dmbok": [
    "Data governance"
   ],
   "dcam": [
    "Data management program and funding"
   ],
   "skills": [
    "data-literacy-improvement",
    "capability-building-for-digital-data-and-technology"
   ],
   "profs": [
    "PR-DD",
    "PR-AF",
    "PR-KIM"
   ],
   "coverage": "Covered",
   "note": "The policy assigns new responsibilities; the guidance lists the skills and training those people need.",
   "prov": "O"
  },
  {
   "id": "CR-22",
   "name": "Data culture and engagement with users",
   "cluster": "People and culture",
   "icon": "heart-handshake",
   "flag": "I",
   "dam": null,
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "promoting-and-ensuring-a-culture-of-data-ownership-within-the-organisation",
     "label": "Promoting a culture of data ownership",
     "flag": "E"
    },
    {
     "doc": "SRC-GDQF",
     "a": "Know-your-users-and-their-needs",
     "label": "Know your users and their needs",
     "flag": "E"
    }
   ],
   "playbook": "capabilities.html#CR-22",
   "dma": [
    1
   ],
   "dmbok": [
    "Data governance"
   ],
   "dcam": [
    "Data governance"
   ],
   "skills": [
    "stakeholder-relationship-management",
    "communicating-between-the-technical-and-non-technical"
   ],
   "profs": [
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "Ownership and quality only last where people value data and know who uses it.",
   "prov": "O"
  },
  {
   "id": "CR-23",
   "name": "Maturity assessment and continuous improvement",
   "cluster": "People and culture",
   "icon": "radar",
   "flag": "I",
   "dam": "oversight-and-implementation-of-the-policy",
   "signposts": [
    {
     "doc": "RB-DMAF",
     "a": null,
     "label": "Data Maturity Assessment for Government",
     "flag": "E"
    },
    {
     "doc": "SRC-GDQF",
     "a": "focus-on-continuous-improvement",
     "label": "Focus on continuous improvement",
     "flag": "E"
    }
   ],
   "playbook": "capabilities.html#CR-23",
   "dma": [
    1,
    2,
    3,
    4,
    5,
    6,
    7,
    8,
    9,
    10
   ],
   "dmbok": [
    "Data governance"
   ],
   "dcam": [
    "Data management strategy and business case"
   ],
   "skills": [
    "data-maturity"
   ],
   "profs": [
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "The policy recognises different levels of data maturity; the government maturity framework is the shared way to measure them.",
   "prov": "O"
  },
  {
   "id": "CR-24",
   "name": "Investment, business cases and value",
   "cluster": "Delivery, change and value",
   "icon": "banknote",
   "flag": "E",
   "dam": "realising-our-data-ambitions",
   "signposts": [
    {
     "doc": "RB-GREEN",
     "a": null,
     "label": "The Green Book and the five case model",
     "flag": "E"
    },
    {
     "doc": "SRC-DQAP",
     "a": "evaluate-costs-and-benefits",
     "label": "Evaluate costs and benefits",
     "flag": "E"
    }
   ],
   "playbook": "capabilities.html#CR-24",
   "dma": [
    9
   ],
   "dmbok": [
    "Data governance"
   ],
   "dcam": [
    "Data management program and funding",
    "Data management strategy and business case"
   ],
   "skills": [
    "delivering-business-impact-through-data",
    "strategic-data-planning"
   ],
   "profs": [
    "PR-DD",
    "PR-AF"
   ],
   "coverage": "Covered",
   "note": "The policy says data must be properly valued and invested in; funding comes through business cases.",
   "prov": "O"
  },
  {
   "id": "CR-25",
   "name": "Integration with programmes, spend control and assurance",
   "cluster": "Delivery, change and value",
   "icon": "workflow",
   "flag": "N",
   "dam": null,
   "signposts": [
    {
     "doc": "RB-GOVS002",
     "a": null,
     "label": "GovS 002: Project Delivery",
     "flag": "E"
    },
    {
     "doc": "RB-IAAP",
     "a": null,
     "label": "Integrated assurance for major projects",
     "flag": "E"
    },
    {
     "doc": "RB-SVCASSESS",
     "a": null,
     "label": "Service assessments",
     "flag": "E"
    },
    {
     "doc": "SRC-DQAP",
     "a": "plan-for-and-manage-changes",
     "label": "Plan for and manage changes",
     "flag": "E"
    }
   ],
   "playbook": "capabilities.html#CR-25",
   "dma": [
    3,
    9
   ],
   "dmbok": [
    "Data governance"
   ],
   "dcam": [
    "Data management program and funding"
   ],
   "skills": [
    "managing-a-data-project",
    "stakeholder-relationship-management"
   ],
   "profs": [
    "PR-PD",
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "Not in the policy text. Most new and replacement data assets arrive through change programmes, so the controls must be built into them.",
   "prov": "O"
  },
  {
   "id": "CR-26",
   "name": "Legacy migration and decommissioning",
   "cluster": "Delivery, change and value",
   "icon": "construction",
   "flag": "N",
   "dam": null,
   "signposts": [
    {
     "doc": "RB-LEGACY",
     "a": "build-a-complete-and-accurate-register-of-your-data-assets",
     "label": "Build a register of your data assets",
     "flag": "E"
    },
    {
     "doc": "RB-LEGACY",
     "a": "issues-that-stop-legacy-technology-migration",
     "label": "Issues that stop legacy migration",
     "flag": "E"
    },
    {
     "doc": "RB-RETIRE",
     "a": "protecting-information",
     "label": "Protecting information when retiring a service",
     "flag": "E"
    }
   ],
   "playbook": "capabilities.html#CR-26",
   "dma": [
    3,
    7
   ],
   "dmbok": [
    "Data integration and interoperability",
    "Data storage and operations"
   ],
   "dcam": [
    "Data and technology architecture"
   ],
   "skills": [
    "data-integration-design",
    "data-preparation-and-linkage"
   ],
   "profs": [
    "PR-DD",
    "PR-KIM"
   ],
   "coverage": "Covered",
   "note": "Not in the policy. The legacy guidance makes a data asset register its second principle; migrations are where quality is most at risk.",
   "prov": "O"
  },
  {
   "id": "CR-27",
   "name": "Ownership transition and handover to business as usual",
   "cluster": "Delivery, change and value",
   "icon": "arrow-right-left",
   "flag": "I",
   "dam": "data-ownership",
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "steps-to-transition-data-ownership-when-someone-leaves-the-organisation",
     "label": "Steps to transition ownership",
     "flag": "E"
    },
    {
     "doc": "SRC-OWN",
     "a": "how-often-data-ownership-should-be-reviewed-or-updated",
     "label": "How often ownership should be reviewed",
     "flag": "E"
    }
   ],
   "playbook": "capabilities.html#CR-27",
   "dma": [
    10
   ],
   "dmbok": [
    "Data governance"
   ],
   "dcam": [
    "Data governance"
   ],
   "skills": [
    "data-governance",
    "stakeholder-relationship-management"
   ],
   "profs": [
    "PR-PD",
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "A named owner must survive staff moves and the end of the project that created the asset.",
   "prov": "O"
  },
  {
   "id": "CR-28",
   "name": "Cross-boundary collaboration",
   "cluster": "Delivery, change and value",
   "icon": "share-2",
   "flag": "E",
   "dam": "organisational-and-administrative-scope",
   "signposts": [
    {
     "doc": "SRC-DQAP",
     "a": "devolved-administrations",
     "label": "Devolved administrations",
     "flag": "E"
    },
    {
     "doc": "SRC-OWN",
     "a": "example-of-handling-data-ownership-for-shared-data-sets-across-multiple-organisations",
     "label": "Shared data sets across organisations",
     "flag": "E"
    }
   ],
   "playbook": "sectors.html",
   "dma": [
    1
   ],
   "dmbok": [
    "Data governance"
   ],
   "dcam": [
    "Data governance"
   ],
   "skills": [
    "stakeholder-relationship-management"
   ],
   "profs": [
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "Departments coordinate with their arm's length bodies, and data passed to devolved administrations can stay in scope.",
   "prov": "O"
  },
  {
   "id": "CR-29",
   "name": "Benefits realisation and evaluation",
   "cluster": "Delivery, change and value",
   "icon": "trending-up",
   "flag": "N",
   "dam": null,
   "signposts": [
    {
     "doc": "RB-MAGENTA",
     "a": null,
     "label": "The Magenta Book",
     "flag": "E"
    },
    {
     "doc": "SRC-OWN",
     "a": "measuring-the-success-of-data-ownership-initiatives",
     "label": "Measuring success of ownership",
     "flag": "I"
    }
   ],
   "playbook": "capabilities.html#CR-29",
   "dma": [
    5
   ],
   "dmbok": [
    "Data governance",
    "Data warehousing and business intelligence"
   ],
   "dcam": [
    "Data management program and funding"
   ],
   "skills": [
    "performance-measurement",
    "delivering-business-impact-through-data"
   ],
   "profs": [
    "PR-AF"
   ],
   "coverage": "Covered",
   "note": "The policy lists benefits such as less duplication and cleansing; showing they happened needs an evaluation plan.",
   "prov": "O"
  },
  {
   "id": "CR-30",
   "name": "Equality and inclusion in data",
   "cluster": "Protection, ethics and trust",
   "icon": "accessibility",
   "flag": "N",
   "dam": null,
   "signposts": [
    {
     "doc": "RB-PSED",
     "a": null,
     "label": "Public sector equality duty",
     "flag": "E"
    },
    {
     "doc": "RB-EQA",
     "a": null,
     "label": "Equality Act 2010",
     "flag": "E"
    }
   ],
   "playbook": "inclusion.html",
   "dma": [
    6
   ],
   "dmbok": [
    "Data governance",
    "Data quality"
   ],
   "dcam": [
    "Data governance"
   ],
   "skills": [
    "applied-empathy-and-inclusivity",
    "data-ethics-and-privacy"
   ],
   "profs": [
    "PR-AF",
    "PR-DD"
   ],
   "coverage": "Covered",
   "note": "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.",
   "prov": "O"
  },
  {
   "id": "CR-31",
   "name": "Cyber resilience and incident response for data assets",
   "cluster": "Protection, ethics and trust",
   "icon": "shield-check",
   "flag": "I",
   "dam": "data-assets-in-scope",
   "signposts": [
    {
     "doc": "SRC-OWN",
     "a": "data-is-secure",
     "label": "Data is secure",
     "flag": "E"
    },
    {
     "doc": "RB-CAF",
     "a": null,
     "label": "Cyber Assessment Framework",
     "flag": "E"
    },
    {
     "doc": "RB-NCSCIR",
     "a": null,
     "label": "NCSC incident management",
     "flag": "E"
    },
    {
     "doc": "RB-GOVS007",
     "a": null,
     "label": "GovS 007: Security",
     "flag": "E"
    }
   ],
   "playbook": "areas.html#DM-SEC",
   "dma": [
    8
   ],
   "dmbok": [
    "Data security"
   ],
   "dcam": [
    "Data control environment"
   ],
   "skills": [
    "data-compliance-and-security",
    "data-risk-management"
   ],
   "profs": [
    "PR-CYB",
    "PR-SEC"
   ],
   "coverage": "Covered",
   "note": "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.",
   "prov": "O"
  },
  {
   "id": "CR-32",
   "name": "Avoiding future legacy: open standards, portability and exit",
   "cluster": "Delivery, change and value",
   "icon": "arrow-right-left",
   "flag": "N",
   "dam": null,
   "signposts": [
    {
     "doc": "RB-OPEN",
     "a": null,
     "label": "Open standards for government",
     "flag": "E"
    },
    {
     "doc": "RB-TECHDEBT",
     "a": null,
     "label": "Prevent technical debt and legacy",
     "flag": "E"
    },
    {
     "doc": "RB-CHOOSE",
     "a": null,
     "label": "Choosing technology",
     "flag": "E"
    },
    {
     "doc": "RB-MSC",
     "a": null,
     "label": "Model Services Contract",
     "flag": "E"
    }
   ],
   "playbook": "capabilities.html#CR-32",
   "dma": [
    3,
    7
   ],
   "dmbok": [
    "Data architecture",
    "Data integration and interoperability"
   ],
   "dcam": [
    "Data and technology architecture"
   ],
   "skills": [
    "data-standards",
    "data-architecture"
   ],
   "profs": [
    "PR-DD",
    "PR-PD"
   ],
   "coverage": "Covered",
   "note": "Not in the policy. Without open formats, documented schemas and exit terms, every new system becomes the next concentration of hard-to-reach data.",
   "prov": "O"
  }
 ],
 "maturity": {
  "verified": "2026-11-05",
  "licence": "CC BY-NC-SA 4.0",
  "url": "https://www.gov.uk/government/publications/data-maturity-assessment-for-government-framework/data-maturity-assessment-for-government-framework-html",
  "topics": [
   {
    "n": 1,
    "name": "Engaging with others",
    "anchor": "topic-1-engaging-with-others",
    "icon": "share-2",
    "rows": {
     "Uses": 0,
     "Data": 0,
     "Leadership": 0,
     "Culture": 7,
     "Tools": 0,
     "Skills": 1
    }
   },
   {
    "n": 2,
    "name": "Having the right data skills and knowledge",
    "anchor": "topic-2-having-the-right-data-skills-and-knowledge",
    "icon": "graduation-cap",
    "rows": {
     "Uses": 1,
     "Data": 1,
     "Leadership": 4,
     "Culture": 1,
     "Tools": 0,
     "Skills": 7
    }
   },
   {
    "n": 3,
    "name": "Having the right systems",
    "anchor": "topic-3-having-the-right-systems",
    "icon": "server",
    "rows": {
     "Uses": 0,
     "Data": 0,
     "Leadership": 1,
     "Culture": 0,
     "Tools": 9,
     "Skills": 0
    }
   },
   {
    "n": 4,
    "name": "Knowing the data you have",
    "anchor": "topic-4-knowing-the-data-you-have",
    "icon": "library-big",
    "rows": {
     "Uses": 0,
     "Data": 4,
     "Leadership": 0,
     "Culture": 0,
     "Tools": 0,
     "Skills": 0
    }
   },
   {
    "n": 5,
    "name": "Making decisions with data",
    "anchor": "topic-5-making-decisions-with-data",
    "icon": "chart-line",
    "rows": {
     "Uses": 7,
     "Data": 0,
     "Leadership": 3,
     "Culture": 0,
     "Tools": 0,
     "Skills": 0
    }
   },
   {
    "n": 6,
    "name": "Managing and using data ethically",
    "anchor": "topic-6-managing-and-using-data-ethically",
    "icon": "scale",
    "rows": {
     "Uses": 0,
     "Data": 2,
     "Leadership": 2,
     "Culture": 5,
     "Tools": 1,
     "Skills": 1
    }
   },
   {
    "n": 7,
    "name": "Managing your data",
    "anchor": "topic-7-managing-your-data",
    "icon": "database",
    "rows": {
     "Uses": 0,
     "Data": 11,
     "Leadership": 1,
     "Culture": 3,
     "Tools": 0,
     "Skills": 0
    }
   },
   {
    "n": 8,
    "name": "Protecting your data",
    "anchor": "topic-8-protecting-your-data",
    "icon": "lock-keyhole",
    "rows": {
     "Uses": 0,
     "Data": 2,
     "Leadership": 0,
     "Culture": 4,
     "Tools": 2,
     "Skills": 2
    }
   },
   {
    "n": 9,
    "name": "Setting your data direction",
    "anchor": "topic-9-setting-your-data-direction",
    "icon": "compass",
    "rows": {
     "Uses": 1,
     "Data": 1,
     "Leadership": 4,
     "Culture": 1,
     "Tools": 0,
     "Skills": 0
    }
   },
   {
    "n": 10,
    "name": "Taking responsibility for data",
    "anchor": "topic-10-taking-responsibility-for-data",
    "icon": "key-round",
    "rows": {
     "Uses": 0,
     "Data": 1,
     "Leadership": 2,
     "Culture": 3,
     "Tools": 1,
     "Skills": 1
    }
   }
  ],
  "themes": [
   {
    "name": "Uses",
    "gloss": "Getting value from data: decisions, evidence of impact, better services."
   },
   {
    "name": "Data",
    "gloss": "The technical side of managing data: assets, collection, quality, interoperability."
   },
   {
    "name": "Leadership",
    "gloss": "How senior and business leaders engage with data: strategy, responsibility, oversight, investment."
   },
   {
    "name": "Culture",
    "gloss": "Attitudes to data across the organisation: awareness, openness, security."
   },
   {
    "name": "Tools",
    "gloss": "The systems and tools used to store, share and work with data."
   },
   {
    "name": "Skills",
    "gloss": "The data skills and knowledge of staff at every level."
   }
  ],
  "levels": [
   "Beginning",
   "Emerging",
   "Learning",
   "Developing",
   "Mastering"
  ],
  "level_anchors": [
   "level-1-beginning",
   "level-2-emerging",
   "level-3-learning",
   "level-4-developing",
   "level-5-mastering"
  ],
  "strands": [
   {
    "id": "own",
    "name": "Ownership and governance",
    "icon": "key-round",
    "cr": [
     "CR-01",
     "CR-07"
    ],
    "dma": [
     10,
     9
    ],
    "levels": [
     "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."
    ]
   },
   {
    "id": "cat",
    "name": "Cataloguing and reporting",
    "icon": "library-big",
    "cr": [
     "CR-05",
     "CR-06",
     "CR-03"
    ],
    "dma": [
     4
    ],
    "levels": [
     "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."
    ]
   },
   {
    "id": "dq",
    "name": "Quality management",
    "icon": "gauge",
    "cr": [
     "CR-08",
     "CR-09"
    ],
    "dma": [
     7
    ],
    "levels": [
     "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."
    ]
   },
   {
    "id": "chg",
    "name": "Change and investment",
    "icon": "workflow",
    "cr": [
     "CR-24",
     "CR-25",
     "CR-26"
    ],
    "dma": [
     3,
     9
    ],
    "levels": [
     "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."
    ]
   }
  ],
  "crosswalk": [
   {
    "level": "Beginning",
    "cmmi": "Initial",
    "iso8000": "Processes performed ad hoc",
    "note": "Little defined practice."
   },
   {
    "level": "Emerging",
    "cmmi": "Managed",
    "iso8000": "Processes performed and managed in places",
    "note": "Practice depends on individuals."
   },
   {
    "level": "Learning",
    "cmmi": "Defined",
    "iso8000": "Processes defined and repeatable",
    "note": "The DAM Policy minimum sits around here for critical assets."
   },
   {
    "level": "Developing",
    "cmmi": "Quantitatively managed",
    "iso8000": "Processes measured",
    "note": "Measures drive decisions."
   },
   {
    "level": "Mastering",
    "cmmi": "Optimising",
    "iso8000": "Processes continually improved",
    "note": "Improvement is systematic."
   }
  ]
 },
 "professions": {
  "verified": "2026-11-05",
  "roles": [
   {
    "id": "data-governance-manager",
    "title": "Data governance manager",
    "url": "https://ddat-capability-framework.service.gov.uk/role/data-governance-manager/",
    "levels": [
     {
      "name": "Data governance manager",
      "anchor": "data-governance-manager",
      "grades": [
       "HEO",
       "SEO",
       "G7"
      ]
     },
     {
      "name": "Lead data governance manager",
      "anchor": "lead-data-governance-manager",
      "grades": [
       "G7",
       "G6"
      ]
     },
     {
      "name": "Head of data governance",
      "anchor": "head-of-data-governance",
      "grades": [
       "G6"
      ]
     }
    ],
    "skills": [
     [
      "Communicating analysis and insight",
      "communicating-analysis-and-insight",
      "W P E"
     ],
     [
      "Communicating between the technical and non-technical",
      "communicating-between-the-technical-and-non-technical",
      "W P E"
     ],
     [
      "Data ethics and privacy",
      "data-ethics-and-privacy",
      "W P E"
     ],
     [
      "Data governance",
      "data-governance",
      "W P E"
     ],
     [
      "Data innovation",
      "data-innovation",
      "W P E"
     ],
     [
      "Data life cycle",
      "data-life-cycle",
      "W P E"
     ],
     [
      "Data literacy improvement",
      "data-literacy-improvement",
      "W P E"
     ],
     [
      "Data management",
      "data-management",
      "W P E"
     ],
     [
      "Data maturity",
      "data-maturity",
      "W P E"
     ],
     [
      "Data standards",
      "data-standards",
      "W P E"
     ],
     [
      "Enabling and informing risk-based decisions",
      "enabling-and-informing-risk-based-decisions",
      "W P E"
     ],
     [
      "Stakeholder relationship management",
      "stakeholder-relationship-management",
      "W P E"
     ],
     [
      "Strategic thinking",
      "strategic-thinking",
      "W P E"
     ]
    ]
   },
   {
    "id": "chief-data-officer",
    "title": "Chief data officer",
    "url": "https://ddat-capability-framework.service.gov.uk/role/chief-data-officer/",
    "grades": "Senior Civil Service 1 and 2",
    "levels": [],
    "skills": [
     [
      "Capability building for digital, data and technology",
      "capability-building-for-digital-data-and-technology",
      ""
     ],
     [
      "Data architecture",
      "data-architecture",
      ""
     ],
     [
      "Data governance leadership",
      "data-governance-leadership",
      ""
     ],
     [
      "Data risk management",
      "data-risk-management",
      ""
     ],
     [
      "Innovation in digital, data and technology",
      "innovation-in-digital-data-and-technology",
      ""
     ],
     [
      "Strategic data planning",
      "strategic-data-planning",
      ""
     ]
    ]
   },
   {
    "id": "data-architect",
    "title": "Data architect",
    "url": "https://ddat-capability-framework.service.gov.uk/role/data-architect/",
    "levels": [
     {
      "name": "Data architect",
      "anchor": "data-architect",
      "grades": [
       "SEO",
       "G7"
      ]
     },
     {
      "name": "Senior data architect",
      "anchor": "senior-data-architect",
      "grades": [
       "G7",
       "G6"
      ]
     },
     {
      "name": "Chief data architect",
      "anchor": "chief-data-architect",
      "grades": [
       "G6"
      ]
     }
    ],
    "skills": [
     [
      "Communicating between the technical and non-technical",
      "communicating-between-the-technical-and-non-technical",
      "W P P"
     ],
     [
      "Communicating data",
      "communicating-data",
      "A W P"
     ],
     [
      "Data analysis and synthesis",
      "data-analysis-and-synthesis",
      "W W W"
     ],
     [
      "Data governance (data architect)",
      "data-governance-data-architect",
      "W P E"
     ],
     [
      "Data innovation",
      "data-innovation",
      "A W P"
     ],
     [
      "Data modelling",
      "data-modelling",
      "W P E"
     ],
     [
      "Data standards",
      "data-standards",
      "W P E"
     ],
     [
      "Metadata management",
      "metadata-management",
      "W P E"
     ],
     [
      "Problem management",
      "problem-management",
      "W P E"
     ],
     [
      "Strategic thinking",
      "strategic-thinking",
      "A W P"
     ],
     [
      "Turning business problems into data design",
      "turning-business-problems-into-data-design",
      "W P E"
     ]
    ]
   },
   {
    "id": "data-analyst",
    "title": "Data analyst",
    "url": "https://ddat-capability-framework.service.gov.uk/role/data-analyst/",
    "levels": [
     {
      "name": "Associate data analyst",
      "anchor": "associate-data-analyst",
      "grades": [
       "EO",
       "HEO"
      ]
     },
     {
      "name": "Data analyst",
      "anchor": "data-analyst",
      "grades": [
       "HEO",
       "SEO"
      ]
     },
     {
      "name": "Senior data analyst",
      "anchor": "senior-data-analyst",
      "grades": [
       "SEO",
       "G7"
      ]
     },
     {
      "name": "Principal data analyst",
      "anchor": "principal-data-analyst",
      "grades": [
       "G7",
       "G6"
      ]
     }
    ],
    "skills": [
     [
      "Applying statistical and analytical tools and techniques",
      "applying-statistical-and-analytical-tools-and-techniques",
      "A W P E"
     ],
     [
      "Communicating between the technical and non-technical",
      "communicating-between-the-technical-and-non-technical",
      "A W P E"
     ],
     [
      "Data ethics and privacy",
      "data-ethics-and-privacy",
      "A W P P"
     ],
     [
      "Data management",
      "data-management",
      "A W P E"
     ],
     [
      "Data preparation and linkage",
      "data-preparation-and-linkage",
      "A W P E"
     ],
     [
      "Data visualisation",
      "data-visualisation",
      "A W P E"
     ],
     [
      "Delivering business impact through data",
      "delivering-business-impact-through-data",
      "A W P E"
     ],
     [
      "Developing code for analysis",
      "developing-code-for-analysis",
      "A W P E"
     ],
     [
      "Managing a data project",
      "managing-a-data-project",
      "A W P E"
     ]
    ]
   },
   {
    "id": "data-engineer",
    "title": "Data engineer",
    "url": "https://ddat-capability-framework.service.gov.uk/role/data-engineer/",
    "levels": [
     {
      "name": "Data engineer",
      "anchor": "data-engineer",
      "grades": [
       "HEO",
       "SEO"
      ]
     },
     {
      "name": "Senior data engineer",
      "anchor": "senior-data-engineer",
      "grades": [
       "SEO",
       "G7"
      ]
     },
     {
      "name": "Lead data engineer",
      "anchor": "lead-data-engineer",
      "grades": [
       "G7"
      ]
     },
     {
      "name": "Head of data engineering",
      "anchor": "head-of-data-engineering",
      "grades": [
       "G7",
       "G6"
      ]
     }
    ],
    "skills": [
     [
      "Communicating between the technical and non-technical",
      "communicating-between-the-technical-and-non-technical",
      "A W P E"
     ],
     [
      "Data analysis and synthesis",
      "data-analysis-and-synthesis",
      "W W P P"
     ],
     [
      "Data compliance and security",
      "data-compliance-and-security",
      "W P E E"
     ],
     [
      "Data development process",
      "data-development-process",
      "W P E E"
     ],
     [
      "Data innovation",
      "data-innovation",
      "A W P E"
     ],
     [
      "Data integration design",
      "data-integration-design",
      "W P E E"
     ],
     [
      "Data modelling",
      "data-modelling",
      "W P E W"
     ],
     [
      "Metadata management",
      "metadata-management",
      "W P P E"
     ],
     [
      "Problem management",
      "problem-management",
      "A W P E"
     ],
     [
      "Programming and build (data and analytics engineering)",
      "programming-and-build-data-and-analytics-engineering",
      "W P P E"
     ]
    ]
   },
   {
    "id": "data-and-ai-ethicist",
    "title": "Data and artificial intelligence (AI) ethicist",
    "url": "https://ddat-capability-framework.service.gov.uk/role/data-and-ai-ethicist/",
    "levels": [
     {
      "name": "Data and AI ethicist",
      "anchor": "data-and-ai-ethicist",
      "grades": []
     },
     {
      "name": "Senior data and AI ethicist",
      "anchor": "senior-data-and-ai-ethicist",
      "grades": []
     },
     {
      "name": "Lead data and AI ethicist",
      "anchor": "lead-data-and-ai-ethicist",
      "grades": [
       "SEO",
       "G7"
      ]
     },
     {
      "name": "Head of data and AI ethics",
      "anchor": "head-of-data-and-ai-ethics",
      "grades": [
       "G6"
      ]
     }
    ],
    "skills": [
     [
      "Analysis and synthesis for data and AI ethics",
      "analysis-and-synthesis-data-ethics",
      "W W P E"
     ],
     [
      "Applied empathy and inclusivity",
      "applied-empathy-and-inclusivity",
      "P P E E"
     ],
     [
      "Applied social sciences",
      "applied-social-sciences",
      "A W P E"
     ],
     [
      "Communicating between the technical and non-technical",
      "communicating-between-the-technical-and-non-technical",
      "W P P E"
     ],
     [
      "Data and AI ethics communication",
      "data-ai-ethics-communication",
      "W P E E"
     ],
     [
      "Data and AI ethics product management",
      "data-and-ai-ethics-product-management",
      "A W P E"
     ],
     [
      "Data ethics and privacy",
      "data-ethics-and-privacy",
      "W P P E"
     ],
     [
      "Managing decisions and risks",
      "managing-decisions-and-risks",
      "W W P P"
     ],
     [
      "Problem management",
      "problem-management",
      "A W P P"
     ],
     [
      "Stakeholder relationship management",
      "stakeholder-relationship-management",
      "A W P E"
     ]
    ]
   },
   {
    "id": "performance-analyst",
    "title": "Performance analyst",
    "url": "https://ddat-capability-framework.service.gov.uk/role/performance-analyst/",
    "levels": [
     {
      "name": "Associate performance analyst",
      "anchor": "associate-performance-analyst",
      "grades": [
       "AO",
       "EO"
      ]
     },
     {
      "name": "Performance analyst",
      "anchor": "performance-analyst",
      "grades": [
       "HEO",
       "SEO"
      ]
     },
     {
      "name": "Senior performance analyst",
      "anchor": "senior-performance-analyst",
      "grades": [
       "SEO",
       "G7"
      ]
     },
     {
      "name": "Lead performance analyst",
      "anchor": "lead-performance-analyst",
      "grades": [
       "G7"
      ]
     },
     {
      "name": "Head of performance analysis",
      "anchor": "head-of-performance-analysis",
      "grades": [
       "G7",
       "G6"
      ]
     }
    ],
    "skills": [
     [
      "Analysis and insight",
      "analysis-and-insight",
      "W P P E P"
     ],
     [
      "Communicating analysis and insight",
      "communicating-analysis-and-insight",
      "W W P E E"
     ],
     [
      "Performance measurement",
      "performance-measurement",
      "A W P E E"
     ],
     [
      "Quality assurance of data and analysis",
      "quality-assurance-of-data-and-analysis",
      "A W P E E"
     ],
     [
      "Technical understanding (performance analyst)",
      "technical-understanding-performance-analyst",
      "A W P E E"
     ],
     [
      "Understanding analysis across the product life cycle",
      "understanding-analysis-across-the-product-life-cycle",
      "A W P E E"
     ],
     [
      "User-centred analysis",
      "user-centred-analysis",
      "A W P E E"
     ],
     [
      "Working within constraints (performance analyst)",
      "working-within-constraints-performance-analyst",
      "A W P E E"
     ]
    ]
   }
  ],
  "persona_map": [
   {
    "persona": "cdo",
    "roles": [
     "chief-data-officer"
    ],
    "profs": [
     "PR-DD"
    ],
    "learn": [
     "RB-NSG",
     "RB-PROSPECTUS",
     "RB-DMAF"
    ]
   },
   {
    "persona": "coo",
    "roles": [
     "data-governance-manager"
    ],
    "profs": [
     "PR-DD",
     "PR-PD",
     "PR-KIM"
    ],
    "learn": [
     "RB-DSFA",
     "RB-PROSPECTUS",
     "RB-DAMA"
    ]
   },
   {
    "persona": "own",
    "roles": [],
    "profs": [
     "PR-OWNPROF"
    ],
    "learn": [
     "RB-DSFA",
     "RB-CURRIC"
    ]
   },
   {
    "persona": "stw",
    "roles": [
     "data-governance-manager",
     "data-analyst"
    ],
    "profs": [
     "PR-KIM",
     "PR-AF",
     "PR-DD"
    ],
    "learn": [
     "RB-DSFA",
     "RB-PKSB",
     "RB-DAMA"
    ]
   },
   {
    "persona": "cat",
    "roles": [
     "data-governance-manager",
     "data-architect"
    ],
    "profs": [
     "PR-KIM",
     "PR-DD"
    ],
    "learn": [
     "RB-PKSB",
     "RB-SFIA",
     "RB-DSFA"
    ]
   },
   {
    "persona": "dql",
    "roles": [
     "data-analyst",
     "data-engineer",
     "performance-analyst"
    ],
    "profs": [
     "PR-AF",
     "PR-DD"
    ],
    "learn": [
     "RB-AFCAREER",
     "RB-RSS",
     "RB-APPDA"
    ]
   },
   {
    "persona": "prg",
    "roles": [],
    "profs": [
     "PR-PD",
     "PR-COM"
    ],
    "learn": [
     "RB-PDPROF",
     "RB-GOVS002",
     "RB-SRO"
    ]
   },
   {
    "persona": "buy",
    "roles": [],
    "profs": [
     "PR-COM",
     "PR-DD"
    ],
    "learn": [
     "RB-SOURCING",
     "RB-DDATPB",
     "RB-PA23G"
    ]
   }
  ],
  "profs": [
   {
    "id": "PR-DD",
    "name": "Government Digital and Data Profession",
    "icon": "database",
    "rb": "RB-DDAT",
    "aligned": "Digital and data function",
    "why": "Home of the data governance manager, data architect, analyst, engineer and chief data officer roles."
   },
   {
    "id": "PR-AF",
    "name": "Analysis Function (statistics, economics, social and operational research, geography, actuaries)",
    "icon": "chart-line",
    "rb": "RB-AFROLES",
    "aligned": "Analysis function",
    "why": "Analysts who own and assure data for statistics, evidence and evaluation."
   },
   {
    "id": "PR-KIM",
    "name": "Knowledge and Information Management",
    "icon": "book-marked",
    "rb": "RB-KIM",
    "aligned": "Specialist profession",
    "why": "Records, information assets, metadata and information asset owner support."
   },
   {
    "id": "PR-SEC",
    "name": "Government Security Profession",
    "icon": "lock-keyhole",
    "rb": "RB-SECPROF",
    "aligned": "Security function",
    "why": "Classification, protective controls and support to the senior information risk owner."
   },
   {
    "id": "PR-CYB",
    "name": "Government Cyber Profession",
    "icon": "shield-check",
    "rb": "RB-CYBERPROF",
    "aligned": "Digital function",
    "why": "Technical security of the systems that hold critical assets."
   },
   {
    "id": "PR-PD",
    "name": "Project Delivery",
    "icon": "workflow",
    "rb": "RB-GOVS002",
    "aligned": "Project delivery function",
    "why": "Senior responsible owners and programme teams who create, migrate and retire data assets."
   },
   {
    "id": "PR-OWNPROF",
    "name": "The data owner's own profession (for example policy, operational delivery or finance)",
    "icon": "users-round",
    "rb": "RB-PROFS",
    "aligned": "Any",
    "why": "Data owners are usually business leaders, not data specialists; the ownership model lists the skills they need."
   },
   {
    "id": "PR-COM",
    "name": "Government Commercial Function",
    "icon": "handshake",
    "rb": "RB-COMMFN",
    "aligned": "Commercial and grants function",
    "why": "Commercial specialists who set the contract terms for data ownership, metadata, quality and exit."
   }
  ],
  "learning": [
   {
    "stage": "Awareness: everyone",
    "icon": "lightbulb",
    "items": [
     "RB-DSFA",
     "RB-CURRIC"
    ],
    "note": "Free courses at awareness level, then the subject-based recommended curriculum."
   },
   {
    "stage": "Working: owners, stewards and coordinators",
    "icon": "pencil-line",
    "items": [
     "RB-DSFA",
     "RB-PROSPECTUS",
     "RB-SPECIALIST"
    ],
    "note": "Working-level data courses and Strand 4 specialist learning from the professions."
   },
   {
    "stage": "Practitioner: specialists",
    "icon": "wrench",
    "items": [
     "RB-DDAT",
     "RB-AFCAREER",
     "RB-PKSB",
     "RB-SFIA"
    ],
    "note": "Use your profession's framework to plan the next role level and the skills it needs."
   },
   {
    "stage": "Expert and leader",
    "icon": "building-2",
    "items": [
     "RB-NSG",
     "RB-DAMA",
     "RB-DMAF"
    ],
    "note": "Leadership programmes, external certification and leading a maturity assessment."
   }
  ],
  "campus": [
   {
    "name": "Data and Analytics: Strand 1, foundations",
    "url": "https://prospectus.governmentcampus.co.uk/01-data-and-analytics/"
   },
   {
    "name": "Digital: Strand 3",
    "url": "https://prospectus.governmentcampus.co.uk/03-digital/"
   },
   {
    "name": "Data and Analytics: Strand 4, specialist",
    "url": "https://prospectus.governmentcampus.co.uk/04-data-and-analytics/"
   },
   {
    "name": "Artificial Intelligence: Strand 4",
    "url": "https://prospectus.governmentcampus.co.uk/04-artificial-intelligence/"
   },
   {
    "name": "Security: Strand 4",
    "url": "https://prospectus.governmentcampus.co.uk/04-security/"
   },
   {
    "name": "Risk Management: Strand 4",
    "url": "https://prospectus.governmentcampus.co.uk/04-risk-management/"
   },
   {
    "name": "Domain knowledge: Strand 5",
    "url": "https://prospectus.governmentcampus.co.uk/find-out-more/05-domain-knowledge/"
   }
  ]
 },
 "change": {
  "stages": [
   {
    "id": "plan",
    "name": "Strategy and business case",
    "icon": "banknote"
   },
   {
    "id": "discover",
    "name": "Discovery",
    "icon": "search"
   },
   {
    "id": "alpha",
    "name": "Alpha",
    "icon": "pencil-line"
   },
   {
    "id": "beta",
    "name": "Beta and build",
    "icon": "wrench"
   },
   {
    "id": "live",
    "name": "Live and business as usual",
    "icon": "activity"
   },
   {
    "id": "retire",
    "name": "Migrate or retire",
    "icon": "archive"
   }
  ],
  "touchpoints": {
   "plan": [
    "List the critical data assets the change will create, change, depend on or retire.",
    "Cost ownership, cataloguing and quality work in the economic and financial cases.",
    "Add data asset risks to the programme risk register."
   ],
   "discover": [
    "Check the catalogue for assets that already meet the need before collecting new data.",
    "Agree who will own each new or changed asset."
   ],
   "alpha": [
    "Design metadata and quality rules alongside the data model.",
    "Run a data protection impact assessment where personal data is involved."
   ],
   "beta": [
    "Catalogue new assets before go-live, with the core metadata.",
    "Write and test the DQAP; reconcile migrated data against the source."
   ],
   "live": [
    "Hand ownership, the DQAP and the runbook to named people in business as usual.",
    "Report the asset in the next annual return."
   ],
   "retire": [
    "Start from the asset register; decide to migrate, archive or dispose of each asset.",
    "Update or close catalogue entries and transfer ownership formally."
   ]
  },
  "items": [
   {
    "id": "CH-01",
    "title": "Put data assets in the business case",
    "icon": "banknote",
    "mode": "Change",
    "stage": "plan",
    "why": "The policy says data must be valued and invested in; business cases are where that money is decided.",
    "actions": [
     "Name each critical data asset in scope of the change in the strategic case.",
     "Cost owner, steward and catalogue effort and DQAP remediation in the financial case.",
     "Count avoided duplicate collection and cleansing as benefits in the economic case.",
     "Name the data owner in the management case."
    ],
    "evidence": [
     "Asset list in the business case",
     "Costed DAM activities",
     "Named owners"
    ],
    "roles": [
     "CDO",
     "OWN",
     "COO",
     "SRO"
    ],
    "refs": [
     "RB-GREEN",
     "RB-AQUA"
    ],
    "cr": [
     "CR-24"
    ],
    "prov": "O"
   },
   {
    "id": "CH-02",
    "title": "Use spend control and service assessments as checkpoints",
    "icon": "stamp",
    "mode": "Change",
    "stage": "alpha",
    "why": "Spend control and service assessments already stop work that is not ready; adding DAM evidence costs little.",
    "actions": [
     "Add three questions to internal spend control: which assets, who owns them, are they catalogued.",
     "At alpha, show the planned metadata and quality rules; at beta, the catalogue entry and DQAP.",
     "Show the panel that data was considered: who owns each asset, how it is described and quality-planned, the DPIA, and that data professionals and users were involved. You do not need to hand in every template; keep them as your team's working record.",
     "Record the answers so the next return reuses them."
    ],
    "evidence": [
     "Spend control submission notes",
     "Assessment evidence pack"
    ],
    "roles": [
     "COO",
     "CAT",
     "DQL",
     "SVO"
    ],
    "refs": [
     "RB-SPEND",
     "RB-SVCASSESS",
     "RB-TCOP",
     "RB-SVC"
    ],
    "cr": [
     "CR-25"
    ],
    "prov": "O"
   },
   {
    "id": "CH-03",
    "title": "Write DAM into programme assurance",
    "icon": "clipboard-check",
    "mode": "Change",
    "stage": "plan",
    "why": "Large programmes have integrated assurance plans; DAM checks in them are reviewed with everything else.",
    "actions": [
     "Add DAM checkpoints to the integrated assurance and approval plan.",
     "Ask reviewers to check asset ownership, catalogue entries and quality plans at each gate.",
     "Give the senior responsible owner a single line on data asset readiness in highlight reports."
    ],
    "evidence": [
     "Assurance plan entries",
     "Gate review findings"
    ],
    "roles": [
     "CDO",
     "BRD",
     "SRO",
     "PMO"
    ],
    "refs": [
     "RB-IAAP",
     "RB-NISTA",
     "RB-GMPP",
     "RB-GOVS002"
    ],
    "cr": [
     "CR-25",
     "CR-03"
    ],
    "prov": "O"
   },
   {
    "id": "CH-04",
    "title": "Plan legacy exits from the asset register",
    "icon": "construction",
    "mode": "Change",
    "stage": "retire",
    "why": "Legacy systems hold large concentrations of hard-to-reach data; the legacy guidance asks for an asset register first.",
    "actions": [
     "Build or update the register of data assets held in the legacy system.",
     "Profile quality before migration and set reconciliation rules for counts, totals and keys.",
     "Decide for each asset: migrate, archive under records rules, or dispose.",
     "Keep the catalogue and ownership in step as each asset moves."
    ],
    "evidence": [
     "Asset register for the system",
     "Profiling and reconciliation results",
     "Disposition decisions"
    ],
    "roles": [
     "OWN",
     "CUS",
     "DQL",
     "CAT",
     "MIG",
     "ARC"
    ],
    "refs": [
     "RB-LEGACY",
     "RB-TECHDEBT",
     "RB-RETIRE",
     "RB-TNA"
    ],
    "cr": [
     "CR-26",
     "CR-15"
    ],
    "prov": "O"
   },
   {
    "id": "CH-05",
    "title": "Target legacy where it blocks outcomes and widens inequalities",
    "icon": "target",
    "mode": "Both",
    "stage": "plan",
    "why": "Where poor or locked-in data delays access to services, the people most affected are often those already disadvantaged.",
    "actions": [
     "Score each critical asset on legacy risk, quality, reuse value and impact on outcomes.",
     "Check whether gaps or errors fall harder on some groups, using the equality duty.",
     "Fund fixes first where risk, value and inequality overlap.",
     "Report the choice and its reasons to the data governance board."
    ],
    "evidence": [
     "Prioritised asset heatmap",
     "Equality analysis"
    ],
    "roles": [
     "CDO",
     "BRD",
     "OWN"
    ],
    "refs": [
     "RB-PSED",
     "RB-LEGACY",
     "RB-DMAF"
    ],
    "cr": [
     "CR-02",
     "CR-30",
     "CR-26"
    ],
    "prov": "O"
   },
   {
    "id": "CH-06",
    "title": "Build DAM into contracts",
    "icon": "handshake",
    "mode": "Both",
    "stage": "discover",
    "why": "Suppliers often hold or process critical assets; without contract terms the owner cannot meet the policy.",
    "actions": [
     "State who owns the data and its metadata.",
     "Require metadata in an agreed format and quality reporting against the DQAP.",
     "Set data return, format and deletion terms for exit.",
     "Include data protection terms from the procurement policy note."
    ],
    "evidence": [
     "Contract schedule for data",
     "Exit plan"
    ],
    "roles": [
     "OWN",
     "COO",
     "CML"
    ],
    "refs": [
     "RB-SOURCING",
     "RB-DDATPB",
     "RB-PPN020"
    ],
    "cr": [
     "CR-20"
    ],
    "prov": "O"
   },
   {
    "id": "CH-07",
    "title": "Manage data asset risk on the same registers",
    "icon": "shield-check",
    "mode": "Both",
    "stage": "live",
    "why": "The policy relies on risk controls; separate data risk lists are easy to ignore.",
    "actions": [
     "Record risks to critical assets on the corporate or programme register.",
     "Link each to the asset, its owner and the senior information risk owner.",
     "Review alongside DQAP results each quarter."
    ],
    "evidence": [
     "Risk register entries",
     "Quarterly review notes"
    ],
    "roles": [
     "OWN",
     "BRD",
     "PDM"
    ],
    "refs": [
     "RB-ORANGE",
     "RB-GSC"
    ],
    "cr": [
     "CR-19"
    ],
    "prov": "O"
   },
   {
    "id": "CH-08",
    "title": "Hand over to business as usual",
    "icon": "arrow-right-left",
    "mode": "Change",
    "stage": "live",
    "why": "Assets created by projects lose their owner when the project closes unless handover is planned.",
    "actions": [
     "Confirm a named business-as-usual owner and steward before the project closes.",
     "Hand over the DQAP, quality rules, runbook and open issues.",
     "Use the ownership model's transition steps and set the next review date."
    ],
    "evidence": [
     "Signed handover note",
     "Updated catalogue entry"
    ],
    "roles": [
     "OWN",
     "STW",
     "COO",
     "PDM",
     "SVO"
    ],
    "refs": [
     "RB-GOVS002"
    ],
    "cr": [
     "CR-27"
    ],
    "prov": "O"
   },
   {
    "id": "CH-09",
    "title": "Plan people change, not just process change",
    "icon": "users-round",
    "mode": "Both",
    "stage": "plan",
    "why": "New duties fail when people are not told, trained, given time or recognised for them.",
    "actions": [
     "Assess who is affected: owners, stewards, custodians, analysts, suppliers.",
     "Put data duties into role descriptions and objectives.",
     "Train each role at the right level and give stewards protected time.",
     "Communicate why the policy matters in terms of services and people, not compliance."
    ],
    "evidence": [
     "Change impact assessment",
     "Training plan",
     "Communications plan"
    ],
    "roles": [
     "CDO",
     "COO",
     "SRO",
     "PDM"
    ],
    "refs": [
     "RB-SUCCESS",
     "RB-DSFA",
     "RB-DDAT"
    ],
    "cr": [
     "CR-21",
     "CR-22"
    ],
    "prov": "O"
   },
   {
    "id": "CH-10",
    "title": "Show the benefits",
    "icon": "trending-up",
    "mode": "Both",
    "stage": "live",
    "why": "Continued funding depends on evidence that the work changed something.",
    "actions": [
     "Agree a few measures before starting, such as reuse requests met, duplicate collections stopped or time spent cleansing.",
     "Take a baseline, then measure each year with the return.",
     "Use proportionate evaluation methods."
    ],
    "evidence": [
     "Benefits map",
     "Baseline and annual measures"
    ],
    "roles": [
     "COO",
     "DQL",
     "PMO"
    ],
    "refs": [
     "RB-MAGENTA"
    ],
    "cr": [
     "CR-29",
     "CR-04"
    ],
    "prov": "O"
   },
   {
    "id": "CH-11",
    "title": "Keep the yearly cycle running in business as usual",
    "icon": "refresh-cw",
    "mode": "BAU",
    "stage": "live",
    "why": "The policy is annual; without a calendar it becomes a scramble before each return.",
    "actions": [
     "Set fixed dates for asset review, metadata updates, DQAP review and the board.",
     "Track each owner's actions between returns.",
     "Feed lessons into the next year's priorities."
    ],
    "evidence": [
     "Annual calendar",
     "Action log"
    ],
    "roles": [
     "COO",
     "BRD"
    ],
    "refs": [],
    "cr": [
     "CR-04",
     "CR-03"
    ],
    "prov": "O"
   },
   {
    "id": "CH-12",
    "title": "Assess maturity and set a target",
    "icon": "radar",
    "mode": "BAU",
    "stage": "plan",
    "why": "A shared maturity measure turns the policy into a plan that can be resourced and tracked.",
    "actions": [
     "Run the government data maturity assessment or use the self-assessment here as a first pass.",
     "Set a target level for each DAM strand with dates.",
     "Repeat every one to two years."
    ],
    "evidence": [
     "Assessment results",
     "Target levels"
    ],
    "roles": [
     "CDO",
     "COO"
    ],
    "refs": [
     "RB-DMAF",
     "RB-DMAHUB"
    ],
    "cr": [
     "CR-23"
    ],
    "prov": "O"
   },
   {
    "id": "CH-13",
    "title": "Share and reuse safely across organisations",
    "icon": "share-2",
    "mode": "Both",
    "stage": "discover",
    "why": "Reuse is the point of the policy, but it never removes legal duties or forces sharing.",
    "actions": [
     "Check the catalogue for reusable assets before collecting new data.",
     "Use the sharing framework and code for agreements.",
     "Record sharing arrangements against the asset in the catalogue."
    ],
    "evidence": [
     "Data sharing agreements",
     "Catalogue links"
    ],
    "roles": [
     "OWN",
     "DPO"
    ],
    "refs": [
     "RB-DSGF",
     "RB-ICOSHARE",
     "RB-DEA"
    ],
    "cr": [
     "CR-17",
     "CR-28"
    ],
    "prov": "O"
   },
   {
    "id": "CH-14",
    "title": "Design out future legacy and lock-in",
    "icon": "arrow-right-left",
    "mode": "Change",
    "stage": "alpha",
    "why": "Systems bought or built today become tomorrow's legacy unless their data can be moved out without loss or delay.",
    "actions": [
     "Require data in open, documented formats with a published schema.",
     "Ask suppliers to show how a full export with metadata works before you sign.",
     "Prefer open standards and APIs that follow the government API standards.",
     "Record each system's exit route against its assets in the catalogue."
    ],
    "evidence": [
     "Exit and portability test results",
     "Schema and API documentation"
    ],
    "roles": [
     "CUS",
     "CAT",
     "OWN",
     "ARC",
     "CML"
    ],
    "refs": [
     "RB-OPEN",
     "RB-API",
     "RB-CHOOSE",
     "RB-TECHDEBT"
    ],
    "cr": [
     "CR-32",
     "CR-26"
    ],
    "prov": "O"
   },
   {
    "id": "CH-15",
    "title": "Prepare for a cyber incident affecting a critical asset",
    "icon": "shield-check",
    "mode": "BAU",
    "stage": "live",
    "why": "A ransomware attack or breach can corrupt or expose a critical asset; quality plans and owners must be ready.",
    "actions": [
     "Mark critical data assets in the incident response plan and asset inventory.",
     "Agree recovery point and recovery time with each data owner.",
     "Test restoring an asset and check its quality afterwards against the DQAP rules.",
     "Agree who tells data users when an asset may be affected."
    ],
    "evidence": [
     "Incident plan entries",
     "Restore test and post-restore quality results"
    ],
    "roles": [
     "OWN",
     "CUS",
     "DPO"
    ],
    "refs": [
     "RB-NCSCIR",
     "RB-CAF",
     "RB-NCSC10",
     "RB-GOVS007"
    ],
    "cr": [
     "CR-31",
     "CR-19"
    ],
    "prov": "O"
   },
   {
    "id": "CH-16",
    "title": "Use the buying routes and contract terms that protect data",
    "icon": "handshake",
    "mode": "Change",
    "stage": "discover",
    "why": "Most catalogue, quality and platform tools are bought; the route and terms decide who controls the data.",
    "actions": [
     "Buy through an established framework where one fits, such as G-Cloud.",
     "Use the model contract schedules for data, security and exit rather than supplier terms.",
     "Make metadata delivery, quality reporting and data return measurable obligations with service credits.",
     "Publish transparency information as the Procurement Act requires."
    ],
    "evidence": [
     "Procurement route decision",
     "Contract data, security and exit schedules"
    ],
    "roles": [
     "COO",
     "OWN",
     "CML"
    ],
    "refs": [
     "RB-GCLOUD",
     "RB-MSC",
     "RB-MTC20",
     "RB-PA23",
     "RB-PA23G",
     "RB-SOURCING"
    ],
    "cr": [
     "CR-20",
     "CR-32"
    ],
    "prov": "O"
   }
  ],
  "programme_roles": {
   "intro": "Medium and large programmes bring in roles the DAM Policy and its guidance do not name. They decide most of what happens to critical data during change, so each needs explicit data responsibilities. This is this portal's assessment; the policy names only the chief data officer, data owners and the Chief Data Officer Council.",
   "rows": [
    {
     "role": "SRO",
     "stages": [
      "plan",
      "live"
     ],
     "works_with": [
      "OWN",
      "CDO"
     ],
     "resp": [
      "Make sure every critical asset in scope has an owner and a funded quality plan",
      "Accept DAM checkpoints into the assurance plan",
      "Sign off handover only when ownership, catalogue and DQAP transfer"
     ],
     "refs": [
      "RB-SRO",
      "RB-IAAP"
     ]
    },
    {
     "role": "PDM",
     "stages": [
      "plan",
      "discover",
      "beta",
      "live"
     ],
     "works_with": [
      "OWN",
      "COO",
      "STW"
     ],
     "resp": [
      "Put DAM activities in the plan, the risk register and gate criteria",
      "Book data owners' time for decisions",
      "Track data asset risks alongside other programme risks"
     ],
     "refs": [
      "RB-GOVS002"
     ]
    },
    {
     "role": "SVO",
     "stages": [
      "discover",
      "alpha",
      "beta",
      "live"
     ],
     "works_with": [
      "OWN",
      "CAT",
      "DQL"
     ],
     "resp": [
      "Check the catalogue before collecting new data",
      "Design validation from the quality rules",
      "Show DAM evidence at service assessments"
     ],
     "refs": [
      "RB-SMROLES",
      "RB-SVCASSESS"
     ]
    },
    {
     "role": "ARC",
     "stages": [
      "alpha",
      "beta"
     ],
     "works_with": [
      "CUS",
      "CAT",
      "STW"
     ],
     "resp": [
      "Approve data models against agreed standards and identifiers",
      "Require documented schemas, open formats and an exit route",
      "Make metadata harvestable from new platforms"
     ],
     "refs": [
      "RB-TCOP",
      "RB-API",
      "RB-OPEN"
     ]
    },
    {
     "role": "MIG",
     "stages": [
      "beta",
      "retire"
     ],
     "works_with": [
      "OWN",
      "DQL",
      "CAT",
      "CUS"
     ],
     "resp": [
      "Profile quality before migration and reconcile after",
      "Keep catalogue entries and ownership in step as assets move",
      "Record lineage from old to new systems"
     ],
     "refs": [
      "RB-LEGACY",
      "RB-RETIRE"
     ]
    },
    {
     "role": "CML",
     "stages": [
      "plan",
      "discover",
      "retire"
     ],
     "works_with": [
      "OWN",
      "DPO",
      "COO"
     ],
     "resp": [
      "Write data ownership, metadata, quality reporting and exit into contracts",
      "Use model contract data and exit schedules",
      "Track contract end dates against the assets they touch"
     ],
     "refs": [
      "RB-MSC",
      "RB-SOURCING",
      "RB-PPN020"
     ]
    },
    {
     "role": "PMO",
     "stages": [
      "plan",
      "beta",
      "live"
     ],
     "works_with": [
      "COO",
      "BRD"
     ],
     "resp": [
      "Check DAM checkpoints at each gate",
      "Report data asset readiness to the senior responsible owner",
      "Feed lessons into the next programme"
     ],
     "refs": [
      "RB-IAAP",
      "RB-NISTA"
     ]
    }
   ],
   "blueprint": [
    {
     "stage": "plan",
     "user": "Programme board agrees scope and business case",
     "front": "Business case names critical assets and costs DAM work",
     "back": "Asset list drawn from the catalogue; risks added to the register",
     "data": "Data owners and the chief data officer agree priorities",
     "support": "Assurance plan includes DAM checkpoints"
    },
    {
     "stage": "discover",
     "user": "Team explores needs and existing data",
     "front": "Catalogue search before new collection",
     "back": "Contracts and data sharing options reviewed",
     "data": "Owners confirmed for each asset in scope",
     "support": "Commercial lead brings data clauses into the route to market"
    },
    {
     "stage": "alpha",
     "user": "Team designs and tests options",
     "front": "Data model and quality rules designed together",
     "back": "Schemas, identifiers and exit route approved by design authority",
     "data": "Stewards agree definitions and targets",
     "support": "DPIA started where personal data is involved"
    },
    {
     "stage": "beta",
     "user": "Team builds, migrates and goes live",
     "front": "New assets catalogued; validation built from rules",
     "back": "Migration profiled and reconciled; lineage recorded",
     "data": "Owners sign off quality against targets",
     "support": "Gate review checks DAM evidence"
    },
    {
     "stage": "live",
     "user": "Service runs; programme closes",
     "front": "Quality published to users",
     "back": "DQAP, runbook and contracts handed over",
     "data": "Business-as-usual owner and steward named",
     "support": "Asset included in the next annual return"
    },
    {
     "stage": "retire",
     "user": "Old systems are switched off",
     "front": "Users told what happens to their data",
     "back": "Assets migrated, archived or disposed of under records rules",
     "data": "Catalogue entries updated or closed",
     "support": "Records transferred where the Public Records Act applies"
    }
   ]
  }
 },
 "testing": {
  "intro": "This portal is ready for early testing with people who will use it. We want to know whether you can find what you need, understand it and act on it. It takes about 20 minutes. Choose the tasks closest to your role; you do not need to do them all.",
  "feedback_form": "testing.yml",
  "tasks": [
   {
    "id": "T-01",
    "roles": [
     "all"
    ],
    "title": "Find what the DAM Policy requires of your organisation",
    "start": "dam.html",
    "done": "You can name two 'must' requirements and the step that meets each one."
   },
   {
    "id": "T-02",
    "roles": [
     "cdo",
     "coo"
    ],
    "title": "Assess your organisation's maturity and download the result",
    "start": "capability-model.html#cm-self",
    "done": "You have a radar profile and a downloaded CSV file."
   },
   {
    "id": "T-03",
    "roles": [
     "cdo",
     "coo"
    ],
    "title": "Find what to build into a programme business case and its assurance plan",
    "start": "change.html#practices",
    "done": "You can list the actions for business cases and for assurance."
   },
   {
    "id": "T-04",
    "roles": [
     "own"
    ],
    "title": "Find what a data owner is accountable for and what happens when you move role",
    "start": "personas.html#persona-own",
    "done": "You know your duties and the steps to hand over ownership."
   },
   {
    "id": "T-05",
    "roles": [
     "stw",
     "dql"
    ],
    "title": "Find which sector supplements apply to an adult social care asset and download its quality rules",
    "start": "sectors.html#which",
    "done": "You have the social care supplement open and its rules file downloaded."
   },
   {
    "id": "T-06",
    "roles": [
     "cat"
    ],
    "title": "Find the metadata you must record, and the extra fields for geospatial data",
    "start": "cataloguing.html#metadata",
    "done": "You can list the 'must' properties and two extra geospatial fields."
   },
   {
    "id": "T-07",
    "roles": [
     "dql",
     "stw"
    ],
    "title": "Set a target and performance bands for a data quality rule",
    "start": "quality.html#method",
    "done": "You can say what target and bands you would set, and why."
   },
   {
    "id": "T-08",
    "roles": [
     "all"
    ],
    "title": "Find a learning route and the career pathway closest to your job",
    "start": "professions.html#pf-route",
    "done": "You have marked at least one learning resource as done."
   },
   {
    "id": "T-09",
    "roles": [
     "all"
    ],
    "title": "Look up what 'data steward' means and where stewards appear in the methods",
    "start": "knowledge.html",
    "done": "You found the definition and one step that names the steward."
   },
   {
    "id": "T-11",
    "roles": [
     "all"
    ],
    "title": "Find what your own team, such as digital, cyber, technology or commercial, should ask and do",
    "start": "perspectives.html",
    "done": "You can name two questions and one action for your team's lens."
   },
   {
    "id": "T-12",
    "roles": [
     "prg"
    ],
    "title": "Find the data responsibilities of a senior responsible owner and what to check at each programme stage",
    "start": "change.html#programme-roles",
    "done": "You can name three responsibilities and the stage each belongs to."
   },
   {
    "id": "T-13",
    "roles": [
     "all"
    ],
    "title": "Use the DAMA wheel to see which knowledge areas your role shapes, and one way records management overlaps",
    "start": "capability-model.html#cm-dama",
    "done": "You chose your role and can name two areas and one records counterpart."
   },
   {
    "id": "T-14",
    "roles": [
     "all"
    ],
    "title": "Pick two recommendations for working with other professions and a community to join",
    "start": "community.html",
    "done": "You marked two recommendations and opened one community page."
   },
   {
    "id": "T-10",
    "roles": [
     "all"
    ],
    "title": "Change the text size and colours, then move around using only the keyboard",
    "start": "index.html",
    "done": "You reached a playbook step without a mouse, with your display settings kept."
   }
  ]
 },
 "lenses": {
  "intro": "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.",
  "caps_order": [
   "gov",
   "cat",
   "dq"
  ],
  "items": [
   {
    "id": "L-DATA",
    "name": "Data",
    "icon": "database",
    "profs": [
     "PR-DD",
     "PR-AF",
     "PR-KIM"
    ],
    "cover_before": {
     "gov": "Strong",
     "cat": "Strong",
     "dq": "Strong"
    },
    "cover_now": {
     "gov": "Strong",
     "cat": "Strong",
     "dq": "Strong"
    },
    "means": "The policy's home lens: identify, describe, own and improve critical data assets, and report them.",
    "questions": [
     "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?"
    ],
    "actions": {
     "gov": [
      "Name an owner and steward for every critical asset.",
      "Run a data governance board that records decisions."
     ],
     "cat": [
      "Record the core metadata in a catalogue and report it to GDS.",
      "Use the cross-government Metadata Exchange Model terms."
     ],
     "dq": [
      "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."
    ],
    "cr": [
     "CR-05",
     "CR-06",
     "CR-07",
     "CR-08"
    ],
    "ch": [
     "CH-11",
     "CH-12"
    ],
    "refs": [
     "RB-DMAF",
     "RB-AIREADY"
    ],
    "gap": "Covered across the three playbooks, the capability model and the sector supplements."
   },
   {
    "id": "L-DIGI",
    "name": "Digital and service",
    "icon": "layers",
    "profs": [
     "PR-DD"
    ],
    "cover_before": {
     "gov": "Partial",
     "cat": "Partial",
     "dq": "Partial"
    },
    "cover_now": {
     "gov": "Strong",
     "cat": "Strong",
     "dq": "Strong"
    },
    "means": "Services create, change and consume critical data. Service teams decide what is collected, how it is validated and what users see.",
    "questions": [
     "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?"
    ],
    "actions": {
     "gov": [
      "Name the data owner as a stakeholder of the service from discovery.",
      "Show DAM evidence at service assessments."
     ],
     "cat": [
      "Catalogue data services and APIs alongside the data sets they expose.",
      "Publish API documentation that follows the government API standards."
     ],
     "dq": [
      "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."
    ],
    "cr": [
     "CR-12",
     "CR-22",
     "CR-25"
    ],
    "ch": [
     "CH-02",
     "CH-13"
    ],
    "refs": [
     "RB-SVC",
     "RB-SVCASSESS",
     "RB-API",
     "RB-RETIRE"
    ],
    "gap": "Strengthened in 1.6 with data service and API actions; user research with service teams is still to do (OR-04)."
   },
   {
    "id": "L-CYBER",
    "name": "Cyber and security",
    "icon": "shield-check",
    "profs": [
     "PR-CYB",
     "PR-SEC"
    ],
    "cover_before": {
     "gov": "Partial",
     "cat": "Gap",
     "dq": "Gap"
    },
    "cover_now": {
     "gov": "Strong",
     "cat": "Partial",
     "dq": "Partial"
    },
    "means": "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.",
    "questions": [
     "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?"
    ],
    "actions": {
     "gov": [
      "Link each critical asset to its CAF outcomes and to the SIRO's risk register.",
      "Agree recovery objectives with each data owner."
     ],
     "cat": [
      "Record classification, handling caveats and access rights accurately; scope depends on them.",
      "Keep the catalogue itself access-controlled where entries reveal sensitive holdings."
     ],
     "dq": [
      "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."
    ],
    "cr": [
     "CR-16",
     "CR-19",
     "CR-31"
    ],
    "ch": [
     "CH-07",
     "CH-15"
    ],
    "refs": [
     "RB-CAF",
     "RB-GCSS",
     "RB-GOVS007",
     "RB-SBD",
     "RB-NCSC10",
     "RB-NCSCIR",
     "RB-GSC"
    ],
    "gap": "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."
   },
   {
    "id": "L-TECH",
    "name": "Technology and architecture",
    "icon": "server",
    "profs": [
     "PR-DD"
    ],
    "cover_before": {
     "gov": "Partial",
     "cat": "Partial",
     "dq": "Partial"
    },
    "cover_now": {
     "gov": "Strong",
     "cat": "Strong",
     "dq": "Strong"
    },
    "means": "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.",
    "questions": [
     "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?"
    ],
    "actions": {
     "gov": [
      "Record the system of record and data platform for each asset.",
      "Apply the Technology Code of Practice and Cloud First when assets move."
     ],
     "cat": [
      "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."
     ],
     "dq": [
      "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."
    ],
    "cr": [
     "CR-11",
     "CR-12",
     "CR-13",
     "CR-14"
    ],
    "ch": [
     "CH-04",
     "CH-14"
    ],
    "refs": [
     "RB-TCOP",
     "RB-CLOUD",
     "RB-API",
     "RB-REFARCH",
     "RB-OPEN",
     "RB-NCSCCLOUD"
    ],
    "gap": "Strengthened in 1.6 with architecture, platform and automation actions and verified sources."
   },
   {
    "id": "L-COMM",
    "name": "Commercial and suppliers",
    "icon": "handshake",
    "profs": [
     "PR-COM",
     "PR-PD"
    ],
    "cover_before": {
     "gov": "Partial",
     "cat": "Gap",
     "dq": "Gap"
    },
    "cover_now": {
     "gov": "Strong",
     "cat": "Partial",
     "dq": "Partial"
    },
    "means": "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.",
    "questions": [
     "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?"
    ],
    "actions": {
     "gov": [
      "Map contracts to the critical assets they touch, with end dates.",
      "Use model contract schedules for data, security and exit."
     ],
     "cat": [
      "Make catalogue-ready metadata a contract deliverable, in the government's terms.",
      "Require suppliers to keep catalogue entries current when they change the data."
     ],
     "dq": [
      "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."
    ],
    "cr": [
     "CR-20",
     "CR-24",
     "CR-32"
    ],
    "ch": [
     "CH-06",
     "CH-16",
     "CH-01"
    ],
    "refs": [
     "RB-SOURCING",
     "RB-DDATPB",
     "RB-MSC",
     "RB-MTC20",
     "RB-PPN020",
     "RB-PA23",
     "RB-PA23G",
     "RB-GCLOUD",
     "RB-SPEND"
    ],
    "gap": "Was thin, with one practice. 1.6 adds a buying-routes practice and verified commercial sources. Needs review by a commercial professional."
   },
   {
    "id": "L-LEGACY",
    "name": "Legacy and technical debt",
    "icon": "construction",
    "profs": [
     "PR-DD",
     "PR-PD"
    ],
    "cover_before": {
     "gov": "Partial",
     "cat": "Partial",
     "dq": "Partial"
    },
    "cover_now": {
     "gov": "Strong",
     "cat": "Strong",
     "dq": "Strong"
    },
    "means": "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.",
    "questions": [
     "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?"
    ],
    "actions": {
     "gov": [
      "Prioritise exits where legacy risk, value and inequality overlap.",
      "Keep ownership in step as assets migrate."
     ],
     "cat": [
      "Start every exit from the data asset register, as the legacy guidance asks.",
      "Record schemas and lineage before the old system goes."
     ],
     "dq": [
      "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."
    ],
    "cr": [
     "CR-26",
     "CR-32",
     "CR-15"
    ],
    "ch": [
     "CH-04",
     "CH-05",
     "CH-14"
    ],
    "refs": [
     "RB-LEGACY",
     "RB-TECHDEBT",
     "RB-RETIRE",
     "RB-TNA",
     "RB-OPEN"
    ],
    "gap": "Covered by the delivery and change practices; 1.6 adds future-legacy prevention."
   }
  ]
 },
 "dama": {
  "intro": "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.",
  "hub": "DM-GOV",
  "areas": [
   {
    "id": "DM-GOV",
    "name": "Data governance",
    "dmbok": "Data governance",
    "desc": "Decision rights, accountability and policy for data across the organisation.",
    "im": "Information governance and the information asset owner role.",
    "uses": {
     "cdo": "Set the mandate and board; hold owners to account",
     "coo": "Run the governance cycle and the return",
     "own": "Make and record decisions for your assets",
     "stw": "Prepare decisions and keep definitions agreed",
     "cat": "Apply governance decisions in the catalogue",
     "dql": "Escalate quality risks to owners",
     "prg": "Bring programme decisions into the governance cycle",
     "buy": "Write data ownership and decision rights into contracts"
    },
    "dam": []
   },
   {
    "id": "DM-ARC",
    "name": "Data architecture",
    "dmbok": "Data architecture",
    "desc": "The blueprint of data across the organisation: where data lives, how it flows and which source is authoritative.",
    "im": "Information architecture and file plans.",
    "uses": {
     "cdo": "Sponsor a target data architecture",
     "coo": "Use it to find candidate assets",
     "own": "Agree the authoritative source for your data",
     "stw": "Map flows and dependencies",
     "cat": "Link catalogue entries to systems",
     "dql": "Trace quality problems to where data enters",
     "prg": "Approve designs against it",
     "buy": "Check tools fit the target architecture before you buy"
    },
    "dam": []
   },
   {
    "id": "DM-MOD",
    "name": "Data modelling and design",
    "dmbok": "Data modelling and design",
    "desc": "Defining the structure, meaning and relationships of data.",
    "im": "Records classification schemes.",
    "uses": {
     "cdo": "Expect agreed definitions for critical assets",
     "coo": "Collect definitions for the return",
     "own": "Approve the meaning of key data items",
     "stw": "Maintain definitions and the glossary",
     "cat": "Publish schemas with entries",
     "dql": "Write rules from the model",
     "prg": "Require documented models from suppliers",
     "buy": "Require suppliers to hand over documented data models"
    },
    "dam": []
   },
   {
    "id": "DM-OPS",
    "name": "Data storage and operations",
    "dmbok": "Data storage and operations",
    "desc": "Running the platforms that store data: backup, recovery, performance and retention.",
    "im": "Storage, preservation and disposal of records.",
    "uses": {
     "cdo": "Fund resilient platforms for critical data",
     "coo": "Know which platform holds each asset",
     "own": "Agree recovery objectives",
     "stw": "Check retention is applied",
     "cat": "Record system of record and location",
     "dql": "Check data after restore",
     "prg": "Plan platform moves and decommissioning",
     "buy": "Agree availability and recovery targets in service levels"
    },
    "dam": []
   },
   {
    "id": "DM-SEC",
    "name": "Data security",
    "dmbok": "Data security",
    "desc": "Protecting data from unauthorised access, change and loss, in line with classification.",
    "im": "Protective marking and access to records.",
    "uses": {
     "cdo": "Link critical assets to cyber risk",
     "coo": "Confirm classification is right before reporting",
     "own": "Accept residual risk for your assets",
     "stw": "Apply handling rules",
     "cat": "Record classification and access rights",
     "dql": "Treat odd quality drops as security signals",
     "prg": "Build security in from the start",
     "buy": "Require security that matches the classification, and incident notice"
    },
    "dam": []
   },
   {
    "id": "DM-INT",
    "name": "Data integration and interoperability",
    "dmbok": "Data integration and interoperability",
    "desc": "Moving and joining data between systems and organisations using shared standards.",
    "im": "Records exchange and transfer formats.",
    "uses": {
     "cdo": "Back open standards and shared identifiers",
     "coo": "Track sharing arrangements",
     "own": "Approve sharing of your data",
     "stw": "Map data to shared standards",
     "cat": "Catalogue APIs and data services",
     "dql": "Check data after each integration",
     "prg": "Avoid bespoke, closed integrations",
     "buy": "Ask for open standards and documented APIs at every boundary"
    },
    "dam": []
   },
   {
    "id": "DM-DOC",
    "name": "Document and content management",
    "dmbok": "Document and content management",
    "desc": "Managing unstructured information: documents, content and records.",
    "im": "The core of records management: capture, classification, retention and disposal.",
    "uses": {
     "cdo": "Align data and records strategies",
     "coo": "Reconcile the asset register with the information asset register",
     "own": "Own records and data consistently",
     "stw": "Apply retention schedules",
     "cat": "Record retention and disposal in entries",
     "dql": "Check documents behind key data items",
     "prg": "Plan records transfer when systems retire",
     "buy": "Make sure tools apply your retention schedule"
    },
    "dam": []
   },
   {
    "id": "DM-REF",
    "name": "Reference and master data",
    "dmbok": "Reference and master data",
    "desc": "Agreeing and maintaining the shared, authoritative versions of key entities and code lists.",
    "im": "Authority files and controlled vocabularies.",
    "uses": {
     "cdo": "Sponsor shared reference data",
     "coo": "Spot duplicate assets",
     "own": "Own the master version of key entities",
     "stw": "Maintain code lists and identifiers",
     "cat": "Link assets that share reference data",
     "dql": "Check codes against the reference list",
     "prg": "Reuse existing reference data, do not copy it",
     "buy": "Buy master data tools whose rules and data can be exported"
    },
    "dam": []
   },
   {
    "id": "DM-BI",
    "name": "Data warehousing and business intelligence",
    "dmbok": "Data warehousing and business intelligence",
    "desc": "Bringing data together for analysis, reporting and decisions.",
    "im": "Retention of reports and derived records.",
    "uses": {
     "cdo": "Use quality statements in decisions",
     "coo": "Report progress from catalogue data",
     "own": "Know where your data is reused",
     "stw": "Record derived data sets",
     "cat": "Catalogue analytical products that are critical",
     "dql": "Publish quality alongside reports",
     "prg": "Plan reporting needs early",
     "buy": "Make sure reporting tools read data through open routes"
    },
    "dam": []
   },
   {
    "id": "DM-META",
    "name": "Metadata management",
    "dmbok": "Metadata management",
    "desc": "Describing data so people and machines can find, understand and trust it.",
    "im": "Records metadata (ISO 23081) and the information asset register.",
    "uses": {
     "cdo": "Require complete metadata for the return",
     "coo": "Build the return from catalogue records",
     "own": "Approve entries for your assets",
     "stw": "Keep descriptions accurate",
     "cat": "Run the catalogue and harvest metadata",
     "dql": "Record quality metadata",
     "prg": "Make metadata a delivery output",
     "buy": "Test a full catalogue export and re-import before you sign"
    },
    "dam": []
   },
   {
    "id": "DM-DQ",
    "name": "Data quality",
    "dmbok": "Data quality",
    "desc": "Defining, measuring and improving how fit data is for its purposes.",
    "im": "Integrity and authenticity of records.",
    "uses": {
     "cdo": "Fund fixes where quality blocks outcomes",
     "coo": "Collate DQAP status",
     "own": "Set targets and accept risks",
     "stw": "Run checks and log issues",
     "cat": "Show quality in entries",
     "dql": "Run the DQAP",
     "prg": "Profile and reconcile in migrations",
     "buy": "Require quality rules you can read, export and run elsewhere"
    },
    "dam": []
   }
  ],
  "lifecycle": [
   {
    "data": "Plan and design",
    "records": "Plan what records are needed",
    "dam": "Identify critical assets; design metadata and rules",
    "who": "Owner, architect, records manager"
   },
   {
    "data": "Acquire or create",
    "records": "Create and capture",
    "dam": "Validate at collection; catalogue on creation",
    "who": "Service owner, steward"
   },
   {
    "data": "Store and secure",
    "records": "Store and protect",
    "dam": "Record classification, location and recovery objectives",
    "who": "Custodian, security"
   },
   {
    "data": "Use and share",
    "records": "Use and provide access",
    "dam": "Publish quality; record sharing arrangements",
    "who": "Owner, data protection officer"
   },
   {
    "data": "Maintain and improve",
    "records": "Review and update",
    "dam": "Annual review of entries and DQAP",
    "who": "Steward, data quality lead"
   },
   {
    "data": "Archive or dispose",
    "records": "Appraise, transfer or destroy",
    "dam": "Close or update entries; transfer where the Public Records Act applies",
    "who": "Records manager, owner"
   }
  ],
  "im_refs": [
   "RB-TNA",
   "RB-TNAIM",
   "RB-TNATRANS",
   "RB-PRA",
   "RB-ISO15489",
   "RB-ISO23081",
   "RB-KIM",
   "RB-PKSB"
  ],
  "cap_area": {
   "gov": "DM-GOV",
   "cat": "DM-META",
   "dq": "DM-DQ"
  },
  "supplement_area": {
   "SUP-ARC": [
    "DM-ARC",
    "DM-MOD"
   ]
  },
  "drilldown": {
   "intro": "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.",
   "effort_key": "Effort: S is days, M is one to two weeks, L depends on other teams. These are this portal's estimates, not measured.",
   "levels": [
    {
     "n": 1,
     "name": "Knowledge area",
     "now": "Built for all 11 areas: DAM capabilities, maturity topics, the records counterpart and how each role uses it.",
     "needs": "Nothing more for the MVP."
    },
    {
     "n": 2,
     "name": "Activities",
     "now": "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).",
     "needs": "Review of each area's activities by the profession that owns it."
    },
    {
     "n": 3,
     "name": "Tasks and products",
     "now": "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.",
     "needs": "Templates and learning modules for the new areas, starting with data architecture (BL-36)."
    },
    {
     "n": 4,
     "name": "Standards and evidence",
     "now": "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).",
     "needs": "Expert review of the standards mapped to the new activities."
    }
   ],
   "wheel_needs": [
    "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."
   ],
   "arc": {
    "summary": "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.",
    "parts": [
     {
      "part": "Purpose and scope",
      "now": "The supplement's summary",
      "needs": "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",
      "effort": "S"
     },
     {
      "part": "Step by step",
      "now": "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",
      "needs": "Review by architecture leads, then promotion to playbook steps",
      "effort": "S"
     },
     {
      "part": "Roles and who does what",
      "now": "A RACI for each of the 5 activities, led by the architect role",
      "needs": "Check the roles against the architect roles in the Government Digital and Data Profession Capability Framework",
      "effort": "S"
     },
     {
      "part": "Templates",
      "now": "T-CAT-4, the entity and relationship list; activities reuse T-CAT-1, T-CAT-2, T-GOV-3 and T-GOV-6",
      "needs": "Templates for a target architecture and architecture decision records",
      "effort": "M"
     },
     {
      "part": "Measures and escalation",
      "now": "A measure for each activity, such as the share of critical assets with a named authoritative source",
      "needs": "Escalation through the governance ladder",
      "effort": "S"
     },
     {
      "part": "Standards",
      "now": "Standards for each of the 5 activities, from the rulebook",
      "needs": "Checked by architecture leads",
      "effort": "S"
     },
     {
      "part": "Learning",
      "now": "None",
      "needs": "At least one learning module with an exercise",
      "effort": "M"
     },
     {
      "part": "Checks and tests",
      "now": "The supplement's checks",
      "needs": "Build validation, a site check and deliberate-break tests, as for the other playbooks",
      "effort": "S"
     },
     {
      "part": "Ownership and review",
      "now": "None",
      "needs": "Architecture leads, such as a design authority or the architecture community, agree to own and review it. This portal cannot set architecture standards.",
      "effort": "L"
     }
    ]
   },
   "phasing": "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."
   ],
   "backlog": [
    "BL-35",
    "BL-36"
   ]
  }
 },
 "joinup": {
  "intro": "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.",
  "recs": [
   {
    "id": "J-01",
    "title": "Keep one register of assets",
    "action": "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.",
    "who": [
     "COO",
     "IAO",
     "CAT"
    ],
    "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."
   },
   {
    "id": "J-02",
    "title": "Use one glossary",
    "action": "Publish one organisation glossary for data, records and security terms, linked to the cross-government vocabulary, and point catalogue entries to it.",
    "who": [
     "STW",
     "CAT"
    ],
    "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."
   },
   {
    "id": "J-03",
    "title": "Run one board for data, information and security risk",
    "action": "Bring the data governance board, information assurance and the senior information risk owner together, quarterly, with one agenda covering critical assets.",
    "who": [
     "CDO",
     "BRD",
     "IAO"
    ],
    "outcome": "Decisions on an asset consider data, records and security together.",
    "measure": "Decisions recorded per quarter that cite more than one discipline."
   },
   {
    "id": "J-04",
    "title": "Put DAM checkpoints in every programme",
    "action": "Agree with the programme office a standard set of DAM checks for business cases, gates and handover, and give programmes a named data contact.",
    "who": [
     "CDO",
     "PMO",
     "SRO"
    ],
    "outcome": "Programmes stop creating unowned, uncatalogued assets.",
    "measure": "Programmes closing with every in-scope asset owned, catalogued and quality-planned."
   },
   {
    "id": "J-05",
    "title": "Align retention with the data life cycle",
    "action": "Map retention schedules to critical assets and record retention and disposal in catalogue entries.",
    "who": [
     "IAO",
     "CAT",
     "OWN"
    ],
    "outcome": "Data is kept as long as needed and no longer, with evidence.",
    "measure": "Critical assets with a recorded retention rule."
   },
   {
    "id": "J-06",
    "title": "Learn together",
    "action": "Run a shared induction for owners, stewards, information asset owners and programme leads, using the recommended curriculum and this portal's modules.",
    "who": [
     "CDO",
     "COO"
    ],
    "outcome": "People in different professions use the same method and language.",
    "measure": "Owners and stewards who completed the shared induction."
   },
   {
    "id": "J-07",
    "title": "Join the right communities",
    "action": "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.",
    "who": [
     "COO",
     "STW",
     "DQL",
     "CAT"
    ],
    "outcome": "Practice spreads across organisations instead of being reinvented.",
    "measure": "Roles with a named community; lessons shared per quarter."
   },
   {
    "id": "J-08",
    "title": "Rehearse an incident together",
    "action": "Run a joint exercise where a critical asset is corrupted or exposed, involving security, records, data quality and the owner.",
    "who": [
     "OWN",
     "CUS",
     "DQL",
     "DPO"
    ],
    "outcome": "Everyone knows their part in recovering and re-trusting an asset.",
    "measure": "Critical assets covered by a tested recovery and quality check."
   },
   {
    "id": "J-09",
    "title": "Share contract clauses",
    "action": "Keep a shared library of data, metadata, quality and exit clauses with the commercial team and reuse it in every relevant procurement.",
    "who": [
     "CML",
     "OWN",
     "DPO"
    ],
    "outcome": "Suppliers face the same data obligations everywhere.",
    "measure": "New contracts touching critical assets that use the shared clauses."
   },
   {
    "id": "J-10",
    "title": "Report one set of measures",
    "action": "Combine catalogue completeness, DQAP status, records compliance and security assurance for critical assets into one quarterly view.",
    "who": [
     "COO",
     "BRD"
    ],
    "outcome": "Leaders see one picture of how well critical assets are managed.",
    "measure": "Quarterly view produced and discussed at the board."
   }
  ],
  "communities": [
   {
    "name": "Chief Data Officer Council",
    "what": "Oversees implementation of the DAM Policy across government.",
    "url": "https://www.gov.uk/government/publications/data-asset-management-policy-in-government/data-asset-management-policy-in-government#oversight-and-implementation-of-the-policy",
    "for_": [
     "cdo"
    ],
    "prov": "V"
   },
   {
    "name": "Government Data Quality Hub",
    "what": "Data quality guidance, tools and support from the Office for National Statistics.",
    "url": "https://www.gov.uk/government/organisations/government-data-quality-hub",
    "for_": [
     "dql",
     "stw"
    ],
    "prov": "V"
   },
   {
    "name": "Government Data Quality Community",
    "what": "Cross-government community for people working on data quality.",
    "url": "https://www.gov.uk/government/news/introducing-the-government-data-quality-community",
    "for_": [
     "dql",
     "stw"
    ],
    "prov": "V"
   },
   {
    "name": "Data Standards Authority",
    "what": "Sets and promotes government data standards.",
    "url": "https://www.gov.uk/government/groups/data-standards-authority",
    "for_": [
     "cat",
     "stw"
    ],
    "prov": "V"
   },
   {
    "name": "Knowledge and Information Management profession group",
    "what": "Community for records, information and knowledge managers.",
    "url": "https://khub.net/group/government-knowledge-and-information-management-profession",
    "for_": [
     "coo",
     "cat"
    ],
    "prov": "V"
   },
   {
    "name": "Data engineering community",
    "what": "Cross-government community for data engineers.",
    "url": "https://www.gov.uk/service-manual/communities/data-engineering-community",
    "for_": [
     "dql",
     "cat"
    ],
    "prov": "V"
   },
   {
    "name": "Performance and data analysis community",
    "what": "Community for performance analysts and data analysts.",
    "url": "https://www.gov.uk/service-manual/communities/performance-and-data-analysis-community",
    "for_": [
     "dql"
    ],
    "prov": "V"
   },
   {
    "name": "API community",
    "what": "Community for people building and running government APIs.",
    "url": "https://www.gov.uk/service-manual/communities/application-programming-interface-community",
    "for_": [
     "cat",
     "prg"
    ],
    "prov": "V"
   },
   {
    "name": "Technical architecture community",
    "what": "Community for technical and data architects.",
    "url": "https://www.gov.uk/service-manual/communities/technology-community-technical-architecture",
    "for_": [
     "prg",
     "cat"
    ],
    "prov": "V"
   },
   {
    "name": "Data and AI ethics community",
    "what": "Community for data and AI ethics practitioners.",
    "url": "https://www.gov.uk/service-manual/communities/data-and-artificial-intelligence-ethics-community",
    "for_": [
     "own",
     "stw"
    ],
    "prov": "V"
   },
   {
    "name": "AI for government knowledge and information management community",
    "what": "Where KIM professionals discuss AI and information.",
    "url": "https://www.gov.uk/service-manual/communities/ai-for-government-knowledge-information-management-community",
    "for_": [
     "coo",
     "cat"
    ],
    "prov": "V"
   },
   {
    "name": "Digital buying community",
    "what": "Community for people buying digital, data and technology.",
    "url": "https://www.gov.uk/service-manual/communities/digital-buying-community",
    "for_": [
     "prg"
    ],
    "prov": "V"
   },
   {
    "name": "Standards and assurance community",
    "what": "Community for service assessors and assurance practitioners.",
    "url": "https://www.gov.uk/service-manual/communities/standards-and-assurance-community",
    "for_": [
     "prg"
    ],
    "prov": "V"
   },
   {
    "name": "Product and service community",
    "what": "Community for product managers and service owners.",
    "url": "https://www.gov.uk/service-manual/communities/product-and-service-community",
    "for_": [
     "prg",
     "own"
    ],
    "prov": "V"
   },
   {
    "name": "Analysis Function",
    "what": "The cross-government network for analysts, including statisticians.",
    "url": "https://analysisfunction.civilservice.gov.uk/",
    "for_": [
     "dql"
    ],
    "prov": "V"
   }
  ]
 },
 "tours": [
  {
   "id": "home",
   "page": "index",
   "title": "Getting around the portal",
   "steps": [
    {
     "sel": "#gbar",
     "title": "Portal sections",
     "text": "The bar lists every part of the portal. Playbooks and Frameworks open menus of related pages. On narrow screens extra items fold into More sections."
    },
    {
     "sel": "[data-open-search]",
     "title": "Search",
     "text": "Search everything: steps, requirements, glossary terms, modules and more. Press Ctrl and K, or the forward slash key, from any page."
    },
    {
     "sel": "#display-toggle",
     "title": "Display options",
     "text": "Make text larger, add line spacing or switch between light and dark colours. Your choices stay in this browser."
    },
    {
     "sel": "#drawer",
     "title": "On this page",
     "text": "The panel on the left lists the sections of the page you are on, with counts. Use the Page contents switch to hide or show it."
    },
    {
     "sel": "#role",
     "title": "Start from your role",
     "text": "Pick the role closest to yours for a route through learning, preparation, doing, reporting and improving."
    },
    {
     "sel": "#capabilities",
     "title": "The three capabilities",
     "text": "Data governance, data cataloguing and data quality each have a step-by-step playbook. Each section of the portal has its own colour."
    },
    {
     "sel": ".share",
     "title": "Share this page",
     "text": "Copy a link, email it or share it in Microsoft Teams. Every page has this button."
    }
   ]
  },
  {
   "id": "playbook",
   "page": "governance",
   "title": "Using a playbook",
   "steps": [
    {
     "sel": "[role=tablist]",
     "title": "Tabs",
     "text": "Each playbook is split into tabs: overview, step by step, roles, templates, measures, sectors and sources."
    },
    {
     "sel": "#tab-method",
     "title": "Step by step",
     "text": "The method, one step at a time. Each step says who does what, what you need and what you get.",
     "click": "#tab-method"
    },
    {
     "sel": ".sbs",
     "title": "Track your progress",
     "text": "Tick each step as you finish it. Progress shows on your role route and stays in this browser only."
    },
    {
     "sel": "#tab-sector-supplements",
     "title": "Sector supplements",
     "text": "If your data is health, social care, geospatial or another specialist kind, this tab shows what each sector supplement adds.",
     "click": "#tab-sector-supplements"
    },
    {
     "sel": "#drawer",
     "title": "Jump within the page",
     "text": "The panel on the left jumps straight to any step or section."
    }
   ]
  },
  {
   "id": "model",
   "page": "capability-model",
   "title": "The capability model",
   "steps": [
    {
     "sel": ".cr-house",
     "title": "Capabilities in six clusters",
     "text": "Every capability the policy and related guidance need. Green, blue and purple edges show whether the policy states it, implies it or not at all."
    },
    {
     "sel": "#tab-cm-map",
     "title": "Requirements map",
     "text": "Filter capabilities and follow the signposts to the exact GOV.UK sections.",
     "click": "#tab-cm-map"
    },
    {
     "sel": ".dama-wheel",
     "title": "DAMA wheel",
     "text": "Knowledge areas around data governance. Choose your role to see how each area applies to you.",
     "click": "#tab-cm-dama"
    },
    {
     "sel": "#sa-chart",
     "title": "Self-assessment",
     "text": "Choose the level closest to your organisation to draw a profile you can download.",
     "click": "#tab-cm-self"
    }
   ]
  },
  {
   "id": "sectors",
   "page": "sectors",
   "title": "Sector supplements",
   "steps": [
    {
     "sel": "#which",
     "title": "Find what applies",
     "text": "Tick what is true of your asset to see which supplements apply."
    },
    {
     "sel": "#all",
     "title": "All supplements",
     "text": "Filter supplements by priority and capability."
    },
    {
     "sel": "#rule-library",
     "title": "Quality rules",
     "text": "Every sector quality rule, downloadable to run in the Data Quality Commons kit."
    }
   ]
  },
  {
   "id": "change",
   "page": "change",
   "title": "Delivery and change",
   "steps": [
    {
     "sel": "#gaps",
     "title": "What the policy leaves to you",
     "text": "Capabilities the policy relies on but does not state, and where this page helps."
    },
    {
     "sel": "#lifecycle",
     "title": "Across the life cycle",
     "text": "Where data asset management fits at each stage of a programme."
    },
    {
     "sel": "#programme-roles",
     "title": "Programme roles",
     "text": "Data responsibilities for senior responsible owners, programme managers, architects and others."
    },
    {
     "sel": "#practices",
     "title": "Practices",
     "text": "Actions you can tick off, filtered by business as usual or change, and by stage."
    }
   ]
  },
  {
   "id": "tooling",
   "page": "tooling",
   "title": "Tools and interoperability",
   "steps": [
    {
     "sel": "#principles",
     "title": "Five principles",
     "text": "The rules of thumb behind everything on this page, starting with owning your metadata."
    },
    {
     "sel": "#tool-list",
     "title": "Kinds of tool",
     "text": "Each kind of tool, the DAMA area it supports, the open standards that connect it and the question to ask a supplier."
    },
    {
     "sel": "#tab-tl-pairs",
     "click": "#tab-tl-pairs",
     "title": "Working together",
     "text": "Which tools need to exchange what, and how mature the open routes are."
    },
    {
     "sel": "#tab-tl-procure",
     "click": "#tab-tl-procure",
     "title": "Procurement",
     "text": "Six steps and the RFI questions, downloadable as CSV."
    }
   ]
  }
 ],
 "ms_form": {
  "url": "https://forms.cloud.microsoft/Pages/ResponsePage.aspx?id=BXCsy8EC60O0l-ZJLRst2OgGVkJSDelPgquubNu4dJpUNjc2Ukw2N1hMTTc1WE5DQTE5QkZEMkVWSi4u",
  "title": "Give feedback privately (Microsoft Forms)",
  "note": "A private route: only the people maintaining this prototype see your answers, you do not need to sign in or have a GitHub account, and your response is anonymous unless you choose to give your email address and organisation, for example to ask for a reply or a copy of your answers. It takes 3 to 5 minutes, and the page or task you came from is filled in for you.",
  "prefill": {
   "where": "r3660656614cc47b499a593f8ceb06013",
   "topic": "r97d3f7fae84f4d3ab28473ec4148a7e2",
   "topics": {
    "question": "A question",
    "problem": "Something is wrong or out of date",
    "accessibility": "An accessibility problem",
    "idea": "An idea or improvement",
    "task": "Feedback on a test task",
    "other": "Something else"
   }
  },
  "privacy": [
   "Everything except your role and your feedback is optional.",
   "Your response is anonymous unless you choose to give your email address and organisation. Microsoft Forms does not record your name or account, because the form does not ask you to sign in.",
   "If you give your email address, we use it only to reply about that feedback or to send you a copy of your answers, as you asked. We do not share it, publish it or add it to a mailing list.",
   "Only the people maintaining this prototype can see responses. They are held in Microsoft Forms, in the government Microsoft 365 account the maintainers work in.",
   "How long responses and contact details are kept, and who is the data controller, are to be confirmed with the data protection officer (open item OR-02). Until then, if you gave your email address and want it deleted, send the form again with \"delete my details\" and the same email address, and we will."
  ]
 },
 "reuse": {
  "intro": "The portal is built to be reused. Pick the approach that fits how your organisation shares knowledge, from a simple link on your intranet to your own branded copy, an AI assistant or an integration through the Model Context Protocol (MCP). Content is published under the Open Government Licence and code under the MIT licence.",
  "approaches": [
   {
    "id": "U-01",
    "title": "Link from your intranet",
    "icon": "link",
    "group": "Link and embed",
    "effort": "low",
    "what": "Stable addresses for every page, tab, step and capability.",
    "how": [
     "Link to a page, or to a section with its anchor, for example governance.html#method.",
     "Share links with the Share button on any page.",
     "Point staff to the role routes and the testing page."
    ],
    "when": "You want staff to use the guidance as it is, always current.",
    "cautions": [
     "Links go to a prototype that is not official guidance; say so on your intranet."
    ]
   },
   {
    "id": "U-02",
    "title": "Embed pages in your intranet or Teams",
    "icon": "layers",
    "group": "Link and embed",
    "effort": "low",
    "what": "Show portal pages inside SharePoint, an intranet page or a Microsoft Teams tab.",
    "how": [
     "Add a web part or a Teams website tab pointing at a page address.",
     "Choose pages that work well on their own, such as a playbook or the self-assessment.",
     "Keep the prototype banner visible."
    ],
    "when": "You want the content inside the tools people already use.",
    "cautions": [
     "Progress and display choices are kept per browser, so they do not follow people between devices."
    ]
   },
   {
    "id": "U-03",
    "title": "Read-only data API",
    "icon": "database",
    "group": "Data and APIs",
    "effort": "low",
    "what": "Every dataset is a stable file you can fetch from code: JSON, CSV, Turtle and YAML, with cross-site access allowed.",
    "how": [
     "Start from the catalogue at data/catalogue.jsonld.",
     "Fetch data/playbooks.json for the full content, or a single CSV.",
     "Pin to a release by recording the version in the catalogue."
    ],
    "when": "You want to build your own views, dashboards or tools on the content.",
    "cautions": [
     "Files change with each release; check the version and the What is new page before relying on a field."
    ]
   },
   {
    "id": "U-04",
    "title": "Harvest into a data catalogue",
    "icon": "share-2",
    "group": "Data and APIs",
    "effort": "low",
    "what": "A DCAT 3 catalogue other catalogues can harvest, such as CKAN or your own metadata platform.",
    "how": [
     "Point your harvester at data/catalogue.jsonld or data/catalogue.ttl.",
     "Map dataset identifiers to your own scheme."
    ],
    "when": "You run a catalogue and want the playbook datasets listed alongside your own.",
    "cautions": [
     "Treat harvested entries as reference material, not as your own critical assets."
    ]
   },
   {
    "id": "U-05",
    "title": "Load into enterprise content and collaboration tools",
    "icon": "library",
    "group": "Enterprise content",
    "effort": "medium",
    "what": "Bring templates, checklists and actions into SharePoint lists, Confluence, Planner or your tracker.",
    "how": [
     "Import a CSV, such as change-checklist.csv or templates.csv, into a list or board.",
     "Link each item back to its page for the full guidance.",
     "Agree an owner to refresh it after each release."
    ],
    "when": "You want teams to work from tasks and templates in their own tools.",
    "cautions": [
     "Copies go out of date; note the version you imported."
    ]
   },
   {
    "id": "U-06",
    "title": "White-label your own copy",
    "icon": "pencil-line",
    "group": "Adapt and brand",
    "effort": "medium",
    "what": "Run your own branded copy with your organisation's name, colours, tone and extra content.",
    "how": [
     "Fork the repository on GitHub.",
     "Change the title, contact form and site address in the content file, and colours in the style sheet.",
     "Edit or add content in the content files; the build checks every reference.",
     "Publish with the included workflow on your own GitHub Pages or web server."
    ],
    "when": "You need the guidance in your own house style, or with local procedures added.",
    "cautions": [
     "Keep the attribution statement and the licences.",
     "Your copy no longer gets updates automatically; merge new releases deliberately."
    ]
   },
   {
    "id": "U-07",
    "title": "Adapt for your audiences and language",
    "icon": "languages",
    "group": "Adapt and brand",
    "effort": "medium",
    "what": "Tailor wording, examples and depth for particular audiences, or translate, for example into Welsh.",
    "how": [
     "Copy the content files and adjust text, keeping identifiers so links still work.",
     "Use the plain English and style checks in the build to keep quality up."
    ],
    "when": "Your audiences need different language, tone or examples.",
    "cautions": [
     "Translations need a named owner to keep them in step with releases."
    ]
   },
   {
    "id": "U-08",
    "title": "Ask an AI assistant about the portal",
    "icon": "brain",
    "group": "AI and integrations",
    "effort": "low",
    "what": "Use an AI assistant or chatbot to answer questions from the portal, alongside the built-in search.",
    "how": [
     "Give the assistant the address of llms.txt, a short guide written for AI tools, or llms-full.txt with the full text.",
     "Or add the portal website, or data/playbooks.json, as a knowledge source in a tool such as Microsoft Copilot Studio.",
     "Ask it to cite the page each answer comes from."
    ],
    "when": "You want people to ask questions in their own words.",
    "cautions": [
     "AI answers can be wrong; check them against the page cited, and against GOV.UK, which is the authority.",
     "Do not paste personal or sensitive data into public AI tools."
    ]
   },
   {
    "id": "U-09",
    "title": "Connect through the Model Context Protocol (MCP)",
    "icon": "network",
    "group": "AI and integrations",
    "effort": "medium",
    "what": "A small reference MCP server in the repository lets AI assistants search the portal and fetch capabilities, requirements, practices and sector rules as structured data, with links to their pages.",
    "how": [
     "Run integrations/mcp/server.py with Python 3; it needs no extra packages.",
     "Add it as an MCP server in an MCP-compatible assistant.",
     "Point it at the live site or at a local copy of data/playbooks.json."
    ],
    "when": "You want an assistant or agent to use the portal's content as a tool, with sources.",
    "cautions": [
     "It is a reference implementation for testing, not a supported service.",
     "Host it inside your own environment if you add internal content."
    ]
   },
   {
    "id": "U-10",
    "title": "Connectors, add-ons and plugins",
    "icon": "sliders-horizontal",
    "group": "AI and integrations",
    "effort": "medium",
    "what": "Use the open data and the MCP server as the basis for a connector, add-on or plugin in your organisation's platforms.",
    "how": [
     "Use the catalogue and JSON files as the data source.",
     "Wrap the MCP server or the files in your platform's connector or plugin format.",
     "Register it through your organisation's approval process for integrations."
    ],
    "when": "You want the content inside a business application or an AI assistant your organisation already uses.",
    "cautions": [
     "Follow your organisation's rules for approving third-party integrations."
    ]
   }
  ]
 },
 "tooling": {
  "intro": "Most organisations run several tools for data asset management, often from different suppliers, and many are offered a bundled suite. This page sets out the kinds of tool involved, the open standards and patterns that let them work together, where bundles and contracts create lock-in, and questions to ask in a request for information (RFI) or tender, framed by what the DAM Policy needs. It names no products and endorses none; for named products and a fuller question builder, see the related links at the end of this page.",
  "principles": [
   "Your metadata, glossary, quality rules, lineage and results are your data. Make sure you can get all of them out, in open formats, at any time and at no extra charge.",
   "Prefer open standards at the boundaries between tools, even when the tools come from one supplier. That keeps the option to replace one part without replacing the rest.",
   "Buy capabilities, not bundles. Price, evaluate and be able to exit each capability separately.",
   "Prove interoperability before you sign. A round-trip test with your own data is worth more than a list of connectors.",
   "Plan the exit at the start: cost it, time it and write it into the contract and business case."
  ],
  "categories": [
   {
    "id": "TL-CAT",
    "name": "Data catalogue and metadata management",
    "icon": "library-big",
    "dama": [
     "DM-META"
    ],
    "caps": [
     "cat"
    ],
    "what": "Records what data assets exist, what they mean, who owns them and how they can be used; harvests technical metadata from data platforms.",
    "standards": [
     "RB-DCAT",
     "RB-METASTD",
     "RB-SKOS",
     "RB-EGERIA"
    ],
    "patterns": [
     "IP-HARVEST",
     "IP-API",
     "IP-FILE",
     "IP-EVENT"
    ],
    "ask": "Can every catalogue record, including custom fields, owners and classifications, be exported as DCAT and imported into another catalogue without loss?"
   },
   {
    "id": "TL-GLOS",
    "name": "Business glossary and vocabularies",
    "icon": "book-open",
    "dama": [
     "DM-META",
     "DM-GOV"
    ],
    "caps": [
     "gov",
     "cat"
    ],
    "what": "Holds agreed business terms, definitions, synonyms and hierarchies, and links them to data assets.",
    "standards": [
     "RB-SKOS"
    ],
    "patterns": [
     "IP-FILE",
     "IP-API"
    ],
    "ask": "Can the glossary be exported and imported as SKOS, keeping broader and narrower terms and links to assets?"
   },
   {
    "id": "TL-DQ",
    "name": "Data quality profiling, rules and monitoring",
    "icon": "gauge",
    "dama": [
     "DM-DQ"
    ],
    "caps": [
     "dq"
    ],
    "what": "Profiles data, runs quality rules, scores dimensions, raises issues and tracks remediation.",
    "standards": [
     "RB-DQV",
     "RB-ODCS",
     "RB-CSVW"
    ],
    "patterns": [
     "IP-API",
     "IP-CONTRACT",
     "IP-EVENT",
     "IP-EMBED"
    ],
    "ask": "Are rules held in a readable, exportable form, and can results be published as DQV or through an open API for a catalogue to show?"
   },
   {
    "id": "TL-LIN",
    "name": "Lineage and data observability",
    "icon": "workflow",
    "dama": [
     "DM-META",
     "DM-INT"
    ],
    "caps": [
     "cat",
     "dq"
    ],
    "what": "Shows where data comes from, how it moves and changes, and whether pipelines ran as expected.",
    "standards": [
     "RB-OLINEAGE",
     "RB-PROVO"
    ],
    "patterns": [
     "IP-EVENT",
     "IP-HARVEST"
    ],
    "ask": "Does the tool emit and accept OpenLineage events, including from pipelines and platforms the supplier does not own?"
   },
   {
    "id": "TL-MDM",
    "name": "Reference and master data management",
    "icon": "layers",
    "dama": [
     "DM-REF"
    ],
    "caps": [
     "gov",
     "dq"
    ],
    "what": "Holds the golden record for entities such as organisations, people, places and products, and the reference lists that other systems share.",
    "standards": [
     "RB-SKOS",
     "RB-UPRN",
     "RB-API"
    ],
    "patterns": [
     "IP-API",
     "IP-EVENT",
     "IP-FILE"
    ],
    "ask": "Can master and reference data, with match and survivorship rules and history, be extracted in an open format and served through a documented API?"
   },
   {
    "id": "TL-POL",
    "name": "Governance workflow, policy and access",
    "icon": "shield-check",
    "dama": [
     "DM-GOV",
     "DM-SEC"
    ],
    "caps": [
     "gov"
    ],
    "what": "Manages stewardship tasks, approvals, data sharing requests, classification and access policies.",
    "standards": [
     "RB-OAS",
     "RB-GSC",
     "RB-DSGF"
    ],
    "patterns": [
     "IP-API",
     "IP-IDENTITY",
     "IP-EVENT"
    ],
    "ask": "Can classifications and access policies be read by other tools through an API, and does the tool use your identity provider rather than its own user store?"
   },
   {
    "id": "TL-CONTRACT",
    "name": "Data contracts and data products",
    "icon": "file-text",
    "dama": [
     "DM-INT",
     "DM-ARC"
    ],
    "caps": [
     "cat",
     "dq"
    ],
    "what": "Describes what a data producer promises consumers, such as schema, quality thresholds, owners and service levels.",
    "standards": [
     "RB-ODCS",
     "RB-ODPS"
    ],
    "patterns": [
     "IP-CONTRACT",
     "IP-FILE"
    ],
    "ask": "Are contracts stored as ODCS files you can keep in your own repository, and can more than one tool enforce them?"
   },
   {
    "id": "TL-REC",
    "name": "Records and content management",
    "icon": "archive",
    "dama": [
     "DM-DOC"
    ],
    "caps": [
     "gov",
     "cat"
    ],
    "what": "Manages documents and records, retention and disposal, and transfer to an archive.",
    "standards": [
     "RB-ISO15489",
     "RB-ISO23081",
     "RB-TNATRANS"
    ],
    "patterns": [
     "IP-API",
     "IP-FILE"
    ],
    "ask": "Can retention and disposal decisions and record metadata be shared with the data catalogue, so a data asset and its records follow one schedule?"
   },
   {
    "id": "TL-AI",
    "name": "AI assistants and search over metadata",
    "icon": "brain",
    "dama": [
     "DM-META"
    ],
    "caps": [
     "cat"
    ],
    "what": "Lets people ask questions of the catalogue, glossary and quality results in plain language.",
    "standards": [
     "RB-MCPSPEC",
     "RB-OAS"
    ],
    "patterns": [
     "IP-AI",
     "IP-API"
    ],
    "ask": "Can an assistant your organisation already approves read the catalogue through an open protocol or documented API, respecting the same access rules?"
   }
  ],
  "patterns": [
   {
    "id": "IP-HARVEST",
    "name": "Scan and harvest",
    "how": "The catalogue or lineage tool connects to a database, warehouse, file store or business intelligence tool and reads its technical metadata on a schedule.",
    "when": "Building and refreshing the inventory of technical assets.",
    "risk": "medium",
    "watch": "Connectors are often licensed separately, priced per source, or maintained only for the supplier's own platform. Ask who maintains each one and how quickly it follows new versions."
   },
   {
    "id": "IP-API",
    "name": "Documented API",
    "how": "One tool reads or writes another's records through a published API, described in OpenAPI, with the same access controls as the user interface.",
    "when": "Showing quality scores in the catalogue, creating issues, syncing owners or terms.",
    "risk": "low",
    "watch": "Check rate limits, whether every object is available through the API (not only some), and whether API calls are charged."
   },
   {
    "id": "IP-EVENT",
    "name": "Events and webhooks",
    "how": "A tool publishes an event when something changes, such as a rule failing, a pipeline running or an asset being classified, and others subscribe.",
    "when": "Near real-time alerts, lineage capture and keeping several tools in step.",
    "risk": "low",
    "watch": "Prefer open event formats such as OpenLineage over supplier-specific payloads."
   },
   {
    "id": "IP-FILE",
    "name": "Open file exchange",
    "how": "Export and import in open formats such as DCAT (JSON-LD or Turtle), SKOS, CSV with CSVW, or ODCS YAML.",
    "when": "Migration, exit, bulk loading, publishing and sharing with other organisations.",
    "risk": "low",
    "watch": "Exports that drop custom fields, history or links are a form of lock-in. Test a full round trip."
   },
   {
    "id": "IP-CONTRACT",
    "name": "Contract-driven checks",
    "how": "Producers publish a data contract; quality and pipeline tools read the same file to check data, and the catalogue shows it.",
    "when": "Agreeing what consumers can rely on, and checking it automatically.",
    "risk": "low",
    "watch": "Contract formats are still maturing; keep contracts in your own repository, not only inside a tool."
   },
   {
    "id": "IP-EMBED",
    "name": "Embedded views",
    "how": "One tool shows another's information in place, for example quality results on a catalogue page.",
    "when": "Giving users one place to look without copying data.",
    "risk": "medium",
    "watch": "Embedding through a supplier's private integration can hide a dependency that breaks when either tool changes."
   },
   {
    "id": "IP-IDENTITY",
    "name": "Shared identity and access",
    "how": "All tools sign users in through your identity provider and take roles and groups from it.",
    "when": "Always. It keeps ownership and stewardship roles consistent across tools.",
    "risk": "low",
    "watch": "Some products charge more for single sign-on or automated user provisioning; ask early."
   },
   {
    "id": "IP-AI",
    "name": "AI access through an open protocol",
    "how": "An assistant reads the catalogue, glossary and quality results through a documented API or a Model Context Protocol server.",
    "when": "Plain-language questions over metadata, with answers that cite their source.",
    "risk": "medium",
    "watch": "Make sure the assistant respects access rules and that prompts and answers stay in your approved environment."
   }
  ],
  "pairs": [
   {
    "between": "Catalogue and data quality",
    "flows": "Quality scores, rule results and open issues shown against each asset; asset owners and definitions used by quality rules.",
    "open": "DQV for results, ODCS for rules and thresholds, documented APIs.",
    "maturity": "Emerging",
    "fallback": "Scheduled export of results as CSV, matched on a shared asset identifier.",
    "watch": "Without a shared, persistent asset identifier the two tools drift apart."
   },
   {
    "between": "Catalogue and lineage",
    "flows": "Where data comes from, where it goes and which jobs change it.",
    "open": "OpenLineage events, PROV-O.",
    "maturity": "Established",
    "fallback": "Harvest lineage from the platform's own logs.",
    "watch": "Lineage limited to one supplier's platform hides the rest of the journey."
   },
   {
    "between": "Catalogue and glossary",
    "flows": "Business terms linked to assets and columns.",
    "open": "SKOS for the vocabulary; DCAT themes and keywords for links.",
    "maturity": "Established",
    "fallback": "CSV term lists with stable identifiers.",
    "watch": "Terms stored as free text cannot be reused elsewhere."
   },
   {
    "between": "Catalogue and master data",
    "flows": "Which assets hold the golden record and which are copies; reference lists used in metadata.",
    "open": "Documented APIs; SKOS for reference lists.",
    "maturity": "Vendor-specific",
    "fallback": "Record the authoritative source as catalogue metadata.",
    "watch": "Bundled master data and catalogue modules often share a private model that is hard to separate."
   },
   {
    "between": "Catalogue and records management",
    "flows": "Retention, disposal and record metadata for data assets that are also records.",
    "open": "Documented APIs; records metadata standards.",
    "maturity": "Vendor-specific",
    "fallback": "A shared retention schedule identifier recorded in both tools.",
    "watch": "Two retention schedules for the same information leads to unlawful keeping or early disposal."
   },
   {
    "between": "Data quality and pipelines",
    "flows": "Rules run as data moves; failed checks stop or flag a load.",
    "open": "ODCS contracts; OpenLineage run events.",
    "maturity": "Emerging",
    "fallback": "Rules called from the pipeline through a documented API.",
    "watch": "Rules written in a proprietary language cannot move with you."
   },
   {
    "between": "Governance workflow and identity and access",
    "flows": "Owners, stewards, approvals and access decisions.",
    "open": "Your identity provider's standard protocols; documented APIs.",
    "maturity": "Established",
    "fallback": "Scheduled sync of roles from the human resources or identity system.",
    "watch": "Local user stores create orphaned owners when people leave."
   },
   {
    "between": "Catalogue and other organisations",
    "flows": "Published and shared dataset descriptions, harvested by national catalogues.",
    "open": "DCAT, schema.org Dataset and the Metadata Exchange Model.",
    "maturity": "Established",
    "fallback": "Publish a CSV catalogue with documented columns.",
    "watch": "Private catalogue formats block harvesting by data.gov.uk and the National Data Library."
   },
   {
    "between": "Catalogue and AI assistants",
    "flows": "Questions answered from catalogue, glossary and quality information, with links back.",
    "open": "Documented APIs; Model Context Protocol.",
    "maturity": "Emerging",
    "fallback": "Publish a text export for an approved assistant to index.",
    "watch": "An assistant that bypasses catalogue access rules can disclose restricted metadata."
   }
  ],
  "bundles": {
   "pros": [
    "One contract, one support route and one user interface.",
    "Integrations between modules usually work on day one.",
    "Can be quicker to start for a small team."
   ],
   "cons": [
    "Modules share a private metadata model, so replacing one part means replacing all of it.",
    "Weaker modules are carried by stronger ones, and evaluated less carefully.",
    "Pricing across modules is hard to compare with separate tools.",
    "Connectors to other suppliers' tools are fewer, slower or charged extra.",
    "The exit cost grows with every module adopted."
   ],
   "tests": [
    "Could you replace the data quality module next year and keep the catalogue? What would it cost?",
    "Are the module prices shown separately, and can you drop a module at renewal without penalty?",
    "Do the modules use the same open standards between themselves that they offer to other tools?"
   ]
  },
  "barriers": [
   {
    "name": "Pricing metric that punishes growth",
    "detail": "Charges per asset, per scanned table, per rule run or per user can make cataloguing everything, or running quality checks often, unaffordable. The DAM Policy expects broad coverage.",
    "mitigate": "Model cost at three and five times today's volume; prefer prices tied to things you control; cap annual increases."
   },
   {
    "name": "Shared credits or consumption pools",
    "detail": "Credits spread across modules make it hard to see what each capability costs and easy to overspend.",
    "mitigate": "Ask for a price per capability and a monthly usage report you can export."
   },
   {
    "name": "Connectors and APIs charged extra",
    "detail": "Some connectors, API access, single sign-on or automated user provisioning sit in higher tiers.",
    "mitigate": "List every integration you need in the requirement and require them in the evaluated price."
   },
   {
    "name": "Export and exit charges",
    "detail": "Fees or effort to get data and metadata out, including cloud egress charges, make exit costly. The CMA found egress fees and interoperability barriers restrict switching in public cloud.",
    "mitigate": "Require complete export in open formats at any time at no extra charge, and an exit plan with supplier support in the contract."
   },
   {
    "name": "Ownership of rules, terms and lineage",
    "detail": "Contracts can leave quality rules, glossary content, classifications or derived lineage as the supplier's property or in a form only their tool can read.",
    "mitigate": "State that all content you or the tool create about your data is yours, and must be exportable."
   },
   {
    "name": "Platform and marketplace commitments",
    "detail": "Buying through a cloud marketplace against a spend commitment can tie a catalogue or quality tool to one cloud platform.",
    "mitigate": "Check the tool runs and is supported on other platforms, and that the commitment does not lengthen the term."
   },
   {
    "name": "Licence terms that limit where software runs",
    "detail": "Licensing that costs more on a rival cloud reduces choice. The CMA has raised concerns about business software licensing in cloud.",
    "mitigate": "Ask for licence terms that are the same wherever the software runs."
   },
   {
    "name": "Long terms, auto-renewal and price uplift",
    "detail": "Multi-year terms, automatic renewal and uncapped increases reduce your bargaining power at exactly the point you might switch.",
    "mitigate": "Use break points, notice periods you can meet, and capped increases; diarise renewal decisions a year ahead."
   }
  ],
  "questions": [
   {
    "group": "Standards and export",
    "items": [
     "Which open standards does the product read and write for catalogue records, glossaries, quality results, lineage and data contracts? Give versions.",
     "Can we export everything, including custom fields, history, owners, classifications, comments and links, at any time, in open formats, without supplier help or extra charge?",
     "Describe a round trip, exporting our catalogue as DCAT and re-importing it into another product. What is lost?",
     "Does the product support the government Metadata Exchange Model for critical data assets?"
    ]
   },
   {
    "group": "APIs, connectors and plugins",
    "items": [
     "Is every object and action in the user interface available through a documented API? Provide the OpenAPI description.",
     "List each connector, who builds and maintains it, its licence and price, and how quickly it follows new versions of the connected system.",
     "Which connectors exist for other suppliers' catalogues, quality tools, lineage tools and records systems?",
     "Does the product emit and accept OpenLineage events? Can it read ODCS data contracts?",
     "What rate limits, call charges or tier limits apply to APIs and events?"
    ]
   },
   {
    "group": "Content ownership and portability",
    "items": [
     "Confirm that metadata, glossary terms, quality rules, scores, lineage and any content the product derives from our data belong to us.",
     "In what form are quality rules held? Can they be read and run outside the product?",
     "Can we keep data contracts and rules in our own code repository and have the product read them from there?"
    ]
   },
   {
    "group": "Commercial terms and exit",
    "items": [
     "Give separate prices for each capability, and confirm we can stop any one at renewal without penalty.",
     "Model the price at today's volumes and at three and five times them.",
     "Which features, connectors, single sign-on or provisioning sit in higher tiers?",
     "What does exit involve, how long does it take, what support is included, and what does it cost, including any cloud egress?",
     "Are licence prices the same on any cloud or on our own infrastructure?"
    ]
   },
   {
    "group": "Security, identity and AI",
    "items": [
     "Does the product use our identity provider for sign-in and automated user provisioning, at no extra charge?",
     "Can classification and access policies be read by other tools?",
     "If the product includes AI features, where are prompts and answers processed and stored, are they used to train models, and can they be switched off?",
     "Can an assistant we already approve query the product through an open protocol, respecting the same access rules?"
    ]
   },
   {
    "group": "Evidence",
    "items": [
     "Name customers who use the product with another supplier's catalogue, quality or lineage tool, and how they connect them.",
     "Will you take part in a short proof of concept using our data and an interoperability test we define?"
    ]
   }
  ],
  "steps": [
   {
    "name": "Map what you have",
    "text": "List the tools in use or planned for each capability, who owns them, contract end dates and how they connect today."
   },
   {
    "name": "Set the boundaries",
    "text": "Decide which open standard sits at each boundary between capabilities, using the pairs on this page, and record it as an architecture decision."
   },
   {
    "name": "Run an RFI",
    "text": "Use the questions on this page. Search Find a Tender and G-Cloud for how other bodies specified similar tools."
   },
   {
    "name": "Test before you buy",
    "text": "In the proof of concept, run a round trip of export and import, show quality results in the catalogue through an open route, and capture lineage from a pipeline you own."
   },
   {
    "name": "Write it into the contract",
    "text": "Include export in open formats, content ownership, separate capability prices, capped increases and a costed exit plan."
   },
   {
    "name": "Keep checking",
    "text": "Repeat the export test each year before renewal, and record the result in your assurance evidence."
   }
  ]
 },
 "related": {
  "intro": "Two other open projects cover ground next to this one. Each has its own owner, purpose, audience and status, so they are signposted here, not merged.",
  "portals": [
   {
    "id": "dqc",
    "name": "Public Sector Data Quality Commons",
    "url": "https://cyberdudeuk.github.io/dq-commons/",
    "status": "Community project",
    "nature": "Open, crowdsourced and voluntary. Built with and for data quality practitioners.",
    "licence": "Code MIT; content Open Government Licence v3.0"
   },
   {
    "id": "cat",
    "name": "GitHub Repos Asset Catalogue",
    "url": "https://cyberdudeuk.github.io/github-repos-asset-catalogue/",
    "status": "Specialist evidence tool",
    "nature": "What public bodies publish as code on GitHub, explained for technical and non-technical readers.",
    "licence": "Code MIT; content and data Open Government Licence v3.0"
   },
   {
    "id": "ap",
    "name": "DCAT Application Profile for the UK (DCAT-AP-UK)",
    "url": "https://cyberdudeuk.github.io/dcat-ap-uk/",
    "status": "Proposed, not endorsed",
    "nature": "A proposed UK application profile of DCAT 3 that evolves the xGov MEM. The MEM remains the endorsed model until the Data Standards Authority decides.",
    "licence": "Content Open Government Licence v3.0; code MIT"
   }
  ],
  "placements": {
   "quality": [
    {
     "portal": "dqc",
     "title": "Check a CSV file",
     "path": "check.html",
     "why": "Run quality rules on a file in your browser; nothing is uploaded."
    },
    {
     "portal": "dqc",
     "title": "Issues framework calculator",
     "path": "guidance.html",
     "why": "Score an issue's priority and time to fix with the GOV.UK issues framework."
    },
    {
     "portal": "dqc",
     "title": "Data quality management playbook",
     "path": "playbook.html",
     "why": "The community's eight-stage practice guide, for more depth than the policy steps here."
    }
   ],
   "cataloguing": [
    {
     "portal": "ap",
     "title": "The proposed UK profile of DCAT",
     "path": "index.html",
     "why": "How the MEM may evolve: every property with its obligation and lineage from the MEM, and a record builder. Proposed, not endorsed."
    },
    {
     "portal": "cat",
     "title": "Data catalogues and standards",
     "path": "#standards",
     "why": "Which public bodies' code shows a catalogue platform or applies DCAT, SKOS or the Metadata Exchange Model."
    },
    {
     "portal": "dqc",
     "title": "Metadata weaver",
     "path": "weaver.html",
     "why": "Describe a dataset once and output it in several metadata standards, with its metadata quality as DQV."
    },
    {
     "portal": "dqc",
     "title": "Standards catalogue",
     "path": "interop.html#catalogue",
     "why": "Open standards for data, digital, cyber and technology with their GOV.UK status, including DCAT, the Metadata Exchange Model and DQV."
    }
   ],
   "tooling": [
    {
     "portal": "dqc",
     "title": "Catalogues and data quality tools",
     "path": "catalogues.html",
     "why": "Named products and how they connect, a lock-in risk checker, an RFI and RFP question builder and a proof-of-concept test script."
    },
    {
     "portal": "dqc",
     "title": "Commercial clause builder",
     "path": "commercial.html",
     "why": "Contract clauses that make suppliers responsible for data quality and exit."
    },
    {
     "portal": "cat",
     "title": "Data tools and suppliers",
     "path": "#suppliers",
     "why": "Which data tools appear in public bodies' code, and where."
    },
    {
     "portal": "cat",
     "title": "Data catalogues and standards",
     "path": "#standards",
     "why": "Catalogue platforms and metadata standards found in public code."
    },
    {
     "portal": "dqc",
     "title": "Standards catalogue",
     "path": "interop.html#catalogue",
     "why": "The open standards that connect tools, with their GOV.UK status and the concepts each one carries."
    }
   ],
   "perspectives": [
    {
     "portal": "cat",
     "title": "Legacy and technical debt",
     "path": "#legacy",
     "why": "Legacy and debt signals in each organisation's public code, with the evidence."
    },
    {
     "portal": "dqc",
     "title": "Data debt and migration",
     "path": "legacy.html",
     "why": "A data debt self-assessment and quality gates for a migration."
    }
   ],
   "change": [
    {
     "portal": "cat",
     "title": "Legacy and technical debt",
     "path": "#legacy",
     "why": "Evidence of legacy in an organisation's public code, to plan exits from."
    },
    {
     "portal": "dqc",
     "title": "Data debt and migration",
     "path": "legacy.html",
     "why": "Data quality gates to carry through a modernisation programme."
    },
    {
     "portal": "dqc",
     "title": "Data quality in change programmes",
     "path": "roles.html#change",
     "why": "Gate questions, a RACI and a service blueprint for data quality during delivery."
    }
   ],
   "capability-model": [
    {
     "portal": "cat",
     "title": "Data management wheel",
     "path": "#dama",
     "why": "Public code projects with evidence of each DAMA knowledge area."
    },
    {
     "portal": "dqc",
     "title": "Data quality capability model",
     "path": "models.html",
     "why": "The data quality capability in more detail, with workflows and downloads."
    },
    {
     "portal": "dqc",
     "title": "Data management wheel (Commons)",
     "path": "wheel.html",
     "why": "The same eleven areas from a data quality angle, shaded by your own maturity answers."
    },
    {
     "portal": "dqc",
     "title": "Three portals, one journey",
     "path": "ecosystem.html",
     "why": "Trace a DAMA area, role or standard through all three portals."
    }
   ],
   "reuse": [
    {
     "portal": "dqc",
     "title": "Use the Commons your way",
     "path": "reuse.html",
     "why": "The Commons' own API, embed mode and MCP tools."
    },
    {
     "portal": "cat",
     "title": "Search all code projects",
     "path": "#search",
     "why": "Download catalogue records as DCAT or CSV."
    }
   ]
  }
 },
 "research": {
  "intro": "This portal is a prototype. What it becomes depends on the people who use it. Take part in research, suggest and vote for ideas, and see how every decision is made, in the open.",
  "why_take_part": [
   "Shape guidance you may be expected to follow, before it settles",
   "Get early sight of what is coming and why",
   "Make sure it works for your role, your organisation and your access needs",
   "Help other organisations avoid duplicated effort"
  ],
  "methods": [
   {
    "id": "M-INT",
    "name": "Interview",
    "icon": "message-square-text",
    "time": "45 to 60 minutes",
    "how": "Online, one to one",
    "what": "How you manage data assets today and what gets in the way"
   },
   {
    "id": "M-USE",
    "name": "Usability session",
    "icon": "list-checks",
    "time": "45 to 60 minutes",
    "how": "Online, one to one, you share your screen",
    "what": "Try real tasks on the portal while thinking aloud"
   },
   {
    "id": "M-TREE",
    "name": "Tree test or card sort",
    "icon": "network",
    "time": "10 to 15 minutes",
    "how": "Online, in your own time",
    "what": "Find things using only the menu labels, so we can test the structure"
   },
   {
    "id": "M-SURVEY",
    "name": "Survey",
    "icon": "clipboard-list",
    "time": "5 to 10 minutes",
    "how": "Online, in your own time",
    "what": "How you use the portal and what you need next"
   },
   {
    "id": "M-A11Y",
    "name": "Accessibility session",
    "icon": "accessibility",
    "time": "60 to 90 minutes",
    "how": "Online or in person, with your own set-up",
    "what": "Use the portal with your assistive technology, such as a screen reader, magnifier or voice control"
   },
   {
    "id": "M-PANEL",
    "name": "Review panel",
    "icon": "users-round",
    "time": "About an hour a month",
    "how": "Online, as a group",
    "what": "Review drafts of new content, such as sector supplements, before they are published"
   }
  ],
  "who": "Anyone who works with data assets in the UK public sector, in any of the roles below, at any level. We especially need people who use assistive technology, people outside central government, and people from all four nations.",
  "signup": {
   "url": "",
   "note": "Sign-up is through a private form, never through GitHub, because it asks for contact details. Until it opens, use the private feedback form and say you would like to take part.",
   "collects": [
    "Your role and organisation type",
    "Which kinds of research you would do",
    "Whether you use assistive technology and anything we should arrange",
    "A way to contact you"
   ]
  },
  "privacy": [
   "Your contact details are kept separately from your answers, only by the research team, and deleted when you ask or within 12 months.",
   "Notes name roles, not people. Quotes are anonymous.",
   "Sessions are recorded only if you agree, and you can stop at any time.",
   "Nothing above OFFICIAL is discussed.",
   "Who controls your data, and the full privacy notice, are confirmed with the data protection officer before the first session."
  ],
  "rounds": [
   {
    "id": "R-0",
    "name": "Introduce and recruit",
    "status": "now",
    "goal": "Introduce the portal to prospective users and teams and build a pool of participants for every role.",
    "methods": [
     "M-SURVEY"
    ],
    "answers": []
   },
   {
    "id": "R-1",
    "name": "Find and follow",
    "status": "next",
    "goal": "Can each role find and follow the steps that apply to them?",
    "methods": [
     "M-USE",
     "M-TREE"
    ],
    "answers": [
     "H-01"
    ]
   },
   {
    "id": "R-2",
    "name": "Access for everyone",
    "status": "next",
    "goal": "Can people who use assistive technology complete a route without help?",
    "methods": [
     "M-A11Y"
    ],
    "answers": []
   },
   {
    "id": "R-3",
    "name": "Fit with how organisations work",
    "status": "later",
    "goal": "Do the hand-offs, roles and yearly cycle match how organisations actually work?",
    "methods": [
     "M-INT",
     "M-PANEL"
    ],
    "answers": [
     "H-02",
     "H-03"
    ]
   }
  ],
  "learned": [],
  "ideas": {
   "category": "Ideas",
   "new_url": "discussions/new?category=ideas",
   "list_url": "discussions/categories/ideas",
   "note": "Ideas are public GitHub Discussions, so do not include your name, colleagues' names or anything above OFFICIAL. Vote by upvoting an idea; comments add evidence."
  },
  "wip_limit": 5,
  "mvp": {
   "definition": "The smallest set of guidance that lets an in-scope organisation make its January 2027 baseline return and finish Phase 1, internal transformation, by the end of December 2026: identify its critical data assets, name their owners, describe them in a catalogue and plan their quality.",
   "core": [
    "DM-GOV",
    "DM-META",
    "DM-DQ"
   ],
   "verdicts": {
    "in": "In the MVP",
    "optional": "In the MVP, optional",
    "lite": "In the MVP as signposts only",
    "after": "After the MVP"
   },
   "caveats": [
    "Evidence of demand is one pilot team. No research with users has run yet (OR-04), so usability is an expert judgement.",
    "The baseline return template, not this portal, sets what organisations must report. Nothing here adds to the return.",
    "Records, security, integration and architecture belong to other teams; their verdicts need those teams' agreement.",
    "New sources found by web search on 11 November 2026 are marked S and need checking before the MVP is promoted."
   ]
  },
  "criteria": [
   {
    "id": "demand",
    "name": "User demand",
    "weight": 25,
    "icon": "users-round",
    "ask": "How many people need it, and how strong is the evidence?",
    "scale": [
     "No evidence",
     "One source",
     "Several sources or 5+ votes",
     "Research finding or 15+ votes"
    ]
   },
   {
    "id": "policy",
    "name": "DAM Policy",
    "weight": 20,
    "icon": "landmark",
    "ask": "Does it help organisations meet the DAM Policy?",
    "scale": [
     "No link",
     "Indirect",
     "Supports a should",
     "Supports a must"
    ]
   },
   {
    "id": "strategy",
    "name": "Government strategy",
    "weight": 20,
    "icon": "compass",
    "ask": "Does it fit the government's direction for digital and data?",
    "scale": [
     "No fit",
     "Weak fit",
     "Clear fit",
     "Named in a strategy"
    ]
   },
   {
    "id": "feasibility",
    "name": "Feasibility",
    "weight": 15,
    "icon": "wrench",
    "ask": "Can it be done with what exists, safely and lawfully?",
    "scale": [
     "Not feasible now",
     "Major unknowns",
     "Some unknowns",
     "Straightforward"
    ]
   },
   {
    "id": "capacity",
    "name": "Capacity and effort",
    "weight": 10,
    "icon": "clock",
    "ask": "Does it fit the time and people available?",
    "scale": [
     "Needs new capacity",
     "Large",
     "Medium",
     "Small"
    ]
   },
   {
    "id": "inclusion",
    "name": "Inclusion",
    "weight": 10,
    "icon": "heart-handshake",
    "ask": "Does it make the portal work for more people?",
    "scale": [
     "No effect",
     "Slight",
     "Clear benefit",
     "Removes a barrier"
    ]
   }
  ],
  "vote_bands": [
   [
    1,
    1
   ],
   [
    5,
    2
   ],
   [
    15,
    3
   ]
  ],
  "bands": [
   [
    70,
    "now",
    "Strong candidate for Now"
   ],
   [
    50,
    "next",
    "Candidate for Next"
   ],
   [
    0,
    "later",
    "Later or not yet"
   ]
  ],
  "strategies": [
   {
    "id": "dam",
    "name": "Data asset management policy",
    "ref": "SRC-DAM"
   },
   {
    "id": "rmdg",
    "name": "A roadmap for modern digital government 2025 to 2030",
    "ref": "RB-RMDG"
   },
   {
    "id": "blueprint",
    "name": "A blueprint for modern digital government",
    "ref": "RB-BLUEPRINT"
   },
   {
    "id": "ndl",
    "name": "National Data Library",
    "ref": "RB-NDLPUB"
   },
   {
    "id": "sdr",
    "name": "Strategic roadmap for public sector data (in development by the Government Data Directorate; announced for April 2026 and not found published on GOV.UK on 5 November 2026)",
    "ref": null
   }
  ],
  "backlog": [
   {
    "id": "BL-01",
    "type": "feature",
    "title": "Private feedback route",
    "story": "As someone without a GitHub account, I need a private way to give feedback, so that I can take part without publishing my views.",
    "source": "OR-02",
    "status": "done",
    "release": "1.8.0",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 2,
     "policy": 1,
     "strategy": 2,
     "feasibility": 3,
     "capacity": 3,
     "inclusion": 3
    }
   },
   {
    "id": "BL-02",
    "type": "feature",
    "title": "Share, site map, guided tours and tutorials",
    "story": "As a first-time visitor, I need to see how the portal fits together, so that I can find my way without help.",
    "source": "Owner request",
    "status": "done",
    "release": "1.8.0",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 2,
     "policy": 1,
     "strategy": 2,
     "feasibility": 3,
     "capacity": 2,
     "inclusion": 3
    }
   },
   {
    "id": "BL-03",
    "type": "feature",
    "title": "Signposts to the sister portals",
    "story": "As a practitioner, I need to know when another portal goes deeper, so that I do not miss tools or evidence.",
    "source": "Owner request",
    "status": "done",
    "release": "1.8.1",
    "strategy": [
     "rmdg",
     "ndl"
    ],
    "assess": {
     "demand": 2,
     "policy": 2,
     "strategy": 2,
     "feasibility": 3,
     "capacity": 3,
     "inclusion": 1
    }
   },
   {
    "id": "BL-04",
    "type": "feature",
    "title": "Data portals compass",
    "story": "As someone working across policy, practice and technology, I need to know where to start and in what order, so that I take the shortest route to a result.",
    "source": "Owner request",
    "status": "done",
    "release": "1.8.2",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 2,
     "policy": 2,
     "strategy": 2,
     "feasibility": 3,
     "capacity": 2,
     "inclusion": 2
    }
   },
   {
    "id": "BL-05",
    "type": "feature",
    "title": "Research, roadmap and ideas in the open",
    "story": "As a user, I need to see what is planned and how decisions are made, and to suggest and vote for ideas, so that the portal meets real needs.",
    "source": "Owner request",
    "status": "done",
    "release": "1.9.0",
    "strategy": [
     "rmdg",
     "dam"
    ],
    "assess": {
     "demand": 2,
     "policy": 2,
     "strategy": 3,
     "feasibility": 3,
     "capacity": 2,
     "inclusion": 2
    }
   },
   {
    "id": "BL-10",
    "type": "research",
    "title": "Round 1: can each role find and follow its steps?",
    "story": "As the service owner, I need evidence from 5 to 8 people per role, so that changes rest on what users do, not what we assume.",
    "source": "OR-04",
    "status": "next",
    "strategy": [
     "dam",
     "rmdg"
    ],
    "assess": {
     "demand": 3,
     "policy": 3,
     "strategy": 2,
     "feasibility": 2,
     "capacity": 1,
     "inclusion": 2
    }
   },
   {
    "id": "BL-11",
    "type": "research",
    "title": "Test with disabled people and assistive technology",
    "story": "As someone who uses a screen reader, magnifier or voice control, I need the portal to work with my set-up, so that I can follow the policy like anyone else.",
    "source": "OR-09",
    "status": "next",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 3,
     "policy": 2,
     "strategy": 2,
     "feasibility": 2,
     "capacity": 1,
     "inclusion": 3
    }
   },
   {
    "id": "BL-12",
    "type": "feature",
    "title": "Private research sign-up form",
    "story": "As a prospective participant, I need to sign up privately, so that my contact details are not published.",
    "source": "OR-02",
    "status": "now",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 3,
     "policy": 1,
     "strategy": 2,
     "feasibility": 3,
     "capacity": 3,
     "inclusion": 2
    }
   },
   {
    "id": "BL-13",
    "type": "research",
    "title": "Round 0: introduce the portal and recruit participants",
    "story": "As the service owner, I need a pool of participants from every role, organisation type and nation, so that research rounds can start quickly.",
    "source": "OR-04",
    "status": "now",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 3,
     "policy": 2,
     "strategy": 2,
     "feasibility": 3,
     "capacity": 2,
     "inclusion": 2
    }
   },
   {
    "id": "BL-14",
    "type": "content",
    "title": "Expert review of the sector supplements",
    "story": "As a sector specialist, I need the supplements checked by people who know the sector, so that I can trust them.",
    "source": "OR-12",
    "status": "next",
    "strategy": [
     "dam"
    ],
    "assess": {
     "demand": 2,
     "policy": 2,
     "strategy": 1,
     "feasibility": 2,
     "capacity": 1,
     "inclusion": 1
    }
   },
   {
    "id": "BL-15",
    "type": "feature",
    "title": "Check this flag",
    "story": "As a policy coordinator, I need to tell you when a capability flag looks wrong, so that the capability model stays accurate.",
    "source": "OR-15",
    "status": "done",
    "release": "1.10.0",
    "strategy": [
     "dam"
    ],
    "assess": {
     "demand": 2,
     "policy": 3,
     "strategy": 1,
     "feasibility": 3,
     "capacity": 3,
     "inclusion": 1
    }
   },
   {
    "id": "BL-16",
    "type": "feature",
    "title": "Embed a step or table on an intranet",
    "story": "As a department's data team, I need to show one policy step or table on our intranet, so that colleagues see it where they work.",
    "source": "Comparison with the Data Quality Commons",
    "status": "done",
    "release": "1.10.0",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 1,
     "policy": 2,
     "strategy": 2,
     "feasibility": 3,
     "capacity": 2,
     "inclusion": 1
    }
   },
   {
    "id": "BL-17",
    "type": "feature",
    "title": "Level labels and easy read summaries",
    "story": "As someone new to data management, I need to know which pages are pitched at me and to read short plain summaries, so that I am not put off.",
    "source": "Comparison with the Data Quality Commons",
    "status": "done",
    "release": "1.10.0",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 1,
     "policy": 1,
     "strategy": 2,
     "feasibility": 3,
     "capacity": 2,
     "inclusion": 3
    }
   },
   {
    "id": "BL-18",
    "type": "feature",
    "title": "Ask questions answered from the portal",
    "story": "As a busy reader, I need to ask a question in my own words and get the page that answers it, so that I do not have to know where things are.",
    "source": "Comparison with the Data Quality Commons and the catalogue",
    "status": "done",
    "release": "1.10.0",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 1,
     "policy": 1,
     "strategy": 3,
     "feasibility": 2,
     "capacity": 1,
     "inclusion": 2
    }
   },
   {
    "id": "BL-19",
    "type": "feature",
    "title": "Releases feed",
    "story": "As a returning user, I need to know when something changes, so that I keep up without checking the site.",
    "source": "Comparison with the Data Quality Commons",
    "status": "done",
    "release": "1.10.0",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 1,
     "policy": 1,
     "strategy": 2,
     "feasibility": 3,
     "capacity": 3,
     "inclusion": 1
    }
   },
   {
    "id": "BL-20",
    "type": "feature",
    "title": "Lineage and ontology downloads",
    "story": "As a metadata specialist, I need the requirement-to-check lineage and the ontology in open formats, so that I can reuse them in our tools.",
    "source": "Comparison with the catalogue",
    "status": "done",
    "release": "1.10.0",
    "strategy": [
     "ndl",
     "dam"
    ],
    "assess": {
     "demand": 1,
     "policy": 1,
     "strategy": 2,
     "feasibility": 2,
     "capacity": 2,
     "inclusion": 0
    }
   },
   {
    "id": "BL-21",
    "type": "feature",
    "title": "Offline copy",
    "story": "As someone whose network blocks GitHub Pages, I need a copy I can open offline, so that I can still use the guidance.",
    "source": "Comparison with the catalogue",
    "status": "done",
    "release": "1.10.0",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 1,
     "policy": 1,
     "strategy": 1,
     "feasibility": 2,
     "capacity": 1,
     "inclusion": 2
    }
   },
   {
    "id": "BL-22",
    "type": "decision",
    "title": "Clearance and an official home",
    "story": "As a department, I need to know whether this is guidance I can rely on, so that I can use it in my organisation.",
    "source": "OR-03",
    "status": "now",
    "strategy": [
     "dam",
     "rmdg"
    ],
    "assess": {
     "demand": 3,
     "policy": 3,
     "strategy": 2,
     "feasibility": 1,
     "capacity": 1,
     "inclusion": 1
    }
   },
   {
    "id": "BL-23",
    "type": "content",
    "title": "Agreed metadata terms for the four missing properties",
    "story": "As a catalogue manager, I need agreed terms for every required property, so that our records match everyone else's.",
    "source": "OR-06",
    "status": "later",
    "strategy": [
     "dam",
     "ndl"
    ],
    "assess": {
     "demand": 2,
     "policy": 3,
     "strategy": 2,
     "feasibility": 1,
     "capacity": 1,
     "inclusion": 0
    }
   },
   {
    "id": "BL-24",
    "type": "research",
    "title": "Welsh language needs",
    "story": "As someone in a Welsh public body, I may need the portal in Welsh, so that we can meet our language duties.",
    "source": "Research question",
    "status": "later",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 0,
     "policy": 1,
     "strategy": 1,
     "feasibility": 1,
     "capacity": 0,
     "inclusion": 3
    }
   },
   {
    "id": "BL-26",
    "type": "content",
    "title": "Boards, councils and networks",
    "story": "As a data leader, I need to know which boards decide, which advise and where practitioners meet, so that I can take issues to the right place.",
    "source": "Owner request",
    "status": "done",
    "release": "1.10.0",
    "strategy": [
     "dam",
     "rmdg"
    ],
    "assess": {
     "demand": 2,
     "policy": 2,
     "strategy": 2,
     "feasibility": 3,
     "capacity": 2,
     "inclusion": 1
    }
   },
   {
    "id": "BL-27",
    "type": "feature",
    "title": "Get involved and champions toolkit",
    "story": "As a champion in my organisation, I need ready-made posts, emails and a walk-through, so that I can bring my team in without extra work.",
    "source": "Owner request",
    "status": "done",
    "release": "1.10.0",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 2,
     "policy": 1,
     "strategy": 2,
     "feasibility": 3,
     "capacity": 2,
     "inclusion": 2
    }
   },
   {
    "id": "BL-28",
    "type": "feature",
    "title": "Badges for taking part",
    "story": "As someone who helps improve the portal, I want a badge for my profile and signature, so that my contribution is recognised.",
    "source": "Owner request",
    "status": "done",
    "release": "1.10.0",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 2,
     "policy": 0,
     "strategy": 1,
     "feasibility": 3,
     "capacity": 3,
     "inclusion": 1
    }
   },
   {
    "id": "BL-29",
    "type": "content",
    "title": "Welsh language summaries",
    "story": "As someone in a Welsh public body, I need key pages summarised in Welsh, so that we can meet our language duties.",
    "source": "BL-24",
    "status": "later",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 0,
     "policy": 1,
     "strategy": 1,
     "feasibility": 1,
     "capacity": 0,
     "inclusion": 3
    }
   },
   {
    "id": "BL-30",
    "type": "feature",
    "title": "Governance layers and what each may change",
    "story": "As a data owner, I need to know what each governance layer may and may not change, so that decisions go to the right place and survive a team handover.",
    "source": "Project Compass pilot (issue 21)",
    "status": "done",
    "release": "1.12.0",
    "strategy": [
     "dam"
    ],
    "assess": {
     "demand": 1,
     "policy": 3,
     "strategy": 2,
     "feasibility": 3,
     "capacity": 3,
     "inclusion": 1
    },
    "dama": [
     "DM-GOV"
    ],
    "mvp": {
     "verdict": "in",
     "usability": "One section on the Roles tab and a CSV; uses the 19 role names people already know.",
     "condition": "Align with the GDS Data Ownership Model before it is promoted; until then it stays labelled as proposed."
    }
   },
   {
    "id": "BL-31",
    "type": "content",
    "title": "Retention fields in the ownership register and catalogue record",
    "story": "As a data owner, I need retention and disposal recorded with each asset, so that data is neither kept too long nor destroyed early.",
    "source": "Project Compass pilot (issue 19)",
    "status": "done",
    "release": "1.12.0",
    "strategy": [
     "dam"
    ],
    "assess": {
     "demand": 1,
     "policy": 1,
     "strategy": 1,
     "feasibility": 3,
     "capacity": 3,
     "inclusion": 0
    },
    "dama": [
     "DM-DOC",
     "DM-GOV",
     "DM-META"
    ],
    "mvp": {
     "verdict": "optional",
     "usability": "Adds five fields to the ownership register and two to the catalogue record, which adds burden if made required.",
     "condition": "Keep the fields optional and out of the return template; agree read-across to records schedules with the government knowledge and information management team."
    }
   },
   {
    "id": "BL-32",
    "type": "content",
    "title": "Data sharing agreement template and gateways",
    "story": "As a data owner, I need a data sharing agreement that covers the lawful basis and legal gateway, so that shared critical assets are on a sound footing.",
    "source": "Project Compass pilot (issue 20)",
    "status": "done",
    "release": "1.12.0",
    "strategy": [
     "dam",
     "ndl"
    ],
    "assess": {
     "demand": 1,
     "policy": 2,
     "strategy": 2,
     "feasibility": 2,
     "capacity": 2,
     "inclusion": 0
    },
    "dama": [
     "DM-SEC",
     "DM-INT",
     "DM-GOV"
    ],
    "mvp": {
     "verdict": "lite",
     "usability": "A 20-field template for owners and data protection officers, not for every user; reached from the data sharing supplement.",
     "condition": "Have the government data protection team review it before it is promoted; a gateway lookup waits until after the MVP."
    }
   },
   {
    "id": "BL-33",
    "type": "content",
    "title": "Data architecture and models supplement",
    "story": "As a data architect, I need to describe a critical asset's entities, relationships and authoritative source, so that others can build on it and returns do not count it twice.",
    "source": "Project Compass pilot (issue 18)",
    "status": "done",
    "release": "1.12.0",
    "strategy": [
     "blueprint"
    ],
    "assess": {
     "demand": 1,
     "policy": 1,
     "strategy": 2,
     "feasibility": 3,
     "capacity": 3,
     "inclusion": 0
    },
    "dama": [
     "DM-ARC",
     "DM-MOD"
    ],
    "mvp": {
     "verdict": "after",
     "usability": "Useful to architects and design authorities; most owners and coordinators will not need it for the baseline return.",
     "condition": "Only the authoritative source question belongs in the MVP, because it helps apply the policy's source data test; the rest follows the baseline return."
    }
   },
   {
    "id": "BL-34",
    "type": "content",
    "title": "Health and care obligations from DHSC and MedTech",
    "story": "As a health or care body, I need the laws, standards and frameworks that apply to our data assets in one place, so that we meet them alongside the DAM Policy.",
    "source": "Project Compass pilot (issue 22)",
    "status": "now",
    "strategy": [
     "dam"
    ],
    "assess": {
     "demand": 1,
     "policy": 2,
     "strategy": 1,
     "feasibility": 1,
     "capacity": 2,
     "inclusion": 1
    },
    "dama": [
     "DM-GOV",
     "DM-SEC",
     "DM-META"
    ],
    "mvp": {
     "verdict": "lite",
     "usability": "Signposts sit in the health supplement that health and care bodies already reach from the sector finder.",
     "condition": "Signposts now; complete with the pilot's feedback and an expert review (BL-14) before implementation begins in January 2027."
    }
   },
   {
    "id": "BL-35",
    "type": "feature",
    "title": "Drill down from the DAMA wheel to activities and tasks",
    "story": "As someone building an enterprise data management capability, I need to go from a knowledge area on the wheel to its activities and tasks, so that I can see what good looks like beyond the three DAM capabilities.",
    "source": "Owner request, 11 November 2026",
    "status": "done",
    "release": "1.14.0",
    "strategy": [
     "dam",
     "blueprint"
    ],
    "assess": {
     "demand": 1,
     "policy": 1,
     "strategy": 1,
     "feasibility": 2,
     "capacity": 1,
     "inclusion": 2
    },
    "dama": [
     "DM-GOV",
     "DM-ARC",
     "DM-MOD",
     "DM-OPS",
     "DM-SEC",
     "DM-INT",
     "DM-DOC",
     "DM-REF",
     "DM-BI",
     "DM-META",
     "DM-DQ"
    ],
    "mvp": {
     "verdict": "after",
     "usability": "Governance, metadata and data quality already drill down to their playbook steps; the other areas would add reading that most organisations do not need for the return.",
     "condition": "Build the structure with data architecture first (BL-36). Add other areas only when the profession that owns each agrees to own its content."
    }
   },
   {
    "id": "BL-36",
    "type": "content",
    "title": "Data architecture capability playbook",
    "story": "As a data architect or design authority, I need a step-by-step playbook for data architecture, so that critical assets have a known structure and authoritative source that others can build on.",
    "source": "Owner request, 11 November 2026",
    "status": "later",
    "strategy": [
     "blueprint"
    ],
    "assess": {
     "demand": 1,
     "policy": 1,
     "strategy": 2,
     "feasibility": 2,
     "capacity": 0,
     "inclusion": 0
    },
    "dama": [
     "DM-ARC",
     "DM-MOD"
    ],
    "mvp": {
     "verdict": "after",
     "usability": "Useful to architects; owners and coordinators need only the authoritative source question, which is already in the cataloguing guidance and the supplement.",
     "condition": "Phase 2, from January 2027, once architecture leads agree to own and review it; see the assessment on the DAMA wheel."
    }
   },
   {
    "id": "BL-25",
    "type": "feature",
    "title": "A chatbot hosted by this portal",
    "story": "As a reader, I would like to chat with the guidance.",
    "source": "Reuse decision",
    "status": "out",
    "reason": "Out of scope: the portal runs no server and sends nothing anywhere. Assistants your organisation approves can use its open data and MCP server instead (Use and reuse).",
    "strategy": [
     "rmdg"
    ],
    "assess": {
     "demand": 1,
     "policy": 0,
     "strategy": 2,
     "feasibility": 0,
     "capacity": 0,
     "inclusion": 0
    }
   }
  ],
  "decisions": [
   {
    "date": "2026-11-11",
    "item": "BL-34",
    "decision": "Health and care obligations stay in Now",
    "why": "The score says Later because demand is one pilot team and the rest depends on its feedback. Signposts were released in 1.12.0, and finishing needs only that feedback and the expert review (BL-14), so it should not wait behind unrelated work."
   },
   {
    "date": "2026-11-11",
    "item": "BL-33",
    "decision": "Data architecture judged After the MVP even though it is built",
    "why": "It sits outside the three DAM capabilities on the DAMA wheel and most organisations will not need it for the baseline return; only its authoritative source question is pulled forward."
   },
   {
    "date": "2026-11-05",
    "item": "BL-05",
    "decision": "Research, roadmap and ideas published in the open",
    "why": "Working in the open lets users see and shape priorities; modelled on the data.gov.uk roadmap."
   },
   {
    "date": "2026-11-05",
    "item": "BL-25",
    "decision": "A hosted chatbot is out of scope",
    "why": "No server, nothing sent anywhere; open data and the MCP server serve approved assistants instead."
   },
   {
    "date": "2026-11-05",
    "item": "BL-10",
    "decision": "Round 1 waits until Round 0 has recruited for every role",
    "why": "Usability sessions need 5 to 8 people per role, including disabled people."
   },
   {
    "date": "2026-11-05",
    "item": "BL-11",
    "decision": "Accessibility sessions wait until Round 0 has recruited assistive technology users",
    "why": "The score says Now, but sessions cannot start without participants; the sign-up form (BL-12) and recruitment (BL-13) come first."
   },
   {
    "date": "2026-11-05",
    "item": "BL-18",
    "decision": "Asking questions in your own words stays in Later",
    "why": "The score says Next, but it needs a way to answer without a server or sending anything anywhere; the open data and MCP server already let approved assistants do this."
   },
   {
    "date": "2026-11-05",
    "item": "BL-23",
    "decision": "Agreed metadata terms stay in Later",
    "why": "The score says Next, but the terms are for the metadata standards owner to agree, not this portal; the proposed crosswalk stays on the cataloguing page meanwhile."
   },
   {
    "date": "2026-11-05",
    "item": "BL-18",
    "decision": "Asking questions built without a server",
    "why": "Answers come from the portal's own search index in the reader's browser; nothing is sent anywhere, so the earlier feasibility concern is met."
   },
   {
    "date": "2026-11-05",
    "item": "BL-21",
    "decision": "Offline copy built as a download of the whole site",
    "why": "A single file would need every page inlined; a zip of the built site opens offline in any browser and stays in step with each release."
   }
  ]
 },
 "bodies": {
  "intro": "Who decides, who advises and where practitioners meet, for data asset management in UK government. Each entry says what the body is for, how it relates to the DAM Policy and how you can take part. Facts were checked on GOV.UK and data.gov.uk on 5 November 2026; where terms of reference are not published, it says so.",
  "checked": "2026-11-05",
  "flow": [
   {
    "id": "networks",
    "step": "Communities of experts",
    "does": "Spot problems, share practice and help develop proposals"
   },
   {
    "id": "GB-PRG",
    "step": "Peer Review Group",
    "does": "Reviews products, proposals and standards"
   },
   {
    "id": "GB-DSASB",
    "step": "DSA Steering Board",
    "does": "Endorses cross-government standards (final step)"
   }
  ],
  "items": [
   {
    "id": "GB-CDO",
    "name": "Chief Data Officer (CDO) Council",
    "kind": "Decision-making council",
    "host": "Government Digital Service",
    "purpose": "The decision-making body overseeing strategic delivery of Mission 3 of the National Data Strategy (government's own use of data).",
    "aims": [
     "Collective accountability for government's own use and reuse of data",
     "Set future strategy as targets are met",
     "Help the Data Standards Authority identify strategic risks, problems and opportunities for common standards"
    ],
    "outcomes": "Strategic direction for data across government; it does not set specific data standards.",
    "dam": "DAM Policy artefacts such as the Data Ownership Model are presented to the CDO Council and its Executive before adoption.",
    "engage": "Through your organisation's chief data officer or equivalent senior data leader. Raise issues with them; the council is not open to direct membership.",
    "tor": "Terms of reference not found published on GOV.UK.",
    "url": "https://www.gov.uk/government/publications/data-standards-authority-operational-model-and-processes/data-standards-authority-operational-model-and-processes",
    "caps": [
     "gov"
    ]
   },
   {
    "id": "GB-DSASB",
    "name": "Data Standards Authority (DSA) Steering Board",
    "kind": "Endorsement board",
    "host": "Government Digital Service",
    "purpose": "A senior advisory group that supports the Data Standards Authority in setting cross-government data standardisation strategy and delivery plans.",
    "aims": [
     "Oversee the DSA's operations and priorities",
     "Approve cross-government standards as the final step of endorsement",
     "Drive implementation in member organisations",
     "Monitor enforcement and assurance"
    ],
    "outcomes": "Endorsed data standards for central government, and their implementation in member organisations.",
    "dam": "Endorsed the data quality action plan guidance and was presented the essential shared data assets policy and Data Ownership Model, which the DAM Policy builds on.",
    "engage": "Through your organisation's representative. Minutes are published, so you can follow decisions.",
    "tor": "Role set out in the DSA operational model; minutes published.",
    "url": "https://www.gov.uk/government/publications/meeting-minutes-for-the-data-standards-authority-governance-boards",
    "caps": [
     "gov",
     "cat",
     "dq"
    ]
   },
   {
    "id": "GB-PRG",
    "name": "Peer Review Group for the DSA and the Data Quality Hub",
    "kind": "Advisory group",
    "host": "Government Digital Service and the Office for National Statistics",
    "purpose": "Reviews products, proposals and standards before they go to the DSA Steering Board, and reviews products from the Government Data Quality Hub.",
    "aims": [
     "Shape the DSA's approach and priorities",
     "Help develop proposals, weighing cost, impact, skills and technical feasibility",
     "Suggest priority areas for standardisation"
    ],
    "outcomes": "Proposals that are tested by practitioners before endorsement.",
    "dam": "Reviews data quality and metadata products that the DAM Policy relies on.",
    "engage": "Through your organisation's representative, or by bringing evidence to a community that feeds it.",
    "tor": "Role set out in the DSA operational model; minutes published.",
    "url": "https://www.gov.uk/government/publications/meeting-minutes-for-the-data-standards-authority-governance-boards",
    "caps": [
     "gov",
     "cat",
     "dq"
    ]
   },
   {
    "id": "GB-OSB",
    "name": "Open Standards Board",
    "kind": "Standards board",
    "host": "Cabinet Office (Government Digital Service)",
    "purpose": "Accountable for the transparent selection and implementation of open standards for government.",
    "aims": [
     "Consider open standards for software interoperability, data and document formats",
     "Decide whether a standard is adopted or made compulsory",
     "Make sure open standards are considered before government creates its own"
    ],
    "outcomes": "Open standards that all of government must or should use, published with profiles on GOV.UK.",
    "dam": "The route for any data or metadata standard a DAM catalogue or tool should use; see Tools and interoperability.",
    "engage": "Propose or support an open standards challenge; volunteer when members are recruited. Members serve 2 years and declare interests.",
    "tor": "Terms of reference on the group's GOV.UK page; terms and conditions for members published.",
    "url": "https://www.gov.uk/government/groups/open-standards-board",
    "caps": [
     "cat"
    ]
   },
   {
    "id": "GB-DTADA",
    "name": "Data and Technology Architecture Design Authority (DTADA)",
    "kind": "Design authority",
    "host": "Government Digital Service",
    "purpose": "The decision-making body for data architecture principles, policies, strategies and standards.",
    "aims": [
     "Commission and approve data architecture artefacts",
     "Oversee the national reference data architecture",
     "Approve domain conceptual data models",
     "Coordinate with other design authorities"
    ],
    "outcomes": "Joined-up data architecture across government. It is a sub-group of the CDO and CTO councils.",
    "dam": "Sets architecture that catalogues, data models and reference data used under the DAM Policy should follow.",
    "engage": "Through your organisation's architecture lead.",
    "tor": "Role set out in the DSA operational model; terms of reference not found published.",
    "url": "https://www.gov.uk/government/publications/data-standards-authority-operational-model-and-processes/data-standards-authority-operational-model-and-processes",
    "caps": [
     "gov",
     "cat"
    ]
   },
   {
    "id": "GB-TOG",
    "name": "Taxonomy Oversight Group",
    "kind": "Oversight group",
    "host": "Government Data Architecture Community",
    "purpose": "Coordinates taxonomy work across government and recommends taxonomies for common use.",
    "aims": [
     "Oversee taxonomy proposals",
     "Address taxonomy challenges",
     "Recommend common taxonomies"
    ],
    "outcomes": "Shared taxonomies that make catalogue records comparable.",
    "dam": "Relevant to the vocabulary and classification fields of a DAM catalogue record.",
    "engage": "Through the Government Data Architecture Community.",
    "tor": "Described in the DSA operational model; terms of reference not found published.",
    "url": "https://www.gov.uk/government/publications/data-standards-authority-operational-model-and-processes/data-standards-authority-operational-model-and-processes",
    "caps": [
     "cat"
    ]
   },
   {
    "id": "GB-DSG",
    "name": "Data Steering Group",
    "kind": "Strategic oversight group (status unclear)",
    "host": "Cabinet Office",
    "purpose": "Strategic oversight of the use and management of government's data, inside and outside the public sector.",
    "aims": [
     "Promote consistent approaches to data privacy and security",
     "Support standards-based access to data",
     "Champion data skills and open data",
     "Review international data policy"
    ],
    "outcomes": "Advice to ministers and the data programme.",
    "dam": "Historical context only. The page was updated in January 2026 but its latest minutes are from 2016, so whether it still meets is unclear.",
    "engage": "None known. Check GOV.UK before relying on it.",
    "tor": "Terms of reference on the group's GOV.UK page.",
    "url": "https://www.gov.uk/government/groups/data-steering-group",
    "caps": [
     "gov"
    ],
    "unclear": true
   },
   {
    "id": "NW-DMC",
    "name": "Data Management Community",
    "kind": "Community of practice",
    "host": "Government Digital Service",
    "purpose": "A cross-government network sharing practice on data quality, metadata, governance and data catalogues. It also maintains the DAM Policy.",
    "aims": [
     "Share practice on governance, cataloguing and quality",
     "Support departments adopting the DAM Policy",
     "Gather feedback on guidance"
    ],
    "outcomes": "Departments supported to adopt the DAM Policy, and guidance shaped by practitioners.",
    "dam": "The closest community to the DAM Policy itself. Bring what you learn from this portal here.",
    "engage": "Join through the Knowledge Hub; the data.gov.uk page has the link.",
    "tor": "Not found published.",
    "url": "https://data.gov.uk/data-manual/join-a-data-community",
    "caps": [
     "gov",
     "cat",
     "dq"
    ]
   },
   {
    "id": "NW-GDQC",
    "name": "Government Data Quality Community",
    "kind": "Community of practice",
    "host": "Government Data Quality Hub (Office for National Statistics)",
    "purpose": "A place for public sector data professionals to meet, share and learn about data quality, launched in 2022.",
    "aims": [
     "Connect people working on data quality",
     "Share best practice and experience",
     "Build capability and skills"
    ],
    "outcomes": "Better data quality across government and the public sector.",
    "dam": "For data quality action plans, quality dimensions and reporting under the DAM Policy.",
    "engage": "Anyone in UK government or the public sector can join; contact the Data Quality Hub through its GOV.UK page.",
    "tor": "Not found published.",
    "url": "https://www.gov.uk/government/news/introducing-the-government-data-quality-community",
    "caps": [
     "dq"
    ]
   },
   {
    "id": "NW-DSNE",
    "name": "Data Sharing Network of Experts",
    "kind": "Expert network",
    "host": "Cross-government",
    "purpose": "Impartial advice to unblock data sharing, bringing together data protection, governance, security, privacy and policy specialists.",
    "aims": [
     "Share good practice on data sharing",
     "Advise on complex cases",
     "Develop guidance and frameworks"
    ],
    "outcomes": "Data shared lawfully and faster.",
    "dam": "For data sharing agreements and access controls on critical data assets.",
    "engage": "Join through the Knowledge Hub; the data.gov.uk page has the link.",
    "tor": "Not found published.",
    "url": "https://data.gov.uk/data-manual/join-a-data-community",
    "caps": [
     "gov"
    ]
   },
   {
    "id": "NW-GDAC",
    "name": "Government Data Architecture Community",
    "kind": "Community of experts",
    "host": "Supported by the Data Standards Authority",
    "purpose": "A cross-government community of data architects; it includes the Taxonomy Oversight Group.",
    "aims": [
     "Identify architecture problems",
     "Share practice",
     "Review solutions"
    ],
    "outcomes": "Proposals and patterns that feed the DSA and the design authority.",
    "dam": "For data models, reference data and catalogue structure.",
    "engage": "Through your organisation's architecture community or the DSA's GOV.UK pages.",
    "tor": "Not found published.",
    "url": "https://www.gov.uk/government/publications/data-standards-authority-operational-model-and-processes/data-standards-authority-operational-model-and-processes",
    "caps": [
     "cat"
    ]
   },
   {
    "id": "NW-API",
    "name": "API and data exchange community",
    "kind": "Community of practice",
    "host": "Cross-government",
    "purpose": "Shares knowledge and practice on APIs and interoperability, with monthly meetings and expert speakers.",
    "aims": [
     "Share API practice",
     "Improve interoperability"
    ],
    "outcomes": "APIs and data exchange that follow common standards.",
    "dam": "For publishing catalogue records and data through APIs.",
    "engage": "Open to anyone in government or the public sector; the data.gov.uk page says how.",
    "tor": "Not found published.",
    "url": "https://data.gov.uk/data-manual/join-a-data-community",
    "caps": [
     "cat"
    ]
   },
   {
    "id": "NW-ETH",
    "name": "Data and AI ethics community",
    "kind": "Community of practice",
    "host": "Cross-government",
    "purpose": "Discusses the ethical use of data, AI and technology in government, with events on transparency, trust and fairness.",
    "aims": [
     "Share ethical practice",
     "Discuss transparency, trust and fairness"
    ],
    "outcomes": "More ethical use of data and AI.",
    "dam": "For decisions about using critical data assets in AI and analytics.",
    "engage": "Open to public sector workers; the data.gov.uk page says how.",
    "tor": "Not found published.",
    "url": "https://data.gov.uk/data-manual/join-a-data-community",
    "caps": [
     "gov"
    ]
   },
   {
    "id": "NW-DENG",
    "name": "Data engineering community",
    "kind": "Community of practice",
    "host": "GOV.UK Service Manual communities",
    "purpose": "Supports people designing data products, automating data processes and applying data standards and models.",
    "aims": [
     "Share data engineering practice",
     "Apply data standards and models"
    ],
    "outcomes": "Data pipelines that build quality and metadata in.",
    "dam": "For automating quality rules and catalogue updates.",
    "engage": "Open to anyone in central government with an interest in data engineering.",
    "tor": "Not found published.",
    "url": "https://www.gov.uk/service-manual/communities/data-engineering-community",
    "caps": [
     "dq",
     "cat"
    ]
   },
   {
    "id": "NW-QCH",
    "name": "Government Statistical Service quality champions",
    "kind": "Champions network",
    "host": "Government Data Quality Hub",
    "purpose": "Departmental quality champions who support statistical heads of profession, meeting monthly.",
    "aims": [
     "Share knowledge and good practice",
     "Two-way flow of information between departments and the Data Quality Hub",
     "Promote good practice rather than enforce compliance"
    ],
    "outcomes": "Higher quality official statistics and easier compliance with the Code of Practice for Statistics.",
    "dam": "A model for champions networks, including this portal's own champions.",
    "engage": "Each department can nominate one or more champions; see the page.",
    "tor": "Role of a champion described on the page.",
    "url": "https://analysisfunction.civilservice.gov.uk/government-statistical-service-and-statistician-group/champion-networks/quality-champions",
    "caps": [
     "dq"
    ]
   },
   {
    "id": "NW-DLCN",
    "name": "Data Linkage Champions Network",
    "kind": "Champions network",
    "host": "Office for National Statistics",
    "purpose": "A methodological network supporting colleagues involved in data linkage at all levels.",
    "aims": [
     "Champion appropriate linkage methods and software",
     "Share knowledge across government",
     "Implement the cross-government data linkage review recommendations"
    ],
    "outcomes": "Better and more consistent data linkage.",
    "dam": "For linking and matching critical data assets, such as master and reference data.",
    "engage": "Champions and practitioners can attend and vote on changes to the network; see the page.",
    "tor": "Role of champions and co-chairs described on the page.",
    "url": "https://analysisfunction.civilservice.gov.uk/support/data-linkage/data-linkage-champion-network",
    "caps": [
     "dq"
    ]
   },
   {
    "id": "NW-NEWS",
    "name": "Data communities newsletter",
    "kind": "Newsletter",
    "host": "Government Digital Service",
    "purpose": "A monthly newsletter with news, events, learning and community updates for public sector data professionals.",
    "aims": [
     "Keep data professionals informed",
     "Promote events and communities"
    ],
    "outcomes": "People who know what is happening across the data communities.",
    "dam": "Announcements about the DAM Policy and its guidance.",
    "engage": "Sign up from the data.gov.uk page.",
    "tor": "Not applicable.",
    "url": "https://data.gov.uk/data-manual/join-a-data-community",
    "caps": [
     "gov",
     "cat",
     "dq"
    ]
   }
  ]
 },
 "involve": {
  "intro": "This portal is built in the open, and anyone can help: use it and tell us what works, test it, suggest and vote for ideas, improve the content, review it as an expert, or champion it in your own team. Every way of taking part is recognised with a badge.",
  "rules": [
   "Follow the code of conduct. Be kind, assume good faith and stay on topic.",
   "Nothing above OFFICIAL, no personal data, and no email addresses anywhere.",
   "Name roles, not people. Credit is given by GitHub username, only if you choose.",
   "Every fact needs a source and a provenance label (see How sources are labelled).",
   "Anyone can suggest a change. The owner reviews every change before it is published, and nobody is added as a collaborator except by the owner's invitation.",
   "Decisions are made in the open, through the roadmap and the decisions log on Have your say."
  ],
  "routes": [
   {
    "id": "IN-USE",
    "name": "Use it and tell us",
    "icon": "message-square-text",
    "time": "2 minutes",
    "how": "Use the portal for real work, then use 'Was this page useful?' at the foot of any page, or the private feedback form.",
    "link": "contact.html",
    "badge": "explorer"
   },
   {
    "id": "IN-TEST",
    "name": "Test it",
    "icon": "list-checks",
    "time": "About 20 minutes",
    "how": "Try the tasks for your role on Help us test and say how each went.",
    "link": "test.html",
    "badge": "tester"
   },
   {
    "id": "IN-RESEARCH",
    "name": "Take part in research",
    "icon": "clipboard-list",
    "time": "5 to 90 minutes",
    "how": "Sign up for a survey, interview, usability or accessibility session.",
    "link": "research.html#sign-up",
    "badge": "tester"
   },
   {
    "id": "IN-IDEAS",
    "name": "Suggest and vote for ideas",
    "icon": "lightbulb",
    "time": "5 minutes",
    "how": "Post an idea in Discussions, vote for others, and add evidence in comments.",
    "link": "research.html#ideas",
    "badge": "contributor"
   },
   {
    "id": "IN-CONTRIB",
    "name": "Improve the content",
    "icon": "pencil-line",
    "time": "As long as you like",
    "how": "Report a problem, suggest a change to a page, add a source, or propose a sector supplement. Changes go through a reviewed pull request.",
    "link": "#contribute",
    "badge": "contributor"
   },
   {
    "id": "IN-REVIEW",
    "name": "Review as an expert",
    "icon": "badge-check",
    "time": "About an hour a month",
    "how": "Join the review panel to check drafts, such as sector supplements, before they are published.",
    "link": "research.html#ways",
    "badge": "reviewer"
   },
   {
    "id": "IN-CHAMP",
    "name": "Champion it in your team",
    "icon": "megaphone",
    "time": "1 to 2 hours a month",
    "how": "Introduce the portal to your team, run a short walk-through, and pass on what your team needs.",
    "link": "#champions",
    "badge": "champion"
   },
   {
    "id": "IN-AMB",
    "name": "Be an ambassador across organisations",
    "icon": "users-round",
    "time": "As agreed",
    "how": "Present the portal at a community, network or working group, and bring back what you hear.",
    "link": "#champions",
    "badge": "ambassador"
   },
   {
    "id": "IN-COMMUNITY",
    "name": "Join a community or network",
    "icon": "handshake",
    "time": "Varies",
    "how": "Join the government data communities and networks listed on Boards, councils and networks.",
    "link": "bodies.html#networks",
    "badge": null
   }
  ],
  "champion": {
   "does": [
    "Share the portal with your team using the toolkit below",
    "Run a 15 minute walk-through at a team meeting",
    "Collect your team's feedback and ideas and post them",
    "Encourage colleagues to take part in research",
    "Tell us when your organisation's practice differs from the portal, so we can fix it"
   ],
   "gets": [
    "Early sight of what is coming on the roadmap",
    "A Champion badge for your GitHub profile and email signature",
    "Your organisation's needs reflected in the roadmap",
    "Recognition by GitHub username on the portal if you choose"
   ],
   "ambassador": [
    "Everything a champion does",
    "Present the portal at a community, network or working group",
    "Bring back what other organisations need",
    "Help shape the roadmap at a review panel"
   ],
   "time": "About 1 to 2 hours a month for a champion. Stop at any time."
  },
  "toolkit": [
   {
    "id": "TK-EMAIL",
    "name": "Email to your team",
    "icon": "send",
    "text": "Subject: Practical help with the Data Asset Management Policy\n\nHello team,\n\nThe DAM capability playbooks are a prototype website that turns the Data Asset Management Policy into practical steps for data governance, cataloguing and quality, by role.\n\nHave a look: {site}\nStart with \"Your role\": {site}personas.html\n\nIt is a prototype, not official GOV.UK guidance, and the team wants feedback. You can test it, take part in research, or suggest and vote for ideas: {site}research.html\n\n[Your name]\n"
   },
   {
    "id": "TK-TEAMS",
    "name": "Microsoft Teams post",
    "icon": "users",
    "text": "**Practical steps for the DAM Policy**\nThe DAM capability playbooks turn the Data Asset Management Policy into steps by role, for governance, cataloguing and quality. Prototype, open for feedback.\nTry it: {site}\nHave your say: {site}research.html\n"
   },
   {
    "id": "TK-SLACK",
    "name": "Slack post",
    "icon": "message-square-text",
    "text": ":bulb: *DAM Policy, made practical.* The DAM capability playbooks show the steps for your role in data governance, cataloguing and quality. It's a prototype and wants feedback.\nTry it: {site}\nSuggest and vote for ideas: {site}research.html#ideas\n"
   },
   {
    "id": "TK-ENGAGE",
    "name": "Viva Engage or intranet community post",
    "icon": "megaphone",
    "text": "Are you a data owner, steward or catalogue manager? The DAM capability playbooks set out what the Data Asset Management Policy asks of your role and how to do it. It is a prototype built in the open. Try a task, then tell the team what works: {site}test.html\n"
   },
   {
    "id": "TK-INTRANET",
    "name": "Intranet news item",
    "icon": "file-text",
    "text": "Headline: Help shape practical guidance for the Data Asset Management Policy\n\nThe DAM capability playbooks are a prototype website that helps organisations meet the Data Asset Management Policy. It sets out the steps for each role in data governance, data cataloguing and data quality, with templates, a capability model and links to GOV.UK guidance.\n\nThe team is looking for people to test it, take part in research, and suggest ideas. Find out more: {site}research.html\n\nIt is not official GOV.UK guidance. Where it repeats GOV.UK, the GOV.UK page is the authority.\n"
   },
   {
    "id": "TK-MEETING",
    "name": "15 minute walk-through at a team meeting",
    "icon": "presentation",
    "text": "1. (2 minutes) What the DAM Policy asks of us: {site}dam.html\n2. (5 minutes) Pick one role in the room and open its route: {site}personas.html\n3. (5 minutes) Try one task together from Help us test: {site}test.html\n4. (3 minutes) Agree one idea or problem to post: {site}research.html#ideas\n"
   },
   {
    "id": "TK-SIGNATURE",
    "name": "Email signature line",
    "icon": "pencil-line",
    "text": "DAM capability playbooks champion · Help shape practical guidance for the DAM Policy: {site}research.html\n"
   }
  ],
  "badges": [
   {
    "id": "explorer",
    "name": "Explorer",
    "colour": "#1d70b8",
    "icon": "compass",
    "earn": "Used the portal for real work and gave feedback.",
    "evidence": "Self-declared.",
    "claim": "self"
   },
   {
    "id": "tester",
    "name": "Tester",
    "colour": "#00703c",
    "icon": "list-checks",
    "earn": "Completed at least three testing tasks, or took part in a research session.",
    "evidence": "Self-declared; research participants are told after their session.",
    "claim": "self"
   },
   {
    "id": "contributor",
    "name": "Contributor",
    "colour": "#6a1b9a",
    "icon": "pencil-line",
    "earn": "An idea, report or change of yours was accepted onto the backlog or published.",
    "evidence": "A link to the idea, issue or pull request.",
    "claim": "request"
   },
   {
    "id": "reviewer",
    "name": "Reviewer",
    "colour": "#00695c",
    "icon": "badge-check",
    "earn": "Reviewed a draft as part of the review panel or an expert review.",
    "evidence": "Confirmed by the service owner.",
    "claim": "request"
   },
   {
    "id": "champion",
    "name": "Champion",
    "colour": "#b23a14",
    "icon": "megaphone",
    "earn": "Introduced the portal to your team and ran a walk-through or passed on your team's feedback.",
    "evidence": "A short note of what you did, with no names.",
    "claim": "request"
   },
   {
    "id": "ambassador",
    "name": "Ambassador",
    "colour": "#3949ab",
    "icon": "users-round",
    "earn": "Presented the portal at a community, network or working group, or championed it across organisations.",
    "evidence": "The community or event, with no names of attendees.",
    "claim": "request"
   }
  ],
  "badge_note": "Badges recognise help with a prototype. They are not an official government credential or qualification."
 },
 "easy_read": {
  "index": [
   "This website helps people follow the Data Asset Management Policy.",
   "The policy is about looking after important government data.",
   "It shows the steps for your role.",
   "It is a test version. It is not official GOV.UK guidance."
  ],
  "dam": [
   "The Data Asset Management Policy says how government must look after its most important data.",
   "This page lists every thing the policy asks for.",
   "Next to each one, it shows the step that helps you do it."
  ],
  "governance": [
   "Data governance means deciding who looks after data and how.",
   "This page shows the steps to set that up.",
   "It has templates you can copy."
  ],
  "cataloguing": [
   "A data catalogue is a list of your data and what it is about.",
   "This page shows how to build one and what to record.",
   "It shows what you must send to the Government Digital Service."
  ],
  "quality": [
   "Data quality means data is right and fit for use.",
   "This page shows how to check data and make it better.",
   "It has rules you can download and run."
  ],
  "personas": [
   "Choose the job closest to yours.",
   "You will see the steps for your job in order.",
   "Tick each step when you finish it."
  ],
  "research": [
   "You can help make this website better.",
   "You can test it",
   "talk to us",
   "or share ideas.",
   "We show what we plan to do and why."
  ],
  "involve": [
   "There are many ways to help.",
   "Pick the one that suits you.",
   "You can get a badge to show you helped."
  ]
 },
 "standards_map": {
  "intro": "Frameworks, methodologies and standards that apply to this capability, grouped by kind. Each one links to its publisher. Where this portal applies one to a step, the step says so under How to do it. The publisher's page is the authority.",
  "kinds": [
   {
    "id": "law",
    "name": "Legislation and statutory codes",
    "icon": "gavel"
   },
   {
    "id": "standard",
    "name": "Standards",
    "icon": "badge-check"
   },
   {
    "id": "framework",
    "name": "Frameworks",
    "icon": "layers"
   },
   {
    "id": "methodology",
    "name": "Methodologies and bodies of knowledge",
    "icon": "route"
   },
   {
    "id": "guidance",
    "name": "Guidance and policy",
    "icon": "book-open"
   }
  ],
  "group_kind": {
   "Legislation": "law",
   "Data protection": "law",
   "Standards": "standard"
  },
  "default_kind": "guidance",
  "kind_of": {
   "RB-COP": "law",
   "RB-ICOSHARE": "law",
   "RB-ICODSA": "law",
   "RB-PRA": "law",
   "RB-PA23": "law",
   "RB-UKMDR": "law",
   "RB-S251": "law",
   "RB-EUDA": "law",
   "RB-SVC": "standard",
   "RB-TCOP": "standard",
   "RB-TCOP4": "standard",
   "RB-OPEN": "standard",
   "RB-OSP": "standard",
   "RB-UPRN": "standard",
   "RB-API": "standard",
   "RB-GEMINI": "standard",
   "RB-GSC": "standard",
   "RB-STYLE": "standard",
   "RB-ATRS": "standard",
   "RB-GOVS002": "standard",
   "RB-GOVS005": "standard",
   "RB-GOVS007": "standard",
   "RB-ISO15489": "standard",
   "RB-ISO23081": "standard",
   "RB-FHIRUK": "standard",
   "RB-SNOMED": "standard",
   "RB-DCB0129": "standard",
   "RB-DCB0160": "standard",
   "RB-METASTD": "standard",
   "RB-DDAT": "framework",
   "RB-ETH": "framework",
   "RB-DMAF": "framework",
   "RB-DSGF": "framework",
   "RB-CAF": "framework",
   "RB-SFIA": "framework",
   "RB-ASCOF": "framework",
   "RB-PKSB": "framework",
   "RB-AFCAREER": "framework",
   "RB-SUCCESS": "framework",
   "RB-CALD": "framework",
   "RB-DSPT": "framework",
   "RB-DAMA": "methodology",
   "RB-DCAM": "methodology",
   "RB-CMMI": "methodology",
   "RB-GREEN": "methodology",
   "RB-MAGENTA": "methodology",
   "RB-AQUA": "methodology",
   "RB-ORANGE": "methodology",
   "RB-QAAD": "methodology",
   "RB-GDSWAY": "methodology",
   "RB-DDATPB": "methodology",
   "RB-SOURCING": "methodology",
   "RB-IAAP": "methodology",
   "RB-SVCASSESS": "methodology",
   "RB-REFARCH": "methodology"
  },
  "aliases": {
   "RB-DAMA": [
    "DAMA-DMBOK",
    "DMBOK"
   ],
   "RB-DCAM": [
    "DCAM"
   ],
   "RB-CMMI": [
    "CMMI"
   ],
   "RB-SVC": [
    "Service Standard"
   ],
   "RB-TCOP": [
    "Technology Code of Practice"
   ],
   "RB-GDSWAY": [
    "GDS Way"
   ],
   "RB-DPA": [
    "Data Protection Act 2018"
   ],
   "RB-DUAA": [
    "Data (Use and Access) Act 2025",
    "Data (Use and Access) Act"
   ],
   "RB-DEA": [
    "Digital Economy Act 2017",
    "Digital Economy Act"
   ],
   "RB-EQA": [
    "Equality Act 2010"
   ],
   "RB-PRA": [
    "Public Records Act 1958",
    "Public Records Act"
   ],
   "RB-PA23": [
    "Procurement Act 2023"
   ],
   "RB-GSC": [
    "Government Security Classifications"
   ],
   "RB-DCAT": [
    "DCAT"
   ],
   "RB-DQV": [
    "Data Quality Vocabulary"
   ],
   "RB-SKOS": [
    "SKOS"
   ],
   "RB-PROVO": [
    "PROV-O"
   ],
   "RB-CSVW": [
    "CSV on the Web",
    "CSVW"
   ],
   "RB-GEMINI": [
    "UK GEMINI"
   ],
   "RB-SDMX": [
    "SDMX"
   ],
   "RB-OLINEAGE": [
    "OpenLineage"
   ],
   "RB-ODCS": [
    "Open Data Contract Standard"
   ],
   "RB-ODPS": [
    "Open Data Product Standard"
   ],
   "RB-OAS": [
    "OpenAPI Specification",
    "OpenAPI"
   ],
   "RB-MCPSPEC": [
    "Model Context Protocol"
   ],
   "RB-OGL": [
    "Open Government Licence"
   ],
   "RB-COP": [
    "Code of Practice for Statistics"
   ],
   "RB-GREEN": [
    "Green Book"
   ],
   "RB-MAGENTA": [
    "Magenta Book"
   ],
   "RB-AQUA": [
    "AQuA Book"
   ],
   "RB-ORANGE": [
    "Orange Book"
   ],
   "RB-CALD": [
    "Caldicott Principles"
   ],
   "RB-DSPT": [
    "Data Security and Protection Toolkit"
   ],
   "RB-SNOMED": [
    "SNOMED CT"
   ],
   "RB-FHIRUK": [
    "FHIR UK Core"
   ],
   "RB-UPRN": [
    "UPRN"
   ],
   "RB-CAF": [
    "Cyber Assessment Framework"
   ],
   "RB-SFIA": [
    "SFIA"
   ],
   "RB-DDAT": [
    "Government Digital and Data Profession Capability Framework"
   ],
   "RB-ETH": [
    "Data and AI Ethics Framework"
   ],
   "RB-ATRS": [
    "Algorithmic Transparency Recording Standard"
   ],
   "RB-DMAF": [
    "Data Maturity Assessment for Government",
    "Data Maturity Assessment"
   ],
   "RB-ISO15489": [
    "ISO 15489"
   ],
   "RB-ISO23081": [
    "ISO 23081"
   ],
   "RB-DCB0129": [
    "DCB0129"
   ],
   "RB-DCB0160": [
    "DCB0160"
   ],
   "RB-GOVS002": [
    "GovS 002"
   ],
   "RB-GOVS005": [
    "GovS 005"
   ],
   "RB-GOVS007": [
    "GovS 007"
   ],
   "RB-EUDA": [
    "EU Data Act"
   ],
   "RB-DSA": [
    "Data Standards Authority"
   ],
   "RB-DQHUB": [
    "Government Data Quality Hub",
    "Data Quality Hub"
   ],
   "RB-NDLPUB": [
    "National Data Library"
   ],
   "RB-SBD": [
    "Secure by Design"
   ],
   "RB-AIPLAY": [
    "AI Playbook for the UK Government",
    "AI Playbook"
   ],
   "RB-OPEN": [
    "Open standards for government"
   ],
   "RB-ICOSHARE": [
    "data sharing code of practice"
   ]
  },
  "stages": {
   "gov.mandate": [
    "RB-GOVS005",
    "RB-DMAF",
    "RB-BLUEPRINT",
    "RB-SRO"
   ],
   "gov.frame": [
    "RB-DAMA",
    "RB-DCAM",
    "RB-ETH",
    "RB-DSGF",
    "RB-ORANGE"
   ],
   "gov.assign": [
    "RB-SMROLES",
    "RB-DDAT",
    "RB-KIM",
    "RB-SFIA"
   ],
   "gov.operate": [
    "RB-DPA",
    "RB-ICOSHARE",
    "RB-ICODSA",
    "RB-GSC",
    "RB-TNAIM"
   ],
   "gov.assure": [
    "RB-DMAHUB",
    "RB-IAAP",
    "RB-CMMI",
    "RB-SVCASSESS"
   ],
   "cat.mobilise": [
    "RB-NDLPUB",
    "RB-DSA",
    "RB-METASTD"
   ],
   "cat.discover": [
    "RB-TNAIM",
    "RB-DCATGOV"
   ],
   "cat.designate": [
    "RB-GSC",
    "RB-DPA"
   ],
   "cat.own": [
    "RB-SMROLES",
    "RB-KIM"
   ],
   "cat.describe": [
    "RB-DCAT",
    "RB-DCATGOV",
    "RB-METASTD",
    "RB-SKOS",
    "RB-GEMINI",
    "RB-ISO23081"
   ],
   "cat.publish": [
    "RB-NDLPUB",
    "RB-OGL",
    "RB-API",
    "RB-OAS",
    "RB-AIREADY"
   ],
   "cat.report": [
    "RB-DCATGOV",
    "RB-DSACAT"
   ],
   "cat.maintain": [
    "RB-PROVO",
    "RB-OLINEAGE",
    "RB-TNARET",
    "RB-ISO15489"
   ],
   "dq.identify": [
    "RB-QAAD",
    "RB-DQHUB"
   ],
   "dq.define": [
    "RB-DQV",
    "RB-COP",
    "RB-ODCS"
   ],
   "dq.baseline": [
    "RB-QAAD",
    "RB-AQUA"
   ],
   "dq.prioritise": [
    "RB-GREEN",
    "RB-ORANGE"
   ],
   "dq.improve": [
    "RB-CSVW",
    "RB-UPRN",
    "RB-TECHDEBT"
   ],
   "dq.report": [
    "RB-COP",
    "RB-DQV"
   ],
   "dq.sustain": [
    "RB-DQHUB",
    "RB-ODCS"
   ],
   "dq.review": [
    "RB-MAGENTA",
    "RB-DMAHUB"
   ]
  }
 },
 "area_guide": {
  "meta": {
   "as_of": "2026-11-12",
   "status": "Draft by this portal for review by the profession that owns each area. Not government guidance.",
   "intro": "The DAM Policy asks for three capabilities: data governance, data cataloguing and data quality. Each rests on work in other data management areas. A catalogue record needs to know where the data lives, who can see it and which system is the authoritative source. A quality plan needs the reference data and the flows that feed it. This guide gives each area the activities that matter for the policy, in the order most organisations need them, down to the steps, outputs and evidence.",
   "inputs": [
    {
     "id": "IN-DMBOK",
     "label": "DAMA-DMBOK knowledge areas (names only, linked, not copied)",
     "prov": "V"
    },
    {
     "id": "IN-SSP",
     "label": "Sovereign Standards Platform: introduction, user guide and roadmap (cross-government internal draft, version 1.1, November 2026). Used for the business glossary anatomy, the knowledge organisation ladder, controlled vocabularies, the draft data standards classification, crypto-dependency and residency fields. The pack is not published; the standards classification and the standards crosswalk it describes are drafts in review with the Data Standards Authority.",
     "prov": "O"
    }
   ]
  },
  "stages": [
   {
    "id": "start",
    "name": "Start",
    "when": "Before your first return",
    "does": "What the DAM Policy needs now, so the return is complete and true."
   },
   {
    "id": "build",
    "name": "Build",
    "when": "Before your second return",
    "does": "Makes the next return easier, and makes critical assets safer to reuse."
   },
   {
    "id": "embed",
    "name": "Embed",
    "when": "Business as usual",
    "does": "Keeps the work going without a project, and prepares critical assets for AI and wider sharing."
   }
  ],
  "areas": [
   {
    "id": "DM-ARC",
    "lead": "ARC",
    "owner": "Your design authority or architecture community",
    "why": "The policy asks you to designate the source data set behind any distribution you designate (DAM-R12). You can only do that if you know where each critical asset lives, which copy is authoritative and how it flows. Architecture gives the catalogue its structure.",
    "supplement": "SUP-ARC",
    "activities": [
     {
      "id": "ARC-1",
      "stage": "start",
      "title": "Map where each critical asset lives",
      "goal": "One list that says which systems hold each critical asset, so nothing is designated from the wrong copy.",
      "steps": [
       "Start from the candidate and designation log. For each candidate, ask the steward and custodian which systems hold the data.",
       "Record each system, the copy it holds (master, replica, extract, archive) and who runs it.",
       "Mark copies that are spreadsheets, shared drives or personal stores. These are risks, not sources.",
       "Add the landscape to the catalogue record as related resources, not as separate critical assets."
      ],
      "outputs": [
       "A data landscape list for critical assets",
       "Updated candidate and designation log"
      ],
      "evidence": "Every designated asset has at least one named system and a named custodian.",
      "measure": "Share of critical assets with a named system and custodian.",
      "raci": {
       "ARC": "A",
       "STW": "R",
       "CUS": "C",
       "CAT": "R",
       "OWN": "I"
      },
      "reqs": [
       "DAM-R01",
       "DAM-R12"
      ],
      "caps": [
       "CR-05",
       "CR-12"
      ],
      "refs": [
       "RB-TCOP",
       "RB-REFARCH"
      ],
      "templates": [
       "T-CAT-1"
      ]
     },
     {
      "id": "ARC-2",
      "stage": "start",
      "title": "Name the authoritative source for each critical asset",
      "goal": "Everyone who reuses the asset knows which copy to trust and where to report problems.",
      "steps": [
       "For each critical asset, decide which system is the authoritative source. If two systems disagree, the data owner decides.",
       "Record the source system, the entities it is authoritative for and how other copies are refreshed from it.",
       "Where you designate a distribution, link it to its source data set in the catalogue (DAM-R12).",
       "Record the decision in the decision log, with the date and who made it."
      ],
      "outputs": [
       "Authoritative source named in each catalogue record",
       "Decision log entries"
      ],
      "evidence": "Designated distributions link to their source data set; decisions are dated and owned.",
      "measure": "Share of critical assets with a named authoritative source.",
      "raci": {
       "OWN": "A",
       "ARC": "R",
       "STW": "C",
       "CAT": "R",
       "CUS": "C"
      },
      "reqs": [
       "DAM-R12",
       "DAM-R02"
      ],
      "caps": [
       "CR-12",
       "CR-14"
      ],
      "refs": [
       "RB-REFARCH",
       "RB-DCAT"
      ],
      "templates": [
       "T-CAT-2",
       "T-CAT-4",
       "T-GOV-3"
      ]
     },
     {
      "id": "ARC-3",
      "stage": "build",
      "title": "Draw the main data flows between systems and organisations",
      "goal": "You can say where critical data goes, so sharing, quality and security risks have a place on the map.",
      "steps": [
       "For each critical asset, list the flows in and out: source, target, method (API, file, manual), frequency and owner.",
       "Mark flows that cross organisational boundaries and link each to its data sharing agreement.",
       "Mark manual re-keying and spreadsheet hand-offs. These are where quality usually drops.",
       "Share the flow list with the data quality lead so quality rules sit where data enters and leaves."
      ],
      "outputs": [
       "A data flow list for each critical asset",
       "Links to data sharing agreements"
      ],
      "evidence": "Every external flow of a critical asset has a sharing agreement or a recorded exception.",
      "measure": "Share of external flows with an agreement.",
      "raci": {
       "ARC": "R",
       "STW": "R",
       "CUS": "C",
       "DQL": "C",
       "DPO": "C",
       "OWN": "A"
      },
      "reqs": [
       "DAM-R11",
       "DAM-R15"
      ],
      "caps": [
       "CR-12",
       "CR-28",
       "CR-17"
      ],
      "refs": [
       "RB-API",
       "RB-ICOSHARE",
       "RB-DEA"
      ],
      "templates": [
       "T-GOV-6"
      ]
     },
     {
      "id": "ARC-4",
      "stage": "build",
      "title": "Set a target data architecture and record decisions",
      "goal": "Changes move critical assets toward open, portable designs instead of new legacy.",
      "steps": [
       "Write down the principles for critical data, for example one authoritative source, open formats and documented interfaces.",
       "Record each significant choice as an architecture decision record with the options, the choice and the reason.",
       "Check new systems and contracts against the principles before approval, including how data leaves at exit.",
       "Review the target each year with the governance board."
      ],
      "outputs": [
       "Data architecture principles",
       "Architecture decision records"
      ],
      "evidence": "New systems holding critical data have a decision record and an exit route for the data.",
      "measure": "Share of new systems holding critical data with a recorded exit route.",
      "raci": {
       "ARC": "R",
       "BRD": "A",
       "CML": "C",
       "SVO": "C",
       "CDO": "I"
      },
      "reqs": [
       "DAM-R16",
       "DAM-R04"
      ],
      "caps": [
       "CR-12",
       "CR-32"
      ],
      "refs": [
       "RB-TCOP",
       "RB-OPEN",
       "RB-LOCKIN",
       "RB-CHOOSE"
      ]
     },
     {
      "id": "ARC-5",
      "stage": "embed",
      "title": "Make architecture review a gate in change",
      "goal": "Every change that touches a critical asset updates its landscape, source and flows before it goes live.",
      "steps": [
       "Add a question to your change and assurance gates, such as \"does this change a critical data asset?\".",
       "If yes, require an updated landscape, flow list and catalogue record before go-live.",
       "Feed spend control and service assessment evidence from the same records rather than a new pack.",
       "Report gate results to the governance board each quarter."
      ],
      "outputs": [
       "A gate question and checklist",
       "Quarterly gate report"
      ],
      "evidence": "Changes to critical assets show updated records at go-live.",
      "measure": "Share of changes to critical assets with records updated at go-live.",
      "raci": {
       "PMO": "R",
       "ARC": "R",
       "PDM": "R",
       "BRD": "A",
       "CAT": "C"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-25",
       "CR-12"
      ],
      "refs": [
       "RB-SVCASSESS",
       "RB-SPEND",
       "RB-GOVS005"
      ]
     }
    ]
   },
   {
    "id": "DM-MOD",
    "lead": "ARC",
    "owner": "Your design authority, with data stewards",
    "why": "A catalogue record describes a critical asset; a data model describes what is inside it. Stewards need a model to agree definitions, quality leads need it to write rules, and users need it to judge whether the asset fits their purpose.",
    "supplement": "SUP-ARC",
    "activities": [
     {
      "id": "MOD-1",
      "stage": "start",
      "title": "List the entities and relationships in each critical asset",
      "goal": "A plain list of what the asset is about (people, cases, payments, places) and how they connect.",
      "steps": [
       "With the steward, name the main things the asset records, in business words.",
       "For each, list its identifier and the few attributes people rely on most.",
       "Record how they relate, for example \"a case has one or more payments\".",
       "Attach the list to the catalogue record and keep it with the asset, not in a project folder."
      ],
      "outputs": [
       "Entity and relationship list"
      ],
      "evidence": "Each critical asset links to an entity list that its steward has checked.",
      "measure": "Share of critical assets with an entity list.",
      "raci": {
       "STW": "R",
       "ARC": "R",
       "CAT": "C",
       "OWN": "A"
      },
      "reqs": [
       "DAM-R13",
       "DAM-R02"
      ],
      "caps": [
       "CR-12",
       "CR-06"
      ],
      "refs": [
       "RB-DCAT"
      ],
      "templates": [
       "T-CAT-4"
      ]
     },
     {
      "id": "MOD-2",
      "stage": "build",
      "title": "Agree definitions for the attributes people rely on",
      "goal": "The same word means the same thing in every system and report that uses the asset.",
      "steps": [
       "Pick the attributes that drive decisions, payments or published figures.",
       "Write one plain-English definition for each and name the steward who owns it.",
       "Check the definition against cross-government standards and the business glossary before writing a new one.",
       "Link each attribute to its glossary term, so a change to the definition reaches every model that uses it."
      ],
      "outputs": [
       "Attribute definitions linked to glossary terms"
      ],
      "evidence": "Key attributes link to an approved glossary term with a named owner.",
      "measure": "Share of key attributes linked to an approved term.",
      "raci": {
       "STW": "A",
       "ARC": "R",
       "CAT": "C",
       "DQL": "C"
      },
      "reqs": [
       "DAM-R13"
      ],
      "caps": [
       "CR-11",
       "CR-07"
      ],
      "refs": [
       "RB-SKOS",
       "RB-DSA"
      ],
      "links": [
       "META-1"
      ]
     },
     {
      "id": "MOD-3",
      "stage": "build",
      "title": "Publish a data dictionary with the catalogue record",
      "goal": "Users can see the columns, types and allowed values before they ask for access.",
      "steps": [
       "Export the column names, types, formats and allowed values from the authoritative source.",
       "Add the definitions from MOD-2 and mark personal or sensitive fields.",
       "Publish the dictionary as a machine-readable file (for example CSV on the Web) linked from the catalogue record.",
       "Regenerate it from the source when the structure changes, rather than editing by hand."
      ],
      "outputs": [
       "Machine-readable data dictionary"
      ],
      "evidence": "The catalogue record links to a current data dictionary.",
      "measure": "Share of critical assets with a current dictionary.",
      "raci": {
       "CAT": "R",
       "CUS": "R",
       "STW": "A",
       "DPO": "C"
      },
      "reqs": [
       "DAM-R02",
       "DAM-R13"
      ],
      "caps": [
       "CR-06",
       "CR-11"
      ],
      "refs": [
       "RB-CSVW",
       "RB-DCAT"
      ]
     },
     {
      "id": "MOD-4",
      "stage": "embed",
      "title": "Control changes to models",
      "goal": "A change to structure never breaks reports, sharing or quality rules without warning.",
      "steps": [
       "Version each model and dictionary. Record what changed and why.",
       "Before a change, list who uses the affected attributes, using the flow list and reuse records.",
       "Tell users in advance and give a date. Mark attributes as retired rather than deleting them.",
       "Where others depend on the asset, record the new structure in its data contract (see INT-4)."
      ],
      "outputs": [
       "Versioned models",
       "Change notices",
       "Data contracts for shared assets"
      ],
      "evidence": "Structure changes have a version, a notice and a date.",
      "measure": "Unplanned breaks to downstream users each year.",
      "raci": {
       "ARC": "R",
       "STW": "A",
       "USR": "I",
       "DQL": "C"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-11",
       "CR-19"
      ],
      "refs": [
       "RB-ODCS"
      ],
      "links": [
       "INT-4"
      ]
     }
    ]
   },
   {
    "id": "DM-OPS",
    "lead": "CUS",
    "owner": "Your technology operations or hosting team",
    "why": "A critical asset is only useful if it is available, recoverable and kept for the right time. The policy's purposes, such as public service delivery, depend on the data being there when needed.",
    "activities": [
     {
      "id": "OPS-1",
      "stage": "start",
      "title": "Name the custodian and hosting for each critical asset",
      "goal": "Someone is responsible for keeping each asset running, and you know where it is hosted.",
      "steps": [
       "Add a custodian to each ownership register entry, separate from the data owner.",
       "Record the hosting (on premises, cloud, supplier service) and the contract that covers it.",
       "Record where the data is physically stored, if your security or contracts require it.",
       "Tell the custodian which assets are critical and why."
      ],
      "outputs": [
       "Custodian and hosting in the ownership register"
      ],
      "evidence": "Every critical asset has a custodian distinct from its owner, or a recorded reason why not.",
      "measure": "Share of critical assets with a named custodian.",
      "raci": {
       "OWN": "A",
       "CUS": "R",
       "STW": "C",
       "COO": "I"
      },
      "reqs": [
       "DAM-R05",
       "DAM-R02"
      ],
      "caps": [
       "CR-07",
       "CR-12"
      ],
      "refs": [
       "RB-CLOUD",
       "RB-NCSCCLOUD"
      ],
      "templates": [
       "T-GOV-2"
      ]
     },
     {
      "id": "OPS-2",
      "stage": "build",
      "title": "Back up critical assets and test that you can restore them",
      "goal": "A failure or attack does not lose critical data or the service that depends on it.",
      "steps": [
       "Agree with the owner how much data the service could lose and how long it could be without it.",
       "Check backups meet that, including copies held offline or out of reach of ransomware.",
       "Test a restore at least once a year and record the result.",
       "Fix gaps and record any accepted risk in the exception register."
      ],
      "outputs": [
       "Recovery targets",
       "Restore test record"
      ],
      "evidence": "A dated restore test for each critical asset.",
      "measure": "Share of critical assets restored in a test in the last 12 months.",
      "raci": {
       "CUS": "R",
       "OWN": "A",
       "SVO": "C",
       "IAO": "C"
      },
      "reqs": [
       "DAM-R09"
      ],
      "caps": [
       "CR-31",
       "CR-10"
      ],
      "refs": [
       "RB-CAF",
       "RB-NCSCIR"
      ],
      "templates": [
       "T-GOV-4"
      ]
     },
     {
      "id": "OPS-3",
      "stage": "build",
      "title": "Monitor availability, freshness and capacity",
      "goal": "Problems are found by the custodian before users find them.",
      "steps": [
       "Monitor whether each critical asset is available and when it was last updated.",
       "Set a freshness threshold with the data quality lead and alert when it is missed.",
       "Feed failures into the data quality issue log, not just the service desk.",
       "Review capacity before peaks, such as year end."
      ],
      "outputs": [
       "Availability and freshness monitoring",
       "Issues logged for failures"
      ],
      "evidence": "Freshness failures appear in the issue log with an owner.",
      "measure": "Freshness failures for critical assets each quarter.",
      "raci": {
       "CUS": "R",
       "DQL": "C",
       "OWN": "A"
      },
      "reqs": [
       "DAM-R06",
       "DAM-R15"
      ],
      "caps": [
       "CR-08",
       "CR-10"
      ],
      "refs": [
       "RB-DQV",
       "RB-DQHUB"
      ],
      "templates": [
       "T-DQ-2"
      ]
     },
     {
      "id": "OPS-4",
      "stage": "embed",
      "title": "Plan retention, archiving and decommissioning",
      "goal": "Data is kept as long as needed and no longer, and nothing critical is lost when a system retires.",
      "steps": [
       "Apply the retention set for each record (see DOC-2) to every store and copy that holds it.",
       "Archive or delete copies on schedule and record what was done.",
       "When a system retires, migrate or archive critical data first, and update the catalogue record.",
       "Remove decommissioned copies so they cannot be used by mistake."
      ],
      "outputs": [
       "Retention linked to each store",
       "Decommissioning checklist"
      ],
      "evidence": "Retired systems show where their critical data went.",
      "measure": "Retired systems with critical data accounted for.",
      "raci": {
       "CUS": "R",
       "IAO": "A",
       "MIG": "R",
       "CAT": "C"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-10",
       "CR-26",
       "CR-15"
      ],
      "refs": [
       "RB-TNARET",
       "RB-RETIRE",
       "RB-LEGACY"
      ],
      "links": [
       "DOC-2"
      ]
     }
    ]
   },
   {
    "id": "DM-SEC",
    "lead": "IAO",
    "owner": "Your security team, data protection officer and information asset owners",
    "why": "In-scope assets are classified OFFICIAL, including handling markings such as 'personal' (DAM-R01). The catalogue must say how each asset is protected and who may use it, or it cannot be shared safely.",
    "activities": [
     {
      "id": "SEC-1",
      "stage": "start",
      "title": "Record classification and personal data for each asset",
      "goal": "Every catalogue record says how the asset is classified and whether it holds personal data.",
      "steps": [
       "Record the classification and any handling marking from your information asset register.",
       "Mark whether the asset holds personal or special category data, with the data protection officer.",
       "Link to the data protection impact assessment where there is one.",
       "Check the record before it goes into the return. Never put the data itself in the catalogue."
      ],
      "outputs": [
       "Classification and personal data fields in each record"
      ],
      "evidence": "No critical asset record has a blank classification.",
      "measure": "Share of records with classification and personal data recorded.",
      "raci": {
       "IAO": "A",
       "DPO": "R",
       "CAT": "R",
       "STW": "C"
      },
      "reqs": [
       "DAM-R01",
       "DAM-R13"
      ],
      "caps": [
       "CR-16",
       "CR-17"
      ],
      "refs": [
       "RB-GSC",
       "RB-DPA",
       "RB-ICODSA"
      ],
      "templates": [
       "T-CAT-2"
      ]
     },
     {
      "id": "SEC-2",
      "stage": "start",
      "title": "Record who can access each asset, and on what basis",
      "goal": "People asking for data can see the route and the conditions without starting from scratch.",
      "steps": [
       "Record who can access the asset now (roles, not names) and how access is granted.",
       "Record the legal basis for any sharing and link to the agreement.",
       "Say how to request access in the catalogue record.",
       "Review access at least once a year with the owner."
      ],
      "outputs": [
       "Access rules and request route in the catalogue record"
      ],
      "evidence": "Each record says how to request access.",
      "measure": "Share of records with an access route.",
      "raci": {
       "OWN": "A",
       "IAO": "R",
       "DPO": "C",
       "CAT": "R"
      },
      "reqs": [
       "DAM-R02",
       "DAM-R13"
      ],
      "caps": [
       "CR-16",
       "CR-17"
      ],
      "refs": [
       "RB-ICOSHARE",
       "RB-DEA",
       "RB-DUAA"
      ],
      "templates": [
       "T-GOV-6"
      ]
     },
     {
      "id": "SEC-3",
      "stage": "build",
      "title": "Link critical assets to cyber risk",
      "goal": "Security effort goes first to the data that matters most.",
      "steps": [
       "Give your security team the list of critical assets and their purposes.",
       "Map each to the systems and Cyber Assessment Framework outcomes that protect it.",
       "Add any gap to the risk register with an owner and a date.",
       "Use the same mapping as evidence for GovAssure rather than a separate survey."
      ],
      "outputs": [
       "Critical assets mapped to systems and CAF outcomes",
       "Risks recorded"
      ],
      "evidence": "Each critical asset is covered by a system in your cyber assurance scope.",
      "measure": "Share of critical assets covered by cyber assurance.",
      "raci": {
       "IAO": "A",
       "CUS": "R",
       "CDO": "I",
       "OWN": "C"
      },
      "reqs": [
       "DAM-R09",
       "DAM-R01"
      ],
      "caps": [
       "CR-19",
       "CR-31",
       "CR-16"
      ],
      "refs": [
       "RB-CAF",
       "RB-GCSS",
       "RB-GOVS007"
      ]
     },
     {
      "id": "SEC-4",
      "stage": "build",
      "title": "Make data incidents reach owners and quality leads",
      "goal": "A breach or corruption of critical data is handled as a data problem as well as a security one.",
      "steps": [
       "Add critical asset owners to the incident response contact list.",
       "After an incident, check data integrity and log any quality impact.",
       "Tell users of affected data what changed and when it is fixed.",
       "Record lessons in the decision log and update controls."
      ],
      "outputs": [
       "Incident plan that names data owners",
       "Quality impact logged"
      ],
      "evidence": "Incidents on critical assets have a quality impact entry.",
      "measure": "Time from incident to notifying data users.",
      "raci": {
       "IAO": "A",
       "CUS": "R",
       "OWN": "R",
       "DQL": "C",
       "DPO": "C"
      },
      "reqs": [
       "DAM-R05",
       "DAM-R15"
      ],
      "caps": [
       "CR-31",
       "CR-09"
      ],
      "refs": [
       "RB-NCSCIR"
      ],
      "templates": [
       "T-DQ-2",
       "T-GOV-3"
      ]
     },
     {
      "id": "SEC-5",
      "stage": "embed",
      "title": "Record which critical assets depend on encryption, and where they are stored",
      "goal": "When encryption or data residency rules change, you can find the affected assets by a search, not a survey.",
      "steps": [
       "Add two fields to the catalogue record or asset register: crypto-dependency (does it rely on encryption?) and data residency (where is it stored?).",
       "For crypto-dependency, record whether the asset relies on public-key cryptography in storage or transfer, and where.",
       "For residency, record the country where it is stored and processed, and any contract terms.",
       "Use the fields to plan migration to post-quantum cryptography on the NCSC timeline."
      ],
      "outputs": [
       "Crypto-dependency and residency fields"
      ],
      "evidence": "Critical assets carry both fields.",
      "measure": "Share of critical assets with both fields recorded.",
      "raci": {
       "IAO": "A",
       "CUS": "R",
       "ARC": "C",
       "CAT": "R"
      },
      "reqs": [
       "DAM-R13"
      ],
      "caps": [
       "CR-31",
       "CR-32"
      ],
      "refs": [
       "RB-NCSCPQC",
       "RB-CAF"
      ],
      "source": "IN-SSP"
     }
    ]
   },
   {
    "id": "DM-INT",
    "lead": "ARC",
    "owner": "Your architecture and integration teams, with data stewards",
    "why": "The policy's introduction promises minimum requirements for interoperability (DAM-R16). Until they are published, using the identifiers and standards government already expects makes your assets easier to join and reuse.",
    "activities": [
     {
      "id": "INT-1",
      "stage": "start",
      "title": "Use the identifiers and standards government expects",
      "goal": "Your critical assets can be matched with others without guesswork.",
      "steps": [
       "List the identifiers in each critical asset, such as UPRN for addresses or company numbers for organisations.",
       "Check each against the Data Standards Authority's recommended standards and the open standards list.",
       "Record the identifiers and standards used in the catalogue record.",
       "Where you use a local identifier, record how it maps to the national one."
      ],
      "outputs": [
       "Identifiers and standards recorded per asset"
      ],
      "evidence": "Records name the identifiers and standards used.",
      "measure": "Share of critical assets that use at least one recommended identifier.",
      "raci": {
       "STW": "R",
       "ARC": "C",
       "CAT": "R",
       "OWN": "A"
      },
      "reqs": [
       "DAM-R16",
       "DAM-R13"
      ],
      "caps": [
       "CR-11"
      ],
      "refs": [
       "RB-UPRN",
       "RB-DSA",
       "RB-OPEN",
       "RB-DSACAT"
      ]
     },
     {
      "id": "INT-2",
      "stage": "build",
      "title": "Classify and crosswalk the standards each asset meets",
      "goal": "Anyone can see which standards an asset meets, and how your terms map to them, in a form machines can read.",
      "steps": [
       "For each standard you use, place it by category, topic and subject. The draft government classification has five building blocks: metadata, common reference data, service and platform design, data lifecycle, and domain-specific.",
       "Map your local terms to the matching concepts in the cross-government standards, with a confidence level for each match.",
       "Mark terms with no match and send them to the Data Standards Authority rather than inventing a standard.",
       "Publish the statement of standards met as part of the catalogue record."
      ],
      "outputs": [
       "Standards statement per asset",
       "Term mappings with confidence",
       "Gaps sent to the DSA"
      ],
      "evidence": "Critical asset records carry a standards statement.",
      "measure": "Share of critical assets with a standards statement.",
      "raci": {
       "STW": "R",
       "CAT": "R",
       "ARC": "C",
       "OWN": "A"
      },
      "reqs": [
       "DAM-R16",
       "DAM-R13"
      ],
      "caps": [
       "CR-11"
      ],
      "refs": [
       "RB-DSA",
       "RB-SKOS",
       "RB-DCAT"
      ],
      "source": "IN-SSP"
     },
     {
      "id": "INT-3",
      "stage": "build",
      "title": "Share critical data through documented interfaces",
      "goal": "Other teams reuse the authoritative source, not a copy made for one project.",
      "steps": [
       "For each regular consumer, offer an API or a published distribution from the authoritative source.",
       "Document it with an open description format and link it from the catalogue record.",
       "Put a data sharing agreement in place for each external consumer.",
       "Retire one-off extracts once the interface is in use."
      ],
      "outputs": [
       "Documented interfaces",
       "Sharing agreements"
      ],
      "evidence": "Regular consumers use a documented interface.",
      "measure": "One-off extracts of critical assets each year.",
      "raci": {
       "ARC": "R",
       "CUS": "R",
       "OWN": "A",
       "DPO": "C",
       "USR": "I"
      },
      "reqs": [
       "DAM-R12",
       "DAM-R11"
      ],
      "caps": [
       "CR-12",
       "CR-17",
       "CR-28"
      ],
      "refs": [
       "RB-API",
       "RB-OAS",
       "RB-ICOSHARE"
      ],
      "templates": [
       "T-GOV-6"
      ]
     },
     {
      "id": "INT-4",
      "stage": "embed",
      "title": "Agree data contracts and record lineage",
      "goal": "Producers and consumers know what to expect, and anyone can trace a figure back to its source.",
      "steps": [
       "For shared assets, write a data contract covering structure, quality rules, freshness and support.",
       "Record lineage for critical flows in a standard format, from source through each transformation.",
       "Check contracts automatically where you can, and log breaches as quality issues.",
       "Review contracts with suppliers and partners each year."
      ],
      "outputs": [
       "Data contracts",
       "Lineage records"
      ],
      "evidence": "Shared critical assets have a contract and lineage.",
      "measure": "Contract breaches each quarter.",
      "raci": {
       "OWN": "A",
       "ARC": "R",
       "DQL": "R",
       "CML": "C"
      },
      "reqs": [
       "DAM-R07",
       "DAM-R06"
      ],
      "caps": [
       "CR-11",
       "CR-20"
      ],
      "refs": [
       "RB-ODCS",
       "RB-OLINEAGE",
       "RB-PROVO"
      ]
     }
    ]
   },
   {
    "id": "DM-DOC",
    "lead": "IAO",
    "owner": "Your records and information management team",
    "why": "Many critical assets are also public records. The catalogue and the records schedule should agree on what the asset is, who is responsible for it and how long it is kept.",
    "activities": [
     {
      "id": "DOC-1",
      "stage": "start",
      "title": "Check which critical assets are also public records",
      "goal": "Records managers and data owners work from the same list.",
      "steps": [
       "Share the critical asset list with your records team.",
       "For each asset, record whether it is a public record and which schedule covers it.",
       "Agree who decides on retention and disposal, the data owner or the information asset owner.",
       "Note any asset whose records status is unclear and resolve it before the return."
      ],
      "outputs": [
       "Records status in the ownership register"
      ],
      "evidence": "Each critical asset says whether it is a public record.",
      "measure": "Share of critical assets with a records status.",
      "raci": {
       "IAO": "A",
       "OWN": "C",
       "COO": "R",
       "CAT": "I"
      },
      "reqs": [
       "DAM-R01",
       "DAM-R11"
      ],
      "caps": [
       "CR-15"
      ],
      "refs": [
       "RB-PRA",
       "RB-TNAIM"
      ],
      "templates": [
       "T-GOV-2"
      ]
     },
     {
      "id": "DOC-2",
      "stage": "build",
      "title": "Attach retention and disposal to each catalogue record",
      "goal": "Users can see how long data is kept and what happens to it next.",
      "steps": [
       "Copy the retention period and disposal action from the schedule into the catalogue record.",
       "Record the review date and who approved any longer retention.",
       "Check the record's own metadata is kept as long as the data.",
       "Flag assets past their retention date to the owner."
      ],
      "outputs": [
       "Retention and disposal fields filled in"
      ],
      "evidence": "No critical asset is past its retention date without an approved reason.",
      "measure": "Assets past retention without a reason.",
      "raci": {
       "IAO": "A",
       "CAT": "R",
       "OWN": "C"
      },
      "reqs": [
       "DAM-R13",
       "DAM-R04"
      ],
      "caps": [
       "CR-15",
       "CR-10"
      ],
      "refs": [
       "RB-TNARET",
       "RB-ISO15489"
      ],
      "templates": [
       "T-CAT-2",
       "T-GOV-2"
      ]
     },
     {
      "id": "DOC-3",
      "stage": "embed",
      "title": "Transfer, archive or destroy with evidence",
      "goal": "Disposal is lawful, recorded and reflected in the catalogue.",
      "steps": [
       "When disposal is due, carry out the action in the schedule and record it.",
       "For records selected for permanent preservation, follow the transfer process.",
       "Keep the catalogue record, marked as retired, with where the data went.",
       "Report disposals to the governance board each year."
      ],
      "outputs": [
       "Disposal records",
       "Retired catalogue records"
      ],
      "evidence": "Retired records say what happened to the data.",
      "measure": "Disposals recorded each year.",
      "raci": {
       "IAO": "A",
       "CUS": "R",
       "CAT": "R",
       "BRD": "I"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-15",
       "CR-26"
      ],
      "refs": [
       "RB-TNATRANS",
       "RB-ISO23081"
      ]
     }
    ]
   },
   {
    "id": "DM-REF",
    "lead": "STW",
    "owner": "Your data stewards, with the owners of national registers",
    "why": "The policy asks for dates in ISO 8601 and plain values instead of blanks (DAM-R13). Reference data goes further: shared code lists for countries, places, organisations and categories are what let critical assets be joined and compared.",
    "supplement": "SUP-REF",
    "activities": [
     {
      "id": "REF-1",
      "stage": "start",
      "title": "Find the reference data each critical asset depends on",
      "goal": "You know which code lists each asset uses and where they come from.",
      "steps": [
       "List the coded fields in each critical asset, such as country, local authority, sector or status.",
       "For each, record the code list used and its source, for example ISO 3166 for countries or ONS codes for geography.",
       "Record dates in ISO 8601 and currencies in ISO 4217.",
       "Mark local code lists that duplicate a national one."
      ],
      "outputs": [
       "Code lists recorded per asset"
      ],
      "evidence": "Coded fields name their code list.",
      "measure": "Share of coded fields with a named national code list.",
      "raci": {
       "STW": "R",
       "CAT": "C",
       "DQL": "C",
       "OWN": "A"
      },
      "reqs": [
       "DAM-R13"
      ],
      "caps": [
       "CR-14",
       "CR-11"
      ],
      "refs": [
       "RB-ISO8601",
       "RB-ISO3166",
       "RB-ISO4217",
       "RB-ONSGEO"
      ]
     },
     {
      "id": "REF-2",
      "stage": "build",
      "title": "Use shared controlled vocabularies, not local copies",
      "goal": "Fewer local lists, so data joins across services without mapping by hand.",
      "steps": [
       "Replace local lists with the national one where it exists, for example ONS geography codes, UPRN and USRN, company numbers, school identifiers and the GSS harmonised standards for age, sex, ethnicity and language.",
       "Use SIC, SOC and CPV codes for sector, occupation and spend.",
       "Where you must keep a local list, map it to the national one and publish the mapping.",
       "Use shared values for status and lifecycle (draft, active, superseded, retired) across catalogues."
      ],
      "outputs": [
       "Local lists retired or mapped"
      ],
      "evidence": "Local lists that duplicate a national one have a mapping or a retirement date.",
      "measure": "Local lists retired or mapped.",
      "raci": {
       "STW": "R",
       "ARC": "C",
       "DQL": "C",
       "OWN": "A"
      },
      "reqs": [
       "DAM-R16"
      ],
      "caps": [
       "CR-14",
       "CR-11"
      ],
      "refs": [
       "RB-GSSHARM",
       "RB-ONSGEO",
       "RB-UPRN",
       "RB-SKOS"
      ],
      "source": "IN-SSP"
     },
     {
      "id": "REF-3",
      "stage": "build",
      "title": "Name a master record for shared entities",
      "goal": "People, organisations and places are recorded once and matched consistently.",
      "steps": [
       "Pick the shared entities your critical assets hold in more than one place.",
       "Name the master source for each and the identifier used to match records.",
       "Write the matching and duplicate rules, and who resolves doubtful matches.",
       "Measure duplicates and fix them at source."
      ],
      "outputs": [
       "Master source and matching rules per entity"
      ],
      "evidence": "Shared entities have a named master source.",
      "measure": "Duplicate rate for shared entities.",
      "raci": {
       "OWN": "A",
       "STW": "R",
       "ARC": "R",
       "DQL": "C"
      },
      "reqs": [
       "DAM-R12"
      ],
      "caps": [
       "CR-14",
       "CR-12"
      ],
      "refs": [
       "RB-UPRN",
       "RB-REFARCH"
      ]
     },
     {
      "id": "REF-5",
      "stage": "build",
      "title": "Find peers before you buy or build",
      "goal": "You learn from public bodies that already run the tool or keep the list, before you commit.",
      "steps": [
       "Look up the tool in the repos asset catalogue's register of expertise, which lists the public bodies that buy or build with it, from tender and contract notices and their public code.",
       "Check whether the list you need is already published, for example the GOV.UK organisations, the planning data registers, the NHS Organisation Data Service, Get Information about Schools or Companies House.",
       "Ask in the cross-government data management community, and note who has done it before.",
       "Read any public code peers share, such as deployment and pipeline code, before you design your own."
      ],
      "outputs": [
       "A list of peers and existing sources",
       "Questions to ask them"
      ],
      "evidence": "The business case names peers asked and existing sources considered.",
      "measure": "Proposals that name peers and existing sources.",
      "raci": {
       "STW": "R",
       "ARC": "R",
       "OWN": "A"
      },
      "reqs": [
       "DAM-R16"
      ],
      "caps": [
       "CR-14"
      ],
      "refs": [
       "RB-OPENSRC",
       "RB-CHOOSE"
      ]
     },
     {
      "id": "REF-6",
      "stage": "build",
      "title": "Choose a master data tool with exit in mind",
      "goal": "The tool fits how you run services, and your master data can leave it.",
      "steps": [
       "Ask how it is hosted and supported, and whether your cloud and support teams can run it without the supplier.",
       "Ask how releases and upgrades work, and how you test them before they reach live data.",
       "Ask how security vulnerabilities are found, reported and fixed, and how fast.",
       "Check the screens your stewards and developers will use meet the accessibility regulations, not only the public ones.",
       "Make export a contract term. Master and reference data, with match and survivorship rules and history, must come out in an open format through a documented API."
      ],
      "outputs": [
       "Evaluation against hosting",
       "releases",
       "support",
       "vulnerabilities",
       "accessibility and exit",
       "Exit terms in the contract"
      ],
      "evidence": "The contract names the export format and the API.",
      "measure": "Master data tools with tested export.",
      "raci": {
       "ARC": "R",
       "OWN": "A",
       "STW": "C"
      },
      "reqs": [
       "DAM-R12"
      ],
      "caps": [
       "CR-14",
       "CR-12"
      ],
      "refs": [
       "RB-TCOP11",
       "RB-TCOP4",
       "RB-NCSCCLOUD",
       "RB-A11YREQ",
       "RB-API"
      ]
     },
     {
      "id": "REF-7",
      "stage": "embed",
      "title": "Publish shared lists as open, versioned data",
      "goal": "Others reuse your list instead of copying it, and every copy can tell when it is out of date.",
      "steps": [
       "Name an owner and a steward for each list you publish.",
       "Give every entry a persistent identifier that does not change when its name or web address does.",
       "Publish JSON first, with CSV and its metadata for spreadsheets, and a catalogue record so others can find it.",
       "Take changes as proposals a steward accepts or rejects in the open, and version every release.",
       "Join other bodies' lists by their identifiers rather than copying their values."
      ],
      "outputs": [
       "Published list with owner",
       "identifiers and versions",
       "Catalogue record"
      ],
      "evidence": "The list has a named owner, persistent identifiers and a version history.",
      "measure": "Published lists reused by another team.",
      "raci": {
       "STW": "R",
       "OWN": "A",
       "CAT": "R",
       "USR": "I"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-14",
       "CR-11"
      ],
      "refs": [
       "RB-REFDATA",
       "RB-SKOS",
       "RB-API"
      ]
     },
     {
      "id": "REF-4",
      "stage": "embed",
      "title": "Govern changes to code lists",
      "goal": "A change to a code list never silently breaks a report or a share.",
      "steps": [
       "Version each code list you own. Record what changed and from when.",
       "Never delete a code. Mark it as retired and point to its replacement.",
       "Tell users before a change takes effect.",
       "Publish your code lists in an open format so others can reuse them."
      ],
      "outputs": [
       "Versioned code lists",
       "Change notices"
      ],
      "evidence": "Code lists have versions and deprecation markers.",
      "measure": "Code list changes with notice given.",
      "raci": {
       "STW": "A",
       "CAT": "R",
       "USR": "I"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-14",
       "CR-11"
      ],
      "refs": [
       "RB-SKOS"
      ]
     }
    ]
   },
   {
    "id": "DM-BI",
    "lead": "DQL",
    "owner": "Your analysis and reporting teams",
    "why": "Each critical asset must support at least one of the policy's seven purposes (DAM-R11). Reports, dashboards and statistics are where much of that value shows, and where quality problems reach decision makers.",
    "activities": [
     {
      "id": "BI-1",
      "stage": "start",
      "title": "List the reports and statistics that use each critical asset",
      "goal": "You can show who relies on the asset, which supports its designation and its priority.",
      "steps": [
       "Ask analysis and reporting teams which reports, dashboards and statistics use each critical asset.",
       "Record each use against the asset, with the decision or publication it supports.",
       "Use the list as evidence of the purpose in the return.",
       "Share it with the data quality lead, who uses it to set the importance of purpose in the issues framework."
      ],
      "outputs": [
       "Reuse list per asset"
      ],
      "evidence": "Each critical asset has at least one recorded use.",
      "measure": "Recorded uses per critical asset.",
      "raci": {
       "USR": "R",
       "STW": "R",
       "DQL": "C",
       "OWN": "A"
      },
      "reqs": [
       "DAM-R11",
       "DAM-R15"
      ],
      "caps": [
       "CR-02",
       "CR-04"
      ],
      "refs": [
       "RB-COP"
      ]
     },
     {
      "id": "BI-2",
      "stage": "build",
      "title": "Show quality and provenance next to published figures",
      "goal": "People reading a figure know how good the data behind it is.",
      "steps": [
       "Publish the data quality statement with each regular report that uses a critical asset.",
       "Say where the data came from and when it was extracted.",
       "Flag known issues from the issue log that affect the figures.",
       "Follow the Code of Practice for Statistics where the output is official statistics."
      ],
      "outputs": [
       "Quality statements with reports"
      ],
      "evidence": "Regular reports link to a quality statement.",
      "measure": "Share of regular reports with a quality statement.",
      "raci": {
       "DQL": "R",
       "USR": "R",
       "OWN": "A"
      },
      "reqs": [
       "DAM-R06"
      ],
      "caps": [
       "CR-08",
       "CR-04"
      ],
      "refs": [
       "RB-QAAD",
       "RB-COP"
      ],
      "templates": [
       "T-DQ-3"
      ]
     },
     {
      "id": "BI-3",
      "stage": "build",
      "title": "Make analytical copies traceable to their source",
      "goal": "Every warehouse table or extract can be traced back to its critical asset.",
      "steps": [
       "Record which critical asset each analytical table comes from.",
       "Record the transformations applied, in the lineage format agreed for shared flows (see INT-4).",
       "Remove unmanaged copies, or bring them under the same quality rules.",
       "Link analytical copies from the catalogue record as distributions."
      ],
      "outputs": [
       "Lineage from source to report"
      ],
      "evidence": "Analytical copies link back to their source.",
      "measure": "Share of analytical copies with recorded lineage.",
      "raci": {
       "DQL": "R",
       "ARC": "C",
       "CAT": "R",
       "OWN": "A"
      },
      "reqs": [
       "DAM-R12"
      ],
      "caps": [
       "CR-12",
       "CR-19"
      ],
      "refs": [
       "RB-PROVO",
       "RB-OLINEAGE"
      ],
      "links": [
       "INT-4"
      ]
     },
     {
      "id": "BI-4",
      "stage": "embed",
      "title": "Measure the value and reuse of critical assets",
      "goal": "The annual review knows which assets earn their keep and which need investment.",
      "steps": [
       "Count uses, users and decisions supported for each critical asset each year.",
       "Set this beside the cost of keeping the asset and its quality score.",
       "Report to the governance board as part of the annual review.",
       "Use the results to prioritise improvement and investment."
      ],
      "outputs": [
       "Annual value and reuse summary"
      ],
      "evidence": "The annual review includes value and reuse.",
      "measure": "Critical assets with a value and reuse figure.",
      "raci": {
       "CDO": "A",
       "DQL": "R",
       "COO": "R",
       "BRD": "C"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-29",
       "CR-04",
       "CR-24"
      ],
      "refs": [
       "RB-GREEN"
      ]
     }
    ]
   },
   {
    "id": "DM-META",
    "lead": "CAT",
    "owner": "Your catalogue manager, with data stewards",
    "why": "The cataloguing playbook covers what the policy asks for. These activities go further, toward governed vocabularies and machine-readable metadata that AI tools and the National Data Library can use.",
    "playbook": "cat",
    "activities": [
     {
      "id": "META-1",
      "stage": "build",
      "title": "Govern a business glossary",
      "goal": "Each important term has one agreed meaning, an owner and a history.",
      "steps": [
       "For each term, record a preferred label, other labels (synonyms and abbreviations), a one-sentence plain-English definition and a scope note saying when to use it.",
       "Name the owner (a steward), the source standard or law it comes from, and the body that endorsed it.",
       "Give it a status (draft, in review, approved, deprecated), a version and valid from and to dates.",
       "Map it to the equivalent term in other standards. When a term retires, point to its replacement; terms are deprecated, never deleted.",
       "Review each term every year, or when its source changes, and log every change."
      ],
      "outputs": [
       "A business glossary with owners",
       "status and history"
      ],
      "evidence": "Approved terms have an owner, a source and a review date.",
      "measure": "Share of governed terms with a named steward.",
      "raci": {
       "STW": "A",
       "CAT": "R",
       "BRD": "C",
       "USR": "I"
      },
      "reqs": [
       "DAM-R13"
      ],
      "caps": [
       "CR-06",
       "CR-07",
       "CR-11"
      ],
      "refs": [
       "RB-SKOS",
       "RB-METASTD"
      ],
      "source": "IN-SSP"
     },
     {
      "id": "META-2",
      "stage": "embed",
      "title": "Climb from glossary to knowledge graph",
      "goal": "Your terms, standards, assets and owners become linked data that people, catalogues and AI tools can query.",
      "steps": [
       "Level 1, glossary: agreed terms with owners (META-1).",
       "Level 2, thesaurus: relate terms as broader, narrower, related, and \"use instead\", so search finds the preferred term.",
       "Level 3, vocabularies and taxonomies: closed code lists and a classification tree (category, topic, subject) applied the same way everywhere.",
       "Level 4, ontologies: describe concepts with SKOS, data sets with DCAT, lineage with PROV-O and quality with DQV, and validate them with SHACL shapes before publishing.",
       "Level 5, knowledge graph: give each term, standard, asset and owner a persistent, resolvable identifier and publish the links, so questions such as \"who owns this term?\" and \"what breaks if it changes?\" can be answered by query."
      ],
      "outputs": [
       "Machine-readable vocabularies with persistent identifiers",
       "Validation in your publishing pipeline"
      ],
      "evidence": "Published vocabularies resolve and pass validation.",
      "measure": "Share of governed terms with a resolvable identifier.",
      "raci": {
       "CAT": "A",
       "ARC": "R",
       "STW": "C"
      },
      "reqs": [
       "DAM-R02"
      ],
      "caps": [
       "CR-06",
       "CR-11",
       "CR-18"
      ],
      "refs": [
       "RB-SKOS",
       "RB-DCAT",
       "RB-PROVO",
       "RB-DQV",
       "RB-SHACL"
      ],
      "source": "IN-SSP"
     }
    ]
   },
   {
    "id": "DM-DQ",
    "lead": "DQL",
    "owner": "Your data quality lead",
    "why": "The quality playbook covers what the policy asks for. This activity prepares critical assets for use with AI, which the capability model treats as an inferred need.",
    "playbook": "dq",
    "activities": [
     {
      "id": "DQ-AI",
      "stage": "embed",
      "title": "Make critical assets ready for AI",
      "goal": "Critical assets can be used by AI tools safely, with known quality, meaning and limits.",
      "steps": [
       "Check the asset has a current catalogue record, glossary-linked definitions and a quality statement.",
       "Record known biases, gaps in coverage and groups under-represented in the data.",
       "Publish machine-readable metadata with persistent identifiers so retrieval tools cite the right source.",
       "Assess any AI use against the data ethics framework and record algorithmic tools where required."
      ],
      "outputs": [
       "AI readiness check per asset"
      ],
      "evidence": "Assets used by AI have a readiness check.",
      "measure": "Critical assets used by AI with a readiness check.",
      "raci": {
       "DQL": "R",
       "OWN": "A",
       "DPO": "C",
       "STW": "R"
      },
      "reqs": [
       "DAM-R06",
       "DAM-R13"
      ],
      "caps": [
       "CR-18",
       "CR-30"
      ],
      "refs": [
       "RB-AIREADY",
       "RB-ETH",
       "RB-ATRS"
      ]
     }
    ]
   }
  ]
 },
 "cap_guide": {
  "meta": {
   "as_of": "2026-11-17",
   "status": "Draft by this portal for review by the professions that own each capability. Not government guidance.",
   "intro": "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."
  },
  "playbooks": [
   {
    "id": "CR-02",
    "mode": "Both",
    "short": "Strategy",
    "lead": "CDO",
    "owner": "The chief data officer, with strategy and portfolio teams",
    "why": "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.",
    "see": [
     "BI-1"
    ],
    "change": [
     "CH-05"
    ],
    "activities": [
     {
      "id": "STR-1",
      "stage": "start",
      "title": "Rank critical assets by what they make possible",
      "goal": "You can say which critical assets matter most and why, in one page.",
      "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."
      ],
      "outputs": [
       "Prioritisation scorecard",
       "Board decision on the top ten"
      ],
      "evidence": "The board's decision log records the ranking and the reasons.",
      "measure": "Share of critical assets scored.",
      "raci": {
       "CDO": "A",
       "COO": "R",
       "OWN": "C",
       "BRD": "C"
      },
      "reqs": [
       "DAM-R14",
       "DAM-R11"
      ],
      "caps": [
       "CR-02",
       "CR-05"
      ],
      "refs": [
       "RB-BLUEPRINT",
       "RB-NDLPUB"
      ],
      "templates": [
       "T-STR-1"
      ]
     },
     {
      "id": "STR-2",
      "stage": "build",
      "title": "Put the ranking into the data strategy",
      "goal": "The data strategy names the assets it depends on and the outcomes they serve.",
      "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."
      ],
      "outputs": [
       "Data strategy with named assets and targets"
      ],
      "evidence": "The strategy names critical assets and targets for them.",
      "measure": "Strategic objectives that name the assets they depend on.",
      "raci": {
       "CDO": "A",
       "COO": "R",
       "BRD": "C",
       "OWN": "I"
      },
      "reqs": [
       "DAM-R08"
      ],
      "caps": [
       "CR-02",
       "CR-24"
      ],
      "refs": [
       "RB-BLUEPRINT",
       "RB-RMDG"
      ]
     },
     {
      "id": "STR-3",
      "stage": "embed",
      "title": "Re-rank every year with the return",
      "goal": "Priorities follow what changed, not what was decided once.",
      "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."
      ],
      "outputs": [
       "Updated ranking"
      ],
      "evidence": "Each year's ranking is kept with the reasons for changes.",
      "measure": "Years with a re-ranking on record.",
      "raci": {
       "CDO": "A",
       "COO": "R",
       "OWN": "C",
       "BRD": "C"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-02",
       "CR-04"
      ],
      "refs": [
       "RB-DMAF"
      ]
     }
    ],
    "templates": [
     {
      "id": "T-STR-1",
      "mode": "Both",
      "name": "Critical data asset prioritisation scorecard",
      "fields": [
       "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"
      ]
     }
    ]
   },
   {
    "id": "CR-13",
    "mode": "Both",
    "short": "Tools",
    "lead": "CML",
    "owner": "Commercial, digital and data teams together",
    "why": "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.",
    "change": [
     "CH-16",
     "CH-14"
    ],
    "activities": [
     {
      "id": "TOOL-1",
      "stage": "start",
      "title": "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.",
      "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."
      ],
      "outputs": [
       "Tool inventory and gap list"
      ],
      "evidence": "Each tool has an owner, a contract end date and a gap assessment.",
      "measure": "Tools assessed against the Must requirements.",
      "raci": {
       "ARC": "R",
       "CML": "R",
       "CDO": "A",
       "CAT": "C",
       "DQL": "C"
      },
      "reqs": [
       "DAM-R02",
       "DAM-R16"
      ],
      "caps": [
       "CR-13",
       "CR-12"
      ],
      "refs": [
       "RB-TCOP",
       "RB-CHOOSE"
      ],
      "templates": [
       "T-PRC-1"
      ]
     },
     {
      "id": "TOOL-2",
      "stage": "build",
      "title": "Run a request for information with ready-made requirements",
      "goal": "Suppliers answer the same questions, so answers can be compared.",
      "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."
      ],
      "outputs": [
       "RFI pack",
       "Scored responses",
       "Shortlist"
      ],
      "evidence": "Every response is scored against the same requirements.",
      "measure": "Requirements answered with evidence.",
      "raci": {
       "CML": "A",
       "ARC": "R",
       "CAT": "C",
       "DQL": "C",
       "STW": "C"
      },
      "reqs": [
       "DAM-R16"
      ],
      "caps": [
       "CR-13",
       "CR-32"
      ],
      "refs": [
       "RB-PA23G",
       "RB-GCLOUD",
       "RB-FTS",
       "RB-SOURCING"
      ],
      "templates": [
       "T-PRC-2"
      ]
     },
     {
      "id": "TOOL-3",
      "stage": "build",
      "title": "Prove it with your own data before you sign",
      "goal": "The tool does what the supplier says, with your data and your other tools.",
      "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."
      ],
      "outputs": [
       "Proof of concept test log",
       "Evaluation scores"
      ],
      "evidence": "A test log with a result for every Must.",
      "measure": "Must requirements proved, not only claimed.",
      "raci": {
       "ARC": "A",
       "CAT": "R",
       "DQL": "R",
       "CML": "C"
      },
      "reqs": [
       "DAM-R16"
      ],
      "caps": [
       "CR-13",
       "CR-32"
      ],
      "refs": [
       "RB-LOCKIN",
       "RB-CHOOSE"
      ],
      "templates": [
       "T-PRC-3",
       "T-PRC-4"
      ]
     },
     {
      "id": "TOOL-4",
      "stage": "embed",
      "title": "Check before every renewal",
      "goal": "You can still leave, and the tool still meets the policy.",
      "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."
      ],
      "outputs": [
       "Renewal check"
      ],
      "evidence": "An export test and a decision before each renewal.",
      "measure": "Renewals with an export test on record.",
      "raci": {
       "CML": "A",
       "ARC": "R",
       "CAT": "C"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-13",
       "CR-32"
      ],
      "refs": [
       "RB-LOCKIN",
       "RB-TCOP11"
      ]
     }
    ],
    "templates": [
     {
      "id": "T-PRC-1",
      "mode": "Both",
      "name": "Tool requirements schedule",
      "sheets": [
       {
        "name": "Functional requirements",
        "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"
        ]
       },
       {
        "name": "Non-functional requirements",
        "fields": [
         "Requirement ID",
         "Theme",
         "Requirement",
         "Priority (MoSCoW)",
         "Weight",
         "How to prove it",
         "Supplier response",
         "Supplier evidence",
         "Score (0 to 4)",
         "Evaluator notes"
        ]
       },
       {
        "name": "Contract clauses",
        "fields": [
         "Clause ID",
         "Clause",
         "What to include",
         "Why it matters",
         "Agreed by commercial (yes or no)",
         "Notes"
        ]
       }
      ],
      "fields": [
       "Functional requirements: Requirement ID",
       "Functional requirements: Kind of tool",
       "Functional requirements: Requirement",
       "Functional requirements: Priority (MoSCoW)",
       "Functional requirements: Weight",
       "Functional requirements: How to prove it",
       "Functional requirements: Capability",
       "Functional requirements: DAM Policy requirement",
       "Functional requirements: Supplier response",
       "Functional requirements: Supplier evidence",
       "Functional requirements: Score (0 to 4)",
       "Functional requirements: Evaluator notes",
       "Non-functional requirements: Requirement ID",
       "Non-functional requirements: Theme",
       "Non-functional requirements: Requirement",
       "Non-functional requirements: Priority (MoSCoW)",
       "Non-functional requirements: Weight",
       "Non-functional requirements: How to prove it",
       "Non-functional requirements: Supplier response",
       "Non-functional requirements: Supplier evidence",
       "Non-functional requirements: Score (0 to 4)",
       "Non-functional requirements: Evaluator notes",
       "Contract clauses: Clause ID",
       "Contract clauses: Clause",
       "Contract clauses: What to include",
       "Contract clauses: Why it matters",
       "Contract clauses: Agreed by commercial (yes or no)",
       "Contract clauses: Notes"
      ]
     },
     {
      "id": "T-PRC-2",
      "mode": "Change",
      "name": "Request for information response form",
      "fields": [
       "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"
      ]
     },
     {
      "id": "T-PRC-3",
      "mode": "Change",
      "name": "Evaluation and moderation sheet",
      "fields": [
       "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"
      ]
     },
     {
      "id": "T-PRC-4",
      "mode": "Change",
      "name": "Proof of concept test log",
      "fields": [
       "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"
      ]
     }
    ]
   },
   {
    "id": "CR-19",
    "mode": "Both",
    "short": "Risk",
    "lead": "OWN",
    "owner": "Data owners, with the risk and assurance teams",
    "why": "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.",
    "see": [
     "MOD-4",
     "SEC-3",
     "BI-3"
    ],
    "change": [
     "CH-07"
    ],
    "activities": [
     {
      "id": "RISK-1",
      "stage": "start",
      "title": "Record the main risk to each critical asset",
      "goal": "Every critical asset has at least one risk on a register someone reviews.",
      "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."
      ],
      "outputs": [
       "Data risks on the register"
      ],
      "evidence": "Each critical asset has a linked risk with an owner.",
      "measure": "Critical assets with a recorded risk.",
      "raci": {
       "OWN": "A",
       "STW": "R",
       "COO": "C",
       "BRD": "I"
      },
      "reqs": [
       "DAM-R05"
      ],
      "caps": [
       "CR-19"
      ],
      "refs": [
       "RB-ORANGE"
      ],
      "templates": [
       "T-RSK-1"
      ]
     },
     {
      "id": "RISK-2",
      "stage": "build",
      "title": "Set risk appetite for data",
      "goal": "Owners know how much risk they can accept and when to escalate.",
      "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."
      ],
      "outputs": [
       "Data risk appetite statement"
      ],
      "evidence": "The board has approved a data risk appetite.",
      "measure": "Risks outside appetite with an action or a dated exception.",
      "raci": {
       "BRD": "A",
       "CDO": "R",
       "OWN": "C",
       "DPO": "C"
      },
      "reqs": [
       "DAM-R08"
      ],
      "caps": [
       "CR-19",
       "CR-01"
      ],
      "refs": [
       "RB-ORANGE"
      ]
     },
     {
      "id": "RISK-3",
      "stage": "embed",
      "title": "Review data risks with the asset review",
      "goal": "Risks stay current as assets and systems change.",
      "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."
      ],
      "outputs": [
       "Reviewed risks",
       "Quarterly board report"
      ],
      "evidence": "Each risk shows a review date in the last year.",
      "measure": "Data risks reviewed in the last 12 months.",
      "raci": {
       "OWN": "A",
       "STW": "R",
       "BRD": "I"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-19",
       "CR-04"
      ],
      "refs": [
       "RB-ORANGE"
      ]
     }
    ],
    "templates": [
     {
      "id": "T-RSK-1",
      "mode": "Both",
      "name": "Data risk register entry",
      "fields": [
       "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"
      ]
     }
    ]
   },
   {
    "id": "CR-20",
    "mode": "Both",
    "short": "Suppliers",
    "lead": "CML",
    "owner": "Commercial teams with data owners",
    "why": "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.",
    "see": [
     "INT-4"
    ],
    "change": [
     "CH-06",
     "CH-16"
    ],
    "activities": [
     {
      "id": "SUPP-1",
      "stage": "start",
      "title": "Find the critical assets held or supplied by third parties",
      "goal": "You know which critical assets depend on a supplier, and on which contract.",
      "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."
      ],
      "outputs": [
       "Third-party data register"
      ],
      "evidence": "Every critical asset held by a supplier names the contract.",
      "measure": "Supplier-held critical assets with ownership and return covered in the contract.",
      "raci": {
       "CML": "R",
       "OWN": "A",
       "DPO": "C",
       "CAT": "C"
      },
      "reqs": [
       "DAM-R01",
       "DAM-R02"
      ],
      "caps": [
       "CR-20",
       "CR-17"
      ],
      "refs": [
       "RB-MTC20",
       "RB-MSC"
      ],
      "templates": [
       "T-SUP-1"
      ]
     },
     {
      "id": "SUPP-2",
      "stage": "build",
      "title": "Put data terms in every new contract",
      "goal": "New contracts protect critical data from the start.",
      "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."
      ],
      "outputs": [
       "Contract clause checklist completed"
      ],
      "evidence": "New contracts that touch critical assets include the clauses.",
      "measure": "New contracts with the data clauses.",
      "raci": {
       "CML": "A",
       "OWN": "C",
       "DPO": "C",
       "ARC": "C"
      },
      "reqs": [
       "DAM-R16"
      ],
      "caps": [
       "CR-20",
       "CR-32"
      ],
      "refs": [
       "RB-MSC",
       "RB-MTC20",
       "RB-PPN020"
      ]
     },
     {
      "id": "SUPP-3",
      "stage": "embed",
      "title": "Test the return of data before contracts end",
      "goal": "Data comes back complete when a contract ends.",
      "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."
      ],
      "outputs": [
       "Return test result"
      ],
      "evidence": "A test return before each relevant contract ends.",
      "measure": "Contracts ending with a successful test return.",
      "raci": {
       "OWN": "A",
       "CML": "R",
       "CUS": "R",
       "DQL": "C"
      },
      "reqs": [
       "DAM-R10"
      ],
      "caps": [
       "CR-20",
       "CR-26"
      ],
      "refs": [
       "RB-LOCKIN"
      ]
     }
    ],
    "templates": [
     {
      "id": "T-SUP-1",
      "mode": "Both",
      "name": "Third-party data register entry",
      "fields": [
       "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"
      ]
     }
    ]
   },
   {
    "id": "CR-21",
    "mode": "BAU",
    "short": "Skills",
    "lead": "CDO",
    "owner": "The chief data officer with learning and development teams",
    "why": "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.",
    "change": [
     "CH-09"
    ],
    "activities": [
     {
      "id": "SKILL-1",
      "stage": "start",
      "title": "Check what each data role needs to know",
      "goal": "Everyone named in a data role knows what is expected of them.",
      "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."
      ],
      "outputs": [
       "Skills assessment",
       "Learning plan per person"
      ],
      "evidence": "Every named role holder has a learning plan.",
      "measure": "Named role holders who have completed their core modules.",
      "raci": {
       "CDO": "A",
       "COO": "R",
       "OWN": "I",
       "STW": "I"
      },
      "reqs": [
       "DAM-R05",
       "DAM-R14"
      ],
      "caps": [
       "CR-21",
       "CR-07"
      ],
      "refs": [
       "RB-DSFA",
       "RB-DDAT"
      ],
      "templates": [
       "T-SKL-1"
      ]
     },
     {
      "id": "SKILL-2",
      "stage": "build",
      "title": "Build data roles into jobs and objectives",
      "goal": "Data roles are part of the job, not extra to it.",
      "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."
      ],
      "outputs": [
       "Updated objectives and job descriptions"
      ],
      "evidence": "Named role holders have the role in their objectives.",
      "measure": "Role holders with the role in their objectives.",
      "raci": {
       "CDO": "A",
       "COO": "R",
       "OWN": "C"
      },
      "reqs": [
       "DAM-R05"
      ],
      "caps": [
       "CR-21",
       "CR-22"
      ],
      "refs": [
       "RB-DDAT",
       "RB-SUCCESS"
      ]
     },
     {
      "id": "SKILL-3",
      "stage": "embed",
      "title": "Keep a community of practice going",
      "goal": "People in data roles learn from each other, inside and across organisations.",
      "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."
      ],
      "outputs": [
       "Community sessions",
       "Induction for new role holders"
      ],
      "evidence": "New role holders are inducted within a month.",
      "measure": "Days from appointment to induction.",
      "raci": {
       "COO": "A",
       "STW": "R",
       "OWN": "I"
      },
      "reqs": [
       "DAM-R10"
      ],
      "caps": [
       "CR-21",
       "CR-28"
      ],
      "refs": [
       "RB-DSFA",
       "RB-KIM"
      ]
     }
    ],
    "templates": [
     {
      "id": "T-SKL-1",
      "mode": "BAU",
      "name": "Data role skills assessment and learning plan",
      "fields": [
       "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)"
      ]
     }
    ]
   },
   {
    "id": "CR-22",
    "mode": "BAU",
    "short": "Culture",
    "lead": "CDO",
    "owner": "The chief data officer with communications and user research",
    "why": "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.",
    "activities": [
     {
      "id": "CULT-1",
      "stage": "start",
      "title": "Find out who uses each critical asset and what gets in their way",
      "goal": "Owners know their users and their main problems.",
      "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."
      ],
      "outputs": [
       "User list and problems per asset"
      ],
      "evidence": "Top critical assets have a list of users and their problems.",
      "measure": "Top assets with user feedback in the last year.",
      "raci": {
       "OWN": "A",
       "STW": "R",
       "USR": "C"
      },
      "reqs": [
       "DAM-R04",
       "DAM-R06"
      ],
      "caps": [
       "CR-22",
       "CR-08"
      ],
      "refs": [
       "RB-SVC",
       "RB-SMUR"
      ],
      "templates": [
       "T-ENG-1"
      ]
     },
     {
      "id": "CULT-2",
      "stage": "build",
      "title": "Tell people what changed because of their feedback",
      "goal": "Users see that raising a problem leads to a fix.",
      "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."
      ],
      "outputs": [
       "Quarterly note"
      ],
      "evidence": "A note published each quarter.",
      "measure": "Problems raised that have a response.",
      "raci": {
       "COO": "A",
       "OWN": "R",
       "STW": "R",
       "PUB": "I"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-22",
       "CR-30"
      ],
      "refs": [
       "RB-STYLE",
       "RB-ETH"
      ]
     },
     {
      "id": "CULT-3",
      "stage": "embed",
      "title": "Make data work visible to leaders",
      "goal": "Leaders ask about data assets as they ask about money and people.",
      "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."
      ],
      "outputs": [
       "Board report",
       "Stories of use"
      ],
      "evidence": "Critical assets appear in executive reporting.",
      "measure": "Executive board meetings that discuss data assets.",
      "raci": {
       "CDO": "A",
       "COO": "R",
       "BRD": "I"
      },
      "reqs": [
       "DAM-R08"
      ],
      "caps": [
       "CR-22",
       "CR-01"
      ],
      "refs": [
       "RB-DMAF"
      ]
     }
    ],
    "templates": [
     {
      "id": "T-ENG-1",
      "mode": "BAU",
      "name": "Data user feedback log",
      "fields": [
       "Date",
       "Asset identifier",
       "User group",
       "Problem or request",
       "Effect on their work",
       "Owner (role)",
       "Action",
       "Status",
       "Response sent (date)"
      ]
     }
    ]
   },
   {
    "id": "CR-23",
    "mode": "BAU",
    "short": "Maturity",
    "lead": "CDO",
    "owner": "The chief data officer and the lead policy coordinator",
    "why": "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.",
    "change": [
     "CH-12"
    ],
    "activities": [
     {
      "id": "MAT-1",
      "stage": "start",
      "title": "Take a baseline",
      "goal": "You know your starting level for each strand of data asset management.",
      "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."
      ],
      "outputs": [
       "Baseline levels with evidence"
      ],
      "evidence": "A baseline with evidence for each level.",
      "measure": "Strands with an evidenced baseline.",
      "raci": {
       "CDO": "A",
       "COO": "R",
       "OWN": "C",
       "STW": "C"
      },
      "reqs": [
       "DAM-R14"
      ],
      "caps": [
       "CR-23"
      ],
      "refs": [
       "RB-DMAF",
       "RB-DMAHUB"
      ],
      "templates": [
       "T-MAT-1"
      ]
     },
     {
      "id": "MAT-2",
      "stage": "build",
      "title": "Set targets and an improvement plan",
      "goal": "Each strand has a target level, a date and the actions to reach it.",
      "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."
      ],
      "outputs": [
       "Improvement plan"
      ],
      "evidence": "The board has approved targets and a plan.",
      "measure": "Plan actions on track.",
      "raci": {
       "BRD": "A",
       "CDO": "R",
       "COO": "R"
      },
      "reqs": [
       "DAM-R08"
      ],
      "caps": [
       "CR-23",
       "CR-02"
      ],
      "refs": [
       "RB-DMAF"
      ]
     },
     {
      "id": "MAT-3",
      "stage": "embed",
      "title": "Reassess every year",
      "goal": "Progress is measured, not assumed.",
      "steps": [
       "Repeat the assessment each year, with the same method.",
       "Compare with the baseline and explain changes.",
       "Reset targets and actions."
      ],
      "outputs": [
       "Annual reassessment"
      ],
      "evidence": "An assessment each year with evidence.",
      "measure": "Strands that moved up a level.",
      "raci": {
       "CDO": "A",
       "COO": "R",
       "BRD": "I"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-23",
       "CR-04"
      ],
      "refs": [
       "RB-DMAF",
       "RB-CMMI"
      ]
     }
    ],
    "templates": [
     {
      "id": "T-MAT-1",
      "mode": "Both",
      "name": "Maturity baseline and improvement plan",
      "fields": [
       "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"
      ]
     }
    ]
   },
   {
    "id": "CR-24",
    "mode": "Change",
    "short": "Investment",
    "lead": "SRO",
    "owner": "Senior responsible owners and finance business partners",
    "why": "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.",
    "see": [
     "BI-4"
    ],
    "change": [
     "CH-01"
    ],
    "activities": [
     {
      "id": "INV-1",
      "stage": "start",
      "title": "Name the critical assets in every business case",
      "goal": "Business cases say which critical assets they create, change or depend on.",
      "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."
      ],
      "outputs": [
       "Data assets section in business cases"
      ],
      "evidence": "Business cases list the critical assets they affect.",
      "measure": "Business cases approved with the section completed.",
      "raci": {
       "SRO": "A",
       "PDM": "R",
       "OWN": "C",
       "CDO": "C"
      },
      "reqs": [
       "DAM-R01",
       "DAM-R05"
      ],
      "caps": [
       "CR-24",
       "CR-25"
      ],
      "refs": [
       "RB-GREEN"
      ],
      "templates": [
       "T-INV-1"
      ]
     },
     {
      "id": "INV-2",
      "stage": "build",
      "title": "Make the case for investing in data assets",
      "goal": "Investment in data assets is argued with costs, benefits and the cost of doing nothing.",
      "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."
      ],
      "outputs": [
       "Business case for data investment"
      ],
      "evidence": "A business case with measurable benefits and owners.",
      "measure": "Benefits with an owner and a baseline.",
      "raci": {
       "SRO": "A",
       "PDM": "R",
       "CDO": "C"
      },
      "reqs": [
       "DAM-R08"
      ],
      "caps": [
       "CR-24",
       "CR-29"
      ],
      "refs": [
       "RB-GREEN",
       "RB-MAGENTA"
      ]
     },
     {
      "id": "INV-3",
      "stage": "embed",
      "title": "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.",
      "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."
      ],
      "outputs": [
       "Business-as-usual budget line"
      ],
      "evidence": "A budget line for the yearly cycle.",
      "measure": "Owning teams with a budget for the cycle.",
      "raci": {
       "CDO": "A",
       "OWN": "R",
       "SRO": "C"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-24",
       "CR-27"
      ],
      "refs": [
       "RB-GREEN"
      ]
     }
    ],
    "templates": [
     {
      "id": "T-INV-1",
      "mode": "Change",
      "name": "Data assets section for a business case",
      "fields": [
       "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"
      ]
     }
    ]
   },
   {
    "id": "CR-25",
    "mode": "Change",
    "short": "Assurance",
    "lead": "PMO",
    "owner": "Programme offices, spend control and assurance teams",
    "why": "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.",
    "see": [
     "ARC-5"
    ],
    "change": [
     "CH-02",
     "CH-03"
    ],
    "activities": [
     {
      "id": "ASSR-1",
      "stage": "start",
      "title": "Add data asset questions to existing checkpoints",
      "goal": "Spend control, gate reviews and service assessments ask about critical data.",
      "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."
      ],
      "outputs": [
       "Updated checkpoint templates"
      ],
      "evidence": "Checkpoint templates include the questions.",
      "measure": "Checkpoints that asked the questions this year.",
      "raci": {
       "PMO": "A",
       "COO": "R",
       "ARC": "C",
       "SRO": "I"
      },
      "reqs": [
       "DAM-R05",
       "DAM-R02"
      ],
      "caps": [
       "CR-25"
      ],
      "refs": [
       "RB-SPEND",
       "RB-SVCASSESS",
       "RB-IAAP"
      ],
      "templates": [
       "T-ASR-1"
      ]
     },
     {
      "id": "ASSR-2",
      "stage": "build",
      "title": "Put data checkpoints into the assurance plan",
      "goal": "Large programmes plan their data assurance from the start.",
      "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."
      ],
      "outputs": [
       "Assurance plan with data checkpoints"
      ],
      "evidence": "Major programmes have data checkpoints in their assurance plans.",
      "measure": "Programmes with data checkpoints planned.",
      "raci": {
       "SRO": "A",
       "PMO": "R",
       "CDO": "C"
      },
      "reqs": [
       "DAM-R08"
      ],
      "caps": [
       "CR-25",
       "CR-19"
      ],
      "refs": [
       "RB-IAAP",
       "RB-GOVS002"
      ]
     },
     {
      "id": "ASSR-3",
      "stage": "embed",
      "title": "Learn from checkpoint findings",
      "goal": "Common problems are fixed in guidance, not found again and again.",
      "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."
      ],
      "outputs": [
       "Quarterly lessons"
      ],
      "evidence": "A quarterly summary of findings and fixes.",
      "measure": "Repeated findings falling over time.",
      "raci": {
       "PMO": "A",
       "COO": "R",
       "ARC": "C"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-25",
       "CR-23"
      ],
      "refs": [
       "RB-GOVS002"
      ]
     }
    ],
    "templates": [
     {
      "id": "T-ASR-1",
      "mode": "Change",
      "name": "Data asset checkpoint questions",
      "fields": [
       "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"
      ]
     }
    ]
   },
   {
    "id": "CR-26",
    "mode": "Change",
    "short": "Legacy",
    "lead": "MIG",
    "owner": "Data migration leads with data owners",
    "why": "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.",
    "see": [
     "OPS-4",
     "DOC-3"
    ],
    "change": [
     "CH-04",
     "CH-05"
    ],
    "activities": [
     {
      "id": "LEG-1",
      "stage": "start",
      "title": "List the critical assets in each legacy system",
      "goal": "You know what data each legacy system holds before anyone plans to replace it.",
      "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."
      ],
      "outputs": [
       "Legacy data asset register"
      ],
      "evidence": "Each system with a planned end has its assets listed.",
      "measure": "Legacy systems with an asset register.",
      "raci": {
       "MIG": "R",
       "OWN": "A",
       "CUS": "R",
       "CAT": "C"
      },
      "reqs": [
       "DAM-R01",
       "DAM-R12"
      ],
      "caps": [
       "CR-26",
       "CR-05"
      ],
      "refs": [
       "RB-LEGACY",
       "RB-TECHDEBT"
      ],
      "templates": [
       "T-LEG-1"
      ]
     },
     {
      "id": "LEG-2",
      "stage": "build",
      "title": "Migrate with reconciliation",
      "goal": "Data arrives complete and correct, and you can prove it.",
      "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."
      ],
      "outputs": [
       "Migration plan",
       "Reconciliation report"
      ],
      "evidence": "A signed-off reconciliation for each migrated asset.",
      "measure": "Migrated assets with a signed-off reconciliation.",
      "raci": {
       "OWN": "A",
       "MIG": "R",
       "DQL": "R",
       "CUS": "C"
      },
      "reqs": [
       "DAM-R06"
      ],
      "caps": [
       "CR-26",
       "CR-08"
      ],
      "refs": [
       "RB-LEGACY"
      ]
     },
     {
      "id": "LEG-3",
      "stage": "embed",
      "title": "Switch off safely",
      "goal": "Nothing needed is lost when a system is turned off.",
      "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."
      ],
      "outputs": [
       "Decommissioning sign-off"
      ],
      "evidence": "The owner signs off before switch-off.",
      "measure": "Switch-offs with owner sign-off.",
      "raci": {
       "OWN": "A",
       "MIG": "R",
       "CAT": "R",
       "CUS": "R"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-26",
       "CR-15"
      ],
      "refs": [
       "RB-RETIRE",
       "RB-TNAIM"
      ]
     }
    ],
    "templates": [
     {
      "id": "T-LEG-1",
      "mode": "Change",
      "name": "Legacy exit and migration plan",
      "sheets": [
       {
        "name": "Assets in the system",
        "fields": [
         "Asset identifier",
         "Asset title",
         "Owner (role)",
         "Downstream dependants",
         "Must be kept (records or legal)",
         "Disposition (migrate, archive, dispose)",
         "Target system"
        ]
       },
       {
        "name": "Reconciliation",
        "fields": [
         "Asset identifier",
         "Check",
         "Old value",
         "New value",
         "Difference",
         "Decision",
         "Decided by (role)",
         "Date"
        ]
       },
       {
        "name": "Switch-off checklist",
        "fields": [
         "Item",
         "Done (yes or no)",
         "Evidence",
         "Signed off by (role)",
         "Date"
        ]
       }
      ],
      "fields": [
       "Assets in the system: Asset identifier",
       "Assets in the system: Asset title",
       "Assets in the system: Owner (role)",
       "Assets in the system: Downstream dependants",
       "Assets in the system: Must be kept (records or legal)",
       "Assets in the system: Disposition (migrate, archive, dispose)",
       "Assets in the system: Target system",
       "Reconciliation: Asset identifier",
       "Reconciliation: Check",
       "Reconciliation: Old value",
       "Reconciliation: New value",
       "Reconciliation: Difference",
       "Reconciliation: Decision",
       "Reconciliation: Decided by (role)",
       "Reconciliation: Date",
       "Switch-off checklist: Item",
       "Switch-off checklist: Done (yes or no)",
       "Switch-off checklist: Evidence",
       "Switch-off checklist: Signed off by (role)",
       "Switch-off checklist: Date"
      ]
     }
    ]
   },
   {
    "id": "CR-27",
    "mode": "Change",
    "short": "Handover",
    "lead": "SRO",
    "owner": "Senior responsible owners and the receiving business owners",
    "why": "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.",
    "change": [
     "CH-08",
     "CH-11"
    ],
    "activities": [
     {
      "id": "HAND-1",
      "stage": "start",
      "title": "Name the business-as-usual owner early",
      "goal": "Every asset a project creates has an owner who will be there after the project.",
      "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."
      ],
      "outputs": [
       "Named owners for new assets"
      ],
      "evidence": "New assets have a business-as-usual owner in the catalogue.",
      "measure": "New assets with a named business-as-usual owner.",
      "raci": {
       "SRO": "A",
       "PDM": "R",
       "OWN": "R"
      },
      "reqs": [
       "DAM-R05"
      ],
      "caps": [
       "CR-27",
       "CR-07"
      ],
      "refs": [
       "RB-SRO",
       "RB-SMROLES"
      ],
      "templates": [
       "T-HND-1"
      ]
     },
     {
      "id": "HAND-2",
      "stage": "build",
      "title": "Hand over with a checklist",
      "goal": "Business as usual receives everything needed to run the asset.",
      "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."
      ],
      "outputs": [
       "Signed handover checklist"
      ],
      "evidence": "A signed checklist for each asset.",
      "measure": "Projects closed with signed handovers.",
      "raci": {
       "SRO": "A",
       "PDM": "R",
       "OWN": "R",
       "PMO": "C"
      },
      "reqs": [
       "DAM-R05",
       "DAM-R06"
      ],
      "caps": [
       "CR-27"
      ],
      "refs": [
       "RB-GOVS002"
      ]
     },
     {
      "id": "HAND-3",
      "stage": "embed",
      "title": "Check six months after handover",
      "goal": "The asset is still owned, catalogued and checked after the project team has gone.",
      "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."
      ],
      "outputs": [
       "Post-handover check"
      ],
      "evidence": "A check six months after each handover.",
      "measure": "Handovers still complete at six months.",
      "raci": {
       "COO": "A",
       "OWN": "R",
       "PMO": "I"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-27",
       "CR-23"
      ],
      "refs": [
       "RB-GOVS002"
      ]
     }
    ],
    "templates": [
     {
      "id": "T-HND-1",
      "mode": "Change",
      "name": "Handover to business as usual checklist",
      "fields": [
       "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"
      ]
     }
    ]
   },
   {
    "id": "CR-29",
    "mode": "Change",
    "short": "Benefits",
    "lead": "SRO",
    "owner": "Benefit owners, with analysts",
    "why": "Showing what better data asset management achieved keeps funding and support. Benefits that are named, measured and owned can be evaluated; general claims cannot.",
    "see": [
     "BI-4"
    ],
    "change": [
     "CH-10"
    ],
    "activities": [
     {
      "id": "BEN-1",
      "stage": "start",
      "title": "Pick a few measures and record the baseline",
      "goal": "You can show change, because you know where you started.",
      "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."
      ],
      "outputs": [
       "Benefits register with baselines"
      ],
      "evidence": "Each measure has a baseline and an owner.",
      "measure": "Benefits with a recorded baseline.",
      "raci": {
       "SRO": "A",
       "PDM": "R",
       "OWN": "C"
      },
      "reqs": [
       "DAM-R08"
      ],
      "caps": [
       "CR-29"
      ],
      "refs": [
       "RB-MAGENTA"
      ],
      "templates": [
       "T-BEN-1"
      ]
     },
     {
      "id": "BEN-2",
      "stage": "build",
      "title": "Track and report the benefits",
      "goal": "Leaders see progress against the baseline each quarter.",
      "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."
      ],
      "outputs": [
       "Quarterly benefits report"
      ],
      "evidence": "Benefits reported each quarter against the baseline.",
      "measure": "Benefits on track.",
      "raci": {
       "SRO": "A",
       "PDM": "R",
       "BRD": "I"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-29",
       "CR-04"
      ],
      "refs": [
       "RB-MAGENTA",
       "RB-AQUA"
      ]
     },
     {
      "id": "BEN-3",
      "stage": "embed",
      "title": "Evaluate after a year",
      "goal": "You know what worked, what did not and why.",
      "steps": [
       "Plan a proportionate evaluation using the Magenta Book.",
       "Compare results with the business case.",
       "Publish the lessons for other organisations."
      ],
      "outputs": [
       "Evaluation report"
      ],
      "evidence": "An evaluation within a year of the main change.",
      "measure": "Lessons published.",
      "raci": {
       "SRO": "A",
       "PDM": "R",
       "CDO": "C"
      },
      "reqs": [
       "DAM-R08"
      ],
      "caps": [
       "CR-29",
       "CR-23"
      ],
      "refs": [
       "RB-MAGENTA"
      ]
     }
    ],
    "templates": [
     {
      "id": "T-BEN-1",
      "mode": "Both",
      "name": "Benefits register",
      "fields": [
       "Benefit ID",
       "Benefit",
       "Measure",
       "How measured",
       "Baseline",
       "Baseline date",
       "Target",
       "Target date",
       "Measurement frequency",
       "Latest value",
       "Benefit owner (role)",
       "Assets involved",
       "Notes"
      ]
     }
    ]
   },
   {
    "id": "CR-32",
    "mode": "Both",
    "short": "Exit",
    "lead": "ARC",
    "owner": "Design authorities and commercial teams",
    "why": "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.",
    "see": [
     "ARC-4",
     "SEC-5"
    ],
    "change": [
     "CH-14"
    ],
    "activities": [
     {
      "id": "EXIT-1",
      "stage": "start",
      "title": "Ask three questions of every new system",
      "goal": "No new system holds critical data you cannot get out.",
      "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."
      ],
      "outputs": [
       "Answers recorded at design review"
      ],
      "evidence": "Design reviews record the three answers.",
      "measure": "New systems with recorded answers.",
      "raci": {
       "ARC": "A",
       "CML": "C",
       "OWN": "C"
      },
      "reqs": [
       "DAM-R16"
      ],
      "caps": [
       "CR-32",
       "CR-11"
      ],
      "refs": [
       "RB-TECHDEBT",
       "RB-OPEN"
      ],
      "templates": [
       "T-EXT-1"
      ]
     },
     {
      "id": "EXIT-2",
      "stage": "build",
      "title": "Write and cost the exit plan",
      "goal": "Leaving is planned and costed before you sign.",
      "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."
      ],
      "outputs": [
       "Exit plan"
      ],
      "evidence": "Systems holding critical data have a costed exit plan.",
      "measure": "Systems with a costed exit plan.",
      "raci": {
       "ARC": "A",
       "CML": "R",
       "OWN": "C"
      },
      "reqs": [
       "DAM-R16"
      ],
      "caps": [
       "CR-32",
       "CR-20"
      ],
      "refs": [
       "RB-LOCKIN",
       "RB-MSC"
      ]
     },
     {
      "id": "EXIT-3",
      "stage": "embed",
      "title": "Test the exit every year",
      "goal": "The exit plan still works.",
      "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."
      ],
      "outputs": [
       "Annual exit test"
      ],
      "evidence": "An exit test each year.",
      "measure": "Systems with an exit test in the last year.",
      "raci": {
       "ARC": "A",
       "CUS": "R",
       "CML": "C"
      },
      "reqs": [
       "DAM-R04"
      ],
      "caps": [
       "CR-32"
      ],
      "refs": [
       "RB-LOCKIN"
      ]
     }
    ],
    "templates": [
     {
      "id": "T-EXT-1",
      "mode": "Both",
      "name": "Exit and portability plan",
      "fields": [
       "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"
      ]
     }
    ]
   }
  ],
  "leader": {
   "intro": "New to data asset management, or asked to lead it? This route tells you what to aim for, how to know it is working, and what to do in your first 30, 60 and 90 days, with checkpoints at 6 and 12 months. Targets use the maturity levels on the Capability model page, which follow the Data Maturity Assessment for Government.",
   "who": [
    {
     "id": "new",
     "icon": "lightbulb",
     "name": "New to this",
     "text": "You have joined a data team, or been named as an owner or steward, and the terms are new."
    },
    {
     "id": "team",
     "icon": "users-round",
     "name": "Leading a team",
     "text": "You run a catalogue, quality or governance team and need a plan for it."
    },
    {
     "id": "capability",
     "icon": "compass",
     "name": "Leading the capability",
     "text": "You are defining, designing, deploying or enabling data asset management across an organisation."
    }
   ],
   "basics": [
    {
     "term": "Critical data asset",
     "text": "Data that matters most to services and decisions. The DAM Policy asks you to find these, describe them, name an owner and manage their quality.",
     "link": "dam.html"
    },
    {
     "term": "Data owner",
     "text": "The person accountable for decisions about a data asset. Every critical asset must have one.",
     "link": "governance.html"
    },
    {
     "term": "Catalogue record",
     "text": "The description of an asset: what it is, who owns it, where it is and how it can be used.",
     "link": "cataloguing.html"
    },
    {
     "term": "Data quality action plan",
     "text": "How you know, prove and improve the quality of an asset, in seven steps.",
     "link": "quality.html"
    },
    {
     "term": "The yearly cycle",
     "text": "Find, describe, own, check and report, every year, so the return stays true.",
     "link": "together.html"
    },
    {
     "term": "Maturity",
     "text": "How established the practice is, from Beginning to Mastering. You do not need Mastering everywhere.",
     "link": "capability-model.html"
    }
   ],
   "aims": [
    {
     "moscow": "Must",
     "aim": "Every critical asset is identified, has a named owner, a catalogue record and a quality plan, and is reported on time.",
     "outcome": "The organisation meets the DAM Policy.",
     "caps": [
      "CR-05",
      "CR-06",
      "CR-07",
      "CR-08",
      "CR-03"
     ]
    },
    {
     "moscow": "Must",
     "aim": "The chief data officer leads, a board meets, and decisions are recorded.",
     "outcome": "Someone is accountable and decisions stick.",
     "caps": [
      "CR-01"
     ]
    },
    {
     "moscow": "Should",
     "aim": "Critical assets are ranked by value and risk, with a plan for the top ten.",
     "outcome": "Effort goes where it matters most.",
     "caps": [
      "CR-02",
      "CR-19"
     ]
    },
    {
     "moscow": "Should",
     "aim": "Business cases, spend control and contracts ask about critical data.",
     "outcome": "New work does not create new legacy.",
     "caps": [
      "CR-24",
      "CR-25",
      "CR-20",
      "CR-32"
     ]
    },
    {
     "moscow": "Should",
     "aim": "Owners and stewards know their role and have it in their objectives.",
     "outcome": "The work continues when people move.",
     "caps": [
      "CR-21",
      "CR-27"
     ]
    },
    {
     "moscow": "Could",
     "aim": "Quality results show in the catalogue, and users can find and request data themselves.",
     "outcome": "Data is reused instead of collected again.",
     "caps": [
      "CR-13",
      "CR-22"
     ]
    },
    {
     "moscow": "Could",
     "aim": "Critical assets are prepared for AI use and wider sharing.",
     "outcome": "The organisation can use AI safely on its best data.",
     "caps": [
      "CR-18",
      "CR-28"
     ]
    },
    {
     "moscow": "Won't (this year)",
     "aim": "Every data asset in the organisation described and quality-managed.",
     "outcome": "Start with critical assets; extend once the cycle runs.",
     "caps": [
      "CR-10"
     ]
    }
   ],
   "outcomes": [
    {
     "id": "OUT-1",
     "outcome": "Critical assets are known and owned",
     "indicator": "Share of critical assets with a named owner and a catalogue record",
     "example": "100% of reported assets by the return date",
     "strand": "own"
    },
    {
     "id": "OUT-2",
     "outcome": "The return is complete and on time",
     "indicator": "Return submitted on time with core metadata complete",
     "example": "On time, with no core field blank",
     "strand": "cat"
    },
    {
     "id": "OUT-3",
     "outcome": "Quality is known and improving",
     "indicator": "Share of critical assets with a DQAP and quality in their target range",
     "example": "Every asset with a DQAP; half in range within a year",
     "strand": "dq"
    },
    {
     "id": "OUT-4",
     "outcome": "Change does not create legacy",
     "indicator": "Share of business cases and checkpoints that asked about critical data",
     "example": "All major programmes within a year",
     "strand": "chg"
    },
    {
     "id": "OUT-5",
     "outcome": "People know their role",
     "indicator": "Share of named role holders who completed core learning",
     "example": "80% within six months of appointment",
     "strand": "own"
    }
   ],
   "plan": [
    {
     "id": "d30",
     "name": "First 30 days",
     "icon": "flag",
     "focus": "Learn, listen and find out where you are.",
     "do": [
      "Read the DAM Policy page and the guide for your role.",
      "Meet the chief data officer, the board chair and a few owners and stewards.",
      "Find last year's return, the asset list and any catalogue.",
      "Take a first baseline with the self-assessment on the Capability model page."
     ],
     "have": [
      "A baseline",
      "A list of the people involved",
      "A first view of gaps"
     ],
     "ask": [
      "Do we know our critical assets?",
      "Does each have an owner who knows it?",
      "When is the next return due, and what will it show?"
     ],
     "activities": [
      "MAT-1",
      "SKILL-1"
     ],
     "targets": {
      "own": "Beginning",
      "cat": "Beginning",
      "dq": "Beginning",
      "chg": "Beginning"
     }
    },
    {
     "id": "d60",
     "name": "Days 31 to 60",
     "icon": "map",
     "focus": "Agree what to aim for and who does what.",
     "do": [
      "Rank critical assets with the prioritisation scorecard and agree the top ten with the board.",
      "Agree your Must, Should and Could aims, and the outcomes and indicators.",
      "Fill gaps in ownership for the top ten.",
      "Map your tools against the Must requirements."
     ],
     "have": [
      "Agreed aims and outcomes",
      "Ranked asset list",
      "Owners for the top ten",
      "Tool gap list"
     ],
     "ask": [
      "Has the board agreed the aims?",
      "Are the top ten owned?",
      "Which gaps would the next return expose?"
     ],
     "activities": [
      "STR-1",
      "TOOL-1",
      "RISK-1"
     ],
     "targets": {
      "own": "Emerging",
      "cat": "Beginning",
      "dq": "Beginning",
      "chg": "Beginning"
     }
    },
    {
     "id": "d90",
     "name": "Days 61 to 90",
     "icon": "trending-up",
     "focus": "Start the cycle on the assets that matter most.",
     "do": [
      "Complete catalogue records for the top ten.",
      "Start a data quality action plan for each of the top ten.",
      "Add the three data questions to spend control and gate reviews.",
      "Give every named role holder a learning plan."
     ],
     "have": [
      "Top ten catalogued",
      "DQAPs started",
      "Checkpoint questions in place",
      "Learning plans"
     ],
     "ask": [
      "Could we report the top ten today?",
      "Is each top asset's quality known?",
      "Are new programmes asked about critical data?"
     ],
     "activities": [
      "ASSR-1",
      "SKILL-1",
      "BEN-1"
     ],
     "targets": {
      "own": "Emerging",
      "cat": "Emerging",
      "dq": "Emerging",
      "chg": "Emerging"
     }
    },
    {
     "id": "m6",
     "name": "Six-month checkpoint",
     "icon": "gauge",
     "focus": "Check progress and fix what is stuck.",
     "do": [
      "Reassess against the baseline, strand by strand.",
      "Extend ownership and catalogue records to all critical assets.",
      "Report benefits against the baseline to the board.",
      "Run a request for information if a tool gap blocks you."
     ],
     "have": [
      "Six-month assessment",
      "All critical assets owned",
      "Benefits report"
     ],
     "ask": [
      "Which strands moved, and which did not? Why?",
      "Are we on track for the return?",
      "What would we stop, start or change?"
     ],
     "activities": [
      "MAT-2",
      "BEN-2",
      "TOOL-2",
      "RISK-2"
     ],
     "targets": {
      "own": "Learning",
      "cat": "Emerging",
      "dq": "Emerging",
      "chg": "Emerging"
     }
    },
    {
     "id": "m12",
     "name": "Twelve-month checkpoint",
     "icon": "calendar-check",
     "focus": "Meet the policy and make the cycle routine.",
     "do": [
      "Submit a complete, on-time return.",
      "Reassess maturity and reset targets for the next year.",
      "Re-rank critical assets and update the plan.",
      "Evaluate what worked, and share the lessons."
     ],
     "have": [
      "Return submitted",
      "Annual assessment",
      "Updated plan",
      "Evaluation"
     ],
     "ask": [
      "Do we meet the Must aims?",
      "Is the cycle owned in business as usual, with a budget?",
      "Which Should aims come next?"
     ],
     "activities": [
      "MAT-3",
      "STR-3",
      "BEN-3",
      "INV-3"
     ],
     "targets": {
      "own": "Learning",
      "cat": "Learning",
      "dq": "Learning",
      "chg": "Learning"
     }
    }
   ],
   "models": [
    {
     "need": "A view of the whole organisation's data maturity, comparable across government",
     "use": "Data Maturity Assessment for Government",
     "ref": "RB-DMAF",
     "link": "capability-model.html"
    },
    {
     "need": "Targets for data asset management specifically, by strand",
     "use": "The DAM strands on the Capability model page (same five levels)",
     "ref": "RB-DMAF",
     "link": "capability-model.html"
    },
    {
     "need": "Quality targets for one asset",
     "use": "The government data quality issues framework, through the DQAP",
     "ref": "RB-DQHUB",
     "link": "quality.html"
    },
    {
     "need": "Process discipline in a delivery or service team",
     "use": "A CMMI-style ladder, crosswalked to the same levels",
     "ref": "RB-CMMI",
     "link": "capability-model.html"
    },
    {
     "need": "Comparing with industry data management programmes",
     "use": "DCAM",
     "ref": "RB-DCAM",
     "link": "capability-model.html"
    }
   ],
   "evaluation": [
    "Measure the same way each time, so change is real.",
    "Report against the baseline, not against an ideal.",
    "Ask users and owners as well as counting.",
    "Plan a proportionate evaluation with the Magenta Book once the main change is in."
   ],
   "templates": [
    {
     "id": "T-LDR-1",
     "mode": "Both",
     "name": "Capability plan for the first year",
     "sheets": [
      {
       "name": "Aims",
       "fields": [
        "Priority (MoSCoW)",
        "Aim",
        "Outcome",
        "Capabilities",
        "Owner (role)"
       ]
      },
      {
       "name": "Outcomes and targets",
       "fields": [
        "Outcome ID",
        "Outcome",
        "Indicator",
        "Baseline",
        "Target",
        "Target date",
        "Maturity strand",
        "Owner (role)"
       ]
      },
      {
       "name": "Plan",
       "fields": [
        "Checkpoint (30, 60, 90 days, 6 or 12 months)",
        "Action",
        "Playbook activity ID",
        "Owner (role)",
        "Due date",
        "Status"
       ]
      },
      {
       "name": "Maturity",
       "fields": [
        "Strand",
        "Baseline level",
        "Target at 90 days",
        "Target at 6 months",
        "Target at 12 months",
        "Evidence"
       ]
      },
      {
       "name": "Risks",
       "fields": [
        "Risk",
        "Owner (role)",
        "Action",
        "Due date"
       ]
      }
     ],
     "fields": [
      "Aims: Priority (MoSCoW)",
      "Aims: Aim",
      "Aims: Outcome",
      "Aims: Capabilities",
      "Aims: Owner (role)",
      "Outcomes and targets: Outcome ID",
      "Outcomes and targets: Outcome",
      "Outcomes and targets: Indicator",
      "Outcomes and targets: Baseline",
      "Outcomes and targets: Target",
      "Outcomes and targets: Target date",
      "Outcomes and targets: Maturity strand",
      "Outcomes and targets: Owner (role)",
      "Plan: Checkpoint (30, 60, 90 days, 6 or 12 months)",
      "Plan: Action",
      "Plan: Playbook activity ID",
      "Plan: Owner (role)",
      "Plan: Due date",
      "Plan: Status",
      "Maturity: Strand",
      "Maturity: Baseline level",
      "Maturity: Target at 90 days",
      "Maturity: Target at 6 months",
      "Maturity: Target at 12 months",
      "Maturity: Evidence",
      "Risks: Risk",
      "Risks: Owner (role)",
      "Risks: Action",
      "Risks: Due date"
     ]
    },
    {
     "id": "T-LDR-2",
     "mode": "Both",
     "name": "Checkpoint review record",
     "fields": [
      "Checkpoint",
      "Date",
      "Strand",
      "Level at last checkpoint",
      "Level now",
      "Evidence",
      "What worked",
      "What did not",
      "Decision (continue or change or stop)",
      "Actions",
      "Owner (role)",
      "Reviewed by (role or forum)"
     ]
    }
   ]
  },
  "learning": {
   "intro": "Learning sticks when you use it, come back to it and explain it to someone else. These tips help you learn from the playbooks and the sources they cite, keep what you learn, share it, and count it towards your role, your career and continuing professional development (CPD).",
   "methods": [
    {
     "id": "acquire",
     "name": "Learn it",
     "icon": "book-open",
     "tips": [
      "Start from a real asset you look after. Read each module with that asset in mind, not in the abstract.",
      "Do the activities, not only the reading. Each one produces something you need for the return anyway.",
      "Read the source behind a point when it matters: every fact links to the GOV.UK page or standard it comes from.",
      "Use the glossary and tooltips the first time a term is new. Hover or focus on a dotted term to see what it means.",
      "Follow the journey for your role first, then pick other modules as your work needs them."
     ]
    },
    {
     "id": "retain",
     "name": "Keep it",
     "icon": "brain",
     "tips": [
      "Try the check of understanding before you reread the module. Recalling an answer helps you keep it more than reading again.",
      "Come back to a module a week later and a month later. The page reminds you when a module is due for a refresher.",
      "Write one sentence after each module: what you will do differently on Monday.",
      "Keep your filled templates. They are a record of what you did and a reminder next year.",
      "Use your progress record as a checklist before each annual return."
     ]
    },
    {
     "id": "share",
     "name": "Share it",
     "icon": "share-2",
     "tips": [
      "Explain one module to a colleague in ten minutes. Teaching it is the quickest way to find what you have not understood.",
      "Run a lunch-and-learn on a playbook with your owners and stewards, using the module activities as the agenda.",
      "Post a question or a lesson in the cross-government data management community, and in the playbooks' discussions.",
      "Suggest a fix when something here is unclear: every page has a link to report a problem or suggest a change.",
      "Share your filled templates inside your organisation so the next person starts from yours."
     ]
    }
   ],
   "role_tips": [
    {
     "role": "OWN",
     "tip": "Take M01 and M02 first. Your job is decisions, not data entry: know your assets, your steward and your review date."
    },
    {
     "role": "STW",
     "tip": "Take M04 to M08. Keep a short list of the questions users ask you; it tells you what to fix first."
    },
    {
     "role": "CAT",
     "tip": "Take M05 and M06 and keep the metadata guidance open while you work. Check one record a week against it."
    },
    {
     "role": "DQL",
     "tip": "Take M07 and M08. Score one real issue with the issues framework before reading further."
    },
    {
     "role": "CDO",
     "tip": "Take M01, M09 and M11, then the leader route. Ask for the maturity baseline in your first month."
    },
    {
     "role": "COO",
     "tip": "Take M01 to M03 and M09. Put the yearly cycle in the calendar before anything else."
    }
   ],
   "career": {
    "intro": "What you learn here counts towards your role, your profession and your next job. The modules map to roles in the Digital and Data Capability Framework and to government professions, so you can use them as evidence in a development conversation, a job application or a promotion.",
    "steps": [
     "Find your role, or the one you want, on the Professions and skills page, and note its skills.",
     "Pick the modules that build those skills, and add them to your development plan.",
     "Record each module you finish, what you did with it and the evidence, in your CPD log.",
     "Use the record in your performance review and in Success Profiles applications.",
     "When you are ready, choose a certification that fits your role and aim for it."
    ],
    "refs": [
     "RB-DDAT",
     "RB-PROFS",
     "RB-SUCCESS",
     "RB-DSFA",
     "RB-PROSPECTUS",
     "RB-KIM",
     "RB-AFCAREER",
     "RB-SFIA"
    ]
   },
   "certifications": [
    {
     "id": "CERT-CDMP",
     "name": "Certified Data Management Professional (CDMP)",
     "body": "DAMA International",
     "ref": "RB-CDMP",
     "fit": "Data management professionals across all knowledge areas, including governance, metadata and quality.",
     "cpd": "Holders recertify every three years; schemes commonly cite 120 hours of continuing education per three-year cycle. Check the current rules on the scheme's own pages.",
     "prov": "S"
    },
    {
     "id": "CERT-BCSDME",
     "name": "BCS Practitioner Certificate in Data Management Essentials",
     "body": "BCS",
     "ref": "RB-BCSDME",
     "fit": "Business analysts, managers and project managers who need a grounding in data management in an organisation.",
     "cpd": "A certificate gained by exam. Log the study hours as CPD.",
     "prov": "S"
    },
    {
     "id": "CERT-CILIP",
     "name": "CILIP professional registration (certification, chartership and knowledge management chartership)",
     "body": "CILIP",
     "ref": "RB-CILIPREG",
     "fit": "Knowledge and information management professionals, including records and catalogue roles.",
     "cpd": "Revalidation asks for at least 20 hours of CPD a year and a short statement. Check the current rules on CILIP's pages.",
     "prov": "S"
    },
    {
     "id": "CERT-RSS",
     "name": "Royal Statistical Society professional development",
     "body": "Royal Statistical Society",
     "ref": "RB-RSS",
     "fit": "Statisticians and analysts working on data quality and official statistics.",
     "cpd": "Professional status includes keeping a CPD record. Check the society's pages.",
     "prov": "S"
    }
   ],
   "cpd": [
    "Each module gives its time in minutes. Count the time you actually spent, including activities and reading the sources.",
    "Most schemes count reflection and applying learning at work, not only courses. Record what you did with each module.",
    "Download your learning record from this page as a start for your CPD log, then add your own notes and evidence.",
    "This portal does not award credits or certificates. Your professional body decides what counts."
   ],
   "templates": [
    {
     "id": "T-LRN-1",
     "mode": "BAU",
     "name": "CPD and learning log",
     "fields": [
      "Date",
      "Activity (module or source)",
      "Kind (course or reading or practice or teaching)",
      "Hours",
      "What I learned",
      "How I applied it at work",
      "Evidence (location)",
      "Skill or role it supports",
      "Certification or scheme it counts towards",
      "Refresher due"
     ]
    }
   ]
  },
  "tailoring": {
   "intro": "Tell us about your role and your organisation, and the page suggests where to start: the modules, the activities and the next checkpoint that fit. If you have taken the self-assessment on the Capability model page in this browser, your organisation's maturity is filled in from it. Nothing leaves your browser.",
   "maturity": [
    {
     "level": "Beginning",
     "stage": "start",
     "checkpoint": "d30",
     "advice": "Start small: name owners and list critical assets before buying tools or writing strategies."
    },
    {
     "level": "Emerging",
     "stage": "start",
     "checkpoint": "d90",
     "advice": "Finish the basics for your most important assets, then make them repeatable."
    },
    {
     "level": "Learning",
     "stage": "build",
     "checkpoint": "m6",
     "advice": "You meet the policy for critical assets. Make the next return easier and fix your weakest strand."
    },
    {
     "level": "Developing",
     "stage": "embed",
     "checkpoint": "m12",
     "advice": "Make the cycle routine in business as usual, with a budget, and prepare assets for wider reuse."
    },
    {
     "level": "Mastering",
     "stage": "embed",
     "checkpoint": "m12",
     "advice": "Share what works across government, and help others in your sector."
    }
   ],
   "literacy": [
    {
     "id": "starting",
     "name": "Starting out",
     "text": "Few people outside the data team use terms such as owner, metadata or data quality with confidence.",
     "levels": [
      "Foundation"
     ],
     "tips": [
      "Start everyone with module M01 and the six things to know first.",
      "Use the glossary and the easy read summaries when you brief people.",
      "Explain the policy with one real asset people already know."
     ]
    },
    {
     "id": "building",
     "name": "Building",
     "text": "People in data roles know the terms; others are learning. Some teams already catalogue or check quality.",
     "levels": [
      "Foundation",
      "Practitioner"
     ],
     "tips": [
      "Give each role holder the modules on their route, and a date to finish them.",
      "Share filled templates between teams so they start from good examples.",
      "Run a short session on the yearly cycle before each return."
     ]
    },
    {
     "id": "confident",
     "name": "Confident",
     "text": "Data roles are established, and people across the organisation ask good questions about data.",
     "levels": [
      "Foundation",
      "Practitioner",
      "Advanced"
     ],
     "tips": [
      "Use the open data downloads and the standards on the Tools and interoperability page.",
      "Take on the AI-ready data stewardship pathway.",
      "Mentor another organisation in your sector."
     ]
    }
   ],
   "contexts": [
    {
     "id": "bau",
     "name": "Business as usual",
     "text": "Running critical data assets day to day: the yearly cycle of review, catalogue upkeep, quality checks and the return.",
     "roles": [
      "CDO",
      "COO",
      "BRD",
      "OWN",
      "IAO",
      "STW",
      "CUS",
      "CAT",
      "DQL",
      "DPO",
      "USR"
     ],
     "tips": [
      "Put the yearly cycle in the calendar: asset review, metadata update, DQAP review, board and return.",
      "Budget the cycle in the teams that own the assets, so it does not depend on a project.",
      "Check handovers six months after each project closes."
     ]
    },
    {
     "id": "change",
     "name": "Change programme",
     "text": "A programme or project that creates, changes, moves or retires critical data assets, from business case to handover.",
     "roles": [
      "SRO",
      "PDM",
      "PMO",
      "SVO",
      "ARC",
      "MIG",
      "CML",
      "OWN",
      "STW",
      "DPO"
     ],
     "tips": [
      "Name the critical assets in the business case, and the business-as-usual owner for each before build.",
      "Use spend control, gate reviews and service assessments as checkpoints for data.",
      "Plan migration, reconciliation, exit and handover from the start, not at the end."
     ]
    },
    {
     "id": "both",
     "name": "Both",
     "text": "Your organisation runs business as usual and change at the same time, and the same people often do both.",
     "roles": [
      "CDO",
      "COO",
      "OWN",
      "STW",
      "ARC",
      "CML"
     ],
     "tips": [
      "Keep one asset register, one set of roles and one catalogue for both, so change feeds business as usual.",
      "Make programmes hand their assets into the yearly cycle with the handover checklist."
     ]
    }
   ],
   "persona_context": {
    "cdo": "both",
    "coo": "bau",
    "own": "both",
    "stw": "bau",
    "cat": "bau",
    "dql": "bau",
    "prg": "change",
    "buy": "both"
   }
  },
  "assessments": {
   "intro": "Service assessments and gate reviews ask whether data management has been thought about, not for every template. Show that the critical data assets the service creates, changes or retires are known, owned, described, of known quality, protected and handed over, and keep the templates as your working evidence.",
   "principles": [
    "Show decisions and their reasons, not documents for their own sake. One page of evidence per point is usually enough.",
    "Use the same asset list, owners and catalogue records the organisation reports under the DAM Policy, so nothing is written twice.",
    "Name the business-as-usual owner of each critical asset before beta, not at handover.",
    "Bring the data people to the assessment: the owner or steward can answer questions a delivery manager cannot."
   ],
   "stages": [
    {
     "id": "plan",
     "gates": [
      "Spend control",
      "Gate 0 strategic assessment (programmes)",
      "Gate 1 business justification"
     ],
     "points": [],
     "look_for": [
      "Which critical data assets the programme creates, changes, depends on or retires, and who owns them.",
      "The cost of the data work, and of not doing it, in the business case.",
      "Data risks on the programme register."
     ],
     "evidence": [
      {
       "text": "Data assets section of the business case",
       "ref": "T-INV-1"
      },
      {
       "text": "Critical assets ranked by value and risk",
       "ref": "STR-1"
      },
      {
       "text": "Data risks recorded",
       "ref": "RISK-1"
      },
      {
       "text": "Benefits with baselines",
       "ref": "BEN-1"
      }
     ],
     "gaps": [
      "Data appears as an IT cost line with no named assets",
      "No owner is consulted before the case is approved"
     ],
     "refs": [
      "RB-SPEND",
      "RB-GATE0",
      "RB-GREEN"
     ]
    },
    {
     "id": "discover",
     "gates": [
      "Discovery peer review, where your organisation runs one",
      "Spend control"
     ],
     "points": [
      1,
      2,
      3
     ],
     "look_for": [
      "That the team searched the catalogue for existing data before planning to collect more.",
      "Who holds the data the service needs today, inside and outside the organisation, and under what agreements.",
      "The people the data describes, and what they would expect."
     ],
     "evidence": [
      {
       "text": "Catalogue searched and existing assets listed",
       "ref": "cat.discover"
      },
      {
       "text": "Third-party and supplier data found",
       "ref": "SUPP-1"
      },
      {
       "text": "Users of the critical assets and their problems",
       "ref": "CULT-1"
      },
      {
       "text": "Reuse checked before new collection",
       "ref": "CH-13"
      }
     ],
     "gaps": [
      "Data collected again because nobody looked for it",
      "Supplier-held data discovered only at contract end"
     ],
     "refs": [
      "RB-SVCASSESS",
      "RB-SVC"
     ]
    },
    {
     "id": "alpha",
     "gates": [
      "Alpha service assessment",
      "Gate 2 delivery strategy",
      "Spend control"
     ],
     "points": [
      2,
      6,
      9,
      11,
      13
     ],
     "look_for": [
      "A data model with entities, relationships, identifiers and authoritative sources.",
      "Quality rules and targets agreed with owners before build.",
      "Open standards and government identifiers chosen, and how data would leave the chosen tools.",
      "Data roles in the team, and the protection and lawful basis for personal data."
     ],
     "evidence": [
      {
       "text": "Entities, relationships and authoritative sources",
       "ref": "MOD-1"
      },
      {
       "text": "Quality rules and targets defined",
       "ref": "dq.define"
      },
      {
       "text": "Identifiers and standards chosen",
       "ref": "INT-1"
      },
      {
       "text": "Exit questions answered for each new tool",
       "ref": "EXIT-1"
      },
      {
       "text": "Request for information with ready-made requirements, if buying",
       "ref": "TOOL-2"
      }
     ],
     "gaps": [
      "Local code lists invented where national ones exist",
      "A tool chosen before its export was tested"
     ],
     "refs": [
      "RB-SVCASSESS",
      "RB-SVC",
      "RB-OPEN",
      "RB-API"
     ]
    },
    {
     "id": "beta",
     "gates": [
      "Beta service assessment",
      "Gate 3 investment decision",
      "Spend control"
     ],
     "points": [
      5,
      9,
      10,
      13,
      14
     ],
     "look_for": [
      "Catalogue records for every critical asset before go-live, owned and reported.",
      "A quality baseline and a data quality action plan, with results the owner has seen.",
      "Data protection, sharing agreements and security controls in place for the classification.",
      "Migration reconciled and signed off, and the business-as-usual owner named.",
      "Contracts that keep the data and metadata yours and let you leave."
     ],
     "evidence": [
      {
       "text": "Assets described in the catalogue",
       "ref": "cat.describe"
      },
      {
       "text": "Quality baseline measured",
       "ref": "dq.baseline"
      },
      {
       "text": "Proof of concept with your own data, if buying",
       "ref": "TOOL-3"
      },
      {
       "text": "Data clauses in contracts",
       "ref": "SUPP-2"
      },
      {
       "text": "Migration reconciled",
       "ref": "LEG-2"
      },
      {
       "text": "Business-as-usual owner named",
       "ref": "HAND-1"
      }
     ],
     "gaps": [
      "Catalogue records written after go-live",
      "Quality known only from test data",
      "No named owner after the project"
     ],
     "refs": [
      "RB-SVCASSESS",
      "RB-SVC",
      "RB-GSC",
      "RB-ICODSA",
      "RB-A11YREQ"
     ]
    },
    {
     "id": "live",
     "gates": [
      "Live service assessment",
      "Gate 4 readiness for service",
      "Gate 5 operations review and benefits realisation"
     ],
     "points": [
      8,
      10,
      14
     ],
     "look_for": [
      "The yearly cycle running in business as usual: review, catalogue upkeep, quality checks and the return.",
      "Handover complete, with budget, and checked after six months.",
      "Benefits measured against the baseline, and data risks reviewed.",
      "An exit test each year for tools holding critical data."
     ],
     "evidence": [
      {
       "text": "Handover checklist signed",
       "ref": "HAND-2"
      },
      {
       "text": "Records kept current",
       "ref": "cat.maintain"
      },
      {
       "text": "Benefits reported",
       "ref": "BEN-2"
      },
      {
       "text": "Data risks reviewed",
       "ref": "RISK-3"
      },
      {
       "text": "Exit tested",
       "ref": "EXIT-3"
      }
     ],
     "gaps": [
      "The project team leaves and nobody reviews the asset",
      "Benefits claimed with no baseline"
     ],
     "refs": [
      "RB-SVCASSESS",
      "RB-GATE5",
      "RB-MAGENTA"
     ]
    },
    {
     "id": "retire",
     "gates": [
      "Retirement decision",
      "Gate 5 operations review, where it applies"
     ],
     "points": [
      14
     ],
     "look_for": [
      "Every critical asset in the system migrated, archived or disposed of under the retention schedule.",
      "Catalogue records marked retired, with what replaced them.",
      "The owner's sign-off before switch-off."
     ],
     "evidence": [
      {
       "text": "Assets in the legacy system listed",
       "ref": "LEG-1"
      },
      {
       "text": "Switch-off signed off",
       "ref": "LEG-3"
      },
      {
       "text": "Legacy exit planned from the asset register",
       "ref": "CH-04"
      }
     ],
     "gaps": [
      "Data needed for records or legal reasons lost at switch-off",
      "Retired assets vanish from the catalogue"
     ],
     "refs": [
      "RB-RETIRE",
      "RB-TNAIM",
      "RB-LEGACY"
     ]
    }
   ]
  }
 },
 "procurement": {
  "meta": {
   "as_of": "2026-11-17",
   "status": "Draft by this portal for review by commercial, digital and data professionals. Not government guidance.",
   "intro": "Ready-made requirements to adapt when you buy or build a tool that supports data asset management. Pick the kinds of tool you need, keep the requirements that fit, change the priority to suit, and use them in a request for information (RFI), a tender or an internal build. Each requirement says which DAM Policy requirement and capability it serves, and how a supplier can prove it.",
   "not_advice": "This is not commercial or legal advice. Your commercial team chooses the route to market and the evaluation method, and the Procurement Act 2023 and its guidance govern the process. Do not copy these requirements into a tender without that review.",
   "inputs": [
    {
     "id": "IN-PILOT",
     "label": "A pilot team's request for standardised templates for the activities in the playbooks (Project Compass session, 11 November 2026)",
     "prov": "O"
    },
    {
     "id": "IN-MDM",
     "label": "A programme choosing a master data management tool asked how other public bodies chose and use such tools (13 November 2026)",
     "prov": "O"
    }
   ]
  },
  "moscow": [
   {
    "code": "Must",
    "text": "Without this the tool cannot do the job, or the organisation cannot meet the DAM Policy. A response that does not meet it fails, however it scores elsewhere."
   },
   {
    "code": "Should",
    "text": "Important and expected. Scored; a gap needs a plan and a date."
   },
   {
    "code": "Could",
    "text": "Useful if it costs little. Scored lightly."
   },
   {
    "code": "Won't (this time)",
    "text": "Out of scope for this purchase. Recorded so the decision is visible."
   }
  ],
  "scoring": [
   {
    "score": 4,
    "label": "Exceeds",
    "text": "Fully meets the requirement, shown in the demonstration or proof of concept, with evidence of use in the public sector."
   },
   {
    "score": 3,
    "label": "Meets",
    "text": "Fully meets the requirement, with credible evidence."
   },
   {
    "score": 2,
    "label": "Mostly meets",
    "text": "Meets most of it; the gap is minor and has a dated plan."
   },
   {
    "score": 1,
    "label": "Partly meets",
    "text": "Significant gaps, or depends on custom work or a third party."
   },
   {
    "score": 0,
    "label": "Does not meet",
    "text": "Not met, not answered, or no evidence."
   }
  ],
  "evaluation": [
   "Agree the evaluation method with your commercial team before you publish anything, and publish it with the tender.",
   "Treat every Must as pass or fail. Score Should and Could requirements from 0 to 4 against the scale here.",
   "Weight the groups of requirements to reflect your priorities, and keep quality and price separate until both are scored.",
   "Score independently first, then moderate as a panel and record the reasons for each moderated score.",
   "Score what the supplier showed you, in the demonstration or proof of concept, above what they wrote.",
   "Keep the scoring sheets, the moderation notes and the decision. They are part of your assurance evidence."
  ],
  "functional": [
   {
    "id": "FR-CAT-01",
    "cat": "TL-CAT",
    "moscow": "Must",
    "caps": [
     "CR-06"
    ],
    "reqs": [
     "DAM-R02",
     "DAM-R13"
    ],
    "refs": [
     "RB-DCATGOV",
     "RB-DCAT"
    ],
    "text": "Record every metadata property in the government guidance on describing data assets, with its obligation, in plain English.",
    "test": "Create a record for one of your critical assets with every property filled in; show where each is held."
   },
   {
    "id": "FR-CAT-02",
    "cat": "TL-CAT",
    "moscow": "Must",
    "caps": [
     "CR-06",
     "CR-03"
    ],
    "reqs": [
     "DAM-R03"
    ],
    "refs": [
     "RB-DCAT",
     "RB-METASTD"
    ],
    "text": "Export the records for critical data assets as DCAT in a form that can be reported to the centre, without manual rework.",
    "test": "Export your test records and validate them against the reporting format."
   },
   {
    "id": "FR-CAT-03",
    "cat": "TL-CAT",
    "moscow": "Must",
    "caps": [
     "CR-07"
    ],
    "reqs": [
     "DAM-R05",
     "DAM-R10"
    ],
    "refs": [
     "RB-DCATGOV"
    ],
    "text": "Hold a named data owner, information asset owner and steward for each asset as roles, and record a successor when an owner leaves.",
    "test": "Change an asset's owner and show the history and the successor field."
   },
   {
    "id": "FR-CAT-04",
    "cat": "TL-CAT",
    "moscow": "Must",
    "caps": [
     "CR-06",
     "CR-04"
    ],
    "reqs": [
     "DAM-R04"
    ],
    "refs": [
     "RB-DCATGOV"
    ],
    "text": "Prompt owners to review each record at least once a year, and report which records are overdue.",
    "test": "Show the review reminder and the overdue report for a record past its review date."
   },
   {
    "id": "FR-CAT-05",
    "cat": "TL-CAT",
    "moscow": "Must",
    "caps": [
     "CR-05"
    ],
    "reqs": [
     "DAM-R01",
     "DAM-R11"
    ],
    "refs": [
     "RB-DCATGOV"
    ],
    "text": "Flag which assets are critical data assets, which of the seven purposes each supports, and its security classification.",
    "test": "Filter the catalogue to critical assets by purpose and classification."
   },
   {
    "id": "FR-CAT-06",
    "cat": "TL-CAT",
    "moscow": "Should",
    "caps": [
     "CR-12",
     "CR-14"
    ],
    "reqs": [
     "DAM-R12"
    ],
    "refs": [
     "RB-DCAT"
    ],
    "text": "Link a distribution to the data set it comes from, and show the source data set on the distribution's record.",
    "test": "Create a distribution and its source, and show the link in both records."
   },
   {
    "id": "FR-CAT-07",
    "cat": "TL-CAT",
    "moscow": "Should",
    "caps": [
     "CR-06"
    ],
    "reqs": [
     "DAM-R02"
    ],
    "refs": [
     "RB-DCAT"
    ],
    "text": "Harvest technical metadata, such as tables, columns and types, from your data platforms on a schedule.",
    "test": "Connect to one of your platforms and show a harvested schema refreshed on a schedule."
   },
   {
    "id": "FR-CAT-08",
    "cat": "TL-CAT",
    "moscow": "Should",
    "caps": [
     "CR-06",
     "CR-22"
    ],
    "reqs": [
     "DAM-R02"
    ],
    "refs": [
     "RB-DCAT"
    ],
    "text": "Let users search and browse in plain language, and request access to an asset from its record.",
    "test": "A user with no training finds an asset and requests access during the demonstration."
   },
   {
    "id": "FR-CAT-09",
    "cat": "TL-CAT",
    "moscow": "Should",
    "caps": [
     "CR-16"
    ],
    "reqs": [
     "DAM-R01"
    ],
    "refs": [
     "RB-GSC"
    ],
    "text": "Show or hide records and fields according to the user's access rights and the asset's classification.",
    "test": "Show the same record to two users with different rights."
   },
   {
    "id": "FR-CAT-10",
    "cat": "TL-CAT",
    "moscow": "Could",
    "caps": [
     "CR-06",
     "CR-11"
    ],
    "reqs": [
     "DAM-R16"
    ],
    "refs": [
     "RB-DCAT",
     "RB-SKOS"
    ],
    "text": "Let you add custom properties without losing them on export.",
    "test": "Add a custom property, export as DCAT and show it in the output."
   },
   {
    "id": "FR-GLOS-01",
    "cat": "TL-GLOS",
    "moscow": "Must",
    "caps": [
     "CR-06",
     "CR-11"
    ],
    "reqs": [
     "DAM-R13"
    ],
    "refs": [
     "RB-SKOS"
    ],
    "text": "Hold terms with definitions, synonyms, broader and narrower terms, an owner and a status.",
    "test": "Create a term with a broader term and a synonym and show its history."
   },
   {
    "id": "FR-GLOS-02",
    "cat": "TL-GLOS",
    "moscow": "Must",
    "caps": [
     "CR-11",
     "CR-32"
    ],
    "reqs": [
     "DAM-R16"
    ],
    "refs": [
     "RB-SKOS"
    ],
    "text": "Import and export the glossary as SKOS without losing hierarchy, synonyms or links to assets.",
    "test": "Export as SKOS, import into a test instance and compare."
   },
   {
    "id": "FR-GLOS-03",
    "cat": "TL-GLOS",
    "moscow": "Should",
    "caps": [
     "CR-06"
    ],
    "reqs": [
     "DAM-R02"
    ],
    "refs": [
     "RB-SKOS"
    ],
    "text": "Link terms to the data assets and fields that use them.",
    "test": "Show a term and every asset and field linked to it."
   },
   {
    "id": "FR-GLOS-04",
    "cat": "TL-GLOS",
    "moscow": "Should",
    "caps": [
     "CR-07"
    ],
    "reqs": [
     "DAM-R05"
    ],
    "refs": [
     "RB-SKOS"
    ],
    "text": "Route proposed new or changed terms to their steward for approval, and record the decision.",
    "test": "Propose a change, approve it as the steward and show the record."
   },
   {
    "id": "FR-DQ-01",
    "cat": "TL-DQ",
    "moscow": "Must",
    "caps": [
     "CR-08"
    ],
    "reqs": [
     "DAM-R06",
     "DAM-R07"
    ],
    "refs": [
     "RB-DQHUB"
    ],
    "text": "Profile a data set and run rules that measure the data quality dimensions your action plan uses.",
    "test": "Profile one of your critical data sets and run three of your rules."
   },
   {
    "id": "FR-DQ-02",
    "cat": "TL-DQ",
    "moscow": "Must",
    "caps": [
     "CR-08",
     "CR-32"
    ],
    "reqs": [
     "DAM-R06"
    ],
    "refs": [
     "RB-DQV",
     "RB-CSVW"
    ],
    "text": "Hold rules in a readable form you can export and run elsewhere, not only inside the product.",
    "test": "Export the rules and show their content."
   },
   {
    "id": "FR-DQ-03",
    "cat": "TL-DQ",
    "moscow": "Must",
    "caps": [
     "CR-09"
    ],
    "reqs": [
     "DAM-R15"
    ],
    "refs": [
     "RB-DQHUB"
    ],
    "text": "Raise an issue when a rule fails, assign it to an owner, and track it to resolution.",
    "test": "Fail a rule and follow the issue to closure."
   },
   {
    "id": "FR-DQ-04",
    "cat": "TL-DQ",
    "moscow": "Should",
    "caps": [
     "CR-09",
     "CR-08"
    ],
    "reqs": [
     "DAM-R15"
    ],
    "refs": [
     "RB-DQHUB"
    ],
    "text": "Prioritise issues with the government data quality issues framework: target range from importance and impact, priority from the band below target.",
    "test": "Set importance and impact for an asset and show the target and priority produced."
   },
   {
    "id": "FR-DQ-05",
    "cat": "TL-DQ",
    "moscow": "Should",
    "caps": [
     "CR-04",
     "CR-08"
    ],
    "reqs": [
     "DAM-R06"
    ],
    "refs": [
     "RB-DQV"
    ],
    "text": "Publish results as DQV or through an open API so the catalogue can show them on the asset's record.",
    "test": "Show a quality score on the catalogue record, taken from the tool through an open route."
   },
   {
    "id": "FR-DQ-06",
    "cat": "TL-DQ",
    "moscow": "Should",
    "caps": [
     "CR-08"
    ],
    "reqs": [
     "DAM-R06"
    ],
    "refs": [
     "RB-DQHUB"
    ],
    "text": "Show trends over time for each rule and dimension.",
    "test": "Show a three-month trend for one rule."
   },
   {
    "id": "FR-DQ-07",
    "cat": "TL-DQ",
    "moscow": "Could",
    "caps": [
     "CR-08",
     "CR-30"
    ],
    "reqs": [
     "DAM-R06"
    ],
    "refs": [
     "RB-EQA",
     "RB-PSED"
    ],
    "text": "Compare quality across groups of people, such as completeness by age or ethnicity, to show where gaps fall unevenly.",
    "test": "Show completeness of one field split by a protected characteristic in test data."
   },
   {
    "id": "FR-LIN-01",
    "cat": "TL-LIN",
    "moscow": "Must",
    "caps": [
     "CR-12",
     "CR-10"
    ],
    "reqs": [
     "DAM-R12"
    ],
    "refs": [
     "RB-OLINEAGE"
    ],
    "text": "Show where a critical data set comes from and where it goes, across systems from more than one supplier.",
    "test": "Trace one of your critical data sets from source to a report."
   },
   {
    "id": "FR-LIN-02",
    "cat": "TL-LIN",
    "moscow": "Should",
    "caps": [
     "CR-11",
     "CR-32"
    ],
    "reqs": [
     "DAM-R16"
    ],
    "refs": [
     "RB-OLINEAGE",
     "RB-PROVO"
    ],
    "text": "Emit and accept OpenLineage events, including from pipelines the supplier does not provide.",
    "test": "Send an OpenLineage event from your own pipeline and show it in the tool."
   },
   {
    "id": "FR-LIN-03",
    "cat": "TL-LIN",
    "moscow": "Should",
    "caps": [
     "CR-31",
     "CR-08"
    ],
    "reqs": [
     "DAM-R06"
    ],
    "refs": [
     "RB-OLINEAGE"
    ],
    "text": "Alert the owner when a pipeline that feeds a critical asset fails or runs late.",
    "test": "Stop a pipeline and show the alert."
   },
   {
    "id": "FR-LIN-04",
    "cat": "TL-LIN",
    "moscow": "Could",
    "caps": [
     "CR-26"
    ],
    "reqs": [
     "DAM-R12"
    ],
    "refs": [
     "RB-OLINEAGE"
    ],
    "text": "Show what depends on a system or table before it is changed or switched off.",
    "test": "Select a table and list everything downstream."
   },
   {
    "id": "FR-MDM-01",
    "cat": "TL-MDM",
    "moscow": "Must",
    "caps": [
     "CR-14"
    ],
    "reqs": [
     "DAM-R12"
    ],
    "refs": [
     "RB-REFARCH"
    ],
    "text": "Hold a master record for each shared entity, with its identifier and source.",
    "test": "Load two sources of the same entity and show the master record."
   },
   {
    "id": "FR-MDM-02",
    "cat": "TL-MDM",
    "moscow": "Must",
    "caps": [
     "CR-14",
     "CR-08"
    ],
    "reqs": [
     "DAM-R06"
    ],
    "refs": [
     "RB-REFARCH"
    ],
    "text": "Apply matching and survivorship rules you can read, change and export, and send doubtful matches to a steward.",
    "test": "Run matching on test data and resolve a doubtful match."
   },
   {
    "id": "FR-MDM-03",
    "cat": "TL-MDM",
    "moscow": "Must",
    "caps": [
     "CR-14",
     "CR-32"
    ],
    "reqs": [
     "DAM-R16"
    ],
    "refs": [
     "RB-API",
     "RB-LOCKIN"
    ],
    "text": "Extract master and reference data, rules and history in an open format, and serve them through a documented API.",
    "test": "Export everything and call the API for one entity."
   },
   {
    "id": "FR-MDM-04",
    "cat": "TL-MDM",
    "moscow": "Should",
    "caps": [
     "CR-11",
     "CR-14"
    ],
    "reqs": [
     "DAM-R13"
    ],
    "refs": [
     "RB-REFDATA",
     "RB-UPRN",
     "RB-ONSGEO"
    ],
    "text": "Use national identifiers and code lists, such as UPRN, company numbers and ONS geography codes, where they exist.",
    "test": "Load a national code list and match local values to it."
   },
   {
    "id": "FR-MDM-05",
    "cat": "TL-MDM",
    "moscow": "Should",
    "caps": [
     "CR-14"
    ],
    "reqs": [
     "DAM-R04"
    ],
    "refs": [
     "RB-REFDATA"
    ],
    "text": "Version reference lists and record who changed what and why.",
    "test": "Change a code and show the version history."
   },
   {
    "id": "FR-MDM-06",
    "cat": "TL-MDM",
    "moscow": "Could",
    "caps": [
     "CR-28",
     "CR-14"
    ],
    "reqs": [
     "DAM-R16"
    ],
    "refs": [
     "RB-REFDATA",
     "RB-SKOS"
    ],
    "text": "Publish reference lists for others to reuse, with persistent identifiers.",
    "test": "Publish a list and resolve one of its identifiers."
   },
   {
    "id": "FR-POL-01",
    "cat": "TL-POL",
    "moscow": "Must",
    "caps": [
     "CR-07",
     "CR-01"
    ],
    "reqs": [
     "DAM-R05",
     "DAM-R09"
    ],
    "refs": [
     "RB-DSGF"
    ],
    "text": "Route stewardship tasks, approvals and access requests to the named owner or steward, and keep the decision record.",
    "test": "Raise an access request and approve it as the owner."
   },
   {
    "id": "FR-POL-02",
    "cat": "TL-POL",
    "moscow": "Must",
    "caps": [
     "CR-16"
    ],
    "reqs": [
     "DAM-R01"
    ],
    "refs": [
     "RB-GSC"
    ],
    "text": "Hold classifications and access policies that other tools can read through an API.",
    "test": "Read an asset's classification from another tool through the API."
   },
   {
    "id": "FR-POL-03",
    "cat": "TL-POL",
    "moscow": "Should",
    "caps": [
     "CR-17",
     "CR-28"
    ],
    "reqs": [
     "DAM-R09"
    ],
    "refs": [
     "RB-DSGF",
     "RB-ICODSA"
    ],
    "text": "Manage data sharing requests and agreements, with the lawful basis and legal gateway recorded.",
    "test": "Record a sharing request with its gateway and approve it."
   },
   {
    "id": "FR-POL-04",
    "cat": "TL-POL",
    "moscow": "Should",
    "caps": [
     "CR-19"
    ],
    "reqs": [
     "DAM-R09"
    ],
    "refs": [
     "RB-ORANGE"
    ],
    "text": "Record exceptions to policy with an owner, a reason and an expiry date, and remind before expiry.",
    "test": "Create an exception and show the expiry reminder."
   },
   {
    "id": "FR-CON-01",
    "cat": "TL-CONTRACT",
    "moscow": "Should",
    "caps": [
     "CR-12",
     "CR-08"
    ],
    "reqs": [
     "DAM-R06"
    ],
    "refs": [
     "RB-ODCS"
    ],
    "text": "Store data contracts as ODCS files you can keep in your own repository.",
    "test": "Export a contract and validate it against the ODCS schema."
   },
   {
    "id": "FR-CON-02",
    "cat": "TL-CONTRACT",
    "moscow": "Should",
    "caps": [
     "CR-08",
     "CR-11"
    ],
    "reqs": [
     "DAM-R06"
    ],
    "refs": [
     "RB-ODCS"
    ],
    "text": "Check data against the contract's schema and quality thresholds, and tell the owner when it breaks.",
    "test": "Break a contract in test data and show the notification."
   },
   {
    "id": "FR-CON-03",
    "cat": "TL-CONTRACT",
    "moscow": "Could",
    "caps": [
     "CR-06"
    ],
    "reqs": [
     "DAM-R02"
    ],
    "refs": [
     "RB-ODPS"
    ],
    "text": "Describe data products with ODPS and link them to their catalogue records.",
    "test": "Show a data product linked to its catalogue record."
   },
   {
    "id": "FR-REC-01",
    "cat": "TL-REC",
    "moscow": "Must",
    "caps": [
     "CR-15"
    ],
    "reqs": [
     "DAM-R04"
    ],
    "refs": [
     "RB-TNAIM",
     "RB-ISO15489"
    ],
    "text": "Apply your retention schedule and disposal actions, and record each disposal.",
    "test": "Apply a schedule to a record and show the disposal record."
   },
   {
    "id": "FR-REC-02",
    "cat": "TL-REC",
    "moscow": "Should",
    "caps": [
     "CR-15",
     "CR-06"
    ],
    "reqs": [
     "DAM-R02"
    ],
    "refs": [
     "RB-ISO23081"
    ],
    "text": "Share retention and disposal decisions with the catalogue so an asset and its records follow one schedule.",
    "test": "Show the retention period on the asset's catalogue record."
   },
   {
    "id": "FR-REC-03",
    "cat": "TL-REC",
    "moscow": "Could",
    "caps": [
     "CR-15"
    ],
    "reqs": [
     "DAM-R04"
    ],
    "refs": [
     "RB-TNATRANS"
    ],
    "text": "Prepare records for transfer to an archive in the format the archive accepts.",
    "test": "Package one record for transfer."
   },
   {
    "id": "FR-AI-01",
    "cat": "TL-AI",
    "moscow": "Should",
    "caps": [
     "CR-18",
     "CR-22"
    ],
    "reqs": [
     "DAM-R02"
    ],
    "refs": [
     "RB-AIPLAY",
     "RB-MCPSPEC"
    ],
    "text": "Let an assistant your organisation already approves read the catalogue through an open protocol or documented API.",
    "test": "Ask an approved assistant a question answered from the catalogue."
   },
   {
    "id": "FR-AI-02",
    "cat": "TL-AI",
    "moscow": "Must",
    "caps": [
     "CR-16",
     "CR-18"
    ],
    "reqs": [
     "DAM-R01"
    ],
    "refs": [
     "RB-AIPLAY",
     "RB-GSC"
    ],
    "text": "Apply the same access rules to an assistant as to the person using it, and never show restricted metadata.",
    "test": "Ask about a restricted asset as a user without access and show the refusal."
   },
   {
    "id": "FR-AI-03",
    "cat": "TL-AI",
    "moscow": "Should",
    "caps": [
     "CR-18"
    ],
    "reqs": [
     "DAM-R02"
    ],
    "refs": [
     "RB-AIPLAY",
     "RB-ATRS"
    ],
    "text": "Show the sources behind every answer, and record use so it can be described in an algorithmic transparency record if one is needed.",
    "test": "Ask a question and follow the source links in the answer."
   }
  ],
  "nonfunctional": [
   {
    "id": "NFR-01",
    "theme": "Accessibility",
    "moscow": "Must",
    "caps": [
     "CR-30",
     "CR-22"
    ],
    "refs": [
     "RB-A11YREQ",
     "RB-MODEL"
    ],
    "text": "Every screen staff use meets WCAG 2.2 level AA, not only public pages, and the supplier provides an accessibility statement.",
    "test": "An accessibility audit of the screens used in the proof of concept, and the statement."
   },
   {
    "id": "NFR-02",
    "theme": "Accessibility",
    "moscow": "Should",
    "caps": [
     "CR-30"
    ],
    "refs": [
     "RB-A11YREQ"
    ],
    "text": "Works with screen readers, screen magnifiers, voice control and keyboard only.",
    "test": "Complete a core task with a screen reader and with keyboard only."
   },
   {
    "id": "NFR-03",
    "theme": "Security",
    "moscow": "Must",
    "caps": [
     "CR-16",
     "CR-31"
    ],
    "refs": [
     "RB-GSC",
     "RB-NCSCCLOUD"
    ],
    "text": "Meets the security your data's classification requires, and the supplier shows how the service meets the NCSC cloud security principles.",
    "test": "The supplier's statement against the principles, reviewed by your security team."
   },
   {
    "id": "NFR-04",
    "theme": "Security",
    "moscow": "Must",
    "caps": [
     "CR-16"
    ],
    "refs": [
     "RB-SBD",
     "RB-GOVS007"
    ],
    "text": "Data is encrypted in transit and at rest, and the supplier explains key management.",
    "test": "Architecture description reviewed by your security team."
   },
   {
    "id": "NFR-05",
    "theme": "Security",
    "moscow": "Should",
    "caps": [
     "CR-31"
    ],
    "refs": [
     "RB-NCSCIR",
     "RB-CAF"
    ],
    "text": "The supplier will tell you about an incident affecting your data within an agreed time, and support your response.",
    "test": "The incident clause and the supplier's last incident report process."
   },
   {
    "id": "NFR-06",
    "theme": "Security",
    "moscow": "Should",
    "caps": [
     "CR-31",
     "CR-16"
    ],
    "refs": [
     "RB-NCSCPQC"
    ],
    "text": "The supplier has a plan for moving to post-quantum cryptography in line with the NCSC timelines.",
    "test": "The supplier's written plan."
   },
   {
    "id": "NFR-07",
    "theme": "Identity and access",
    "moscow": "Must",
    "caps": [
     "CR-16"
    ],
    "refs": [
     "RB-NCSCCLOUD"
    ],
    "text": "Uses your identity provider for sign-in and roles, rather than its own user store.",
    "test": "Sign in through your identity provider in the proof of concept."
   },
   {
    "id": "NFR-08",
    "theme": "Identity and access",
    "moscow": "Should",
    "caps": [
     "CR-16",
     "CR-19"
    ],
    "refs": [
     "RB-NCSC10"
    ],
    "text": "Logs who viewed or changed what, and lets you export the logs to your own monitoring.",
    "test": "Export a day of audit log."
   },
   {
    "id": "NFR-09",
    "theme": "Data protection",
    "moscow": "Must",
    "caps": [
     "CR-17",
     "CR-20"
    ],
    "refs": [
     "RB-DPA",
     "RB-MTC20",
     "RB-PPN020"
    ],
    "text": "Processes personal data only on your instructions, under a data processing schedule, with the location of processing stated.",
    "test": "The processing schedule and the list of sub-processors and locations."
   },
   {
    "id": "NFR-10",
    "theme": "Data protection",
    "moscow": "Should",
    "caps": [
     "CR-17"
    ],
    "refs": [
     "RB-DPA"
    ],
    "text": "Lets you find, export and delete a person's data to meet their rights.",
    "test": "Find and export one test person's data."
   },
   {
    "id": "NFR-11",
    "theme": "Interoperability",
    "moscow": "Must",
    "caps": [
     "CR-11",
     "CR-32"
    ],
    "refs": [
     "RB-PPN0715",
     "RB-TCOP4",
     "RB-OPEN"
    ],
    "text": "Uses open standards at every boundary with other tools, and names the standard and version for each.",
    "test": "The supplier's list of standards with versions, checked against the open standards for government."
   },
   {
    "id": "NFR-12",
    "theme": "Interoperability",
    "moscow": "Must",
    "caps": [
     "CR-11",
     "CR-12"
    ],
    "refs": [
     "RB-API",
     "RB-OAS"
    ],
    "text": "Every object and action in the interface is available through a documented API, described in OpenAPI.",
    "test": "The OpenAPI description, and a call for one object you choose."
   },
   {
    "id": "NFR-13",
    "theme": "Portability and exit",
    "moscow": "Must",
    "caps": [
     "CR-32",
     "CR-20"
    ],
    "refs": [
     "RB-LOCKIN",
     "RB-TCOP11"
    ],
    "text": "You can export all your content, including custom fields, history, owners, classifications and links, at any time, in open formats, without supplier help or extra charge.",
    "test": "A full export in the proof of concept, compared with what was loaded."
   },
   {
    "id": "NFR-14",
    "theme": "Portability and exit",
    "moscow": "Must",
    "caps": [
     "CR-32",
     "CR-26"
    ],
    "refs": [
     "RB-LOCKIN",
     "RB-MSC"
    ],
    "text": "The supplier gives a costed exit plan and will help you move to another product at the end of the contract.",
    "test": "The exit plan and the exit assistance terms."
   },
   {
    "id": "NFR-15",
    "theme": "Portability and exit",
    "moscow": "Should",
    "caps": [
     "CR-32",
     "CR-13"
    ],
    "refs": [
     "RB-LOCKIN"
    ],
    "text": "Each capability can be priced, bought and ended separately, even when sold as a suite.",
    "test": "A price for each capability on its own."
   },
   {
    "id": "NFR-16",
    "theme": "Hosting and resilience",
    "moscow": "Should",
    "caps": [
     "CR-31",
     "CR-12"
    ],
    "refs": [
     "RB-CLOUD",
     "RB-NCSCCLOUD"
    ],
    "text": "States availability, recovery time and recovery point targets, and reports against them.",
    "test": "The service level terms and the last year's performance."
   },
   {
    "id": "NFR-17",
    "theme": "Hosting and resilience",
    "moscow": "Should",
    "caps": [
     "CR-12"
    ],
    "refs": [
     "RB-CLOUD"
    ],
    "text": "Handles the number of assets, users and runs you expect in three years without a change of product tier you have not priced.",
    "test": "A load test or reference site at that scale, and the price at that volume."
   },
   {
    "id": "NFR-18",
    "theme": "Support and change",
    "moscow": "Should",
    "caps": [
     "CR-13",
     "CR-27"
    ],
    "refs": [
     "RB-SVC"
    ],
    "text": "Gives notice of changes that affect you, lets you test them first, and supports versions for an agreed time.",
    "test": "The release and support policy."
   },
   {
    "id": "NFR-19",
    "theme": "Support and change",
    "moscow": "Should",
    "caps": [
     "CR-21"
    ],
    "refs": [
     "RB-SVC"
    ],
    "text": "Provides training and guidance your staff can use without the supplier, in accessible formats.",
    "test": "A sample of the training and guidance."
   },
   {
    "id": "NFR-20",
    "theme": "Records and retention",
    "moscow": "Should",
    "caps": [
     "CR-15"
    ],
    "refs": [
     "RB-TNAIM"
    ],
    "text": "Lets you apply retention to the tool's own content and logs, and delete them when the schedule says.",
    "test": "Set retention on a test record and show its deletion."
   },
   {
    "id": "NFR-21",
    "theme": "AI and transparency",
    "moscow": "Must",
    "caps": [
     "CR-18"
    ],
    "refs": [
     "RB-AIPLAY",
     "RB-ETH"
    ],
    "text": "States any AI in the product, what it does with your data, and lets you turn it off. Your data is not used to train models without your agreement.",
    "test": "The supplier's AI statement and the setting to turn it off."
   },
   {
    "id": "NFR-22",
    "theme": "Open source and reuse",
    "moscow": "Could",
    "caps": [
     "CR-32",
     "CR-28"
    ],
    "refs": [
     "RB-OPENSRC",
     "RB-CHOOSE"
    ],
    "text": "Open source components, or the whole product, are named with their licences, and anything built for you can be shared across government.",
    "test": "The software bill of materials and the intellectual property terms."
   },
   {
    "id": "NFR-23",
    "theme": "Usability",
    "moscow": "Should",
    "caps": [
     "CR-22",
     "CR-21"
    ],
    "refs": [
     "RB-SVC"
    ],
    "text": "People who look after data part time can do the common tasks without specialist training.",
    "test": "Usability test with two of your stewards in the proof of concept."
   }
  ],
  "rfi_sections": [
   {
    "id": "RFI-A",
    "name": "About you",
    "questions": [
     "Describe your organisation and the product, and who builds and supports it.",
     "Which UK public sector bodies use the product for a similar purpose, and can we speak to one?",
     "Which buying routes is the product available through, such as G-Cloud?"
    ]
   },
   {
    "id": "RFI-B",
    "name": "Fit with our needs",
    "from": "functional",
    "lead": "For each requirement, say whether the product meets it now, partly, on a dated roadmap or not, and how you would show it."
   },
   {
    "id": "RFI-C",
    "name": "Interoperability and exit",
    "from": "questions",
    "lead": "The questions from the Tools and interoperability page."
   },
   {
    "id": "RFI-D",
    "name": "Security, accessibility and data protection",
    "from": "nonfunctional",
    "lead": "For each requirement, say how the product meets it and what evidence you can provide."
   },
   {
    "id": "RFI-E",
    "name": "Commercial",
    "questions": [
     "Describe the pricing model, what drives the price, and the price at our expected volume today and in three years.",
     "Can each capability be bought and ended separately?",
     "What are the renewal terms, and is any price increase capped?",
     "What does exit cost, and what help do you give?"
    ]
   },
   {
    "id": "RFI-F",
    "name": "Proof",
    "questions": [
     "Would you take part in a proof of concept with our own test data, including a full export and re-import?",
     "What would you need from us for the proof of concept, and how long would it take?"
    ]
   }
  ],
  "clauses": [
   {
    "id": "CL-01",
    "name": "Ownership of content",
    "caps": [
     "CR-32",
     "CR-20"
    ],
    "refs": [
     "RB-MSC",
     "RB-LOCKIN"
    ],
    "text": "You own your data and everything you put into or create in the tool: metadata, glossary, rules, results, lineage and configuration.",
    "why": "Without it the assets you report under the policy, and their history, may not be yours to move."
   },
   {
    "id": "CL-02",
    "name": "Export in open formats",
    "caps": [
     "CR-32"
    ],
    "refs": [
     "RB-LOCKIN",
     "RB-PPN0715"
    ],
    "text": "Full export at any time, in named open formats, at no extra charge, tested before go-live and before each renewal.",
    "why": "Keeps you able to report and to change product."
   },
   {
    "id": "CL-03",
    "name": "Exit plan and assistance",
    "caps": [
     "CR-32",
     "CR-26"
    ],
    "refs": [
     "RB-MSC",
     "RB-LOCKIN"
    ],
    "text": "A costed exit plan in the contract, updated each year, with the supplier's help to move.",
    "why": "An exit you have not planned is the legacy of the future."
   },
   {
    "id": "CL-04",
    "name": "Data processing",
    "caps": [
     "CR-17",
     "CR-20"
    ],
    "refs": [
     "RB-MTC20",
     "RB-PPN020"
    ],
    "text": "A data processing schedule naming the processing, sub-processors and locations.",
    "why": "Needed whenever personal data is processed for you."
   },
   {
    "id": "CL-05",
    "name": "Separate prices",
    "caps": [
     "CR-13",
     "CR-24"
    ],
    "refs": [
     "RB-TCOP11"
    ],
    "text": "A price for each capability, and the right to end one without ending the rest.",
    "why": "Lets you replace one part without replacing everything."
   },
   {
    "id": "CL-06",
    "name": "Capped increases",
    "caps": [
     "CR-24"
    ],
    "refs": [
     "RB-TCOP11"
    ],
    "text": "A cap on price increases at renewal, and notice of any change.",
    "why": "Keeps the cost in the business case true."
   },
   {
    "id": "CL-07",
    "name": "Security and incidents",
    "caps": [
     "CR-31",
     "CR-16"
    ],
    "refs": [
     "RB-GSC",
     "RB-NCSCIR"
    ],
    "text": "Security that matches the classification, notice of incidents within an agreed time, and help to respond.",
    "why": "Critical data assets must stay available and protected."
   },
   {
    "id": "CL-08",
    "name": "Accessibility",
    "caps": [
     "CR-30"
    ],
    "refs": [
     "RB-A11YREQ"
    ],
    "text": "The tool meets WCAG 2.2 AA for staff screens, with an accessibility statement kept up to date.",
    "why": "The accessibility regulations apply to tools staff use."
   },
   {
    "id": "CL-09",
    "name": "Service levels",
    "caps": [
     "CR-31"
    ],
    "refs": [
     "RB-NCSCCLOUD"
    ],
    "text": "Availability, recovery time and recovery point targets, reported each month, with remedies.",
    "why": "Owners need to know how long a critical asset could be unavailable."
   },
   {
    "id": "CL-10",
    "name": "AI use of your data",
    "caps": [
     "CR-18"
    ],
    "refs": [
     "RB-AIPLAY"
    ],
    "text": "No use of your data to train models without written agreement, and a setting to turn AI features off.",
    "why": "Keeps control of how your data is used."
   }
  ]
 }
}