Two document types carried the value: quotes with zone-level scope, and seasonal service notices. A third — watering guidance — worked only after we removed every universal claim, and a fourth, backflow and cross-connection paperwork, we kept purely administrative.
What makes irrigation documents awkward is that the correct answer almost always depends on the site — soil, slope, sun exposure, plant types, water pressure, local restrictions. A draft that sounds authoritative without that information is worse than one that asks for it.
Where it helped
Quotes with zone-level scope
Zone count, head types, controller, whether the repair includes locating and marking, whether winterisation or startup is bundled, and what is excluded. The structure transfers between jobs; the specifics come from the site visit. Drafting fell from about 20 minutes to 6.
The exclusions line did most of the work — stating that main line breaks, controller wiring faults and drainage issues are quoted separately removed the most common category of dispute.
Seasonal service notices
Spring startup and autumn winterisation reminders, with what the visit includes and roughly how long it takes. Generated versions were fine, and having them written before the season starts matters more than the drafting time. Include the consequence plainly: systems that are not drained can crack, and that repair is not a small one.
Booking confirmations with access notes
Arrival window, whether someone needs to be home, where the controller and water shut-off are, and whether pets will be in the yard. Standard structure, real time saved — roughly 4 minutes instead of 12.
Where it failed
Watering schedules
Drafts produced specific run times and frequencies. Correct watering depends on soil type, slope, sun, plant type, nozzle output and local restrictions — all site-specific, and in many areas subject to rules that change through the year. The safe version explains what to observe — dry patches, runoff, wilt — and refers scheduling to the technician.
Backflow and cross-connection statements
Generated text asserted that a device was compliant or that testing was complete. Whether a backflow assembly has been tested, and by whom, is a matter of record, and in many jurisdictions testing must be done by a certified tester with results filed. Keep it as a status field with a date and a certificate reference.
Coverage and pressure claims
Drafts stated that a zone would cover a given area or that pressure was adequate. Coverage and pressure are measured, and they change with the municipal supply. Observation only.
Contractor licensing and permit statements
Generated text referred to licensing requirements as though known. These vary by state and by council, and getting them wrong in writing is a problem. Name the authority to check with, or omit the claim.
What customers actually check
Someone with an irrigation problem wants to know: is it a leak, a controller, or a coverage issue — and how soon can you come. Describing the diagnostic sequence rather than guessing the cause was the single change that reduced return visits in our testing.
Worth adding to every quote: whether the price includes locating the valves and marking the heads, since an unmapped system is where most of the time goes.
The backflow paperwork most customers forget
Backflow testing carries more administrative weight than any other part of irrigation work, and customers are usually unaware of it. Treat it as a status field, not prose: date last tested, certificate reference, and when it is next due. Send the reminder before the due date rather than after. Whether testing is required, how often, and who may perform it vary by jurisdiction — name the authority to confirm with rather than stating a rule.
Seasonal timing that reduces the rush
Irrigation demand arrives in a spike, and most operational pain comes from the spike rather than the total volume. Book winterisation slots while the weather is still good, and confirm spring startup dates before the first warm week rather than after it. In our testing, customers responded well to being asked to commit early, provided the reminder named a concrete window rather than "sometime in spring".
Editing time, from our 30-day benchmark
Quotes went from roughly 20 minutes to 6, near $7 saved at $30 per hour. Seasonal notices from about 12 minutes to 3. Booking confirmations from 12 to 4. Backflow and licence content was kept administrative or omitted.
A workflow that holds up
Template the quote with mandatory fields for zone count, controller and whether the repair covers valve location. Write seasonal notices before the season, not during it. Send the booking confirmation with the access fields. Watering schedules, coverage claims, backflow status and licence or permit statements come from the site visit and your own records — observed on site, filed with the authority, and written by whoever is accountable.
Quote the zones, measure the coverage
Quotes and seasonal notices scale. Head coverage and pressure have to be checked on site.
Try Rytr →Frequently Asked Questions
Can AI write our irrigation quotes?
The structure, yes — with zone count, controller and valve-location scope filled in from the site visit.
Should it give watering schedules?
Not specific ones. Explain what to observe and refer scheduling to the technician, since local restrictions also apply.
Can it confirm backflow compliance?
No. Treat it as a record: tester, date, certificate reference.
What about coverage or pressure claims?
Measure them. Do not state them from a description.
Should it mention licensing or permits?
Name the authority to check with, or leave it out. Requirements vary by location.
Is this worth it for a two-person crew?
The seasonal notices pay back first — they fill the calendar outside peak season.