Start a Duke Energy Florida Solar Application With One Verifiable Project File

Confirm Duke serves the exact meter

A St. Petersburg or Orlando mailing address does not establish that Duke Energy Florida serves the property. Read the provider name on a current bill and record the service address, account-holder name and available meter identifier exactly as shown. Keep mailing address and installation address in separate rows when they differ. Do not send utility login credentials to a contractor or enter them into a public form.

Build a private identity worksheet with four columns: field, current source, value and unresolved difference. If the proposal abbreviates the owner name, uses a parcel address that differs from the utility record or references a meter that was recently exchanged, mark the issue for the account holder and utility to resolve. Do not edit an older utility document so that it appears to have been issued for the current project. Origin can organize proposal questions, but Duke controls its account and interconnection records.

Determine the published tier without hiding the inputs

Duke currently describes Tier 1 as 10 kW and less and Tier 2 as larger than 10 kW and under 100 kW. [1][2] Ask the responsible designer which project rating Duke uses for the proposed configuration and show the underlying module, inverter and storage equipment. Annual production in kWh is not the same quantity as a power rating in kW.

Hypothetical example: one proposal headline says 10.2 kW, while the equipment schedule shows module DC capacity and inverter AC output as different values. Do not choose the lower number merely to obtain a preferred tier label. Preserve both calculations, the equipment pages supporting them and the designer’s explanation of the application value. If a design sits on a boundary or includes existing generation, ask Duke how the complete project should be classified. This example teaches document control; it does not classify a real system.

Create one controlling design record

Give each proposal version a date and a short identifier. For that version, collect the signed scope, module and inverter schedule, battery equipment if present, one-line diagram, site or array plan, proposed system rating, financing or lease scope and the application pages the installer intends to submit. The same equipment should be recognizable across every record.

Use a comparison table with one row per document and columns for system rating, module count, inverter model, storage model, revision date and open question. Mark a missing item as not provided. Do not make a clean-looking packet by copying a model number from one document into another; have the party responsible for each record correct its own version. The goal is traceability between what the homeowner accepted and what the utility is asked to review.

Record who may submit and who must answer

Write down the account holder, property owner, contractor, design professional where applicable and the person managing the Duke submission. A contractor may prepare and transmit project records without becoming the issuer of a Duke decision. The account holder should know what is being submitted in their name and how to receive status or correction notices.

Keep a simple responsibility log: action, owner, due date, evidence and status. Examples include confirming account identity, completing the equipment schedule, answering a utility correction and updating the permit set. A verbal promise that somebody is handling the file is not a durable status. A submission confirmation proves transmission; it does not establish that Duke found the package complete or accepted the design.

Track corrections as versions rather than replacing history

Save the original submission, confirmation, utility reference and every correction request. When a response changes the equipment, rating or drawing, create a new dated version and identify what it supersedes. Do not delete the earlier packet; it explains why the project changed and helps prevent an installer from using a superseded plan.

At each status check, ask three questions: which version is under review, what exact item remains open and who owns the next documented action? Florida’s interconnection rule establishes the statewide framework, but Duke’s current process and account-specific review determine the project file. [3] Origin Direct can compare the proposed project and surface missing scope. It cannot promise a utility decision, approval date, bill outcome or property-specific installation price before verification.

Primary sources

1. Duke Energy: Net Metering Tier 1 Interconnection Process

   Checked October 21, 2026. Duke currently labels Tier 1 as projects 10 kW and less. Confirm the applicable Duke Energy Florida process, rating basis and current documents for the actual account and design.

2. Duke Energy: Net Metering Tier 2 Interconnection Process

   Checked October 21, 2026. Duke currently labels Tier 2 as projects larger than 10 kW and under 100 kW. Confirm current insurance, application and project requirements directly for the account.

3. Florida Administrative Code Rule 25-6.065: Interconnection and Metering of Customer-Owned Renewable Generation

   Checked October 21, 2026. Florida Department of State identifies this as the latest final adopted version. Utility forms, tariffs and project-specific review still control the actual submission.

Planning examples and questions are Origin’s editorial guidance, not a property-specific diagnosis, engineering design, tax determination or promise of savings. Manufacturer and utility references do not imply an affiliation with Origin.

Related guidance

• Reconcile the Duke equipment record
• Track local and utility closeout
• St. Petersburg project planning