How Accurate Shading Analysis Wins More Solar Deals

Two Reps, One Roof, Two Very Different Numbers

Same house. Same south-facing roof. Two reps walk it on the same week. The first one glances at the big oak on the southwest corner, decides it is "not a big deal," and quotes a round production number that makes the payback look great. The second rep pulls the roof into a design tool, runs a shade model across the full year, sees that the oak clips the lower strings every afternoon from October through February, and quotes a number about eight percent lower. The homeowner now has two proposals on the kitchen table. One is optimistic and vague. One is lower and backed by a shade map that shows exactly which panels lose what, and when.

Here is the part that surprises reps who sell on the biggest number. The second rep wins more of these. The homeowner is getting three or four bids, and after the second conversation they can tell the difference between a sales pitch and an estimate. The lower, explained number reads as the truth. The higher, hand-waved one reads as the trap they have been warned about. Then the two systems get installed, and a year later only one of them produces what the proposal said it would. That is the whole argument for treating shade analysis as a closing tool. It wins the signature and it keeps the customer. This post is about how shade actually maps to lost output, and how you turn an honest shade number into a stronger close.

What Shade Actually Costs in Production

Shade is the single most site-specific loss on a roof. Tilt, azimuth, and weather are knowable from the location. Shade is unique to the house, the trees around it, and the stuff bolted to the roof. That is exactly why a rep cannot eyeball it and why it is the input that most often separates a proposal from reality. The Department of Energy is plain that a system's real output is governed by site conditions rather than the nameplate rating, and shade sits right at the top of that list.

The Department of Energy explains that a solar system's actual performance depends on real-world conditions including sunlight reaching the panels, temperature, soiling, and shading, rather than on the nameplate rating measured under ideal test conditions.

U.S. Department of Energy, Solar Performance and Efficiency

The trouble with shade is that it does not scale politely. A shadow across ten percent of the array does not cost you ten percent of production. Depending on how the panels are wired and whether the system has module-level electronics, one shaded module can drag down the whole series string it sits in. So a small, intermittent shadow can carve out a surprising chunk of annual kWh, and the loss lands at specific times of day and specific months rather than spreading evenly. A rep who assumes shade loss is small and linear will overstate the system almost every time there is a tree or a chimney anywhere near the roof. The error compounds because the same optimism that inflated the kWh then inflates the savings, the payback, and the financing pitch that sits on top of it. One guessed input poisons the whole proposal.

Why Shade at Noon Hurts More Than Shade at Dawn

Not all shade is worth the same. A shadow at 7 a.m. falls on a panel that is barely producing yet, because the sun is low and weak. The same shadow at 1 p.m. falls on a panel that is near its daily peak. The Department of Energy ties real output to the actual sunlight hitting the panels across the day, which is why the clock position of a shadow matters as much as its size (DOE). Lose an hour of midday sun and you lose the fattest part of the production curve.

This is where eyeballing fails hardest. A rep standing in the driveway at 10 a.m. sees a clear roof and signs off. They never see the 2 p.m. shadow the neighbor's two-story addition throws across the west plane in winter. A real model walks the sun across every hour of every representative day and records when each panel is lit and when it is dark. That timing data is what tells you whether a shadow is a rounding error or a real hit to the annual number. It also tells you something you can sell. When you can show a homeowner that their shade mostly lands in the low-value early morning, you can quote confidently and win on honesty without giving up the number.

Near Shading and Far Shading Are Not the Same Problem

Shade comes from two directions, and they behave differently. Near shading is caused by objects on or close to the roof. Chimneys, plumbing vents, satellite dishes, dormers, parapet walls, and the array's own rows shading each other. Near shade tends to be sharp, high-contrast, and predictable, and it often hits the same few modules hard. The fix is usually in the layout. Move the module, respect a setback around the obstruction, or wire that zone so a shaded panel does not pull down its neighbors.

Far shading comes from things in the surrounding landscape. Tall trees, neighboring houses, a hillside, a distant ridgeline. Far shade is usually softer at the edges and sweeps across the array as the sun moves, and it is the kind that changes most across the seasons as the sun angle drops. A deciduous tree is the hard case, because its canopy is full and dense in summer and bare in winter, which is the opposite of what a quick look in one season would suggest. You have to model both kinds. Near shade drives your layout and wiring decisions. Far shade drives your honest ceiling on how much this roof can ever make. Treat them as one blurry blob and you will get both the layout and the number wrong. A good model keeps the two sources separate so you can act on each. Near shade becomes a punch list of layout moves. Far shade becomes a frank line in the proposal about the roof's real limit, which is far better delivered at the kitchen table than discovered on a winter bill.

The Sun Path Moves All Year, and So Does the Shadow

A single satellite image is a snapshot of one sun position on one day. The sun does not hold still. It climbs high in June and runs low across the southern sky in December, and the shadows stretch and swing with it. A tree that clears the array entirely at the summer solstice can bury the bottom two rows in late December when the sun barely gets above the treeline. That is why a summer photo is the most dangerous input a rep can trust. It hides the worst months.

Accurate shade analysis models the sun path across the whole year, not one season. It accounts for how the sun's altitude and azimuth change month to month, so the December afternoon loss shows up in the estimate instead of surprising the customer on their first winter bill. The Department of Energy frames setting realistic production expectations as part of a sound solar purchase, and a year-round sun-path model is how you set those expectations honestly (DOE). A rep who models all twelve months can stand behind the annual number in a way a rep working from one bright afternoon simply cannot.

How a Shadow Turns Into Lost kWh

A shade map is only useful if it turns into kilowatt-hours, because kWh is what the customer pays for and what the meter reports. The chain runs like this. The model finds, for each panel and each hour, how much of the sky and sun is blocked. That blockage reduces the sunlight reaching the cells. The reduced sunlight cuts the panel's output for that hour. The wiring design then decides how far that one panel's loss spreads, because a shaded module in a series string can hold back the lit modules wired with it unless module-level power electronics let each panel work on its own.

Sum that across every hour and every month and you get the annual production the roof will really deliver, shade included. This is also where design choices earn their money. Reorganizing strings so the shaded zone sits on its own circuit, or specifying optimizers or microinverters where the shade is unavoidable, can recover a real share of the loss. But you can only make those calls if the model shows you where and when the shade lands. The point is not to make the shade disappear. It is to count it correctly, design around what you can, and quote the honest remainder. Independent buyer guidance pushes homeowners to question production and savings claims, so the number you hand them has to survive scrutiny (Consumer Reports).

Why the Honest Number Closes the Deal

Sales logic says the biggest production number wins. On a shaded roof, the opposite is closer to the truth. Buyers who collect several bids are pattern-matching for trust, and a lineup of proposals teaches them fast. When one rep's number is noticeably higher than the rest with no explanation, that rep looks like the outlier who is either careless or stretching. When your number is backed by a shade map, a per-panel breakdown, and a clear statement of which months lose what, you look like the one who actually studied the roof.

That shade map is your edge in the room. You can point at the oak on the screen and show the homeowner the exact afternoon hours it costs them, then show how your layout wires around it. You are no longer arguing about whose number is right. You are the only rep who brought evidence, and that is a hard thing for a competing bid to answer. The homeowner remembers who showed them the roof and who showed them a glossy rendering with a big number floating next to it. The honest number also protects the economics you are selling. Electricity prices vary widely by state and customer class, so the dollar value of every lost or saved kWh is specific to that home (EIA). Overstate production and you overstate savings and payback, and a sharp buyer comparing cost-per-watt and projected bills across bids will catch it (EnergySage). Honest shade numbers keep your whole financial story defensible.

The Year-One Call You Never Want to Get

The deal does not end at the signature. It ends about fourteen months later, when the customer has a full year of production data and compares it to the proposal. If the system beat or met its honest projection, you get a referral and a review. If it fell short because a rep waved off the trees, you get a phone call, a hard conversation, and sometimes a claim against a production guarantee. That call is expensive. It eats a truck roll or an engineering review, it sours a customer who was going to refer their neighbors, and it can put a performance warranty on the hook.

Shade is one of the quietest causes of that shortfall, because it is the input most often guessed and the one that hits in the exact months a summer-walked proposal ignored. Accurate year-round shade modeling is how you make the year-one data match the proposal. The Department of Energy is clear that real output depends on these site conditions rather than the nameplate figure, which means an honest estimate has to price the shade in from the start (DOE). When the number was honest, the anniversary is a referral event instead of a dispute. Retention and win rate are driven by the same discipline. Quote what the roof will really make.

Eyeballed vs Modeled: Where the Outcomes Split

The two approaches diverge at almost every point that matters to a deal. This is the comparison to keep in front of any rep who still thinks a quick look at the trees is good enough.

The eyeballed column wins exactly one thing. It is faster at the desk. Every other row goes to the modeled approach, and most of those rows are worth real money across a year of installs.

A Shade-Analysis QA Before You Quote

Run this short pass on every shaded roof before the number goes into a proposal. It is deliberately brief, because a checklist only helps if reps actually use it on every job.

• Shade modeled across the full year, including the low December sun, not a single season.
• Both near shading from vents, chimneys, and dormers and far shading from trees and neighbors included.
• Deciduous trees handled for both their bare-winter and full-summer canopy states.
• Time-of-day shading checked, with special attention to the high-value midday hours.
• Per-panel shade and output reviewed, not just a whole-array average.
• Wiring and string plan set so a shaded module does not drag its lit neighbors.
• Module-level electronics evaluated where shade is unavoidable.
• Final production stated as a modeled estimate with its assumptions, never as a guarantee.
• The shade map ready to show the customer during the pitch.
• Quoted kWh cross-checked against comparable installs in the same area for sanity.

How Shade Estimates Go Wrong

The misses repeat across crews and markets. These are the patterns that turn a confident quote into a year-one callback.

Walking the roof in the wrong season. A rep visits on a clear summer morning and signs off on a roof that loses its bottom rows to a low winter sun. The proposal looks great until the first January bill lands.

Trusting one satellite image. A single overhead shot freezes the sun in one position and hides how the shadow swings across the day and the year. It flatters the roof and understates the loss.

Treating shade as linear. Assuming a shadow on ten percent of the array costs ten percent of output ignores how one shaded module can hold back a whole series string. The real loss is often larger and lands at specific hours.

Ignoring the deciduous trap. Judging a tree by its summer canopy misses that a bare winter tree still throws shade and a full summer one throws much more. The worst month gets priced as if it were the best.

Averaging the whole array. A single shade factor smeared across every panel hides the two rows that are actually getting hammered, so the layout never gets fixed and the wiring never gets rethought.

Selling the number without the map. Quoting a production figure with nothing to back it leaves you defenseless the moment a buyer compares bids or questions the estimate. Buyer guidance tells homeowners to scrutinize exactly these claims (Consumer Reports).

One Model From Quote to Install

Most shade errors come from the estimate and the design living in different places. A rep eyeballs the trees for the sales number, then an engineer models the real shade later, and the two numbers do not match. By then the customer has signed for the optimistic figure, and the gap becomes a problem the install crew and the account inherit. The fix is to run the same shade model that drives the design at the moment you build the quote, so the number you sell is the number the roof will make.

That is the problem Enact's remote design is built to solve. You pull the roof into a 3D model, run year-round shading and production in the same place you build the proposal, and quote a number backed by a per-panel shade map instead of a guess, which is what keeps reps from overselling and keeps the year-one call from coming (Enact for installers). Because the shade model, the layout, and the production estimate share one source, the figure on the proposal is the figure your design uses and the one the meter reports. For larger rooftops and carports where shade from parapets, equipment, and neighboring structures gets complicated, the same year-round modeling carries into commercial projects (Enact for commercial). Accurate shade is not a back-office task. It is how you win the bid and keep the customer, and it works best when one model carries the number all the way from the quote to the roof.

Frequently asked questions

How does shade affect solar panels?

Shade cuts the sunlight reaching the cells, which lowers output, and the loss is rarely proportional to the shaded area. A single shaded module wired in a series string can drag down the lit panels around it unless module-level electronics isolate it. The Department of Energy lists shading among the real-world conditions that govern actual production rather than the nameplate rating (DOE).

How accurate is remote shade analysis?

Remote shade analysis can be very accurate when it models the sun path across the full year and accounts for both near and far obstructions, rather than relying on one satellite image. The accuracy comes from modeling every month and hour, not from standing on the roof. A workflow that runs the same shade model behind both the quote and the design keeps the number consistent from sale to install (Enact for installers).

Why does shade at midday cost more than shade in the early morning?

Midday is the peak of the production curve, so a shadow then blocks the hours when panels make the most power. The same shadow at dawn falls on panels that are barely producing because the sun is low and weak. The Department of Energy ties real output to the actual sunlight reaching the panels across the day, which is why the timing of a shadow matters as much as its size (DOE).

Does accurate shade analysis really help close more deals?

Yes, because buyers comparing several bids trust a modeled number backed by a shade map more than an optimistic figure with nothing behind it. An honest estimate also keeps your savings and payback math defensible, since electricity rates and bill savings vary widely by location (EIA). A sharp buyer comparing cost-per-watt across proposals will reward the estimate that holds up (EnergySage).

What is the difference between near shading and far shading?

Near shading comes from objects on or beside the roof, such as vents, chimneys, dormers, and the array's own rows, and it usually drives layout and wiring decisions. Far shading comes from trees, neighboring buildings, and terrain, and it sets the honest ceiling on how much the roof can produce across the seasons. Both have to be modeled, because real output depends on all the shade reaching the panels (DOE).

How can installers avoid year-one underperformance claims from shade?

Model shade across the full year before quoting, count both near and far obstructions, and present production as a modeled estimate with its assumptions rather than a promise. When the proposal already prices in winter and afternoon shade, the first year of data matches what the customer was told. The Department of Energy frames realistic production expectations as central to a sound solar purchase, which is the standard an honest estimate has to meet (DOE).

Sources

1. DOE - Solar Performance and Efficiency
2. DOE - Solar Energy Technologies Office
3. DOE - Homeowner's Guide to Going Solar
4. EnergySage - Solar Panel Cost
5. Consumer Reports - Solar Panels
6. EIA - Average Price of Electricity (FAQ)
7. Enact - Solar Design for Installers
8. Enact - Commercial Solar Software