Station Workflow Layout

April 23, 2026 · View on GitHub

Layout: Vertical stack of workstation rows; each row exposes an ID-badged header plus a labeled multi-column attribute strip Best for: Detailed workflow breakdowns where each step carries several structured attributes — inputs, processing, outputs, approval gates, durations — that a single-line description would flatten

Template

Workflow · Station Detail

Order Intake Pipeline

Each station is one named step with a committed contract: what it takes in, what it produces, what can approve it, and how long it should take end to end.

W1 Request Intake Automated
InputEmail, form, or partner webhook
ProcessIntent parse, identity match, entity extract
OutputStructured request payload
GateNone — pass-through
DurationUnder 60 seconds
W2 Case Retrieval Automated
InputRequest payload from W1
ProcessVector search over prior cases plus tag scoring
OutputRanked neighbor set with evidence
GateNone — auto-pass
DurationUnder 2 minutes
W3 Cross-System Reconciliation Assisted
InputW1 payload plus W2 neighbors
ProcessBounded tool calls across systems of record
OutputEvidence bundle with anomalies flagged
GateAnalyst spot-check on flagged items
DurationUnder 15 minutes
W4 Decision & Response Reviewed
InputW3 bundle plus policy context
ProcessDraft decision and response letter
OutputSigned response and audit record
GateTwo-signature review before send
DurationUnder one working day
Process Reference · Intake v2

Variations

  • Four columns: drop one cell (e.g. Gate) and switch to repeat(4, 1fr) for lighter content.
  • Emphasis station: add the hl modifier on the station that carries the highest decision weight; limit to one station per card.
  • Duration-only strip: keep the header row and compress attributes into a single "Before / After" duration comparison when the card is about speed, not contract.

When Not to Use

  • The workflow has more than six stations → switch to timeline-flow and move attributes into hover details or a companion table.
  • Each station carries only one attribute (just a description) → timeline-flow is a better fit.
  • The stations are parallel, not sequential → use badge-grid or bento-grid.