Risks can be escalated (and de-escalated) through the project and organisation structure. This feature enables risk to be managed at the most appropriate level within the business, whether thats the project, programme, or corporate or portfolio level.
Why would I escalate / de-escalate a risk?
Risks created by your project team may be better managed at the organisation level, or even at a higher level within the federated organisation structure. If so, they can be escalated.
Conversely, risks in the organisation (portfolio or corporate) risk register may be applicable for new projects or may be better managed at the project level and so can be 'de-escalated.'
How do I escalate / de-escalate arisk?
Risks can be escalated when creating the risk or at any time thereafter when you're editing the risk.
Escalating a risk or issue is achieved by setting it’s ownership level to organisation (Elevated).
De-escalating a risk or issue is achieved by setting it’s ownership level to project.
When the risk is escalated you need to select a new risk owner and actionee from the new ownership level.
The new owner and actionee/s will be notified when they are escalated the risk.
To de-escalate a risk, just do the same but select 'de-escalate.'
This video will show you how risk escalation / de-escalation, works.
Transfer a risk
Risks can be managed at any level of the organisation. There are a number of ways each risk can be managed and these features, and how they relate to the escalation / de-escalation process are shown in the table below;
|Project||Organisation Unit||Parent Organisation Unit|
|Visibility||The creating org + project as well as shared with orgs||Previously visible + org admins and owners||Previously visible + parent org admins and owners|
|Ownership||The creating org + project admins and owners||Org level owners and admins only||Parent org owners and admins|
|Task assignment||The creating org + project and shared with orgs||Org level admins / owners + creating org + project team||Org level admins / owners + creating org + project team|
|To org level owners + admins (project owners can escalate)||To parent org admin / owners + deescalation to project||escalate to parent + deescalate to child org units|
|Transfer||To orgs the risk is shared with||Record can be either transferred or escalated||N/A|
|Linking||The creating org + visible to admins and owners||The org unit + visible to admins and owners||The org unit + visible to admins and owners|
|Commenting||All visible||All visible original + org level owner / admins||All visible original + parent org level owner / admins|
|Sharing||The creating org/project to org level and project partners. (Received risks can’t be escalated unless owned)||To parent org. ( Optionally to projects as view only)||To parent org. ( Optionally to projects as view only)|