Skip to main content
Design and build of government services

Guidance and regulation

Skip to results
48 results sorted by Most viewed
  • We want everyone to be able to do what they need to do with our websites and services, regardless of their access needs, due to a disability or condition.

  • Avoid duplicating effort and unnecessary costs by collaborating across government and sharing and reusing technology, data, and services.

  • Guidance to help you assess if artificial intelligence (AI) is the right technology for your challenge.

  • Use this guidance and the templates when you write Department for Work and Pensions (DWP) research reports.

  • Checking your website's accessibility if you cannot pay for an audit and do not have an expert in your organisation.

  • This page collates the various existing ethical principles for data and AI, developed by government and public sector sector bodies. It intends to provide clarity and guidance for public servants working with data and/or AI.

  • Lessons learnt from the 'Secure by Design' approach adopted by MOD which ensures security is designed into any project delivering capabilities or services.

  • All digital services and technical infrastructure must be built to comply with the Government Cyber Security Standard

  • Information about how to contact the Government Digital Service (GDS) to request or report something.

  • Understand how to manage a project which uses artificial intelligence.

  • Reduce development overhead and time to deployment by standardising how teams design, launch and manage APIs in your organisation.

  • How government organisations can work with the Government Digital Service (GDS) to close government websites and move content to GOV.UK.

  • All public facing services must use a GOV.UK domain, or another public sector domain in line with the GOV.UK Proposition, and use the GOV.UK Design System.

  • All government services must use the functionality of mandated central services: GOV.UK Notify and GOV.UK Pay.

  • An introduction to understanding and using artificial intelligence in the public sector.

    First published during the 2016 to 2019 May Conservative government

  • You must have a legacy-proofing plan for all digital products and services to prevent the build up of technical debt and future legacy

  • How you can test and manage your API when it is in alpha development.

  • A set of principles to maintain and make changes to the GOV.UK topic taxonomy

  • This guidance covers how to run your API as a service, including building the team you will need and the lifecycle of your API

  • If a supplier has a contract for service provision, it must not also do the service integration for that service