Smart Home Commissioning & Handover in India: The Practitioner Playbook

Most Indian smart-home projects are declared "done" the moment the last switch is screwed in and the lights blink on. That is not done — that is installed. The gap between a system that was installed and a system that was commissioned and handed over is exactly the gap between a happy client and a stream of weekend callbacks. Commissioning is the disciplined process of proving every device, every automation and every failure mode works as designed, hardening the system, and packaging it so that someone who never touched the build can run it, fix it and hand it on. This is the practitioner playbook for doing that in Indian homes.

A smart home is not handed over when it works for the person who built it. It is handed over when it works for the person who did not — when the client, the next integrator, and the electrician three years from now can all understand it from the documents alone.

This guide sits after the smart home installation guide for India and before the smart home maintenance guide. It pairs with the smart home BOQ and specification guide — because you commission against the spec you promised — and with the smart home privacy and security guide for the hardening steps. For the wider picture, start at the ultimate guide to smart homes in India.

What commissioning actually means

Installation is physical: devices mounted, wired to code under IS 732, powered up. Commissioning is functional and contractual: you verify that what was built matches what was specified, that it behaves correctly under normal and abnormal conditions, and that the client formally accepts it. In building-services language, commissioning is the bridge between "energised" and "operational".

For a smart home specifically, commissioning has to prove things that a lighting or HVAC contractor never worries about: that the Wi-Fi mesh holds under load, that automations fire on the right triggers and only those, that the house still functions when the Internet drops, that no default password survives, and that the hub configuration exists somewhere other than a single SD card that can die.

The commissioning checklist

Treat each gate as pass/fail. You do not proceed to the next until the current one is clean. Below is the working checklist a serious integrator runs on an Indian residential job.

Gate 1 — Device inventory, addressing and naming

Every device that draws power or joins the network gets logged before anything else. If it is not on the inventory, it is not commissioned. Build the inventory as a spreadsheet keyed to the room map from the BOQ and specification.

Naming convention is non-negotiable. Adopt one scheme — typically Floor-Room-Type-Number for IDs and plain-English for friendly names — and apply it everywhere: the hub, the app, the labels on the DB, and the docs. Inconsistent names are the single most common reason a second integrator refuses to touch a system.

Gate 2 — Network configuration and segmentation

The network is the foundation; commission it as its own subsystem. Confirm the mesh or access-point coverage against a walk-test in every room, verify DHCP reservations for hubs and cameras (static-ish addressing prevents "device unreachable" after a reboot), and segment the network. Isolate IoT devices and cameras onto a separate VLAN or guest SSID so a compromised bulb cannot see the family's laptops — this is the same principle argued in the smart home privacy and security guide.

Gate 3 — Automations and scenes tested

Every scene and automation from the design gets a test row. Trigger it deliberately, confirm the exact expected outcome, and confirm nothing else fires. Motion-triggered lights that also trip a geyser because of a shared condition are the kind of ghost you catch here, not at 2 a.m. six months later. Cross-check against the smart home scenes and automations guide for common logic traps.

Gate 4 — Failover, no-Internet behaviour and security hardening

This is the gate that separates professionals from box-fitters. Physically pull the Internet and confirm the house still works: local switches must toggle lights, locks must open from the keypad, the hub must run local automations. Then pull power to the hub and confirm nothing dangerous happens on reboot. Finally, harden: change every default credential, disable UPnP and unused cloud accounts, enable two-factor on the owner account, and update firmware to the tested baseline.

Gate 5 — Backups of hub and controller config

If the hub dies and the only copy of the configuration died with it, you have not commissioned a smart home — you have installed a time bomb. Export and store the hub configuration (Home Assistant snapshot, Hubitat backup, or the vendor cloud export), the network config, and the device inventory. Keep one copy off-site or in the client's own cloud. Record where the backups live in the handover pack.

Acceptance testing with the client

Acceptance is a joint walk-through, not an email. Sit with the client and run a scripted acceptance test: they operate each key function, you observe, and both parties sign. Anything that fails goes on the snag list rather than blocking the whole handover. Use the smart home cost calculator beforehand to reconcile the delivered scope against what was quoted, so acceptance is not the moment a scope surprise appears.

The acceptance document should record: date, attendees, functions tested and result, open snags with agreed dates, warranty start date, and signatures. This single page resolves ninety per cent of "you never delivered X" disputes.

The handover pack

The handover pack is the deliverable clients remember when your competitor left them a shoebox of manuals. Assemble it as a labelled folder — printed and digital.

Handing over credentials securely

Never email passwords or leave them on a WhatsApp thread. Hand over credentials through the client's own password manager, a printed sealed envelope, or a shared vault entry that only they control after handover. Force a password reset on the owner account at handover so the integrator's working password is retired. Log which accounts were transferred.

Training the household

The system is only as good as the least technical person who has to live with it. Run at least one training session with everyone in the house, including domestic staff who operate lights and locks daily. Keep it hands-on: the client should physically run each scene, add a routine, and arm and disarm security, not watch you do it. Record a short walkthrough video and store it in the pack. A one-page fridge-magnet quick-start beats a fifty-page manual nobody opens.

The snag list

The snag (or punch) list is the honest record of what remains. Every item has an owner, a target date and a status. A short, tracked snag list signals professionalism; a project with zero snags usually means nobody looked hard enough. Close the list against the acceptance document, and only then is the project truly handed over — and ready to roll into an ongoing maintenance and AMC regime.

Common commissioning failures in Indian homes

Three failures recur across Indian residential jobs, and all three are avoidable at the gates above. The first is skipping the failover test: a system commissioned only against a live Internet connection looks perfect on handover day and collapses the first time the broadband drops during monsoon, because nobody proved the local fallback. The second is undocumented naming — a technician names devices ad hoc during pairing, never harmonises them, and the client is left with "Switch 3" controlling the bedroom while "Bedroom" controls a corridor. The third is the single-copy hub configuration, sitting on one SD card or one phone, with no export and no restore path; when that card corrupts, the entire logic of the home is gone.

Each of these is a gate failure, not bad luck. A disciplined commissioner refuses to sign Gate 4 until failover is demonstrated, refuses to close Gate 1 until naming is consistent across the hub, app and physical labels, and refuses Gate 5 until a backup has been restored to prove it works. The extra afternoon this costs is trivially cheaper than the reputational damage of a system that strands its owners.

Why the discipline pays

It is tempting, on a small apartment job, to treat commissioning as bureaucratic overhead and just "hand over the app". The economics say otherwise. A callback in an Indian metro costs a half-day of a technician's time plus travel, and repeat callbacks erode the referral pipeline that keeps a small integrator alive. A properly commissioned and documented handover front-loads a few structured hours and buys years of quiet. It also protects the client if you, the integrator, ever move on — because the as-built pack lets any competent successor pick up the system cleanly, which is exactly the continuity a homeowner is paying a professional to guarantee.

References

• Bureau of Indian Standards — IS 732: Code of Practice for Electrical Wiring Installations
• Central Electricity Authority — CEA (Measures relating to Safety and Electric Supply) Regulations
• CERT-In — Guidelines on securing IoT and connected devices
• Home Assistant — Backups and snapshots documentation
• Wipro Smart Home — Product and warranty documentation