Document Risk Triggers and Thresholds Based on Context

A risk trigger is the event or condition that signals a risk is about to happen or has just started happening — distinct from the risk's root cause, which is why it could happen in the first place, and its consequence, which is what happens if it does. This task is about documenting all three clearly enough that the team can actually recognize a risk materializing in real time, not just describe it after the fact.

As the project's actual context evolves, the thresholds and categories set earlier need to be reassessed and confirmed against updated data — a threshold that made sense at kickoff may not still fit six months in. Documenting triggers, causes, and timing (when a risk is likely to materialize) alongside consequences and impact gives the team something genuinely actionable, and empowering stakeholders to challenge existing thresholds keeps the whole system from calcifying around assumptions that no longer hold.

Study focus: triggers, causes, and consequences get tested as three distinct concepts. A question describing a specific warning sign that a risk is about to occur is asking about a trigger — not the cause, and not the consequence.