Smart Home Documentation & Handover Standard
A smart home project isn't finished when the lights turn on — it's finished when the next installer can open the file and understand the system without calling you. Here's the documentation package PanelCraft treats as standard practice on every project, wired or wireless.
Building the handover package
Capture as-built during commissioning
Record what was actually wired, paired and configured — not the original design — while the system is still open and testable.
Build the device & address inventory
List every automated device with its protocol address or network identity and its physical location, whatever the mix of KNX, DALI, Zigbee/Thread or Matter.
Diagram the network and topology
Map how bus segments, gateways and IP devices connect, with bus/communication cabling clearly separated from power cabling.
Hand over credentials and panel records formally
Pass access credentials to the owner or facility manager — not just an installer's personal account — together with panel documentation to IEC 61439.
What belongs in the file
Reality, not the original plan
The core of the package is documentation that reflects what's actually installed on site — every change during commissioning gets folded back in.
Protocol-agnostic by design
The same structure works whether the installation is wired KNX/DALI, a wireless Zigbee/Thread/Matter retrofit, or a mix running on a local hub like Home Assistant.
Vendor-neutral credential handover
Access stays with the project owner, not locked inside one installer's personal cloud login — so a future contractor isn't blocked from day one.
Topology that separates bus from power
Network diagrams show gateways, bus segments and IP devices with communication cabling kept visually distinct from power cabling.
Panel records aligned to IEC 61439
Any panel built for the installation follows the same low-voltage switchgear assembly discipline as any other panel, with automation modules documented alongside breakers.
A living document, not a one-off PDF
The package is meant to be updated at every service visit, so the as-built stays as-built instead of drifting from reality again.
The handover package
Five components PanelCraft includes on every project — and recommends any integrator adopt as standard practice.
- As-built schematics reflecting the completed installation
- Device & address inventory with physical locations
- Network & topology diagram
- Secure access credential handover record
- Panel documentation to IEC 61439
Frequently asked questions
What counts as 'as-built' documentation?
Drawings and lists that match what was actually installed and configured on site — including every change made during commissioning — not the original design drawings.
Why does handover documentation matter if the system already works?
Because the day it needs a service call, whoever shows up either reads the file or starts reverse-engineering the installation from scratch. Without documentation, effective ownership of the system quietly stays with the original installer, even after the project is closed.
Does a wireless Zigbee/Thread/Matter installation need the same package as a wired KNX system?
Yes, adapted to the technology — you still need a device/address inventory and network diagram, just without the bus cable schematics a wired system requires.
Who should hold the access credentials after handover?
The project owner or their facility manager, in a record that survives staff changes — not only inside the original installer's personal app account.
Does panel documentation change for a smart-home panel versus a standard distribution board?
The IEC 61439 assembly discipline is the same; the difference is documenting the extra DIN-rail space for automation modules and gateways, and keeping bus wiring separated from power wiring.
Setting up handover documentation for a project?
Talk to our engineers about applying this standard to your next smart-home installation, wired or wireless.