You don't need to install anything or know how to code. Data you check stays in your browser. This guide covers the basics, every page, guided tours and common questions.
Each part of the menu has its own colour: Start teal, Learn purple, Check blue, Improve orange, Apply green and Contribute pink. The colour is used on the menu, the label above each page title and the previous and next links. Sections on a page take turns with other colours, matched in the On this page list. Colour is always backed up by words, so you never need to see colour to use the Commons.
The site map shows every page on one screen, by part and level, with suggested routes for common tasks.
Columns are sized to what they hold: short codes stay narrow and long descriptions get more room. Rows are lightly striped. On large screens wide tables use the space beside the page. If a table is still wider than the screen, a shadow shows at its edge and a note tells you to scroll sideways. Long tables keep their headings in view.
Acronyms have a dotted underline the first time they appear on a page: hover over or tap one to see what it means. Buttons that only show an icon explain themselves when you hover over or tab to them. Press Escape to close a tooltip.
A thin bar under the top menu shows how far down the page you are. Top (bottom right) takes you back to the start. The end of every page links to the previous and next page in menu order.
Share this page sits under every page title. Ask the Commons answers questions from across the portal. Use the Commons your way explains embedding, the open data API, white-label copies, AI assistants and connectors.
Select Aa in the top bar to change the text size (up to 150%), widen line, letter and word spacing, switch to an easier-to-read font, choose light, dark or high contrast colours, reduce movement, and show or hide source labels. Your choices stay in this browser and apply to every page.
Every link to an outside source is followed by a small label saying what kind of source it is, so you can judge how far to rely on it:
The Commons' own judgements, such as mappings between frameworks or scores on the roadmap, are labelled in the text as the Commons' view. Facts marked verified have been checked at source by a person; a quarterly sample re-checks 5% of them.
Each link opens the page and starts its tour. Tours move focus to a small panel next to the part being explained. Use Next and Back, or the arrow keys, and Escape to stop.
Short tutorials for common jobs. Each one ends with a link that opens the page with its guided tour.
Go to Check your data. Open a CSV file or choose an example. Add rules from the rule builder, or start from the rule library: person, address, organisation, geography and publication templates. Press Run the checks.
Identifier checks test the format and, where there is one, the check digit: NHS number, National Insurance number, postcode, UPRN, GSS code, Companies House number, charity number, school URN, ODS code and LEI.
Open the standards catalogue. Search by name or filter by domain and status. Each row links to the specification, the GOV.UK list, its Rosetta concepts, Weaver support and where it is used in public code.
In the Metadata Weaver, paste a record and open the DQV (metadata quality) tab. Publish the result next to your DCAT record.
Open Three portals, one journey. Compare the portals, choose a box on the lineage map, or trace a DAMA area, role or standard through all three.
Go to Frameworks and standards. Filter by nation, sector or type. Open a framework to see its dimensions and how they map. The clause table breaks policies down line by line, with devolved and international comparisons and known gaps.
Go to Maturity self-assessment. For each of 8 themes, choose the statement that fits best. You'll get a level per theme and next steps. Your answers stay in your browser.
Use the calculator on Issues framework. Enter how important the purpose is and how bad the impact would be. It gives the target, the priority band and how quickly to fix.
Open the data management wheel. Choose your role, then an area of the wheel, to see what it means for you, what to do for the DAM policy, where it shows up in maturity, and how records and information management fits in. If you have done the maturity self-assessment, tick Colour by my maturity results. Tick the join-up actions you will take and download your plan.
On For your role, pick your change role (for example SRO, delivery manager, business analyst, architect, migration lead or records manager). Use the lifecycle and gate questions at each assurance review, the RACI to agree who does what, and the service blueprint to plan the data and records work behind each phase.
Every page ends with a feedback link. Choose the Microsoft Form (no sign-in, no names), the GitHub contact form, a survey, or the accessibility route. All routes are on Help us build this.
Read AI for data quality, then try the rules assistant, which runs in your browser with no AI service. Always review what it drafts: the page tests every draft against the kit before showing it.
Use Community for the contributions library and wishlist, and Surveys and commissions to take or run a survey or request help. If saving isn't available where you opened the portal, each form links to a GitHub form instead.
See Operating model and Pipeline status. The GitHub Actions pipeline measures every asset, keeps history, opens escalation issues and rebuilds this portal.
No. It's a prototype public good service. It links to official sources first and marks anything not yet verified.
No. Checks run in your browser. Only things you choose to submit (a contribution, a survey answer, a request) are saved, and those never include your name or email unless you add a contact detail.
No. Those are two of the scenarios. The toolkit works for any data, and the Scenarios page covers statistics, health, local government, geospatial, personal data, AI and more.
Yes. Rules are plain YAML and results are W3C DQV, CSV and JSON. See Tooling for routes into Great Expectations, R validate, Purview, Fabric and others, and the MCP server for AI agents.
See the support tiers on Operating model. Accessibility problems are answered within 1 working day.
We aim to meet WCAG 2.2 AA. The portal works with a keyboard alone, screen readers, voice control and zoom up to 400%, follows your light or dark setting and respects reduced motion. Charts always have a table or text alternative.
Known gaps: the portal hasn't yet had an independent audit (planned, XDMH-213), and there is no Welsh version yet (XDMH-216). Tell us about anything that doesn't work for you through Surveys and commissions or the service desk.