Project governance
Directing a Project
Run governance as a decision system so sponsors and boards can direct value, tolerance, and risk in time.
What this helps you do
Keep governance focused on decisions, tolerance control, and benefits confidence rather than status theatre.
Use this when
- Setting up governance cadence at initiation.
- Preparing sponsor or board-level highlight reports.
- Escalating exceptions, major changes, or value concerns.
- Reviewing continuation decisions at stage boundaries.
What good looks like
- Decision rights, escalation triggers, and approval routes are explicit.
- Sponsor packs are concise and action-led with clear decision asks.
- Approvals, conditions, and rationale are captured in the decision trail.
- Board time is spent on choices, trade-offs, and tolerance, not narrative updates.
- Continuation decisions reference value, risk, and delivery confidence.
Minimum viable version
- Named decision forum and governance calendar.
- Decision log with owner, due date, rationale, and status.
- Highlight report rhythm aligned to tolerance and sponsor needs.
- Escalation rule for exception and urgent decisions.
Stronger version
- Assurance checkpoints aligned to risk and spending profile.
- Stage gate decision packs with options and recommendation.
- Benefit confidence trend and disbenefit visibility in board reporting.
- Supplier and dependency risk view integrated into governance packs.
Step-by-step operating flow
- Define governance roles and decision rights across sponsor, board, and PM.
- Set reporting cadence and required decision pack structure.
- Agree tolerance thresholds and explicit escalation conditions.
- Run regular directing cycles with concise action-led highlight packs.
- Escalate exceptions with option impacts and recommendation.
- Record approvals, conditions, and follow-up actions in the decision log.
- Use stage boundaries to direct continue, adjust, reset, or stop choices.
- Reconfirm value and strategic fit after material change.
Inputs needed
- PID Lite, business case lite, and stage plan.
- Current RAID and decision backlog.
- Forecast variance, tolerance status, and benefit confidence.
- Assurance findings and supplier performance where relevant.
Outputs produced
- Directed actions from sponsor or board.
- Recorded decisions with rationale and accountability.
- Continuation or reset direction at boundaries.
- Updated governance actions and escalation outcomes.
Common mistakes
- Turning governance meetings into information broadcasts.
- Presenting risk without options or recommendation.
- Escalating too late, after tolerance has already failed.
- Failing to record conditional approvals and follow-up ownership.
- Separating value decisions from delivery reality.
Tailoring notes
- Lite projects can run with one sponsor forum and lean packs.
- Enhanced and Recovery work needs tighter cadence and stronger assurance.
- Public-sector projects should include audit-ready rationale for major approvals.
- Supplier-heavy projects should include dependency and contract exposure in every pack.
Related templates
Related tools
PRINCE2 mapping
Operational translation of PRINCE2 Directing a Project, emphasising governance decisions at initiation, stage boundaries, exceptions, and closure.