Smart Home Commissioning and Handover: Programming Documentation, User Training and Ongoing Support Plans

Summary

Commissioning is where the difference between a professional smart home installer and a technically capable individual most clearly shows. The physical installation is the visible part of the work; commissioning is the invisible work that makes the system reliable and maintainable over its 15–25 year lifespan.

In practice, many residential smart home projects are poorly commissioned: systems work at handover but have no documented configuration, clients cannot adjust settings without calling the installer, and any modification requires expensive callouts because the original programming logic is undocumented. This is a commercial problem for the installer (callbacks are unprofitable) and a reputational problem (clients who feel held hostage to one contractor become vocal detractors).

Structured commissioning and handover — following CEDIA Best Practice frameworks — turns the installation into a documented, maintainable system that generates ongoing support revenue through annual maintenance agreements rather than emergency callbacks.

Key Facts

• CEDIA Best Practices — published by CEDIA (Custom Electronic Design & Installation Association); sets out documentation standards for residential AV and smart home installations; free to CEDIA members
• As-built drawings — floor plans showing final device positions, cable routes, zone assignments; updated from design drawings to reflect actual installation
• Device schedule — list of every installed device with make, model, serial number, firmware version at commissioning, IP address or device address, and location
• Programming documentation — full record of automation logic: scenes, triggers, time schedules, voice control assignments, integration connections; must be sufficient to replicate the system from scratch
• Group address list (KNX) — exported from ETS; maps every group address to its function and the devices linked to it; essential for any KNX system modification
• Network topology diagram — shows VLAN assignments, switch port configurations, Wi-Fi SSIDs, IP address allocation, and firewall rules
• Handover session — structured walk-through of the system with the client; covers daily operation, common scenarios, and basic troubleshooting; typically 2–4 hours for a comprehensive system
• User guide — written (or video) documentation tailored to the specific installation; not the manufacturer's generic manual; covers the client's specific scenes, button assignments, and voice commands
• Support plan — ongoing service agreement; defines response times, included callouts, firmware update service, and annual system health check; typically priced at 10–15% of system installation cost per year
• Remote access — ability to access and modify the system programming remotely; requires secure VPN or vendor-authorised remote access tool; reduces callout cost for software changes
• Factory reset procedure — documented in handover package; essential for insurance or estate purposes; describes how to reset each device to factory defaults
• Firmware update log — record of when firmware was applied to each device; demonstrates due diligence for warranty and security purposes

Quick Reference Table

Detailed Guidance

Pre-Commissioning: What Must Be Complete Before Testing

Commissioning begins only when all hardware is installed and cabled. A pre-commissioning checklist:

• All devices powered on and responding to network
• All speaker cables terminated and tested for continuity and polarity
• All video connections tested for signal presence (use HDMI test card or basic signal generator)
• All network ports tested for connectivity (ethernet tester; verify switch port LEDs)
• All smart home devices visible in hub/controller before programming begins
• Power supply adequacy confirmed (no overloaded PoE ports, UPS correctly sized)
• Access credentials collected for all manufacturer cloud accounts

Attempting to commission before hardware issues are resolved is inefficient — fault-finding during programming is time-consuming and causes context switching.

Programming Documentation Standards

For Sonos/standard streaming audio systems: Document the zone assignments (which amplifier drives which speakers, room naming in app), source connections (what inputs are connected to which Sonos Port/Amp), scene or playlist setups, and integration connections (Alexa, Google Home, Spotify account linked).

For KNX systems: The ETS project file (.knxproj) is the master documentation. In addition, export:

• Group address list (CSV or PDF) showing every function in the system
• Device-by-device parameter summary (printout from ETS)
• As-built bus topology diagram
• Commissioning notes (any deviations from design, site-specific workarounds)

The ETS project file must be archived by the installer AND a copy given to the client. Without the project file, any modification requires a complete re-read of the system from the bus, which adds several hours to any service visit.

For Control4 or Crestron systems: The project file (C4P or SIMPL) is proprietary and typically retained by the dealer only (client does not receive a copy under most dealer agreements). Document the project backup date and version, plus a written description of all automations and driver versions. Advise clients that migrating from one Control4/Crestron dealer to another may require a system backup transfer fee.

For voice control / app control: Document which voice commands trigger which scenes; which app accounts are linked; which devices require which apps; PIN or code for any voice purchasing controls.

Client Handover Session Structure

A structured handover session for a comprehensive smart home:

Section 1: System overview (30 minutes) Walk through each system type and explain what it does. Don't demonstrate technical details — explain in terms of what the client can do with it. "This button turns the living room lights to 'evening mode' and lowers the blinds. This button on the app does the same thing remotely."

Section 2: Room-by-room walkthrough (60–90 minutes) Demonstrate every lighting scene, blind/curtain control, audio zone, and climate control for each room. Client confirms each function works. Document any items the client wants adjusted during the session (brightness levels, scene colour temperatures, volume defaults).

Section 3: App and voice control demonstration (30 minutes) Show the client the primary app (Sonos, Lutron, Control4, etc.); demonstrate voice commands with Alexa, Google Home, or Siri; demonstrate geofencing if configured (home/away automation). Show how to add additional family members to the app.

Section 4: Basic troubleshooting (30 minutes) Explain what to do if: a device appears offline; an app is not controlling a device; the Wi-Fi is down and which devices continue to work locally. Explain the support plan and how to reach the installer.

Section 5: Security and credentials (20 minutes) Walk through the security checklist: confirm 2FA is enabled on key accounts; explain the IoT VLAN separation; confirm firmware auto-update is enabled; provide the written handover document with credentials and device list.

Ongoing Support Plans

Smart home support plans are a sustainable revenue stream that converts one-off installation revenue into recurring income. A tiered support plan structure:

Essential (c. 10% of installation cost/year):

• Annual health check visit
• Telephone and email support (within 48 hours)
• Remote access diagnostics
• Firmware update monitoring and notification

Standard (c. 12% of installation cost/year):

• All Essential inclusions
• 2 included callout visits per year (additional at day rate)
• Priority response (within 24 hours)
• One scene or automation change per year

Premium (c. 15% of installation cost/year):

• All Standard inclusions
• 4 included callout visits per year
• Same-day emergency response
• Unlimited scene and automation changes
• Annual user retraining session

Support contracts should be presented at handover, not as an afterthought. Systems are most useful during the first 6–12 months when clients are learning to use them — the support plan provides the value that turns a one-time client into a long-term relationship.

Remote Access Configuration

The ability to access and modify a smart home system remotely is fundamental to a cost-effective support model. Approaches by platform:

Control4/Crestron: Native dealer remote access through manufacturer portals; Control4 Ovrc, Crestron XiO Cloud; requires annual subscription

KNX: Remote access via KNX IP Router + secure VPN to the client's network; ETS connects to the IP router; never expose KNX IP directly to the internet

Sonos: Sonos customer service remote diagnostics (read-only); full system changes require local network access or Sonos app on the client's network

Ubiquiti UniFi: UniFi Site Manager (cloud key or Dream Machine required); full remote configuration capability; secure with 2FA

Home Assistant: Home Assistant Cloud (Nabu Casa subscription) or self-hosted VPN; full remote configuration via web interface

Frequently Asked Questions

How long should a commissioning visit take?

Rule of thumb: 1 hour per zone or control point for a well-planned system where the programming was done in advance. A 6-zone audio system + 12-zone KNX lighting + HVAC integration + network configuration = approximately 8–12 hours commissioning. Pricing commissions at an hourly rate (with a fixed estimate) ensures time is charged appropriately.

Who owns the programming files — installer or client?

The client owns the system and should receive all documentation including programming files. For open systems (KNX, Home Assistant, Hubitat), the project files are standard formats that any competent installer can use. For proprietary systems (Control4, Crestron), the dealer typically retains the live project file for technical reasons but should provide a backup on request. CEDIA Best Practice states that clients should receive their documentation.

What happens to a smart home system during a house sale?

The new buyer inherits the smart home system. Best practice: include the full commissioning documentation package in the conveyancing documentation alongside the FENSA certificates, boiler warranty, and building regulations compliance certificates. Without documentation, a new buyer either cannot use the system effectively or must pay an installer to reverse-engineer it. A documented, supported smart home system is a selling point; an undocumented one is often seen as a risk.

Can I offer support plans if I'm a sole trader?

Yes. A sole trader can offer support plans with clear terms of service that define what happens if you are unavailable (referral to a named alternative installer, for example). Document this in the support agreement and ensure it is explained at handover. Some CEDIA members have mutual referral arrangements to cover this scenario.

Regulations & Standards

• CEDIA Best Practices — documentation standards for residential AV and smart home; available to CEDIA members; sets the industry benchmark

• BS 7671:2018+A2:2022 — electrical installation documentation requirements; test certificates, inspection records; applies to mains wiring elements

• GDPR / UK GDPR — if support plan includes remote monitoring of cameras or occupancy data, there are data processing obligations; documented in the support agreement's privacy notice

• Consumer Rights Act 2015 — goods and services must be of satisfactory quality; programming and commissioning services are subject to this Act; well-documented commissioning protects the installer

• CEDIA — Best Practice Documentation Templates — documentation frameworks for residential installations

• Control4 — Ovrc Remote Support Platform — dealer remote access for Control4 installations

• KNX Association — ETS Project Documentation — ETS export formats and documentation guidance

• Home Assistant — Remote Access Guide — Nabu Casa and self-hosted remote access options

• [cedia membership smart home|CEDIA membership](/wiki/smart-home/cedia-membership-smart-home|CEDIA membership) — the professional framework for commissioning standards

• [smart home system specification|smart home system specification](/wiki/smart-home/smart-home-system-specification|smart home system specification) — how to scope and specify the system before commissioning begins

• [iot device cybersecurity|IoT device cybersecurity](/wiki/smart-home/iot-device-cybersecurity|IoT device cybersecurity) — security documentation that should be included in the handover package

• [knx home automation overview|KNX home automation](/wiki/smart-home/knx-home-automation-overview|KNX home automation) — ETS documentation requirements specific to KNX installations