Smart Home BOQ & Specification: A Practitioner's Guide (India)

Ask three Indian integrators to quote a smart home and you will get three numbers that differ by a factor of two — not because one is cheating, but because each quoted a different scope. One priced Wi-Fi switches, another priced a wired KNX bus, the third left out the network entirely and assumed the client's router would do. Comparing those quotes is meaningless. The instrument that makes them comparable, and that protects both client and professional, is a proper Bill of Quantities and technical specification: a document that fixes what is being supplied, in what quantity, to what standard, so that every vendor prices the same thing.

This guide is for the architect, interior designer, project manager or quantity surveyor who must scope an automation package. It covers how to structure a smart-home BOQ, how to itemise by category, how to write a specification tender teams can price, how to take quantities off the drawings, how much contingency to carry, how to compare quotes fairly, and how to close the scope gaps that otherwise appear as variations. It follows directly from the design work in smart home design for architects and the physical build in the smart home installation guide; the BOQ is the bridge between the two.

A quote you cannot compare is not a quote — it is a guess with a rupee sign. The BOQ is what turns three guesses into three prices for the same job.

What a BOQ is, and what a specification adds

A Bill of Quantities lists every item to be supplied and installed, with a measured quantity and a unit, so that a rate can be applied to each line and the whole priced. A specification describes each item precisely enough that only compliant products qualify — make and model or an equal-approved alternative, electrical rating, protocol, and the relevant standard. The BOQ answers how many; the specification answers exactly what. You need both. A BOQ without a specification lets vendors substitute the cheapest generic module for a named brand and undercut an honest competitor; a specification without a BOQ leaves quantities open to dispute. Together they form the tender package that also draws on the smart home BOQ generator for a first-pass structure.

Structure the BOQ by category

Organise the bill into logical work categories so that scope is visible and nothing falls between sections. The figure below shows the anatomy of a single line item — the discipline every row must follow.

The categories below cover almost every domestic automation package. Keep them as separate sections so a vendor cannot bury a gap.

Itemise each category properly

Two categories cause most disputes and deserve special care.

CCTV and security. Do not write "CCTV system — 1 lot". Itemise: each camera by type (dome, bullet, PTZ) and resolution; the recorder by channel count and storage; the hard disk by capacity and grade (surveillance-rated, not desktop); PoE switch ports; and every cable run. The PoE-versus-Wi-Fi CCTV decision changes the cabling and switch lines materially, so lock it before you quantify.

Network and cabling. This is the most commonly omitted category, and the one that silently breaks a wireless home. Itemise the router, each managed or PoE switch, every access point, the rack and patch panel, and cabling by length. Coordinate against the smart home networking design so the backbone is priced, not assumed. Labour must be a named line too — supply-only quotes that hide installation are the classic trap.

Write tender-ready specifications

A specification line must be tight enough to exclude non-compliant substitutes and open enough to allow fair competition. The convention in Indian tenders is make and model "or equal approved" — you name a benchmark product and permit alternatives the consultant approves as technically equivalent. Each spec should state the attributes below.

Add a general-conditions preamble covering: neutral-wire and deep-box requirements, that all cabling runs in conduit, that programming and a documented handover are included, that the vendor commissions and demonstrates every scene, and that a defects-liability period applies. These clauses close the gaps that otherwise become "not in my scope" on site.

Quantity take-off from drawings

Quantities come off the coordinated low-voltage layout and RCP, not from memory. Count switch points, camera positions, sensor points, access points and panels directly from the marked-up plans produced at design stage. Measure cable lengths by scaling the runs from rack to each drop and adding a realistic slack allowance — a common rule is the measured route plus 10 to 15 percent for terminations, dressing and vertical rises. Count conduit by run and back-boxes by switch position. Because the take-off is only as good as the drawing, an incomplete drawing set is the root cause of most quantity disputes — which is why the smart home planning drawings must be complete before you bill them.

Contingency, spares and provisional sums

No smart-home BOQ should total to the rupee and stop. Carry a contingency of 10 to 15 percent for design development, site conditions and the client changes that always arrive. Include a spares line — a few switch modules and a spare camera — because matching a discontinued module two years later is painful. Use provisional sums for items whose scope is not yet fixed (a home-cinema fit-out, say) so the tender total is honest rather than falsely precise. Validate the whole number against an independent benchmark with the smart home cost calculator before you issue it, and cross-read the smart home cost guide for realistic Indian rates.

Compare vendor quotes fairly

The BOQ pays for itself at bid evaluation. Because every vendor priced the same lines, you can lay their rates side by side and compare like with like. The workflow below is the sequence from specification to award.

When you normalise the quotes, watch for the tricks: a rock-bottom bidder who has left out labour, who has substituted a generic module for the specified make, who has omitted the network, or who has quietly moved commissioning into a separate future charge. Score on price, technical compliance and demonstrated track record together. The cheapest number is rarely the cheapest project once variations land. For the deeper make-versus-DIY reasoning behind vendor selection, see choosing a home automation system and the broader home automation guide.

Avoiding scope gaps

Scope gaps are the difference between the BOQ total and the final bill. They come from a handful of predictable places, closed by a handful of clauses.

A sample BOQ structure

A workable domestic BOQ, condensed, reads like the table below — each real line carrying its own make, rating, standard, quantity and rate.

Closing

The BOQ and specification are not paperwork — they are the professional's control over cost, quality and scope. A well-built bill turns three incomparable guesses into three comparable prices, protects the honest vendor from being undercut on a substitution, and gives the client a document they can hold every party to. Build it category by category off complete drawings, specify every line to make and standard, carry honest contingency, and evaluate on more than the bottom number. Do that, and the project you priced is the project you build.

References

• National Building Code of India 2016, Part 8 — Building Services — the framework for electrical and low-voltage services that your specifications must respect.
• IS 732:2019 Code of Practice for Electrical Wiring Installations, BIS — the wiring standard your BOQ specifications reference.
• Bureau of Indian Standards — product certification — source of the IS numbers (such as IS 3854 for switches) cited in your specification.
• KNX Association — for professionals — reference for specifying wired-bus components to an open standard.
• Connectivity Standards Alliance — Matter — the interoperability standard to name in device specifications.
• Central Electricity Authority (Safety and Electric Supply) Regulations, India — the statutory safety rules that govern the installed work you are billing.