Do small industrial contractors need to submit a tender programme?
Updated: 18 hours ago
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
Small industrial contractors need to submit a tender programme when the invitation to tender requires one, and in practice when the quality evaluation scores delivery or the programme. Where neither applies it is optional, but still worth building, because the tender programme sets the durations that every time-related cost in the price depends on.
The first two cases answer themselves. A missing programme can make a bid non-compliant, and leaving out a scored one throws away marks that every competitor who included theirs can earn. The third case, where nobody has asked, is where the programme is easiest to skip, and where the strongest reason for building one has nothing to do with the evaluator. It is about the price.
A mechanical, civil or electrical contractor pricing a package without building the programme is guessing at the time-related costs in the bid. How long the site establishment runs. How many weeks the crane is on hire. Where the labour peaks and what the peak costs. How much risk sits in the durations and whether the price carries provision for it. These are not estimating questions that a programme later confirms. They are programme questions that the estimate depends on, and a contractor who answers them by feel rather than by logic is submitting a price built on guesses about time. On an industrial package, where preliminaries, plant and supervision make up a large part of the price, that guess can be the largest unexamined risk in the bid.
The most expensive outcome for a small contractor is not a lost bid. It is a won bid priced on guessed durations. The lost bid costs the tender effort. The mispriced win costs real money for the entire delivery period, and the contractor discovers the cost slowly, month by month, as the prelims run longer than the allowance and the plant stays on hire past the date the price assumed.
This article answers the question in the title: what a tender programme is, when it is required, when it is effectively required and when it is genuinely a choice. Then it makes the case the question usually misses: the programme is a pricing instrument before it is a submission document. It follows the programme through the tender period and past award, where it either becomes the contract baseline or has to be turned into the clause 31 programme. A checklist to run before the programme goes in is at the end.
What is a tender programme?
A tender programme is the programme a contractor builds while bidding for work. It shows how and when the works would be carried out if the bid wins: the sequence, the durations, the key dates and the time assumptions behind the price. It is prepared for the tender documents, before any contract exists.
The CIOB's Code of Estimating Practice, in its seventh edition of 2009, called it the tender works programme. It described a programme drawn from the overall strategy for the job and the information available at tender, to be prepared as a critical path network. It should not be relied on for construction, the code said, though it can be the basis of the master programme.
Its level of detail follows the tender documents and the size of the job. On a small package it can be an outline programme of a page or two. On a framework call-off the documents may ask it to show what clause 31.2 of the NEC4 ECC asks of a programme submitted for acceptance, in the software the client names. Either way it is a plan of the works. That sets it apart from two other schedules in the same bid: the bid team's own plan for producing the tender, and the client's timetable for clarifications, tender return and award.
It often goes in with a narrative, the written account of the sequence and its risks that evaluators read alongside the bars, which is the subject of why your programme narrative is the part evaluators actually read.
When a tender programme is required, scored or genuinely optional
The contractual position first, because it is simpler than it looks.
NEC itself does not require a tender programme. Under the NEC4 ECC the programme provisions start at the Contract Date. Either the Contract Data identifies a programme, which is then the Accepted Programme, or clause 31.1 has the Contractor submit a first programme for acceptance within the period the Contract Data states. The tender-stage requirement, where it exists, comes from the procurement documents, not from the contract form. This distinction matters because it tells you where to look. The answer to "do we need to submit one" is in the invitation to tender, the instructions to tenderers, and the quality submission requirements, and it lands in one of three places.
The first situation is the explicit requirement. The ITT lists a tender programme among the mandatory submission documents, sometimes with a prescribed format, level of detail, or software. Here the question answers itself. A missing programme makes the bid non-compliant. When a contracting authority runs a competitive tendering procedure for a public contract at or above the threshold, section 19 of the Procurement Act 2023 lets it disregard a tender that breaches a procedural requirement in the tender notice or tender documents. That term includes a requirement to provide information. Below the threshold, and on private work, the client's own tender rules apply, and they can reserve the same right. The contractor who treats a mandatory programme as optional is not taking a commercial position. They are handing the client a reason to set the bid aside.
The second situation is the scored submission. The programme is not listed as mandatory, but the quality evaluation criteria include delivery approach, programme confidence, methodology, or mobilisation planning, and the tender programme is the document that carries those marks. This is common on NEC frameworks and sub-packages, and it is mandatory in everything but name. A bid without a programme can still be submitted, but it scores nothing on the programme criteria while every competitor who included one can score, and on an evaluation weighted towards quality, those lost marks can outweigh a sharper price. What those criteria test since the Procurement Act 2023 took effect is set out in how UK contractors win NEC tender bids.
The third situation is the genuinely optional case. Smaller packages, some private sector work, informal quotation processes where the enquiry asks for a price and a lead time and nothing more. No requirement, no scored criteria, no evaluator expecting logic links. This is where small contractors are tempted to conclude the programme is unnecessary effort, and it is exactly here that the pricing argument should decide the question instead, because the evaluator was never the main beneficiary of the tender programme in the first place.
Whichever situation applies, the contract fixes one thing the programme should test before the bid goes in: the Completion Date, which the Contractor signs up to, with delay damages under Option X7 where the contract includes it. The client can state it in Contract Data part one, or leave the bidder to decide it in part two. Either way, the tender programme is how a bidder finds out whether the date can be met before agreeing to it.
One boundary worth drawing before going further. How the tender programme functions as evidence, why evaluators trust a logic-linked programme over a narrative of experience, and how smaller contractors close that gap against larger competitors, is the subject of winning NEC bids as a small or specialist contractor. That is the external case, and it stands on its own. What follows here is the internal case, the half of the argument that has nothing to do with who reads the bid.
What a tender programme is actually for
Strip away the submission question entirely. Assume nobody outside the business will ever see the document. The tender programme still earns its cost, because it is the instrument that converts the scope into a price the contractor can stand behind.
Four cost lines in an industrial bid are programme outputs, whether or not a programme was built to produce them.
Durations drive the preliminaries. Site establishment, supervision, welfare, access equipment, temporary services: every week the package runs is a week of prelims, and the prelims allowance in the price is a direct function of how long the programme says the work takes. A contractor who prices prelims on a round-number duration ("call it sixteen weeks") has set the largest time-related cost in the bid by instinct. A contractor who builds the sequence and reads the duration off the logic has set it by calculation. When the instinct is two weeks short, the difference comes straight out of margin at roughly the weekly prelims rate, every week, until the work finishes.
Sequence drives the plant. Crane hire, MEWPs, temporary works, test equipment: these cost by the period on hire, and the period on hire is set by where the activities that need them sit in the sequence. A programme that shows the crane needed for weeks three to nine prices seven weeks of crane. No programme prices a guess, and guesses about time tend to be optimistic, because the person guessing is picturing the work going well. HM Treasury's guidance on optimism bias asks public sector appraisers to correct for that tendency in project durations as well as costs.
Resource peaks drive the labour cost. The same total hours cost different amounts depending on how they fall. A sequence that stacks three trades into the same fortnight prices differently from one that runs them consecutively: travel and subsistence for a peak gang, supervision ratios, productivity loss from congestion, premium time to hold dates. The resource profile only exists once the sequence exists. Without it, the labour price assumes a smooth profile that the real job will not deliver.
Float decisions drive the risk pricing. Where the durations carry provision for the contractor's own risk, the price needs to know it, and where they do not, the price needs to carry it elsewhere. A tender programme built with visible, reasoned allowances tells the estimator exactly what risk the durations already absorb. It is the same discipline that protects the contractor later. The article on time risk allowances in NEC covers why the contract expects time risk allowances to be shown on the programme, and why risk hidden in padded durations is harder to defend. At tender stage the point is simpler. Risk priced twice loses the bid. Risk priced never loses the margin. The programme is how you find out which one the estimate is doing.
Figure 1 shows an example: a tender programme for a typical small industrial package, with the four cost lines read off it on the same weeks.
Run those four together and the conclusion is hard to avoid. The tender programme is not a document produced to accompany the price. It is the calculation the price comes from. The CIOB's 2009 code made the same link: where the tender documents set no contract period, it took the duration from the tender works programme and put the time-related site costs for that duration into the tender. The contractor who skips it has not saved the planning effort. They have moved the same questions into the estimator's head and accepted whatever answers instinct supplies. On a package where time-related costs are thirty per cent of the value, that is thirty per cent of the bid priced by feel.
What proportionate looks like for a small industrial package
The objection small contractors raise is proportionality, and it is a fair one. A £2 million M&E package does not need a two-thousand-activity programme, and nobody is suggesting it does.
A proportionate tender programme for a small industrial package can often be built in a day or two by someone who knows the work, in sixty to a hundred and fifty activities. It carries the contract dates and any sectional or interface milestones the enquiry identifies. It shows the real sequence with logic links, not a list of bars drawn to look right. It includes the procurement chain for long-lead items, because on industrial work the equipment deliveries often drive the critical path. It shows testing and commissioning as actual scope with actual durations rather than a single bar at the end. It carries visible, reasoned time risk allowances where the contractor-risk exposure sits. And it is resourced at least to the level of gang sizes and key plant, because that is the level the price needs.
That is the whole specification. The tool matters less than the logic: P6 where the client ecosystem expects it, other scheduling tools where it does not, but built on linked logic either way, because logic is what makes the durations and the costs derivable instead of decorative. For contractors who do not carry this capability in-house, the build is a bounded piece of external work at a cost a single bid can absorb. The article on remote planning support covers how smaller contractors access it without standing overhead.
A day or two of structured planning, against a bid whose time-related costs can run to hundreds of thousands of pounds, is not an overhead question. It is the cheapest insurance in the tender.
NEC Planning Solutions builds tender programmes from the scope and tender documents you already hold, at a fixed fee or an agreed upper limit, confirmed in writing before chargeable work begins. A logic-linked tender programme starts from £1,500 plus VAT, and from £2,500 plus VAT it comes with the narrative, the phasing and support at clarification. Either way it is structured to become the construction baseline after award. The tender programme service sets out what is included.
Tender planning: where the programme fits in the tender process
Tender planning is the planning work done while a bid is prepared: reading what the tender documents ask the programme to show, choosing the method and sequence, building the tender programme, and feeding its durations into the price and its sequence into the quality answers. On a large bid a tender planner does it. On a small one it often falls to the estimator or a contracts manager, alongside everything else.
The order matters more than the effort. The programme has to exist before the price is adjudicated, because the price depends on it, and before the quality answers are written, because they describe it. Built last, it gets drawn to fit a price already set, which is the outcome this article argues against. Table 1 sets out the programme work at each stage of a typical tender.
Stage of the tender | The programme work |
Selection, before the invitation to tender | Usually none, beyond evidence of planning capability |
Invitation to tender | Find what the programme must show, in what format, and whether it is required or scored. Note the Completion Date, Key Dates, access dates and whether the Contract Data can identify a programme |
Clarifications and site visit | Test what the programme assumes: access, outages, working hours and client-supplied items. Ask before the clarification deadline, and expect the answers to go to every bidder |
Preparing the bid | Build the logic-linked programme first, then price from it: durations for the prelims, hire periods for the plant, peaks for the labour and allowances for the risk |
Submission | Submit it in the required format, checked against the price, the method statements and the narrative |
Post-tender clarification and interview | Defend it, and revise it with the price if the scope or dates change |
Award | Identified in the Contract Data, it is the Accepted Programme from the Contract Date. If not, it can be the starting point for the first programme submitted for acceptance |
Table 1: the programme work at each stage of a typical tender, with NEC4 ECC terms at award.
Tender programme vs clause 31 programme
A tender programme is the bidder's plan for the works, judged against the tender documents before any contract exists. A clause 31 programme is the first programme the Contractor submits for acceptance under the NEC4 ECC once the contract is in place, and it has to show everything clause 31.2 lists. Where the Contract Data identifies the tender programme, it is the Accepted Programme from the Contract Date and nothing is submitted under clause 31.1.
Under the NEC4 ECC | Tender programme | Clause 31 programme |
When | During the tender period | Within the period after the Contract Date that the Contract Data states (31.1) |
What it must show | Whatever the tender documents ask for | Everything clause 31.2 lists, in the form the Scope states |
Who judges it | The client's evaluation panel, for compliance or a score | The Project Manager, who accepts it or gives reasons within two weeks (31.3) |
Contract status | None, unless the Contract Data identifies it | The Accepted Programme once accepted (11.2(1)) |
What it is used for | Winning the work and setting the price | Assessing delay from compensation events (63.5) and measuring progress |
If it is missing | A non-compliant bid, or the programme marks lost | A quarter of the Price for Work Done to Date retained until a compliant first programme is submitted (50.5), and compensation events assessed on the Project Manager's own view of the programme (64.1, 64.2) |
Table 2: the tender programme and the first programme for acceptance under an NEC4 ECC, where the Contract Data identifies no programme.
The route is set by the tender documents. Where Contract Data part two has room for the Contractor to identify a programme, and the tender programme is named there, it is the Accepted Programme from the Contract Date. Clause 11.2(1) defines the Accepted Programme as the programme identified in the Contract Data until the Project Manager accepts a later one. There is no first submission, no two-week wait and no clause 50.5 retention.
Where no programme is identified, clause 31.1 has the Contractor submit a first programme for acceptance within the period the Contract Data states, and clause 31.3 gives the Project Manager two weeks to accept it or give reasons. Until a first programme showing the information the contract requires is submitted, clause 50.5 retains a quarter of the Price for Work Done to Date, which the guide to NEC assessment dates works through in cash terms. On a two-stage tender let with a separate pre-construction services agreement, the programme built in the first stage takes the same routes, as the PCSA guide explains.
The risk runs the other way as well. A tender programme named in the Contract Data is never submitted for acceptance, so the Project Manager's check under clause 31.3 never happens. Whatever it shows, or leaves out, is the programme compensation events are assessed against until the Project Manager accepts a revised one (63.5). From then on the Accepted Programme is kept current through clause 32 revisions.
Other forms draw the same line in their own terms. Under the JCT Standard Building Contract 2016 the contractor provides its master programme as soon as possible after the contract is executed, unless it has provided one already. The 2017 FIDIC books want the initial programme under Sub-Clause 8.3 within 28 days of the Contractor receiving the Notice of the Commencement Date.
The second life of the tender programme
The programme built at tender does not retire at submission. On a won bid, it becomes the most valuable document the contractor owns at the moment they can least afford to produce it from scratch.
Where the Contract Data does not identify it, the clause 31 acceptance process decides whether the contractor has a working Accepted Programme or months of resubmission while the job runs unprotected. A contractor who built a real tender programme starts that process with most of the work done. The logic exists, the sequence has been thought through, the durations were derived rather than guessed, and the first contractual submission is a development of work already in hand. A contractor who priced without a programme starts from a blank file during mobilisation, while the period for the first programme is already running, which is how first submissions end up late, thin and rejected.
The consequences run further than acceptance. The Accepted Programme is the baseline for assessing delay from compensation events, the reference for progress, and the foundation of the commercial protection covered in why specialist contractors lose margin on NEC jobs. For a small contractor without an in-house planning function, the tender programme is the one moment where planning effort was going to be spent anyway. Spending it properly means the delivery phase inherits a working foundation instead of a gap. The article on pre-construction planning covers how that foundation becomes the delivery controls system.
The view from the desk
My position is simple. Build the tender programme before the price is adjudicated, on every package, including the ones where nobody asked for it. When the estimator can point at the bar behind each time-related line in the price, the price can be defended at clarification and held after award. When nobody can, the number is a hope.
I would also rather see eighty honest activities than eight hundred decorative ones. An evaluator can test eighty, an estimator can price from them, and a planner can turn them into the first programme for acceptance in days rather than weeks. Size is not the measure of a tender programme. Logic is.
And where the tender documents leave room in Contract Data part two to name a programme, I would name it only when it already shows what clause 31.2 asks for, updated to the expected award date. Named, it saves the first submission and keeps clause 50.5 out of the picture. Named while it is thin, it is the baseline for every compensation event until a revised programme is accepted, and that is a harder problem than a two-week acceptance period.
Summary
So, do small industrial contractors need to submit a tender programme? Where the ITT requires one, yes, without discussion. Where the quality evaluation scores delivery or the programme, yes in everything but name. Where it is genuinely optional, the honest answer is that submission was never the real question. The tender programme exists to make the price true. The durations behind the prelims, the hire periods behind the plant, the peaks behind the labour and the risk inside the durations are either calculated from a programme or guessed without one, and the guess does not disappear because nobody asked for the document. It travels into the price, unexamined, and waits.
After award the same programme either becomes the Accepted Programme, where the Contract Data identifies it, or gives the clause 31 submission a head start. A lost bid costs a few days of tender effort. A won bid priced on guessed time costs margin every week until the job is finished, and small industrial contractors run on margins that cannot fund the difference. Build the programme for the evaluator when the rules require it. Build it for yourself every other time.
Download the tender programme checklist
A two-page check to run before the programme goes in with the bid: what the tender documents ask for, the dates and constraints, the logic and durations, whether the price and the programme agree, and what happens after award under the NEC4 ECC. Direct download, no sign-up.
Tender programme: frequently asked questions
What is a tender programme?
A tender programme is the programme a contractor prepares while bidding for work. It shows how and when the works would be carried out if the bid wins: the sequence, durations, key dates, procurement and testing, and the time assumptions behind the price. It is judged against the tender documents and has no contractual status unless the contract identifies it, as NEC4 ECC Contract Data part two can.
Do small contractors have to submit a tender programme on NEC bids?
It depends on the procurement documents, not on NEC itself. Where the invitation to tender lists a programme as a mandatory submission, yes, and a missing programme can make the bid non-compliant. Where the quality evaluation scores delivery approach or programme confidence, it is effectively mandatory because omitting it gives up those marks. Only where it is neither required nor scored is it a genuine choice.
Does NEC require a programme at tender stage?
No. Under the NEC4 ECC the programme provisions start at the Contract Date. Either the Contract Data identifies a programme, which is then the Accepted Programme (11.2(1)), or clause 31.1 has the Contractor submit a first programme within the period the Contract Data states. Any tender-stage requirement comes from the invitation to tender, which can ask for a programme to be identified in Contract Data part two at award.
What is the difference between a tender programme and a clause 31 programme?
The tender programme is the bidder's plan, made before any contract exists. The clause 31 programme is the first programme submitted for acceptance under the NEC4 ECC after the Contract Date. It shows everything clause 31.2 lists, and the Project Manager accepts it or gives reasons within two weeks. Where the Contract Data identifies the tender programme, it is the Accepted Programme and no first programme is submitted.
What should a tender programme include for a small industrial package?
Contract dates and interface milestones, a logic-linked sequence, the procurement chain for long-lead items, testing and commissioning shown as real scope, visible time risk allowances where contractor-risk exposure sits, and resourcing to gang and key-plant level. For many small mechanical, civil or electrical packages that is sixty to a hundred and fifty activities, which can often be built in a day or two.
Is a tender programme worth it if the client has not asked for one?
Yes, because the programme is a pricing instrument before it is a submission document. Durations set the prelims, sequence sets the plant hire periods, resource peaks set the labour cost, and float decisions set the risk pricing. Without the programme, those lines are priced by instinct. The most expensive bid a small contractor submits is the one they win at the wrong price.
What happens to the tender programme after the contract is won?
Under the NEC4 ECC it is the Accepted Programme from the Contract Date if the Contract Data identifies it. If not, it can be the starting point for the first programme submitted for acceptance under clause 31. A contractor with a real tender programme starts mobilisation with the logic, sequence and durations already built, so acceptance, and the commercial protection it brings, come sooner.
What is tender planning?
Tender planning is the planning done while a bid is prepared: reading what the tender documents ask the programme to show, choosing the method and sequence, building the tender programme, and feeding its durations into the price and its sequence into the quality answers. A tender planner does it on large bids, and an estimator or contracts manager often does it on small ones.
About the author
Roman Bazelchuk is the Founder of NEC Planning Solutions Ltd, a UK project planning and controls consultancy supporting contractors with NEC programme compliance, compensation event assessments and live project controls. He is an NEC Accredited Project Manager and holds the APMG Project Planning and Control qualification, with a BEng in Mechanical Engineering and postgraduate training in Planning and Control.
NEC Planning Solutions provides contract-aware planning support through a QA-governed delivery model, helping project teams keep programmes accepted, current and commercially useful from tender through to live delivery.
Pricing a package and the programme does not exist yet?
If the ITT requires a tender programme the team cannot produce in-house, if the quality submission needs a programme and narrative that will score, or if the price is being built on round-number durations that nobody has tested against a sequence, specialist tender programme support builds the logic-linked programme the bid needs at a cost a single tender can absorb.
