---
ref_id: PR22
ref_type: Process
ref_name: "Identify Risks"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.7.2.2"
companion_ref_shortcode: PG-APG-5.19
related_skills:
  - SKL-03-11
related_artifacts:
  - A19
file_path: "reference/processes/PR22-identify-risks.md"
---
# PR22 — Identify Risks

## Classification
- **Performance Domain:** Risk
- **Process Group:** Planning (iterative throughout)
- **PMBOK 8 Reference:** Section 2.7.2.2
- **Process Groups Practice Guide Reference:** Section 5.19

---

## Purpose
Identify Risks is the process of identifying individual project risks as well as sources of overall project risk and documenting their characteristics. The key benefit is that it documents existing individual project risks and sources of overall project risk, bringing together information so the project team can respond appropriately.

---

## Inputs
- Project management plan (requirements, schedule, cost, quality, resource, risk management plans; scope, schedule, cost baselines)
- Project documents: assumption log, cost estimates, duration estimates, issue log, lessons learned register, requirements documentation, resource requirements, stakeholder register
- Agreements
- Procurement documentation
- Enterprise environmental factors
- Organizational process assets

---

## Tools & Techniques
- Expert judgment
- Data gathering (brainstorming, checklists, interviews)
- Data analysis (root cause analysis, assumption and constraint analysis, SWOT analysis, document analysis)
- Interpersonal and team skills (facilitation)
- Prompt lists (PESTLE, TECOP, VUCA)
- Artificial intelligence
- Meetings

---

## Outputs
- Risk register
- Risk report
- Project documents updates (assumption log, issue log, lessons learned register)

---

## Key Concepts
- Risk identification is iterative — new risks emerge as the project progresses.
- A risk is described in a cause-event-consequence structure.
- Distinguishing genuine risks from non-risks (concerns, issues) is essential.
- Potential risk owners may be nominated during this process and confirmed during qualitative analysis.
- Preliminary risk responses may also be identified and recorded.

---

## Source Traceability
- PMBOK 8: Section 2.7.2.2
- Process Groups Practice Guide: Section 5.19

---

## Cross-References

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

## Practitioner Notes

Practitioners executing this process should seek answers to the following questions:
1. Have multiple risk identification techniques been applied (brainstorming, interviews, checklists)?
2. Are both threats and opportunities captured in the risk register?
3. Are risk owners assigned for each identified risk?
4. Are assumptions tested as part of the risk identification process?
5. Is the risk register reviewed and updated at defined intervals?

## 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 |
