Build the programme.
A programme is just the job, in the right order, with sensible timings. Here’s a simple one for a bathroom refit. Read it, then answer the questions — the same thinking scales up to a whole building.
The order of work
| Step | Task | Time |
|---|---|---|
| 1 | Strip out the old bathroom | 1 day |
| 2 | First fix — pipes & cables in the walls | 1 day |
| 3 | Plaster the walls | 1 day (+ drying) |
| 4 | Tile | 2 days |
| 5 | Fit the suite & second fix | 1 day |
| 6 | Seal, test & hand over | 1 day |
Everything below is based on this programme. Read the order, then answer.
Why does 'first fix' come before plastering?
Why: First fix (pipes and cables) has to happen before the walls are closed up and plastered - you can't easily add them afterwards.
Task B can't start until Task A finishes. That's called...
Why: When one task relies on another finishing first, that's a dependency - the backbone of any programme.
The tiling slips by two days. What's most likely affected?
Why: Tasks that depend on tiling all shift too. A slip early in the chain ripples through everything after it.
'Lead time' on the chosen tiles is 3 weeks. What should the manager do?
Why: If something takes 3 weeks to arrive, you order it early - or it holds the whole job up.
What's the point of building a programme at all?
Why: A programme sequences the work, reveals clashes before they happen, and gives everyone a finish date to aim at.
Nice start.
We’ll do the same quiz at the end of the week — you’ll spot the difference.
Sequenced it out?
Mark it complete and we’ll bounce you back to your Operations dashboard with the stamp added. Ask your buddy to show you a real site programme — they can get big.