How to Prepare a Landscape Lighting Handover When a Home Changes Hands

What should the handover accomplish?

The receiving person should be able to identify the system's intended operating arrangements, locate the relevant records and contact the appropriate provider when something differs from normal. That is a more useful goal than collecting every document associated with the property. Begin with the questions a new homeowner or authorized manager will actually need to answer during an ordinary evening.

Separate the information handover from the property transaction and any technical inspection. A record of controls does not establish what equipment is included in a sale, whether a warranty transfers or whether the installation meets applicable requirements. Those matters need their own appropriate review. Label the handover's scope so the recipient understands which questions it answers and which remain with the seller, agreement, manufacturer or qualified professional.

Who should prepare the information?

Ask the person who currently manages the lighting to assemble what is known, with help from the installer or service provider where appropriate. Identify one coordinator so that model numbers, schedules and service notes do not arrive as unrelated messages. The coordinator should distinguish firsthand observations from information supplied by someone else rather than presenting every recollection as a verified technical fact.

The receiving person should participate in a walkthrough and identify unresolved questions. A document that seems clear to the outgoing owner may rely on familiar landmarks or account shortcuts. If a professional contributes information, record what they reviewed and the date. Do not imply that a provider inspected the entire system merely because it supplied an old invoice or answered a narrow question about one component.

What belongs in the system inventory?

Record identifiable components at a level useful for service: visible equipment labels, model information, approximate location, associated area and source of the information. Use photographs where they can be taken safely without opening enclosures or disturbing equipment. Mark unknown information clearly. A model guessed from appearance can send the recipient toward the wrong manual or replacement part.

Keep the inventory separate from a prescription for repair. The receiving person needs to know where information is stored and who can assess the system, not how to perform electrical work from a general article. If equipment is inaccessible or its identification is unclear, leave that field pending for the appropriate provider. A partial inventory with honest limits is preferable to a complete-looking list built from assumptions.

How should lighting areas be described?

Use plain names linked to a simple property sketch or photographs: front approach, side path, patio edge or a particular planting area. The names should help a newcomer connect a control with the area it is intended to serve. Avoid relying only on internal labels such as zone three when nobody has recorded what that label means in the current arrangement.

Do not infer wiring or circuit relationships from which lights appear to turn on together. Describe the observed operating association and let the qualified provider confirm technical configuration where necessary. The sketch is a navigation aid, not an as-built electrical drawing. If professional plans exist, preserve their identifiers and versions alongside the simplified map so the recipient can distinguish an owner's guide from technical documentation.

What should be recorded about normal operation?

Describe what the outgoing owner expects to see under the current settings and conditions. Include the date, relevant schedule reference and any known seasonal adjustment. A brief observation can help the recipient recognize an unexplained difference, but it should not be described as a performance guarantee. Trees, weather, settings and service conditions can change what a person sees.

Record exceptions explicitly. If one area is intentionally off or a fixture is awaiting review, do not let the recipient assume that condition is the intended design. Separate observed behavior from the reason someone believes it occurs. The record should help frame a useful service question without diagnosing a fault. A statement that a light did not operate on a particular evening is different from a conclusion about why it failed.

How do you document schedules and controls?

Identify the control method actually used and where the applicable instructions can be found. Record the current user-facing schedule in ordinary language, with the date it was checked. The Department of Energy's exterior-lighting resources discuss controls as part of lighting operation and efficiency; they do not establish the correct settings for this property or promise a particular saving from the handover.

Do not copy generic programming steps for a different product. A schedule label, time setting or seasonal behavior can depend on the installed equipment and its configuration. Preserve the correct manufacturer's documentation and ask the provider when the behavior is unclear. The handover should explain how to find reliable guidance and who manages changes, rather than inviting a new owner to experiment with unfamiliar technical settings.

How should app or account access be handled?

Identify whether an app or online account is involved and ask the provider or manufacturer for the supported transfer process. Do not place passwords in a public handover document, share the outgoing owner's personal account casually or assume that a change of house ownership transfers an account automatically. The appropriate process depends on the actual product and the parties involved.

Record that an access handover is required and who is responsible for completing it. Keep the access action separate from the informational walkthrough. This article does not perform a credential change or authorize anyone to access another person's account. The receiving person should confirm that the approved arrangement works through the provider's normal process. A screenshot of an app is not evidence that the recipient has legitimate, usable control of the system.

What is a worked example of an incomplete handover?

Imagine a fictional property with lighting described as front and back in an owner's notes. The receiving person discovers that the app uses different zone names and one area has an unresolved service issue. The outgoing owner provides screenshots but the account still belongs to a personal email address. None of these facts proves a technical fault, yet the recipient cannot confidently manage the intended arrangement.

The coordinator creates a plain-language area map, labels the unresolved issue and asks the provider to explain the supported account-transfer process. The final record states which information is confirmed and which action remains pending. This example shows why a document collection and an operational handover are different tasks. The solution is not to guess credentials or technical settings, but to connect the missing responsibilities with the right people.

Which manuals and invoices are useful?

Preserve documents that can be tied to the installed equipment or a specific service event. Record the provider, date, item or area and scope described. An invoice can identify what was supplied or worked on, but it may not represent a current complete inventory. Keep that limitation visible rather than assuming every item in an old proposal was installed exactly as described.

For manuals, confirm the product identifier and version where possible. A link to a manufacturer's general website may be helpful, but a specific applicable manual is more useful. Do not silently substitute a similar model's instructions. If the correct document cannot be found, record the question for the provider. The handover should make reliable information easier to locate without turning every historical file into an active operating instruction.

How should maintenance history be summarized?

Use a dated list of observed issues, requested work, provider-reported actions and remaining questions. Identify the area or component involved. A note saying system serviced is less useful than a record showing which task was performed and which parts were not examined. Preserve the provider's description rather than expanding it into a broader inspection claim.

Record recurring observations without diagnosing them. If the same area has needed attention several times, that history may help a qualified provider assess the next report. The recipient should be able to distinguish a resolved item from an open concern. Do not remove a known issue from the handover simply because the property looks attractive on the walkthrough evening or because the next person has not yet noticed it.

What should happen to warranty information?

Collect the actual warranty documents and identify the issuing party, product reference and source. Ask the appropriate provider or manufacturer about any transfer conditions rather than assuming coverage follows the property. This guide does not interpret warranty terms or determine whether a particular claim will be accepted. Record the question and the response accurately.

Keep a manufacturer's product warranty separate from an installer's service arrangement or any representation in a property transaction. They may cover different things and have different conditions. A sales phrase such as long-lasting equipment should not become an unsupported promise in the handover. The useful document shows where the recipient can find the terms and which questions still need an answer from the responsible party.

How should spare parts be recorded?

List only parts that can be identified reliably, along with where they are stored and any provider information linking them to the system. Do not assume an unlabelled item is suitable because it looks similar. A spare component can help a service visit, but choosing and fitting it may require technical judgment. Keep that work with the appropriate provider.

Distinguish a retained sample, unused supply and removed component. Those categories can be confused in a storage box. If the history is uncertain, label it unknown and ask the provider before anyone relies on it. The record should prevent a newcomer from treating every item left in a garage as an approved replacement. It does not need to become a comprehensive parts catalogue if a simple, accurate list answers the practical question.

How do you plan the walkthrough?

Choose a suitable time and conditions for observing the lighting through normal authorized operation. Agree on the areas to review and avoid unsafe access or technical manipulation. The receiving person should use the plain-language map and identify where the instructions are unclear. The outgoing owner or provider can explain known arrangements, with unresolved questions recorded rather than answered by guesswork.

Keep the walkthrough within its scope. It can help someone understand the intended appearance and controls, but it is not an inspection of every concealed component or confirmation of all requirements. If a concern needs a specialist, stop that part of the discussion and assign the follow-up. The handover is more credible when it states what was observed than when it claims that an evening tour proved the entire system was in good condition.

What should the receiving person demonstrate?

Ask them to identify the main records, locate the approved contact and explain the intended normal operating arrangement in their own words. Where appropriate, they can follow the supported user instructions under the agreed access arrangement. This is a comprehension check, not a test of technical skill. The aim is to discover unclear labels and missing information before the outgoing owner becomes difficult to reach.

Record assistance that was needed. A task completed only after a verbal hint may indicate that the written guide needs improvement. Do not treat the recipient's uncertainty as a personal failure. Familiarity with the property can hide how much the outgoing owner knows implicitly. Use the observation to make the handover clearer, then verify the relevant part again if a correction materially changes the instructions.

How should unresolved issues be handed over?

Create a short list with the observation, date, affected area, supporting record, responsible contact and next action. Avoid vague descriptions such as needs attention. State what remains unknown and whether the issue has been referred to a provider. Do not promise a repair date or outcome that has not been agreed by the party responsible for the work.

Keep the issue list connected to the property transaction or management process as appropriate, with suitable professional advice where needed. This article does not decide who bears a cost or obligation. Its documentation method helps the relevant people understand the same facts. An unresolved issue should remain visible until an actual decision or service result supports changing its status, rather than disappearing when the handover document is marked complete.

What should a service request include after handover?

Give the provider the system identifier, location, observed behavior, relevant date and available history. Describe what changed from the recorded normal arrangement, if known. Include appropriate photographs without exposing account credentials or unrelated private information. Do not assign a technical cause merely to make the request sound more informed.

Ask what access or information the provider needs before the visit and who may authorize additional work. A clear handover can reduce the amount of background reconstruction required, but it does not guarantee a faster repair or lower cost. The provider still needs to assess the actual system and scope. Use the record to communicate accurately rather than to prescribe a diagnosis or replacement before the appropriate review.

How do you keep the handover useful after the move?

Assign the receiving owner or manager to maintain the current summary when settings, equipment or service arrangements change. Add dated updates and preserve supporting history. A handover becomes outdated if the first service visit changes a component but the record continues to point to an old manual. The useful guide is maintained information, not a one-time packet filed away at closing.

Review the contact and unresolved-issue list when a provider changes or a question is resolved. Keep account information in its approved location rather than copying it into every revision. If several people manage the property, identify the authoritative record and who may update it. The process should remain simple enough to use; a short current summary is better than a detailed archive nobody can distinguish from active instructions.

Can AI organize the handover documents?

An assistant can help index authorized files, extract candidate model references and organize questions for review. Require source locations and uncertainty labels. It should not infer electrical configuration, warranty transfer, account rights or equipment suitability from a partial description. Review important identifiers against the actual label or source document rather than trusting a polished extraction.

Keep sensitive information out of tools not approved for it. A document bundle can contain property details, personal contact information or account references that the summary does not need. The assistant's role is organization, not inspection or authorization. If the source is missing, the correct output may be a question for the provider. Do not let a generated completion checklist conceal that the underlying operating or access issue remains unresolved.

What should the downloadable worksheet include?

Use fields for area, observed function, component reference, source document, control reference, service history, unresolved issue, contact and receiving-owner confirmation. Keep credentials separate. The worksheet should help someone connect the physical property with the records and responsible people. It is not a technical drawing or a substitute for manufacturer instructions.

Try one area before documenting the whole property. Ask whether another authorized person can identify the relevant record and understand the next action from the entry. If not, revise the description. The worksheet's value comes from usable references, not the number of filled cells. Leave unknowns visible and route them to the appropriate source rather than guessing to make the packet appear finished.

FAQ: Does a complete inventory establish that the system is safe?

No. An inventory describes recorded equipment and information. It does not establish installation quality, condition, compliance or suitability. Those questions may require appropriate professional inspection and applicable records. Keep the documentation claim narrow so the recipient does not mistake a well-organized packet for technical approval.

If the walkthrough reveals a concern, record the observation and involve the responsible provider. Do not ask a homeowner to open equipment or perform an improvised test to complete the worksheet. The purpose is to improve the next conversation and preserve operating knowledge, while leaving technical work and judgments with the people qualified and authorized to make them.

FAQ: Should the outgoing owner demonstrate every possible setting?

Not necessarily. Focus on the normal supported user operations and the information the recipient needs to manage them. An exhaustive demonstration can be confusing and may involve functions outside the intended handover scope. Use the applicable manufacturer guidance and provider advice to identify what should be shown.

Record the settings or functions not covered and where reliable instructions can be found. The receiving person should know how to ask for help rather than feeling expected to experiment. A concise demonstration with a clear recovery contact is often more useful than a long sequence of changes that nobody records or understands afterward.

FAQ: What if a different provider will service the system?

Share the available records and explain which information is confirmed, reported or unknown. Ask the new provider what it needs to assess the work and whether it can support the installed products. Do not assume that a provider accepts responsibility for every prior installation simply because it offers landscape-lighting service.

Lumascapes' service information is a place to discuss a potential scope directly. This guide does not promise that every system or location can be supported. The documentation can help frame the inquiry, while the provider determines its actual offering and assessment needs. The next useful step is an accurate service conversation, not a claim that transferring the packet transfers all responsibility for the system.

Use the blank worksheet

Download the editable preparation worksheet. Complete it with actual observations and source references; an empty or filled form is not professional approval.

Related reading and next steps

• Discuss an existing-system service scope
• Read about service for another installer’s system
• Contact Lumascapes
• Compare the scope of provider proposals

Primary sources and scope

Sources checked October 25, 2026. Proposed workflows and fictional examples are original editorial material; linked organizations do not endorse this guide. No professional review or client outcome is claimed.

• DOE: exterior-lighting controls background; not property-specific advice
• FTC: reviewing contractor scope and source information