Have your say Level: Foundation
Have your say: shape this portal
Take part in user research, suggest and vote for ideas, and see what is planned and why. We work in the open.
In brief
- Sign up for research that suits you: from a 5 minute survey to an hour on a call.
- Suggest ideas and vote for the ones you want; votes count towards priority.
- See the roadmap, the backlog of 32 items and how each is scored against government strategy.
Easy read summary
- 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.
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
Want to do more? Get involved: improve the content, champion the portal in your team, and earn badges.
Ways to take part
Choose as many or as few as suit you. Every session is online unless you ask otherwise, and you can stop at any time.
45 to 60 minutes · Online, one to one
Interview
How you manage data assets today and what gets in the way
45 to 60 minutes · Online, one to one, you share your screen
Usability session
Try real tasks on the portal while thinking aloud
10 to 15 minutes · Online, in your own time
Tree test or card sort
Find things using only the menu labels, so we can test the structure
5 to 10 minutes · Online, in your own time
Survey
How you use the portal and what you need next
60 to 90 minutes · Online or in person, with your own set-up
Accessibility session
Use the portal with your assistive technology, such as a screen reader, magnifier or voice control
About an hour a month · Online, as a group
Review panel
Review drafts of new content, such as sector supplements, before they are published
Who we want to hear from
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. See Your role for the roles.
Sign up
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.
The form asks for:
- 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
If you use assistive technology, tell us what you use and anything we should arrange. We follow the Service Manual on Service Manual: running research sessions with disabled peopleV: Verified against the primary source on 2026-11-05.
How we look after you and your information
- 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.
This follows the Service Manual on Service Manual: getting informed consent for user researchV: Verified against the primary source on 2026-11-05 and Service Manual: managing user research data and participant privacyV: Verified against the primary source on 2026-11-05.
Research rounds
Each round answers questions from the research plan on Service design, and tests its hypotheses.
| Round | Name | What it will find out | Methods | When | Hypotheses tested |
|---|---|---|---|---|---|
| R-0 | Introduce and recruit | Introduce the portal to prospective users and teams and build a pool of participants for every role. | Survey | Now | None yet |
| R-1 | Find and follow | Can each role find and follow the steps that apply to them? | Usability session, Tree test or card sort | Next | H-01 |
| R-2 | Access for everyone | Can people who use assistive technology complete a route without help? | Accessibility session | Next | None yet |
| R-3 | Fit with how organisations work | Do the hand-offs, roles and yearly cycle match how organisations actually work? | Interview, Review panel | Later | H-02, H-03 |
Introduce the portal to your team
Share this page with colleagues who manage, describe or use data assets. Teams can take part together in a review panel.
Roadmap
What is being worked on now, next and later, modelled on the data.gov.uk roadmapV: Verified against the primary source on 2026-11-05. Now holds at most 5 items at a time, so work gets finished; it holds 4. Reviewed at least every 3 months and after each research round.
Now 4
Being worked on, or next to start.
BL-13 · Research
Round 0: introduce the portal and recruit participants
As the service owner, I need a pool of participants from every role, organisation type and nation, so that research rounds can start quickly.
Score 80 Strong candidate for Now
BL-12 · Feature
Private research sign-up form
As a prospective participant, I need to sign up privately, so that my contact details are not published.
Score 77 Strong candidate for Now
BL-22 · Decision
Clearance and an official home
As a department, I need to know whether this is guidance I can rely on, so that I can use it in my organisation.
Score 70 Strong candidate for Now
Data asset management policy A roadmap for modern digital government 2025 to 2030
BL-34 · Content
Health and care obligations from DHSC and MedTech
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.
Score 43 Later or not yet · decided differently
Next 3
Planned once Now has room.
BL-10 · Research
Round 1: can each role find and follow its steps?
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.
Score 78 Strong candidate for Now · decided differently
Data asset management policy A roadmap for modern digital government 2025 to 2030
BL-11 · Research
Test with disabled people and assistive technology
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.
Score 75 Strong candidate for Now · decided differently
BL-14 · Content
Expert review of the sector supplements
As a sector specialist, I need the supplements checked by people who know the sector, so that I can trust them.
Score 53 Candidate for Next
Later 4
Wanted, but not yet planned.
BL-23 · Content
Agreed metadata terms for the four missing properties
As a catalogue manager, I need agreed terms for every required property, so that our records match everyone else's.
Score 58 Candidate for Next · decided differently
BL-36 · Content
Data architecture capability playbook
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.
Score 38 Later or not yet
BL-24 · Research
Welsh language needs
As someone in a Welsh public body, I may need the portal in Welsh, so that we can meet our language duties.
Score 28 Later or not yet
BL-29 · Content
Welsh language summaries
As someone in a Welsh public body, I need key pages summarised in Welsh, so that we can meet our language duties.
Score 28 Later or not yet
Done
- BL-01 Private feedback route released in 1.8.0
- BL-02 Share, site map, guided tours and tutorials released in 1.8.0
- BL-03 Signposts to the sister portals released in 1.8.1
- BL-04 Data portals compass released in 1.8.2
- BL-05 Research, roadmap and ideas in the open released in 1.9.0
- BL-15 Check this flag released in 1.10.0
- BL-16 Embed a step or table on an intranet released in 1.10.0
- BL-17 Level labels and easy read summaries released in 1.10.0
- BL-18 Ask questions answered from the portal released in 1.10.0
- BL-19 Releases feed released in 1.10.0
- BL-20 Lineage and ontology downloads released in 1.10.0
- BL-21 Offline copy released in 1.10.0
- BL-26 Boards, councils and networks released in 1.10.0
- BL-27 Get involved and champions toolkit released in 1.10.0
- BL-28 Badges for taking part released in 1.10.0
- BL-30 Governance layers and what each may change released in 1.12.0
- BL-31 Retention fields in the ownership register and catalogue record released in 1.12.0
- BL-32 Data sharing agreement template and gateways released in 1.12.0
- BL-33 Data architecture and models supplement released in 1.12.0
- BL-35 Drill down from the DAMA wheel to activities and tasks released in 1.14.0
Every change is on What's new.
Out of scope
- BL-25 A chatbot hosted by this portal. 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).
Backlog
Every item is written as a user story, with where it came from: research, the open register, an idea, or a review. Download it as CSV or JSON.
| ID | Story | Type | Came from | Status | Score | Fits |
|---|---|---|---|---|---|---|
| BL-13 | Round 0: introduce the portal and recruit participants As the service owner, I need a pool of participants from every role, organisation type and nation, so that research rounds can start quickly. | Research | OR-04 | Now | 80 | A roadmap for modern digital government 2025 to 2030 |
| BL-12 | Private research sign-up form As a prospective participant, I need to sign up privately, so that my contact details are not published. | Feature | OR-02 | Now | 77 | A roadmap for modern digital government 2025 to 2030 |
| BL-22 | Clearance and an official home As a department, I need to know whether this is guidance I can rely on, so that I can use it in my organisation. | Decision | OR-03 | Now | 70 | Data asset management policy A roadmap for modern digital government 2025 to 2030 |
| BL-34 | Health and care obligations from DHSC and MedTech 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. | Content | Project Compass pilot (issue 22) | Now | 43 | Data asset management policy |
| BL-10 | Round 1: can each role find and follow its steps? 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. | Research | OR-04 | Next | 78 | Data asset management policy A roadmap for modern digital government 2025 to 2030 |
| BL-11 | Test with disabled people and assistive technology 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. | Research | OR-09 | Next | 75 | A roadmap for modern digital government 2025 to 2030 |
| BL-14 | Expert review of the sector supplements As a sector specialist, I need the supplements checked by people who know the sector, so that I can trust them. | Content | OR-12 | Next | 53 | Data asset management policy |
| BL-23 | Agreed metadata terms for the four missing properties As a catalogue manager, I need agreed terms for every required property, so that our records match everyone else's. | Content | OR-06 | Later | 58 | Data asset management policy National Data Library |
| BL-36 | Data architecture capability playbook 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. | Content | Owner request, 11 November 2026 | Later | 38 | A blueprint for modern digital government |
| BL-24 | Welsh language needs As someone in a Welsh public body, I may need the portal in Welsh, so that we can meet our language duties. | Research | Research question | Later | 28 | A roadmap for modern digital government 2025 to 2030 |
| BL-29 | Welsh language summaries As someone in a Welsh public body, I need key pages summarised in Welsh, so that we can meet our language duties. | Content | BL-24 | Later | 28 | A roadmap for modern digital government 2025 to 2030 |
| BL-05 | Research, roadmap and ideas in the open 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. | Feature | Owner request | Done | 78 | A roadmap for modern digital government 2025 to 2030 Data asset management policy |
| BL-01 | Private feedback route As someone without a GitHub account, I need a private way to give feedback, so that I can take part without publishing my views. | Feature | OR-02 | Done | 72 | A roadmap for modern digital government 2025 to 2030 |
| BL-03 | Signposts to the sister portals As a practitioner, I need to know when another portal goes deeper, so that I do not miss tools or evidence. | Feature | Owner request | Done | 72 | A roadmap for modern digital government 2025 to 2030 National Data Library |
| BL-04 | Data portals compass 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. | Feature | Owner request | Done | 72 | A roadmap for modern digital government 2025 to 2030 |
| BL-15 | Check this flag As a policy coordinator, I need to tell you when a capability flag looks wrong, so that the capability model stays accurate. | Feature | OR-15 | Done | 72 | Data asset management policy |
| BL-30 | Governance layers and what each may change 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. | Feature | Project Compass pilot (issue 21) | Done | 70 | Data asset management policy |
| BL-02 | Share, site map, guided tours and tutorials As a first-time visitor, I need to see how the portal fits together, so that I can find my way without help. | Feature | Owner request | Done | 68 | A roadmap for modern digital government 2025 to 2030 |
| BL-26 | Boards, councils and networks 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. | Content | Owner request | Done | 68 | Data asset management policy A roadmap for modern digital government 2025 to 2030 |
| BL-27 | Get involved and champions toolkit 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. | Feature | Owner request | Done | 65 | A roadmap for modern digital government 2025 to 2030 |
| BL-16 | Embed a step or table on an intranet 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. | Feature | Comparison with the Data Quality Commons | Done | 60 | A roadmap for modern digital government 2025 to 2030 |
| BL-17 | Level labels and easy read summaries 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. | Feature | Comparison with the Data Quality Commons | Done | 60 | A roadmap for modern digital government 2025 to 2030 |
| BL-19 | Releases feed As a returning user, I need to know when something changes, so that I keep up without checking the site. | Feature | Comparison with the Data Quality Commons | Done | 57 | A roadmap for modern digital government 2025 to 2030 |
| BL-18 | Ask questions answered from the portal 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. | Feature | Comparison with the Data Quality Commons and the catalogue | Done | 55 | A roadmap for modern digital government 2025 to 2030 |
| BL-33 | Data architecture and models supplement 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. | Content | Project Compass pilot (issue 18) | Done | 53 | A blueprint for modern digital government |
| BL-28 | Badges for taking part As someone who helps improve the portal, I want a badge for my profile and signature, so that my contribution is recognised. | Feature | Owner request | Done | 52 | A roadmap for modern digital government 2025 to 2030 |
| BL-32 | Data sharing agreement template and gateways 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. | Content | Project Compass pilot (issue 20) | Done | 52 | Data asset management policy National Data Library |
| BL-31 | Retention fields in the ownership register and catalogue record As a data owner, I need retention and disposal recorded with each asset, so that data is neither kept too long nor destroyed early. | Content | Project Compass pilot (issue 19) | Done | 47 | Data asset management policy |
| BL-20 | Lineage and ontology downloads 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. | Feature | Comparison with the catalogue | Done | 45 | National Data Library Data asset management policy |
| BL-21 | Offline copy As someone whose network blocks GitHub Pages, I need a copy I can open offline, so that I can still use the guidance. | Feature | Comparison with the catalogue | Done | 42 | A roadmap for modern digital government 2025 to 2030 |
| BL-35 | Drill down from the DAMA wheel to activities and tasks 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. | Feature | Owner request, 11 November 2026 | Done | 42 | Data asset management policy A blueprint for modern digital government |
| BL-25 | A chatbot hosted by this portal As a reader, I would like to chat with the guidance. | Feature | Reuse decision | Out of scope | 22 | A roadmap for modern digital government 2025 to 2030 |
MVP assessment against the DAMA wheelO: This playbook's own synthesis of published guidance
The MVP: 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.
Items in the core of the wheel (Data governance, Metadata management, Data quality, the three DAM capabilities) are judged first for the MVP; items in other knowledge areas need a reason tied to the return. Score is the backlog score above; feasibility is its feasibility rating. See the DAMA wheel.
| Item | DAMA knowledge areas | Score | Feasibility | Usability | Verdict and condition |
|---|---|---|---|---|---|
| BL-30 Governance layers and what each may change | Data governance | 70 | Straightforward | One section on the Roles tab and a CSV; uses the 19 role names people already know. | In the MVP Align with the GDS Data Ownership Model before it is promoted; until then it stays labelled as proposed. |
| BL-31 Retention fields in the ownership register and catalogue record | Document and content management Data governance Metadata management | 47 | Straightforward | Adds five fields to the ownership register and two to the catalogue record, which adds burden if made required. | In the MVP, optional Keep the fields optional and out of the return template; agree read-across to records schedules with the government knowledge and information management team. |
| BL-32 Data sharing agreement template and gateways | Data security Data integration and interoperability Data governance | 52 | Some unknowns | A 20-field template for owners and data protection officers, not for every user; reached from the data sharing supplement. | In the MVP as signposts only Have the government data protection team review it before it is promoted; a gateway lookup waits until after the MVP. |
| BL-33 Data architecture and models supplement | Data architecture Data modelling and design | 53 | Straightforward | Useful to architects and design authorities; most owners and coordinators will not need it for the baseline return. | After the MVP 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. |
| BL-34 Health and care obligations from DHSC and MedTech | Data governance Data security Metadata management | 43 | Major unknowns | Signposts sit in the health supplement that health and care bodies already reach from the sector finder. | In the MVP as signposts only Signposts now; complete with the pilot's feedback and an expert review (BL-14) before implementation begins in January 2027. |
| BL-35 Drill down from the DAMA wheel to activities and tasks | Data governance Data architecture Data modelling and design Data storage and operations Data security Data integration and interoperability Document and content management Reference and master data Data warehousing and business intelligence Metadata management Data quality | 42 | Some unknowns | 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. | After the MVP Build the structure with data architecture first (BL-36). Add other areas only when the profession that owns each agrees to own its content. |
| BL-36 Data architecture capability playbook | Data architecture Data modelling and design | 38 | Some unknowns | Useful to architects; owners and coordinators need only the authoritative source question, which is already in the cataloguing guidance and the supplement. | After the MVP Phase 2, from January 2027, once architecture leads agree to own and review it; see the assessment on the DAMA wheel. |
Limits of this assessment:
- 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.
Ideas and voting
Suggest a feature, a page, a fix or a whole new idea. Vote for the ideas you want most. Ideas are public, so everyone can see them and how each one is handled.
Suggest an idea Vote for ideas
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. You need a free GitHub account. If you do not have one, use the private feedback form and we will add your idea for you, without your name.
Most voted ideas
No ideas yet. Be the first to suggest one.
What happens to an idea
- Suggested. Anyone can suggest an idea and anyone can vote.
- Triaged within 2 weeks. We reply, link related ideas and ask questions if we need to.
- Assessed. If it fits the portal's purpose, it becomes a backlog item with a user story and is scored against the six criteria. Votes count towards user demand: 1 or more votes scores 1; 5 or more votes scores 2; 15 or more votes scores 3.
- Placed. Its score suggests Now, Next or Later. Where we decide differently, we say why in the decisions log.
- Closed with a reason. Done ideas link to the release. Ideas we will not do are marked out of scope, with the reason.
How we prioritise
Votes tell us what people want. They are one input, not the decision. Each backlog item is also assessed by the service team for policy, strategy, feasibility, capacity and inclusionO: This playbook's own synthesis of published guidance.
| Criterion | Weight | Question | Scores from 0 to 3 |
|---|---|---|---|
| User demand | 25% | How many people need it, and how strong is the evidence? |
|
| DAM Policy | 20% | Does it help organisations meet the DAM Policy? |
|
| Government strategy | 20% | Does it fit the government's direction for digital and data? |
|
| Feasibility | 15% | Can it be done with what exists, safely and lawfully? |
|
| Capacity and effort | 10% | Does it fit the time and people available? |
|
| Inclusion | 10% | Does it make the portal work for more people? |
|
The score
Score = the sum, for each criterion, of its weight × its score ÷ 3. The result is out of 100.
Example, BL-12 Private research sign-up form: 25 × 3/3 + 20 × 1/3 + 20 × 2/3 + 15 × 3/3 + 10 × 3/3 + 10 × 2/3 = 77.
| Score | Suggests |
|---|---|
| 70 or more | Strong candidate for Now |
| 50 or more | Candidate for Next |
| Under 50 | Later or not yet |
A score suggests a place on the roadmap; it does not decide it. When we place an item differently, for example because it depends on something else, the reason is in the decisions log below. Now holds at most 5 items.
Government strategies we align to
An item scores higher on government strategy when it helps deliver one of these.
- Data asset management policy in governmentV: Verified against the primary source on 2026-11-05
- A roadmap for modern digital government 2025 to 2030V: Verified against the primary source on 2026-11-05
- A blueprint for modern digital governmentV: Verified against the primary source on 2026-11-05
- National Data LibraryV: Verified against the primary source on 2026-11-05
- 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) Not yet published: unconfirmed
The 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). When it is published, it will be added and every item reassessed against it.
Decisions log
| Date | Item | Decision | Why |
|---|---|---|---|
| 2026-11-11 | BL-34 | Health and care obligations stay in Now | 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. |
| 2026-11-11 | BL-33 | Data architecture judged After the MVP even though it is built | 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. |
| 2026-11-05 | BL-05 | Research, roadmap and ideas published in the open | Working in the open lets users see and shape priorities; modelled on the data.gov.uk roadmap. |
| 2026-11-05 | BL-25 | A hosted chatbot is out of scope | No server, nothing sent anywhere; open data and the MCP server serve approved assistants instead. |
| 2026-11-05 | BL-10 | Round 1 waits until Round 0 has recruited for every role | Usability sessions need 5 to 8 people per role, including disabled people. |
| 2026-11-05 | BL-11 | Accessibility sessions wait until Round 0 has recruited assistive technology users | The score says Now, but sessions cannot start without participants; the sign-up form (BL-12) and recruitment (BL-13) come first. |
| 2026-11-05 | BL-18 | Asking questions in your own words stays in Later | 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. |
| 2026-11-05 | BL-23 | Agreed metadata terms stay in Later | 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. |
| 2026-11-05 | BL-18 | Asking questions built without a server | 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. |
| 2026-11-05 | BL-21 | Offline copy built as a download of the whole site | 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. |
What we have learned
Nothing yet: Round 0 is recruiting. After each round we publish what we found, what we changed because of it, and which hypotheses held or failed. Findings name roles, never people.
Was this page useful? Tell us Tell us privately, without GitHub