Components

The patterns follow one recommended path for a workflow screen: See, Decide, Act, Confirm, Record, and back to See. It is a path, not a standard, and not every screen needs every stage. Read the story for how the stages connect. Each pattern works alone.

See#

What is happening?

• Status strip: a headline number, a segmented bar and a legend, with a slot for the action.
• Data table: a list of rows with named saved views, selection, and an action slot fed the selected rows.

Decide#

What needs me, and who hears?

• Recipient roster: one list of people with a switch per channel.
• Alert rules: reminder days, escalation and quiet hours, written as a rule you can read and save before anything is sent.

Act#

Do it safely.

• Save bar: "Unsaved changes" with Discard and Save, hidden when clean.
• Approval step: a sign-off with a stated reason and meaning.
• Confirm send: click, confirm with the count, send, "Sent to N".

Confirm#

Did it work, who knows?

• Notify envelope: pure helpers for rosters, list comparison and the one-message To/Cc envelope.
• Quiz: tap an answer and see at once whether it was right, and which option was.

Record#

Can I prove who did what?

• Audit timeline: a read-only "who did what, when, and why" list for the events your server has recorded. It closes the loop back to See.

Whole screens#

Several stages already wired together.

• Status and notify: a status headline, a confirm-then-send action, and one roster of who hears about it. Runs from See to Confirm.
• Calibration desk: all five stages on one screen, a worked example you read first. Gauges due for calibration, a recall that two people must approve, a notice to the owners, and an audit trail, with an in-memory server you replace with your own. Runs from See to Record.