Start with supplier delay. The entry pairs “Lead-time signal” with “Monitor”. That pairing is useful only when it is clear why the context supports the state. A risk register becomes a list of anxieties when it lacks a trigger, an accountable owner and an agreed response.
Begin with the constraint
Describe the condition, its impact and an early signal. Review the response when the signal appears, not only at a scheduled meeting.
Example: Supplier delay
The illustrative record contains lead-time signal. Its state is monitor. 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 supplier delay, use “Lead-time signal” as the starting context.
- Find the source behind the example record. For supplier delay, use “Lead-time signal” as the starting context.
- Write down the open question before choosing a state. For supplier delay, use “Lead-time signal” as the starting context.
A small exercise
Take one recent project risk planning 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 “Scope growth” 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 journal →