Wastewater Collection Division and Prevent Blocked Drains divide the local workflow into symptom record, city report, boundary finding, private scope, resolution. Those records answer different parts of the question and cannot substitute for one another.
The working answer is the symptom record, city report, boundary finding, private scope, resolution ledger below. A property-line decision tree anchors every later repair record to the City’s documented first response.
Build this evidence ledger
| Record | What to capture | Why it matters |
|---|---|---|
| Symptom record | Date, fixtures affected, backup location, photos, safety conditions | Preserves observation |
| City report | Contact route, time, service address, ticket or confirmation | Shows notice |
| Boundary finding | Observed location, cleanout or line checked, City response | Separates public and private paths |
| Private scope | Plumber finding, proposed work, exclusions, permit question | Keeps a proposal from becoming a City conclusion |
| Resolution | City work or private repair, completion, recurrence, final ticket status | Documents the end state |
What the official records establish
The Wastewater Collection Division from City of Tampa supports the collection-system role and city maintenance boundary. The page does not diagnose a particular stoppage.
The Prevent Blocked Drains from City of Tampa supports the current blockage reporting and prevention context. Prevention guidance is not evidence of the observed cause.
Read these records only through the symptom record, city report, boundary finding, private scope, resolution fields in the ledger. Each source is evidence for its stated role and access date; it does not silently decide another authority’s stage or result.
Keep the boundary visible
A symptom, prevention list, or private diagnosis does not establish that the City main or the private lateral caused the event.
Write “not established” when a field has no reliable answer. If the scope or event changes, preserve the earlier version and record the new decision instead of overwriting the evidence chain.
Practical sequence
- Confirm the service address and the responsible municipality, county, utility, or inspection office.
- Save the current official instructions and the exact form, portal record, or notice used.
- Record intake, payment, comments, corrections, inspections, and responses as separate dated events.
- Keep private work evidence beside—but not in place of—the public record.
- Close the ledger only with the named authority’s final decision, credit, certificate, release, or status.
Before acting, revisit every live official page. The access date proves what Local Service Ledger reviewed; it does not freeze a form, rate, office route, eligibility rule, or permit interpretation.
Source and method
Local Service Ledger reviewed 2 official records on 2026-09-01. We assigned each source a limited job, compared its fields, and produced the 5-row ledger above. A property-line decision tree anchors every later repair record to the City’s documented first response.
This guide does not determine jurisdiction, permit need, code compliance, engineering, causation, utility responsibility, eligibility, fee, credit, inspection outcome, contractor quality, or a private dispute for a particular property.