HyreSolar

Problems

Your solar is producing less than promised: what to check

Start with the estimate rather than the equipment. It has published error bars and most people have never seen them.

Updated September 2026 · Data as of National laboratory documentation read on 3 September 2026

Written by HyreSolar Research team Research and analysis

Audited by HyreSolar Research team Data audit and fact check

±10% stated annual error on the model ±30% monthly
0% is the default assumption for snow loss And 0% for ageing
3% shading default, for an unshaded horizon Excludes your own trees

The short answer

Before concluding the hardware is faulty, find out how precise the promise ever was. The modelling tool behind a great many residential estimates publishes its own uncertainty, and its manual is blunt: "The errors may be as high as ±10% for annual energy totals and ±30% for monthly totals" for typical weather data, and "actual performance in a specific year may deviate from the long-term average up to ±20% for annual and ±40% for monthly values". A month 25% below projection is inside the stated error of the model. Its default assumptions are worth knowing too: 3% for shading, which the documentation says is for an unshaded horizon and excludes your own trees, 0% for snow and 0% for ageing. So the first question is not what is wrong with your system. It is what the estimate assumed.

The estimate has error bars, and they are published

Almost every residential solar estimate traces back to a free modelling tool from a national laboratory, either directly or through software built on top of it. It is a genuinely good tool. It also documents its own limits with a candour that never survives into a sales proposal.

From the manual, verbatim: "the results should be interpreted as being a representative estimate for a similar actual system operating in a year with typical weather. The errors may be as high as ±10% for annual energy totals and ±30% for monthly totals for weather data representing long-term historical typical conditions. Actual performance in a specific year may deviate from the long-term average up to ±20% for annual and ±40% for monthly values."

Sit with the monthly figures. A single month coming in 30% below the projection is within the model's stated error for typical weather, and a specific year can deviate by up to 40% in a month. Judging a system on one month is judging it against a number the model itself does not claim to that precision.

The manual is also explicit that this is the low-fidelity option by design: it "hides much of the complexity of accurately modeling PV systems from the user by making several assumptions", and while useful for a quick estimate, "several more sophisticated tools are available for making more accurate predictions". The laboratory names its own more detailed model as the alternative.

None of that means your system is fine. It means the comparison you are making needs a tolerance attached before it can tell you anything, and most people are comparing a real measurement against a number they believe is exact.

Attribute the numbers carefully

The PVWatts error figures quoted above come from the Version 5 manual, published September 2014, which is the version we could read in full. Later versions of the tool have shipped.

We could not reach the current documentation to check whether it restates the same figures, so we attribute them to that manual by name and date rather than to the tool in general. If precision matters to your case, the current documentation is the thing to check.

The default losses your estimate probably used

Underneath the headline number is a stack of assumed losses. The tool ships with defaults, and unless whoever produced your estimate changed them, those defaults are what your projection assumed about your roof.

Three of them deserve attention, and two are zeros.

Shading is defaulted to 3%, and it is not the shading you are thinking of. The documentation is explicit that this figure represents an unshaded horizon, and that it does not account for shading from the homeowner's own trees or nearby buildings. If you have a tree, the default assumed you did not.

Snow is defaulted to 0%. Not a small number, zero. Set that against a national laboratory's published statement that "snow-related power losses can exceed 30% of annual production" at northern latitudes, and it becomes the largest silent assumption in any northern estimate. That statement is a bounding claim rather than a typical value, and the gap between a bound like that and a default of zero is where a northern homeowner's disappointment lives.

Ageing is defaulted to 0%. The model assumes no degradation over the period. Panels degrade, and separate research puts the median field rate around half a percent a year with a mean higher than that. Over a long projection that assumption compounds.

Soiling2%
Shading3%
Mismatch2%
Wiring2%
Connections0.5%
Light-induced degradation1.5%
Nameplate rating1%
Availability3%

The default loss stack, in full

Loss categoryDefaultWhat it assumes
Soiling2%Dirt on the glass. A single national default for every climate
Shading3%For an unshaded horizon. NREL states this excludes shading from the homeowner’s own trees and buildings
Snow0%Assumed to cost nothing, anywhere, in any climate
Mismatch2%Modules in a string not performing identically
Wiring2%Resistive losses in the DC and AC runs
Connections0.5%Losses at connectors and terminations
Light-induced degradation1.5%The initial drop when new modules first see sun
Nameplate rating1%Modules not exactly matching their rated output
Age0%No degradation over time is assumed at all
Availability3%Time the system is not operating

Default system losses from the PVWatts Version 5 manual, NREL/TP-6A20-62641, September 2014. Read September 2026.

The two zeros are the ones to query. A model assuming no snow loss and no ageing will, over a long projection in a cold climate, produce a number no real system reaches. That is not a flaw in the tool, which documents all of this. It is a flaw in using its output as a promise.

What the validation study actually validated

The same manual reports a validation against nine real systems, and the headline is reassuring: the current version underpredicted annual AC energy by only 1.8%, against 11.9% for a much older version.

Read the sentence that follows it. "All of the systems considered were unshaded, and the periods during which the system was unavailable were removed from the comparison. Consequently, the loss mechanisms for shading and availability were set to zero for both models."

So the model was validated on unshaded systems, with downtime excluded, and with the two loss mechanisms most likely to affect a real house switched off. That is a legitimate way to test a model's physics. It is not evidence about what the model does on a roof with a tree and an inverter that was offline for a fortnight.

The words your monitoring and your proposal use differently

Typical meteorological year
The synthetic weather year most estimates are built on, assembled from long-run historical data. Your actual year was not this year, and the difference is inside the model’s stated tolerance rather than evidence of anything.
System losses
The stack of assumed deductions applied to the ideal output. The default total is around 14%, and two of its components are set to zero.
Availability
The share of time the system is actually operating. Defaulted at 3%. If yours was offline longer than that, the missing energy is an uptime problem rather than a performance problem, and it has a different remedy.
Derate
Any factor reducing output from the nameplate ideal. Used loosely in sales conversations, precisely in the model.
Clipping
Output lost when the array’s DC production exceeds what the inverter can convert. By design in some system sizing, and it looks like underproduction on a sunny midday if you do not know to expect it.
Specific yield
Annual kilowatt-hours per kilowatt of installed capacity. The number to compare across systems of different sizes, and more useful than raw kilowatt-hours when you are asking whether yours is normal.

What the shape of a shortfall tells you

Most diagnosis effort goes into the size of the gap. The shape of it is more diagnostic and your monitoring already shows it.

Uniformly low across every hour and every month points at something systemic: the system is smaller than you think, the model was optimistic in a way that does not vary, or something is derating everything equally. It rarely points at shading, which is time-specific by nature.

Fine at midday, poor in the morning or afternoon is the signature of shading, and which end of the day it falls on tells you which direction the obstruction is. This is the pattern trees produce, and it worsens over years as they grow, which is one reason a system that met expectations in year one may not in year eight.

Fine most days, occasional near-zero days is usually weather or an outage rather than a defect. Cross-check the near-zero days against local weather and against any grid interruption.

One string or one area consistently below its neighbours is the most actionable pattern of all, because it localises the problem to hardware in a specific place. If your monitoring reports at panel level, this is where that capability earns its cost.

A flat top on sunny days is not a fault at all. It is clipping: the array producing more DC than the inverter can convert, which is a deliberate design choice in many systems. Worth confirming rather than reporting.

How to actually diagnose it, in order

  1. 1
    Compare a full year, not a month

    The stated monthly error is ±30% for typical weather and up to ±40% in a specific year. Annual is ±10% and ±20%. If you have not had a full year, you do not yet have a comparison the model claims to support.

  2. 2
    Ask what the estimate assumed for shading, snow and ageing

    If the answer is "the defaults", then it assumed an unshaded horizon, no snow loss and no degradation. Any of those three being wrong for your roof explains a gap without anything being broken.

  3. 3
    Check the weather year, not just the system

    The model is built on typical historical weather. A genuinely cloudy year produces less, and that deviation is inside the model’s own stated tolerance rather than evidence of a fault.

  4. 4
    Look at the shape of the shortfall, not just the size

    A system down uniformly across all hours points somewhere different from one that is fine at noon and poor in the afternoon, which points at shading. Your monitoring shows this if it reports at panel or string level.

  5. 5
    Check for downtime

    The model’s availability default is 3%. If your system was offline for longer than that, the missing energy is not a performance problem, it is an uptime problem, and it has a different owner and a different remedy.

  6. 6
    Then check soiling, seasonally and by region

    In dry climates, months without rain can accumulate substantial loss that rain then clears. In humid regions there is evidence of a different mechanism that rain does not clear. We cover both separately.

  7. 7
    Only then treat it as a hardware question

    If a full year is well outside tolerance, the shortfall is uniform, uptime was good and the model’s assumptions matched your roof, you have a real case to put to your installer while any workmanship warranty is live.

What a realistic expectation looks like

There is one more piece of context worth having, from a large fleet study rather than from a model.

Work examining a portfolio of well over a hundred plants totalling around nine gigawatts found actual generation running at roughly 81 to 82% of ideal expected energy, with inverter downtime around 2 to 3% against roughly 1% typically assumed in financing. That is utility-scale rather than residential, and it is not directly transferable to a house.

What it does establish is directional and useful: across a large professionally operated fleet, real output sits meaningfully below ideal expectation, and one of the larger contributors is availability rather than the panels underperforming. Residential systems are not monitored or maintained to that standard.

One more asymmetry is worth naming, because it explains why this argument is so often unresolvable. The installer holds the model and its assumptions; you hold the meter. Neither of you can settle the question alone, and the assumptions are the half that never gets written down. Asking what the estimate assumed is not an accusation, it is a request for the other half of the evidence.

So the realistic frame is that a well-functioning residential system produces somewhat less than an idealised model says, for reasons that are mostly not defects. The question worth asking is not "is it hitting the number" but "is the gap explained by things I can name". If every item on the list above accounts for part of it, the system is probably fine. If a large part of the gap is unexplained after you have worked through them, that is when to escalate.

Method and limitations

What was read

The PVWatts Version 5 manual in full, for the stated error bars, the default loss table, the statement that the tool is deliberately simplified and that more accurate tools exist, and the validation study together with its own caveats about unshaded systems and removed downtime. Retrieved through the Department of Energy's repository, because the laboratory's own domain was unreachable from our environment.

The snow bounding statement and the fleet performance figures come from separate laboratory and industry publications, each cited below.

Attribution and version

The error figures belong to Version 5 of the tool, dated September 2014. Later versions exist and we could not reach their documentation to confirm whether the figures are restated. We attribute them by version and date throughout rather than to the tool generally, and anyone relying on the precise numbers should check the current documentation.

What this page does not tell you

It does not tell you your system is fine. Systems do underperform, hardware does fail, and installations are sometimes wrong. The argument here is about sequence: establish what the promise was worth before treating a gap as a fault, because the most common outcome of doing it the other way round is an argument nobody can settle.

And it gives no figure for what a typical residential system achieves against its estimate. We found no primary source for one. The fleet figures quoted are utility-scale, professionally operated, and cited as directional context rather than as a benchmark for a house.

Questions

How much less than the estimate is normal?
The model behind many residential estimates states its own errors as up to ±10% for annual totals and ±30% for monthly totals on typical weather, with a specific year deviating up to ±20% annually and ±40% monthly. So a month well below projection can sit entirely inside the model’s stated tolerance, and a year is the shortest comparison worth drawing conclusions from.
Does the estimate account for my trees?
Probably not, if it used the default. The documentation states that the 3% shading default represents an unshaded horizon and does not account for shading from the homeowner’s own trees or nearby buildings. If you have shading and nobody modelled it specifically, the projection assumed it away.
Does the estimate account for snow?
The default is zero. Set against a laboratory statement that snow-related losses can exceed 30% of annual production at northern latitudes, that default is the single largest silent assumption in a northern estimate. Ask whether snow was modelled at all, and if so, on what basis.
Does the estimate account for panels getting older?
The default ageing loss is also zero. Separate research puts median field degradation around half a percent a year with a mean higher than that, so over a long projection the assumption compounds. A twenty-five-year savings figure built on no degradation is optimistic by construction.
My system was validated as accurate. Does that not settle it?
Read what the validation covered. The manual reports the current version underpredicting annual energy by 1.8% against nine real systems, and states in the same paragraph that all were unshaded, that unavailable periods were removed, and that shading and availability losses were set to zero for the comparison. That tests the physics rather than the model’s behaviour on a shaded roof with real downtime.
What is the first thing to check?
Whether you are comparing a full year. After that, what the estimate assumed for shading, snow and ageing, because the defaults for two of those are zero. Most gaps we would expect to be explicable at that point, without anyone examining the hardware.
When is it actually a fault?
When a full year is well outside the model’s stated tolerance, the shortfall is uniform across the day rather than concentrated in particular hours, uptime was good, and the model’s assumptions matched your roof. At that point you have a specific and evidenced case, which is a much stronger thing to bring to an installer than a feeling that the bills are higher than expected.
Should I expect to hit the estimate exactly?
No, and the model does not claim you will. Large fleet studies of professionally operated plants find real generation running meaningfully below ideal expectation, with availability a significant contributor. A residential system is not monitored to that standard. The useful test is whether the gap is explained by things you can name.

Written and audited by

HyreSolar Research

Primary-source research, data analysis and fact checking

We are a research desk, not a sales floor. We read the statute, the tariff, the code section, the federal filing or the manufacturer data sheet ourselves, and we publish the figure with the document it came from and the date we retrieved it. Where a number cannot be traced to a primary source, we publish the shorter page and say what we could not verify. That rule has cost us whole sections, and it is the reason the rest can be trusted.

160
primary sources read and cited
220
figures with a retrieval date
115
federal and state government sources
66
researched pages published

How this desk works

  • Primary sources only. Statutes from the legislature’s own publishing system, federal data from the agency that collects it, code text from the adopted edition, manufacturer claims from the data sheet. We do not cite an article that cites a source; we go and read the source.
  • Every figure carries its provenance. A named document and the date we retrieved it, so you can check it and so you know how old it is. Retrieval dates are not decoration: an EIA rate from May is a different fact from an EIA rate from August.
  • We publish what we could not verify. Every research page carries a section naming the things we tried to establish and could not, and why. A paywalled standard, a state website that refused the request, a manufacturer that publishes no figure at all.
  • We separate measurement from modelling from our own reasoning, and label which is which on the page. A laboratory measurement, an assumption inside a modelling tool and our own inference are three different kinds of claim and they are never presented as one.
  • We do not sell solar, and we take no payment for placement, ranking or a favourable mention. Nobody buys a position on this site.

Data as of National laboratory documentation read on 3 September 2026. Authorship on this site is organisational: the analysis belongs to the desk rather than to a named individual, and we do not publish credentials we do not hold. Our editorial policy sets out how we source, date and correct what we publish.

Sources & retrieval dates

  1. PVWatts Version 5 Manual (NREL/TP-6A20-62641) — National Renewable Energy Laboratory, September 2014. Source for the stated error bars of ±10% annual and ±30% monthly on typical weather data and ±20% annual and ±40% monthly for a specific year, for the full default system loss table including 3% shading, 0% snow and 0% age, for the statement that the tool is deliberately simplified and that more accurate tools exist, and for the validation study together with its caveats that all systems were unshaded, unavailable periods were removed, and shading and availability losses were set to zero. Retrieved 3 September 2026.
  2. Cooper, Braid and Burnham, Identifying the electrical signature of snow in photovoltaic inverter data (SAND2023-14122C) — Sandia National Laboratories. Source for the statement that snow-related power losses can exceed 30% of annual production at northern latitudes. Quoted here as a bounding statement rather than a typical value, which is how the paper frames it. Retrieved 3 September 2026.

Producing less than the proposal promised?

Send us the proposal and a year of production data. We will tell you what the estimate assumed, whether the gap is inside the model’s own tolerance, and what is left to explain.

Get production checked Open the calculators

HyreSolar is an independent analysis and matching service. We are not an installer, lender or utility. When a reader asks to be introduced, installers may pay us a referral fee. That fee never buys ranking, scores or placement in research. Our editorial policy sets out the rules.