GovWire

Request a thing

Government Digital Service

September 1
11:34 2022

New publishers must complete training before they can have an account.

If youre the GOV.UK lead or a managing editor in your organisation, you can submit a request to:

  • change an existing account
  • change a users permissions
  • reset 2-step verification (2SV) on a users account (use the Other, give details part of the form for requests about 2SV)
  • become an organisation admin or super organisation admin so you can manage your organisations accounts

You can also remove a user.

Training

If you need a GOV.UK publishing account, you must apply to attend the required training.

Other opportunities to learn

The cross-government content community organises regular opportunities to learn and share knowledge. For example:

  • the large-scale content conference ConCon
  • peer learning programmes
  • online lunch and learn sessions

Find out about these and other learning opportunities on the content community service manual page.

Sign up for the newsletter to get updates and invites. We send emails every 4 to 6 weeks.

Change GOV.UK content

There are different ways to request a change to GOV.UK content depending on whether the content is mainstream or Whitehall.

Its likely to be Whitehall content if:

  • it has government or publication in the URL - for example: www.gov.ukhttps://www.gov.uk/government/organisations/hm-revenue-customs
  • its tagged to the name of a department or agency - for example: From: Foreign, Commonwealth & Development Office

To request a change to Whitehall content, talk to your organisations GOV.UK publishing team.

If it does not have government or publication in the URL, its mainstream and is managed by the content design team at GDS. For example: www.gov.uk/register-to-vote

To request a change to mainstream content, use the GOV.UK content change form. You need a Signon account to access the form. If you need one, ask your departments GOV.UK lead.

For technical issues, or to request a change in functionality, read the guidance on support requests.

What to include in your request

The GOV.UK content team can work on your request faster if you include:

  • a clear title that explains what needs to change - for example, Update phone numbers on Universal Credit guide

  • the section of content that needs to change - for example, Overview chapter, first paragraph

  • the reason for the change - how it helps meet the user need

  • how many users are affected (if you know)

  • the consequence for the user if the change is not made - for example, a user misses out on a benefit theyre entitled to because the eligibility criteria are wrong

  • evidence to support the change - for example, call centre feedback, user research or policy change

  • any deadlines or embargoes, and why - for example, an upcoming policy change or a new service launch

Explain as much as you can in the request itself. Write your request clearly and in plain English. Avoid acronyms, jargon and legal language.

Its fine to suggest wording if it helps to explain whats changed. However, the GOV.UK content team cannot put your copy straight onto GOV.UK, even if its signed off. Theyre responsible for presenting information in a way that users will understand.

What happens next

Youll get a confirmation email with a Zendesk ticket number.

If you need to update the request, follow the link in the confirmation email.

Read about the steps involved in getting something published.

How your request is prioritised

If the change will take less than 20 minutes to make, itll usually be made within a working day. For example, updating a fee or a phone number.

If the request is more complex, your ticket will be prioritised against other tickets. Itll be prioritised according to:

  • any deadlines
  • the impact on the user
  • whether the change is editorial or factual
  • how old the request is

Content advice

You can ask for content advice from the GDS content team. This could be about:

It may be a quick question about content youre working on or a request for a formal response you can share with colleagues in your organisation. Whatever the nature of your request, you need to clearly explain:

  • what you need
  • what your deadline is

This will help us prioritise the work and understand how much detail to give in our response.

Request content advice.

Short URL

Related Articles

Comments

  1. We don't have any comments for this article yet. Why not join in and start a discussion.

Write a Comment

Your name:
Your email:
Comments:

Post my comment

Recent Comments

Follow Us on Twitter

Share This


Enjoyed this? Why not share it with others if you've found it useful by using one of the tools below: