The details missing example highlights a different part of the process: return to sender. Start with one repeatable event. Draw a branch for missing information and an explicit stopping point for each approval. Compare it with approved before assuming that both items require the same response.
Work through the specimen
A neat happy path hides the steps that cause real delays: incomplete requests, failed checks and ambiguous ownership.
Example: Details missing
The illustrative record contains return to sender. Its state is branch. Ask what evidence supports that state, which detail is still uncertain and whether the next person could understand it without reading a separate message thread.
Questions for a working review
- Check the current condition against the stated context. For details missing, use “Return to sender” as the starting context.
- Identify which role can verify the information. For details missing, use “Return to sender” as the starting context.
- Record the exception as well as the expected path. For details missing, use “Return to sender” as the starting context.
A small exercise
Take one recent workflow automation example from your own process. Write its context without using a status label, then add the label separately. If the two contradict each other, investigate the source before updating the record. Compare the result with “Approved” in the demonstration to see which distinctions your process needs.
These are planning notes. The specimen is illustrative, and the preview does not process live work.
More practical notes →