The word “streetlight” hides two different workflows: a neighborhood-funded lighting request and a report about equipment already in 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 |
|---|---|---|
| Request class | New, replacement, ordinary outage, damaged pole, or downed equipment | Routes the event before contact |
| Petition area | Boundary map, owner list, plan, approximate cost, and signature record | Preserves the district proposal |
| Public action | Verification, hearing notice, objections, and BOCC result | Separates filing from approval |
| Utility event | TECO report identifier, equipment location, response, and completion | Tracks the utility handoff |
| Assessment | Parcel, tax-bill year, footage basis, and first charge | Connects cost to the correct property record |
What the official records establish
The Request a Residential Street Light from Hillsborough County, Florida supports the unincorporated-county petition, assessment, hearing, approval, and teco-installation sequence. A request for a new or replacement light is not the same record as an outage report.
The Street Light Outages from Hillsborough County, Florida supports the route for an existing-light outage and the separate damaged or downed-equipment safety boundary. The page does not create a new lighting district or approve a replacement project.
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 report downed energized equipment through an ordinary petition ledger. Do not describe a majority petition, hearing placement, or advance assessment as installation approval.
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 five-stage decision card that keeps district formation, assessment, utility outage, safety escalation, and completed installation from collapsing into one “streetlight request.”
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.