Specialty & Site Support
Backflow Testing
Backflow-prevention assembly testing with service records, test-result documentation, and related compliance support for government facilities, public-sector properties, institutional sites, and other defined water-system requirements.
Defined assemblies. Documented testing. Clear results.
Service Overview
Backflow Testing Built Around the Requirement
Backflow-testing requirements vary by assembly type, device size, installation configuration, water-system use, facility location, governing authority, testing interval, access conditions, and required reporting procedures.
Azure Tide approaches each requirement by reviewing the identified assemblies, test locations, required due dates, applicable forms, service-access conditions, reporting expectations, submission requirements, and defined acceptance standards.
Service may be structured around annual or periodic compliance testing, acceptance testing, scheduled retesting, multiple-device programs, or another clearly defined backflow-prevention testing requirement.
Typical Scope Elements
Backflow-Prevention Testing Services
Depending on the assembly type, jurisdiction, and governing requirement, service may include one or more of the following testing and documentation elements.
Periodic Backflow Testing
Scheduled testing of designated backflow-prevention assemblies according to the interval and procedures identified by the applicable requirement.
Reduced-Pressure Assemblies
Testing of designated reduced-pressure-principle backflow-prevention assemblies where this assembly type is included in the facility requirement.
Double-Check Assemblies
Testing of designated double-check backflow-prevention assemblies where applicable to the installed system and governing testing requirement.
Testable Vacuum Breakers
Testing of compatible pressure-vacuum-breaker or other testable assemblies where the device type and governing requirements call for field testing.
Acceptance & Initial Testing
Initial or acceptance testing can be coordinated where the applicable scope requires verification following a new installation, replacement, relocation, or other defined system change.
Retesting
Retesting can be incorporated where a prior result, corrective action, repair, replacement, or governing requirement calls for an additional test.
Assembly Identification
Device type, size, manufacturer, model, serial number, location, or other identifying information can be recorded where required by the applicable test form.
Pass / Fail Documentation
Test results can be documented using the required pass/fail criteria, measured values, assembly information, and other required report fields.
Test Reports & Records
Required test reports, certificates, inspection forms, service records, or other supporting documentation can be incorporated according to the applicable requirement.
Multiple Assemblies & Locations
Requirements involving multiple devices, buildings, campuses, service connections, or facility locations can be structured within one defined testing program.
Failed-Test Reporting
Failed results, observed test limitations, inaccessible assemblies, or conditions preventing completion can be documented for appropriate follow-through.
Other Defined Backflow Testing
Additional testable backflow-prevention requirements can be evaluated when clearly identified in the applicable solicitation, statement of work, or facility requirement.
Testing Schedule
Periodic Testing Around Compliance Requirements
Backflow-testing schedules can be structured around jurisdictional due dates, facility maintenance cycles, assembly inventories, system changes, prior test results, and defined contract requirements.
-
Annual or Periodic Testing
Testing can be scheduled according to annual, periodic, contract-defined, or jurisdictionally established compliance intervals.
-
Defined Test Windows
Service can be coordinated around facility operating hours, water-use requirements, security access, tenant or occupant schedules, and required compliance deadlines.
-
Retesting & Follow-Up
Retesting can be scheduled following failed results, completed corrective work, device replacement, or other conditions requiring subsequent verification.
Performance Visibility
Test Reports & Compliance Documentation
Where required by the scope, backflow-testing performance can be supported through assembly records, measured test results, pass/fail documentation, required forms, and exception follow-through.
Assembly Records
Facility, device location, assembly type, size, manufacturer, model, serial number, and other required identifying information can be recorded.
Test Results
Required readings, valve or component results, pass/fail status, test date, and other test information can be documented using the applicable reporting format.
Required Forms & Reports
Jurisdictional forms, facility reports, inspection records, certificates, or other required documentation can be incorporated when identified by the scope.
Exception Follow-Through
Failed tests, inaccessible devices, missing identification, observed deficiencies, or incomplete documentation can be tracked for appropriate follow-up.
Requirement Planning
Information That Helps Define the Scope
Providing available assembly, location, jurisdiction, access, deadline, and reporting information helps clarify the backflow-testing requirement.
- Facility address, jurisdiction or water authority, and each building or service location included in the testing requirement.
- Number of backflow-prevention assemblies and available device type, size, manufacturer, model, serial number, or asset-identification information.
- Exact assembly locations, including indoor or outdoor placement, vaults or enclosures, mechanical rooms, irrigation areas, service yards, or other access conditions.
- Last test date, current due date, previous test report, prior failed results, compliance notice, or other available service history.
- Facility operating hours, access procedures, water-use restrictions, security requirements, escort requirements, and permitted testing windows.
- Required test forms, electronic reporting portal, submission process, distribution list, inspection certificate, tagging, or other documentation requirements.
- Requirements following a failed test, including notification, separate corrective work, retesting, deadlines, and documentation of subsequent results.
- Applicable statement of work, assembly inventory, photographs, plumbing or site drawings, compliance notices, previous reports, solicitation documents, and required acceptance criteria.
Need Backflow Testing?
Contact Azure Tide with the facility location, assembly information, required testing date, jurisdictional requirements, documentation expectations, and applicable requirement details.