4.2.5 Check a users eligibility

Use this pattern to help users check if they qualify for your service saving them time registering for a service they would not qualify for and redirecting them where possible.

Asking for eligibility flow diagram

How it works

To use this pattern you need to have:

• A service information sheet

• A series of simple eligibility questions

• An understanding of what existing data you can integrate with

Service information sheet

Have a web page for your service where people can find the required information about the service. Such as requirements to access the service, actions and steps they need to start using your service. Check an example of a service information sheet.

Ensure to include general rules and information about whether the service can be used such as age limit.

A series of simple eligibility questions

Present the user with a series of simple questions that can determine their eligibility. Use questions when the eligibility criteria for the service is complex and require detailed information to determine if a user qualifies.

Ask the user to provide information such as their age, location, employment status, income level, or other relevant details to your service. Follow the question page pattern.

Automatically check if a user is eligible

the system should automatically process the information provided and determine whether the user is eligible to access the feature or service.

An outcome page

• Eligibility outcome that clearly states whether the user is eligible or ineligible to access the service or feature.

• Reason for eligibility determination such as a clear explanation if the user is found to be ineligible. This can include information such as incomplete or incorrect information provided in the form, not meeting certain age or income requirements, or other criteria.

• Next steps depending on the outcome of the eligibility check. For example, if the user is found to be eligible, direct them to the next step which may be to register for the service. If they are found to be ineligible, direct them to another service or further guidance.

Here are some elements that can be included on the outcome page:

Present an outcome page to users to let them know the result of their eligibility check. The outcome page should provide a clear and concise summary of the user's eligibility status. If eligible, you should let the user know of the next steps to access the service. If the user is not eligible, let them know why and what they should do instead.

• Eligibility outcome that clearly states whether the user is eligible or ineligible to access the service or feature.

• Reason for eligibility determination such as a clear explanation if the user is found to be ineligible. This can include information such as incomplete or incorrect information provided in the form, not meeting certain age or income requirements, or other criteria.

• Next steps depending on the outcome of the eligibility check. For example, if the user is found to be eligible, direct them to the next step which may be to register for the service. If they are found to be ineligible, direct them to another service or further guidance.

When to use this pattern

Services where eligibility criteria can be complex and may vary depending on the specific service or feature being accessed. By using the "check eligibility" pattern, users can quickly and easily determine whether they qualify for a particular service, without having to go through a lengthy application process or wait for manual approval.