If Tampa Water sends a notice to test a backflow prevention device, preserve the letter before scheduling anything. The live City page, its linked test form, and the Water Department manual publish different repair timing statements. None should be silently substituted for the instruction on the account’s current notice.
Build the file around events: notice, device, tester, test, submission, result, repair, retest, and City receipt.
Start with the notice and device identity
The City’s current backflow page tells a recipient of its named testing notice to arrange a certified-technician test within 30 days of receiving the letter. Preserve the complete notice, envelope or delivery record, received date, account/service address, contact route, due-date wording, and any device or meter identifier.
Then match the physical assembly and proposal to the City test-report fields:
| Identity field | Record to retain |
|---|---|
| Facility and service address | Notice, water-account record, and test report |
| Device type and size | Visible label and tester’s report |
| Manufacturer and model | Label photograph and report |
| Serial number | Legible label and report |
| Device location | Safe photograph and written location |
| Meter number | Notice/account record and report |
Do not merge two devices at one address or carry a serial number forward without checking it. A test for the wrong assembly does not become correct because it was uploaded.
Keep the tester check neutral
The City publishes a list for convenience but expressly says it does not recommend or endorse the listed testers or companies. It also says it does not review their skill, insurance, or quality.
Before hiring, preserve the tester’s current City registration or certification evidence, the exact assembly covered, scheduled date, price and exclusions, responsibility for SwiftComply upload, failed-device procedure, and the record you will receive. This guide does not recommend a tester.
The live page lists testing every two years for residential properties and annually for commercial properties. The Water Department manual also describes biennial residential and annual commercial testing, while allowing earlier testing when the City considers it reasonable. Use the actual City notice rather than calculating the next date from a generic interval alone.
Split test performance from test submission
Record at least these states:
- appointment scheduled;
- device actually tested;
- initial readings and pass/fail result recorded;
- customer receives a copy;
- tester submits through SwiftComply;
- SwiftComply or City shows receipt; and
- City accepts the result or identifies another action.
The live page says certified results must reach Tampa Water through SwiftComply within seven calendar days of testing. The manual assigns a seven-day return duty to the certified tester and says a failed assembly must be reported to the City within 48 hours.
Those are separate clocks from the customer’s notice. Ask for the submission confirmation; “the tester handled it” is not a receipt.
Preserve the repair conflict instead of choosing a number
The public records show four different timing statements:
| Source | Published event or instruction | Timing statement |
|---|---|---|
| Live City page | Defective device is serviced or replaced | Within 15 days |
| Linked City test form | Note about all repairs | Within 10 days |
| 2020 manual | City receives an acceptable report after a submitted report shows repair is needed | 30-day extension |
| 2020 manual | Customer has a repaired assembly tested and submits the report | Within 14 days after repair |
The manual also describes other 30-day compliance language after a noncompliant report. These provisions may begin from different events. The public materials do not give enough context to calculate one universal deadline.
If a device fails:
- save the failed report and readings;
- record when the tester notified the City;
- send Tampa Water the notice, account, device, failed-test, and form references;
- ask which exact repair and retest dates apply;
- retain the written response;
- preserve the repair scope, qualified party, date, and replacement identifiers; and
- obtain the retest report and submission receipt.
Do not delay while researching the conflict. Follow the shortest applicable instruction unless Tampa Water gives a different project-specific direction—but do not represent that risk-management choice as a legal deadline calculated by this article.
A passing result still needs a record trail
The test form has initial-result, repair-action, and final-test fields. A repair invoice alone does not show a passing retest. A passing paper report alone does not show SwiftComply submission or City receipt.
Close the file only after reconciling:
- notice and device identity;
- tester and test date;
- initial readings and result;
- failed-result notification, if applicable;
- written City timing confirmation;
- repair and replacement details;
- final readings and tester certification;
- submission reference; and
- City receipt or account status.
If the portal, tester, and City account disagree, keep all three records and ask the Field Quality contact shown on the current page to identify the missing step.
Sources and method
Local Service Ledger compared the live customer page, City-linked WAT-P-1 report, and City-hosted 2020 manual as accessed August 9, 2026. The timing table deliberately leaves the 10-, 14-, 15-, and 30-day statements attached to their sources and events; it is not a deadline calculation or compliance opinion.