In unincorporated Hillsborough County, “residential solar permit” is not one complete description. The County’s current checklist routes a roof-mounted photovoltaic system to an Electrical Trade permit and a ground-mounted system to a Residential Miscellaneous permit. That first choice changes the file that follows.
This guide is limited to the County permitting authority. A Tampa, Plant City or Temple Terrace address may use a different building office. Utility interconnection and permission to operate are also separate from the County permit.
Put the authority and mount type at the top
Start the project record with two confirmations:
- The parcel is governed by Hillsborough County rather than a municipal permitting authority.
- The proposed array is roof-mounted, ground-mounted, or a mixed scope that the County has classified in writing.
Do that before comparing proposals. A contractor’s statement that “permits are included” does not identify the filed authority, permit type, application number, or accepted scope.
Roof and ground files share a core, then diverge
The County’s Solar Photovoltaic System Checklist identifies common design records: signed and sealed plans, structural and electrical information, a one-line or three-line drawing, array electrical values, grounding information, and data for major components. Modules and inverters belong in that record; batteries and charge controllers belong there when they are part of the proposed system.
The mount-specific fields differ:
| Record | Roof-mounted system | Ground-mounted system |
|---|---|---|
| Permit type | Electrical Trade | Residential Miscellaneous |
| Structural context | Roof loading, wind loading, access or pathways, and setbacks shown in the plans | Support design plus placement on the parcel |
| Site evidence | Roof and building plan fields | Scaled plan showing boundaries, structures, setbacks, easements, conservation or wetland areas, trees, and work location |
| Conditional reviews | Structure, wind region, building type, fire access and equipment conditions as applicable | Those conditions plus site, tree and special-flood-hazard-area questions as applicable |
The table is an indexing aid, not a design specification. It shows where a proposal needs a matching document; it cannot say whether that document is adequate.
Use a twelve-field handoff ledger
Carry these entries from proposal to application and closeout:
- Authority: County jurisdiction evidence for the address.
- Permit type: the County route tied to the mount type.
- Property identity: owner, address, parcel, building type and any community context.
- Applicant: licensed contractor identity or documented owner-builder route.
- Structural plan: signed/sealed material and the scope it covers.
- Electrical plan: diagram, conductor, grounding and related design fields requested by the County.
- Array: layout, values, access and setback information.
- Components: exact modules, inverter and conditional battery/control equipment.
- Site: ground-mount boundaries, easements, protected areas, trees and location.
- Special conditions: manufactured-home, wind, flood, fire-access or other reviewer flags.
- Issued permit: number, approved scope, accepted plan set and conditions.
- Inspections and closeout: requested inspection, result, correction history and final record.
Versions matter. If a module, inverter, battery, array position or mounting design changes after filing, log the change and ask whether revised plans are required. Do not let an updated sales sheet silently replace the accepted permit documents.
Owner-builder and commencement records are separate gates
The checklist identifies a recorded, certified Notice of Commencement before the first inspection. If the owner is acting as contractor, the County’s Owner-Builder Permit Requirements add a disclosure and owner participation steps. Neither document proves that the applicant qualifies or that the work passed inspection.
For a contractor-led project, record the exact legal name on the proposal, permit and license evidence. For an owner-builder filing, record the County’s actual determination and the signed disclosure rather than assuming ownership alone creates eligibility.
An inspection request is not an inspection result
The solar checklist names a rough-in stage and refers to a virtual route. The County’s Virtual Inspections page sets the general submission process, but project-specific eligibility still has to be confirmed.
Keep four separate entries:
- requested inspection type and date;
- whether the County accepted an in-person or virtual format;
- result and written correction items; and
- final/closeout status in the permit record.
After County closeout, preserve the utility interconnection and permission-to-operate records in a separate section. A permit, a passed rough inspection and a utility application each answer a different question. None should be used as shorthand for the others.