Annual testing
Open the annual page when the utility notice is about routine testing, timing, and accepted submission methods.
municipal utility
City of McKinney Cross Connection Prevention backflow testing requirements
McKinney is a paperwork-heavy utility. The main risk is not just failing the field test; it is using the wrong City form, the wrong registration path, or the wrong submission method.
Testing cadence: As required by the City workflow using McKinney test forms
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.
Annual or event-based timing
Properties and testers operating within McKinney's cross-connection prevention program, including general assemblies, irrigation jobs, and fireline testing workflows.
- 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.
Non-compliance penalties
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.
- Electronic signatures are not accepted.
- Using the wrong form can break the acceptance workflow even if the assembly was tested.
- Registration expires with the gauge calibration expiration date, so stale tester credentials can create compliance problems.
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.
- Register the BPAT with the City of McKinney and pay the registration fee before testing.
- Use only City-approved test forms for each assembly tested, and switch to the fireline form set when the scope requires it.
- If the project involves irrigation, complete the CSS permit and inspection path alongside the backflow paperwork.
- Submit the signed and dated original through the Public Works recordkeeping process by mail or physical drop-off.
- Keep registration, calibration, and payment details current so reports are not rejected.
Source block
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.
- Last verified: 2026-06-29
- Verification code: TL
- Freshness window: 45 days
- Report a correction or stale source
- McKinney backflow program official program page
- McKinney irrigation portal page official program page
- McKinney BPAT registration form official form
- McKinney fireline BPAT registration form official form
- McKinney BPAT test report form official form
Submission methods and utility contact
Where the rule applies
- Properties whose assemblies are tested under the City's cross-connection prevention workflow
- Irrigation systems routed through the City's CSS portal
- Fireline testers and general testers registering with the City
Devices in scope
- General backflow assemblies tested using City forms
- Irrigation backflow devices
- Fireline assemblies using the separate fireline registration path
Residential notes
- Residential owners most often meet McKinney through irrigation permitting and inspection, not through a public approved-tester list.
- If the assembly touches a permitted irrigation job, the CSS portal matters before the test report does.
Commercial and managed properties
- Commercial and managed properties should treat McKinney as a document-control city because registration, original signatures, and the right form set all matter.
- Fireline and general testing use different City registration documents, so scope mistakes are easy to make.
FAQ
Local questions people actually ask
Does City of McKinney Cross Connection Prevention require 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.
Who is affected by City of McKinney Cross Connection Prevention backflow rules?
Properties and testers operating within McKinney's cross-connection prevention program, including general assemblies, irrigation jobs, and fireline testing workflows.
How do I submit or confirm a backflow test for City of McKinney Cross Connection Prevention?
Use the official utility workflow and submission methods listed on this page: McKinney backflow program page, McKinney irrigation portal page, McKinney test report form. Program phone: 972-547-7362.
Where should I look for testers for City of McKinney Cross Connection Prevention?
No public tester directory is live for this utility yet. Use the official utility page first and do not infer approval from a generic directory.
Need a tester or local help?
No public tester route is live for this utility yet. Stay on the authority workflow and submission methods before treating any outside provider directory as reliable.
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.