Evergreen guide

Approved testers vs find a tester

These two page types look similar on the surface, but they have different trust contracts. If they blur together, the site stops being reliable.

Last reviewed: 2026-06-29 Verification code: TL Freshness window: 120 days
Why this page exists

Support the local pages without blurring the official rule

Official authority lists stay official-first. Directory pages are clearly labeled as non-official and only exist when there is real public inventory to show.

Backflow instrumentation and technical ledger panel
Technical reading path

Guides should reduce interpretation risk, then route the user back down into the exact utility rule and tester workflow.

Guide chapter

What an approved tester page can say

An approved tester page can point to an official utility list or city-maintained lookup. It can also show clearly separated directory inventory, but only below the authority block and without implying endorsement.

  • Round Rock, Lewisville, and College Station all expose official tester lists.
  • The authority source should always appear before any directory placement.
Guide chapter

What a find-a-tester page can say

A non-official directory can help users discover local testers, but it cannot borrow the language or visual hierarchy of an authority list. If there is no real public inventory, the page should not render.

  • Directory pages are for lead routing, not for making compliance claims.
  • If a provider list is draft-only or unverified, the route should stay hidden.
Guide chapter

Where people get misled

The common failure mode is taking a city page that mentions tester registration and presenting it as though the site itself maintains the approved roster. That is exactly the ambiguity this project avoids.

  • Dallas is a good example of a strong official program page that still does not justify an approved-list claim by itself.
  • When in doubt, route users back to the governing utility page.
Utility layer

Use this guide with local utility pages

Metro layer

Metro clusters where this guide matters

Review record

How this guide is kept trustworthy

Official tester lists and commercial directories must stay separate. Authority pages lead with the governing source; non-official directories are explicitly labeled and only go live when real inventory exists.

This page exists to make a repeated question legible without pretending to replace utility-specific authority language.

Related guides

Support pages that belong in the same reading path

Reading path

Backflow test notice: what to do next

What to check when a city, utility, BSI, SwiftComply, VEPO, or water district sends a backflow test notice.

Reading path

How we verify local backflow rules

What counts as an official source, how local utility pages override generic assumptions, and how stale pages are re-verified.

Reading path

Failed backflow test next steps

What a failed backflow test usually means, how repair and retest sequencing works, and where owners lose time.

Reading path

Backflow test cost: annual testing, repairs, and portal fees

How annual backflow test cost changes when the utility requires registered testers, repairs, retests, BSI fees, or online reporting.