---
ref_id: PR02
ref_type: Process
ref_name: "Identify Stakeholders"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.2"
companion_ref_shortcode: PG-APG-4.2
related_skills:
  - SKL-02-03
  - SKL-03-03
  - SKL-03-08
  - SKL-04-04
related_artifacts:
  - A04
  - A07
  - A10
  - A18
  - A19
  - A29
file_path: "reference/processes/PR02-identify-stakeholders.md"
---

# PR02 — Identify Stakeholders

**Ref ID:** PR02
**Type:** Process
**PMBOK8 Source:** §2.2
**Version:** 1.0.0

---

## Definition

Identify Stakeholders is the process of identifying project stakeholders regularly and analyzing and documenting relevant information regarding their interests, involvement, interdependencies, influence, and potential impact on project success.

## Key Characteristics

- **Continuous Execution:** Repeated regularly throughout the project lifecycle, starting before or during charter development.
- **Systematic Analysis:** Assesses stakeholder power, interest, influence, and expectations to determine engagement priority.
- **Inclusive Scope:** Identifies all potential internal and external individuals, groups, or organizations affected by or affecting the project.
- **Central Documentation:** Consolidates stakeholder information in the Stakeholder Register for secure and controlled team reference.
- **Engagement Grounding:** Directly informs communication planning, risk assessment, and stakeholder engagement strategies.

## PMBOK 8 Context

Under PMBOK 8, Identify Stakeholders is a primary pillar of the **Stakeholders Performance Domain** and is closely linked with the **Governance Performance Domain**. Effective stakeholder identification ensures that project objectives align with stakeholder needs and that governance structures have the right representation. This process is revisited at the start of each phase and whenever major organizational changes occur.

## Inputs

| Input | Description | Source |
|---|---|---|
| Project Charter | Provides initial high-level stakeholder context, project purpose, and sponsoring authority. | PR01 Develop Project Charter |
| Business Documents | Business case and benefits management plan identifying early stakeholders and beneficiaries. | Sponsoring Organization |
| Project Documents | Change log, issue log, and requirements documentation highlighting new stakeholder interactions. | Core Team |
| Agreements | Contractual arrangements referencing suppliers, customers, and key legal contacts. | Procurement / Sourcing |
| Factors & Assets | Enterprise environmental factors and organizational process assets (e.g. templates and directories). | Enterprise / PMO |

## Outputs

| Output | Description | Destination |
|---|---|---|
| Stakeholder Register | Comprehensive directory of identified stakeholders, categorization, and assessment details. | A07 Stakeholder Register |
| Change Requests | Formally requested modifications to current planning basis triggered by stakeholder identification. | PR31 Integrated Change Control |
| PMP Updates | Revisions to requirements, communications, risk, and stakeholder engagement plans. | PR03 Develop PMP |
| Document Updates | Updates to assumption logs, issue logs, and risk registers. | Project Registry |

## Tools and Techniques

- **Expert Judgment:** Guidance from advisors with experience in organizational dynamics, regulatory landscapes, and stakeholder analysis.
- **Data Gathering:** Brainstorming, questionnaires, and surveys to identify potential stakeholders.
- **Data Analysis:** Stakeholder analysis and document analysis to understand power, interest, and influence.
- **Data Representation:** Stakeholder mapping matrices (e.g. Power/Interest grid) and representation models.
- **Meetings:** Alignment sessions and stakeholder workshops to discover and categorize project participants.

## Cross-References

| Related Item | Type | Relationship |
|---|---|---|
| A04 | Artifact | Input context and authority source |
| A07 | Artifact | Principal output of this process |
| A10 | Artifact | Resources and communications planning component updated by stakeholder needs |
| A18 | Artifact | Issues log updated when stakeholder challenges emerge |
| A19 | Artifact | Risk register updated when stakeholder dynamics introduce threats or opportunities |
| PR01 | Process | Supplying the authorizing charter and early high-level stakeholder frames |
| SKL-02-03 | Skill | Identify and Analyze Stakeholders |
| SKL-03-08 | Skill | Plan Stakeholder Engagement |

## Practitioner Notes

Practitioners executing this process should seek answers to the following vital questions:
1. Who can affect or be affected by project decisions, execution, outcomes, value realization, or phase completion?
2. Which stakeholders possess high influence, high impact, or high interest and therefore require deliberate management?
3. Have external parties such as regulatory bodies, suppliers, end-users, and local communities been systematically included?
4. What specific risks or potential project issues arise from stakeholder expectations, resistance, or dependency networks?
5. At what key project milestones or phase transitions will the stakeholder analysis be refreshed?

## Change Log

| Version | Date | Description | Author |
|---|---|---|---|
| 1.0.0 | 2026-06-02 | Rebuilt to align with canonical REF file structure and YAML front-matter | PMO Director |

---

*Authority: PMBOK8 Guide §2.2; Process Groups Practice Guide §4.2*
