What should you receive at the end of a smart-home installation?

The handover starts in the proposal

A finished installation should be understandable to someone other than the person who built it. Agree the handover deliverables before work begins: the intended routines, equipment records, access arrangements, practical demonstration and any support included in the price.

Acceptance criteria make the result easier to review. “Evening lighting scene operates from the agreed wall control and dashboard” is specific. “Smart lighting installed” leaves too much unclear. Include relevant failure and recovery behaviour in the scope rather than discovering it after a problem.

Know what you own and how to access it

You should know which accounts belong to you, where the main controller is and how authorised household members access it. Agree how any installer access is granted and removed. Do not put passwords in a printed equipment list or an ordinary enquiry email.

Also list third-party services and subscriptions separately. Ending an optional support arrangement is different from cancelling a service on which a feature depends. A clear dependency list helps you make that distinction and avoids surprise costs or loss of functionality.

Make recovery a practical deliverable

Home Assistant provides backup and restore tools, documented in its common-tasks guidance. If backups are part of your installation, ask where they are stored, who can access them and what is needed to restore them, including any required encryption information.

Our proposed handover records the agreed backup arrangement and recovery responsibilities. A backup existing somewhere is not the same as a household knowing how to use it. The project scope should define the level of recovery testing and support being provided.

Supporting guidance: Home Assistant backup and restore guidance

Learn the ordinary controls and the exceptions

Walk through the routines you will actually use: arriving home, changing lighting, adjusting comfort and temporarily overriding automation. Keep the instructions short enough to consult when needed. Explain unavailable readings and the route to normal manual controls.

Then cover common changes: replacing a phone, changing internet equipment or adding a device. You do not need to become the system designer, but you should know which changes are routine and which deserve help. A documented system is easier to maintain and to hand to a future specialist.

Agree what support means

Ask about the support period, availability, included corrections and the treatment of new feature requests. Avoid assuming that a successful installation includes permanent monitoring or emergency assistance. Those are separate commitments that need their own scope and price.

At Cotswold Automation, documentation and a practical handover form part of the agreed implementation scope. Care memberships are still being developed. Your proposal should therefore explain the support actually included now, so you can decide with clear expectations rather than rely on a future plan.