What should I do when irrigation runs outside its programmed times?

Compare the observation with the complete program

Write down when watering was seen, the area or zone, how long it appeared to continue and whether the sequence repeated. Use a safe photograph of the display if practical. Keep the controller model and existing program record with the observation rather than assuming a remembered start time is the whole schedule.

Rain Bird's model-family support explains that multiple start times can cause a program to run through zones again. That is a product-specific possibility, not a diagnosis of every irrigation system. Ask the provider to use the manual and full configuration for the actual controller.

Identify who can change the system

Record who has local or app access: the owner, landscape company, irrigation provider or caretaker. Ask whether a recent change was authorized and documented. Several people adjusting the same program can make the expected behavior unclear even when no part has been diagnosed as defective.

Keep credentials and sensitive access details private. Do not share an administrative password in a public guide, directory message or broad email group. Use the product's supported access arrangement and name the person responsible for reviewing changes.

Gather the details before a visit

• Actual controller model and the current saved program if available.
• Date, time and zone or area observed.
• Whether watering repeated in a sequence or appeared continuous.
• Recent service, power interruption or accepted program change.
• Visible error message or other safely observed equipment condition.
• The person who can authorize assessment and additional work.

Mark missing facts unknown. A screenshot of one screen may not include every program, start time or automated feature. Ask the provider which records it needs instead of attempting to reproduce the whole system from memory.

Ask for settings and equipment review

Request an assessment that distinguishes the controller configuration, any app or automated feature and physical system conditions. A programming review and a repair are different scopes. If the business proposes replacement, ask what finding supports it and which alternative has been considered.

Keep the written result clear: what was observed, what was confirmed, what was changed and what remains uncertain. Do not treat a changed setting as proof that every equipment component has been checked. Conversely, a repaired component does not establish that the final program matches the owner's intent or current rule.

This guide does not provide wiring, valve, pump or controller-disassembly instructions. Do not open equipment or bypass a device to test a guess. Follow the actual manual and qualified provider's direction for any operational response.

Confirm the applicable watering requirements

SFWMD's current landscape-irrigation information is the starting point for checking the address and water source. A default controller program or a company's usual schedule does not establish compliance for every property. Ask the provider to identify the rule and source it used.

Record the accepted program and its date. If automated adjustments are part of the system, ask how they work on the actual product and what the owner should monitor. Do not apply a feature description from another model as a guarantee of your installation's behavior.

Close the issue with an operating record

Ask the provider to demonstrate the agreed functions, supply the final configuration and identify how the next unusual event should be reported. Keep the previous version for context. Share the accepted change with the people responsible for landscape care so another person does not unknowingly restore the old setting.

If watering recurs unexpectedly, preserve the new date and sequence and return to the findings from the earlier visit. Ask what additional assessment is needed rather than assuming the same change should be repeated. Keep an unconfirmed cause visible.

Separate programmed intent from observed operation

Write the date, observed start and stop if known, affected area and how you noticed it. Distinguish water actively spraying from residual surface wetness. A wet lawn at an unexpected time does not by itself prove when a system ran or which program initiated it.

Record who last changed the controller, whether an app or external service is connected and whether a recent authorized visit involved programming. Do not reset the controller to clear the history before the provider has reviewed the relevant information. The goal is to preserve a useful event record, not to instruct the owner to alter settings.

Ask for a configuration and operation review

Question	Useful reported answer
Which controller and connected services were reviewed?	Actual model and accepted review scope
What scheduled or manual activity was identified?	Provider's findings, not a guessed explanation
What remains uncertain?	Missing history, intermittent behavior or other limits
What change is proposed?	Authorized configuration or repair tied to the finding
Who can change it afterward?	One documented authority and support route

Multiple start times may repeat sequences on some products, but that possibility is not a universal diagnosis or a button sequence for an unknown controller. Ask the provider to apply the actual manual to the installed product.

Check restrictions separately from the fault

SFWMD's resources help determine the current restriction framework and relevant local rules for the address. A permitted day does not establish that an unexplained run was intended, and a suspected schedule fault does not exempt a property from applicable restrictions. SFWMD watering resources.

After service, retain the provider's reported configuration, scope of verification and instructions for reporting recurrence. If several people have access, reconcile permissions so a later event is not interpreted against an obsolete schedule. This is an unexpected-operation problem record, distinct from the WRLW seasonal-programming topic.

Does unexpected watering always mean the controller failed?

No. The actual configuration and system need assessment. A product-specific explanation of repeated start times is one possibility, not a universal diagnosis.

Should I replace the controller before the visit?

Obtain the finding and a defined proposal first. Replacement does not automatically address every physical or scheduling problem associated with the system.

What should a remote owner keep?

The event record, final program, responsible contact, product manual and approved changes. Store them privately in My Home or the owner's chosen record system.