Tampa solar dealers: define lead registration and the roof-to-install handoff
Build a Tampa dealer operating discussion around accepted opportunities, written scope, multi-trade responsibilities and customer follow-up.
Agree how an opportunity becomes an accepted project
Before a dealer team submits opportunities, confirm the approved registration process and the information needed for acceptance. Ask how existing records, duplicate submissions, customer introductions and Origin Direct inquiries are handled. Record who decides a disputed attribution and which written agreement governs that decision.
A public referral code is useful context, not proof of exclusivity or an accepted dealer relationship. Confirm the team’s approved market, services, equipment and account permissions. Ask what must happen before anyone describes Origin as the contractor for a specific customer. An introductory application does not reserve capacity or authorize representation.
Build one packet for the customer’s accepted scope
Define the required documents with the operating team: customer and property details, authorized usage records, the accepted proposal, signatures, survey information and any additional scope approvals. Identify the packet owner and the contact who answers corrections. Keep a distinction between a packet submitted for review and a packet accepted for the next stage.
If the customer also needs roofing, detach and reset work, a charger or electrical upgrades, make each responsibility visible. Do not bury a related trade inside an unexplained adder or assume another contractor has accepted it. Confirm how scope revisions are priced, presented to the customer and recorded before work changes.
Use a roof-to-install sequence with named owners
Ask who verifies roof readiness, equipment storage where existing panels are removed, attachment requirements and the point at which the solar crew may proceed. Include access restrictions and customer communication in the plan. Name the person who handles a condition that changes the roof or array scope.
City of Tampa commercial permit resources distinguish photovoltaic and roof re-covering work. [1] Confirm the actual jurisdiction and applicable category for each property. For Tampa Electric accounts, utility connection is a separate handoff. [2] Dealer schedules should show dependencies and actual statuses, rather than treating contract signing as evidence that approval or installation is imminent.
Make service and commercial terms part of onboarding
Ask who performs the welcome call, owns ongoing customer updates and handles escalation when a document or approval is waiting. At closeout, define the monitoring transfer, equipment records, warranty information and service contact. A customer should not have to guess whether the dealer or operating team owns an unresolved task.
Review redline, approved adders, splits, payment milestones, cancellations and expenses through the private account and written agreement. Distinguish a modeled commission from an approved or paid amount. Confirm capacity and supported services with Origin for the actual market. A public guide can prepare the questions; the account-specific terms determine how the dealer team operates.
Bring these questions to onboarding
- Confirm registration, acceptance, duplicate handling and escalation.
- Name the submission-packet owner and corrections contact.
- Show roofing and electrical responsibilities in the accepted scope.
- Record roof readiness, permit and utility dependencies.
- Review compensation, capacity and service terms privately in writing.
Primary sources
- City of Tampa: Commercial Permits
Checked September 30, 2026. Includes photovoltaic and roof re-covering resources. Confirm the exact property jurisdiction and applicable permit category.
- Tampa Electric: Steps to Connect
Checked September 30, 2026. Confirm current requirements for the actual account and configuration; no utility affiliation or turnaround commitment is implied.
Origin’s workflow questions are editorial guidance. Current account permissions and written agreements govern representation, compensation and project responsibility. Utility references do not imply an affiliation.