HOA Irrigation Compliance Audit: Who Qualifies and What Documentation You Actually Need
Few commercial landscaping companies in South Florida can satisfy a municipal or HOA water-restriction compliance audit. Most treat irrigation as a side service. They install the heads, set the controller, and move on. When a water management district inspector shows up or a board member demands proof of schedule compliance, the answer is usually a phone call and a promise, not a document.
Green Image operates differently. Every property we serve in Palm Beach, Broward, and Miami-Dade counties runs on a documented irrigation program that tracks zone-by-zone water consumption, flags inefficiencies, and produces written records you can hand to an auditor the same day they ask. If your board needs proof of compliance, not a promise of it, that documentation already exists in your account file.
This listicle breaks down exactly what qualifies a landscaping company to manage irrigation at the compliance level your HOA requires, what documentation you should expect to see, and what to do if you are switching vendors and need to protect your records in the transition.
1. Every Irrigation Zone Is Mapped, Scheduled, and Individually Documented
A compliance audit does not ask whether your irrigation runs. It asks which zones run, on which days, for how long, and whether that schedule conforms to your county’s watering restrictions. If your vendor cannot produce a zone-level schedule map, you are not audit-ready regardless of how green the turf looks.
At minimum, your irrigation documentation should include a current as-built zone map showing head types, coverage areas, and controller station assignments. Each zone should have a named schedule tied to the applicable watering-day restriction for your jurisdiction. In Miami-Dade, Broward, and Palm Beach counties, those restrictions vary by address and are enforced by the South Florida Water Management District. A schedule that works at one property address may be non-compliant two miles away.
A vendor that qualifies for compliance management can show you that map on request. If they cannot, the system may be physically functional but it is not managed. That distinction matters the moment an inspector knocks.
2. Controller Run Times Are Calibrated Seasonally, Not Set Once and Left
South Florida’s rainfall distribution is not uniform across the calendar. The wet season runs roughly June through September. The dry season runs October through May. A controller set to a single annual runtime is almost certainly overwatering during the wet season, which wastes water and can trigger a violation, and may be underwatering during dry-season stress periods.
A qualified irrigation management program recalibrates run times at least twice per year, with a documented schedule change at each transition. That change should be logged with a date, the technician who made it, and the reason. “Seasonal adjustment, wet-to-dry transition, October 1” is a compliance record. “We turn it down in the summer” is not.
The South Florida Water Management District’s landscape irrigation guidelines explicitly address seasonal adjustment as a component of responsible water use. If your vendor cannot show you a seasonal calibration log, their process is informal, and informal does not survive an audit.
3. Water Consumption Is Tracked at the Zone Level, Not Just at the Meter
Your utility meter tells you total water use for the property. That number matters for billing, but it does not tell you which zone is leaking, which head is misting instead of rotating, or which section of turf is consuming twice its expected allocation.
Zone-level consumption tracking requires either a flow meter installed at each zone valve or consistent runtime-plus-precipitation-rate documentation that lets you calculate estimated zone output. Either method works. What does not work is relying on the monthly utility bill as your only data point.
When zone-level data exists, it produces real value beyond audit compliance. It lets you identify zones that are overwatering before a water bill spikes or a violation is cited. It lets you demonstrate responsible stewardship to residents who raise water-use concerns at board meetings. It supports a rate or budget defense when a vendor proposes an irrigation infrastructure upgrade, because you can compare current consumption to post-upgrade projections with actual baseline data. It also lets you compare consumption quarter over quarter to verify that seasonal adjustments are actually reducing usage, not just on paper.
4. Every Schedule Change Is Logged With Date, Reason, and Technician
This item is unglamorous. It is also the one most vendors skip entirely.
A change log is the difference between “we adjusted the schedule” and “Technician M. Reyes adjusted Zone 7 runtime from 12 minutes to 8 minutes on March 14 due to observed wet-season saturation and SFWMD Day 2 restriction compliance.” The second version is a compliance document. The first version is a verbal assurance.
Your board should require that any landscaping contract governing irrigation include a contractual obligation to maintain a written change log. Not a courtesy. A deliverable. If the vendor pushes back on that requirement, that is useful information. Vendors who maintain good logs do not object to showing them.
5. Rain Sensor and Soil Moisture Sensor Records Are Part of the Documentation Package
Florida Statute 373.62 requires automatic irrigation systems permitted after May 1991 to be equipped with a functioning rain sensor or equivalent device. That is not a recommendation. It is state law. For HOA properties, this requirement applies to common area irrigation systems across the board.
A compliance audit can and does ask for evidence that the rain sensor is installed, functional, and connected to the controller in a way that actually interrupts the irrigation cycle during and after rainfall events. A sensor that is wired but overridden is not compliant.
Your vendor should maintain an asset record for every sensor on the property, including installation date, last tested date, and current status. If a sensor fails, the corrective action, including the date it was replaced or repaired, should appear in the service log. If your vendor cannot show you that record, you do not know whether your property is in compliance with state law, regardless of what your controller schedule says.
6. Variance and Exception Permits Are Tracked and Filed in the Property Record
Some HOA properties operate under temporary variances from standard watering restrictions. New landscape installations, sod establishment periods, and drought-tolerant conversion projects can qualify for exception permits from the South Florida Water Management District or local municipality. Those permits have expiration dates and specific conditions.
A landscaping vendor managing irrigation at the compliance level must know which of your zones are operating under a permit, what the permit conditions require, and when it expires. That information should be in your property file, not in the technician’s memory.
When an auditor asks why Zone 12 ran on a non-scheduled day, “we had a permit for that” is only a valid answer if the permit is in hand and its conditions match what the zone actually did. If your vendor cannot produce it, the variance becomes a violation.
7. A Corrective Action Log Exists If Any Prior Violations Were Cited
A prior violation is not automatically disqualifying in an audit. Auditors understand that irrigation systems age, sensors fail, and storms create unusual conditions. What disqualifies a property is a prior violation with no documented corrective action.
If your property received a warning or notice of violation from a water management authority, your compliance record should show: the date of the notice, the specific violation cited, the corrective action taken, the date the correction was completed, and the technician or supervisor who performed it. That record closes the loop for an auditor. Without it, a prior violation looks like an ongoing condition.
This is also the document your board needs when a resident escalates a water-use complaint into a legal or regulatory inquiry. The corrective action log is your paper shield.
8. Compliance Documentation Can Be Exported and Delivered Within 48 Hours of Request
Audit readiness is not just about having records. It is about being able to produce them on the timeline an auditor or regulator imposes. In most HOA contexts, a compliance audit arrives with limited advance notice. A vendor who needs two weeks to compile your irrigation records is not audit-ready.
A qualified irrigation management program produces documentation that can be exported and presented to a board, property manager, or municipal inspector on request. That means the records are organized, current, and accessible in a format that is readable outside your vendor’s internal system.
Before your next contract renewal, ask your vendor this question: “If we receive an audit notice tomorrow morning, what can you put in front of the inspector by end of business?” Their answer tells you everything.
What to Do If You Are Switching Irrigation Vendors
Vendor transitions are one of the riskiest moments for irrigation compliance documentation. Records that exist inside a vendor’s proprietary system can be difficult or impossible to recover after the contract ends. Here is what to do before you issue a termination notice.
Request your current controller access credentials before the termination notice goes out. Controllers are your property. The programming inside them, including schedules, runtime settings, and zone configurations, is your data. Some vendors configure controllers with proprietary access codes they do not share voluntarily. Get those credentials in writing before the relationship ends.
Ask your incoming vendor to conduct a formal irrigation audit within the first 30 days, not just a walkthrough. That audit establishes a baseline. It becomes the starting point for all future compliance documentation. A walkthrough tells you what the system looks like. An audit tells you how it is performing against applicable restrictions.
Confirm that rain sensors and soil sensors appear on your asset inventory, not as vendor-supplied equipment. Some vendors list sensors as part of their service package rather than permanent property assets. If sensors leave with the contract, you have a compliance gap and a state law violation on day one of the new contract.
Set a documentation delivery cadence in the new contract as a contractual deliverable. Monthly summary reports, quarterly zone-level consumption logs, and a pre-audit package available within 48 hours of request should be written obligations, not verbal commitments. If a vendor resists putting documentation standards in the contract, that is the answer you need before you sign.
FAQ
Can you produce water-use records if we are notified of a compliance audit on short notice?
Yes. Every active property we manage has a current irrigation file that includes zone maps, controller schedules, seasonal change logs, sensor status records, and consumption summaries. That package can be compiled and delivered within 48 hours of a request in standard cases. For properties with prior violation records or active variance permits, we maintain a separate compliance sub-file that is updated at each service visit.
What if our current irrigation system does not have a functioning rain sensor?
A non-functioning rain sensor is both a state law compliance issue under Florida Statute 373.62 and a practical risk factor. We treat sensor installation or repair as a priority item in the first 30 days of any new contract. Until the sensor is functioning, we document the gap, flag it in the property record, and note it in any compliance file as a known corrective action in progress. We do not leave it undocumented.
Do you manage irrigation separately from grounds maintenance, or is it the same crew?
Irrigation management at the compliance level requires dedicated irrigation technicians, not grounds maintenance crew members who also turn controllers on and off. Our irrigation team operates on a separate service track. They hold the controller credentials, perform the seasonal calibrations, maintain the change logs, and interface with auditors and inspectors. Grounds crews report irrigation observations during maintenance visits, but documentation and schedule management are handled by the irrigation team.
We have multiple sub-associations. Can you maintain separate records for each?
Yes. For HOA portfolios with multiple sub-associations or distinct common-area zones under separate governance, we maintain separate irrigation files for each entity. That means separate zone maps, separate schedule logs, and separate compliance documentation. If a sub-association faces an audit independently of the master association, its records are complete as a standalone file.
What counties and municipalities do you serve?
We serve commercial HOA and multifamily properties in Palm Beach, Broward, and Miami-Dade counties. Within those counties, our irrigation programs are calibrated to the South Florida Water Management District restrictions that apply to each specific property address. Watering-day assignments vary by address in some municipalities, and our documentation reflects the applicable restriction for each property, not a county-wide default.
