The evidence example highlights a different part of the process: assumptions stated. State the reader’s decision first. Arrange sections around the evidence needed to make that decision, then review the gaps. Compare it with next steps before assuming that both items require the same response.
Work through the specimen
A long draft can contain every fact and still leave the reader unable to see the recommendation or its supporting evidence.
Example: Evidence
The illustrative record contains assumptions stated. Its state is section 2. 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 evidence, use “Assumptions stated” as the starting context.
- Identify which role can verify the information. For evidence, use “Assumptions stated” as the starting context.
- Record the exception as well as the expected path. For evidence, use “Assumptions stated” 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 “Next steps” 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 →