Gate Managementpmo.gate_management

P0 owner role: ProgrammeLead display order 50

Programme gate definitions (Discovery exit, Design exit, Build entry, Cutover ready, Go-live, Stabilisation exit), exit criteria, and approval chains. Governs phase progression of the transformation as a whole.

Depends on: pmo.programme_charter pmo.governance_forums

Questions (4)

id	prompt	scope	category	priority	artefact
pmo.q.gate_definitions	Which phase gates govern this transformation? For each, capture name, position in timeline, exit criteria, and approval chain.	GCC	Gate Management	P0	table
pmo.q.gate_evidence_standards	What standard of evidence is required to pass each gate? Define what 'evidence sufficient to approve' looks like (e.g., 'all P0 questions answered AND classified Reviewed').	GCC	Gate Management	P0	checklist
pmo.q.gate_approval_chain	Who must approve each gate, and in what order? Capture the named approval chain per gate type.	GCC	Gate Management	P0	table
pmo.q.conditional_gate_policy	What is the policy on conditional gate approvals (Go with caveats)? When are they permissible, what evidence must be tracked, and what triggers a follow-up gate review?	GCC	Gate Management	P2	text

Decisions related to this workstream (1)

id	title	scope	priority	evidence questions
pmo.dec.gate_definitions_lock	Lock programme gate definitions (which gates, in what order, with what criteria)	GCC	P0	4