# Step Indicator and Multi-Step Flow

A step indicator communicates position in a staged task, while the multi-step flow defines the sequence, navigation, validation, and saved state behind it.

- Type: framework
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-10-06
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/step-indicator-and-multi-step-flow/>)

## What it means

A step indicator, sometimes called a progress tracker or stepper, shows completed, current, and upcoming stages in a task spanning several views. It represents a multi-step flow but does not by itself determine whether stages are linear, editable, optional, conditional, or resumable. It is distinct from a numeric stepper that increments a value.

## Why it matters

Long tasks become easier to plan when users understand their current position and what remains. A truthful flow model also helps teams manage validation, back navigation, conditional paths, saving, and recovery consistently.

## When to use it

Use a step indicator for a stable process with several meaningful stages and a flow when splitting the task reduces cognitive or technical load. Avoid exposing a misleading total when branches change substantially, and keep short or freely ordered tasks on one page when that is simpler.

## How it works

1. Map the task into user-meaningful stages rather than implementation screens.
2. Define which stages are required, optional, conditional, revisitable, or locked.
3. Show current position and completed stages in text as well as visually.
4. Preserve entered data, validate at the right boundary, and provide predictable Back and Continue actions.
5. Test branching, errors, refresh, resume, small screens, screen-reader order, and long labels.

## A practical example

A business-account application groups many screens into Company, Owners, Documents, and Review. The indicator says “Step 2 of 4: Owners,” Back preserves valid entries, and an added document question changes content inside Documents without falsely changing the advertised number of stages.

## Where it breaks

A visible sequence can imply certainty when requirements are conditional. Splitting a task creates navigation and state-management overhead, while overly granular stages make progress feel slower rather than clearer.

## Common mistakes

- Treating every screen as a separate user-meaningful step.
- Using the indicator as navigation when stages cannot actually be visited.
- Losing entered data when users move backward or resume later.
- Showing a fixed total that becomes inaccurate after conditional answers.

## Sources

1. [Step indicator](<https://designsystem.digital.gov/components/step-indicator/>) — U.S. Web Design System · Institutional design system
2. [Progress tracker](<https://atlassian.design/components/progress-tracker>) — Atlassian Design System · Institutional design system

## Related topics

- [Progress Indicator](<https://wiki.soroush.uk/topic/progress-indicator/>)
- [Form Validation](<https://wiki.soroush.uk/topic/form-validation/>)
- [User Onboarding](<https://wiki.soroush.uk/topic/user-onboarding/>)
