BackflowPath Local backflow requirements
Request help
Menu
Request help
Report submission route

Submit Pleasanton Aqua/TrackMyBackflow backflow test reports

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

Open utility source workflow Utility requirements Find from notice Request local help
City: Pleasanton Utility: City of Pleasanton Cross-Connection Control Plan Cadence: Annual testing and event-driven follow-up under the City's cross-connection control plan Last verified: 2026-07-06
Local answer

What to check for Pleasanton

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

  • Due basis: Pleasanton's official cross-connection control plan says testers submit qualifications and completed test reports through an online portal held by the City's third-party backflow service provider, currently Aqua Backflow.
  • Notice or device clue: Look for the Hazard ID, Site ID, device record, or TrackMyBackflow customer record.
  • Who is affected: Pleasanton customers with required backflow assemblies and testers who must keep certification, gauge calibration, and business license records current.
  • Acceptance rule: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
  • Program phone: 925-931-5500
Notice-to-closeout map

Source-backed procedure before the record is treated as closed

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

Authority City of Pleasanton Cross-Connection Control Plan
Notice trigger Look for the Hazard ID, Site ID, device record, or TrackMyBackflow customer record.
Tester gate View the official tester list
Submission route Pleasanton cross-connection control plan (official plan)
Proof to keep Report acceptance depends on the named portal and the utility-approved tester route; 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: Pleasanton cross-connection control plan - official plan
  • Submission path: Aqua Backflow online portal - Aqua Backflow reporting portal
  • Notice or device clue: Look for the Hazard ID, Site ID, device record, or TrackMyBackflow customer record.
  • Tester gate: Start with the governing authority's published tester list. This utility has an official approved-tester route and it should be treated as the primary source.
  • Report acceptance: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
  • Due basis: Pleasanton's official cross-connection control plan says testers submit qualifications and completed test reports through an online portal held by the City's third-party backflow service provider, currently Aqua Backflow.
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 Hazard ID, Site ID, device record, or TrackMyBackflow customer record.
  • 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

  • Pleasanton cross-connection control plan (official plan)
  • Aqua Backflow online portal (Aqua Backflow reporting portal)
  • View the official tester list
After filing

Keep acceptance proof

  • Report acceptance depends on the named portal and the utility-approved tester route; 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

Pleasanton workflow order

  1. Match the utility notice to the service address, device or assembly record, and due date.
  2. Confirm the tester is accepted through the governing tester-list or approval route before the report is filed.
  3. File the result through the stored submission path: Pleasanton cross-connection control plan, Aqua Backflow online portal.
  4. Keep proof that the report was submitted and accepted; a passed field test alone may not close the compliance cycle.
  5. If the assembly failed, follow the repair, retest, and resubmission sequence before assuming compliance is restored.
City FAQ

Pleasanton questions before you act

How do I submit a backflow test report for Pleasanton?

Use the official utility workflow and submission methods listed on this page: Pleasanton cross-connection control plan, Aqua Backflow online portal. Program phone: 925-931-5500. Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.

What information should be ready before filing the Pleasanton report?

Look for the Hazard ID, Site ID, device record, or TrackMyBackflow customer record. Also keep the due date, service address, tester credential status, device type, and proof of submission.

Does the tester or owner submit the Pleasanton 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 Pleasanton Cross-Connection Control Plan.

Who controls the rule for Pleasanton?

Pleasanton search demand is routed to City of Pleasanton Cross-Connection Control Plan. Pleasanton customers with required backflow assemblies and testers who must keep certification, gauge calibration, and business license records current.

What costs or fees should I expect for Pleasanton?

Testing is market-priced by the tester. Repair and retest cost depends on assembly type and whether another accepted portal entry is needed. Pleasanton's strongest cost signal is the administrative risk around accepted online reporting and tester credential upkeep.