The BMS Tender Process: A Step-by-Step Timeline From Enquiry to Submission

A BMS tender process typically takes a competent controls contractor 10–15 working days of internal effort from receipt of enquiry to submission — covering go/no-go review, take-off and measure, specification review, site survey, subcontractor and supplier pricing, controls schedule development, RFI issue and response, commercial risk review, internal checking, and document assembly. Complex, multi-system or fast-track projects can extend this to 4–6 weeks.

Every BMS tender we've ever returned late came down to the same root cause: someone underestimated how long one of the internal stages actually takes and tried to compress it. Not the headline "we've got three weeks to price this" figure everyone quotes — the actual mechanics underneath it. A controls schedule for a 12-floor commercial refurb with mixed AHU, FCU and chiller plant doesn't get built in an afternoon, and a subcontractor pricing a specialist interface (metering, fire interlock, generator changeover) doesn't turn a quote around overnight just because your deadline says so.

This is what the process actually looks like from the inside, stage by stage, with realistic timescales for each one, the risks that blow through them, and the difference between the hours a contractor actually works and the calendar time the whole thing takes.

How long does a BMS tender actually take?

For a straightforward single-building commercial project with a complete, coordinated M&E design, a competent controls contractor should budget 10–15 working days internally, spread across the fifteen stages below. Multi-system projects — plant replacement plus BMS integration, phased occupation, or anything with a fire strategy interface — routinely run 4–6 weeks once RFI cycles and specialist subcontractor lead times are factored in. If you want the client-facing headline figure most tender documents quote for return periods, that's covered in our BMS quoting and tendering FAQs — this article is about what has to happen internally to hit it.

The BMS tender process, stage by stage

These are typical, indicative ranges based on our own experience running BMS tenders — every project varies, and the only way to know actual figures for a specific job is to price it. Treat this as a planning benchmark, not a guarantee.

Four different clocks are running through all of this, and conflating them is where most tender programmes go wrong. Working hours are the actual desk and site time a contractor's own team spends — take-off, schedule building, checking. Supplier waiting time is subcontractor and panel-builder quote turnaround, which the contractor can chase but not compress — six to ten working days is normal, not a failure. RFI waiting time is however long a consultant or client team takes to answer a query, often a working week or more once every bidder's questions are pooled. And total elapsed tender period is the calendar span from receipt to submission — which is almost always longer than the sum of working hours alone, because supplier and RFI waiting time run in parallel with the contractor's own work rather than adding to it sequentially. A tender priced only against working hours, with no allowance for the other two clocks, is the single most common cause of a late or rushed return.

Tender receipt and go/no-go review

Before any of the technical work starts, someone has to decide whether the project is even worth pricing properly. That means a quick read of the scope, location, programme and return date against the business's actual capacity and risk appetite — not a full take-off, just enough to answer "can we resource this properly in the time given, and is it a project we want." Skipping this stage doesn't save time; it just moves the decision to week two, after real hours have already gone into a tender that was never going to be competitive or resourced properly in the first place.

Take-off and measure: 1–3 days

This is where a tender either starts on solid ground or starts leaking time it'll never get back. Take-off means going through the mechanical and electrical drawings point by point — every AHU, FCU, VAV box, chiller, pump, valve, damper actuator, meter — and building a raw points count and a first-pass device list. On a well-coordinated design with an accurate M&E schedule, this is a one- to two-day desk exercise. On drawings where the M&E consultant hasn't finished coordinating services, or where the points schedule is a generic template rather than a project-specific one, it stretches to three days and generates the first round of RFIs before pricing has even started.

The habit that saves the most time here: never take a client's stated points count at face value. We re-count from the drawings every time. A schedule that says "180 points" and a drawing set that actually shows 240 once you've walked the plant list is the single most common source of late-stage repricing panic, and it's avoidable if it's caught on day one instead of day twelve. Missing schematics or an unclear existing controls network — common on refurbishment enquiries — belong in this stage too: if the as-installed drawings don't match what's actually on site, that has to be flagged as a survey requirement rather than assumed away.

Site survey requirements

Take-off is desk-based; a site survey is not, and the two get conflated far too often. A survey needs to physically confirm what the drawings say, check the condition of any existing plant and controls network being retained or extended, and establish practical access constraints before they become programme risk: is there an up-to-date asbestos register the survey team needs sight of before opening any ceiling void or riser, is scaffold, a tower or a MEWP needed to reach plant safely, what inductions and permits does the site require before anyone gets access at all, and are ceilings and risers actually accessible or will builders' work be needed just to get a look. None of this is exotic — it's routine due diligence — but it's routinely skipped on a tight tender programme because survey access has to be arranged through a third party and doesn't happen on the contractor's own schedule. A site that only permits weekend or out-of-hours access can turn a one-day survey into a two-weekend exercise before take-off can even be finalised.

Specification review: 2–3 days

Once the points count is solid, the spec gets read properly — not skimmed for scope, but checked line by line against what's actually buildable and against the manufacturer platform being specified (Trend, Distech, Siemens, whichever), with the control strategy narrative reviewed alongside it to confirm the sequence of operations is actually coherent against the points list rather than boilerplate. This is where sensor accuracy, control strategy detail, and interface requirements either match the drawings or don't. CIBSE Guide H (2009), section 3.1.3.1, specifies that a sensor accuracy of 0.6 K over the 15–25°C range is suitable for zone air temperature measurement — specs that ask for tighter tolerances than that without a stated reason usually mean either the consultant has copied boilerplate from a previous project, or there's a genuine process requirement (a lab, a server room, a pharma cleanroom) that needs pricing differently. Either way, it's a question that has to go out as an RFI now, not discovered during commissioning.

Spec review also decides what actually needs a formal Request for Information versus what a controls engineer can reasonably infer and price with a stated assumption. Over-RFI-ing a tender slows everyone down and irritates the consultant; under-RFI-ing it means you've priced a guess. Getting that balance right is a judgement call that only comes from having sat through the commissioning fallout when it goes wrong.

Subcontractor, panel-builder and supplier pricing: 5–10 working days, run in parallel

This is the stage most programmes get wrong, because it's the one stage a contractor doesn't fully control. Panel builders, cabling subcontractors, and specialist interface suppliers (metering, BMS-to-fire-panel gateways, generator/ATS interfaces) all need the enquiry, the points schedule and enough of the spec to price accurately — and they're pricing several other people's tenders at the same time as yours. Panel-builder and controls-manufacturer pricing is worth tracking as its own line rather than lumping it in with general subcontractor enquiries: a panel build quote depends on a settled panel schedule or single-line diagram, which often isn't ready until the controls schedule itself is well underway, so it's frequently the last quote back rather than the first. Six to ten working days is a realistic average turnaround for a subcontractor or panel-builder RFQ on a project of any complexity, which is why this stage has to start the moment take-off is confident enough to issue enquiries, run fully in parallel with spec review and RFI issue, and never be left until the schedule is "finished" before anyone outside the business sees it.

The programme risk here isn't pricing arithmetic — it's chasing. A panel builder who goes quiet for four days on a tender due in two weeks is the difference between a submitted return and a late one, and it's the reason we run supplier pricing as a tracked, chased process rather than a fire-and-forget email. It's also why the lead time on every controller, panel and long-lead device has to be confirmed in writing with the actual supplier at this stage rather than assumed from the last job — we cover what that looks like in practice, especially for London sites, in our guide to BMS lead times and delivery risk.

Controls schedule and points list: 2–4 days

The controls schedule is the technical backbone of the return — every point, every strategy, every interface, mapped against the device list and priced individually. On top of the raw points count from take-off, this stage adds control strategy narrative, graphics scope, and — critically — the interface schedule: what's a hard-wired input, what's BACnet or Modbus, what needs a gateway, what's someone else's scope entirely. BS EN ISO 16484-3:2005 defines the functions of Building Automation and Control Systems, including a standard points-list documentation template, and a controls schedule that doesn't follow a recognisable documentation structure against that template is usually a sign the interface boundaries haven't been thought through — which is exactly the kind of ambiguity that turns into a dispute at commissioning, not at tender.

A straightforward single-plant-room project with 150–250 points is 2 days' work for an experienced controls engineer. A phased multi-building project with several interface types and mixed protocols is closer to 4, and that's before RFI answers come back and change the count.

Labour, access and programme calculation

Pricing labour properly means pricing the actual working conditions, not a generic day-rate assumption. Out-of-hours or weekend-only access adds real cost and needs its own labour build-up, not a percentage bolted on afterwards. Whose scope a piece of enabling work sits in is worth confirming explicitly at this stage rather than after award: fire stopping around new containment penetrations, builders' work such as chasing, coring and making good, the final power connection into a new panel, and the containment (tray or conduit) the cabling runs in are all boundary items that get disputed precisely because nobody wrote down at tender stage who was providing them. On a phased or occupied-building job, check whether commissioning has a seasonal constraint too — a heating-only or cooling-only commissioning window on a project that spans a season change can add months to programme if it isn't accounted for at pricing stage, not discovered once the install is finished and the plant won't run in the mode needed to prove it.

London logistics and FORS considerations

For any London site, delivery access, FORS accreditation requirements and congestion/emissions charging all affect programme and cost, and they need pricing at tender stage rather than absorbed later. This is covered in full — including current FORS tier requirements, ULEZ and Congestion Charge figures, and TfL's Direct Vision Standard for HGV deliveries — in our companion post on BMS lead times and London delivery risk; there's no need to repeat that detail here beyond flagging it as its own line in the programme.

RFIs: issued early, chased constantly, answered on their own clock

RFIs don't sit in their own slot in the programme — they run underneath every stage above, from the first ambiguity spotted in take-off to the last query raised during pricing review. What matters for timescale purposes is when they're issued, not when they're answered: an RFI raised on day one has ten working days or more to come back before it threatens submission; the same question raised on day nine of a fourteen-day tender is a genuine risk to the return date, because a consultant or client team answering RFIs from multiple bidders on the same project rarely turns them around in under a working week. We cover the mechanics of logging, tracking and escalating RFIs during the tender period — including what to do when they don't come back in time — in our companion piece on handling RFIs during a BMS tender. The discipline that actually protects programme is simple: read the whole spec and drawing set for ambiguity in the first two days, not as you go.

Commercial risk review

Separate from the technical pricing review, someone needs to check the commercial terms the return is being submitted against: what retention is being withheld and for how long, what the payment terms actually are versus what the business can absorb on a job of this size, and how long the priced return stays valid for before material and labour costs are exposed to movement. This is a generic discipline every contractor should run — not a place to publish internal margin or markup detail — but skipping it is how a technically excellent tender return turns into a commercially painful contract.

Internal checking: 1–2 days

Once subcontractor quotes, the controls schedule and the RFI answers are all in, someone who wasn't building the price line by line needs to sanity-check the whole return before it goes out. That means checking the build-up against our per-point costing methodology, confirming labour, commissioning and witness-testing days are realistic against the actual points count rather than a rule-of-thumb ratio, and checking every qualification and exclusion is stated rather than assumed. This is deliberately not the same person who built the schedule — a second pair of eyes catches the arithmetic errors and the optimistic assumptions the estimator has stopped noticing after four days inside the same spreadsheet.

Tender presentation and submission: 1–2 days

The last stage before the deadline is presentation, not pricing: assembling the priced schedule, method statement, programme, qualifications register, and compliance documents into the format the tender actually asked for. This sounds trivial until a return gets marked non-compliant for missing a required attachment or submitting the wrong file format two hours before a portal deadline. Building this stage into the programme as its own 1–2 days — rather than assuming it happens instantly once pricing is "done" — is one of the simplest, least-discussed ways a tender programme slips at the very last moment.

Post-tender clarifications and value engineering

Submission isn't the end of the process. Further queries from the client or consultant, requests for value-engineering alternatives, and delayed approvals are all normal in the weeks after a return goes in — and every week that passes is a week eating into the lead times that were confirmed with suppliers at tender stage. A controller quoted at eight weeks when the tender was priced can be a very different proposition if award slips three months, and remobilising a team and a supply chain against a start date that's moved significantly is a real cost that a good contractor prices as a risk factor from the outset, not an afterthought once it happens.

What usually goes wrong

Almost every late or rushed BMS tender we've seen traces back to one of a handful of things: subcontractor pricing started too late because the schedule "wasn't ready" for enquiries to go out, RFIs got batched up and issued as one long list in week two instead of raised as they were spotted, the internal review stage got skipped entirely because the deadline had already eaten into it, or a site survey never happened so an incomplete points schedule and an unknown existing controls network went into the price as an assumption rather than a checked fact. None of these are pricing failures — they're programme-management failures, and they're the reason the stage-by-stage timeline above matters more than the single headline "how many weeks have we got" number most people fixate on.

Standards and legislation that shape tender timescales

Two references worth knowing if you're managing a tender programme rather than just pricing one. CIBSE Guide H (2009), section 3.1.3.1, sets the sensor accuracy benchmark referenced above and is the first thing worth checking against an unusually tight-tolerance spec during review. And for public-sector procurements, the Public Contracts Regulations 2015 (PCR 2015), Regulation 27, set a statutory minimum time limit of 35 days from despatch of the contract notice for receipt of tenders under the open procedure, reducible to 30 days where the contracting authority accepts electronic submission of tenders — which is why public-sector BMS tenders routinely run longer end-to-end than a privately negotiated return, even though the internal contractor-side stages described above are the same length either way.

A real example: what actually extends a programme

Take a central London office where FCU controls were being upgraded across 16 floors with the building still in full daily use: the constraint wasn't the pricing — it was access. The building only allowed weekend working, which meant the site survey that would normally happen in a day had to be scheduled around two consecutive weekends before take-off could be finalised, and the controls schedule (Trend controllers integrating with the building's LightFi occupancy sensing) had to account for a commissioning and witness-testing programme that could only run on the same restricted access pattern. None of that changed the pricing methodology. It changed the programme, and it had to be priced and stated as an assumption in the return rather than discovered after award.

What good looks like

A well-run BMS tender treats the stages above as parallel and overlapping, not sequential — subcontractor and panel-builder pricing, and RFI issue, start as soon as take-off gives a confident points count, not after the spec review is "finished." It logs every RFI the moment it's spotted rather than batching them. It builds site survey, commercial risk review, internal checking and document assembly into the programme as real days, not slack time. And it prices the actual access, phasing and interface complexity of the project rather than a generic points-count formula. That's the difference between a return that holds up at commissioning and one that generates variations from week one.

When to get a specialist controls contractor involved early

If a tender enquiry is coming with an incomplete M&E design, a fast-track programme, or any hint of phased or restricted access, the earlier a controls contractor sees it, the more of the process above can run in parallel instead of in sequence. Bringing us in at RFI stage rather than at final pricing stage is consistently what turns a rushed return into a realistic one.

Conclusion

A BMS tender isn't one task with one deadline — it's fifteen overlapping stages, each with its own realistic timescale, running across four different clocks of working hours, supplier waiting time, RFI waiting time and total elapsed period. The programmes that go wrong are almost always the ones that treated it as a single block of "pricing time" instead. Get in touch with Alpha Controls early in your tender programme, or request a quote once your enquiry documents are ready, and we'll tell you honestly how long a proper return will take.

Frequently Asked Questions

How long does a BMS tender take from enquiry to submission?

For a straightforward single-building project, 10–15 working days internally is realistic once go/no-go review, take-off, spec review, site survey, subcontractor and panel-builder pricing, controls schedule development, RFI turnaround, commercial risk review and internal checking are all accounted for. Complex or multi-system projects typically run 4–6 weeks.

What is a controls schedule in a BMS tender?

It's the technical backbone of the return — every point, control strategy, and interface mapped against the device list and individually priced, built during a dedicated 2–4 day stage after take-off and specification review.

How are RFIs handled during a BMS tender?

RFIs should be raised the moment an ambiguity is spotted — ideally in the first two days of take-off and spec review — rather than batched and issued late, because a considered answer from a consultant or client team can take a working week or more to come back.

Why do BMS tenders take longer than the quoted return period?

Almost always because subcontractor pricing started too late, RFIs were batched instead of raised as they were spotted, a site survey wasn't secured in time, or the internal checking stage was skipped under deadline pressure — programme-management failures rather than pricing failures.

Does a public-sector BMS tender take longer than a private one?

Often yes — the Public Contracts Regulations 2015, Regulation 27, set a statutory minimum of 35 days under the open procedure, reducible to 30 days where electronic tender submission is accepted, though the internal contractor-side stages described in this article are the same length regardless of sector.