Planning advice for contractors

A PCSA, or pre-construction services agreement, pays a contractor for defined services before the main contract is awarded. Law firms cover its scope, fees and termination. This guide covers the contractor's obligations from the planner's side: the programme built under it, the standard forms from JCT and NEC4, Option X22, the three routes for that programme at contract award under NEC4, and what to write into the services schedule before signing.

NEC4 Option A and Option C both price the works in an activity schedule, and there the resemblance ends. One pays for completed activities and leaves the overrun with the Contractor. The other pays forecast Defined Cost plus the Fee and settles the risk through the share at Completion. This guide sets them side by side through the programme: what each pays, what each asks of the programme, how compensation events land and where each one goes wrong.

The client asks for a recovery plan. Somebody compresses the bars until the end date fits and issues it. That document is not a recovery plan, it is the same programme with less air in it, and everyone knows it within a fortnight.

FIDIC does not ask anyone to approve the programme. It asks the Engineer to review it, and gives a period in which to object. Let the period pass and a Notice of No-objection is deemed given, so the defined Programme exists whether anybody meant to create one or not. This guide covers what Sub-Clause 8.3 of the 2017 books requires, how the review works, and when and how the programme is revised.

Data cut-off on the 25th, report issued around the 5th, discussed mid-month. A decision taken on the 15th rests on information that was already three weeks old when it was read. Nobody is hiding anything. The loop is simply longer than the rate at which the job changes.

Most of the commentary on PPN 026 has led with the 20 per cent weighting. It is the wrong headline. What changed is that the menu is gone, and that on the larger contracts the commitment you write becomes a KPI somebody publishes and reports on every year.

The JCT Standard Building Contract asks for a master programme under clause 2.9, leaves critical paths optional in the Contract Particulars, and only requires an update when you apply for an extension of time. The Design and Build form does not expressly require a programme at all. None of that changes what a retrospective claim has to prove. This is the gap between the contractual floor and the evidential bar, and what to keep so the claim stands up.

The notice says not accepted, and what happens next decides more than the fate of one submission. This playbook covers the moment in full: the four reasons Clause 31.3 permits and why they are the only four, the detail a notice must give you under Clause 13.4, the triage that sorts right from wrong from unclear, when withholding acceptance becomes a compensation event under 60.1(9), and the cost of drifting while the Accepted Programme goes stale.

Most contractors prepare NEC programmes for submission. The strongest contractors prepare them for review. The difference is whether the planning team knows what the project manager actually checks, in what order, and what triggers rejection at each step. This article walks through the review sequence as the project manager experiences it: the first thirty seconds, the structural integrity pass, the clause 31.2 information check, the realism test, and the scope compliance che

NEC requires mitigation but cannot impose acceleration. Most contractors confuse the two. Contractors who mitigate when they should be quoting for acceleration give away recovery work the contract entitles them to be paid for. Contractors who refuse to mitigate lose entitlement because the assessment assumes they would have mitigated anyway. This is the practical guide to understanding where the line sits and how to protect the commercial position on both sides of it.

A programme that has lost integrity does not announce itself. It looks exactly like one that works. The problems only surface when a compensation event tests it and the programme cannot answer the one question the NEC contract keeps asking. This article describes five signs any project director can check in ten minutes, without specialist planning knowledge, to know whether the programme is protecting their commercial position or quietly giving it away.

Most contractors submit programme revisions that update progress, move the data date forward, and miss everything else clause 32 requires. The project manager receives a schedule that shows where the job is but not what the contractor is doing about it. That is not a revision. It is a progress snapshot. This article explains what a clause 32 programme revision actually needs to contain, why most revisions are rejected, and what to do when the project manager is deliberately a

Primavera P6 is the industry-standard scheduling tool on major UK construction projects. It is also an opinionated one. Its defaults were shaped by contracts that work very differently from NEC, and a P6 schedule built to generic best practice will usually look fine on the surface and fail at the moments that matter most. This is the complete contractor guide to Primavera P6 for NEC programmes.

Most contractors treat clause 31 as a procedural hurdle to clear at the start of the job. Submit the programme, wait for acceptance, move on. That approach quietly hands commercial control to the project manager. This article explains what the accepted programme actually protects, how the deemed acceptance mechanism works, and why a programme that was accepted at mobilisation provides almost no commercial protection by month six.

For mechanical, electrical, civil, groundworks and fit-out contractors, the accepted programme often only becomes important when change or delay lands on a programme that no longer reflects the live job. This article explains why that drift matters under NEC and how programme protection is often lost by degrees, not all at once.

Many specialist subcontractors run NEC packages without a full planning team. The issue is not team size. It is whether the programme stays live, current and commercially usable while the job is moving.

Time Risk Allowance and terminal float both create breathing space in an NEC programme. That is why contractors often confuse them. But they sit in different places, serve different purposes, and blurring the line between them weakens programme acceptance, distorts the update cycle, and makes compensation event assessments harder to defend. This article explains what each one actually is, how they connect without being the same, and why keeping the distinction clean matters c

Clause 15 only works when early warnings trigger decisions and programme movement. Here’s a quantified register method and weekly rhythm you can run on real jobs.

There is a four-to-twelve-week window between contract award and site mobilisation that the contractor's commercial outturn depends on more than any other stage of delivery. It is unremarkable in most calendars and rarely discussed at board level. Yet what gets set up during this window will determine, more than any subsequent decision, whether the project's commercial position is defensible at month eighteen. Pre-construction is not preparation.

Excel is not a planning tool. It is a calculation tool with planning-shaped output. NEC contracts are built on logic recalculation. The seven recurring pitfalls of Excel programmes on NEC projects are not seven separate problems with seven separate fixes. They are seven symptoms of one structural mismatch between the category of tool and the category of contract. This is the complete analysis: why Excel cannot perform the contractual functions.