# Task List

A task list helps users plan and resume a long service by showing its meaningful tasks and the status of each one.

- Type: artifact
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-10-07
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/task-list/>)

## What it means

A task list is an interface for a multi-part service in which users can see, choose, and track distinct tasks, often across sessions. Each item combines a clear task name with a status and optional guidance; it differs from a step indicator because completion order may be flexible rather than a fixed linear sequence.

## Why it matters

Long applications and setup processes are easier to understand when users can see their workload, dependencies, and progress at a meaningful level. A task list can support planning and return visits without exposing every page as an intimidating checklist.

## When to use it

Use a task list when evidence shows that a service contains distinct tasks, may span sessions, or allows users to choose their completion order. Prefer a simpler linear flow when work is brief or strictly sequential, and simplify the service before adding progress machinery.

## How it works

1. Model the service as user-meaningful tasks rather than individual screens or backend stages.
2. Group related tasks and write short action-oriented names that set accurate expectations.
3. Define a small, consistent set of statuses and explain blocked or unavailable work.
4. Link each row to the place where the task can be started or resumed while preserving completed work.
5. Update status from reliable completion rules and state what remains before final submission.

## A practical example

A licensing service lets applicants complete business details, upload evidence, nominate staff, and pay in any order over several days. The task list distinguishes Not started, In progress, and Completed and explains why submission remains unavailable.

## Where it breaks

A task list adds navigation and status complexity and can make a simple journey look larger. It depends on reliable saved state, and it does not suit work whose steps must be completed in one strict sequence.

## Common mistakes

- Turning every form page into a separate task rather than modeling meaningful work.
- Adding a task list before attempting to shorten or simplify the service.
- Using color alone for status or leaving status terms undefined.
- Showing tasks as selectable when dependencies prevent users from acting on them.

## Sources

1. [Task list](<https://design-system.service.gov.uk/components/task-list/>) — GOV.UK Design System · Institutional design system
2. [Complete multiple tasks](<https://design-system.service.gov.uk/patterns/complete-multiple-tasks/>) — GOV.UK Design System · Institutional design pattern

## Related topics

- [Step Indicator and Multi-Step Flow](<https://wiki.soroush.uk/topic/step-indicator-and-multi-step-flow/>)
- [Progress Indicator](<https://wiki.soroush.uk/topic/progress-indicator/>)
- [Form Design](<https://wiki.soroush.uk/topic/form-design/>)
