Understanding Construction Programmes

Introduction

The construction programme is not just a scheduling tool — it is the single most important commercial document on a construction project. For the quantity surveyor, the programme drives interim valuations, delay claims, compensation events, cost forecasting, cash flow management, and preliminary cost assessment. If you have read our article on Programme & Scheduling, which covers scheduling fundamentals — Gantt charts, critical path method, scheduling software — this article picks up where that leaves off. It focuses on how the QS reads, interrogates, and relies on the programme for commercial decisions throughout the project lifecycle.

Why the Programme Matters Commercially

Every major commercial function the QS performs is anchored to the programme. Interim valuations are assessed against it — the QS cross-references the contractor’s payment application against programmed progress to validate whether the claimed value is consistent with work actually completed. Delay claims require a credible baseline programme — without one, the contractor cannot demonstrate which events caused which delays, and the QS cannot assess the claim. Compensation events under NEC4 are assessed against the accepted programme, making programme acceptance a prerequisite for the entire commercial management process. Cost forecasting depends on the programme to project cash flow, anticipate final account, and identify risks such as acceleration or resequencing. And preliminary costs — site management, plant hire, welfare, insurances — are directly tied to programme duration: every week the programme extends, time-related preliminaries increase.

Reading a Programme as a QS

When a contractor submits a programme, the QS should evaluate it through a commercial lens, not just a planning one. The key elements to examine are the critical path (the longest sequence of activities with zero float, which determines the completion date), float (the time available for activities to slip without affecting completion), logic links (the dependencies between activities — do they reflect realistic construction sequencing?), milestones and key dates (practical completion, sectional completion, design approvals, long-lead item deliveries), and resource loading (are the assumed labour and plant levels realistic for the scope of work?).

The QS should also know how to spot an unrealistic programme. A front-loaded programme compresses the majority of work into the first third of the project — this is rarely sustainable and signals that the contractor may be trying to secure cash early through inflated interim valuations. A back-loaded programme defers most work to the final stages, creating acceleration risk and cash flow stress. Missing logic — activities with no predecessor or successor — indicates a hastily prepared programme that is unlikely to reflect actual site conditions. Excessive float across the majority of activities suggests either padded durations or missing dependencies. In all these cases, the QS should recommend rejection or revision before accepting the programme as a commercial baseline.

The Programme Under JCT

Under standard JCT contracts, the programme is not a contract document. It is informational — the contractor submits it, and the architect or Contract Administrator may review it, but it has no formal contractual status. The contractor’s obligation is to proceed regularly and diligently (Clause 2.1), not to comply with a specific programme. This means the QS cannot hold the contractor to programmed dates in the same way as under NEC4.

Nevertheless, the programme remains a critical commercial tool under JCT. The QS uses it to validate interim payment applications — comparing claimed progress against the programmed sequence to detect front-loading or over-valuation. The QS also uses it for cost forecasting, plotting cumulative spend against cumulative programme progress (S-curve analysis) to identify whether the project is tracking to budget. And if a delay dispute arises, the baseline programme becomes the reference point for delay analysis, even though it was never formally a contract document. For more on how interim valuations work in practice, see our article on Interim Valuations and Payment Applications.

The Programme Under NEC4

Under NEC4, the programme has full contractual status — and this changes the QS’s role fundamentally. Clause 31 requires the contractor to submit a programme for acceptance by the Project Manager within the period stated in Contract Data (typically two weeks from the starting date). The programme must show the order and timing of operations, dependencies, resources, float, and time risk allowances. The PM must accept or reject it; once accepted, it becomes the accepted programme — the baseline against which all compensation events are assessed.

Float under NEC4 belongs to neither party — it is consumed on a first-come-first-served basis. Time risk allowances, however, are owned by the contractor. When a compensation event occurs, the time impact is measured against the accepted programme: the question is whether the event moves planned completion, not whether it consumes the contractor’s float. This distinction is commercially significant and the QS must understand it to assess compensation event quotations correctly. For a detailed treatment of the NEC4 framework, see our article on NEC4 Engineering and Construction Contract Explained.

Many NEC projects run into commercial difficulty because there is no valid accepted programme — the PM has not formally accepted one, or the contractor has not submitted updates. Without an accepted programme, assessing the time impact of compensation events becomes extremely difficult and contentious. The QS should treat programme acceptance as a priority commercial issue and escalate immediately if it is not in place.

Programme and Interim Valuations

At each interim valuation, the QS should cross-reference the contractor’s payment application against the programme. The process involves marking up the programme — colour-coding activities as complete, in progress, or not yet started — and comparing the percentage of completed activities against the percentage of cost claimed. If the contractor claims 35% of the contract sum but the programme shows only 20% of activities complete, the QS must investigate whether this reflects genuinely high-value early work (mobilisation, foundations) or front-loading.

S-curve analysis is particularly useful. By plotting cumulative spend against cumulative programme progress month by month, the QS can identify divergences early. A spend curve that runs ahead of the programme curve signals that the contractor is claiming cost faster than work is being completed — a red flag for over-valuation that the QS should challenge before it compounds through subsequent valuations.

Programme and Delay Analysis

The programme is the foundation of every delay claim. The baseline programme provides the as-planned schedule against which actual progress is measured. The critical path identifies which activities determine the completion date — and only delays to critical activities entitle the contractor to an extension of time. The QS must be able to identify the critical path, understand how delay events affect it, and challenge claims where the delayed activity was not actually on the critical path.

The delay analysis methods set out in the SCL Delay and Disruption Protocol — as-planned vs as-built, impacted as-planned, time impact analysis, collapsed as-built, and windows analysis — all depend on a credible programme. Without a realistic, accepted baseline, the analysis lacks a foundation and the claim is difficult to substantiate or defend. For a detailed treatment of these methods, see our article on Delay Analysis and Extension of Time.

Programme and Cost Forecasting

The programme is the QS’s primary tool for projecting the final account. By mapping the remaining programme activities against their estimated cost, the QS can forecast cash flow, identify when peak expenditure will occur, and flag risks to the project budget. If the programme extends — whether through employer-risk events, contractor delays, or scope changes — the QS must immediately update the cost forecast to reflect the additional time-related preliminaries, inflation exposure, and potential acceleration costs.

Programme changes also reveal cost risks that may not yet have materialised as formal claims. If the contractor is resequencing work to recover time, the QS should anticipate disruption and efficiency losses. If activities are being compressed — shorter durations than originally planned — unit costs are likely to increase due to overtime, additional resources, or premium supply rates. The QS who monitors the programme proactively can forecast these impacts before they hit the final account.

Programme and Preliminaries

Time-related preliminaries — site management salaries, plant hire, welfare facilities, scaffolding rental, insurances, security — are directly linked to programme duration. Every week the programme extends, these costs continue. The QS must distinguish between fixed preliminaries (one-off costs such as site mobilisation and initial setup, which do not increase with duration) and time-related preliminaries (ongoing costs that scale directly with programme length, typically 60–70% of total preliminary cost). When assessing prolongation claims, only the time-related element is recoverable for the extended period. For more on how preliminaries are structured and priced, see our article on Preliminaries and General Items in Construction.

Common Programme Issues

No accepted programme (NEC4). This is the most serious commercial issue on an NEC project. Without an accepted programme, compensation events cannot be properly assessed, and the employer’s position is weakened in any dispute. The QS should escalate immediately.

Programme drift without formal revision. The contractor submits a baseline programme at the start but does not update it for months. Actual progress diverges from the plan, but there is no revised programme to measure against. The QS should require monthly programme updates and flag non-compliance.

Logic manipulation. Contractors may introduce artificial lead-lags or soft logic to compress the critical path or create float that does not exist in practice. Resource-loaded programmes are harder to manipulate than task-driven schedules — the QS should request resource loading where feasibility is in doubt.

Front-loaded payment applications. The contractor’s spend profile runs ahead of the programme. The QS should reconcile every application against the programme line by line and challenge over-valuation before it compounds.

Practical Tips

Insist on programme acceptance early. Under NEC4 this is contractually required. Under JCT, push for a formally agreed baseline anyway — it strengthens the employer’s position in any future dispute.

Maintain a programme mark-up at every valuation. Colour-code activities as complete, in progress, or not started. File it as part of the valuation record. This is evidence if progress is later disputed.

Create an S-curve from day one. Plot cumulative budget against cumulative programme progress monthly. If the actual curve diverges more than 10% from planned, investigate immediately.

Benchmark contractor durations. Compare programmed activity durations against CIOB guidance, industry norms, and the contractor’s own track record on previous projects. Challenge any activity that looks padded or unrealistic.

APC Relevance

Programme understanding falls within the RICS APC competencies of Contract Practice (using the programme for contract administration, interim valuations, and delay claims), Programming and Planning (reading and interpreting programmes, understanding critical path and float), and Project Financial Control and Reporting (using the programme for cost forecasting, cash flow projection, and preliminary cost management). APC candidates should be able to explain how the programme drives the QS’s commercial decisions, describe the difference between JCT and NEC4 programme status, and demonstrate how they have used the programme in interim valuations or delay analysis on a real project.

Further Reading on ProQS

Programme & Scheduling — the fundamentals of construction scheduling, Gantt charts, and critical path method.

Delay Analysis and Extension of Time — how the programme baseline supports delay claims and the analytical methods used.

NEC4 Engineering and Construction Contract Explained — the contractual status of the programme under NEC4 and how it drives compensation events.

Interim Valuations and Payment Applications — how the QS uses the programme to validate interim payment claims.

Key References

CIOB Guide to Good Practice in the Management of Time in Major Projects — the industry-standard reference for programme management on construction projects.

SCL Delay and Disruption Protocol (2nd Edition, 2017) — guidance on how the programme is used in delay analysis methodology.

Designing Buildings Wiki: Construction Programme — comprehensive UK-focused reference covering programme types, critical path, and float.

RICS Black Book — professional standards for contract administration and project financial control.

NEC Contracts — guidance on programme requirements under NEC4 Clauses 31 and 32.