How to Qualify Solar Leads Before You Burn a Design Hour

Consider an illustrative morning in a sales queue. Three new inquiries arrive before lunch. One asks for an urgent proposal but gives only a first name and phone number. Another supplies a property address and an electricity bill, yet the account name and project contact do not match. The third has a clear decision, usable records, and a known request, but the site is outside the company’s active territory.

Sending all three to design feels responsive. It is actually a refusal to decide. A designer opens each record, reconstructs what sales knows, searches for the latest attachment, discovers the missing condition, and returns the request. The expensive part is not drawing modules. It is technical attention spent discovering that no design decision was ready.

Solar lead qualification should function as admission control for design. It does not decide whether a person is worthy, predict whether a deal will close, or settle technical feasibility. It chooses the next responsible state for the inquiry: admit it to a defined design class, keep it in sales discovery, hold it for evidence, or decline or refer it under company policy.

That boundary separates this guide from the sales tasks that prepare an accepted design request. Once a lead has crossed the admission gate, that article explains how sales can assemble the packet. This guide decides whether the request should cross the gate yet.

What does solar lead qualification decide before design starts?

Solar lead qualification decides the next permitted use of company attention. It identifies the customer decision, project identity, contact and data basis, service fit, evidence state, requested output, open conditions, and accountable owners. The outcome is a route with limits, not a prediction of revenue or a substitute for technical review.

Treat the qualification event as a release decision. The sales manager is releasing the inquiry into a specific work queue for a named purpose. “Qualified” without a work class is too vague. It can mean suitable for a discovery call, suitable for an early visual, suitable for technical design, suitable for a proposal, or merely worth keeping in contact. Those states need different evidence and authority.

A design-admission record should answer one sentence plainly: What may the next team do with this lead, using which evidence, for which customer decision? If the record cannot answer that, the lead may still deserve attention, but it is not ready for design.

Solar qualification also has a negative boundary. Sales can verify that an address was supplied, an account document is readable, a customer request is recorded, a service-area rule applies, or a required field remains missing. Sales should not infer roof suitability, electrical compatibility, structural capacity, system size, expected production, bill savings, equipment acceptance, permit treatment, or approval from those administrative facts.

The United States Department of Energy says in its homeowner’s guide to solar that there is no universal solar solution. The guide discusses roof and site suitability, energy use, ownership or lease context, utility rates, excess-generation compensation, and the role of a custom estimate. Those categories explain why a thin lead record cannot support a site-specific answer. They do not qualify any private project.

The release language matters because a lead can be “qualified” in one sense and unready in another. A serious buyer with a good site may still be missing the usage evidence required for the promised output. A complete form may represent a project the company does not serve. A small project may fit the operating model perfectly. Qualification should describe current readiness, not flatter projected deal size.

Which solar leads should enter design, stay in discovery, or pause?

Admit a solar lead to design only when the requested design class has a defined customer decision, identifiable project, current service fit, minimum evidence, visible unknowns, and named owners. Keep the lead in discovery when questions remain conversational. Use an evidence hold for material missing items. Decline or refer when policy or authority requires it.

Use four operating states instead of one “qualified” checkbox. Each state should have a reason code, owner, allowed response, and exit event. A fifth catchall called “other” will become a graveyard, so allow notes but keep the route itself controlled.

Admit to a named design class

Admission means the next team can begin a specified level of work. That could be an early site visual, a consumption scenario, a preliminary layout, a commercial screen, or another company-defined output. The record names the source package, known limitations, responsible reviewer, and customer-facing use.

Admission is never blanket permission to create every downstream artifact. Evidence enough for an educational visual may be insufficient for a production scenario. Evidence enough for a bounded concept may be insufficient for pricing or a customer proposal. Design receives the smallest useful assignment, not an open invitation to fill gaps.

Keep in sales discovery

Discovery is appropriate when the next useful work is a conversation rather than a design. The lead may need to clarify the decision, confirm the property, explain who participates, identify the relevant account, separate a future project from the current site, or understand which record the company needs.

Discovery should not be treated as failure. It is a productive state when the next question is known. “Follow up” is not enough. Record the exact question, why it changes routing, who will ask it, what response counts as closure, and what happens if the customer cannot answer.

Place on an evidence hold

An evidence hold is appropriate when the decision is clear but a material input is missing, unreadable, outdated, disputed, or tied to the wrong project. The hold record names the item and its consequence. It also prevents a later rep from reopening the request with the same gap hidden in a note.

Do not request every possible document. Ask only for the item required by the proposed next stage. The six inputs for a useful preliminary response provide a deeper method for tailoring an early evidence request without pretending it is a final design packet.

Decline, archive, or refer under policy

Some requests fall outside territory, customer segment, project type, company capacity, ethical policy, contact basis, or another approved boundary. The person handling the lead should use the company’s current reason and communication rules. A decline should not smuggle in a technical verdict that nobody made.

“We cannot accept this request under our current service policy” is different from “solar will not work at your property.” The first is an operating decision. The second is a technical conclusion and may be unsupported. Keep that distinction in the record and customer message.

A lead’s state should expire or reopen when its controlling facts change. New property information, a different requested output, updated usage, revised customer authority, a territory change, or a specialist finding can alter the route. Preserve the prior decision and create a successor. Editing the old checkbox erases why design acted on it.

What should sales verify before admitting a solar lead to design?

Before design admission, sales should verify the source and status of the customer decision, contact route, project identity, service fit, energy and site evidence, commercial context, requested output, and open conditions. Verification means confirming what was supplied and how it may be used. It does not mean making technical, legal, financial, property, or approval conclusions.

The word “verify” causes trouble because teams use it for both administrative checking and specialist acceptance. Split those ideas. Sales can verify that a file is present, legible, current according to its label, tied to a named account, and consistent with another supplied field. A qualified reviewer decides whether its content supports a technical or financial conclusion.

Customer decision and buying context

Start with the decision, not the desired deliverable. “Needs a proposal” describes a file. It does not explain whether the customer is comparing broad options, deciding whether to schedule a site visit, seeking internal budget permission, requesting a firm commercial offer, planning a later project, or asking for educational information.

Record the question in the customer’s language, the people involved, any decision event they disclosed, and what they believe the next output will prove. If they expect a preliminary layout to establish final feasibility, reset the output boundary before admitting work. Design should not inherit a promise it did not make.

The FTC’s solar consumer guidance identifies project-specific questions involving energy, site, roof, sunlight, shade, bids, contracts, finance, and sales pressure. That is United States consumer education, not a qualification standard. It does show why a “solar interested” label says almost nothing about the decision that must follow.

Contact basis and communication restrictions

Record how the inquiry arrived, what the person requested, which contact channels they supplied, any recorded preferences or restrictions, and the policy source the team used. Route ambiguous or regulated situations to the responsible legal, compliance, or privacy owner. This guide does not decide whether a message or call is permitted in any jurisdiction.

Do not copy consent language from one campaign into another qualification rule. Web forms, event lists, referrals, purchased leads, partner transfers, prior customers, and inbound calls may carry different records and obligations. The operating record should preserve the source instead of reducing everything to “marketing lead.”

Project and property identity

Capture the address exactly as supplied, plus unit, parcel, building, account, business, portfolio, or site identifiers relevant to the company’s work. Record the contact’s stated relationship to the project. Flag mismatches among the form, bill, property record, CRM account, and attachments rather than choosing whichever value looks plausible.

The Census Bureau’s geocoding documentation defines geocoding as taking an address and returning an actual or calculated latitude and longitude. It also documents matched-address and benchmark output. A coordinate response can help normalize a location record. It does not prove property ownership, customer authority, roof identity, service territory, solar feasibility, or design readiness.

Portfolio and commercial inquiries need an additional separation. The corporate contact, utility account, legal entity, site operator, property owner, bill payer, and project sponsor may be different parties. The qualification record does not need to resolve every contract question, but it must show which identity is known and which authority remains open.

Service fit and request class

Apply current company rules for territory, project segment, service, system type, customer class, project stage, and accepted request class. These are operating filters, not universal solar rules. Name the policy version and exception owner so a rep cannot quietly waive a boundary to keep an attractive opportunity moving.

Separate “we serve this market” from “this project is technically feasible.” The sales manager may confirm that a residential rooftop inquiry falls within the offered segment and area. That does not accept the roof, electrical service, structure, equipment, utility path, economics, or permit path.

Energy-use evidence

Record what the customer supplied, the account or meter identity shown, the covered period as labelled, file readability, known missing portions, stated load changes, and any disagreement. Do not turn a bill total or customer estimate into a system size or savings claim at qualification.

The requested stage decides what is enough. An education call may require only the customer’s stated concern. A usage-based scenario may require a defined record under the company’s modeling policy. Commercial interval data, multiple meters, demand charges, aggregation, tenant allocation, or planned operations may need specialist review before the request receives any modeled output.

Site evidence without site conclusions

Inventory supplied imagery, photos, plans, measurements, roof age statements, land information, shading concerns, known obstructions, planned construction, access notes, and previous assessments. For each item, retain supplier, date, project identity, coverage, and visible limitation.

Sales should describe what a photo shows without translating it into structural or electrical acceptance. A clear image can still omit hidden damage, dimensions, load capacity, service details, boundaries, access, code conditions, or objects outside the frame. The qualification decision may admit a limited visual while holding later technical claims.

Commercial and financial expectation

Capture the customer’s stated budget context, ownership or financing interest, proposal purpose, price expectation, requested comparison, and claims already shown to them. Do not decide affordability, lending, tax treatment, incentive eligibility, payback, savings, or contract acceptability during administrative qualification unless the company’s authorized process and evidence support that separate decision.

The FTC’s advertising guidance for small businesses says United States advertising must be truthful and non-deceptive and objective claims need supporting evidence. That general guidance does not approve a solar offer or script. It supports a simple operating rule: preserve exactly which claim the customer saw and which evidence or owner must review it.

Requested output and release boundary

Name what design is being asked to produce and how the result may be used. “Design” is too broad. A bounded educational visual, early layout, production scenario, equipment comparison, technical screen, proposal input, permit set, procurement package, and construction output carry different evidence and review needs.

The admission record should state prohibited uses too. If the request is admitted for an early concept, say that it cannot be represented as final feasibility, engineering, approval, firm production, savings, procurement, or construction direction. Put the limit beside the request, not in a distant policy file the designer never sees.

How should missing or conflicting information affect qualification?

Missing information should change the route only when it matters to the requested stage. Record the gap, consequence, owner, allowed interim response, and closure event. Conflicting information should remain visible until the responsible authority resolves it. Sensitive information should be collected and retained under approved privacy, access, and purpose rules.

A rigid completeness score makes two errors. It may reject an early education inquiry because it lacks files that the conversation does not need. It may also admit a later-stage request because every field contains something, even though several values conflict or come from an unknown source.

Use materiality. Ask what decision the next output will support, which input controls that decision, and what the company permits when the input is absent. The answer can be a hard hold, a limited output with a visible assumption, specialist review, or a different non-design response. The responsible owner defines those paths.

The W3C forms tutorial says forms should request only information required for the transaction or process. It recommends labels, instructions, validation, user notifications, correction options, grouping, and logical stages. That accessibility guidance is useful here because a qualification form should explain why a field matters and let a person correct it. It is not a legal-compliance finding for any implementation.

Data handling deserves its own owner. NIST describes its Privacy Framework as a voluntary tool for identifying and managing privacy risk while protecting individuals’ privacy. The framework is not a consent rule, law, certification, or retention schedule. Use the company’s applicable privacy and legal process to decide what lead information may be collected, accessed, shared, corrected, retained, or deleted.

A missing item should never disappear when a lead is re-routed. If the team allows an early visual, carry the gap into the design request and the customer-facing limitation. If the customer later supplies evidence, record the successor state and reopen only the conclusions it affects.

How do you build a solar lead qualification workflow?

Build solar lead qualification around one controlled admission event. Define design classes, minimum evidence, decision owners, exception routes, and customer-facing limits. Then capture source-tagged inputs, choose one lead state, release only the permitted work, preserve returned exceptions, and review real routing outcomes without converting them into unsupported sales promises.

Begin with a small set of lead states and design classes the company can actually govern. A large scoring model hides judgment behind arithmetic. A controlled route exposes who decided, why, and what happens next.

1. Define design classes before defining lead scores. Name each output design may produce, its permitted customer use, minimum evidence groups, required reviewers, and prohibited interpretations. If the company cannot describe the output class, sales cannot admit a lead to it consistently.

2. Assign authority by decision. Sales operations may own administrative completeness, a sales manager may own service-fit exceptions, design may own technical sufficiency, privacy or legal owners may govern contact and data handling, and commercial leaders may own acceptance policy. Use the company’s real roles. Do not let one “qualification owner” silently absorb every authority.

3. Capture the decision and source package. Record what the customer wants to decide, which project they mean, how the inquiry arrived, what evidence was supplied, what the company already represented, and which uncertainties are visible. Preserve original files and source dates.

4. Apply the stage-minimum evidence test. Compare the source package with the exact requested design class. Mark each required group as accepted for routing, missing, conflicting, expired, unreadable, not applicable, or pending specialist review. Administrative acceptance should not masquerade as technical acceptance.

5. Choose one operating state and reason. Admit, discovery, evidence hold, or decline or refer. Name the reason code in plain language, the next owner, allowed customer response, blocked actions, and the event that changes the state. Avoid parallel active states that leave two teams believing the other owns the lead.

6. Release a bounded request to design. Include the customer decision, project identity, design class, accepted evidence, open conditions, assumptions allowed by policy, required reviewer, due event, customer-facing limit, and return path. Link the exact artifact revisions rather than attaching anonymous copies.

7. Handle returns without restarting from zero. Design may discover that an accepted input is unusable, a site condition needs review, or the requested class cannot support the promised output. Return the named exception with its consequence and owner. Preserve the rest of the accepted packet so sales does not rebuild the request from memory.

8. Review routing evidence, not vanity totals. Examine which reason codes recur, which fields cause avoidable returns, which admission rules produce conflict, where customers abandon an unclear request, and which exceptions are waived repeatedly. Change the workflow only after responsible owners review real records and downstream effects.

The solar design request process begins after this release and carries the active revision, project evidence, open conditions, and review gates through design work. The fast first design checklist can support the receiving team’s first bounded review. Neither page replaces qualification admission.

Do not promise a universal service level in this guide. A company’s timing depends on staffing, request class, evidence, technical complexity, market, external parties, and queue policy. Measure its own stages, separate active work from waiting, and publish a commitment only when operations can support it.

Copy-ready solar lead qualification and design-admission record

Use this copy-ready operating record as a starting point. Adapt the fields, authority, privacy treatment, technical gates, customer language, and service policy to the company and jurisdiction. A field should exist because it changes a decision, protects a person, supports a handoff, or preserves traceability.

SOLAR LEAD QUALIFICATION AND DESIGN-ADMISSION RECORD

Record identity
- Lead or account ID:
- Qualification record revision:
- Created by and date:
- Current owner:
- Source campaign, referral, event, partner, or inbound route:
- Governing qualification policy and version:

Customer decision
- Customer's question in their words:
- Decision the next output must support:
- People or roles involved:
- Stated timing event, if supplied:
- Requested output:
- Customer expectation of what that output proves:

Contact and data basis
- Contact channels supplied:
- Recorded request or communication basis:
- Preferences, restrictions, or open compliance review:
- Data purpose and access owner:
- Sensitive records received:
- Applicable policy or specialist review:

Project identity
- Site address exactly as supplied:
- Unit, building, parcel, meter, account, or portfolio identifiers:
- Customer's stated relationship to site or account:
- Identity sources and dates:
- Conflicts among form, bill, account, property, or attachments:
- Owner of unresolved identity question:

Service fit
- Territory or market rule:
- Customer and project segment:
- Requested service and design class:
- Current fit disposition:
- Exception requested, owner, and decision:

Evidence matrix
- Energy-use evidence, source, date, state, and limitation:
- Site evidence, source, date, coverage, and limitation:
- Customer objectives and constraints:
- Known future changes:
- Commercial or finance context supplied by customer:
- Claims or outputs already shown to customer:
- Missing, conflicting, stale, unreadable, or specialist-review items:

Qualification route
- State: ADMIT TO DESIGN / SALES DISCOVERY / EVIDENCE HOLD / DECLINE OR REFER
- Plain-language reason:
- Permitted next action:
- Blocked actions:
- Next owner:
- Customer-facing response:
- Exit or reconsideration event:
- State expiry or review date, if applicable:

Design admission, if released
- Design class and purpose:
- Source package revision:
- Accepted administrative inputs:
- Technical review still required:
- Visible assumptions permitted by policy:
- Prohibited customer interpretations:
- Required reviewer and return path:
- Qualification authority, decision, and date:

Change history
- Changed fact or request:
- Prior state:
- Successor state:
- Affected outputs and people notified:

Keep the record beside the lead and project, not in a private sales spreadsheet. Design should be able to see why the request was admitted and return an exception to a named owner. Sales should be able to see whether a technical finding changes the customer response. Managers should be able to audit a decision without reconstructing a chat history.

Avoid turning the template into a longer form for every visitor. The public form, sales discovery record, internal qualification record, and design request can have different fields. Connect them through stable identity and source references. The personalized solar design lead-magnet guide explains the narrower visitor exchange.

Illustrative workflow: a promising lead that is not yet design-ready

This illustrative workflow is not a customer case. It contains no claimed conversion, response time, design saving, project result, or technical conclusion.

A facilities contact requests a rooftop solar proposal for one building in a larger portfolio. The request includes a street address, a recent electricity document, several roof photos, and a statement that management wants an internal budget discussion. The record looks complete enough to send to design.

Sales checks identity before routing. The electricity document names a different building within the portfolio, while two photos have no date or building label. The contact can coordinate the project but has not identified who owns the property decision or which account management intends to evaluate. The requested “proposal” could mean an early budget concept or a firm commercial offer.

The sales manager does not reject the lead and does not ask design to make favorable assumptions. The manager routes it to sales discovery with three named questions: which building and account support the budget discussion, what decision management expects from the next document, and who can confirm the site and account relationship. The existing files remain attached with their source and mismatch labels.

The contact confirms that management wants a bounded early concept for the addressed building, supplies the matching account record, and identifies the facilities and finance participants. One roof-photo date remains unknown. Under this illustrative company’s hypothetical policy, that missing date blocks a later site-specific claim but does not block a clearly preliminary concept that exposes the imagery source and open site verification.

The lead then moves to “admit to preliminary concept,” not “fully qualified.” The release names the customer decision, matching account, exact source package, remaining photo limitation, prohibited claims, next reviewer, and event that would be required before a later proposal class. Design receives a real assignment instead of a pile of promising attachments.

The example shows why qualification is a routing method rather than a character judgment. The lead was serious throughout. Its readiness changed when the customer decision and project evidence became usable for a specific output.

Where does SurgePV fit after a lead is qualified?

SurgePV can support connected project work after a company admits a lead to a defined design stage. Its verified scope includes roof modeling, layout, shading, energy and financial modeling, electrical workflow support, BOM output, and proposal generation. Qualification authority, contact permission, property verification, evidence acceptance, technical judgment, and release approval remain outside that claim.

The repository source of truth for SurgePV’s product scope lists 3D roof modeling, solar array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. Results still depend on source data, assumptions, equipment models, configuration, review, and responsible external approval.

That product fit begins after the operating decision this article describes. A company may connect an admitted project identity, source evidence, defined design class, accepted assumptions, and later outputs in one workflow. No retained first-party fact establishes that SurgePV captures lawful consent, proves an address, qualifies a customer, applies the company’s acceptance policy, chooses which lead deserves attention, or guarantees fewer design returns.

Test configured routing with representative cases before relying on it. Include incomplete forms, conflicting addresses, multiple meters, portfolio contacts, future construction, unsupported request classes, restricted communication records, service-area exceptions, changed customer decisions, and design returns. Compare the software state with the authoritative human decision and retain a manual exception path.

The product should make a decision easier to inspect, not make the decision disappear. Keep the qualification revision, project identity, source package, allowed use, open conditions, and owner visible beside the work that follows.

Frequently Asked Questions

What is a qualified solar lead?

A qualified solar lead is an inquiry routed to a defined next stage under the company’s current rules. Design-ready means the customer decision, project identity, service fit, requested output, minimum evidence, restrictions, and owners are clear enough for that design class. A lead can remain valuable while staying in discovery or on an evidence hold.

Qualification should be stage-specific. A lead may be ready for an education call, early visual, preliminary technical screen, or another bounded response without being ready for a proposal. Record the exact route rather than applying one permanent label to the person or project.

Should every qualified solar lead receive a design?

No. Qualification should route work proportionately. Some inquiries need education, a document request, site confirmation, specialist review, or a commercial conversation before design. Others may be outside service scope or unsuitable for active pursuit. The qualification record should state the route, reason, permitted response, next owner, and event that allows reconsideration.

Design is one possible next action, not a reward for filling a form. Send the inquiry to design when a named design class supports the next customer decision and the stage-minimum evidence and owners are in place.

Can sales qualify a solar site without a designer?

Sales can verify administrative and customer-supplied facts, classify their sources, and apply approved routing rules. Sales should not turn images, bills, addresses, customer statements, or form answers into technical feasibility, system sizing, production, savings, structural, electrical, code, or approval conclusions. Those decisions stay with the qualified people assigned by the company.

Write administrative status precisely. “Photo received and tied to the submitted address” is supportable when the record shows it. “Roof suitable for solar” is a different conclusion and needs the company’s required technical evidence and authority.

What should happen when a solar lead is missing information?

Record the missing item, why it matters to the requested stage, who can supply or review it, the allowed interim response, and the release consequence. Then route the lead to discovery, evidence hold, or a bounded preliminary path under company rules. Do not invent a favorable value or treat every missing item as an automatic rejection.

If the item becomes available, create a successor qualification decision and identify which restrictions it resolves. Do not silently overwrite the earlier state, because design and sales may have acted within that earlier boundary.

Can solar software automatically decide which leads deserve design time?

Software can store inputs, connect project records, and support configured routing, but no verified SurgePV claim establishes automatic lead acceptance, consent handling, property verification, technical feasibility, design approval, or sales prioritization. A company must define its admission rules, test them against real work, protect exceptions, and keep accountable people in every consequential decision.

Automation can flag a missing required field or route a known request class. The team still owns whether the rule is appropriate, whether the input is trustworthy, which exceptions apply, and what may be represented to the customer.

Admit a decision, not an attractive-looking record

A weak qualification process asks whether a lead looks promising. A durable process asks whether the next team has permission, purpose, evidence, and authority for a specific kind of work.

That shift protects good leads as much as it protects design capacity. A customer is not discarded because one document is missing. The lead receives a useful state, a named question, an owner, and a path forward. Design is not asked to discover the sales conversation hidden inside the request.

Preserve the reason behind every route. When the customer decision or evidence changes, create a successor. That history lets sales, design, operations, and the customer work from the same project state without pretending uncertainty has vanished.