How We Run a Build Programme

Running a programme is not chasing people. It is removing the reasons they would need chasing — the missing decision, the unordered window, the inspection nobody booked.

How We Run a Build Programme — practical guidance from the team running construction project management on the Garden Route. Below is what we actually do week to week to keep a build on programme, and what you should expect to receive while it is running.

Built before the site opens

A programme is written before construction starts and it includes far more than trades.

The activities and their logic — what depends on what, so a delay anywhere can be traced to its effect on the completion date.

The approvals and inspections — municipal stage inspections, NHBRC inspections, engineer sign-offs. Each is a dependency held by somebody outside the site and none of them respond to urgency.

Procurement lead times for every long-lead item, working backwards from the date it is needed to the date it must be ordered. Windows, cupboards, stone tops, specialist tiles, sanitaryware, switchgear.

Your decision dates — a schedule of every selection you have to make and when. This is the item that most reliably determines whether a build finishes on time.

Float, visible. A programme with no slack anywhere is one where the first bad week becomes a delay to completion.

And the weather logic. On the Garden Route, reaching weathertight before the wet part of the year removes most weather risk from the rest of the job, so the sequence is built around that milestone rather than around it happening when it happens.

On public sector and larger private work the contractual and registration framework shapes the programme as much as the construction logic does. CIDB grading governs who may hold the contract, the SACPCMP-registered health and safety agent has to be appointed before work starts where the Construction Regulations require one, and each contractor’s COIDA letter of good standing has to be current at the gate. None of these are difficult, but every one of them is capable of stopping a start date, so they belong on the programme rather than in someone’s inbox.

The weekly rhythm

A two-week look-ahead, issued weekly. What is happening this week, what is happening next week, what each trade needs in order to start, and what we need from you. Most of the friction on a build comes from surprise rather than from difficulty, and a look-ahead removes the surprise.

Progress measured against the programme, not described. “On track” is not a report. Which activities are complete, which are in progress, which have slipped and by how much, and what that does to the critical path.

Procurement tracked as a live list. Ordered, confirmed, manufactured, delivered. Every item with a required-on-site date. This list is where most programme failures are visible weeks before they bite.

Decisions chased before they are late, against the decision schedule, with enough notice to actually decide rather than react.

Inspections booked ahead and the programme paused for them rather than working around them.

And a site meeting with a written record. Decisions taken, actions with owners and dates, and variations raised. The written record is what prevents the end-of-job disagreement about what was agreed in week nine.

Early warning

This is the highest-value thing programme management does, and it is the principle NEC4 is built around.

Raise the problem while there is still float to absorb it. A window with a six-week lead time that is going to be four weeks late is a problem you can resequence around if you know in week two. In week five it is a delay to completion.

That requires a culture where flagging a problem early is rewarded rather than treated as failure. Contractors who hide slippage until it is undeniable are not managing risk, they are deferring it onto you.

What we do with it: resequence where the logic allows, expedite where it is worth paying to, or tell you the completion date has moved and by how much. All three are better than finding out at handover.

And it works both ways. If you know a decision is going to be late, or a supplier you are dealing with directly has slipped, telling us early is worth far more than apologising later.

What you should expect to receive

A dependency-based programme at the start, including approvals, lead times and your decision dates — not a bar chart of trades.

A decision schedule, with dates.

A weekly two-week look-ahead.

A monthly programme update against actual progress, showing where the critical path now runs.

A live procurement list with required-on-site dates and current status.

Minutes of every site meeting, with actions, owners and dates.

Written variations priced with their programme effect stated, before the work happens.

And honesty about the date. A contractor who agrees to a completion date they cannot meet is not doing you a favour. We would rather have the difficult conversation at tender than in the week you were meant to move in.

Frequently asked questions

What is a two-week look-ahead?

A short weekly document showing what is happening this week and next, what each trade needs in order to start, and what is required from the client. It is the single most effective tool for reducing friction on a site, because most of that friction comes from surprise rather than from anything being difficult — a decision nobody knew was needed, or a trade arriving before the previous one has finished.

How often should I get a programme update?

A look-ahead weekly and a full programme update against actual progress monthly on a residential build, more often on a fast or complex one. The update should show what has slipped, by how much, and where the critical path now runs — because the critical path moves as a job progresses. A programme that has not been revised since week one is not tracking anything.

What is early warning and why does it matter?

Raising a problem while there is still time to absorb it. A long-lead item running four weeks late is something you can resequence around if you know in week two; in week five it is a delay to completion. It requires a working relationship where flagging problems early is treated as good management rather than as failure — which is exactly the principle NEC4 contracts are built around.

What is a decision schedule?

A list of every selection the client has to make and the date each is needed for the programme to hold — finishes, fittings, sanitaryware, colours, anything that cannot be ordered or installed without a choice. Late decisions convert directly into standing time, which is the most expensive form of delay because nothing is being produced. It is the most effective single tool for keeping a build on time.

Who tracks long-lead items?

The contractor or project manager should, as a live list with required-on-site dates and current status against each item. Windows, cupboards, stone tops, specialist tiles and switchgear all have lead times measured in weeks, and they are routinely ordered when the programme reaches them rather than when the job starts. That list is where most programme failures become visible weeks before they actually bite.

What happens when the programme slips?

It gets assessed against the critical path, because not every slip moves the completion date. Where it does, the options are resequencing if the logic allows, expediting if it is worth paying for, or accepting a revised date — and you should be told which of those applies rather than reassured. Where the cause is a client change, late decision or late approval, that is usually a contractual entitlement to an extension of time, which is another reason to have a proper contract.

Related reading

• Programme vs schedule: what your PM manages
• Timeline of a new home build
• Site establishment, day 1
• Construction project management