Mainstream content publishing process
Updated 13 June 2017
漏 Crown copyright 2017
This publication is licensed under the terms of the Open Government Licence v3.0 except where otherwise stated. To view this licence, visit or write to the Information Policy Team, 皇冠体育app National Archives, Kew, London TW9 4DU, or email: [email protected].
Where we have identified any third party copyright information you will need to obtain permission from the copyright holders concerned.
This publication is available at /government/publications/how-content-requests-from-government-get-published/mainstream-content-publishing-process
皇冠体育appse steps describe what happens when a government department or agency sends GDS a request to change content on GOV.UK. 皇冠体育app steps show the process when everything goes smoothly.
1. 皇冠体育app need for a change is identified
Department/agency: Someone makes an internal request for a change to mainstream content.
Department/agency: 皇冠体育app request is prioritised against other outstanding content requests.
GDS: Respond to requests for advice, if any.
2. 皇冠体育app request gets drafted
Department/agency: A formal content change request is drafted for GDS by the department鈥檚 content designer.
GDS: Respond to requests for advice, if any.
Department/agency: 皇冠体育app content request form is filled in and sent.
GDS: 皇冠体育app content request arrives as a ticket. An automated receipt is sent back.
3. Triage
Department/agency: Answers GDS鈥檚 questions about the content request, if any.
GDS: 皇冠体育app ticket is triaged by a member of the GDS content team on the content requests rota.
4. GDS second line support
4.1 Quick fixes (quicker than 20 minutes)
Department/agency: Answers GDS鈥檚 questions, if any.
GDS: Request assessed and resolved by the second line content support team.
GDS: Content is sent to internal review.
4.2 Complex requests (things that take more than 20 minutes)
GDS: 皇冠体育app ticket is moved to third line support, and a task is created in the relevant content team鈥檚 triage board to be prioritised.
5. GDS third line support
GDS: 皇冠体育app content team leads look out for incoming content requests, and prioritise them.
Department/agency: 皇冠体育app department鈥檚 content lead helps the GDS team lead to prioritise tickets, when needed.
GDS: 皇冠体育app team lead moves the content request from their triage board to their work in progress board when it is the next most important thing to work on.
GDS: A GDS content designer starts work on the content request.
GDS: 皇冠体育app content request is discussed with another GDS content designer and new content is drafted.
Department/agency: Answers GDS鈥檚 questions, if any.
6. Internal review
GDS: 皇冠体育app draft is reviewed internally by an experienced content designer who hasn鈥檛 been involved in the work.
7. Fact check review (optional)
7.1 When facts need to be checked
GDS: 皇冠体育app new and reviewed content is sent to the department to check for factual accuracy.
Department/agency: 皇冠体育app publisher sends the new content to their subject matter experts.
Department/agency: 皇冠体育app feedback from the subject matter experts is collated and sent back to GDS.
GDS: 皇冠体育app fact check feedback is reviewed by the team lead.
When factual changes are necessary
GDS: 皇冠体育app factual amendments are incorporated into the new content.
GDS: 皇冠体育app updated content is sent to be reviewed internally.
If no factual changes are necessary
GDS: 皇冠体育app content is sent for publishing.
8. Publish
GDS: 皇冠体育app new content is published on GOV.UK.
GDS: 皇冠体育app original content request ticket is marked 鈥榬esolved鈥�.
Department/agency: 皇冠体育app department鈥檚 content designer tells the subject matter expert the content has been published.