Irrigation station map turnover record

Direct answer

An irrigation controller turnover record should prove that every controller station can be found in the field, matched to the right valve box tag, matched to the right zone or hydrozone, shown on the as-built map, tested from the controller, tied to the current program, and handed to the owner with rain sensor status and open exceptions clearly documented. The record should include controller ID, station number, program, runtime, start time, watering day basis, rain sensor or weather sensor status, valve box ID, valve tag, zone description, plant material, irrigation method, as-built photo, representative running-zone photo, issue photo, correction photo, retest result, owner training note, and release decision.

This is not the same as a broad irrigation audit. A catch-can audit, pressure review, water budget, distribution uniformity calculation, or seasonal schedule review may be part of the larger turnover package. This article focuses on the identity layer that makes the system maintainable: what station controls what area, where the valve is, whether the rain sensor is active, what the controller is programmed to do, and what photo evidence proves the installed field condition before the contractor leaves.

A useful record lets a maintenance person open the controller door, read station 8, find valve box VB-3, see a permanent zone tag, compare the as-built zone photo to the field area, run the station manually, confirm the rain sensor is not bypassed unless approved, and understand whether station 8 is accepted, held, or pending a correction. A weak record says irrigation complete and leaves the owner to rediscover the system one zone at a time.

Use this as documentation guidance only. The approved irrigation drawings, specifications, owner standards, local water rules, state landscape ordinances, product manuals, backflow requirements, electrical requirements, reclaimed-water requirements, inspection authority, designer, irrigation professional, landscape architect, maintenance contract, and owner acceptance process control the actual installation, testing, programming, compliance, and turnover.

Define the turnover boundary

Start by defining the exact controller and landscape area being turned over. A strong boundary says Controller LC-1, stations 1 through 18, serving the north entry turf, east parking lot islands, west shrub beds, tree bubbler zones, and temporary establishment drip zones, with valve boxes VB-1 through VB-9 and rain sensor RS-1. A weak boundary says site irrigation and creates confusion when the property has more than one controller, multiple phases, temporary valves, battery controllers, or future expansion wiring.

The boundary should also say what is outside the record. A controller station map record does not by itself approve backflow testing, mainline pressure, pump station operation, water meter accounting, reclaimed-water signage, trench compaction, landscape establishment, plant health, or a water budget. Those items may need their own records. This record should stay tight: controller station identity, field valve identity, sensor status, zone photos, current program, exceptions, and owner handoff.

For phased work, state the phase and the omitted stations. A controller may already have spare stations, future station modules, disabled stations, abandoned construction-phase valves, or stations serving areas not yet planted. The record should distinguish active, inactive, spare, future, temporary establishment, and excluded stations. If a controller skips station numbers because of module configuration or programming, record that plainly so the owner does not interpret the gap as a missing valve.

If the turnover boundary changes during the walk, update the record before release. A contractor may intend to turn over the whole controller and then discover that one island is not planted, one rain sensor is not paired, one station map is not laminated, or one valve box has no tag. The final release should say whether the whole controller is accepted or whether only named stations are accepted.

Start with source documents

Collect the approved documents before walking the site: irrigation plans, valve schedule, controller schedule, hydrozone map, planting plan, shop drawings, controller manual, rain sensor manual, owner standard, irrigation audit form, local checklist, punch list, product submittals, as-built markups, and maintenance contract. The goal is to compare the installed system to the accepted basis, not to create a new field design with photos.

The Riverside irrigation specification reviewed for this package is a useful owner-standard example because it requires service manuals before the substantial-completion walk, record drawings or as-builts, field as-built review before walk-through, final as-built verification, and controller charts for each controller. It even describes color-coded controller charts sized for the controller door. That is not a universal rule for every job, but it shows why controller charts and as-builts belong in the turnover evidence.

The University of Washington irrigation design standard reviewed for this package adds another owner example. It calls for as-built drawings maintained on site, labels tied to zone numbers and descriptions, automatic control valves by zone, permanent valve tags, color-coded laminated zone maps and tables, electronic operation and maintenance material, owner training documents, and progress photos linked to plan markups. Again, the project documents control the work, but the record logic is strong: the controller, labels, photos, and as-builts must agree.

Product manuals also matter. Rain Bird ESP-ME3 material reviewed for this package describes station numbering, program-based scheduling, weather sensor settings, rain sensor on/off behavior, manual station runs, station run times, seasonal adjust, flow sensor and rain sensor by station, and master valve by station. Rain Bird rain sensor material describes sensor location, wiring, automatic suspension, pairing or signal indicators, and test procedures. The turnover record should identify the installed model and preserve the settings that matter for owner operation.

Build the station map

The station map is the spine of the turnover record. It should list controller ID, station number, program, valve box ID, valve tag, zone name, plant type, irrigation method, exposure, slope or special condition if relevant, current runtime, start-time basis, sensor relationship, and photo references. If the owner standard requires a controller chart inside the door, the record should show the final chart installed or ready for installation.

Do not rely on the station number alone. Texas A&M AgriLife controller basics material reviewed for this package distinguishes controller stations from landscape zones and tells users to map zones and fill in a short description in the controller box for reference. The Irrigation Association worksheets reviewed for this package include controller data, stations being used, program settings, sensors installed, controller settings, smart controller settings, test area or station, and site conditions. Those sources support a station map that is more than a numbered list.

Good station descriptions are specific. Controller LC-1 station 4, east entry turf spray zone, VB-2, warm-season turf, full sun, spray heads, rain sensor active, Program A, establishment schedule through July 15 is useful. Station 4 lawn is weaker but may be acceptable for a small property if it matches the owner expectation. Station 4 unknown is a hold, not a label.

The station map should also show the stations that are not released. If station 14 is spare, say spare. If station 15 is future phase, say future phase. If station 16 serves temporary establishment irrigation, say temporary and include the removal or schedule-change condition. If station 17 is disabled because no module is installed, show that the controller display or program skips it. A clean map prevents future crews from spending time chasing phantom valves.

Make valve box tags readable

A valve box tag should let the owner connect the controller to the field without opening every box. Photograph the valve box lid, box location, valve assembly, permanent tag, wire splice tag if present, controller station number, common or spare wire labels where required, and the area served. The record should show that the tag is durable, legible, and placed where it can be found without blocking service.

The University of Washington standard reviewed for this package specifically calls for permanent alphanumeric valve tags to denote zone numbers in valve boxes and common or spare wire run descriptions at wire assembly box terminations, tied where visible without inhibiting serviceability. The California MWELO audit checklist reviewed for this package includes a check that valve boxes are properly set and identified. Those are strong source anchors for photographing valve box identity before turnover.

The valve box tag should match the controller station map. If the controller says station 6 is VB-4 west shrubs and the box tag says station 8, the record should stop and resolve the conflict. Do not hand the owner a map that requires a translation key no one approved. If the field wiring changed, update the map, controller chart, valve tag, and as-built photo as a single correction.

Take both context and close-up photos. A close-up tag photo proves the label, but not where it is. A wide photo proves the location, but not the tag. Pair them: one photo showing the valve box relative to walk, curb, wall, tree, bed edge, or building corner, and one photo showing the tag and inside condition. When boxes sit in mulch or dense plantings, add a measurement or landmark so the owner can find them after growth.

Prove rain sensor status

Rain sensor status belongs in the turnover record because a controller can run perfectly during a manual test and still ignore rainfall if the sensor is bypassed, missing, miswired, unpaired, poorly located, or never tested. Record the rain sensor model, location, controller interface if used, controller setting, active or bypass status, signal or battery indicator if applicable, test method, and final normal state.

EPA WaterSense audit material reviewed for this package includes a rain shutoff device criterion for technology that inhibits or interrupts irrigation during rainfall or sufficient moisture. The WaterSense controller checklist also expects weather-based or soil-moisture controller capabilities, including interfacing with a rainfall device. That supports documenting whether the rain sensor or related moisture technology is part of the accepted system.

Rain Bird ESP-ME3 material reviewed for this package shows why photos must be precise. It has controller settings that make the controller obey or ignore a weather sensor, and when the sensor setting is off, all stations ignore the rain sensor. It also allows rain sensor behavior by station in special features. Therefore, a photo that merely shows a rain sensor mounted outside is not enough. The controller setting and station relationship also matter.

The rain sensor itself needs a physical record. Rain Bird RSD material reviewed for this package says the sensor should be placed where it can collect natural precipitation without interference and should not be mounted where sprinklers, gutters, trees, or debris affect its ability to record rainfall. It also describes testing the system after installation. Rain Bird WR2 material adds pairing, signal, battery, and controller-interface indicators for wireless sensors. The turnover record should show the installed condition and the test result, not just the product box.

Use as-built zone photos

As-built zone photos make the station map real. Each active station should have at least one photo that shows the area served and enough site context to identify it later. For complex sites, include a plan markup with photo numbers. The best photos show the zone boundary, plant material, head or drip type when visible, valve box reference, nearby landmark, and whether the station is turf, shrub, tree, drip, rotor, spray, bubbler, or temporary establishment irrigation.

A photo of wet pavement is not an as-built zone photo. It must connect to a controller station and a field location. Caption the image with controller, station, valve box, zone name, and direction of view. For example: LC-1 S07, VB-3, north walk shrub drip, looking east from lobby door. If a station covers two separated areas, photograph both and say why one station serves more than one area.

As-built photos should capture accepted differences from the original drawing. If a valve moved from the plan, a spray zone became drip, a planter was deleted, a tree bubbler station was combined, a station was split, or a future sleeve became active, record the approved basis and the final photo. A photo without approval does not make a field change acceptable. It only proves the field condition existed at turnover.

Use the photos to protect maintenance handoff. The owner will inherit plant growth, mulch changes, seasonal adjustments, broken heads, and future construction work. A clear zone photo gives the owner a baseline: this is what station 5 was intended to water at acceptance, this is where the valve box was, this is the rain sensor status, and these were the open exceptions.

Run stations from the controller

The turnover walk should prove that the controller station number activates the expected field zone. Use the product-approved manual or test function, then record the controller screen, station number, field zone operating, and the valve box or tag if practical. If the controller supports manual single-station operation, use it under the approved procedure. If a central control system owns the station, include the central command or local override evidence required by the owner.

Rain Bird ESP-ME3 material reviewed for this package includes manual watering options such as test all stations and run a single station, plus station run-time programming and display of active station information during watering. That supports station-by-station functional evidence. It also warns that manual watering can start even when the weather sensor is set to sensor on, which means a manual run does not automatically prove the rain sensor will stop scheduled irrigation.

Record actual mismatches as exceptions. If station 3 runs the west bed when the map says north turf, the station map is wrong, the wiring is wrong, or the controller programming is wrong. Do not solve it by saying the owner can figure it out later. The turnover record should either correct the map and tags or hold the station until the field and controller agree.

Station runs should be long enough to identify the area and obvious defects, but the article does not set a universal runtime. The right runtime depends on the test purpose, product manual, plant material, site conditions, water restrictions, and owner procedure. The point of this record is identity and handoff, not a universal irrigation duration.

Capture controller programs

Photograph or export the controller program at turnover. The record should show current date and time, active programs, station runtimes, start times, watering days or interval, seasonal adjustment, rain delay or sensor status, smart-controller settings if applicable, master valve or pump-start relationship if applicable, and any station set to zero or disabled. If the owner changes the program later, this turnover record remains the baseline.

The Irrigation Association worksheets reviewed for this package include controller data, program start times, days on, station minutes, smart controller settings, plant factor, soil type, slope, soil moisture, precipitation rate, and distribution uniformity fields. The California MWELO audit checklist reviewed for this package includes active stations, hydrozone maps kept with the controller, controller type, establishment setting, and schedules for establishment and established landscapes. These sources support capturing controller configuration rather than only the physical hardware.

Rain Bird ESP-ME3 material reviewed for this package also supports the importance of program evidence. It describes start times, station runtimes, water days, program-based scheduling, common programming errors with multiple start times, seasonal adjust, flow sensor by station, rain sensor by station, and master valve by station. A screenshot packet can show whether the controller is in a known turnover state.

Do not let the schedule record become a design guarantee. The record should say what program was active at turnover, what approved schedule it came from, what establishment period applies, and who owns future changes. It should not promise that the schedule will remain correct through every season, weather pattern, planting change, or maintenance decision.

Index the photo log

A station map record depends on a usable photo index. Do not leave photos in a camera roll with generic filenames. Use a sequence that matches the controller map, such as LC1-S01-zone, LC1-S01-valve-tag, LC1-S01-controller-run, and LC1-S01-correction if needed. For rain sensor photos, use the sensor ID and test step. For controller program photos, use controller ID, program, and screen type. This makes the packet reviewable months later when the owner is trying to solve a dry spot, a leaking valve, or a sensor complaint.

Each photo caption should answer four questions: what controller, what station, where on site, and what condition is being shown. A caption that says VB-2 tag close-up is not enough if the owner has several controllers. LC-1 station 5, VB-2, west entry shrubs, valve tag after correction is much better. Wide photos should name the direction of view. Close-up photos should keep enough surrounding context to avoid becoming anonymous parts photos.

Photo indexes also help when the record is partial. If station 11 is held for a missing valve tag, the photo index should show that station 11 has a controller run photo and a zone photo, but no accepted valve tag photo. That helps the owner see exactly what remains open. It also prevents a later reviewer from mistaking a missing photo for a passed condition.

When the owner requires a digital closeout system, preserve file names and metadata as much as the platform allows. If the system renames uploads, add a photo schedule in the package. The University of Washington standard reviewed for this package supports photo documentation linked to plan markups in an owner records environment. The practical point is simple: the photo log should survive outside the installer's phone.

Confirm smart-controller access

Smart-controller access is part of owner handoff when the installed system uses an app, web portal, Wi-Fi module, central control platform, weather service, or soil-moisture data source. The record should show who owns the account, how the owner receives access, whether the controller is online or locally managed at turnover, and whether remote settings match the physical controller and field station map. Do not publish passwords or private account details in the public packet; store credentials under the owner's secure process.

EPA WaterSense controller material reviewed for this package frames weather-based and soil-moisture-based controllers as tools that work when installed, programmed, and maintained properly. That means a smart controller cannot be treated as a black box. The turnover record should show whether weather data, soil sensor input, seasonal adjustment, and station naming are active, disabled, or outside the scope. If the controller is clock-based, say so. If it is smart-capable but not connected, say that too.

Smart-controller station names should match the field record. If the app says Front Lawn while the controller chart says Station 2 and the valve tag says S03, the owner inherits confusion. Align the account station names, controller door chart, as-built map, and valve tags before turnover or list the mismatch as a hold. The best handoff lets the owner search the app, the printed chart, and the photo folder using the same station names.

Remote access should not be confused with acceptance. A controller can be online and still have wrong valve tags, a bypassed rain sensor, unknown spare stations, or outdated as-built photos. Conversely, a simple clock controller can have an excellent turnover record if every station is mapped, tagged, photographed, and explained. The record should document the actual system rather than ranking technology as good or bad.

Reconcile map mismatches

Station-map mismatches should be resolved before final release whenever possible. Common mismatches include the controller station number not matching the valve tag, the valve box tag not matching the as-built plan, a station serving a different zone than the controller chart, a spare station showing a runtime, a future station accidentally active, or a rain sensor setting documented in the app but not in the controller photo set. Each mismatch should be treated as a traceability problem until corrected.

Use a simple reconciliation process. First, run the station from the controller or approved central command. Second, identify the area receiving water. Third, find the valve box and tag. Fourth, compare the as-built drawing and controller chart. Fifth, compare the controller program or app station name. Sixth, update only the records that are proven wrong. This avoids the common mistake of changing the map to match one observation while leaving the controller or tag inconsistent.

Some mismatches are documentation-only and can be cleared quickly. A missing caption, an outdated controller chart, or a photo filed under the wrong station may only need a record correction and reviewer signoff. Other mismatches suggest field work: crossed wires, swapped solenoids, wrong valve tag, abandoned station, hidden valve box, or a station that controls two areas not shown on the plan. Those conditions need a field correction or explicit owner acceptance.

The record should preserve the reconciliation history. Keep the first mismatch photo, the corrected chart or tag, the station run retest, and the final release note. If the owner accepts a known nonstandard condition, such as one station serving two small planters because the approved design says so, write it clearly. Future maintenance crews should not have to decide whether a condition was intentional or a turnover oversight.

Inspection table

Use a compact table so the irrigation contractor, landscape architect, owner, maintenance team, and commissioning or QA reviewer look at the same evidence.

Turnover checklist

Run this checklist before owner turnover of the controller station map and field identity record.

• Controller ID, location, model, station module status, and active station count are recorded.
• Every active station has a controller number, program, runtime, zone name, and valve box ID.
• Every inactive, spare, future, temporary, or excluded station is named instead of left blank.
• Valve box lids, box locations, internal valve tags, and station labels are photographed.
• Permanent valve tags match the controller station map and as-built drawing.
• The rain sensor or weather sensor model, location, controller setting, and test result are recorded.
• Wireless sensor signal, pairing, and battery indicators are photographed where applicable.
• Controller settings show sensor active or bypass status and any station-specific sensor override.
• Each active station is run from the controller or accepted central-control command.
• Each active station has at least one as-built zone photo with controller, station, and direction caption.
• Controller runtimes, start times, watering days, seasonal adjust, rain delay, and establishment schedule are documented.
• Hydrozone map, laminated controller chart, or owner-required station map is attached or photographed.
• Mismatches between controller, valve tag, station map, and field zone are held or corrected.
• Corrections include before photo, correction owner, updated map or tag, and retest photo.
• Owner receives manuals, controller access, sensor location, station map, as-builts, and maintenance notes.
• Final release says which controller, stations, maps, tags, sensors, and exceptions are accepted.

Weak versus strong record

Weak record: Controller programmed, rain sensor installed, valve boxes tagged, irrigation accepted.

Strong record: Controller LC-1 at the north maintenance room was reviewed on June 9, 2026 for stations 1 through 18. The controller door chart, station map, and field tags were checked against irrigation as-built sheet IR-3. Photos LC1-01 through LC1-05 show the controller, station module status, active programs, current date and time, seasonal adjust, and rain sensor setting. Photos LC1-06 through LC1-23 show each active station running and the as-built zone view for each station.

The station map lists station 1 as north entry turf spray, VB-1; station 2 as north entry shrub drip, VB-1; station 3 as west parking lot island rotor, VB-2; and so on through station 18. Stations 19 through 22 are shown as unused module capacity. Each valve box has a wide location photo and a close-up tag photo. Rain sensor RS-1 is photographed on the south fascia, with controller sensor setting active and the approved test procedure documented.

Two exceptions were found. VB-4 had a field tag that read station 9 while the controller map showed station 8. Station 14 had no as-built photo for the west tree bubbler area. The contractor corrected the VB-4 tag, updated the controller chart, added retest photos LC1-31 through LC1-33, and added the missing station 14 zone photo. The owner accepted LC-1 stations 1 through 18 with no open station-map exceptions.

Common mistakes

The most common mistake is confusing a station list with a station map. A list of numbers and runtimes does not tell the owner where the water goes, where the valve is, what plant material is served, or what photo proves the field condition. The record should connect controller, station, valve box, tag, zone, program, and photo in one traceable chain.

Another mistake is proving the rain sensor physically exists but not proving it is active in the controller. Some controllers can obey or ignore a weather sensor globally, and some allow station-level behavior. A mounted sensor, a controller display, and a manual station run need to be interpreted together. A manual run may bypass or ignore a sensor depending on the controller behavior and procedure, so the test method matters.

Valve box mistakes are also common. Tags are missing, labels are handwritten with fading marker, box lids are not photographed in context, tags are tied where they block service, boxes are buried in mulch, or the valve tag does not match the controller station. These mistakes make maintenance slower and can cause the wrong valve to be adjusted during a leak or dry-spot complaint.

Other mistakes include failing to mark spare stations, forgetting temporary establishment zones, leaving an outdated controller chart inside the door, photographing only wet turf, missing owner credentials for smart controllers, not documenting station-specific sensor overrides, deleting failed observations after correction, and handing over a schedule without saying who changes it after establishment.

When to hold turnover

Hold turnover when the controller station map does not match the field. Examples include station 6 running a different zone than the chart, a valve box tag showing a different station number, a controller program with station runtimes for unused stations, a future station left active, or an as-built map that omits a field change. These are identity failures, and they should be corrected before the owner inherits the system.

Hold turnover when the rain sensor or weather sensor cannot be proven. A sensor with no model, unknown location, bypassed controller setting, failed test, dead battery, weak signal, missing pairing, or station-level override that nobody documented should be held. If the project intentionally leaves a sensor bypassed for establishment or construction reasons, the owner should approve that condition and the record should say when it changes.

Hold turnover when the owner cannot operate or maintain the station map after acceptance. Missing controller door chart, no as-built zone photos, no valve box tag photos, no manuals, no smart-controller credentials, no maintenance-period schedule, no field training, or no open-exception list can all turn an otherwise working system into a maintenance dispute.

A hold should be precise. Name the controller, station, valve box, sensor, photo number, issue, correction owner, retest method, map update required, and whether the hold affects one station, one controller, or the entire landscape phase. Vague notes such as map issue or sensor check needed are hard to clear and easy to ignore.

Correction and retest photos

Corrections should preserve both the original issue and the final condition. If a valve tag was wrong, keep the wrong-tag photo, add the corrected-tag photo, and show the updated station map. If a rain sensor was bypassed, keep the bypass photo, then show the corrected setting and test result. If an as-built photo was missing, add the zone photo with the station caption and update the index.

Retest the specific link that failed. A changed valve tag needs a tag and station-map check. A wiring correction needs a controller-to-zone run. A rain sensor correction needs a product-appropriate sensor test or status confirmation. A controller chart correction needs a photo of the final chart. A zone mismatch needs a station run and field photo after the correction.

Do not let a correction create a new mismatch. If station 11 and station 12 are swapped in the controller, changing only the valve tags may leave the program wrong. If the as-built plan is updated but the controller door chart is not, the owner still has two conflicting records. When one part of the chain changes, review controller, station map, valve tag, as-built photo, program, and owner handoff together.

The final retest photo should show the system in its accepted state. For a controller, that means the correct program, sensor status, and normal operating mode. For a valve box, that means the tag is visible and serviceable. For a rain sensor, that means the test has been completed and the device is returned to its intended setting. For a station map, that means the final file or chart is the one the owner actually receives.

Owner handoff

The owner handoff should include the controller chart, digital station map, as-built irrigation plan, valve box photo log, rain sensor photo and test record, controller program screenshots or export, manuals, warranty or service contacts, smart-controller access procedure, seasonal schedule basis, establishment-to-established change date, open exceptions, and training attendance. The record should be usable by the person who was not present during installation.

For large or institutional properties, include the format the owner actually uses. The University of Washington standard reviewed for this package expects an electronic operation and maintenance package, owner and grounds training documents, and photos with plan-markup links. Riverside material expects service manuals, as-builts, and controller charts delivered before maintenance starts. Those are owner-specific examples, but the practical lesson is broad: the handoff should live in the owner's system, not only in a contractor's phone.

Training should be station-based. Walk the owner through one or two representative stations: read the controller chart, run the station, find the valve box, read the tag, confirm the as-built photo, point out the rain sensor, and show where the current program is recorded. That short exercise reveals whether the record is understandable. If the owner cannot follow the chain, the packet is not ready.

The handoff should also explain what the record does not do. It does not guarantee plant health, eliminate future seasonal adjustments, replace periodic irrigation audits, replace backflow testing, approve electrical work, or commit the contractor to a maintenance scope not in the contract. It preserves the turnover baseline so the owner can operate and maintain the system with fewer unknowns.

Different from an audit article

The broader irrigation audit article on Anvilfield covers catch-can data, overspray, leaks, controller schedules, sensors, repairs, and owner handoff. This article intentionally narrows the lens. It asks whether the controller station map, valve box tags, rain sensor proof, and as-built zone photos are ready for owner turnover. It is the map-and-identity layer inside the broader audit packet.

A site can pass a station-map turnover check and still need a detailed irrigation audit. For example, every station may be correctly mapped and tagged, yet a catch-can test may show poor uniformity on a turf rotor zone. The opposite can also happen: an audit may collect useful performance data, but the owner still cannot find VB-7 or tell whether station 12 is a shrub drip zone or tree bubbler zone. Both records matter.

Keep the deliverables separate when the review questions differ. The audit asks how the system applies water, whether defects exist, and what schedule is appropriate. The station-map record asks whether the owner can find, operate, test, and understand the installed system station by station. On a small job the same packet may contain both. On a larger job, separate sections make the record easier to maintain.

Source-backed field logic

The validated sources do not create one universal irrigation turnover form. They support the logic of the record. EPA WaterSense audit material supports documenting leaks, runoff, overspray, rain shutoff, controller capabilities, catch-can data where applicable, and schedules. EPA WaterSense controller material supports the importance of weather-based or soil-moisture-based controllers being properly installed, programmed, and maintained.

Irrigation Association worksheets support controller data, stations being used, sensors installed, start times, station minutes, smart controller settings, test area maps, site conditions, and schedule worksheets. Texas A&M AgriLife controller material supports mapping zones before programming, keeping a zone listing in the controller box, manually testing zones, understanding start times and runtimes, and recognizing rain or freeze sensor purpose.

Owner standards support the handoff format. Riverside material supports service manuals, record drawings, field as-builts, final as-built verification, and controller charts. University of Washington material supports daily-maintained as-builts, alphanumeric labels tied to zone numbers, one automatic control valve per zone, permanent valve tags, color-coded laminated zone maps and tables, electronic operation and maintenance submittals, owner training documents, and site progress photos linked to plan markups.

Manufacturer manuals support the controller and sensor record. Rain Bird ESP-ME3 material supports station numbering, station runtimes, program schedules, manual single-station operation, weather sensor settings, and station-level sensor behavior. Rain Bird RSD and WR2 rain sensor material supports rain sensor placement, status indicators, battery or signal evidence for wireless sensors, and functional testing. That is why the article requires photos of both field devices and controller settings.

Answer-ready summary

A concise answer for meeting notes: The irrigation controller station map turnover record should connect every active station to the correct valve box tag, zone description, program setting, rain sensor status, as-built zone photo, exception, correction, retest, and owner handoff before the system is accepted.

For a photo packet, use this sentence: Include controller overview photos, station program screenshots, controller door chart, valve box wide and close-up tag photos, rain sensor location and test photos, as-built zone photos for each active station, mismatch corrections, retest photos, and final release notes.

For a hold, use this sentence: Turnover is held for controller blank station blank until the valve tag, controller map, rain sensor status, as-built photo, and station run test agree, and the owner receives the corrected map and retest photo.

Compliance and safety limits

This article does not interpret landscape ordinances, approve water budgets, certify irrigation efficiency, size valves, approve backflow protection, approve reclaimed-water systems, perform electrical work, set legal watering days, design controller programs, select sensors, authorize trenching, approve pressure testing, or define maintenance contract obligations. It is a documentation structure for turnover evidence.

Follow the approved drawings, specifications, product manuals, owner standards, water agency requirements, local and state rules, backflow authority, electrical safety procedure, reclaimed-water requirements, irrigation professional direction, landscape architect direction, and owner acceptance process. If those documents conflict with this checklist, follow the controlling document and record the decision in the turnover file.

Do not open energized controllers, alter wiring, bypass sensors, change valve tags, modify programs, enter traffic areas, open valve boxes in unsafe conditions, test during prohibited watering periods, or disturb backflow, pump, or reclaimed-water equipment unless the qualified team and project procedure allow it. If the station map cannot be verified safely, hold the record and get direction.

Final release questions

Can the owner open the controller and understand every active station? Does each station have a zone name, valve box ID, field tag, program setting, as-built photo, and release status? Are spare, future, disabled, temporary, and excluded stations labeled clearly enough that future maintenance crews will not chase them?

Can the owner find each valve box and read the tag? Do the controller chart, as-built plan, field valve tag, and photo log agree? Is the rain sensor location known, the controller setting documented, the test recorded, and the final state clear?

Are exceptions closed or held with correction owners and retest photos? Did the owner receive the station map, manuals, credentials, training, schedule basis, and maintenance notes? If the answer is yes, the station map turnover record is useful. If the answer is no, the irrigation system may run, but the handoff is not ready.

Sources checked

• EPA WaterSense, Guidelines for Irrigation Audits on WaterSense Labeled New HomesUsed for visual inspection, leaks, runoff, overspray, rain shutoff, controller capabilities, schedule posting, pressure verification, and audit documentation context.
• EPA WaterSense, Labeled New Home Irrigation Audit ChecklistUsed for checklist evidence around leaks, overspray, DULQ, rain shutoff, controller capabilities, station scheduling, and supporting documents.
• EPA WaterSense, WaterSense Labeled ControllersUsed for weather-based and soil-moisture-based controller context, proper installation, programming, maintenance, and controller handoff framing.
• EPA WaterSense, Water Efficiency Management Guide: Landscaping and IrrigationUsed for commercial irrigation inspection, controller and sensor programming, schedule adjustment, overspray, runoff, and ongoing maintenance context.
• California Department of Water Resources, MWELO Irrigation Audit ChecklistUsed as a state checklist example for active stations, hydrozone map with controller, valve box identification, controller type, establishment schedule, and irrigation schedule fields.
• Irrigation Association, Landscape Irrigation Auditor Blank WorksheetsUsed for controller data, stations being used, sensors installed, start times, station minutes, smart controller settings, test area map, site conditions, and schedule worksheet context.
• Texas A&M AgriLife Extension, Controller BasicsUsed for station versus zone terminology, valves in valve boxes, mapping zones before programming, controller box station descriptions, manual zone testing, runtimes, start times, and rain/freeze sensor context.
• Rain Bird, ESP-ME3 Controller Advanced User ManualUsed for station numbering, station runtimes, programs, manual station runs, weather sensor settings, rain sensor on/off behavior, station-level rain sensor options, and controller program documentation.
• Rain Bird, WR2 Wireless Sensor User ManualUsed for wireless rain sensor components, controller interface, pairing, signal, battery indicators, mounting, and irrigation suspension context.
• Rain Bird, WR2 Product Testing in FieldUsed for rain sensor test methods, rainfall suspension evidence, controller-interface indicators, and field-test documentation context.
• Rain Bird, RSD Rain Sensor Installation and Operating InstructionsUsed for rain sensor location, natural precipitation exposure, wiring terminals, rainfall settings, automatic suspension, and post-installation sensor test context.
• University of Washington Facilities, Irrigation Design StandardUsed as owner-standard context for as-built drawings, zone labels, valve tags, color-coded laminated zone maps, eO&M documents, owner training, and photo-linked plan markups.
• County of Riverside Transportation Agency, Section 328400 Irrigation SystemUsed as owner-spec context for service manuals, record drawings, field as-builts, final as-built verification, controller charts, and final walk-through handoff.
• NC State Extension, Landscape Irrigation Auditing Made SimpleUsed for inspection before audit, broken or nonfunctioning components, head alignment, leaks, pressure symptoms, and repair-before-measurement context.
• New Mexico State University Extension, How to Perform a Catch Can Irrigation AuditUsed for practical sprinkler-zone audit workflow context and for distinguishing station identity records from broader catch-can measurement records.

Related guides