# Review workflows

Review workflows make a sequence, its unresolved work, and its decisions visible without turning the page into a dashboard of competing cards.

## Workflow card

- Name the workflow and explain the ordered requirement in one sentence.
- Place the workflow status and `Step n of total` together in the card header.
- Render steps as equal-width destinations on wide screens and a readable vertical sequence on small screens.
- The current step uses the inverse treatment. Future steps remain legible but visibly locked; completed steps use a clear completion signal.
- Put the continuation requirement next to the Next action, not inside a large tooltip.

## Tooltips for locked steps

Use the compact shared tooltip for a short reason such as `Complete the previous step first`. It uses small type, compact padding, one line when possible, and no oversized callout styling. The same reason must be available on keyboard focus and through accessible description.

## Decision rows

- Each row identifies the subject first, then state, then actions.
- Group mutually related icon actions in one bordered segmented control. All segments use equal 36px square targets and the first and last segments own the outer radii.
- Use addition tone for approve, removal tone for decline, and neutral tone for abstain or not applicable. Icons require accessible names and tooltips when their meaning is not visible.
- Do not make the rightmost segment wider merely because it is last; each action receives the same hit area.
- A pending status may explain an external blocker through a compact tooltip, but the blocker must not be encoded only as an icon.

## Proposed access changes

- Proposed additions and removals use `--change-*` tokens rather than final success and danger tokens.
- Summaries state the total proposed changes and compact counts such as `+1 addition` and `−1 removal`.
- Use plain headings such as `Access to add` and `Access to remove`; avoid internal process language such as “documented for addition.”
- An applied row state reads `Access will be added` or `Access will be removed` and provides a quiet Undo action.

## Page actions

Primary workflow approval is a primary button. Decline or Deny is a bordered negative action, not unstyled red text. Cancel request and Export remain secondary and may be separated when their scope differs. Destructive actions require confirmation.

## Summary card

Keep request or review status in the summary-card heading, where it is interpreted with proposed changes and justification. Separate Summary and Justification with a clear section divider; use an Edit action only when the viewer has permission.