About Level: Foundation
About this portal
Step-by-step guidance on data governance, data cataloguing and data quality for critical data assets in UK government.
In brief
- A prototype that brings together the playbooks for the three capabilities behind the DAM Policy.
- Every fact is labelled with where it came from.
- What it cannot yet do is listed openly under known limitations.
Purpose
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.
How sources are labelled
- V: Verified against the primary source Verified against the primary source
- P: Practitioner material from cross-government playbooks not yet published Practitioner material from cross-government playbooks not yet published
- O: This playbook's own synthesis of published guidance This playbook's own synthesis of published guidance
- S: Found by web search; the site blocked automated checking, so open it before relying on it Found by web search; the site blocked automated checking, so open it before relying on it
- K: General knowledge, not checked against a source in this release General knowledge, not checked against a source in this release
- U: Unconfirmed Unconfirmed
Requirement strength follows the wording of the source. Step sequences are labelled as synthesis or practitioner material; they are not GOV.UK requirements.
Verification findings
F-01: Issues framework Table 4 contradicts its own rule for a 97.5% target
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.
Action: This portal follows the stated rule. Raise with the GDS data quality team; tracked as a repository issue. Verified 2026-11-05 against Data quality issues framework
F-02: The Data Ethics Framework is now the Data and AI Ethics Framework
The GOV.UK page at the Data Ethics Framework address is titled 'Data and AI Ethics Framework' (updated 18 December 2025).
Action: Use the new name. Earlier practitioner material that cites the old name should be updated. Verified 2026-11-05 against the live page named above
F-03: The GOV.UK style guide has moved
The style guide and 'writing for GOV.UK' addresses on GOV.UK now redirect to guidance.publishing.service.gov.uk.
Action: Link to the new address. Verified 2026-11-05 against the live page named above
F-05: The government data maturity framework uses a licence this portal cannot carry
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.
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). Verified 2026-11-05 against Data maturity assessment for government
F-06: Legacy technology guidance asks for a data asset register but does not mention the DAM Policy
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.
Action: Delivery and change practice CH-04 starts legacy exits from the DAM catalogue. Suggest GDS cross-refers the two. Verified 2026-11-05 against Managing legacy technology
F-07: The government learning platform is not yet fully accessible
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.
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. Verified 2026-11-05 against Accessibility statement for the Government Skills Campus
F-04: Four metadata properties have no slot in the Metadata Exchange Model
temporalCoverage, conformsTo, expires and supersededBy appear in the GOV.UK metadata guidance but not in the published MEM classes.
Action: Proposed crosswalk below, to be agreed by the metadata standards owner (OR-06). Verified 2026-11-05 against Recording metadata to describe critical data assets
How the portal decides things
- Search order. Exact title matches first, then titles that start with your words, then titles containing all your words, then other matches, each in page order.
- Progress. A step is done when you mark it. A module is done when all its activities are marked. A route counts both.
- Status page. A weekly automated run checks sources, the review date and page weight. It never changes content; it opens an issue for a person to act on.
Known limitations
What this prototype cannot yet do or promise. Bear these in mind while you test it, and tell us through the testing page or the contact form if you can help close one.
| ID | Limitation |
|---|---|
| OR-01 | The cataloguing method is built from public guidance. 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. |
| OR-02 | How long private feedback is kept is not yet confirmed. 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. |
| OR-03 | Not cleared as official guidance. Not cleared as official guidance. Clearance, and a move to an official GitHub organisation, are needed before departments are told to rely on it. |
| OR-04 | Not yet tested with users. 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. |
| OR-05 | Interoperability requirements are not yet stated. 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. |
| OR-06 | Proposed metadata terms are not agreed. 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. |
| OR-07 | Some dates come from material that is not public. Dates for the rollout phases, returns and support offer come from practitioner material, not a public page. Confirm before external use. |
| OR-08 | Escalation timescales are a recommendation. The governance escalation timescales are this playbook's recommendation. Each organisation should set its own. |
| OR-09 | Not yet tested with disabled people. Not tested with disabled users or assistive technology users in person; automated checks only. |
| OR-12 | Sector supplements need review by sector experts. 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. |
| OR-14 | The maturity framework is linked, not copied. 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). |
| OR-15 | Capability flags are this portal''s reading of the policy. 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. |
Accessibility statement
This portal aims to meet WCAG 2.2 at level AA. Each release is checked automatically with axe-core in a real browser, for keyboard use, for sideways scrolling from 320 to 1920 pixels wide, and in light and dark modes. You can change text size, line spacing and colours in Display options.
Known limitations: it has not been tested in person with disabled users or with assistive technology users (OR-09). The knowledge graph is a visual aid; the same relationships are in tables on the policy and capability pages. Progress tracking needs scripts; every page can be read without them.
If you find a problem, use the contact form. If you cannot use it, ask a colleague to send it for you. If you are not happy with the response, contact the Equality Advisory and Support Service (EASS).
Privacy
The portal sets no cookies and loads nothing from other sites. Your display choices and progress are kept only in your own browser and can be cleared from the home page. The contact form opens GitHub, where messages are public. Ideas and votes are GitHub Discussions, which are public too. If you sign up for user research, a separate private form collects your contact details; see how we look after them.
The private feedback form
The private feedback form is a Microsoft form. It opens with the page or task you came from filled in.
- 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.
Build and checks
Build DAMCP-1.10.1-C5B3DD76. Generated from one content file. Each release runs structural, link, provenance, email, language, accessibility and layout checks. Each check is shown to fail on a deliberate break before it is trusted. Defects and the checks that now prevent each one are recorded in the repository, with the build report and the full register of open items: repository documents.
Was this page useful? Tell us Tell us privately, without GitHub