How to Document Irrigation Work Orders for Property Management

Document irrigation work orders by capturing zone location, system components, issue description, and completion photos for every service request. Based on 100K+ completed jobs across our 12 markets, documentation averages 12-18 minutes per property when you follow a standard template.

This process applies to single-family properties. Multi-family and commercial properties have different documentation requirements and system complexities.

Why Irrigation Work Order Documentation Matters for Property Managers #

Poor documentation costs property managers time and money. Every missing photo, vague description, or skipped zone number creates problems down the line—lost disputes, missed warranty claims, and repeated repairs because nobody recorded what happened the first time.

Documentation delivers three core benefits:

• Accountability and Proof of Completion. Without completion photos and detailed records, you’re taking someone’s word for it. Every documented irrigation work order creates an audit trail showing who did what, when they did it, and what the system looked like before and after the work. At Breasy, we require same-day completion photos before releasing any invoice.

• Cost Control and Budget Tracking. When you document every irrigation work order, you build a maintenance history for each property. You can see patterns—maybe Zone 3 at 1847 Oak Street needs a head replacement every spring, signaling a root intrusion problem that needs a different solution. Documented work orders let you track spending by property, by zone, and by component type.

• Liability Protection and Compliance. Irrigation systems touch water supply lines. Most municipalities require annual backflow preventer testing with specific certification requirements. Phoenix, Las Vegas, and most Texas metros mandate annual testing and the retention of documentation. Your compliance documentation protects you during audits, when properties sell, and when something goes wrong.

What to Include in Every Irrigation Work Order #

A complete irrigation work order captures property information, system details, the actual problem, and timeline requirements. Skip any of these, and you create gaps that cause problems later.

Property and Zone Information #

Start with the basics. Property address. Unit number, if applicable. Gate codes or access instructions.

Then add irrigation-specific details:

Field	Example	Why It Matters
Zone count	6 zones	Confirms system scope
Controller location	Garage, east wall	Tech knows where to start
Water source	Municipal, meter at curb	Affects shutdown procedures
Last service date	March 2025	Shows maintenance history

Zone numbers matter more than property managers realize. “Sprinkler broken in front yard” tells a tech nothing. “Zone 2, second head from the driveway” tells them where to go.

System Components and Equipment Details #

Document what equipment exists at the property. Controller brand and model. Head types. Valve locations.

This isn’t busywork. When a tech shows up with the wrong replacement parts, the job takes twice as long. When you document that a property uses Hunter PGP rotors, the tech arrives with them.

Build a component inventory for each property:

• Controller: Brand, model, number of stations
• Heads: Type (spray, rotor, drip), brand if known
• Valves: Quantity, location markers
• Backflow preventer: Type, test date, tag number

Across our markets, we see regional equipment preferences that affect parts planning. Our Texas properties tend toward Hunter controllers, while Phoenix properties show more Rainbird installations. Knowing what’s installed before dispatch saves return trips.

Issue Description and Service Type #

Vague issue descriptions kill efficiency—consider that “irrigation not working” could mean anything. The controller won’t power on. Zone 4 has no pressure. There’s a geyser in the backyard.

Good issue descriptions include:

• What’s happening (or not happening)
• Where it’s happening (zone number, location)
• When it started
• What changed before the problem started

Service request types should be specific: repair, inspection, adjustment, winterization, spring startup, component replacement.

Timeline Requirements and Priority Level #

Not every irrigation issue is urgent. A stuck spray head is routine. A mainline break flooding a foundation is an emergency.

Set clear priority levels:

Priority	Response Time	Example Issues
Emergency	Same day	Mainline break, flooding
Urgent	24-48 hours	Zone not functioning, leak
Standard	5 business days	Head replacement, adjustment
Scheduled	Pre-set date	Seasonal startup, winterization

Document the timeline requirement on every work order. Then document when the work was completed.

Step-by-Step Irrigation Work Order Documentation Process #

This process works whether you use property management software, a mobile work orders app, or a spreadsheet. The steps don’t change. The documentation requirements don’t change.

Step 1: Initial Request and Quote Documentation #

Start documentation when the request comes in. Not when the tech arrives. Not when the job is done. When the request comes in.

Record:

• Date and time of request
• Source (tenant, owner, inspection, preventive maintenance schedule)
• Initial issue description
• Photos or videos from the requester, if available

If the owner requires a quote, document the quote date, amount, and what’s included. When the quote gets approved, document who approved it and when.

Breasy delivers market-rate quotes within 48 hours. Every quote includes itemized components so property managers know what they’re approving.

Step 2: Pre-Work Inspection and Photo Capture #

Before any work starts, document the current state. This is required.

Pre-work documentation includes:

• Photos of the affected zone or component
• Controller display showing current settings
• Any visible damage or issues
• Meter reading if relevant

These photos protect everyone. They show what the tech found when they arrived. They prove pre-existing conditions. They create a baseline for the work.

Step 3: Work Completion and Zone Testing #

Document what work was performed. Not what was quoted. What was done.

For each zone affected:

• Run the zone manually
• Check for proper coverage
• Verify no leaks
• Document pressure if relevant

Record any deviations from the original scope. If the tech found additional issues, document them separately. If parts differed from the quote, note the change and reason.

Step 4: Final Documentation and Completion Photos #

Completion photos close the loop on job completion documentation.

Required final photos:

• Repaired components in operation
• Controller settings after adjustment
• Any replaced parts (old components)
• Wide shot showing zone coverage

We include same-day completion photos with every Breasy job. You see the photos before you see the invoice.

Photo Documentation Standards for Irrigation Work #

Most guides say “take photos.” That’s not enough. The wrong photos are almost as useless as no photos.

Required Before Photos #

Before photos serve one purpose: proving the starting condition.

Capture these shots before any work begins:

• Wide shot: Shows the zone location in context of the property
• Problem shot: Shows the specific issue (broken head, leak, dry spot)
• Controller shot: Shows current programming
• Access shot: Shows the point where work will happen

Date and time stamps matter. Most mobile work order apps add them automatically. If yours doesn’t, enable the setting.

Required After Photos #

After photos prove the work is done and done right.

• Same angle as before: Shows the repair in the same framing
• Operation shot: Shows the system running
• Component close-up: Shows the installed part clearly
• Coverage shot: Shows water pattern if heads were replaced

Match the before and after angles. This seems minor but makes a huge difference when reviewing repair documentation months later.

Component Close-Ups and Zone Markers #

Close-up shots document specific components for future reference.

Photograph:

• Model numbers on replaced heads
• Valve locations with reference points
• Controller wiring (especially if changed)
• Backflow device tags

Create zone markers if they don’t exist. A simple flag or paint mark at each valve box makes future service faster. Document these markers in your photos.

Zone Mapping and System Documentation #

Asset tracking for irrigation means knowing what exists at each property. Zone mapping is how you get there.

Creating Zone Maps for Each Property #

A zone map shows which areas each zone covers. Most property managers don’t have these. They should.

Create a basic zone map:

• Sketch or photograph the property layout
• Label each irrigation zone by number
• Mark valve box locations
• Note head types in each zone
• Mark the controller location

Store zone maps with your property records. Update them when systems change.

After 100K+ jobs across our 12 markets, we’ve learned that properties with zone maps get serviced faster and more accurately. Techs know where to go. GPS Renting experienced this firsthand: reliable, professional service that allowed them to focus on tenant satisfaction rather than chasing down irrigation details.

Documenting Controller Settings and Schedules #

Controller settings change. Tenants adjust them. Previous landscapers changed them. Seasons require different schedules.

Document the baseline settings:

Setting	Spring	Summer	Fall	Winter
Zone 1 runtime	10 min	15 min	8 min	Off
Zone 2 runtime	12 min	18 min	10 min	Off
Start time	5:00 AM	4:00 AM	6:00 AM	N/A
Days	M-W-F	Daily	Tu-Th-Sa	N/A

Record these settings during seasonal work. When something seems wrong, you have a reference point.

Tracking Component Locations and Specifications #

Build an inventory of what’s installed at each property.

Track:

• Head brands, models, and nozzle sizes
• Valve brands and sizes
• Pipe types and sizes (if known)
• Controller brand, model, and age

This inventory makes ordering parts faster. It prevents mismatched components. It supports your preventive maintenance schedule by telling you what needs attention and when.

Seasonal Irrigation Work Order Templates #

Different seasons require different documentation. Use templates that capture what matters for each service type.

Spring Startup Work Order Template #

Spring startup brings systems back online after winter. Documentation confirms everything works and catches freeze damage that stayed hidden until water pressure returns.

Spring Startup Documentation Checklist:

• [ ] Controller powers on
• [ ] Programming set for spring schedule
• [ ] Battery backup replaced if needed
• [ ] Each zone runs manually
• [ ] Heads pop up fully; no stuck heads
• [ ] No leaks at heads or valves
• [ ] Backflow preventer opens correctly
• [ ] Pressure within normal range
• [ ] Coverage adequate for each zone
• [ ] Completion photos for all zones

In Denver and Colorado Springs, we see spring startups spike in April. Frozen components from winter often don’t show problems until water pressure hits them.

Mid-Season Inspection Template #

Mid-season inspections catch problems before they get expensive. Finding a cracked head in July costs less than finding dead grass in August.

Mid-Season Documentation Checklist:

• [ ] Visual inspection of all zones
• [ ] Head alignment check
• [ ] Coverage test (run each zone)
• [ ] Controller schedule verification
• [ ] Leak check at visible fittings
• [ ] Backflow device visual inspection
• [ ] Filter cleaning if applicable
• [ ] Battery backup test
• [ ] Adjustment notes
• [ ] Photos of any issues found

Schedule these inspections in your preventive maintenance schedule.

Winterization Work Order Template #

Winterization protects systems from freeze damage. In cold-weather markets, this documentation is your protection against spring damage claims.

Winterization Documentation Checklist:

• [ ] Controller set to rain or off mode
• [ ] Main water supply shut off
• [ ] System drained or blown out
• [ ] PSI used for blowout
• [ ] Each zone cleared
• [ ] Backflow preventer drained
• [ ] Test cocks left open
• [ ] Controller unplugged if required
• [ ] Photo of controller showing off state
• [ ] Photo of main shutoff

Documentation proves the technician completed winterization correctly. “We winterized it” means nothing without the records.

Common Irrigation Documentation Mistakes to Avoid #

These three mistakes cause the most problems:

• Incomplete zone information: “Front yard zone” isn’t documentation. Always use zone numbers. If a property doesn’t have them assigned, create them.
• Missing completion photos: A work order without completion photos is a claim, not proof. Tenant communication and owner questions get resolved with pictures, not explanations.
• Vague issue descriptions: Push back on “irrigation broken.” Get the zone number, symptoms, and timeline. Turn “sprinklers broken” into “Zone 3, third rotor from fence, not rotating, only spraying straight.”

Frequently Asked Questions #

As Bahia Property Management noted in its experience working with us, fast response and excellent customer service come with complete documentation at a fair cost. Our 90% quote approval rate reflects property managers’ trust in documented cost breakdowns.