A start request, name change, transfer of responsibility, stop request, final bill, and returned deposit are different account events.
The practical answer is to keep each decision in its own record. Start with the exact address, vehicle, material, or project; identify the authority; then preserve the source-dated result beside the scope it actually covers.
Build this evidence ledger
| Record | What to capture | Why it matters |
|---|---|---|
| Authority | Service address, provider confirmation, service class | Establishes the right utility |
| Opening | Application, identity/occupancy evidence, deposit, start date | Creates the initial state |
| Change | Name, responsible party, mailing, service, and effective-date record | Preserves account history |
| Closing | Stop request, meter/read context, confirmation, and final-service date | Separates request from closure |
| Settlement | Final bill, payment, deposit credit/refund, and zero-balance record | Documents financial closeout |
What the official records establish
The Pinellas County Utilities Policy Manual from Pinellas County, Florida supports account establishment, deposits, name changes, final billing, and unauthorized-service policy. The current policy manual controls only Pinellas County Utilities accounts.
The Billing and Rates from Pinellas County, Florida supports the live county utility account, start-service, billing, and rate routes. The topic page is an intake router, not proof that an account action completed.
These records should be read together only through their stated roles. A registration does not become a permit; a permit page does not establish physical condition; a rate table does not classify a private event; and a material list does not authorize an unlisted load.
Keep the boundary visible
Do not infer provider territory, deposit eligibility, unauthorized use, or a zero balance from a form submission. Use the current policy for the exact account.
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 exact address, authority, and current official intake route.
- Save the source page, form, or portal result with its access date.
- Record the application or request separately from review, payment, and issuance.
- Attach every correction, inspection, response, and status change to the same identifier.
- Close the ledger only with the responsible authority’s final record.
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-08-30. We assigned each source a limited job, compared its fields, and produced the 5-row ledger above. The original contribution is a lifecycle chronology that prevents opening, responsibility changes, service termination, final billing, and deposit disposition from being merged.
This guide does not decide jurisdiction, eligibility, permit need, code compliance, engineering, price, approval, inspection outcome, utility responsibility, or a private dispute for a particular property.