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-07 — Communications & Reporting Cadence

Defines who receives what information, when, and in what format.

Owner: PM GuildApprover: PMO DirectorVersion: 2.4Updated: 10/23/1969

1. Purpose

Give stakeholders the right information at the right time to make decisions.

2. Scope

All projects.

3. Definitions

  • Comms plan — The document listing recipients, cadence, channel, and content of each communication.

4. Roles & Responsibilities (RACI)

ActivityRACICadence
Author comms planPMPMO DirectorSponsorTeamPer project
Send status reportsPMPMO DirectorTeamStakeholdersWeekly

5. Procedure

  1. Author the comms plan at planning; align with stakeholder register.
  2. Publish weekly status: RAG, milestones, RAID highlights, decisions needed.
  3. Publish monthly Steering pack: finance, risks, forecast.
  4. Publish quarterly executive report to the Executive Sponsor and portfolio.

6. Inputs & Outputs

Inputs

  • Stakeholder register
  • Status data

Outputs

  • Weekly status
  • Monthly Steering pack
  • Executive report

7. Controls & Metrics

MetricTarget
Status reports issued on cadence≥ 98%

8. Exceptions & Escalation

  • Crisis comms escalates cadence to daily until resolution.

9. Records & Retention

RecordRetention
Status reports3 years

10. Related Documents

  • SOP-PM-02
  • SOP-PM-04

11. References

  • PMBOK 7

12. Revision History

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

Document code: SOP-PM-07 · 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