Build a phase-gate exit checklist for project approvals

Create a structured, objective sign-off checklist to prevent teams from advancing past project phase gates prematurely.

You getPhase Gate Governance Rules, phase 1 to Phase 2 Exit Checklist and phase 2 to Phase 3 Exit Checklist

Prompt

Prompt
Act as a PMO director. Create a standardized Phase-Gate Exit Checklist that project teams must satisfy before moving from Design to Build, and from Build to Test.

Rules:
- Use objective pass-fail criteria rather than vague confidence ratings.
- Cover deliverables, risk sign-offs, technical debt agreements, and budget reconciliation.
- Include explicit sign-off roles for each category.
- Keep items concise and verifiable through tangible artifacts.

Output format:
1. Phase Gate Governance Rules (3 basic operating principles)
2. Phase 1 to Phase 2 Exit Checklist (table with columns: Category, Verification Requirement, Mandatory Artifact, Sign-Off Role)
3. Phase 2 to Phase 3 Exit Checklist (same table format)
4. Gate Decision Options (Approved, Conditional Approval, Rejected, with strict definitions)

Example output

  1. Phase Gate Governance Rules
  • Gate reviews require unanimous sign-off from designated role leads before work begins in the subsequent phase.
  • Conditional approvals expire after 10 business days; if unresolved items remain, work pauses automatically.
  • All supporting artifacts must be linked and archived in the project repository 48 hours before the review meeting.
  1. Design to Build Exit Checklist
CategoryVerification RequirementMandatory ArtifactSign-Off Role
ScopeAll functional requirements baselined and signed off by clientSigned Product Requirements DocProduct Owner
TechnicalSystem architecture reviewed for security and infrastructure scalingApproved Technical Architecture DesignLead Architect
BudgetRemaining capital expenditure verified against updated vendor quotesMid-Point Budget LedgerFinance Lead
OperationsSupport organization briefed on operational requirementsOperational Readiness ConceptSupport Director
  1. Build to Test Exit Checklist
CategoryVerification RequirementMandatory ArtifactSign-Off Role
Code QualityUnit test coverage reaches minimum 80% thresholdAutomated Pipeline Test ReportQA Lead
EnvironmentsDedicated testing sandbox provisioned with sanitized test dataEnvironment Sign-off SheetDevOps Lead
DefectsZero open Critical or High severity code bugsBug Tracking System ExportEngineering Manager
ComplianceRegulatory and privacy checks passed without active audit flagsCompliance Clearance MemoRisk Officer
  1. Gate Decision Options
  • Approved: All checklist criteria verified; immediate authorization to begin next phase tasks and release budget.
  • Conditional Approval: Minor administrative deficiencies exist; team proceeds with a 10-day deadline to resolve listed gaps.
  • Rejected: Major deliverables or quality thresholds missed; project remains in current phase under active remediation.
Written by AI from this prompt. Your results will vary.

Run this prompt directly in ChatGPT, Claude, or Gemini to establish an approval baseline for your PMO. Ask a follow-up specifying your methodology (such as Waterfall or hybrid Agile) to tailor the listed artifacts.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Project Management
Project Management

Audit a RACI chart for split accountability

Identify dangerous governance flaws, duplicate owners, and delivery bottlenecks in an existing RACI matrix. Use this before launching high-stakes projects.