Data display

Work queue

<forma-work-queue>

Attention-first list of unresolved work with reason, context, and application-supplied legal actions.

Authoring tag
<forma-work-queue>
Category
Data display
Behavior owner
Ordo / application
Canonical source
patterns/work-queue.html

Purpose

A work queue is a bordered section with a header (title and item count) and an ordered list of items that need a person's attention. Each item states what needs attention, why, and relevant context such as age, due date or evidence status, next to the one action the application says is currently legal. Forma lays this out and stacks it on phones. It never decides what is in the queue, in what order, whether work is blocking or resolved, or which actions are allowed; that comes from Ordo or the application.

Use when

  • A person must resolve a set of items, and each item has a reason and a next action.
  • The order is meaningful (priority or due date) and set by the application.
  • Unknown or reconciling outcomes need follow-up and must not be shown as failures.

Avoid when

  • Items are records to browse, sort and filter: use Data grid.
  • Items are a stream of events with optional actions: use Feed item.
  • Items are obligations tied to a record's legal transitions: use Obligation panel.
  • Prerequisites must all be met before one transition: use Readiness checklist.

Behavior to know

  • Header row: title (with an optional kicker) at the start, count at the end; stacks at 30rem and below.
  • Each item is a minmax(0, 1fr) auto grid: reason and context on the start side, the action on the end side.
  • Items are separated by subtle rules; the last item has none.
  • At 40rem and below each item becomes one column and its button stretches to full width.

Basic example

The smallest correct markup: the canonical pattern from patterns/work-queue.html inside its public tag. Copy this first, then adapt labels, names and state.

Canonical

Minimal work queue

Rendered from the canonical pattern file.

Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.

Attention

Needs your attention

3 items
  1. Invoice INV-1042 is overdue

    32 days overdue · Customer follow-up is available.

  2. Write outcome is unknown

    Reconcile before retrying or assuming failure.

  3. Publication validation has warnings

    2 warnings require review before publishing.

HTML · Minimal work queue Raw HTML for HTML · Minimal work queue
<forma-work-queue class="forma-component-tag">
<section class="forma-work-queue" aria-labelledby="work-queue-title">
  <header class="forma-work-queue__header">
    <div><span class="forma-component-kicker">Attention</span><h3 id="work-queue-title">Needs your attention</h3></div>
    <span class="forma-status-lozenge">3 items</span>
  </header>
  <ol class="forma-work-queue__list">
    <li class="forma-work-queue__item">
      <div><strong>Invoice INV-1042 is overdue</strong><p>32 days overdue · Customer follow-up is available.</p></div>
      <button type="button">Review</button>
    </li>
    <li class="forma-work-queue__item">
      <div><strong>Write outcome is unknown</strong><p>Reconcile before retrying or assuming failure.</p></div>
      <button type="button">Reconcile</button>
    </li>
    <li class="forma-work-queue__item">
      <div><strong>Publication validation has warnings</strong><p>2 warnings require review before publishing.</p></div>
      <button type="button">Inspect</button>
    </li>
  </ol>
</section>
</forma-work-queue>

Click or tap the code once to select all of it, then copy.

Examples

Scenario

Overdue, unknown and blocked work

Three items with different application states, each written as text with a Status lozenge. The unknown write outcome asks for reconciliation rather than a retry, and the blocked item's action is to view the blocker because nothing else is legal.

Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.

Finance operations

Needs your attention

3 items
  1. Invoice INV-1042 is 32 days overdue

    Overdue Due 28 Aug · Customer follow-up is available.

  2. Payment PAY-88122 outcome is unknown

    Unknown The bank accepted the request but has not confirmed. Reconcile before retrying.

  3. Quarter close cannot start

    Blocked Waiting on 2 unreconciled accounts owned by Treasury.

HTML · Overdue, unknown and blocked work Raw HTML for HTML · Overdue, unknown and blocked work
<forma-work-queue class="forma-component-tag">
  <section class="forma-work-queue" aria-labelledby="work-queue-mixed-states-title">
    <header class="forma-work-queue__header">
      <div><span class="forma-component-kicker">Finance operations</span><h3 id="work-queue-mixed-states-title">Needs your attention</h3></div>
      <span class="forma-status-lozenge">3 items</span>
    </header>
    <ol class="forma-work-queue__list">
      <li class="forma-work-queue__item">
        <div><strong>Invoice INV-1042 is 32 days overdue</strong><p><span class="forma-status-lozenge" data-state="attention">Overdue</span> Due 28 Aug · Customer follow-up is available.</p></div>
        <button type="button" aria-label="Review INV-1042">Review</button>
      </li>
      <li class="forma-work-queue__item">
        <div><strong>Payment PAY-88122 outcome is unknown</strong><p><span class="forma-status-lozenge" data-state="unknown">Unknown</span> The bank accepted the request but has not confirmed. Reconcile before retrying.</p></div>
        <button type="button" aria-label="Reconcile PAY-88122">Reconcile</button>
      </li>
      <li class="forma-work-queue__item">
        <div><strong>Quarter close cannot start</strong><p><span class="forma-status-lozenge" data-state="blocked">Blocked</span> Waiting on 2 unreconciled accounts owned by Treasury.</p></div>
        <button type="button" aria-label="View blockers for quarter close">View blockers</button>
      </li>
    </ol>
  </section>
</forma-work-queue>

Click or tap the code once to select all of it, then copy.

Scenario

Queue cleared

Nothing needs attention. The section stays in place with a 0 count and an explanation, instead of disappearing, so users can tell an empty queue from one that failed to load.

Needs your attention

0 items
  1. Nothing needs your attention

    Checked at 09:40 UTC. New items appear here when they are assigned to you.

HTML · Queue cleared Raw HTML for HTML · Queue cleared
<forma-work-queue class="forma-component-tag">
  <section class="forma-work-queue" aria-labelledby="work-queue-empty-queue-title">
    <header class="forma-work-queue__header">
      <div><h3 id="work-queue-empty-queue-title">Needs your attention</h3></div>
      <span class="forma-status-lozenge" data-state="ok">0 items</span>
    </header>
    <ol class="forma-work-queue__list">
      <li class="forma-work-queue__item">
        <div><strong>Nothing needs your attention</strong><p>Checked at 09:40 UTC. New items appear here when they are assigned to you.</p></div>
      </li>
    </ol>
  </section>
</forma-work-queue>

Click or tap the code once to select all of it, then copy.

Mobile

Each mobile example renders in its own document inside a real narrow viewport, so Forma's media and container queries run exactly as they would on a phone. Choose a width to compare.

Mobile example

Mobile work queue

Two items at phone width. Each item stacks its reason above a full-width action, and the header stacks the count under the title.

Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.

Viewport width

Frames narrower than the selected width show the component at the width available.

What changes at narrow widths

  • At 40rem (640px) and below each item becomes a single column and its button stretches to 100% width, giving a full-width touch target.
  • At 30rem (480px) and below the header becomes a grid, so the count sits under the title instead of competing for width.
  • The application's order is kept exactly; nothing is reordered for mobile.
  • Long reasons and context wrap within the item; nothing scrolls horizontally at 320px.
HTML · Mobile work queue Raw HTML for HTML · Mobile work queue
<forma-work-queue class="forma-component-tag">
  <section class="forma-work-queue" aria-labelledby="work-queue-mobile-queue-title">
    <header class="forma-work-queue__header">
      <div><span class="forma-component-kicker">Releases</span><h3 id="work-queue-mobile-queue-title">Awaiting your review</h3></div>
      <span class="forma-status-lozenge">2 items</span>
    </header>
    <ol class="forma-work-queue__list">
      <li class="forma-work-queue__item">
        <div><strong>rel-2026.09.29 needs production approval</strong><p>Requested 3 hours ago by the release manager.</p></div>
        <button type="button" aria-label="Review rel-2026.09.29">Review</button>
      </li>
      <li class="forma-work-queue__item">
        <div><strong>Publication validation has warnings</strong><p>2 warnings must be acknowledged before publishing.</p></div>
        <button type="button" aria-label="Inspect publication warnings">Inspect</button>
      </li>
    </ol>
  </section>
</forma-work-queue>

Click or tap the code once to select all of it, then copy.

Baseline

Mobile · 320px

The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.

Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.

Viewport width

Frames narrower than the selected width show the component at the width available.

API and configuration

Forma components have no JavaScript API. Their public contract is the markup: native elements and attributes you write, and the CSS hooks below. The CSS hook table is generated from the built stylesheet, so it always matches the shipped implementation.

Native and ARIA attributes
AttributeOnValuesDefaultDescription
aria-labelledbysection.forma-work-queueid of the header heading—Names the queue region.
aria-labelitem buttonstring—Names the item an action applies to when the visible verb repeats across items.
typebuttonbutton—Actions are native buttons handled by the application.
CSS hooks (derived from dist/all.css)
HookKindValues or defaultDescription
.forma-work-queueBlock class—Bordered root section.
.forma-work-queue__headerElement class—Padded, ruled header row with title and count spaced apart; a grid at 30rem and below.
.forma-work-queue__itemElement class—One item: reason/context and action in a two-column grid, stacking at 40rem and below with a full-width button.
.forma-work-queue__listElement class—The unstyled ordered list of items.
Keyboard interaction
KeysResult
Tab / Shift+TabMoves through each item's action button in queue order.
Enter / SpaceActivates the focused action (native button).
Events
EventDescription
clickNative click on an item action. The application re-validates legality, performs or opens the action, and updates the queue.

Form behavior

Not a form control.

States

Work queue states
StateHow it is expressedPresentation
Item needing actionli.forma-work-queue__item with a buttonReason, context and the legal next action.
Item stateStatus lozenge or text in the itemOverdue, Unknown, Blocked and so on, supplied by the application.
Emptyapplication-rendered messageThe queue explains that nothing needs attention and when it was checked.
Stackedviewport ≤ 40remItems single column with full-width actions; header stacks at 30rem.

Accessibility

Forma provides

  • Uses an ordered list so position and count are announced.
  • Keeps reason before action in DOM order at every width.
  • Stretches actions to full width on phones for large touch targets.

Your application supplies

  • Order items by the application's attention rules; do not rely on visual position to imply priority beyond that order.
  • Write why attention is needed and the state as text; unknown must not read as failure.
  • Render only actions that are legal now, and re-check legality when the action is activated.
  • Give repeated action buttons record-specific accessible names.
  • After an item is resolved, move focus to the next item or the header and update the count.

Responsive behavior

  • Above 40rem: reason and action side by side.
  • At 40rem and below: items stack and buttons fill the width.
  • At 30rem and below: the header stacks title and count.
  • Text wraps inside items; the start column is minmax(0, 1fr).

Motion

  • No animation: items are added and removed by the application without transitions.

Usage guidance

Do

  • Lead each item with the outcome needed, not the record type.
  • Keep one clear action per item.

Avoid

  • Showing actions the user is not currently allowed to take.
  • Coloring items by severity instead of stating it.
  • Letting Forma layout or order stand in for application priority.

Verification specimens

Generated fault-injection specimens expose content, spacing, color-cue, and reduced-effective-contrast risks. They screen presentation robustness as engineering screens without claiming human-subject validation.