Irrigation city route

McKinney irrigation backflow testing

McKinney irrigation work runs through a separate City Services and Sustainability portal. Contractor registration, permits, inspections, and payments all sit in CSS before the assembly paperwork is truly done.

Open irrigation workflow Utility requirements Find from notice Request local help

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

Local answer

What to check for McKinney

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.
Who is affected: Properties and testers operating within McKinney's cross-connection prevention program, including general assemblies, irrigation jobs, and fireline testing workflows.
Acceptance rule: Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.
Report workflow: McKinney Public Works signed-original report workflow
Credential gate: City BPAT registration, Gauge calibration that keeps registration current, Fireline BPAT registration form when the tester works on fireline assemblies
Program phone: 972-547-7362

Evidence-backed next step

Use the governing utility workflow

City search demand maps directly to the McKinney backflow program and City-form workflow.

Open irrigation workflow

Notice-to-closeout map

Source-backed procedure before the record is treated as closed

This is the working path for McKinney notices: match the authority, confirm the tester gate, use the accepted submission route, and keep proof that the report was accepted.

Authority City of McKinney Cross Connection Prevention

Notice trigger Look for the utility name, service address, assembly serial number, account or notice ID, and due date.

Tester gate Confirm tester eligibility with the governing utility before scheduling.

Submission route McKinney Public Works signed-original report workflow

Proof to keep Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.

Failure branch Open failed-test workflow before treating repair, retest, or resubmission as complete.

Local signals

Signals that matter before you act

Irrigation uses a separate City portal rather than only the backflow page.
Contractors, permits, inspections, and payments are all handled in CSS.
Backflow testing still has to align with the City's approved forms and submission rules when the assembly is part of the irrigation project.

Other McKinney routes

Stay inside the city intent cluster

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 fire-line backflow testing Check McKinney fire-line backflow testing triggers, assembly rules, tester requirements, and the official utility workflow.

arrow_forward

Workflow

McKinney workflow order

Use the CSS portal for irrigation contractor registration, permits, and inspections.
Coordinate the backflow test with the irrigation project timeline.
Submit the signed City test report once the field work is complete.

Official source trail

Source-backed utility record

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

City FAQ

McKinney questions before you act

Which utility controls this McKinney backflow route?

McKinney maps to City of McKinney Cross Connection Prevention. City search demand maps directly to the McKinney backflow program and City-form workflow.

What should I verify before scheduling in McKinney?

Confirm the due basis, property type, device type, and submission method before booking. Then use the non-official directory only after confirming the utility workflow, and make sure the report can be filed through the required utility or portal path.

Who controls the rule for McKinney?

McKinney search demand is routed to City of McKinney Cross Connection Prevention. Properties and testers operating within McKinney's cross-connection prevention program, including general assemblies, irrigation jobs, and fireline testing workflows.

What costs or fees should I expect for McKinney?

Private market pricing varies; BPAT registration with the City also carries a public registration fee. Repair and retest costs vary by assembly and scope, but paperwork handling is stricter than many BSI-managed cities. In McKinney, process friction matters almost as much as the raw test quote because the City still wants signed originals and approved forms.