Skip to main content
BackflowVerdictIdentify · decide · verify Find my utility
Menu

municipal utility · official record

McKinney utility 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.

Last verified2026-06-29
Testing frequencyAs required by the City workflow using McKinney test forms
Report routeMcKinney Public Works signed-original report workflow
Evidence5 official source link(s)

Fast answer

Who, when, and what device?

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
Properties and testers operating within McKinney's cross-connection prevention program, including general assemblies, irrigation jobs, and fireline testing workflows.
Covered devices
General backflow assemblies tested using City forms · Irrigation backflow devices · Fireline assemblies using the separate fireline registration path
Risk if missed
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.

Exact workflow

Follow the local sequence

  1. 01

    Register the BPAT with the City of McKinney and pay the registration fee before testing.

  2. 02

    Use only City-approved test forms for each assembly tested, and switch to the fireline form set when the scope requires it.

  3. 03

    If the project involves irrigation, complete the CSS permit and inspection path alongside the backflow paperwork.

  4. 04

    Submit the signed and dated original through the Public Works recordkeeping process by mail or physical drop-off.

  5. 05

    Keep registration, calibration, and payment details current so reports are not rejected.

Tester gate

Who can produce an accepted result?

City BPAT registration, Gauge calibration that keeps registration current, Fireline BPAT registration form when the tester works on fireline assemblies

Submission route

Where the result goes

McKinney Public Works signed-original report workflow

Report packet: City-approved BPAT test report form, City BPAT registration, Signed and dated original report, Fireline registration form when the assembly scope requires it

Tester credentials: City BPAT registration, Gauge calibration that keeps registration current, Fireline BPAT registration form when the tester works on fireline assemblies

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

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

  • McKinney backflow program page program page
  • McKinney irrigation portal page program page
  • McKinney test report form official form

Local detail

Property, device, and enforcement notes

Open the parts that match the property and system. These details stay subordinate to the fast workflow above.

Program and failure notes
  • 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.
  • BPAT registration with the City is required before testing.
  • Electronic signatures are not accepted on the City's forms.
  • Registration expires with the gauge calibration expiration date.
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 notes
  • 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.
Irrigation

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.

  • 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.
Fire line

McKinney separates fireline testing administratively. Fireline BPATs use a different City registration form than general testers, so the first compliance question is which registration path applies.

  • McKinney publishes a dedicated fireline BPAT registration form.
  • Using the general registration path for a fireline-only scope creates avoidable paperwork risk.
  • The City still expects the correct test form and signed original once testing is complete.
Cost and fee context

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.

Evidence ledger

Official sources

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.

BackflowVerdict summarizes these records; the governing entity remains the authority.

Open official program page
  1. 01
    McKinney backflow programofficial program pageOpen source ↗
  2. 02
    McKinney irrigation portal pageofficial program pageOpen source ↗
  3. 03
    McKinney BPAT registration formofficial formOpen source ↗
  4. 04
    McKinney fireline BPAT registration formofficial formOpen source ↗
  5. 05
    McKinney BPAT test report formofficial formOpen source ↗

Commercial handoff · separate layer

Still need help after reading the rule?

The request keeps this utility ID and source page with the handoff.

Get help with City of McKinney Cross Connection Prevention