A risk owner left the organization. What should happen immediately?
Orphaned risk responsibilityReassign accountability and check whether response actions, evidence, and authority transferred with the role. Changing the name in the register is not enough.
What to do now
- Identify affected risks and responses
- Appoint an interim accountable owner
- Transfer context and pending actions
- Confirm new review and escalation arrangements
When to escalate
Escalate when
A significant response deadline will pass without an authorized owner.
Who decides
The accountable risk owner
Example
A procurement manager's departure triggers a review of supplier-contingency actions and delegated authority.
Mistake to avoid
Assuming the departing person's manager automatically knows every risk.
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
- Nobody wants to own a risk outside their department. Who should take it?Cross-boundary risk ownership
- How should we handle a risk we cannot prevent?Unavoidable exposure
- Who owns benefits after the project team leaves?Unassigned benefits accountability
- We have no owner after the AI pilot succeeds. What should happen before launch?Missing AI service ownership