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

Lock stakeholder engagement planpmo.dec.stakeholder_engagement_plan_lock

P2 GCC

Summary

Lock the engagement model for non-Steerco stakeholders. After lock, deviations require Programme Lead approval and a logged rationale.

Rationale prompt skeleton

Rationale should reference the stakeholder map question and the communication cadence. Note any stakeholders who require bespoke engagement.

Default options (2)

tiered_engagement Tiered engagement (High influence/high interest = active; high/low = manage; low/high = inform; low/low = monitor)

Classical Mendelow grid. Each tier has a defined engagement frequency and channel.

Pros
  • + Well-understood model
  • + Engagement effort matches stakeholder importance
Cons
  • − Static classification; influence/interest change over time
  • − Requires periodic review
ad_hoc_with_programme_lead_judgment Ad-hoc engagement at Programme Lead's judgment

No structured plan; engagement happens as needed.

Pros
  • + Flexible; no planning overhead
Cons
  • − Engagement drift; stakeholders get under-served or over-served
  • − Hard to audit

Default approval chain

  1. Admin
  2. ExecutiveViewer

Linked evidence questions (1)

id prompt workstream
pmo.q.stakeholder_map Who are the programme's stakeholders beyond the Steerco? Capture name, role, interest, influence, and engagement model for each. pmo.governance_forums