7 Solar Referral Materials for Roofing, HVAC & Electrical

A roofer finds a customer already thinking about the roof’s next twenty years. An HVAC contractor hears that a heat-pump project may change the home’s electricity use. An electrician sees a service record that the customer wants a solar company to review. Those are useful moments, but usefulness disappears quickly when a partner guesses at system size, promises savings, forwards personal information without a clear introduction, or hands the customer a brochure nobody owns.

The partner does not need to become a solar salesperson. The partner needs a small, controlled set of materials that makes the next step easy and keeps technical, commercial, safety, and approval decisions with the people who own them.

This article covers referral-only materials for roofing, HVAC, and electrical partners. The solar career transition guide covers workers who want to learn solar and take on solar duties. The solar partner enablement checklist covers the larger relationship, including agreements, data access, training, commercial mechanics, launch gates, and operating review. Keeping those jobs separate prevents a seven-piece referral kit from turning into an implied license to design, sell, or install.

The framework is written for multi-jurisdiction solar businesses. It is not legal, privacy, advertising, contract, licensing, engineering, electrical, structural, HVAC, roofing, safety, permitting, utility, tax, financing, warranty, or site-specific advice. Responsible reviewers must adapt the materials to the partner’s work, the customer relationship, the market, and the current project.

What should solar referral materials help a trade partner do?

Solar referral materials should help a trade partner recognize a possible customer need, describe the next step accurately, obtain an authorized introduction, transmit useful observations, and leave every solar conclusion with the solar team. The pack should also show what the partner may not say, what information may be shared, who responds, and when to escalate without inventing an answer.

Confidence in this context means knowing the boundary, not sounding certain about the project. A roofing partner can recognize that roof timing matters without deciding whether the structure is suitable. An HVAC contractor can flag a planned equipment change without predicting a solar array. An electrician can identify a customer-approved record without deciding what the authority or utility will accept.

The U.S. Federal Trade Commission’s advertising and marketing guidance says advertising claims must be truthful, cannot be deceptive or unfair, and must be evidence-based. It also notes that specialized products or services may face additional rules. That is U.S. federal business guidance, not a complete referral-partner compliance plan. The operating lesson is still direct: every customer-facing statement in the kit needs a source and an owner.

The FTC’s home-solar consumer guidance tells consumers to know what they are getting before agreeing and to compare detailed written bids with specific system and cost information. A trade partner’s one-page explainer is not that bid. It should make that distinction visible instead of compressing an eventual assessment, design, proposal, contract, installation, inspection, and utility process into “we can get you solar.”

Treat the materials as controlled operating records. Each item should carry:

• a document name and identifier;
• the partner roles and markets where it applies;
• an effective version and review date;
• the content owner and approving reviewers;
• permitted use and prohibited use;
• a correction or withdrawal route;
• the destination for questions and exceptions.

Without those controls, a PDF can remain in a truck, shared drive, or text thread long after an offer, contact, claim, or process has changed. The partner may think they are following the program while the solar company thinks the old material was retired.

Which seven solar referral materials belong in the trade-partner kit?

The kit needs seven distinct materials: a role-and-authority card, plain-language solar explainer, fit-and-trigger card, trade observation sheet, approved conversation guide, permissioned introduction form, and status-and-escalation map. Together they control recognition, explanation, observation, permission, transfer, and follow-up. Combining them into one brochure usually hides the exact boundary a partner needs in the moment. Each one should solve one repeatable partner task.

Use this map before building the documents:

1. Role-and-authority card

Make the first material short enough to use during a service call. It should state the partner’s role in one sentence, then list allowed actions, prohibited actions, and escalation triggers. “Referral partner” is too vague unless the card translates it into verbs.

Allowed actions might include offering an introduction, sharing the current solar explainer, recording customer-approved contact details, and transmitting observations collected during authorized trade work. Prohibited actions might include quoting a system, selecting equipment, estimating savings or production, interpreting incentives, accepting a solar contract, promising a site visit, deciding structural or electrical suitability, or speaking for an authority or utility.

Do not copy the same card across every partner tier. A referral-only roofing company and an electrical subcontractor working under a separate scope may have very different authority. This article addresses the referral-only case. The solar partner program guide covers broader program structures; its tiers and compensation terms should not be smuggled into this card without agreement and review.

Add a bright-line escalation route for the predictable awkward moment: the customer asks a good solar question that the partner cannot answer. Give the partner a sentence such as, “I can connect you with the solar team that reviews that from the property and project records.” A boundary is easier to keep when it comes with a useful next action.

2. Plain-language solar next-step explainer

This material answers what the customer can expect after saying yes to an introduction. It should name the solar company, relationship to the trade partner, initial contact method, information requested first, early assessment purpose, likely decision points, and the difference between an early conversation and an approved project.

Use states rather than a perfect timeline. A practical sequence might include introduction received, contact permission confirmed, basic fit reviewed, source information requested, preliminary assessment prepared, qualified review completed where applicable, proposal discussed, contract decision made, project work planned, external steps tracked, and customer handoff completed. Not every project uses every state, and the order may vary.

The U.S. Department of Energy’s Homeowner’s Guide to Solar says there is no universal solar solution and identifies roof age, tree cover, size, shape, and slope among factors consumers may need to consider. Those are reasons to describe assessment, not reasons for a partner to judge a property from the driveway.

Avoid “easy,” “approved,” “ready,” “free,” “guaranteed,” “no-cost,” and fixed-timing language unless the responsible owner has documented exactly what the term means and qualified reviewers have approved its use in that market. Give the explainer a visible line stating that design, pricing, production, savings, financing, incentives, permitting, installation, and approval depend on the live project and responsible reviews.

3. Fit-and-trigger card

A trigger card helps the partner notice when an invitation may be relevant. It is not a secret qualification score. Use observable events and customer-stated needs rather than demographic shortcuts, property assumptions, or technical conclusions.

Roofing triggers can include a customer asking how solar relates to a planned reroof, requesting a coordinated conversation, or wanting a solar professional to review available roof documents. HVAC triggers can include a customer asking about solar alongside planned electrification, new equipment, load changes, or resilience. Electrical triggers can include a customer requesting review of service information, planned panel work, EV charging, storage, or another documented electrical change.

The card also needs a “do not refer yet” or “ask the program owner” route. Examples include no customer interest, no permission to share contact details, an address outside the current service area, a concern involving an active complaint, a request for technical assurance, or a conflict with the partner’s own scope. These are authored workflow categories, not universal rejection rules.

Keep the full qualification decision with the solar team. The partner should never promise that a trigger means the customer qualifies, the roof works, the service is adequate, the economics are favorable, or a project will be approved.

4. Trade observation sheet

The observation sheet captures context the partner already encountered during authorized work. It should never send someone back onto a roof, into equipment, or near electrical work merely to improve a referral. The sheet needs separate fields for customer statements, partner observations, source documents, photo references, unknowns, and inferences that require review.

Ask for provenance. “Roof appears old” is vague and blends observation with judgement. A better record identifies what the customer stated, what document was available, what area was observed during the roofing scope, and who must assess any solar implication. “Customer says roof was replaced in 2018; invoice offered for later upload” preserves the source without certifying the roof.

OSHA’s solar-energy hazard resources include electrical work, falls, lockout/tagout, heat and cold stress, personal protective equipment, and crane or hoist safety topics. That list does not establish the safe-work plan for any project. It does support a firm referral boundary: collecting extra solar data must not expand the partner’s authorized task, access, training, or safe-work process.

Include a stop field: “Information was not collected because access, permission, scope, evidence, or safe-work conditions did not support collection.” Missing information should reach the solar intake as missing. A blank field is safer than a confident guess only when the blank also carries an owner and next action.

5. Approved conversation guide

Give partners an opening, three or four approved answers, and a transfer sentence. Do not give them a miniature sales script that rewards improvisation. The conversation guide should sound like the trade partner, while the claims remain controlled by the solar company.

A roofing opening could be: “Since we are discussing the roof work, would you like an introduction to a solar team that can review solar separately?” An HVAC opening could mention the customer’s planned equipment change. An electrical opening could refer to the customer’s question about solar, storage, or EV charging. Each opening asks permission and avoids implying suitability.

Build an answer library around real questions:

• Can you tell whether my home will work? “I can share what we observed within our trade scope. The solar team needs to assess solar fit from its own records and reviews.”
• How much will I save? “I cannot estimate that from this visit. The solar team can explain the inputs and assumptions used in a project-specific model.”
• Will permits be easy? “The solar team will verify the current authority and utility process for the project.”
• Can you install it? “Our role in this program is the introduction described on this card. The solar company will explain who owns each later stage.”

The Department of Energy’s rooftop-solar permitting and inspection overview describes permitting, post-installation local inspection, and utility connection, and says local rules, details, and fees may vary by jurisdiction. Keep that variation visible. Never turn a national overview into a local promise.

6. Permissioned introduction form

This form records who asked for the connection, what the partner may share, which contact route the customer chose, and what should happen next. It should distinguish permission to introduce from permission for marketing, ongoing contact, document access, photo sharing, bill sharing, or communication with another decision-maker. Qualified privacy and legal reviewers must define the actual consent and notice language.

Collect the minimum information needed for the stated next step. Typical operating fields include customer name, property identifier or address where appropriate, preferred contact route, reason for interest in the customer’s words, partner identity, permission timestamp and method, documents the customer offered, observations attached, and restrictions on contact or sharing.

NIST describes its Privacy Framework as a voluntary tool intended to help organizations identify and manage privacy risk while protecting individuals’ privacy. The framework is not a consent rule for solar referrals. The bounded lesson is useful: the handoff should name the data, purpose, actors, access, and risk treatment instead of assuming every partner may send everything it knows.

Include rejection and correction mechanics. The solar team needs a way to return an incomplete form, flag a duplicate, correct an identity error, honor a withdrawal, or route a question without silently creating a sales lead. The partner needs to know whether to contact the customer again or step back.

7. Status-and-escalation map

The final material tells the partner what happens after the introduction without exposing customer information the partner is not authorized to receive. Define a small set of partner-visible states such as received, permission check required, accepted for contact, returned for missing information, outside current scope, customer declined contact, or closed under the applicable program terms.

Do not give the partner unrestricted access to the solar CRM. Decide which state information serves the referral relationship, which information belongs only to the customer and solar team, and which commercial status the agreement requires. The same privacy, contract, and customer-experience review should govern notifications.

The map also needs named escalation reasons: customer says contact was unexpected, partner used retired material, unsupported claim was made, customer data was sent outside the route, a technical question is being redirected repeatedly, the referral touches an active complaint, or the relationship between the companies was described inaccurately.

Close the loop on material quality. If partners regularly leave one field blank or keep asking the same question, the owner should inspect the form or guide. Do not treat every exception as a training failure. Sometimes the material asks for something the partner cannot observe or uses language nobody understands.

How should the seven materials change by roofing, HVAC, or electrical trade?

Keep the seven-document structure consistent, then change the trigger examples, observation fields, prohibited conclusions, and escalation owners for each trade. A roofer sees roof context, an HVAC contractor sees equipment and load-change context, and an electrician sees electrical records. None of those views alone establishes solar suitability, design, savings, permitting, interconnection, or approval. Make every variation explicit, traceable, and reviewable.

Use one governed template with controlled trade modules:

Tailor the words, not the authority

Partners should sound like themselves. A roofer can say “roof covering” where an HVAC contractor would say “planned equipment change.” That does not mean each trade gets a different solar story. The definitions of referral, assessment, design, proposal, approval, installation, and activation should remain consistent across the program.

Use the partnership marketing guide for deciding which partner categories fit the market. Once the partner category is chosen, this kit should make the customer’s handoff feel specific to the trade without pretending the partner owns the solar outcome.

Keep existing trade work separate from extra solar collection

The observation sheet may reuse information legitimately produced during the partner’s current work, subject to permission and policy. It should not create a shadow site survey. If a solar team needs roof measurements, electrical details, usage records, HVAC schedules, photos, or access beyond the existing trade scope, the solar team must assign the right person and process.

This separation matters even when a partner has deep expertise. A licensed electrician may be highly capable, but a referral-only agreement still has a defined role. Broader work requires the correct agreement, scope, insurance, authority, project record, and qualified review. The career-transition page owns the question of what skills a tradesperson needs to take on solar work; this article assumes they are making an introduction.

Make unknowns useful

Each trade module should include “unknown,” “customer statement,” “documented,” “observed during authorized work,” and “requires review” values. Those labels preserve the strength of the information.

For example, an HVAC contractor may know that a customer ordered new equipment but not have a final operating schedule. An electrician may have a photo of a service label but no authority to decide the solar implication. A roofer may know the replacement scope but not the structure below. A useful referral makes those gaps visible rather than filling them with confident prose.

How should a solar company deploy and control the referral materials?

Deploy the materials by defining the referral-only role, mapping real customer moments, writing one source-backed claim library, tailoring observation fields by trade, testing permission and handoff routes, assigning owners, piloting with a small partner group, withdrawing old versions, and reviewing exceptions. A partner should demonstrate the workflow before receiving customer-facing files for live use. Access follows successful training and acknowledgement.

Use this nine-step process:

1. Write the referral-only role before the materials. Name what the partner may say, collect, send, and receive. Route legal, privacy, licensing, safety, advertising, and contract questions to qualified reviewers.
2. Reconstruct three real customer moments. Use one roofing, one HVAC, and one electrical scenario. Identify what prompted the solar question, what the partner already knew, what remained unknown, and where an introduction would occur.
3. Create the claim source table. For every sentence about the offer, process, company relationship, timing, design, price, savings, financing, incentives, permitting, or approval, name its source, owner, market, expiration, and prohibited variants.
4. Build the common seven-document shell. Keep document identity, version, owner, permission route, escalation contact, and withdrawal notice in the same location across all three trade modules.
5. Tailor observation fields by trade. Ask whether each field can be gathered during authorized work, whether the customer controls it, whether the partner can label its source, and whether the field changes the solar team’s next action.
6. Test the permissioned handoff. Run the form from customer request through receipt, duplicate check, contact, return, withdrawal, and closure. Verify who can see each field and which notification reaches the partner.
7. Run scenario-based partner review. Ask the partner to handle an uncertain roof, a planned HVAC change, an electrical-record question, a savings question, a permitting question, and an unexpected-contact complaint using only the pack.
8. Release and withdraw versions. Record which partner received which version, remove old links and print stock where practical, require acknowledgement for material changes, and retain the effective dates needed for audit.
9. Review exceptions and edit the source. Inspect returned forms, unsupported claims, missing permissions, unanswered questions, and repeated escalations. Change the material or workflow when the source of failure sits there.

The broader partner enablement checklist should govern agreement readiness, training, data access, commercial terms, launch scope, and incident treatment. The nine steps here govern only the material bundle.

Failure modes to test before release

Copy-ready trade-partner solar referral handoff card

Copy this into a controlled template. Have the responsible legal, privacy, safety, technical, commercial, and program owners adapt it before use.

TRADE-PARTNER SOLAR REFERRAL HANDOFF

DOCUMENT CONTROL
Material ID:
Effective version:
Applies to partner role:
Applies to market / service area:
Content owner:
Reviewers:
Next scheduled review:
Immediate withdrawal contact:

PARTNER ROLE
Our role is:
We may:
We may not:
Questions we transfer immediately:

CUSTOMER REQUEST AND PERMISSION
Customer requested a solar introduction: Yes / No / Unclear
Permission recorded by:
Permission date, time, and method:
Approved contact route:
Information customer approved for sharing:
Information not approved for sharing:
Other decision-makers or contact limits:

REFERRAL CONTEXT
Customer's reason for interest, in the customer's words:
Current roofing / HVAC / electrical work:
Timing stated by customer:
Documents the customer offered:
Partner observations from authorized work:
Unknowns:
Items requiring solar or qualified review:

HANDOFF
Solar-team destination:
Files or evidence attached:
Submitted by and at:
Receipt state:
Next customer contact owner:
Partner-visible next checkpoint:

EXCEPTIONS
Unexpected-contact concern:
Unsupported claim concern:
Wrong or retired material used:
Data correction or withdrawal request:
Technical, safety, legal, privacy, or complaint escalation:

The card deliberately contains no project score. A “good” referral is one the solar team can handle accurately and lawfully under its process, not one a trade partner has pre-sold.

Illustrative example, not a customer case

During an authorized rooftop-unit replacement discussion, an HVAC contractor hears the property owner’s plan to electrify another building system next year. The owner asks whether solar could help. The contractor uses the role card and says they can offer an introduction, while the solar team will assess the property, energy information, design, and commercial questions.

The trigger card identifies a customer-requested conversation and a planned load change. On the observation sheet, the contractor records the equipment project and timing as customer statements, lists the documents the customer offered, and marks future energy use as unknown. The contractor does not estimate an array or describe the roof as suitable.

The owner approves an email introduction and allows the contractor to share the current equipment schedule, but not utility bills. The permissioned introduction form records that boundary. The solar team acknowledges receipt, asks the customer directly for any later energy information, and gives the partner the allowed state: accepted for customer contact.

If the customer asks the contractor for a savings figure the next day, the approved conversation guide routes the question to the solar team. The example does not establish that the property is suitable, that the planned equipment will produce a particular load, or that solar will deliver a particular financial outcome.

Where can software support solar partner referral materials?

Software can support document versions, intake fields, source labels, permission records, assignments, design inputs, proposal outputs, and handoff status. It cannot authorize a partner, obtain valid consent by itself, inspect a site, choose safe work, decide what a trade license permits, approve a customer claim, or replace engineering, authority, utility, legal, and privacy decisions. The accountable owner still makes decisions.

Start outside the software. Define the partner role, data purpose, material owner, claim sources, decision authority, and exception route. A form builder can make an unclear intake easier to submit, and an automated message can distribute an old promise faster. Configuration should follow the controlled process.

Within the solar team, connect accepted referrals to the current project record. A solar designing workspace can support the controlled design side of that handoff. Keep customer statements separate from partner observations and later solar-team findings. Preserve the source and date for roof, electrical, HVAC, bill, equipment, design, and commercial information. When one of those inputs changes, decide which customer-facing and partner-facing materials must be revised.

SurgePV supports 3D roof modeling, solar array layout, shading analysis, energy-yield and financial modeling, electrical workflow, bill-of-materials output, and proposal generation. For a partner-originated opportunity, the solar team must still verify every input it accepts and decide which output is ready for customer use. Results depend on source data, assumptions, equipment models, configuration, and review. SurgePV does not replace approval by the responsible engineer, authority, lender, insurer, or utility.

The preliminary roof-layout guide explains why an early layout needs its source and review boundary. That same discipline applies when a partner receives a customer-safe visual or document: label the stage, assumptions, purpose, owner, and next review. Do not turn a preliminary artifact into proof that a project is final.

SurgePV does not manage every partner agreement, permission, complaint, payment, training record, field visit, or customer communication channel. Use the systems and accountable owners required for those jobs. If a guided walkthrough would help, bring the handoff fields and one representative referral path so the demo can stay grounded in your actual process.

Seven good materials do not make a partner a solar expert. They make the referral boundary usable under pressure, when the customer asks a reasonable question and the trade partner needs a truthful answer, a clean handoff, and a person who will take responsibility from there.

Frequently Asked Questions

What should be in a solar referral partner kit?

Include a role-and-authority card, plain-language solar explainer, fit-and-trigger card, trade observation sheet, approved conversation guide, permissioned introduction form, and status-and-escalation map. Give every item a version, owner, review date, market boundary, and withdrawal route. Keep commercial terms and broad partner governance in their own controlled records.

What can a roofing partner record for a solar referral?

A roofer can record customer-stated interest, roof covering and area observed during authorized roofing work, known reroof scope, visible obstructions, available documents, photo references, and access constraints. The partner should label observations and customer statements separately. Structural suitability, remaining roof life, attachment design, waterproofing method, solar fit, and code conclusions require responsible review.

What should an HVAC contractor ask before referring a solar customer?

Ask whether the customer wants a solar conversation, which property and decision-makers are involved, whether planned HVAC or electrification work may change energy use, when that work is expected, which bills or equipment records the customer is willing to share, and how the customer prefers to be introduced. Do not predict solar size, savings, or equipment compatibility.

Should an electrician estimate solar suitability for a referral?

A referral-only electrician should stay within the role defined by the partner agreement and applicable rules. They can transmit customer-approved service information or documented observations from authorized work. Solar capacity, interconnection, code, upgrade, design, and approval conclusions belong to the responsible solar, electrical, engineering, authority, and utility roles for the live project.

How often should solar referral materials be reviewed?

Set a scheduled review and immediate change triggers. Recheck materials when the offer, service area, intake requirements, contact route, product scope, claim library, privacy process, partner agreement, authority guidance, or escalation owner changes. Remove superseded copies, record the effective version, and require acknowledgement when a change affects what partners may say, collect, or send.