Answer
Explain shading by identifying the obstruction, showing when and where its shadow reaches the proposed modules, and distinguishing sunlight loss from modeled electrical production. Compare feasible layouts using consistent assumptions, label any planned mitigation, and state which site checks remain. Present the energy forecast as an estimate; verify financial and contractual promises separately.
A homeowner should leave the shade discussion knowing which part of the proposed array is affected, what the installer recommends, and what remains uncertain. Start with their property, not a string of percentages or a promise that new electronics will solve every shadow.
The U.S. Department of Energy’s Homeowner’s Guide to Solar identifies tree cover and roof condition among the factors that can make a rooftop less suitable. It recommends a custom production estimate from an installer. The discussion below helps sales and design teams explain that estimate clearly; it does not establish the suitability of an individual home.
1. Name the object and show the affected roof area
Use the dated site photograph or model to identify the tree, chimney, adjacent building or other obstruction. Point out the proposed modules it affects. If the obstruction’s height is estimated or the imagery predates a site change, say so beside the visual.
A useful opening is: “This chimney casts shade onto this part of the proposed array. We have modeled it using the current roof geometry; the survey still needs to confirm its height.” That explains what the team knows and what it has not yet confirmed without making the customer decode a loss diagram.
Keep the current site condition separate from a proposed change. A digitally removed tree belongs in a labeled mitigation scenario until the removal is authorized and completed.
2. Explain timing before showing the annual total
Show the periods in which the shadow reaches the proposed modules, then relate them to the monthly production forecast. A screenshot at noon or on one date cannot represent every relevant season and hour.
Distinguish two different ideas: the amount of energy available in a month and the fraction lost to shading in that month. A shorter day can reduce energy even without an additional shadow. Weather and other operating conditions also affect measured output; a low-production month alone does not identify shading as the cause.
For example: “The model shows this obstruction reaching these modules in the morning during this season. Here is the monthly estimate with that obstruction included.” Avoid telling the buyer that a winter dip is always normal or always caused by the tree.
3. Define what the percentage actually measures
Solar Access describes shaded solar resource relative to an unshaded reference at the same orientation. It is not automatically the percentage of electricity the installed array will deliver. Aurora’s discussion of shaded-system design explains that Solar Access alone does not account for system configuration.
Before quoting a loss percentage, state:
| Label to clarify | Question the buyer should be able to answer |
|---|---|
| Quantity | Is this sunlight resource, electrical energy, or bill savings? |
| Period | Is the result hourly, monthly, annual, or a lifetime estimate? |
| Reference | What is the result compared with? |
| Scope | Does it apply to one module, a roof plane, or the whole system? |
| Status | Is the site geometry confirmed or preliminary? |
Aurora’s system-loss documentation separates irradiance losses from electrical and other losses. When using any platform, check its definitions and which assumptions the final production figure already includes. Do not apply the shade reduction twice.
If the customer wants to interpret the actual report fields, use our guide to reading a shade report. Keep the sales conversation centered on their design and decision.
4. Compare the layout responses without promising a cure
Show the feasible choices: move affected modules, use another suitable roof area, adjust the array arrangement, investigate permitted pruning, or retain the shaded section with its modeled consequences. Some homes may need an alternative to rooftop solar. The appropriate options depend on the property and the responsible designers’ assessment.
Microinverters and optimizers can affect electrical mismatch, but they do not restore sunlight intercepted by a tree. Discuss their modeled effect and cost in the actual design rather than describing them as removing shade.
Illustrative production comparison
Hypothetical values, not customer results: suppose a consistent model predicts 12,000 kWh/year for a defined unshaded reference and 10,800 kWh/year for the same equipment and layout with the modeled obstruction. The modeled difference is 1,200 kWh/year, or 10% of that reference. These numbers are assumed solely to demonstrate the explanation; they do not predict any particular home’s output.
The calculation is (12,000 − 10,800) ÷ 12,000 × 100 = 10%. If moving modules also changes the installed system size, the next comparison is a different design alternative, not a pure shade-loss calculation. Identify every material change.
Do not convert the 1,200 kWh difference directly into a savings promise. Its financial effect depends on when energy is used or exported, applicable tariffs, export compensation and other financial assumptions.
5. State the assumptions beside the forecast
Attach a short assumptions note to the customer-facing production estimate. It should identify the design revision, site evidence dates, modeled obstructions, weather basis, equipment and relevant loss assumptions. State any planned intervention and whether it is included in the quoted estimate.
A measured bill, a modeled annual generation figure and a contract guarantee are different evidence. If the offer contains a production guarantee, explain its written terms separately rather than treating the model as the guarantee.
Avoid burying a material unresolved tree or roof issue in small print while presenting the headline output as certain. Give the customer the existing-condition result or a clearly conditional scenario, as appropriate to the stage of the project.
6. Agree on the verification and next decision
Name the item that needs checking, the person responsible and the deliverable that will change after the check. For example: “The survey team will confirm the enclosure height. The designer will update the shade model and issue a revised layout and production forecast if that measurement changes the design.” This is a suggested communication script, not a claimed completed project.
If the array, obstruction data or equipment changes, reconcile the report, forecast and quotation before asking the customer to rely on them. Installers can use the pre-layout shading checklist to organize that technical handoff.
A concise homeowner explanation
“Here is the obstruction and the area it affects. This forecast includes the shade as modeled, plus the stated equipment and other losses. We considered these layout options, and this is why we recommend this one. These site items remain to be confirmed. If they change the design, we will show you the revised layout and estimate before proceeding.”
Evaluate the presentation workflow
When reviewing SurgePV’s shading workflow, bring a representative project and ask which analysis, visuals and report outputs are available. Check whether your team can explain the assumptions and revisions clearly. Book a demo to discuss those requirements; software presentation does not replace responsible site and design review.
Frequently Asked Questions
Does a 10% shade figure mean 10% less electricity?
Not necessarily. First establish whether the figure describes solar resource or modeled electrical energy, its time period and its reference. Electrical configuration and other losses also affect production. Do not subtract shading again from a forecast that already includes it.
Can microinverters or optimizers remove shading?
They cannot remove an obstruction or restore blocked sunlight. They may mitigate some electrical mismatch effects, depending on the equipment and design. Ask for the modeled comparison rather than a promise that shading disappears.
Is this a final engineering design?
No. A proposal must identify assumptions and later validation steps.
What should a buyer ask when two quotes show different production?
Ask the installers to reconcile the module layout, equipment, weather data, shade model, loss assumptions and reporting period. Compare the same design scope before concluding that the higher forecast is more reliable.
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.
