From findings to finished: following up on irrigation inspection repairs

Every irrigation inspection ends the same way: with a list. A couple of things were fixed on the spot, a few need more time or parts, and one or two need the customer's approval before anyone touches them. The technician hands in the sheet, heads to the next property, and from that moment the list starts competing with everything else your office has to do.

Some of those items get done the following week. Others drift. A leaking lateral line noted in June can still be leaking in August, not because anyone decided to ignore it, but because it was a line in a report rather than a job somebody owned. If you've ever had a property manager point out a problem your own inspection found months earlier, you know how much that costs in credibility.

Following up well isn't complicated. It mostly comes down to a few habits, applied consistently, that move each finding from “noted” to “finished.”

Give every finding a life of its own

The single most useful change most irrigation contractors can make is to stop treating inspection findings as part of the inspection. Once the technician leaves the property, anything that wasn't fixed should become its own piece of follow-up work, separate from the report it came from.

The reason is simple. A separate job can be assigned to someone, scheduled, sent for approval, and marked done. A line on a PDF can't. As long as a finding lives only on the inspection, the only way to know whether it was handled is to remember, and memory doesn't scale across dozens of properties and several technicians.

When the finding becomes its own job, it should carry everything the next person needs: the property, the controller and zone, a plain description of the area, exactly what was found, what was already tried, the photos from the inspection, and any parts that are likely to be needed. It also helps to keep a link back to the inspection, so anyone can see the context.

Sort findings by what they need next

Not every finding needs the same treatment, and the fastest way to get the urgent ones done is to stop them from waiting in the same line as the routine ones. A quick review right after the inspection, usually by whoever coordinates the work, is enough.

Some findings are urgent. A zone that won't shut off, a main line leak, or water flooding a building's foundation can't wait for the next scheduled visit. Those should be flagged and handled within days, and sometimes the right first step is simply shutting off the water. Others need a decision from the customer: replacing a valve, adding heads to fix coverage, anything outside the contract. Those go out for approval. The rest are routine fixes, like raising sunken heads in one zone, that can be folded into the next visit to the property. And any zone that couldn't be inspected at all, because of a locked gate or an inaccessible controller, needs a plan to get access.

Making that call once, deliberately, is what keeps a dangerous leak from sitting behind a cosmetic adjustment.

Get approvals without the back-and-forth

Approvals are where follow-up work most often stalls. The request goes out vaguely worded, the property manager has questions, the questions sit in an inbox, and meanwhile nothing happens. The fix is to make each approval request answerable in one read.

That means saying what's wrong and where in a sentence or two, attaching a photo that shows the problem, stating what you recommend doing, and explaining what happens if it waits: a dry area that will keep browning, or water running at the valve box around the clock. Include any price your contract requires and make it obvious how to reply. A manager who can see the problem and understand the stakes can usually say yes on the spot.

Once the request is out, keep the job clearly marked as waiting on approval. That distinction matters more than it seems. It tells everyone in your office that the work isn't stuck on your side, and it makes it easy to see which customers need a polite nudge after a few days.

Set up the return visit to succeed

Return visits go wrong when the technician arrives without the background. They don't know what was found, they don't have the right part, and they end up rediagnosing a problem someone already diagnosed. Before the visit, make sure the job has the original finding, the photos, and any notes from the customer or manager. If a specific part is likely to be needed, such as a particular valve or pipe size, note it, so it's on the truck.

After the repair, the technician should record what they did, the parts they used, and an after photo, then move the job forward so the office can close it out. That record becomes part of the property's history, which turns out to be one of the most valuable things a contractor accumulates.

Let the history tell you something

When the same zone shows up in follow-ups month after month, the history is trying to tell you something. A nozzle that clogs every month may point to a filtration or water-quality problem. Heads along a walkway that keep breaking may be set too high or sit in the path of a mower. A valve that keeps failing may simply be at the end of its life.

Being able to show a customer that pattern changes the conversation. Instead of another small repair, you can recommend a real fix and explain why. It's the difference between being the contractor who keeps patching things and the one who actually solves problems. We look at this more closely in How to reduce sprinkler repair return visits.

Report what was found and what was done

Property managers and HOA boards rarely see your technicians at work. What they see is the report, so it's worth making it good. A useful inspection report tells them when the inspection happened and who did it, gives a clear result for each zone, lists the repairs completed on site, and shows the status of anything still open: scheduled, waiting on their approval, or completed since. Photos of anything significant make it real.

A PDF works well for most managers. A spreadsheet-friendly export helps the ones who track work across many properties. Either way, a consistent, honest report is one of the strongest arguments you have at contract renewal time. On community properties, it also helps to let the resident who first reported a problem know when it's fixed. It reduces repeat reports and builds goodwill. See How landscape contractors can manage HOA resident requests for more on that.

A small weekly habit that holds it together

None of this works without someone looking at the open follow-ups regularly. Once a week is enough for most contractors. The questions are always the same: which urgent items aren't finished yet, which approvals have been waiting too long, which properties still have zones nobody could inspect, and which completed repairs haven't been reported to the customer. Twenty minutes with those questions catches almost everything before it becomes a phone call from an unhappy manager.

Where software fits

You can run this process on paper and spreadsheets, and plenty of good contractors do. It just gets harder as properties and technicians multiply. In Groundlark, every problem found on a wet check becomes its own irrigation ticket, with the location, the issue found, the work performed, parts used, and before-and-after photos. Work moves through New, In Progress, Awaiting Approval, and Closed, urgent items can be flagged, closed work can be reopened if a problem comes back, and wet-check reports export as PDF or CSV.

You can see how it fits an irrigation business on our irrigation contractor software page. Or book a walkthrough, bring a recent inspection, and we'll follow one of its findings through together.