Coordinating AV, ELV, fire and automation before the BOQ

A bill of quantities is where systems coordination either pays off or quietly unravels. We are often handed a BOQ that reads as a catalogue — a list of devices, with quantities already fixed — assembled before anyone resolved how AV, ELV, fire and automation would share the same ceilings, trays, power and network. By then the cheapest decisions have already passed. The provisions that cost almost nothing to coordinate at design stage cost several times more to retrofit once quantities are locked and the carcass is up. This is a briefing on what to coordinate before the BOQ, written for architects, consultants and project teams.

Start with provisions, not products. At design stage the decisions that matter are not brands — they are cable pathways and riser space, the location and size of the equipment room and racks, power and UPS provisioning on the electrical load schedule, and the ceiling and acoustic coordination on the reflected ceiling plan. Fix these on the drawings and the later product choices drop into a design that was ready for them. Leave them to the BOQ and the install is forced into whatever space is left over, and it will look retrofit even if the hardware is reference-grade.

Let fire and life-safety set the envelope. Fire-alarm, hydrant and extinguisher scope follows the building's occupancy classification and the project's fire strategy, and that strategy is led by the appointed fire consultant and the authority having jurisdiction — not by a product list in a BOQ. A common and expensive mistake is to pre-empt the fire strategy with quantities. Settle the strategy and the approval path first; the systems scope then aligns to it. The same discipline applies to anything regulated or privacy-sensitive: the design follows the consultant and the authority, and the early coordination is about readiness, not layouts.

Most scope gaps hide in the seams. AV, security and ELV, fire, automation and IT do not live in separate worlds — they share the same ceiling void, the same cable trays, the same power and the same network backbone. The gaps that surface on site, and the variations that follow, almost always sit in the seams between disciplines that each assumed someone else owned a shared route or a shared power feed. Coordinating the seams — who owns which pathway, which power feed, which network segment — before the BOQ is the single highest-leverage thing a project team can do.

Assemble the right inputs before quantities. A coordinated BOQ rests on a small, consistent set of inputs: general-arrangement and reflected-ceiling plans, the electrical load schedule, the occupancy type and a room or area schedule, a view of network and power intent, and a clear answer to who will operate and maintain the systems after handover. None of this is exotic, and most of it already exists at design stage — it simply needs to be in one place before the quantities are written.

Structure the early conversation with the advisory tools. We built a set of free, advisory consoles to make this preparation concrete rather than abstract. The System Need Finder suggests which disciplines a project should even include. The Architect Brief Builder assembles a plain-language coordination brief. The Fire Readiness Checklist helps you prepare for a fire-systems conversation without producing any layout or pass/fail. The Boardroom Solution Selector and Smart Home Discovery Wizard point meeting rooms and homes in a sensible direction before design. Every one of them is qualitative and additive — they produce no quantities, no layouts and no pricing, and they hand off to a conversation with the studio.

Treat the BOQ as a coordination output, not a starting point. When provisions are fixed on the drawings, the seams are owned, the fire strategy is led by the consultant and the inputs are assembled, the BOQ writes itself as the reflection of a design that already works. When those steps are skipped, the BOQ becomes a shopping list that the architecture then has to absorb — and absorbing it is where programmes slip and budgets drift. The work above is what lets a project be delivered as one accountable contract, with final design, statutory review and approvals remaining, as they should, with the appointed consultants and the authority having jurisdiction.