UBC — AI Solutions

Audit — Dynamic Documentation Platform

Living documentation that stays in sync with engineering, cloud, AI, and compliance activity. Documents update themselves as the organization changes.

Back to library

SOP

Fresh

SOP-PM-02 — Stakeholder Register & RACI

Identifies stakeholders and documents responsibilities via RACI.

Owner: PM GuildApprover: PMO DirectorVersion: 2.5Updated: 11/7/1969

1. Purpose

Ensure every project has a current stakeholder register and a clear RACI.

2. Scope

All projects.

3. Definitions

Stakeholder — Anyone who affects or is affected by the project.
RACI — Responsible, Accountable, Consulted, Informed.

4. Roles & Responsibilities (RACI)

Activity	R	A	C	I	Cadence
Identify stakeholders	PM	PMO Director	Sponsor	Team	Per project
Author RACI	PM	PMO Director	Function leads	Team	Per project
Refresh register	PM	PMO Director	Team	Stakeholders	Monthly

5. Procedure

Interview sponsor and function leads to identify stakeholders.
Assess power/interest and engagement strategy per stakeholder.
Draft a project-level RACI covering all major deliverables.
Review with the Steering Committee at kickoff.
Refresh monthly and on any material team change.

6. Inputs & Outputs

Inputs

Charter
Org chart

Outputs

Stakeholder register
RACI

7. Controls & Metrics

Metric	Target
Projects with current RACI	100%
Stakeholder register freshness	≤ 30 days

8. Exceptions & Escalation

Large programs may require a tiered stakeholder register with sub-project RACIs.

9. Records & Retention

Record	Retention
Register & RACI	Life of project + 3 years

SOP-PM-07
SOP-QMS-07

11. References

PMBOK 7 Stakeholders, Team

12. Revision History

See the Versions tab for the full change history maintained by the Auto-Doc Engine.

Document code: SOP-PM-02 · Aligned to PMBOK 7 Stakeholders / Team. Controlled document — reproduction outside the UBC QMS requires the Quality Manager's approval.

Suggested by AI

No suggestions right now.

Frameworks

PMBOK 7

ISO 9001