---
name: timeline
description: Turn a list of project phases into a defensible programme, roadmap or Gantt-style schedule with dependencies, milestones and critical decisions marked. Use to build a first-pass programme for a proposal or a client update.
---

# Programme

## What it does
Takes phases and durations and structures them into a clear programme with dependencies and milestones an architect or PM can defend.

## When to use
- In a fee proposal, to show a credible timeline.
- At kickoff, to align the client and consultants on dates.

## Instructions
1. Ask for the phases (or use RIBA/typical stages), rough durations, and any fixed dates (authority lodgement, client board dates).
2. Identify dependencies and the critical path. Flag where durations are assumptions.
3. Mark client decision points and approval gates explicitly, since these are the usual cause of slippage.
4. Offer the output as a table first; a Gantt view can be generated from it.

## Output format
- Phase table: phase | start | duration | depends on | milestone
- Critical path called out
- Client decision/approval gates listed with lead times
- Key risks to the programme

## The one mistake to avoid
Do not bury client decisions inside phases. Slippage almost always comes from late approvals, so surface every gate as its own dated item.