The programme is the backbone of every construction project. When the programme works, the project flows. When it does not, everything from subcontractor coordination to client confidence falls apart. This guide covers the practical aspects of programme management that matter most to site managers, from setting up a realistic baseline to managing delays and planning recovery.
Setting Up the Baseline Programme
The baseline programme is the agreed plan against which all progress is measured. Getting it right at the start prevents arguments throughout the project.
- Be realistic: A programme that shows everything finishing early to impress the client is worse than useless. It sets expectations that cannot be met, hides the real critical path, and makes delay analysis impossible. Use realistic durations based on actual productivity rates, not optimistic ones.
- Include all activities: Not just construction work, but also design periods, procurement lead times, approval processes, building control inspections, utility connections, and commissioning. These non-construction activities often cause more delays than the physical work.
- Build in dependencies: Activities should be linked logically. You cannot start brickwork until foundations are complete. You cannot start M&E second fix until walls are plastered. These links drive the critical path and reveal the true programme duration.
- Allow for weather: In the UK, you will lose working days to weather. Build in realistic weather allowances based on historical data for your region. Ignoring weather in your programme guarantees you will be behind by the first winter.
- Get it agreed: The baseline should be formally agreed with the client and the design team. This creates the benchmark for measuring progress and assessing delay claims.
Understanding the Critical Path
The critical path is the sequence of activities that determines the earliest possible completion date. If any activity on the critical path is delayed by one day, the completion date moves by one day.
As a site manager, you need to know your critical path at all times. It tells you where to focus your attention and resources. The critical path is not fixed -- it can change as the project progresses. An activity that had 3 weeks of float at the start of the project may end up on the critical path if earlier activities take longer than planned.
Key principles:
- Focus resources on critical path activities: If the critical path runs through the M&E installation, that is where you need your best supervision, your most reliable subcontractor, and your most detailed planning.
- Protect float: Activities with float provide a buffer. Do not use that buffer carelessly. If a non-critical activity has 2 weeks of float, that does not mean it is OK to start it 2 weeks late -- something else might go wrong in the meantime.
- Monitor near-critical activities: Activities with less than 1 week of float are at high risk of becoming critical. Watch them closely.
- Understand the difference between total float and free float: Total float is the amount an activity can be delayed without delaying the project. Free float is the amount it can be delayed without affecting any successor activity. These are often different, and it matters for delay analysis.
Look-Ahead Planning
The look-ahead programme is your operational planning tool. It takes the next 3-6 weeks of the master programme and breaks it down into daily activities with specific resource allocations.
- Update weekly: The look-ahead should be reviewed and updated every week, typically during the subcontractor coordination meeting.
- Include prerequisites: For each activity, identify what needs to be in place before it can start: preceding work complete, materials on site, information received, permits in place, access available.
- Assign responsibility: Each activity should have a named responsible person (usually the subcontractor foreman).
- Share with the team: Display the look-ahead on the site notice board. Brief subcontractors on their upcoming activities. Everyone should know what is happening this week and what is coming next week.
- Use it for daily briefings: The look-ahead feeds directly into your daily routine, telling you what should be happening today and what you need to check.
Monitoring Progress
You cannot manage what you do not measure. Progress monitoring should be systematic and honest.
- Measure progress objectively: Use physical completion percentages rather than time-based estimates. "We have laid 120 of 200 metres of drainage" (60% complete) is more reliable than "we have been doing drainage for 3 of 5 weeks" (which assumes constant productivity).
- Update the programme regularly: At least fortnightly, update the programme with actual progress. Show actual start dates, actual completion dates, and revised forecasts for activities in progress or not yet started.
- Compare against baseline: The updated programme should be compared against the baseline to identify slippage. Where is the project ahead? Where is it behind? What has changed on the critical path?
- Record delays contemporaneously: When delays occur, record them in your site diary on the day they happen. Note the cause, the impact, and any mitigation attempted. This evidence is essential for delay claims.
Managing Delays
Delays are inevitable on construction projects. How you manage them determines whether they are minor setbacks or project-defining problems.
- Identify delays early: The earlier you identify a delay, the more options you have for mitigation. Do not wait until a milestone is missed to acknowledge that you are behind. The signs are usually visible weeks in advance.
- Categorise delays: Excusable delays (caused by the client, design changes, weather, force majeure) may entitle you to an extension of time. Non-excusable delays (caused by the contractor's own failings) do not. The categorisation matters for commercial and contractual reasons.
- Communicate immediately: Tell the client about delays as soon as they are identified. Do not hide them. Clients can handle bad news. What they cannot handle is being blindsided by a delay they should have been told about weeks ago.
- Mitigate where possible: Can you re-sequence activities? Bring forward work from later in the programme? Add resources? Work weekends? Even if the delay is the client's fault, you have a duty to mitigate its impact.
- Document everything: Every delay, its cause, its impact, and the mitigation attempted should be recorded. This evidence supports extension of time claims and protects you against liquidated damages.
Recovery Planning
When the programme has slipped, you need a recovery plan. Here are the options available:
- Re-sequencing: Can activities be reordered to recover time? Can you start the first fix in Block B while Block A finishes? Can external works be brought forward?
- Additional resources: More labour, additional plant, extra shifts. This costs money but may be cheaper than the liquidated damages for late completion. Beware of the law of diminishing returns -- throwing more people at a problem does not always speed things up.
- Extended working hours: Weekend working, longer shifts, bank holiday working. Consider the cost, the impact on workforce fatigue and safety, and any restrictions from the local authority or neighbours.
- Method changes: Can a different construction method speed things up? Precast instead of in-situ concrete? Prefabricated bathroom pods instead of traditional fit-out? Off-site manufacture of components?
- Scope review: Can any elements be deferred to a later phase? Can the specification be simplified in non-critical areas? This requires client agreement but may be the most practical option in some cases.
Recovery plan rule: Any recovery plan must be realistic. A plan that shows recovery through "increased productivity" without explaining how that productivity increase will be achieved is wishful thinking, not planning. Be specific about the measures, the expected time saving, and the cost.
Programme Reporting
Programme information should be communicated clearly in your progress reports and site meetings:
- Summary dashboard: Overall percentage complete, current critical path status, forecast completion date vs baseline completion date. Use traffic light indicators (green/amber/red).
- Milestone tracker: Key milestones with planned, forecast, and actual dates. Highlight any that have moved.
- Delay register: List of delays incurred, their cause, duration, impact, and status (mitigated, claimed, unresolved).
- Look-ahead: 3-4 week look-ahead programme showing upcoming activities, milestones, and key decisions needed.
Site Manager AI can help you generate programme reports and progress summaries that communicate the right information clearly and concisely, without spending hours on formatting and layout.
Related Articles
Generate Documents in Minutes, Not Hours
Site Manager AI creates RAMS, COSHH assessments, toolbox talks, inspection reports, and more -- tailored to your specific project. Used by UK site managers to cut admin time by up to 80%.
Try Site Manager AI Free