How to Coordinate Irrigation Repairs Across a Multi-Property Portfolio

Property managers handling irrigation repairs across 10 or more properties face a coordination problem, not a technical one. The repairs are straightforward. The challenge is routing the right information to the right vendor quickly enough to prevent a one-day repair window from becoming a week of turf damage in summer.

A per-property irrigation record, a structured repair request format, and a vendor with a re-dispatch guarantee reduce coordination overhead more than any other tools available.

The Coordination Problem at Scale #

A property manager with 5 properties can manually coordinate irrigation. A phone call per failure, a text confirmation per repair, a follow-up call per invoice. It is inefficient but manageable.

At 20 properties, the same approach breaks down. Five or six repair requests in the same week during a post-monsoon service surge cannot be tracked in a text thread. Different vendors with different response windows create inconsistent repair timelines. Without written documentation of what was repaired and when, disputes about repeat failures and warranty callbacks become unresolvable.

The transition from manageable to broken typically happens somewhere between 10 and 15 properties. The solution is not more manual tracking — it is a system that ensures every repair request is handled consistently, regardless of scale.

Building a Per-Property Irrigation Record #

The per-property irrigation record is the foundation of efficient repair coordination. It converts every repair request from a discovery conversation (“what controller does this property have?”) into a targeted dispatch (“zone 3 of the Hunter Pro-C at 4521 W Orangewood needs a solenoid replacement”).

What goes in the record for each property:

The record does not need to be elaborate. A shared spreadsheet or a property management system with custom fields works. The critical discipline is to update it after every service visit and make it available to whoever dispatches repair requests.

How to Structure Repair Requests for Speed and Accuracy #

A phone call with a problem description often leads to a lengthy back-and-forth before a technician can be assigned. A structured repair request with consistent fields can be dispatched in under 5 minutes.

Minimum fields for a repair request:

• Property address (with access notes from the property record)
• Zone affected (zone number from the controller)
• Symptom (what was observed and when it was first noticed)
• Photo (one photo of the affected area, head, or wet patch)
• Urgency category (active water waste/zone-down/reduced coverage)

A repair request with these five fields reaches a technician with enough information to arrive with the likely replacement parts, reduces on-site diagnostic time, and eliminates the “I need to go back for parts” second visit that doubles the service call cost.

Train whoever handles tenant reports to collect the symptom and a photo before routing it to dispatch. Most tenants can photograph a geysering head or a wet patch. That photo, combined with the property record, gives the technician more information than a verbal description ever would.

Batch Repairs vs. Per-Property Dispatch: When Each Makes Sense #

• Batch pre-season inspections (May): Schedule all properties for pre-summer irrigation inspections during a defined 3-4-week window in May. A single May inspection per property surfaces all deferred repairs in a single pass, enables batch quoting, and confirms system readiness before peak demand. This is the highest-ROI coordination decision in the irrigation calendar.

• Per-property reactive dispatch: Category Failures (active water waste, full zone down) are dispatched individually as they occur. The property record provides the technician with context. The structured repair request provides the symptom and a photo. These cannot be batched—urgency drives individual dispatch.

• Batch post-monsoon checks (July-August): After significant monsoon events that affect multiple properties in the same market, a batch post-storm check across all affected addresses is more efficient than waiting for individual tenant reports. Our team can run post-storm checks across a portfolio with same-day photos delivered for each property in a single report.

Using Completion Photos as Your Remote Audit System #

For property managers who are not on-site at every property, same-day completion photos from every service visit are the only remote visibility into system condition. What photos surface that verbal reports do not:

Whether the repair was actually completed (not just reported as complete). Adjacent problems visible during the repair visit that were not in the original work order. System condition changes since the previous visit (new wet patch, new dry strip, head that has shifted). Controller screen showing the current program settings.

A vendor who does not provide same-day completion photos creates a documentation gap that becomes visible only when a repair is disputed, a repeat failure occurs, or an owner requests a maintenance audit. Build completion photo requirements into every vendor agreement at onboarding, not after the first documentation dispute.

We provide irrigation repairs across all active markets, delivering same-day completion photos as a standard deliverable on every visit. Property managers coordinating across multiple addresses use our single-point scheduling to confirm all repairs, inspections, and post-storm checks without having to manage individual vendor relationships.

For a recurring maintenance structure, our guide on recurring landscaping schedules covers how to build irrigation checks into an annual maintenance cadence.

Frequently Asked Questions #