Tester-list pages look deceptively similar. The problem is that the trust claim changes depending on whether the list comes from a county health agency, a utility approval program, or a non-endorsed public handout.
This site has to keep those list types separate because they drive different wording, different route names, and different commercial constraints.
When a city or utility publishes its own approved or authorized tester list, the route can legitimately lead with the authority source and use approved-list language.
A county-certified tester directory can still be valuable, but it describes a different authority relationship. Pasadena is a strong example because the county list informs routing without automatically turning every local page into a utility-approved roster.
Some utilities publish a tester handout while explicitly saying they do not endorse the listed firms. That matters for route naming, label hierarchy, and sponsor separation.
A county-certified tester directory, a utility-approved roster, and a non-endorsed public handout may all be helpful, but they are not interchangeable trust contracts.
What counts as an official source, how local utility pages override generic assumptions, and why stale pages are suppressed.
What a failed backflow test usually means, how repair and retest sequencing works, and where owners lose time.
Why official tester lists and commercial directories must stay separate, and what each page type is allowed to claim.
How to think about annual testing, repair, and retest pricing without confusing a market quote with the compliance rule.