Escalated Threats Are Not Monitored Further by the Project Team

PMBOK v8 Definition

Escalated threats are risks that the project team determines to be outside the scope of the project or requiring a response that exceeds the project manager's authority. Once escalated, these threats are managed at the portfolio level, program level, or other relevant part of the organization—not at the project level. Escalated threats are not monitored further by the project team after escalation, although they may be recorded in the risk register for information purposes only. This concept belongs to the Plan Risk Responses process within the Risk Performance Domain.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions testing your understanding of risk response strategy boundaries. Questions often present scenarios where a project manager encounters a threat beyond their authority, and you must identify that escalation is the correct strategy—and crucially, that monitoring responsibility transfers away from the project team. Expect this in situational judgment questions about risk response selection and project manager responsibilities.

Key Points to Remember (for the exam)

• Definition of Escalation: Appropriate when the threat is outside the project scope OR the proposed response would exceed the project manager's authority
• Ownership Transfer: It is important that ownership of escalated threats is accepted by the relevant party in the organization
• No Further Monitoring: The project team does not monitor escalated threats after escalation—this is a non-negotiable rule
• Risk Register Entry: Escalated threats may be recorded in the risk register for information, but this is optional and for documentation only
• Escalation Level: Threats are usually escalated to the level that matches the objectives that would be affected if the threat occurred
• Communication: The project manager determines who should be notified and communicates details to that person or part of the organization
• Distinction from Avoid: Avoid is when the project team acts to eliminate the threat or protect the project from its impact—this is different from escalation

Typical PMI Exam Example

A project manager identifies a regulatory change that could halt the project. The change requires negotiation with government officials—an activity outside the project manager's authority and the project's defined scope. The project manager escalates this threat to the program director. After escalation, the project team does not monitor this threat further. The threat may be recorded in the risk register for information.

PMI Exam Traps

• Trap: Confusing "recorded in risk register" with "still monitored by project team"

  • Reality: Recording is for information only; monitoring responsibility transfers to the receiving party

• Trap: Thinking escalation means the project manager still tracks the threat

  • Reality: The project team explicitly does not monitor escalated threats after escalation

• Trap: Confusing escalation with avoidance

  • Reality: Avoidance is an action taken by the project team; escalation transfers responsibility to a higher level

• Trap: Assuming escalation applies only to threats

  • Reality: Escalation also applies to opportunities—same rules apply for both threats and opportunities

Important PMI Connections

Quick Review Questions

1. After a threat is escalated, who is responsible for monitoring it?

2. Under what two conditions is escalation the appropriate risk response strategy?

3. Can an escalated threat still appear in the project risk register? If so, for what purpose?

4. What must happen for escalation to be complete and effective?

5. If a project team continues to monitor a threat after escalation, are they following PMBOK v8 guidance?

PMBOK v8 Reference

Section 5 – Tools and Techniques (pages 203-204) – Strategies for threats: Escalate
Section 2.7.2.6 – Monitor Risks (process context)