An uploaded identity or lease document proves only what was submitted; it does not prove account creation, deposit treatment, or live service.
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 |
|---|---|---|
| Applicant | Name, ID type, contact, and authorized-party evidence | Ties the request to one person |
| Occupancy | Service address, move date, ownership or signed lease record | Documents the claimed relationship |
| Financial step | Deposit, reference, waiver request, receipt, and balance | Avoids assuming waiver approval |
| Submission | Channel, timestamp, confirmation, and attachments | Proves intake only |
| Activation | Account number, service class, effective date, and first bill | Establishes the final state |
What the official records establish
The Start Your Gas or Utility Service from City of Clearwater supports identity, occupancy, ownership or lease, deposit, reference, and intake fields for starting service. Submitting evidence does not establish activation or a deposit waiver.
The Pay My Bill from City of Clearwater supports account access, billing inquiry, payment, and service-order starting routes. The account record must identify which Clearwater service and action it covers.
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 publish personal identifiers. A reference, deposit payment, or submitted request does not establish service territory or activation.
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 privacy-conscious activation ledger that links required proof to the later account, deposit, and service-state records without treating intake as completion.
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.