Platform · Governance
Change, risk, and approvals — in the workflow
Governance is not a separate spreadsheet: BotPM weaves RAID, change control, and stakeholder accountability into the same execution paths as schedule and EVM — with autonomy and tier gates you control.
In practice
Proposals before impact — not after the fact
In higher autonomy modes, the AI can draft and route more work — but policy-gated actions still surface for humans when your rules say so. That is how PMOs keep velocity without losing defensibility.
- RAID-style registers with insight-linked narratives where enabled
- CCB workspace for structured change — not ad-hoc email chains
- Alignment to stakeholder comms so approvals and broadcasts stay coherent
Governance building blocks
Depth of automation and which gates apply depend on subscription, services, and org policy.
RAID & issues
Registers and narratives stay linked to schedule and cost — so risks and issues show up where executives already look.
Change control & CCB
Quick requests and full change workspaces with proposals your policies can require before baselines move.
Approvals & audit posture
High-impact actions surface as proposals where rules demand it; execution leaves traces for reviews (see Trust & Security).
Finish strong: closeout
Governance extends to handover, archive readiness, and lessons — tie the loop before the next program starts.