Taking over a smart home: Assess first, then offer changes

You receive an enquiry about changing a smart home that is already set up. The original installer is no longer the contact, the residents want different routines, and a project file is supposed to exist somewhere. For your integration business, this creates a specific job: establish what foundation is actually available for the requested change. The customer buys clarity about the existing installation before deciding on alterations.

The key question is whether you can already offer a clearly defined change or whether a separate assessment comes first. Neither a working app nor a photograph of the distribution board answers that question. You need a traceable connection between the desired result, available documentation and the installation actually examined. A defined takeover assessment makes that connection understandable and your work tangible for the customer.

Start with a specific change

First ask what should be different in the home. Does the owner want to change an existing evening routine, add a room or understand the installation after buying the house? These situations call for different depths of investigation. A confusing control sequence may initially call for an explanation. An additional function raises the question of which parts need to work together. Describe the reason so the customer can repeat it without product names.

Then ask for a description of the current routine. What happens when the relevant button is pressed? Which other rooms are affected by the same action? What should stay as it is? You are collecting observations for the assessment, without confirming a cause or assuming that a change is possible. A comparison of current and desired behaviour is particularly useful when unresolved points remain visible.

Agree which areas the assessment covers. Investigating the living room controls does not automatically mean examining shading, heating and access throughout the building. If your specialists identify a relevant connection to other areas, they explain that dependency before extending the investigation. The customer can then decide whether to commission the additional clarification or initially narrow the project.

Sort documents by what they establish

Ask which documents exist: product details, operating descriptions, invoices, plans and any files from the original project work. Ask when they were produced too. A document may describe an earlier installation stage, with further rooms added later. The useful question is therefore which part of today’s installation the documentation demonstrably describes, as well as whether documentation exists.

Keep three things separate in your overview: information reported by the customer, documents actually received and connections your team has already checked. A filename containing “final” initially belongs in the second group. Whether its contents match the installation and proposed work is a separate technical question. This distinction prevents an assumption from becoming an apparently confirmed foundation when passed to the project manager.

For KNX, the official ETS6 project export documentation identifies the knxproj file format. This is a system-specific example of project documentation, not general approval for a takeover.

Discuss who can obtain missing documents. A file may remain with the previous contractor, or the former owner may only know an old contact. Your proposal should distinguish assessing available documentation from helping obtain it. If your business offers that help, name the specific result. Contacting someone promises neither a complete set of data nor reconstruction of missing project work.

Separate operating access from the basis for changes

A customer may operate the lights every day while lacking documentation for the requested change. Ask separately about everyday use and project editing. Who can explain the current controls? Who knows the businesses previously involved? Which access does your team actually need to clarify for the agreed investigation? This keeps the assessment focused on the customer’s concern before any technical action begins.

The general record needs a note of responsibilities, rather than a collection of passwords. Record the named person with whom your team will arrange necessary access and its secure handling. The contractor defines the actual procedure for the system and job. The customer should understand what cooperation is needed and which investigation remains unresolved without it. Instructions for bypassing existing access restrictions are outside the takeover proposal.

Also establish whether other businesses continue to work on the installation. If an existing provider changes settings at the same time, your team needs an agreed project state for its assessment. Agree with those involved which documented state the assessment concerns and how later changes will be identified. This creates an organisational basis for the appointment without promising a technical lock.

Give the assessment a result the customer can buy

Describe the outcome from the customer’s perspective: after the assessment, the owner should know what foundation exists for the desired change, what questions remain and which next job appears appropriate. You could offer an overview of the examined area, a comparison with received documentation and a technically reasoned recommendation. Choose only elements your business actually delivers and explain them in the specific proposal.

State what remains unchanged during the assessment. The customer should not confuse examining the installation with commissioning reprogramming. If investigation requires interventions, your specialists must clarify their scope and prerequisites separately beforehand, particularly where other building functions could be affected. This proposed job structure replaces neither technical evaluation nor the individual planning the work requires.

Agree a decision point for additional findings. If documentation does not cover a relevant part of the building, for example, your team can explain the finding and offer a defined additional investigation. The customer gets a choice before further work arises. The initial assessment still has a result: a precisely identified gap helps the owner commission the next step with understanding.

A further distinction concerns an existing fault. If the customer wants a new routine, you examine the prerequisites for that change. If a malfunction is reported, the investigation must concern that fault. Both may emerge in one conversation, but the proposal should keep them clear. A light that occasionally fails to respond and a different evening routine are two tasks. Ask about observed situations and let your specialists determine the appropriate investigation before offering both together.

Also ask what outcome is sufficient for the customer’s next decision. Someone who first wants to know whether your business can take on further work needs a different result description from someone already commissioning a specific alteration proposal. Write that expectation into the assessment job. Your team can then focus the investigation on the agreed question and explain why a finding is sufficient for that decision or which specific information is still missing.

Fictional case: A different evening routine after buying a house

An entirely fictional owner has bought a house with an existing smart home installation. There is a shared evening control on the ground floor. The owner wants the study lights to stay on longer while retaining the existing routine in the living area. The previous owner provided operating notes and a project file. Your business has not yet examined whether they reflect the current state.

Your first proposal therefore concerns examining this routine and its documented connections. The customer supplies the available documentation and names the previous contact. Your team compares the described use with the agreed investigation area and records unresolved connections. Heating, access and other floors are not casually listed as also examined. Any necessary extension would be discussed beforehand.

The example has two possible outcomes. If the checked foundation supports a specific alteration proposal, you describe that separately from the completed assessment. If essential information is missing, you offer a named clarification step or explain why your business is not yet offering the alteration on that basis. Either outcome gives the owner a sound decision about your next scope of work without anticipating a successful conversion.

The original wish remains the reference point for discussing the later proposal: use the study differently while preserving the living area. A lengthy installation report alone does not answer it. Explain which finding concerns the requested change and what it means for the next job. The customer can then connect your investigation with daily life, instead of receiving documents without a clear decision to make.

Connect the takeover decision to the next job

Present findings in an understandable order: examined routine, associated documentation, unresolved questions and the next step offered. Clearly distinguish checked facts from assumptions still requiring clarification. If you can offer an alteration, the customer should see the specific foundation used. If you recommend further investigation, name the question it is intended to answer.

Discuss the later handover too. Which documents from your own job will the customer receive, how will edited versions be identified and who will discuss unresolved points? This shows how the new relationship will be documented from the outset. You do not need to require an extensive support package first. A clear description of the result and its agreed recipient is enough to start shaping the actual proposal.

Leave unexamined building areas explicitly identified as such. A customer should not infer a promise about the entire third-party installation from your willingness to work together. At the same time, explain positively which part your team wants to take on now and which additional foundation would enable a later step. That gives your business a technically understandable position: a clear path from an unknown starting point to a reasoned alteration decision.

During internal handover, check whether a colleague understands the same job from your notes. They should see which routine is involved, which documents actually exist, who is obtaining anything else and when the customer needs to decide again. If clarity is missing, add that specific point. The assessment then becomes a distinct service that others can continue, without restarting a general smart home consultation at the next meeting.

New conversations for your integration services

If your business offers these services, you can introduce them in conversations with new prospects. The webRichtung smart home industry page leads to the actual customer enquiry offer. You clarify the specific takeover situation yourself; it is not a promised enquiry attribute or order filter. Register your business there and check the current price in webRichtung Customer before commissioning the service.