If you’ve ever been six months into a project and found yourself arguing with a subcontractor about whether BMS commissioning was in their price, you already know how this story ends. Variations. Delays. Budget overruns that nobody saw coming — except they were hiding in plain sight, buried in the exclusions of a tender document that nobody scrutinised properly before the order was placed.
The BMS package is one of the most misunderstood scopes in any M&E tender. It sits at the interface of mechanical, electrical, and controls — touching everything from the boiler plant to the fire alarm — and yet it routinely gets treated like a commodity line item. Price it off the drawings, compare the bottom lines, pick the cheapest. What could go wrong? Quite a lot, as it turns out. A poorly scoped BMS tender doesn’t just create cost problems — it creates programme problems, commissioning problems, and handover problems that echo for years after practical completion.
This post breaks down how to read a BMS tender properly, what the red flags look like, and what a well-structured tender should contain so you can compare like with like and avoid the arguments that bad tenders inevitably create.
A BMS tender should cover everything required to deliver a fully functioning building management system from first fix through to handover. That means field devices (sensors, actuators, damper motors), controllers, network infrastructure, the supervisor or head-end system, all software and licensing, programming and graphics, commissioning, witness testing, documentation, and training. It also means the labour, cable, containment, and preliminaries needed to install all of it.
That sounds straightforward on paper. In practice, BMS tenders are a minefield of omissions because the scope depends on what’s been coordinated with other trades. Who wires the interlocks between the BMS and the fire alarm? Who provides the cable containment on the risers? If these interfaces aren’t pinned down in the tender documents, they’ll be pinned down on site — usually at cost, usually under programme pressure, and usually with someone claiming it was always someone else’s responsibility.
The most dangerous tenders are the ones that price only what’s explicitly shown on the drawings. A BMS contractor pricing competitively will leave out anything the specification doesn’t call out. That’s not dishonest — it’s the nature of competitive tendering. The problem is when the client assumes it’s included because “surely that’s obvious.” Nothing in a tender is obvious. If it’s not written down, it’s not in the price.
This isn’t just a controls contractor’s problem. Bad BMS tenders cause pain across the entire project team.
For the main contractor, every gap in the BMS scope that surfaces during construction becomes a change order — and BMS changes are particularly expensive because they affect programme. You can’t commission a system that hasn’t been fully installed, and you can’t hand over a building without a commissioned BMS. A single missed integration can hold up an entire floor’s commissioning for weeks while the scope argument plays out.
For the M&E contractor, the BMS tender defines the interfaces with their mechanical and electrical packages. If the BMS contractor hasn’t priced the wiring from their panels to the field devices, or hasn’t included the interlocks with the M&E plant, the M&E contractor is left filling that gap at their own cost or fighting a disputed variation.
For the FM team inheriting the building, the quality of the BMS tender directly determines what they receive at handover. A tender that excluded training means nobody knows how to operate the system. A tender that omitted O&M documentation means no operating manual, no as-built drawings, and no maintenance specification. Every shortcut in the tender becomes a long-term operational problem.
For the consulting engineer, a vague BMS tender makes it nearly impossible to evaluate competing bids fairly. If Contractor A has priced BMS commissioning as a two-week exercise and Contractor B has excluded it entirely, comparing those bottom lines is meaningless — they’re not bidding the same job.
Having tendered, won, lost, and inherited the consequences of hundreds of BMS packages over the years, the problems fall into the same categories almost every time. Here are the seven red flags that should make you stop and ask questions before you sign anything.
Buried exclusions. The most commercially dangerous feature of a bad BMS tender is the exclusions list — and specifically, where it sits in the document. Some contractors bury exclusions on page 14 of a 16-page submission, in small text, using vague language like “all works not specifically included in the above scope.” That single sentence can exclude thousands of pounds of work that the client assumed was covered. Read the exclusions first, before you read the price.
No points schedule. A BMS points schedule is the definitive list of every point the BMS will monitor and control — every sensor input, every actuator output, every alarm, every meter reading. If the tender doesn’t include one, or includes one that’s vague (“points schedule to be developed during detailed design”), you have no way of knowing what the BMS will actually do. You’re buying a system with no specification for its functionality. Any points schedule worth the paper it’s printed on should list every point by type (AI, AO, DI, DO, network), identify its source and destination, and map to a specific piece of plant or zone.
Vague commissioning scope. BMS commissioning is where most tenders fall short, because it’s the most labour-intensive and time-dependent phase of the project. A tender that says “BMS commissioning included” without specifying what that means — how many engineering days, which systems, whether it includes point-to-point testing, whether it includes attendance at witness testing, whether it covers seasonal commissioning — is a tender that’s either underpriced or deliberately ambiguous. Either way, you’ll pay for the missing detail later.
Missing witness testing. Witness testing is the formal process where the BMS contractor demonstrates to the consulting engineer, the client, or the main contractor that each control strategy operates as specified. It’s a contractual requirement on most projects, and it requires significant engineering time to prepare for and attend. If witness testing isn’t priced as a specific line item with an assumed number of sessions and attendees, it will either be rushed to fit whatever time is left or claimed as a variation.
No handover deliverables defined. A BMS tender should specify exactly what documentation, training, and data will be delivered at handover. That means O&M manuals, as-built drawings, controller configuration backups, points schedules, trend log templates, alarm schedules, training hours and attendee numbers. If the tender is silent on handover, you’ll get whatever the contractor feels like providing — which, under programme pressure, will be the absolute minimum.
Unclear programming hours. The BMS software — the control strategies, graphics pages, alarm configurations, and integrations — represents a significant proportion of the BMS cost. A tender that doesn’t break out programming hours, or that lumps software into a single line, gives you no visibility of how much development time has been allowed. When changes inevitably arise during construction, you’ll have no basis for evaluating whether additional programming costs are reasonable.
Interface gaps between packages. This is the most common source of BMS variations on any project. The BMS needs to interface with the fire alarm, the lighting controls, the access control system, the metering package, the packaged plant controllers, and potentially the landlord’s existing BMS. Each interface requires coordination, cabling, protocol conversion, and testing. If the BMS tender assumes these interfaces are in someone else’s scope, and that someone else’s tender assumes the same, the interface falls into a gap that nobody has priced. Both parties exclude it. The client pays twice.
Two standards are particularly relevant to BMS tender quality, and both provide specific requirements that a well-structured tender should address.
BSRIA BG 6/2018: A Design Framework for Building Services (part of the BSRIA Soft Landings framework) sets out the principle that building handover and aftercare should be planned from the earliest stages of a project, not treated as an afterthought at practical completion. BG 6/2018 specifically requires that commissioning management, operator training, and post-occupancy evaluation are addressed in the project brief and carried through into subcontract scopes. For a BMS tender, this means the tender should include defined training hours for the FM team, a post-handover support period (typically 12 months of aftercare), and a commitment to seasonal commissioning in the first year of operation. A BMS tender that ignores handover and aftercare entirely is inconsistent with BSRIA BG 6/2018’s framework — and it’s a strong signal that the contractor is pricing to install, not to deliver a working building.
CIBSE Commissioning Code M: Commissioning Management provides the management framework for building services commissioning. Code M requires that commissioning is planned, resourced, and managed as a distinct activity — not squeezed into whatever time remains before practical completion. Specifically, Code M requires that BMS commissioning includes point-to-point testing of every hardwired and network point, functional performance testing of each control strategy under realistic operating conditions, and a formal commissioning record that documents the tested and verified performance of the system. A BMS tender that doesn’t allow for point-to-point testing, or that doesn’t reference a commissioning plan aligned with Code M’s requirements, is a tender that hasn’t properly scoped the commissioning phase. When commissioning gets squeezed — and it always does on a tight programme — a vague tender gives the contractor every reason to cut corners.
Beyond these, any BMS tender for a project with energy performance targets should reference Approved Document L compliance, particularly around controls requirements for optimum start/stop, weather compensation, and zone control. And tenders involving BACnet or Modbus integrations should reference BS EN ISO 16484-5 (the BACnet standard) or BS EN 61158 (the Fieldbus standard for Modbus) to confirm protocol compliance and interoperability testing requirements.
The Pinsent Masons project in London is a good example of what happens when the BMS tender is done properly from the outset. Alpha Controls was appointed to deliver the BMS upgrade across 16 floors of a live, occupied commercial office building — replacing end-of-life controllers with Trend IQ4 hardware, integrating LightFi occupancy sensing, and delivering the entire project with weekend-only site access to avoid disrupting the law firm’s operations.
The key to avoiding the usual BMS tender problems was scope definition. The tender was built around a complete points schedule mapping every controller, sensor, actuator, and integration point across all 16 floors. No ambiguity about what was in the price. The commissioning scope was defined as a specific number of engineering days per floor, with point-to-point testing for every hardwired point and every BACnet object on the network. Witness testing was priced as five formal sessions with the consulting engineer, each covering a defined group of floors with pre-agreed test scripts.
The Trend controller specification was locked in at tender stage, eliminating post-award value engineering arguments. Every FCU, AHU interface, and meter integration was mapped to a specific controller type and I/O configuration. When the project reached site, there were no surprises — the controllers matched the schedule, the software matched the points list, and the commissioning plan matched the programme.
The handover package was specified in the tender: full O&M documentation, as-built schematics, controller backups, alarm schedules, and two days of operator training. The aftercare period — 12 months of remote monitoring and a seasonal commissioning return visit — was a priced line item, not a goodwill gesture.
The result was zero BMS-related variations, a clean commissioning record, and an FM team that took ownership of a system they understood from day one. That doesn’t happen by accident. It happens because the tender was written properly. You can read more about installation cost considerations that factor into projects like this on our dedicated guide.
A properly structured BMS tender should give you everything you need to evaluate the scope, compare bids on a like-for-like basis, and hold the contractor to account during delivery.
The tender should open with a clear scope summary defining the boundaries of the package — what’s included, what’s excluded, and what’s assumed to be provided by others. Every exclusion should be specific. “Fire alarm interface cabling by others” is clear. “All works not specifically described” is not.
The points schedule should be appended, covering every monitored and controlled point, categorised by system and by point type. This is the technical backbone of the bid — without it, you’re comparing prices without knowing what you’re buying.
When you receive multiple tenders structured this way, you can actually compare them. You can see which contractor has priced more commissioning time, which has included the fire alarm interface, and whether the programming allowance is realistic. That’s how you compare BMS tenders properly — not by looking at the bottom line, but by reading the detail.
The time to catch a bad BMS tender is during pre-construction, before the subcontract order is placed. Once the tender is accepted and becomes the agreed price, every exclusion in that document is contractually binding. If fire stopping wasn’t included, it’s a variation. If commissioning was vague, you’ll pay for clarity. If the interfaces weren’t defined, you’ll pay for coordination. The contract is the tender — and the tender is only as good as the scrutiny it received before someone signed it.
Whoever reviews the BMS tender needs to understand building controls — not just pricing. Main contractors should have someone who can read a points schedule and spot unrealistic commissioning allowances. Consulting engineers should assess scope completeness, not just compare bottom lines. FM teams should focus on training, documentation, and aftercare — the elements that determine whether you inherit a building you can manage or one you’ll spend two years trying to understand.
The pre-construction meeting is where ambiguities get surfaced and resolved. Walk through every interface, challenge every exclusion, document every assumption. It takes a few hours at tender stage. It takes months and tens of thousands of pounds to sort it out on site.
A BMS tender is not a commodity quote — it’s a technical scope document that defines what your building’s control system will do, how it will be commissioned, and what you’ll receive at handover. The difference between a good BMS tender and a bad one isn’t the price on the front page. It’s the detail in the points schedule, the clarity of the commissioning scope, the specificity of the exclusions, and the quality of the handover commitments.
Every BMS variation, every commissioning delay, every post-handover argument about what was and wasn’t included can be traced back to a tender that wasn’t scrutinised properly. The fix is straightforward: read the exclusions before the price, demand a points schedule, define the commissioning scope explicitly, and make sure every interface between trades is assigned to someone. Do that, and you’ll avoid the vast majority of BMS tender disputes.
If you’re preparing to tender a BMS package and want to make sure the scope is right before you go to market — or if you’ve received BMS tenders and need help evaluating them — Alpha Controls can help. We’ve been on both sides of the tendering process and know exactly where the gaps hide. Request a quote or get in touch with our services team to talk through your project.
Our team of building automation specialists is ready to help you optimise your building's performance and efficiency.
Get in Touch
