A risk we recorded has now happened. What changes?

Risk becoming an issue

Manage the event as a current issue while preserving the risk history. Activate the planned response, assess actual impact, and check whether related uncertainties remain.

What to do now

  1. Confirm the event and immediate impact
  2. Activate the authorized response
  3. Create or link the issue record
  4. Review residual risks and the recovery forecast
Recommended action flow for risk becoming an issue: Confirm the event and immediate impact then Activate the authorized response then Create or link the issue record then Review residual risks and the recovery forecast. Escalate when the actual impact exceeds the response owner's authority.

When to escalate

Escalate when

The actual impact exceeds the response owner's authority.

Who decides

The accountable risk owner

Example

A supplier outage becomes an active issue, while the risk of a longer interruption remains under review.

Mistake to avoid

Leaving an occurred event only in the risk register.

Prevent a repeat

Review whether response tasks and trigger conditions remain appropriate as the project changes.

Suggested ApprovedFlow setup

  • Documents
  • Tasks
  • Approvals

Store the risk assessment as a controlled project document and assign response tasks; do not assume a native risk engine is enabled. See the platform

Related cases

Practice references