GCC Build OSv0
/api
Home/bootminds.pmo/decisions/pmo.dec.raid_owner_assignment

Assign programme RAID register ownerpmo.dec.raid_owner_assignment

P2 GCC

Summary

Name the individual accountable for the RAID register (risks, assumptions, issues, dependencies). After lock, register hygiene is this person's job.

Rationale prompt skeleton

Rationale should reference the raid-register-owner question and the resourcing RACI. Confirm the review cadence and link to Steerco RAID section ownership.

Default options (2)

programme_lead_owns_raid Programme Lead owns the RAID register

Standard for most programmes. RAID review is a fixed item in the Programme Lead's weekly cadence.

Pros
  • + Single accountable owner for the operational health of the programme
  • + No extra hire required
Cons
  • − Risk of de-prioritisation under Programme Lead time pressure
  • − Concentration risk on a single person
dedicated_risk_lead Dedicated Risk/PMO Lead owns RAID register

Separate named role responsible for register hygiene, escalation, and Steerco RAID section. Typical for larger or higher-risk programmes.

Pros
  • + Dedicated focus; less risk of decay
  • + Brings specialist risk-management discipline
Cons
  • − Additional headcount
  • − Risk of the role becoming a buffer between Programme Lead and reality

Default approval chain

  1. Admin
  2. ExecutiveViewer

Linked evidence questions (1)

id prompt workstream
pmo.q.raid_register_owner Who owns the programme RAID register? Capture the named owner and review cadence. pmo.governance_forums