Start with recommendation. The entry pairs “Decision required” with “Section 1”. That pairing is useful only when it is clear why the context supports the state. A long draft can contain every fact and still leave the reader unable to see the recommendation or its supporting evidence.
Begin with the constraint
State the reader’s decision first. Arrange sections around the evidence needed to make that decision, then review the gaps.
Example: Recommendation
The illustrative record contains decision required. Its state is section 1. 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 recommendation, use “Decision required” as the starting context.
- Find the source behind the example record. For recommendation, use “Decision required” as the starting context.
- Write down the open question before choosing a state. For recommendation, use “Decision required” as the starting context.
A small exercise
Take one recent document workflows 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 “Evidence” 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 field notes →