Check a service is suitable
Ask users questions to help them work out if they can or should use your service.
Doing this helps users save time as it tells them upfront whether they are eligible to use it and if they need it.
It can also help reduce time and money spent processing queries from users confused about whether they’re eligible to use your service, or if it’s suitable for them.
See a complete example of check a service is suitable
When to use this pattern
If you have complicated eligibility requirements you should follow this pattern. This will save users from having to read through large amounts of documentation outside of your service to work out if they can use it.
Use this pattern to help users work out:
- if they’re eligible to use your service
- how much it will cost them to use
- how much money they will get
- how long it will take to get something
Read guidance about designing your service so you give users information at the point they need it in the Service Manual.
When not to use this pattern
Don’t use this pattern if you can reasonably include information users need to know about your service and its eligibility requirements on a start page.
How it works
You should help people find out whether your service is right for them as soon as you can.
When using this pattern you need to:
- ask a series of simple questions
- automatically work out what a user needs to know
- present the user with a ‘results’ page
If there are general rules about whether a service can or can’t be used such as an age limit or fixed deadline, include these on the start page.
Your results page should show the user if they’re eligible to use it. Where applicable, it should also show them:
- if they have to use your service
- how much it will cost them to use it
- how much money they’ll get from using it
- how long the whole process will take
If a user isn’t eligible to use your service, explain why and, if possible, tell them what they should do instead.
Here’s an example of a results page:
Research on this pattern
Read a blog post about testing and iterating this pattern.
Please note this pattern used to be called ‘Check before you start’.
Get in touch
If you’ve got a question, idea or suggestion share it in #govuk-design-system on cross-government Slack (open in app) or email the Design System team on email@example.com