Escalated Opportunities: Project Team Stops Monitoring After Escalation

PMBOK v8 Definition

Escalated opportunities are managed at the portfolio level, program level, or other relevant part of the organization, but not at the project level. The project manager determines who should be notified about the opportunity and communicates the details to that person or part of the organization. Escalated opportunities are not monitored further by the project team after escalation, although they may be recorded in the risk register for information. This is one of five alternative strategies for dealing with opportunities, applied when the opportunity is outside the project scope or exceeds the project manager's authority.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions about risk response strategies, specifically testing your ability to distinguish when an opportunity should be escalated versus managed within the project team. Questions often present scenarios where a project manager identifies an opportunity that affects organizational objectives beyond the project, and you must select "Escalate" as the correct response strategy.

Key Points to Remember (for the exam)

• Trigger for escalation: The project team or project sponsor agrees the opportunity is outside the project scope OR the proposed response would exceed the project manager's authority
• Management level after escalation: Portfolio level, program level, or other relevant part of the organization—never at the project level
• Monitoring responsibility: The project team stops monitoring escalated opportunities after escalation
• Documentation: Escalated opportunities may be recorded in the risk register for information purposes only
• Ownership requirement: It is important that ownership of escalated opportunities is accepted by the relevant party in the organization
• Escalation target: Opportunities are usually escalated to the level that matches the objectives that would be affected if the opportunity occurred
• Communication: The project manager determines who should be notified and communicates the details to that person or part of the organization

Typical PMI Exam Example

A project manager identifies a new market opportunity that could benefit the organization's strategic goals, but implementing the response requires changes to company-wide policies beyond the project's scope. The project manager escalates this opportunity to the program level. After escalation, the project team does not monitor this opportunity further, though it is recorded in the risk register for information.

PMI Exam Traps

• Trap: Thinking the project team continues to monitor escalated opportunities

• Reality: Escalated opportunities are not monitored further by the project team after escalation

• Trap: Confusing "Escalate" with "Exploit" strategy

• Reality: Escalate transfers ownership to higher organizational levels; Exploit seeks to make the opportunity happen (100% probability) within the project

• Trap: Believing escalated opportunities are removed from all documentation

• Reality: They may be recorded in the risk register for information purposes

• Trap: Assuming escalation is only for threats, not opportunities

• Reality: Escalation applies to both threats and opportunities with parallel processes

Important PMI Connections

Quick Review Questions

1. After a project team escalates an opportunity, who is responsible for monitoring that opportunity?

2. What two conditions must be present for the escalate strategy to be appropriate for an opportunity?

3. Where are escalated opportunities documented after they are escalated?

4. What happens to an escalated opportunity if the relevant party in the organization does not accept ownership?

5. To which organizational level should an opportunity be escalated?

PMBOK v8 Reference

Section 11.5 - Plan Risk Responses (Strategies for Opportunities: Escalate)