City of Lewisville Backflow Testing failed backflow test next steps
Use the governing utility workflow first, then move through repair, retest, and reporting in the order the utility expects.
The path to compliance
Follow these steps in order. Repair alone is not enough. The retest and the accepted report are what close the failure.
Repair device
Use a tester or repair company that fits the local utility workflow and device type.
Retest
Schedule the passing retest after repairs are complete and before the utility deadline passes.
Submit report
The corrected report and proof of acceptance are what actually restore compliance.
What the failed notice means
A failed result is not closed until the repair, retest, and accepted submission all happen. Use this page to understand the sequence before anyone treats the job as complete.
- The failure notice means the utility still considers the device out of compliance
- Repair alone does not close the file
- The passing retest has to happen before the deadline slips
- The accepted report is what actually closes the utility record
Need repair, retest, or provider coordination?
Use this when the next job is field action, not explanation. Repair by itself does not close the failure.
- Repair the failed assembly or blocked components first
- Schedule the passing retest before the deadline slips
- Get the accepted report into the utility workflow last
Do not stop at the repair
- Late reports can miss Lewisville's ten-day submission rule even if the test itself was completed.
- The City warns that not every registered tester can test every assembly type.
- Lewisville's code language includes service shutoff and fine exposure.
Support guides
Evergreen support
What a failed backflow test usually means, how repair and retest sequencing works, and where owners lose time.