Skip to content
PMPCAPM

Escalate (Risk Strategy)

Escalate is a risk response strategy used when a risk is outside the scope or authority of the project team. The risk is transferred upward to a program, portfolio, or organizational level where it can be effectively managed.

Explanation

Escalation is appropriate when a risk affects objectives beyond the project level, requires authority or resources the project manager does not have, or is better managed at a higher organizational level. Examples include strategic risks, regulatory changes, enterprise-level resource constraints, or risks that span multiple projects in a program.

When a risk is escalated, ownership shifts to the appropriate level (program manager, portfolio manager, or PMO). The risk is still documented in the project risk register with a note that it has been escalated, but the project team is no longer responsible for developing or implementing a response.

Escalation was formally introduced as a named strategy in the PMBOK Guide Sixth Edition. It applies to both threats and opportunities. The key distinction from transfer is that escalation moves the risk within the organization (upward), while transfer shifts it to an external third party.

Key Points

  • Used when risk is outside the project scope or authority
  • Ownership moves to program, portfolio, or organizational level
  • Applies to both threats and opportunities
  • Different from transfer: escalation is internal (upward), transfer is external

Exam Tip

Escalation is for risks beyond the project team's control. If a question describes a risk requiring executive decisions or spanning multiple projects, "escalate" is likely the correct response.

Frequently Asked Questions

Related Topics

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.