Back to Blog

The Visual-Selling Checklist for Residential Solar Consultations

Use this residential solar consultation checklist to review roof visuals, production estimates, savings assumptions, and customer questions.

Rainer Neumann

Written by

Rainer Neumann

Editorial contributor · SurgePV

Published

Answer

Use visuals in a residential consultation to answer practical questions in sequence: where panels go, what blocks them, what the system produces, what assumptions shape savings, and what happens after the buyer says yes.

A residential solar consultation needs visuals that answer the buyer’s questions without disguising what remains unknown. Keep the original seven-step sequence below: roof and usage goal, exclusions, layout, production, financial assumptions, milestones and a matching summary. Each visual should have a source, current revision and clear purpose.

This is a presentation checklist, not a site survey or engineering approval. The Department of Energy homeowner guide covers roof suitability, electricity use, installers and purchasing questions. Apply local requirements and qualified project review rather than treating an educational guide as approval of an individual system.

1. Start with the buyer’s roof and usage goal

Confirm the selected building and roof area with the buyer. Ask whether the goal is bill reduction, backup, appearance or another priority. Record planned roof work and changes in consumption. A map selection does not establish ownership, structural capacity or the right to install.

Show imagery source and observation date when available. If the date or roof outline is uncertain, state that explicitly. Let the buyer identify changes, but label their notes as user-provided until accepted by the responsible reviewer.

2. Show exclusions before the preferred layout

Mark the areas not included in the current option and explain why: customer preference, observed obstruction, provisional design assumption or a confirmed project constraint. Keep those reasons separate. Do not draw a universal setback or claim roof capacity from imagery alone.

Identify which restrictions require local authority, fire-access, structural, roofing or electrical review. A salesperson can describe the recorded review status; the visual does not supply the missing technical decision.

3. Use a legible layout and clear legend

Name the project, option and revision. Distinguish proposed modules, existing equipment, obstructions and excluded areas using labels or patterns as well as color. State whether modules are representative or selected equipment and whether dimensions are measured, inferred or provisional.

Keep a text equivalent for important diagrams. W3C’s complex-images guidance explains the use of short descriptions and fuller text descriptions for information-rich visuals. A description alone does not prove accessibility; test the actual page, file and consultation medium.

4. Explain seasonal production with its model basis

Label charts as modeled or measured, with units, period and source. Do not convert annual modeled kWh into a constant monthly or daily promise. Weather, shading representation, orientation, equipment, losses and operating conditions affect interpretation.

Distinguish system generation from grid export, self-consumption and utility import. A production chart alone does not establish how much energy coincides with household demand or whether the system supplies backup during an outage.

5. Put financial scenarios beside their assumptions

Identify consumption period, tariff source and date, import/export treatment, system price and financing assumptions where applicable. Explain which costs and obligations are included. Mark uncertain incentives as unresolved rather than silently applying a default benefit.

Do not equate annual production with bill savings. Time-based tariffs, fixed charges, export settlement and load timing can change financial results. Tax eligibility and finance terms require their own current source and qualified review.

6. Show milestones and their dependencies

Distinguish the current proposal decision from later site review, engineering, permitting, utility permission and installation. Use the actual jurisdiction and project route. State the next action, responsible role and unresolved dependency; do not turn a target date into guaranteed approval or energization.

7. Leave a summary matching the current proposal

The takeaway should identify the same option, equipment basis, model status, exclusions and financial scenario discussed during the consultation. Preserve the next review question and contact route. If an input changes, issue a clearly identified revision rather than leaving two incompatible summaries in circulation.

Copy-ready consultation check

Check Evidence to retain If unresolved
Correct building and objective Buyer selection and stated priority Clarify before presenting a recommendation
Visible exclusions Reason, source and review status Label or hold the affected option
Current readable layout Option/revision, legend and text equivalent Repair the visual or use another format
Interpretable production Model/measurement status, units and period Withhold unsupported performance language
Explainable financial scenario Current source inputs and cost boundary Obtain the missing evidence
Clear next milestone Owner and actual dependency State a conditional next action
Consistent takeaway Current proposal and summary versions Correct before reuse

Evaluate Solar Proposals against those presentation needs using a sanitized project. Confirm the offered configuration’s outputs and manual dependencies in a guided demonstration. This checklist does not establish native accessibility, automatic revision notices or a conversion advantage.

Frequently Asked Questions

Is this a final engineering design?

No. A proposal must identify assumptions and later validation steps.

Can software remove human review?

No. Professionals retain responsibility for project review and approvals.

Sources

Primary research and reference material used for this desk-research article.

About the Contributors

Author
Rainer Neumann
Rainer Neumann

Editorial contributor · SurgePV

Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.

Get Solar Design Tips in Your Inbox

Join 2,000+ solar professionals. One email per week - no spam.

No spam · Unsubscribe anytime

Book Free Demo

Choose which optional technologies SurgePV may use. Essential storage remains active for security and requested features.