Backflow testing for apartment & multifamily property managers
For a single-family homeowner, backflow testing is one letter and one phone call a year. For a property manager it's a portfolio problem: multiple buildings, multiple assemblies per building, different due dates, and notices that may be going to an owner's address instead of yours.
Who's actually responsible
Legally, the property owner. In practice, testing lands with whoever runs building operations — usually the management company — the same way elevator inspections and fire alarm monitoring do. Two things to nail down in the management agreement: who tracks the due dates, and who pays for tests and repairs.
Step one: inventory
A typical multifamily property has more assemblies than anyone remembers: landscape irrigation, a fire line, sometimes premises isolation at the meter, plus boiler or pool connections. Start with the water purveyor's records for each address, then have a tester verify what physically exists — records drift when assemblies are added or removed without paperwork.
Run it as a portfolio, not per-letter
- One testing company across the portfolio: one contact, batched visits, per-device pricing, one set of records.
- Your own compliance calendar. Don't depend on notices — they go to whatever address the purveyor has on file, which is often the owner, not you.
- A standing spreadsheet of every assembly: property, location on site, serial number, due date, last result. Any good testing company will supply this after the first portfolio visit.
- Budget for failures. Across a portfolio, a few assemblies will fail each year — plan for repair-or-replace decisions rather than being surprised by them.
Condo or HOA context instead? The responsibility split works differently — see HOA backflow testing responsibilities.