Everything on this page runs on GitHub: votes are 👍 reactions, suggestions and messages are GitHub issue forms that open already filled in. You need a free GitHub account to vote or send; if you don't have one, ask a colleague.
The stages below come from the backlog. For the scores behind each priority, delivery objectives, government strategy and capacity, see the open roadmap and priorities. To help decide what comes next, take part in user research.
Every item is also a GitHub issue labelled backlog, so you can comment, follow or pick it up. Priority uses MoSCoW: must, should, could, won't (this time).
| Item | Priority | Area | Status | Why it matters |
|---|
Vote for the features you need most by giving the wish a 👍 on GitHub. Votes help set the order of the backlog, and you can change them at any time.
Every method has an alternative: if a live session doesn't suit you, use the asynchronous route or the contact form. We provide captions, transcripts and materials in advance.
| Method | When | How |
|---|
Live sessions rotate between three times, so no region always gets the early or late slot. Pick the partners taking part to see each slot in their local time. Times in grey fall outside 8am to 7pm local time; the asynchronous route is always open.
Read the full charter, code of conduct and contributing guide on GitHub.
The Commons checks itself. These routines run automatically or on a schedule; "planned" ones are on the backlog.
| Routine | What it does | When | Status |
|---|
Where another body keeps the authoritative version, the Commons links to it rather than keeping its own copy.
| What | Authoritative source | Used on |
|---|
| Where | Kind | What it is | How you can tell |
|---|
The provenance audit runs on every change: if anything that looks like an example appears without being registered here, the build fails. Spotted something that looks invented? Tell us.
See the contributors list. Credit is by GitHub username or organisation, never personal details.
The same notes are in CHANGELOG.md, and each release is tagged in Git. Open from any page.
Every product, architecture and delivery document for this version in one standalone page: product requirements, theory of change, user research, architecture (solution, high-level and low-level design), functional, technical and integration requirements, build manifest, README, change log, decisions and build log.
Open the bundle (repository copy)
The bundle is generated from the repository's docs by scripts/build_bundle.py, so it always matches the build.
Choose the route that suits you. None of them asks for your name or email, and we never show an email address.
Download the questions as a Word document (for Microsoft Forms' Quick import, where your organisation allows it).
Send us a message through this form. It is the only way to contact the team: we never publish an email address, which keeps spam and impersonation down, and you never need to give yours. The form opens a pre-filled GitHub contact issue (a free GitHub account is needed; if you don't have one, ask a colleague) and we reply there.
See contact issues and our replies on GitHub.
Security problem? Report it privately through GitHub's vulnerability reporting, not here.