Irrigation and landscape service handoff

Transfer a shared record rather than separate assumptions

Landscape care and irrigation maintenance affect the same property but may be delivered by different businesses. A useful handoff tells each provider what areas it serves, what it is expected to observe and how it requests a change. Do not assume the lawn company owns the controller program or the irrigation contractor diagnoses every plant concern.

Prepare the current area and zone information, equipment identity, accepted program, care agreements and open findings. Keep uncertain zone boundaries or plant identification marked unknown. A diagram used for communication should not be presented as a verified buried-system plan.

Name the roles

• Routine landscape provider: the actual cutting, bed or planting scope.
• Irrigation provider: the accepted system assessment, repair and program responsibilities.
• Observer: the person reporting visible changes between visits.
• Decision maker: the person authorizing changes and extra work.
• Backup contact: the person reached if the owner is unavailable.

One person may hold several roles, but each must be understood. A provider should know whether it is authorized to make a routine agreed adjustment, propose additional work or only report a concern for the owner.

Keep the current watering basis with the program

SFWMD's current irrigation resources provide the starting point for checking the actual address and water source. Keep the date and source used by the provider with the accepted program. Do not pass along an old schedule without reviewing the applicable requirement.

Name one person who approves and records program changes. Avoid several participants independently changing runtimes or restoring a previous program. The record should explain what changed, why and who supplied the recommendation.

Separate observations from diagnoses

A landscape crew can report a dry-looking patch, persistent wet area or damaged component without declaring its cause. Ask for the location, date, safely obtained photograph and the relevant task or zone if confirmed. Keep the finding for the appropriate assessment.

UF/IFAS Florida-Friendly Landscaping principles connect plant placement, watering, inputs and runoff. A useful handoff therefore preserves the wider question rather than automatically adding irrigation or treatment when appearance changes. Ask which professional will assess each concern.

Make exceptions actionable

Ask each provider to report when its ordinary work cannot be completed. Identify access failure, a damaged component, another contractor's project or a condition outside the accepted scope. The message should state what happened, what was completed and the next recommended action.

Agree on how a material concern reaches a decision maker and backup. A routine report filed where no one reads it is not an effective handoff. Keep the notification route private and make clear which messages require a response.

Control extra work and specialist tasks

Require a defined finding, proposed scope, quote or clear pricing method and authorization for work outside the agreement. Confirm the actual business's relevant qualifications for applications, connections or other specialist tasks. A routine maintenance relationship does not expand its lawful scope.

Keep access, account and credential information limited to authorized people. For a connected controller, use the product-supported sharing arrangement and identify who owns the account. Do not put administrative passwords in a broad service log or public message.

Update the plan after a project

New planting, repaired zones, changed equipment or a landscape redesign can make an old handoff inaccurate. Ask the project provider for the final product and area information, instructions and open findings. Transfer those records to the people maintaining the property and confirm who accepts the new duties.

Keep the earlier version for context, but label the current accepted plan clearly. Do not let a former program or task list remain the default merely because it is familiar. Record the date and reason for a substantive change.

Review before an extended absence and return

Before leaving, confirm the reporting contact, authority for extra work and unresolved concerns. An observer should not be asked to dig, open equipment or perform a technical test while the owner is away. Arrange qualified work through the agreed process.

Before return, request a summary of changes, completed tasks and open follow-up. Use it to plan the next appointment instead of treating every old recommendation as completed. Retain the record in My Home or another private system.

Reconcile one landscape change across both providers

If planting, bed layout or an irrigation area changes, record what changed, who assessed the relevant interface and who accepted the updated responsibility. A landscape crew's completion record does not automatically mean the irrigation provider knows the new arrangement. Likewise, controller work does not establish that a new planting's care has been accepted.

Use an interface ledger: location, changed feature, actual instruction source, receiving person and acceptance date. Leave unresolved items visible. For example, a provider can report a changed bed while the owner still needs to commission an assessment of its irrigation needs. Do not turn that report into an owner-authored runtime.

Close the program-change loop

Keep the current reported configuration and the person allowed to approve changes in a private record. When a qualified provider revises the program, ask it to state the reason and what related party needs to know. Use current SFWMD and local resources for the actual address rather than copying a seasonal rule from another home. SFWMD irrigation resources.

At handoff, distinguish information received from responsibility accepted. Ask the receiving company to identify tasks it declines or needs clarified. That protects the owner from assuming that a file transfer purchases an expanded service. The WRLW seasonal irrigation and empty-home landscape articles retain their broader advice; this module is the operational record between accepted services.

Who should change the controller?

The accepted arrangement should name the responsible qualified provider and approval process. Avoid independent undocumented changes by several people.

Can the caretaker diagnose a dry patch?

They can provide a useful dated observation within their role. The actual diagnosis belongs with the appropriate assessment, not an assumption based on appearance.

Does a handoff authorize every future repair?

No. Define the scope and limits of ordinary authority and require additional approval where needed. Keep decisions with the actual finding and proposed work.