Office Property Backflow Services
Use the office-property service page when a building needs testing, repair, or a more tailored commercial review.
Portfolio / benchmarking
Water is not a side issue for commercial buildings. EPA's 17% benchmark gives property managers a fast way to explain why leaks, fixture upgrades, and backflow compliance belong in the same operational conversation.
Primary keyword: commercial building water use statistics
Key Takeaways
EPA WaterSense says commercial and institutional facilities account for 17% of public-water withdrawals in the United States. For property managers, that benchmark matters because it reframes water as a real operating resource instead of a background utility line item. If a portfolio already tracks electricity, gas, and maintenance tickets closely, water should sit in the same management stack.
The benefit of using a national benchmark is that it gives internal teams a common starting point. You do not need a perfect submetering program on day one to know that leak response time, fixture performance, irrigation losses, and protected assemblies deserve attention. The 17% figure is a strong reminder that water is large enough to manage on purpose.
Backflow testing belongs in the same conversation because commercial properties often have multiple protected systems running at once. Domestic service, irrigation, fire lines, cooling or process water, and tenant improvements can all affect how a building manages water risk. A team that only looks at monthly consumption can miss the compliance and contamination side of the picture.
That is why strong facility workflows connect the benchmarking conversation to field work. When a site reviews water use, it should also review whether assemblies are accessible, whether any failed tests still need corrective action, and whether recent plumbing or tenant work changed the risk profile of the building. Good water management is operational, not just analytical.
The most useful commercial reviews are not generic. They combine resource visibility with the parts of the site that create service calls, deadlines, or avoidable exposure. For most portfolios, that means leak visibility, documentation discipline, and protected-system follow-through.