Loxone Commissioning & Handover Documentation
A professional Loxone installation ends with a documented handover package, not just a working system. Give installers and customers a clear paper trail: project file, device list, network settings and test results.
The handover package, step by step
Export and version the Config project
Export the final Loxone Config project file and label it with a version date, so any future service call starts from the exact file that was commissioned.
Compile the I/O and device list
List every connected device and I/O point in the installation, so the customer and any future installer know exactly what is on the system.
Document network settings
Record the Miniserver's static IP and any VLAN configuration on a network settings sheet, separate from the Config project itself.
Run and log function tests
Test each function group — lighting, shading, heating, security — and log the result, so commissioning is verifiable, not just assumed.
What a documented handover protects
core deliverables
Project file, device list, network sheet, test log, training checklist and backup schedule — the six pieces of a defensible handover.
Versioned Config project file
The exported Loxone Config file, dated, so the commissioned state is traceable and not lost to overwrites.
I/O and device list
A record of every device and I/O point on the Miniserver and Loxone Link/Tree/Air network, for service and troubleshooting.
Network settings sheet
Static IPs and VLAN assignment (if used) documented outside the project file, where a network engineer can find them.
Function test log
A per-function record — lighting, shading, heating, security — showing what was tested and confirmed working at handover.
Training checklist and backup schedule
Proof the customer was walked through the system, plus an agreed schedule for backing up the project file going forward.
Handover package contents
What we recommend every commissioning finishes with.
- Exported Loxone Config project file with version date
- I/O and device list
- Network settings sheet — static IPs, VLAN if used
- Test log per function: lighting, shading, heating, security
- Customer training checklist and backup schedule for the project file
Frequently asked questions
What should a Loxone handover package include?
At minimum: the versioned Config project file, an I/O and device list, a network settings sheet with static IPs and VLAN details, a function test log, a customer training checklist, and a backup schedule for the project file.
Why version the Config project file with a date?
Loxone Config projects get edited over years of service calls. A dated version at handover gives a fixed reference point — proof of what was actually commissioned, before any later changes.
Why document static IPs and VLAN settings separately from the project file?
Network settings are needed by IT staff and future installers who may not have or need access to the Config project itself, so they belong on their own sheet.
What should a function test log record?
For each function group — lighting, shading, heating, security — log what was tested and the result, so commissioning can be verified rather than taken on trust.
Who keeps the Config project file backup after handover?
That should be agreed and written down as part of the handover — typically the installer keeps a copy and the customer or facility manager knows the backup schedule.
Need a second pair of eyes on your handover package?
Our engineers work with certified Loxone Partner installers across the EU — talk to us about commissioning documentation, device lists or your next panel build.