---
ref_id: PR39
ref_type: Process
ref_name: "Monitor Risks"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.1"
companion_ref_shortcode: PG-APG
related_skills:
  - SKL-05-06
related_artifacts:
  - A19
  - A20
file_path: "reference/processes/PR39-monitor-risks.md"
---
# PR39 — Monitor Risks

## Process Identity
| Field | Value |
|---|---|
| **Process ID** | PR39 |
| **Process Name** | Monitor Risks |
| **Process Group** | Monitoring and Controlling |
| **Knowledge Area** | Risk Management |
| **PMBOK Source** | Process Groups: A Practice Guide §7.10; PMBOK 8 §2.7.2.6 |

---

## Purpose
Monitor the implementation of agreed-upon risk response plans, track identified risks, identify and analyze new risks, and evaluate risk process effectiveness throughout the project. Enables project decisions to be based on current information about overall project risk exposure.

---

## Inputs
| Input | Description |
|---|---|
| Project management plan | Risk management plan |
| Project documents | Issue log, lessons learned register, risk register, risk report |
| Work performance data | Raw risk status data |
| Work performance reports | Integrated performance reports from Monitor and Control Project Work |

---

## Tools and Techniques
| Tool / Technique | Notes |
|---|---|
| Data analysis | Technical performance analysis, reserve analysis |
| Audits | Independent review of risk management effectiveness |
| Meetings | Risk review meetings |

---

## Outputs
| Output | Description |
|---|---|
| Work performance information | Current risk status and exposure |
| Change requests | Risk response adjustments, corrective/preventive actions |
| Project management plan updates | Any component affected by risk changes |
| Project documents updates | Assumption log, issue log, lessons learned register, risk register, risk report |
| Organizational process assets updates | Risk process lessons and templates |

---

## Key Concepts
Monitor Risks determines whether:
- Implemented risk responses are **effective**
- Level of **overall project risk** has changed
- Status of **identified individual risks** has changed
- **New risks** have arisen
- Risk management **approach** is still appropriate
- **Assumptions** are still valid
- **Contingency reserves** require modification
- **Project strategy** is still valid

---

## PMBOK 8 Alignment
- Maps to **Monitor Risks** in PMBOK 8 §2.7.2.6.
- Risk monitoring is ongoing across the entire project life cycle.
- Connects to the **Risk** performance domain check results (Table 2-11).

---

## Related Processes
- Depends on: PR26 (Implement Risk Responses)
- Feeds into: PR31 (Perform Integrated Change Control)
- Cross-links: PR30 (Monitor and Control Project Work)

---

## Cross-References

| Related Item | Type | Relationship |
|---|---|---|
| A19 | Artifact | Primary artifact produced or updated by this process |
| A20 | Artifact | Primary artifact produced or updated by this process |
| SKL-05-06 | Skill | Skill that executes this process |

## Practitioner Notes

Practitioners executing this process should seek answers to the following questions:
1. Are risk triggers monitored and documented during execution?
2. Are risk response effectiveness assessments performed regularly?
3. Are new risks identified during monitoring added to the risk register?
4. Are risk reserve consumption levels reported and within approved thresholds?
5. Are residual and secondary risks reassessed as the project progresses?

## Change Log

| Version | Date | Description | Author |
|---|---|---|---|
| 1.0.1 | 2026-06-03 | Added Cross-References, Practitioner Notes, and Change Log sections (F-12 Batch 4) | PMO Director |
