Answer
Use six visual roles in a solar proposal: identify the site, explain the proposed array, show constraints, describe modeled production, compare financial assumptions, and map the next steps. Give each visual a source, project version, caption and status. Keep units and assumptions visible, and distinguish a sales concept from engineering release, external approval or a guaranteed outcome.
A proposal visual should help a buyer make one decision. Use six roles: identify the site, explain the proposed array, show constraints, describe expected production, compare the financial assumptions, and identify the next project steps. A clear image needs a caption, source, project version and status; visual polish does not establish technical approval or a guaranteed return.
SurgePV publishes this editorial checklist and sells solar software. These visual roles are a suggested communication method, not evidence that every software platform creates or validates every output.
Start with the buyer’s current decision
A homeowner deciding whether to proceed needs different detail from a designer releasing construction documents. Record the buyer’s objective and the proposal’s intended use before choosing images. Separate a preliminary roof-fit discussion from equipment selection, contract acceptance, engineering release, permitting and interconnection.
The Department of Energy homeowner solar guide provides U.S. buyer context for evaluating suitability, installers, financing and the purchase process. Local requirements and contractual responsibilities still control the actual project. Do not present a sales illustration as an official approval stage.
1. Show the property and proposed project area
Use an authorized site photograph, aerial view or diagram that lets the reader identify the relevant building and surfaces. Mark the roof zones being considered, orientation and any boundary needed to understand the scope. Redact personal or account information that is not necessary for the decision.
Label the imagery source and capture date where available. A recent screenshot can contain older underlying imagery; do not use its export date as the observation date. If part of the roof or obstruction is unclear, name the missing observation and who will confirm it.
Useful caption: “Preliminary project area on the west roof plane; underlying image date recorded in the project file. Roof condition and electrical service are not established by this view.”
Acceptance check: Can the buyer identify which roof is included and distinguish it from adjacent or excluded areas? If the image depicts a different property or a generic example, label that prominently rather than implying it is the proposed site.
2. Present a readable array layout
Show the proposed module positions without hiding the roof geometry beneath decorative rendering. Include the equipment basis, module count, DC nameplate capacity and relevant design revision. Keep units clear: installed kW or kWp is power capacity, while modeled annual kWh is energy.
Distinguish a sales concept from an engineering or installation issue. Indicate excluded surfaces and unresolved choices. If the buyer is choosing between options, use the same scale and viewpoint so a larger image does not make one option seem larger or better.
Illustrative arithmetic: Twelve assumed 400 W modules total 4,800 W, or 4.8 kW DC nameplate. This count does not establish annual production, inverter compatibility, usable roof area or structural suitability.
Acceptance check: Does the count and equipment basis match the proposal schedule? If equipment changes, update the linked layout, model and commercial assumptions instead of changing the headline alone.
3. Explain shade, access and other constraints
Use an annotated roof view or a readable shade illustration to explain why some areas were used or excluded. Identify the obstruction, modeled or observed basis, dates or periods represented, and the review still required. Use our guide to explaining solar access visually for that specific communication task.
Keep different concepts separate. A sun-path drawing describes solar position. A geometric shade view shows obstruction relationships under its assumptions. An annual energy-loss result needs the relevant production and electrical model; a dark patch in one image is not itself an annual loss percentage.
Access paths, setbacks, equipment clearances and roof-use constraints should show their source and review status. Do not reuse one jurisdiction’s dimension as a universal rule. If field evidence contradicts remote imagery, resolve or clearly flag the discrepancy before releasing a later-stage package.
Acceptance check: Can the buyer explain the main constraint without treating a modeled view as a field survey or approval?
4. Show production with its assumptions
Use monthly modeled energy bars or a suitable time-series chart to explain seasonality. Name the modeled design, units, source period or weather dataset, method and major loss assumptions. Identify whether the output is a modeled scenario, measured history or a contractual guarantee; these are different claims.
PVWatts estimates grid-connected PV production from inputs. It is an example of an estimation method, not support for an unexplained result from a different model. Use the actual method and inputs behind the proposal.
If electricity demand is shown on the same chart, use consistent periods and boundaries. Monthly production and demand totals do not establish simultaneous self-consumption; interval timing matters. Battery charging, losses and discharge need separate accounting where storage is included.
Acceptance check: Do monthly values sum to the displayed annual value within stated rounding, and does the output belong to the displayed equipment and layout revision? Use a sensitivity range only if it was actually calculated; do not decorate a single scenario with an invented uncertainty band.
5. Compare money on the same basis
Use a compact table rather than a large savings number with qualifications hidden later. Separate installed price, grants actually applicable, financing, recurring costs, export value and projected avoided purchases. Identify the currency, tax basis, tariff date and ownership structure.
| Comparison field | What the buyer needs to see |
|---|---|
| Initial cost | Quoted scope, exclusions and applicable tax basis |
| Incentive | Eligibility, amount, timing and source |
| Electricity benefit | Timed avoided imports and export treatment |
| Financing | Fees, interest, term and payment assumptions |
| Operating cost | Maintenance, replacements and relevant charges |
| Payback or NPV | Defined baseline, study period and calculation assumptions |
For example, a hypothetical £10,000 net cost and £800 constant annual net saving give a simple payback of 12.5 years before changes or replacements. That is not a measured customer outcome or a discounted return. Keep a loan payment separate from a project’s payback calculation and explain how cash flows are compared.
Do not add the same solar kWh as both a full avoided retail purchase and a full export receipt. For storage, account for charging losses and the export opportunity cost of surplus PV. A comparative table should make these boundaries visible.
Acceptance check: Could a reviewer reproduce the figure from the retained inputs, and does the buyer know which assumptions could change it?
6. Map the next steps and decision owners
Show the applicable sequence as a project-specific milestone map. A preliminary review, survey, equipment confirmation, contract, engineering issue, permit decision, installation, commissioning and permission to operate may involve different owners. Their order and necessity depend on the market and project.
For each current step, name the responsible role, required input and condition for completion. Separate a target date from a confirmed booking or authority decision. “The designer will confirm the obstruction and issue a revised concept by Thursday” is a proposed handoff; it is not a promise that permitting will finish then.
Acceptance check: Can the buyer identify the next action and distinguish a completed internal review from an external approval? Use the solar design review checklist to structure the team’s release checks.
Keep the visuals usable when shared
Captions, assumption labels and commercial qualifications should travel with each visual into a PDF, email or presentation. Register the proposal issue and changes so the buyer and team can identify the current version. A downloaded file does not automatically update when the project record changes.
Do not depend on color alone to explain accepted and excluded areas. Supply readable labels, text equivalents and data tables where needed. W3C’s guidance for complex images describes ways to provide the information in charts and diagrams to readers who cannot see them.
Review a complete proposal before standardizing it
Test the six roles on a representative project, including one that needed revision. Ask a colleague unfamiliar with it to identify the site, design basis, main constraint, modeled result, financial assumptions and next action. Revise the specific visual or missing input that caused confusion; do not treat attractiveness as evidence of comprehension or conversion improvement.
| Review question | Retained evidence | Action if missing |
|---|---|---|
| Does the visual support its stated decision? | Caption and intended-use note | Narrow the claim or choose another visual |
| Are inputs and assumptions visible? | Source, date, model basis and open items | Add a clear limitation beside the output |
| Can a revision be traced? | Project issue, equipment basis and change note | Reconcile the affected outputs |
| Does the buyer know what happens next? | Role, input and completion condition | Assign a specific handoff |
Evaluate SurgePV solar proposals against these requirements on your project. Ask which outputs are supported and how revisions, units and assumptions are retained. A guided demo can help examine the workflow; it does not establish a particular closing rate, delivery speed or engineering outcome.
Practical questions
Is a proposal visual a final engineering design?
Its status depends on the actual document and release. A preliminary sales visual should state its intended use, assumptions and later engineering, field, permitting or utility checks; it must not imply those checks are complete.
What should a buyer do when proposals show different production or savings?
Compare the design, equipment, periods, weather and loss assumptions, tariffs, export treatment, cost scope and financing before comparing headline figures. Request the inputs and identify unresolved differences.
Can software remove professional review?
Software can help produce and connect outputs, but the project still needs the responsible parties to review inputs, constraints and deliverables. Demonstrate the supported workflow on representative conditions instead of assuming an automatic approval.
Which visual should appear first?
Start with the visual needed for the buyer’s current decision, often the site and proposed project area. If the site is already understood, a specific constraint or option comparison may be more useful. Keep its purpose and source clear.
Sources
Primary research and reference material used for this desk-research article.
