Annual testing
Open the annual page when the utility notice is about routine testing, timing, and accepted submission methods.
municipal utility
City of Leander Cross-Connection Control backflow testing requirements
Leander is useful because it publishes hazard-based frequency rules, including annual tests for many residential and commercial hazards and five-year testing for some residences without septic.
Testing cadence: Annual for many hazards; every five years for some residences without septic
Last verified: 2026-06-29
Verification code: TL
Freshness window: 45 days
Next-step paths
Start with the page that matches your situation
This page is the rule hub. Use it to confirm the governing utility workflow, then open the focused page that matches the actual situation on site.
Failed test
Open the failed-test page when the device already failed and you need the repair, retest, and reporting order.
Irrigation
Open the irrigation page when the question is tied to sprinkler systems, reclaimed water, or landscape devices.
Fire line
Open the fire-line page when the backflow assembly serves fire protection equipment or a managed commercial site.
View the official tester list
Use the published tester route after you confirm the rule, due basis, and submission path on this utility page.
Annual or event-based timing
Commercial sites with listed hazards, fire sprinkler systems, pools with auto-fillers, and irrigation systems, especially where septic affects the hazard class.
- Annual for many hazards; every five years for some residences without septic
- Leander's hazard list sets frequency by hazard. The FAQ says annual testing applies to fire sprinkler systems, pools with auto-fillers, residences with septic using irrigation, and other listed hazards, while some residences without septic test every five years.
Non-compliance penalties
Testing frequency depends on the City's hazard list and grandfather rules; replacement of older grandfathered DCVAs may trigger stricter RPZ requirements.
- Leander's cadence depends heavily on hazard type, so using the wrong local assumption can over- or under-test.
- Septic-connected irrigation gets annual RPZ treatment.
- A grandfathered DCVA that needs replacement loses its grandfathered status and must be replaced with an RPZ.
Compliance workflow
Official workflow
Every focused page on this utility still runs through this authority sequence. Confirm the rule here before you branch into repair, testing, or provider routing.
- Use the Leander hazard list and FAQ to determine the testing frequency for the property.
- Use a licensed tester and send new-installation or existing-assembly results through the correct BSI path.
- Check whether an older grandfathered DCVA can remain or must be replaced with an RPZ.
- Keep the property's hazard conditions current with the City if the use changes.
Source block
Leander publishes a hazard-based frequency table, routes new-installation and existing-assembly reports through BSI, and gives unusually clear residential examples in its FAQ.
- Last verified: 2026-06-29
- Verification code: TL
- Freshness window: 45 days
- Report a correction or stale source
- Leander cross-connection and backflow prevention page official program page
- Leander commercial irrigation inspection program official program page
- Leander qualified irrigation inspectors list official pdf
- Leander backflow presentation official presentation
Submission methods and utility contact
Where the rule applies
- Commercial properties with listed hazards
- Residential properties with fire sprinklers or pools with auto-fillers
- Residential irrigation systems, especially where septic is present
Devices in scope
- RPZ
- Grandfathered DCVA in limited older cases
- Other hazard-appropriate backflow assemblies
Residential notes
- Leander is one of the best residential pilot cities because the FAQ explicitly distinguishes annual irrigation cases from five-year low-hazard residential cases.
- Pools with auto-fill, fire sprinklers, septic-connected irrigation, and some private-well setups move a property out of the generic low-hazard bucket.
Commercial and managed properties
- Commercial sites should treat Leander as hazard-list driven rather than blanket annual-for-everything.
- The City also runs a separate commercial irrigation inspection program with a published inspector list, which adds a second workflow next to the backflow assembly rules.
FAQ
Local questions people actually ask
Does City of Leander Cross-Connection Control require annual backflow testing?
Annual for many hazards; every five years for some residences without septic. Leander's hazard list sets frequency by hazard. The FAQ says annual testing applies to fire sprinkler systems, pools with auto-fillers, residences with septic using irrigation, and other listed hazards, while some residences without septic test every five years.
Who is affected by City of Leander Cross-Connection Control backflow rules?
Commercial sites with listed hazards, fire sprinkler systems, pools with auto-fillers, and irrigation systems, especially where septic affects the hazard class.
How do I submit or confirm a backflow test for City of Leander Cross-Connection Control?
Use the official utility workflow and submission methods listed on this page: Leander cross-connection program, BSI submission portal. Program phone: 512-528-2780.
Where should I look for testers for City of Leander Cross-Connection Control?
Start with the governing authority's published tester list. This utility has an official approved-tester route and it should be treated as the primary source.
Need a tester or local help?
Start with the governing authority's published tester list. Use provider help only after the official rule, due basis, and submission path are clear.
Market cost analysis
Local cost band
Typical testing and repair pricing used to frame next-action decisions in the metro around this utility.
Provider browse layer
Public provider direction
Provider routing stays clearly labeled below the official workflow. This block exists to frame public provider discovery without implying authority status.
Local testing profiles
Use provider profiles and metro pages only after confirming the utility workflow and list rules above.
Public directory stays separate
Provider help is reviewed separately from the official utility workflow and never replaces the authority guidance above.