Do small industrial contractors need to submit a tender programme?
- Aug 9, 2025
- 10 min read
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
Whether a small industrial contractor needs to submit a tender programme depends on which of three situations the bid sits in. Where the invitation to tender requires one, submission is mandatory, and a missing programme can make the bid non-compliant before anyone reads the price. Where the programme is scored in the quality evaluation, it is effectively mandatory, because submitting without one hands marks to every competitor who included theirs. Only where the programme is neither required nor scored is it genuinely optional, and that is the situation where most small contractors get the decision wrong, because the strongest reason for building a tender programme has nothing to do with the evaluator at all.
It is about the price.
A mechanical, civil or electrical contractor pricing a package without building the programme is guessing at every time-related cost 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 industrial packages, where time-related costs routinely run to a quarter or a third of the package value, the guess is the single 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 properly: when a tender programme is required, when it is effectively required, and when it is genuinely a choice. Then it makes the case the question usually misses, which is that the programme is a pricing instrument before it is a submission document, and the contractor who builds one protects the bid they win as much as the bids they chase.
When a tender programme is required, scored or genuinely optional
The contractual position first, because it is simpler than most bid teams assume.
NEC itself does not require a tender programme. Clause 31 governs the programme submitted after the contract is in place: either a programme identified in the Contract Data at tender award, or a first programme submitted within the period stated after the starting date. 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 is a non-compliant bid, and on public sector and major industrial procurements, non-compliance is grounds for exclusion before evaluation begins. The contractor who treats a mandatory programme as optional is not taking a commercial position; they are disqualifying themselves quietly.
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 the most common situation on NEC frameworks and sub-packages under the current procurement regime, and it is mandatory in everything but name. A bid without a programme can still be submitted, but it concedes the programme-related quality marks to every competitor, and on evaluations weighted sixty or seventy per cent to quality, conceded marks decide outcomes more often than price does.
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 the situation where small contractors 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.
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 specific cost lines in every 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 plant guesses are nearly always optimistic because the person guessing is picturing the work going well.
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, which is the same discipline that protects the contractor later under the contract: the article on time risk allowances in NEC covers why declared allowances are the only risk provision the contract protects. 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.
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 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.
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.
Under NEC, the contractor either identifies a programme in the Contract Data or submits one within the stated period after the starting date, and the clause 31 acceptance process then determines 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 eighty per cent 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, the busiest fortnight of the project, which is precisely how first submissions end up late, thin, and rejected.
The downstream consequences run further than acceptance. The accepted programme is the baseline for every compensation event assessment, the reference for progress, and the foundation of the commercial protection covered in the hidden cost of weak planning. 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.
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 is typically sixty to a hundred and fifty activities, built in a day or two by someone who knows the work. 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 usually own 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 where time-related costs run to hundreds of thousands of pounds, is not an overhead question. It is the cheapest insurance in the tender.
The bid you should worry about is the one you win
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 approach, yes in everything but name. And 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, the risk inside the durations: every one of them is either calculated from a programme or guessed without one, and the guess does not disappear because nobody asked for the document. It just travels into the price, unexamined, and waits.
A lost bid costs a few days of tender effort. A won bid priced on guessed time costs margin every week until completion, 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.
FAQ
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 omission concedes marks. Only where it is neither required nor scored is it a genuine choice.
Does NEC require a programme at tender stage?
No. Clause 31 governs the programme after contract: either one identified in the Contract Data or a first programme submitted within the stated period after the starting date. Tender-stage requirements come from the invitation to tender and the instructions to tenderers. A tender programme identified in the Contract Data can, however, become the first contractual programme, which is one more reason to build it properly.
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 most small mechanical, civil or electrical packages that is sixty to a hundred and fifty activities, 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, every one of those is 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?
It becomes the foundation of 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, which means earlier acceptance and earlier commercial protection. A contractor who priced without one starts from a blank file in the busiest fortnight of the project.
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 BSc 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.
