McKinney backflow prevention requirements
Start with the utility page to confirm who is affected, accepted submission methods, phone contact, and source evidence.
City backflow route
McKinney backflow testing routes through City of McKinney Cross Connection Prevention.
City search demand maps directly to the McKinney backflow program and City-form workflow. This page keeps the city search term visible while routing the actual compliance work to the governing utility record.
City: McKinney
Utility: City of McKinney Cross Connection Prevention
Cadence: As required by the City workflow using McKinney test forms
Last verified: 2026-06-29
Next action
Pick the McKinney backflow path that matches the problem
The city term helps discovery. The governing utility still decides the rule, submission method, tester route, and follow-up order.
McKinney annual backflow testing
As required by the City workflow using McKinney test forms McKinney's public materials focus on process more than a consumer-friendly cadence. BPATs must register with the City, use City-specific forms, and submit signed original test results through the Public Works recordkeeping process. Irrigation work runs through the CSS permitting and inspection portal, and fireline testing has a separate City registration form.
McKinney backflow reporting portal
Use the utility page to confirm whether reports go through BSI, WEIRS, SwiftComply, a city portal, or another official submission path.
McKinney failed backflow test
Use the failed-test page when the assembly has already failed and the next step is repair, retest, and report submission.
McKinney irrigation backflow testing
Use this path when the question is tied to sprinkler systems, reclaimed water, outdoor service, or irrigation assemblies.
McKinney fire-line backflow testing
Use this path when the assembly serves fire protection equipment or a managed commercial site.
City intent map
McKinney pages linked from this hub
These routes keep local searches connected to the exact city, while each page still routes back to the governing utility record.
McKinney annual backflow testing
McKinney annual backflow testing: verify who must test, the due-date rule, tester requirements, and the official submission workflow.
arrow_forward
McKinney reporting portal backflow reporting portal
Find the McKinney reporting portal backflow report route, notice or device identifiers, tester gate, and proof of accepted submission.
arrow_forward
Submit McKinney reporting portal backflow test reports
How to submit a backflow test report in McKinney through reporting portal, including notice clues, tester requirements, and accepted filing proof.
arrow_forward
McKinney failed backflow test
What to do after a failed backflow test in McKinney: repair, retest, and confirm accepted report submission with the utility.
arrow_forward
McKinney irrigation backflow testing
Check McKinney irrigation backflow testing triggers, device rules, tester requirements, and the official utility workflow.
arrow_forward
McKinney fire-line backflow testing
Check McKinney fire-line backflow testing triggers, assembly rules, tester requirements, and the official utility workflow.
arrow_forward
Check the local rule before treating this as a generic tester search
- Cadence: As required by the City workflow using McKinney test forms
- Due basis: McKinney's public materials focus on process more than a consumer-friendly cadence. BPATs must register with the City, use City-specific forms, and submit signed original test results through the Public Works recordkeeping process. Irrigation work runs through the CSS permitting and inspection portal, and fireline testing has a separate City registration form.
- Notice or device clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
- Submission: McKinney backflow program page
- Acceptance rule: Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.
- Cost signal: Private market pricing varies; BPAT registration with the City also carries a public registration fee.
McKinney action split
Why McKinney maps to City of McKinney Cross Connection Prevention
City search demand maps directly to the McKinney backflow program and City-form workflow.
- Properties and testers operating within McKinney's cross-connection prevention program, including general assemblies, irrigation jobs, and fireline testing workflows.
- McKinney accepts only City-approved forms and signed originals, so noncompliant paperwork can be rejected even when the field test was completed. Registration lapses with calibration expiration, and separate permit or inspection steps can block closeout.
- Program phone: 972-547-7362
- City route reviewed: 2026-04-04
Source-backed workflow
McKinney is a workflow city, not a simple list city: BPAT registration, signed originals, paper forms, CSS irrigation permitting, and separate fireline registration all matter.
McKinney backflow program
official program page
arrow_forward
McKinney irrigation portal page
official program page
arrow_forward
McKinney BPAT registration form
official form
arrow_forward
McKinney fireline BPAT registration form
official form
arrow_forward
McKinney BPAT test report form
official form
arrow_forward
Support guides
Read these before acting on the McKinney workflow
Backflow test notice: what to do next
What to check when a city, utility, BSI, SwiftComply, VEPO, or water district sends a backflow test notice.
How we verify local backflow rules
What counts as an official source, how local utility pages override generic assumptions, and how stale pages are re-verified.
Backflow reporting portals: BSI, SwiftComply, WEIRS, VEPO, Aqua, Tokay, and SpryBackflow
Find how BSI Online, SwiftComply, WEIRS, VEPO, Envirotrax, Aqua Backflow, TrackMyBackflow, Tokay WebTest, SpryBackflow, and utility customer portals affect backflow test report submission after the field test.
Residential vs commercial backflow rules
Why the local trigger is rarely just residential versus commercial, and how utilities actually split hazard, irrigation, multifamily, and managed-property cases.