Workflow status should tell staff what happened and what they can do next. Internal labels such as running or success can hide whether a customer request was saved, approved, sent, or still uncertain.
Staff status is a domain view
A staff-facing status translates trusted workflow state into an understandable operational meaning. It should preserve the distinction between decision, execution, and business outcome without requiring employees to understand orchestration internals.
For a proposed status model, show the current business stage, known effect, next action, owner, and relevant time. Use plain labels such as waiting for review, approved but not sent, update failed before saving, or result being checked.
Do not simplify uncertainty into failure merely to avoid a longer label. Staff may retry a failed action, while an uncertain action may need reconciliation first. The difference changes what is safe.
Test a fictional approved request
A manager approves a customer update, but the external service is unavailable. A screen that shows only approved may lead staff to believe the record changed. A better view says that approval is complete and execution is pending, with the responsible recovery queue.
A second fixture loses the external response. The status should explain that the outcome is being checked and disable any generic action that would blindly repeat the write.
| Trusted state | Staff-facing meaning |
|---|---|
| Pending decision | Waiting for an authorised review |
| Approved, queued | Approved; change not yet confirmed |
| Rejected before effect | Not applied; stated correction needed |
| Remote outcome unknown | Result being checked before retry |
| Authoritative completion | Defined change completed with record link |
Ask ordinary staff to interpret fictional cases without coaching. Check whether they identify the correct next action and avoid unsupported promises to customers.
Keep detail available without overwhelming the view
The main screen can remain concise while linking to authorised evidence, attempts, and history. Include timestamps with clear meaning; creation time, last attempt, and completion time are not interchangeable.
Too many statuses can confuse people, while too few hide consequence. Define labels around actions staff need to take and group technical subcategories behind details. Review wording after incidents where staff misunderstood the state.
This interface model is proposed. The HVAC case study describes staff-visible request and notification retry states without claiming this exact status system. Pair it with automation handover design.
Workflow status FAQ
Should staff see raw execution errors?
Show a safe actionable explanation, with controlled technical detail for the appropriate role.
Is approved equivalent to completed?
No. Decision and execution are separate stages.
What makes a status useful?
It accurately describes the known business effect, next permitted action, current owner, and any meaningful uncertainty.