Find out how to decide if something is suitable for GOV.UK, what the content lifecycle is and why accessibility must be planned for.
What to publish on GOV.UK
All content published on GOV.UK must have a clear user need backed up with evidence.
Content should be published either:
- as guidance to help users complete a transaction with government
- to help users understand what government is doing
Content that does not do one of these things should not be published on GOV.UK.
What should not be published
The following types of content should not be published on GOV.UK:
- content that repeats or significantly overlaps with existing content
- advertising for commercial purposes
- intranet or other services exclusively for civil servants
- professional training or qualifications
- information or advice that is not specific to government and can be provided by other organisations or charities, for example housing advice from Shelter or business help from the British Business Bank
- legislation that’s on www.legislation.gov.uk
- information from sites and agencies exempt from transition to GOV.UK
- organisations and companies, like mutuals, that are not publicly owned
- content only relevant to users in devolved parts of the UK (Wales, Scotland and Northern Ireland)
Where to put guidance content on GOV.UK
Guidance is practical information that people need to complete a task or make a decision.
All guidance published on GOV.UK must have a clear user need (backed up with evidence) and be about something the government does (for example issuing passports or driving licences).
Before you create guidance content you must decide whether your users are:
- members of the public (or small businesses) with no specialist skills or experience - ‘mainstream’ users
- specialists who are trained or experienced
Guidance for mainstream users
- is for the general public or small businesses
- is written for users who do not have (and are not expected to have) any previous experience or specialist knowledge of the subject
- guides users from when their need arises to when they complete a task or have the information they need to complete a task (this can include directing users to third-party organisations)
- is organised and written by task, rather than audience or the government department or agency
- explains the current situation - it only describes future changes if they are certain or very likely to happen and affect choices a user can make right now, for example if users should apply for something now because a scheme is closing or a service will be down for maintenance
Volume of users does not necessarily make something suitable or unsuitable for mainstream guidance.
Mainstream guidance must not:
- duplicate content better served by other organisations (for example charities, the NHS, Citizens Advice)
- give advice or offer opinions
Guidance for mainstream users is written and maintained by the content team at GDS.
Send a content request for new content or to make changes to existing content.
Guidance for specialist users
- is aimed at specific audiences who already have an understanding of the topic
- assumes the user has some expert knowledge that will allow them to understand the guidance and take action
- does not promote government initiatives or policies - use the campaigns platform or other channels to support marketing or promotional activity, or use a news story or press release for announcements
- does not explain the policy behind the guidance
Some users want to know the detail of policy, but analysis and research has shown that they’re rarely the same users as those looking for guidance.
The detail of policies should be in a policy paper or one of the other formats that help users understand what government is doing.
Specialist guidance should not duplicate mainstream guidance. It can include a specific part of a mainstream task if it only needs to be done by a small proportion of users. For example, it should not take specialist knowledge to understand National Insurance, but only some users will need to understand National Insurance for share fishermen.
Guidance for specialist users is created by government departments using Whitehall Publisher.
Content that helps users understand what government is doing
You need to make sure you choose the right content type when you create content about what government is doing.
There are over 40 content types on GOV.UK, each of which has been developed for a specific purpose.
To help you choose the right one, you should:
- have a look at your source content and review available content types to choose which format to use
- check how to create and update pages
New government activity or policy: content types to use
These are the relevant formats to use when the government talks about what it’s doing. The following real life examples show how you might meet users’ needs for information about government policy. They’re intended as illustrations.
Top-level introductions to policy
Analysis and research shows there is little audience for top-level introductions to policy compared with task-focused guidance content.
However, sometimes there’s a need to explain government activity in brief, without going into the level of detail that users of the ‘policy paper’ format expect.
The best way to know how to publish this is to explore the user need more closely. How and why will users find this information? It’s bad content design practice to burden users with information that’s irrelevant to what they need right now.
Policy in guidance
Around 80% of page visits on GOV.UK are to guidance to help users complete a task or interaction with government. Most people will not read background text that’s not relevant to the task they’re performing.
Some users want to know the detail of policy, but they are not the same users as people looking for guidance.
Guidance on how to apply for a programme or scheme should not include more than 1 or 2 sentences about what the programme is.
Guidance should not include:
- why it exists (the problem being solved)
- how much money has been allocated to it
- who runs it
- aspirational statements about the intended outcome
These should be in a policy paper or other formats explained in the scenarios in this guidance.
Scenario 1: announcing a new policy or activity
There are a number of formats you can use to tell users about a new policy or activity.
These formats include:
These are sufficient to announce something new until more specific information is available.
An example announcement is Government sets out plans to reshape workplace pensions.
Scenario 2: policy top-level introductions
Use a policy paper to set the context and reasoning behind a policy.
This means you can explain the intentions and research behind a policy separately from information about how it’s being implemented.
Scenario 3: government activity top-level introductions
If this information is brief, you can add it to a relevant corporate information page. For example, use a ‘Petitions and campaigns’ page for policy information about a campaign.
You can alternatively use a policy paper to explain what the government is doing about a particular policy or issue. This might include information about:
- how the government is implementing a policy
- how much money is being spent
You can group a number of related publications for a known audience in a document collection.
This allows users to find all the information about a distinct government activity in 1 place.
Scenario 4: more detail about an aspect of the policy
Detail about the policy should be part of a policy paper.
This could include:
- the outcome the government is trying to achieve
- actions the government is taking to achieve the outcome
- why the government is doing this activity
- the background to this policy
- the budget and timescale for the policy actions
Scenario 5: telling users they may need to do something in the future
To tell users that something is changing and they will need to do it differently in the future, use a news story. This includes new schemes they can apply for or services they will be able to use.
Make sure this news story is user-focused. Make it as short and factual as possible. For example, Transit visa requirements are changing.
Scenario 6: telling users they may need to do something now to prepare for a change in the future
Sometimes a change to a policy, scheme or service will either:
- mean that users need to do something to prepare
- affect a major decision citizens or businesses need to make now
If there’s clear evidence of this, use guidance to tell users about how upcoming changes will affect them now. You may also need to publish a short, factual, user-focused news story to announce the changes.
If the change is to do with EU Exit, follow the guidance on telling users about changes resulting from the UK leaving the EU.
When to communicate future changes
If the change is to do with EU Exit, follow the guidance on telling users about changes resulting from the UK leaving the EU.
Only tell users about changes to schemes or processes if all the following apply:
- it’s certain or very likely that the change will happen
- it affects decisions users are going to make now or very soon
- there’s something different users will need to do (not just “be aware of”)
For example, if a scheme is changing and users might want to apply:
- for a different scheme
Do not publish ‘everything you need to know’ pages for specific audiences as these are never comprehensive and can be hard to navigate.
When to do user research
Do user research when you’re:
- starting a new project
- improving existing content
Use user research to:
- find out what users need
- test assumptions you have about what users need
The resources for user researchers explains the different types of user research and when they’re helpful.
Understanding the content lifecycle
Check the content retention and withdrawal (‘archiving’) policy to see if/when content should be retired. To find out what content exists already, you can export a CSV (comma separated file) by using the ‘Export as CSV’ link at the bottom right of the documents list in Whitehall publisher. You can filter the list before you export it.
We’re still working on this section. Sign up to get an alert when we make changes to the guidance.
GOV.UK content and services need to be as accessible and usable as possible. Government has a legal obligation to make sure people can access the information we produce. This includes users with visual, hearing, cognitive or motor impairments, as well as those with learning difficulties.
When planning content, it’s important to think about:
- how to write for GOV.UK
- choosing the right file format
- making PDFs as accessible as possible
- images and videos
Documents created in open formats can be opened with either free or paid-for software.
This means they:
- can be read and used by more people
- help people to share their work more easily
- make it easier and cheaper to do business with government
The government is committed to publishing documents (including text, presentations, charts and graphs) using open standards. These standards apply to documents designed to be viewed and edited.
They do not apply to datasets that are intended to be machine-readable. If you currently publish data as .csv files, it’s fine to continue doing this.
Documents designed to be viewed
The document ‘viewing’ standards apply to documents that users are meant to read, rather than to edit or interact with.
Documents for ‘viewing’ must be available in one or both of the following formats:
- HTML (the language web pages are built with), for example HTML publications
- a PDF that has been formatted to be accessible and meets the PDF/A standard
Documents designed to be edited
A separate set of formats applies to documents designed to be edited (for example spreadsheets) or used for collaborative working.
This type of document must be published as:
- .odt (OpenDocument Text) for text documents
- .ods (OpenDocument Spreadsheet) for spreadsheets
- .odp (OpenDocument Presentation) for presentation slides
The open standards rules do not cover the publication of datasets designed to be machine readable by external software.
However, if you need to publish structured data like tables or spreadsheets, you should use:
- .ods - an open format that can be used in free, open or proprietary licensed software
- .csv - a machine-readable format which enables users to process the data it contains
Avoid publishing statistical tables or datasets within a PDF or other format designed mainly for text. This is because it makes it difficult for visually impaired users who rely on screen readers. Instead, try to provide them separately using .ods or .csv.
GOV.UK URLs (web addresses) are designed to follow a consistent, predictable, user-friendly format.
Most URLs are generated automatically when a page is created in Whitehall Publisher. However, short or ‘friendly’ URLs are sometimes created for promotional purposes. If you need a short URL, you need to: