Phase-Gate (Stage-Gate) Timeline

1  Slide Type Name
Phase‑Gate (Stage‑Gate) Timeline

2  One‑Sentence Purpose Statement
Clarifies “Which phase are we in, what’s next, and what approvals must we secure to advance?”

3  Visual Description (Designer Instructions)

• Lay out a 16 × 9 slide with a wide horizontal band occupying the middle third.
• Segment the band into consecutive rectangular blocks—one for each project phase (e.g., Concept, Design, Build, Test, Launch). Size each block proportionally to its planned duration; assign a distinct soft color per phase for quick differentiation.
• Print the phase title in bold, centered within each block, with the planned start‑ and finish‑date range in a smaller font beneath the title.
• Between every pair of phase blocks, place a narrow vertical “gate” column (≈ 1 cm wide). Inside each gate, use a large outlined circle or hexagon with a check‑mark placeholder. Under the icon, label the gate (e.g., “Gate 1: Business Case Approval”).
• Draw a thin timeline axis along the bottom of the phase blocks, marking key calendar ticks (months or quarters). Extend faint gridlines upward to help align the gates precisely on their decision dates.
• Optionally add a bold vertical “Today” line, spanning the height of the phase band, to orient viewers.
• Keep generous whitespace above and below the band for commentary or KPI call‑outs. Use a consistent sans‑serif font; limit the palette to 3‑4 harmonized colors plus one accent for gates.

4  Business Questions This Slide Answers

• Which project phase are we currently executing?
• What governance gates are upcoming, and when?
• Has each completed phase received the necessary approval?
• How do phase durations compare—where is the longest or riskiest stretch?
• What slippage exists between planned and actual gate dates?

5  When to Use (Typical Situations)

• Stage‑gate product‑development reviews (e.g., R&D, pharmaceuticals, aerospace).
• Capital‑investment programs that require formal toll‑gate go/kill decisions.
• Governance packs for PMOs, steering committees, or board oversight.
• Regulatory projects with mandated review checkpoints.
• Vendor‑selection or procurement cycles with down‑select gates.

6  Core Data Fields Required

• Phase names and planned durations (start and finish dates).
• Gate identifier, description, and scheduled decision date.
• Actual “Today” date (for status line).

7  Optional / Advanced Data Fields

• Gate status icon (✓ approved, ✕ rejected, ⏳ pending).
• Phase RAG status or % complete shading.
• Phase owner / accountable lead.
• Budget or benefit estimates per phase.
• Confidence level or risk rating for each phase/gate.