Report submission route

Submit McKinney reporting portal backflow test reports

Use this page when the notice or tester workflow is about submitting, uploading, filing, or confirming a backflow test report for McKinney.

Open utility source 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

Use this page when the notice or tester workflow is about submitting, uploading, filing, or confirming a backflow test report 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.
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 utility source 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 backflow program page (program page)

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

Submission path: McKinney backflow program page - program page
Submission path: McKinney irrigation portal page - program page
Submission path: McKinney test report form - official form
Notice or device clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
Tester gate: 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.
Report acceptance: Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.
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.

Submission packet

What the report needs before it can count

Use this as the working checklist for the owner, tester, or property manager before treating a passed field test as a completed compliance cycle.

Before filing

Match the notice record

Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
Service address, device type, due date, and utility name must match the notice.
Use the utility workflow before relying on a generic tester search.

Filing gate

Confirm the accepted route

McKinney backflow program page (program page)
McKinney irrigation portal page (program page)
McKinney test report form (official form)
Confirm tester eligibility with the utility or portal.

After filing

Keep acceptance proof

Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.
Keep portal confirmation, email receipt, account history, or accepted report record.
If the assembly failed, use the failed-test workflow before assuming the case is closed.

Failed-test workflow

Workflow

McKinney workflow order

Match the utility notice to the service address, device or assembly record, and due date.
Confirm tester eligibility with the utility or portal before treating the report as accepted.
File the result through the stored submission path: McKinney backflow program page, McKinney irrigation portal page, McKinney test report form.
Keep proof that the report was submitted and accepted; a passed field test alone may not close the compliance cycle.
If the assembly failed, follow the repair, retest, and resubmission sequence before assuming compliance is restored.

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

How do I submit a backflow test report for McKinney?

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. Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.

What information should be ready before filing the McKinney report?

Look for the utility name, service address, assembly serial number, account or notice ID, and due date. Also keep the due date, service address, tester credential status, device type, and proof of submission.

Does the tester or owner submit the McKinney report?

The field tester often controls portal entry, but the owner should keep the notice, due date, and proof that the report was accepted by City of McKinney Cross Connection Prevention.

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.