Start with tk-104. The entry pairs “Attachment missing” with “Due Friday”. That pairing is useful only when it is clear why the context supports the state. An email thread can contain a deadline without making anyone responsible for it. That gap creates avoidable last-minute work.
Begin with the constraint
Keep the source date, responsible coordinator and next review together. Record missing information separately from completed checks.
Example: TK-104
The illustrative record contains attachment missing. Its state is due friday. 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 tk-104, use “Attachment missing” as the starting context.
- Find the source behind the example record. For tk-104, use “Attachment missing” as the starting context.
- Write down the open question before choosing a state. For tk-104, use “Attachment missing” as the starting context.
A small exercise
Take one recent case tracking 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 “TK-108” 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 reading room →