Start with roasted vegetables. The entry pairs “Tray batch” with “12 portions”. That pairing is useful only when it is clear why the context supports the state. A recipe may list the right ingredients but omit the practical details that make a batch repeatable during a busy service.
Begin with the constraint
Record yield and preparation order alongside quantities. Keep service notes separate from changes to the base method.
Example: Roasted vegetables
The illustrative record contains tray batch. Its state is 12 portions. 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 roasted vegetables, use “Tray batch” as the starting context.
- Find the source behind the example record. For roasted vegetables, use “Tray batch” as the starting context.
- Write down the open question before choosing a state. For roasted vegetables, use “Tray batch” as the starting context.
A small exercise
Take one recent recipe organization 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 “Herb dressing” 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 →