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
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
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.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Build a project intake scoring rubric for requests
Establish an objective scoring matrix to evaluate incoming project requests and prevent urgent ad-hoc demands from crowding out strategic priorities.
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.
Design a change control board review agenda and rubric
Establish a fast, repeatable 30-minute Change Control Board agenda paired with an objective scoring rubric to approve or reject changes.
Create a shared milestone alignment brief across teams
Generate a unified alignment brief that resolves date conflicts and sets clear accountability across teams. Use this when cross-functional partners work off competing schedules.
Synthesize past project lessons into kickoff safeguards
Turn historic post-mortem archives into practical governance rules, charter additions, and pre-mortems for upcoming projects.
Create a stakeholder matrix and communication plan
Map project stakeholders by power and interest to design a targeted communication cadence that prevents noise and missed updates.