Smart Home Commissioning and Handover: Programming Documentation, User Training and Ongoing Support Plans
Quick Answer: A complete smart-home commissioning and handover should include: a system test sheet (every device tested and confirmed working), as-built documentation (network, electrical, control system schematics), an Operation and Maintenance (O&M) manual, a user training session covering daily use and basic troubleshooting, login credentials transferred securely (password manager, not email), an ongoing support plan (annual review, firmware updates, faults), and signed-off Building Regulations certificates for any notifiable work. Most installation failures over time are not technical — they are documentation and handover failures.
Summary
The single biggest predictor of long-term smart-home success is the quality of commissioning and handover. A perfectly installed system that the homeowner doesn't understand becomes a frustration. A system handed over with credentials emailed in plain text and no documentation becomes a security risk. A system without an ongoing support plan slowly degrades as devices go end-of-life and credentials get lost.
This article covers the structured handover process — what to test, what to document, what to train the user on, and how to set up a sustainable ongoing relationship. It draws on CEDIA's recommended practices for project handover and the broader experience of professional integrators in the UK.
The article assumes the system has been correctly installed. Commissioning here means the post-install activities of testing, programming, optimisation, documentation and user enablement. For Part P notification and electrical certificates see part p implications smart home; for security briefing see iot device cybersecurity.
Key Facts
- CEDIA Project Documentation Recommended Practice — sets out standard handover documentation
- System test sheet — every controllable device tested across all expected control paths
- As-built documentation — drawings reflecting actual install, not original design
- O&M manual — Operation and Maintenance manual; standard CDM 2015 deliverable
- User training — typically 1-2 hour session at handover; longer for complex systems
- Credentials transfer — secure password manager (1Password, Bitwarden), NOT email
- Building Regulations sign-off — Part P notification certificates from CPS-registered electrician
- Annual review — recommended; verify operation, update firmware, refresh credentials
- Snag list — punch list of outstanding items; tracked to closure post-handover
- First-month follow-up — proactive contact to address early issues
- Maintenance contract — typically 1-3% of system value per year
- Remote access — for support; secure VPN or vendor remote tools
- Firmware update strategy — auto-update where supported, scheduled manual otherwise
- Battery replacement schedule — 2-5 year cycle for sensors and remotes
- End-of-life planning — devices typically 5-7 year refresh cycle for active components
- Document storage — accessible to client; cloud or local depending on preference
- Insurance documentation — IBG warranties, public liability of installer
Quick Reference Table
Spending too long on quotes? squote turns a 2-minute voice recording into a professional quote.
Try squote free →| Handover Document | Format | Storage Location |
|---|---|---|
| As-built network diagram | PDF + editable source | Cloud + client folder |
| System schematics | Client folder | |
| Device inventory | Spreadsheet | Cloud + client folder |
| Cabling schedule | Spreadsheet | Client folder |
| Programming export | Native format (e.g. ETS file) | Secure cloud + installer offline |
| Network credentials | Password manager | Encrypted vault |
| User app credentials | Password manager | Encrypted vault |
| EIC / Part P certificates | Original PDF | Client folder + scheme portal |
| IBG warranty documents | Original | Client folder |
| O&M manual | PDF + bound paper | Client folder |
| User quick-start guide | PDF + paper | Visible location in home |
| Training video / recording | MP4 | Client cloud folder |
| Test Type | What to Verify |
|---|---|
| Power test | All circuits energised; no faults |
| Network test | All devices reachable; correct VLAN; correct DHCP/static |
| AV signal test | Each source through each zone at expected quality |
| Speaker polarity | All speakers in phase |
| Speaker level | Calibrated in-room |
| Lighting test | Each circuit; each scene; each switch panel |
| Heating test | Each zone; setpoint achieved; valve operation |
| Security test | Sensors, cameras, alarm panels |
| Voice control test | Common commands across rooms |
| App control test | Phone-based control of all systems |
| Scene test | Programmed scenes execute correctly |
| Edge case test | What happens if Wi-Fi fails? Mains cut? |
Detailed Guidance
The commissioning sequence
Commissioning is structured, not ad hoc:
1. Power-up and basic verification
- Apply power circuit by circuit
- Verify no immediate faults (RCD trips, smoke, smell)
- Test consumer unit and all RCBOs
- Verify supply voltage and earthing
2. Network commissioning
- Configure router, switches, access points
- Set up VLANs per design
- Verify Wi-Fi coverage with site survey app
- Test internet performance (speed test, latency)
- Document IP allocations
3. Device inclusion / pairing
- Add IoT devices to hubs (Z-Wave, Zigbee, Matter)
- Apply firmware updates
- Set device names and locations
- Group devices by room/area
- Test individual control of each device
4. Programming
- Build scenes (Movie, Dinner, Goodnight, Welcome Home)
- Set up schedules (lighting, heating)
- Configure automations (motion-triggered lighting)
- Set up notifications (alarm, leak, low battery)
5. Calibration and tuning
- AV: Audyssey, Dirac, ARC speaker calibration
- Lighting: scene levels match design intent
- Heating: setpoints and schedules per client
- Cameras: motion zones, recording schedules
6. Integration testing
- Voice control of every controllable device
- App control on every household member's phone
- Wall panels and remotes in every room
- Cross-system: "Movie" scene triggers AV + lighting + blinds
7. Edge case testing
- What happens if internet fails? Local control still works?
- What happens if a hub fails? Reset and rejoin?
- What happens if a battery dies? Notification?
- What happens during a power cut? UPS protects critical systems?
8. Snag list
- Walk through with client; note items not yet correct
- Categorise: critical (delay handover), major (fix within 1 week), minor (fix within 1 month)
- Track to closure with dates
As-built documentation
The "as-built" reflects what's actually installed, not what was designed. Differences arise inevitably during installation — a cable route changes due to a beam, a speaker moves 200mm because of a service. Update the documentation to reflect reality.
Standard as-built deliverables:
Network diagram — physical and logical:
- Patch panel port allocation
- Switch port allocation
- AP locations and SSIDs
- VLAN structure
- Internet WAN details (provider, speed, IP if static)
- Server / NAS details
- Equipment rack contents
Electrical schematics — supplementing the registered electrician's:
- Circuit allocation for AV, smart-home loads
- Lighting circuit assignments
- Smart device circuit grouping
Lighting schedule — by room:
- Each fitting's location, model, lamp type
- Each switch's location, model, function
- Each scene's settings
Audio/Video routing — for AV systems:
- Source-to-zone matrix
- Speaker-to-amplifier mapping
- HDMI input/output assignments
Heating zone diagram — for multi-zone:
- Boiler / heat pump details
- Zone valve / manifold layout
- Thermostat locations
Security plan — if alarm system:
- Sensor locations
- Camera positions and field of view
- Panel locations
- Monitoring service details
O&M manual
The Operations and Maintenance manual is required under CDM 2015 for all residential projects with notifiable structural / M&E content. For smart-home installs:
- Equipment inventory with model and serial numbers
- Manufacturer manuals for each major piece
- Warranty information per device
- Maintenance schedules — annual, periodic
- Spare parts list
- Emergency contacts (electrician, plumber, integrator)
A bound paper copy plus a PDF copy is best — the paper goes in a kitchen drawer, the PDF in cloud storage.
User training
The training session is the most underrated part of handover. Key points:
- Do it after a snag list closure — don't train on a system with known issues
- All household members present — wife, husband, partner, children, cleaner, anyone who'll use it
- Walk through real use cases — "When you come home in the evening, here's how you set up for cooking"
- Show the simple things first — "How to play music in the kitchen", "How to dim the lounge lights"
- Show the wow features — "Watch this: 'Hey Alexa, movie night'"
- Show the troubleshooting — "If the lights stop responding, here's the reset button"
- Record the session — short videos for later reference; client likes; you save support calls
Training typical duration:
- Single-system smart heating: 30 minutes
- Multi-room audio: 30-45 minutes
- Lighting control + heating + audio: 1-1.5 hours
- Whole-house automation with cinema: 2-3 hours
Credentials transfer
A secure handover of credentials is essential. Approaches:
Best — password manager export
- Set up a household password manager (1Password Family, Bitwarden, Dashlane)
- Transfer all device and account credentials into the manager
- Train family members on accessing it
- Installer retains administrative access only by mutual agreement
Acceptable — printed credentials in sealed envelope
- Print all credentials on paper
- Seal in tamper-evident envelope
- Hand to client; document the handover
- Client stores securely; installer destroys their copy
Unacceptable — email or chat
- Plain-text credentials in email or WhatsApp
- Permanently in client's inbox; in your sent folder; in their phone
- Common security incident vector
The PSTI Act 2024 mandates that products avoid universal default passwords — installers should not undermine that by handing over credentials insecurely.
Maintenance and support plans
A modern smart-home system needs ongoing care. Typical service plans:
Reactive only (basic) — call out for faults, charged hourly. Cheapest for the homeowner; most expensive when something goes wrong.
Annual maintenance visit (mid-tier) — once-per-year visit covering:
- Firmware updates on all major devices
- Battery replacement on remote / battery devices
- Network performance review
- Account credential refresh
- Device end-of-life flagging
- Brief client refresher training
Comprehensive support contract (premium) — annual visit plus:
- Remote support (typically capped hours/month)
- Priority response for faults (24/48-hour)
- Software updates and minor reconfigurations included
- Hardware replacement at cost (parts only)
Pricing typical 1-3% of installed system value per year.
Remote access for support
For ongoing remote support, configure secure remote access at handover:
- VPN — WireGuard or OpenVPN configured at the firewall; installer connects to LAN as needed
- Reverse SSH tunnel — for command-line systems (Linux, NAS)
- Vendor remote tools — Crestron Cloud Pairing, Control4 4Sight, UniFi remote, Philips Hue cloud — vendor-managed
- Screen sharing on demand — TeamViewer, AnyDesk for occasional support of Windows/Mac equipment
Remote access must be:
- Documented in a service agreement
- Auditable — installer logs each session
- Time-limited — credentials rotated periodically
- Removable — client can disable at any time
First-month follow-up
A scheduled 30-day follow-up call or visit catches issues that emerge with real-world use:
- "Have you used scenes yet? Any not working as expected?"
- "Has anyone in the family had trouble using the system?"
- "Any devices that need re-pairing or reset?"
- "Any feature you wished worked differently?"
This 30 minutes of contact prevents months of frustration. It also generates referrals — a happy client one month in is your best marketing.
End-of-life planning
Smart-home devices have a lifecycle:
- Active devices (hubs, routers, switches) — typically 5-7 years before performance degrades or vendor support ends
- Battery devices (sensors, remotes) — battery replacement every 2-5 years; replacement of unit every 7-10 years
- Wired devices (in-wall switches, in-ceiling speakers) — long lifespan; 10-15 years
- Cabling infrastructure — 25+ years; protocol-agnostic
A maintenance plan should track device end-of-life dates and prompt the homeowner ahead of needed replacements:
- "Your Hue Bridge v2 will stop receiving updates in 2027 — recommend replacement to v3 next year"
- "Your IoT cameras are 6 years old — consider modern replacements with better PSTI compliance"
Building Regulations and warranty paperwork
At handover provide:
- EIC / Part P certificate — for all notifiable electrical work
- MEIWC — for non-notifiable but documented work
- Building Regulations Compliance Certificate — issued by CPS scheme
- Manufacturer warranties — registered to the homeowner
- IBG warranty (if applicable) — for installations where insurance-backed cover applies (rare for smart home; common for related works like waterproofing)
- Public liability insurance certificate — installer's PL cover at time of works
- PSTI Statement of Compliance — for connectable products installed
Originals to client; copies to installer's project file.
Frequently Asked Questions
Should I record the user training session?
Yes — record on phone or tablet, transfer to client cloud folder. Many clients forget what they learned in the first month and a recorded walk-through is hugely valuable. Also useful when household members change (new partner, children growing up, cleaner, lodger).
What if the client wants to do their own maintenance?
Provide the documentation and credentials, train them on the system, and step back. Some technically-inclined clients prefer self-management, especially for software updates. Make clear what is in your scope (e.g. consultation hours billed) and what is theirs.
How long should I store project files?
CEDIA recommends 7-10 years minimum for active projects. Files should be:
- Project programming files (ETS for KNX, system files for Crestron, etc.)
- As-built documentation
- Photos during construction
- Email correspondence
- Invoices and contracts
For systems with long warranties (10+ year IBG) keep until the warranty expires plus 2 years.
What's the right level of detail for the O&M manual?
Enough that another competent integrator could pick up the system and continue work. Too much detail and it's never read; too little and it's useless. Aim for:
- A 1-page summary "this is the system at a glance"
- Equipment list with manufacturer, model, serial, location
- Network diagram
- Maintenance schedule
- Emergency contacts
- Manufacturer manuals as appendices (PDF references, not paper inclusions)
Do I need to insure my client's smart-home data?
Probably not directly — your professional indemnity insurance should cover loss of data caused by your error. However, do clarify:
- Where credentials are stored
- Who has remote access
- What happens if you cease trading (a clause in the contract)
- Who owns the project files (typically you, with client right to copy)
A well-drafted contract handles this; consult a solicitor for the standard terms.
Regulations & Standards
CDM 2015 — Construction (Design and Management) Regulations; O&M deliverables
CEDIA Project Documentation Recommended Practice — handover standards
BS 7671:2018+A2:2022 — Wiring Regulations; certification requirements
Building Regulations Part P — Electrical safety; notification and certificates
PSTI Act 2024 — IoT product security; Statement of Compliance per device
GDPR / UK DPA 2018 — Personal data including credentials; secure handling
CDM 2015 — Health and Safety File — for projects with multiple contractors
IPSEC standards — IETF standards for VPN remote access security
CEDIA Recommended Practices — Project documentation guidance
HSE CDM 2015 — Working with O&M manuals — CDM duties
PSTI Act 2024 implementation — gov.uk
BSI Knowledge — handover documents — Industry guidance
1Password Business / Family — Password manager
Bitwarden — Password manager (free tier)
iot device cybersecurity — Security briefing as part of handover
cedia membership smart home — CEDIA-aligned documentation standards
smart home system specification — System spec feeding into handover scope
home networking for av — Network as-built documentation
part p implications smart home — Electrical certificate handover