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

  1. Service manual
  2. Design
  3. Task list pages (beta)

This is a beta pattern that’s still being tested and is likely to change. You don’t have to use it, but we’d like your feedback if you do.

Task list pages let you show users:

  • the tasks involved in completing a transaction
  • the order tasks should be completed in
  • when tasks have been completed

Using patterns in your service

This is a beta pattern, which means it’s been tested in prototypes but needs further research. Unlike other GOV.UK design patterns, you don’t have to use it to pass a service assessment.

Read the guide on using, adapting and creating patterns before you start designing or building anything.

Example of a task list page

task-list-whole.png

See an example task list page in the GOV.UK prototyping kit.

When to use this pattern

Only use a task list page for longer transactions involving multiple tasks that users may need to complete over a number of sessions.

Before using one, try to simplify the transaction. If you’re able to reduce the number of tasks or steps involved, you may not need a task list page.

If you do need one, you must show it:

  • at the start of the transaction
  • after completing each task
  • at the start of each returning session

Show the status of the task

Whenever you show a task list page, make it clear to users which tasks they’ve completed by labelling them ‘Completed’.

task-list-statuses.png

Group things into tasks

Group related activities and questions into tasks (for example, ‘Provide financial evidence’ and ‘Give medical information’). This will help users understand and plan what they need to do.

Where possible, task names should:

  • describe what the task or activity will involve
  • start with verbs (for example, ‘check’, ‘declare’, ‘report’)

Group tasks into sections

If your transaction involves lots of tasks, make it more manageable by splitting it into sections that represent stages in the process.

For example, you could group all tasks which help users find out if your service is right for them in a section called ‘Check before you start’.

Where possible, allow users to complete tasks in any order. This will help them plan their time and complete sections as and when they can.

Research on this pattern

As this is a beta pattern, the design community wants to learn more about the best way to represent:

  • which task to complete next
  • tasks that cannot be completed yet
  • partially completed tasks

If you use this pattern, share your feedback on the design patterns wiki.

Read a blog post about testing and iterating the task list pattern.

You may also find these guides useful:

Published by:
Design community
Last update:

Guidance first published