# Progress rails: layouts that mirror the sequence of work, not its categories

> A progress rail is the shape that emerges when a sequential job gets the interface it needs. Not a wizard, not a stepper, not tabs — something closer to a spatial map of the work already done and the work still ahead.

Source: https://www.thedesignagent.ai/field-notes/progress-rails · Patterns · 2026-05-06

The tab problem has a positive answer. When a sequential job gets a tabbed layout — categories imposed on a workflow that needs to move in one direction — the fix isn't just "remove the tabs." It's to replace them with something that mirrors what the job actually is: a sequence with a beginning, a current position, and an end.

That shape is a progress rail. Not a wizard that hides previous steps. Not a stepper that asks for navigation decisions at each transition. Something closer to a spatial map: here's where you've been, here's where you are, here's what's ahead.

## Anatomy of a rail

A well-built progress rail has a specific structure. The steps are visible simultaneously — the user can see the full sequence at a glance. But they're not equal: the current step gets the primary working area of the screen, and the others are rendered smaller, in the rail itself, as spatial context rather than navigation targets.

Completed steps show completion state and are accessible if the user needs to reference or revise them. They don't disappear. Upcoming steps are visible but not interactive until they're unlocked by completing the current one. The rail communicates progress through position — the user knows where they are in the sequence by looking at the rail, not by reading a step counter or a breadcrumb.

Status is implicit. The warehouse operator who's at the Pack step doesn't need a status badge that says "In Progress." They're at Pack. That's the status.

> **Pattern:** a progress rail mirrors the job's sequence. The current step gets the screen. Completed steps provide spatial memory. Upcoming steps set expectation. Navigation is through completion, not clicking.

## How it differs from tabs

Tabs and rails look similar at a glance — both show multiple labeled sections. The difference is behavioral and cognitive.

Tabs are for non-sequential browsing. The user can jump between them in any order; none implies a path through the others. The right tab for inventory status doesn't follow from the left tab for purchase orders. Tabs work when the sections are genuinely parallel — multiple views of related data with no prescribed sequence.

Rails are for sequential progress. The user moves through them in order because the work requires it. You can't pack before you pick; you can't ship before you pack. The rail enforces this and makes it visible. Trying to use tabs for a sequential job breaks the spatial relationship between layout and work — the operator has to mentally reconstruct the sequence the tabs took apart.

## How it differs from a wizard

Wizards are multi-step forms for one-time or infrequent tasks. They're linear and typically hide completed steps to reduce visual complexity. The model is "we're going to collect a lot of information across several screens, and you only need to focus on the current screen."

Rails are for operational workflows that repeat. An operator fulfills many orders per shift. A planner processes many recommendations per week. The rail is part of the working surface, not a temporary guide through a setup process. Completed steps remain visible because the operator may need to reference what they packed before confirming shipment. The spatial context of the full sequence is load-reducing, not load-adding, because the job is familiar.

## When to use it

Progress rails fit jobs that are sequential (steps must happen in order), repeated (the same workflow runs multiple times per session), and referential (the user benefits from seeing earlier steps while at a later one).

Order fulfillment. Expense approvals with a multi-stage review. Customer onboarding flows for account managers. Manufacturing quality checks. Claims processing. The domain varies; the job shape is the same — a fixed sequence of steps, each of which passes context to the next.

## How TheDesignAgent patches to it

When the `/ux` lens identifies a tab layout applied to a sequential job, the patch names the swap directly: "replace tabbed navigation with progress rail; steps: [extracted from the workflow]; current step gets full working area; completed steps accessible in rail." The agent gets the step names, the navigation model, and the layout prescription in one patch.

The score delta on `jtbd_alignment` is typically large when this patch is applied — sequential job on a tab layout is one of the highest-scoring mismatches the system identifies. The complementary score, `extraneous_load`, also improves: the cognitive cost of mentally stitching the split-screen-across-tabs job back together is eliminated.
