Beta This is new guidance. Complete our quick 5-question survey to help us improve it.

  1. Service manual
  2. Technology
  3. Using common components

You should use common components to make it easy to build user-centred government services.

Why you should use common components

Using common government components makes it easy to build user-centred services because you don’t have to invent your own solution to problems. For example, instead of each service team getting a payment provider, we’ve created one payment product that can be used by everyone.

Right now there are 5 components. These will be supported in the future, updated and expanded using research about what works for government users.

GOV.UK Notify

GOV.UK Notify is a product to keep users updated by helping government service teams to send text messages, emails or letters.

Find out more about GOV.UK Notify.

GOV.UK Verify

GOV.UK Verify is a platform for identity assurance, so that individual users can access digital government services securely by proving who they are.

Find out more about GOV.UK Verify.

GOV.UK Pay

GOV.UK Pay is a product that allows users to make payments to government in the same way, regardless of what service they’re using. Whether they’re applying for a passport or renewing a licence, they’ll be using the same payment process.

GOV.UK Pay allows service teams to manage payments, including things like reconciliation and refunds.

Find out more about GOV.UK Pay.

Platform as a Service for government (PaaS)

Platform as a Service for government (PaaS) is cloud hosting that makes it easier and cheaper for teams across government to host applications, services and components.

PaaS provides all the infrastructure you need for hosting services. This means individual teams don’t have to build and manage their own infrastructure..

Find out more about Platform as a Service for government.

Registers

Registers are lists of information, and each register is the most reliable list of its kind. Each register is managed by a single person, known as a ‘custodian’, who is responsible for keeping it up to date and accurate.

Other lists or datasets might not be properly looked after. Using these to build your service could mean you’re using data that’s incomplete or out of date.

Find out more about registers.

Published by:
Design community
Last update:

Guidance first published