Start with rp-041. The entry pairs “Label sent” with “Requested”. That pairing is useful only when it is clear why the context supports the state. A return label moves a parcel without explaining its condition, the inspection outcome or the next message to the customer.
Begin with the constraint
Keep the stated reason separate from the observed condition. Record inspection evidence before choosing a resolution.
Example: RP-041
The illustrative record contains label sent. Its state is requested. 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
- Define the decision the reader needs to make. For rp-041, use “Label sent” as the starting context.
- Find the source behind the example record. For rp-041, use “Label sent” as the starting context.
- Write down the open question before choosing a state. For rp-041, use “Label sent” as the starting context.
A small exercise
Take one recent return logistics 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 “RP-042” 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 notes →