Reading a solar production estimate.

A solar production estimate is a modeled view of how much electricity a proposed PV system is expected to generate over time. It usually turns a proposed system size, roof orientation, location, irradiation data, shading assumptions, and loss assumptions into annual and monthly production.

The first distinction to understand is between kWp and kWh. kWp describes the rated size of the solar array. kWh describes energy produced or consumed over time. A proposal may say the system is a certain size in kWp and is expected to produce a certain amount of kWh per year. Those two numbers are connected, but they are not the same thing.

There is a second distinction that matters even more for the investment decision: production is not automatically savings. Savings depend on when the site consumes energy, how much solar energy is used directly, what tariff assumptions are applied, and what happens to energy produced when the site is not using it.

Before reading any savings or payback line, check the model itself. What system size is being proposed? What annual production is assumed? Is the monthly curve visible? Which site location, tilt, orientation, shading, and losses were used?

A useful estimate makes those inputs easy to find. If the page only shows a large annual production number and a payback claim, the reader cannot tell whether the output comes from careful site assumptions or a generic template.

This matters when comparing quotes. Two providers may show similar annual kWh, but one estimate may include shading, realistic losses, and a conservative roof layout while another assumes ideal roof conditions. On paper they look comparable. In practice they are modeling different projects.

A single annual number hides the shape of production. Solar output changes month by month, and site consumption changes too. A Moroccan hotel may care about summer occupancy, guest-room cooling, hot water, pumps, laundry, and kitchen rhythm. A villa may have strong daytime use during some periods and heavier evening use during others. A factory may have weekday production windows. An agricultural site may care about irrigation months rather than annual averages.

The monthly curve helps reveal whether production is arriving when the site can use it. A system that looks strong on annual kWh may still require careful review if the site consumes heavily at night, during limited operating windows, or in seasons that do not match the highest production months.

That does not mean the estimate must become complicated. It means the monthly production line should be read together with real operating rhythm, not as an isolated number.

Self-consumption is the share of solar energy used directly on site when it is produced. It is one of the most important ideas in a solar estimate because, for many Moroccan projects, the safest starting logic is using solar energy on site unless a specific export framework is confirmed for the project.

Imagine a site that produces strongly at noon but consumes most of its energy after sunset. The production estimate may still look good. The financial logic needs a load profile, because the site may not be able to use all production directly. The answer may be a different system size, a schedule adjustment, a battery discussion, or a clearer understanding of unused solar energy. It should not be guessed from annual production alone.

The estimate is only as useful as the assumptions behind it. Roof orientation and tilt influence how the array receives sunlight. Shading from parapets, neighboring buildings, trees, antennas, water tanks, or HVAC equipment can reduce output. Dust and soiling can matter depending on the site. Temperature, inverter conversion, wiring and system losses, module mismatch, availability, and degradation can all reduce the gap between ideal sunlight and delivered energy.

A good estimate does not need to bury the reader in technical detail. It should make the main assumptions visible enough that a decision-maker can ask the right questions. Was the roof inspected? Was shading considered? Were losses stated? Was the monthly curve generated from real site inputs or generic default values?

Weak assumptions can make two quotes look similar while one is much less grounded than the other. This is where many poor comparisons begin.

Shading is easy to underestimate from a document. Even partial shade can affect production depending on when it appears, how long it lasts, and how the system is designed by qualified professionals. The buyer does not need wiring diagrams or string design instructions. The buyer needs to know whether shading was actually considered.

A useful estimate should show or explain the shaded areas, the affected periods where relevant, whether the provider inspected the roof or used reliable site information, and whether the proposed panel zone avoids obvious conflicts. If a roof has parapets, nearby walls, antennas, HVAC equipment, water tanks, or future access needs, the estimate should not pretend the roof is an empty rectangle.

More roof area does not automatically mean a better solar design. A useful design balances sunlight, shade, orientation, tilt, safe access, maintenance paths, roof condition, equipment placement, waterproofing concerns, and actual consumption.

A large roof with poor shade, difficult access, or many obstacles may be weaker than a smaller clean zone. A compact panel field placed where it can be maintained and used effectively may support a better decision than filling every possible surface simply to increase annual kWh.

Every production estimate includes some form of loss logic, whether it is shown clearly or hidden inside the model. Losses are normal reductions between theoretical sunlight and real delivered energy. They can include temperature effects, inverter conversion, cables and system losses, soiling, mismatch, shading, and availability.

The issue is not whether losses exist. The issue is whether they are stated clearly enough to compare estimates. If one proposal shows loss assumptions and another hides them, the annual kWh figures are not being presented with the same transparency.

A mismatch between production and consumption does not automatically justify batteries. Batteries can be valuable, but only when they solve a defined problem: selected backup, outage tolerance, evening consumption, critical circuits, remote operation, or another clear need.

For a villa, the question may be whether selected loads should remain available during outages. For a hotel or riad, the discussion may involve guest comfort, hot water controls, refrigeration, pumps, or other continuity priorities. For a business, the battery decision may depend on critical loads and operating hours. In each case, the production estimate is only one input.

If a quote adds batteries because “some solar energy is unused,” slow down. The estimate should be connected to load profile, backup expectations, usable capacity, maintenance, cost, and the practical value of stored energy.

Savings and payback depend on self-consumption, tariff assumptions, operating hours, energy price assumptions, system cost, maintenance, financing if relevant, and what happens to unused energy. A precise payback can still be weak if the production, consumption, and tariff assumptions are vague.

This is why the estimate should not be read as a promise. It should be read as a modeled scenario. The stronger the baseline and assumptions, the more useful the scenario becomes. The weaker the assumptions, the more the financial line becomes a sales claim with numbers attached.

For most buyer decisions, the safest question is: What would need to be true for this savings or payback line to be credible?

A production estimate does not need to be long to be useful. It needs to show enough logic for the reader to understand what is being modeled and what remains uncertain.

If several of these signs appear together, the problem is not that the estimate is simple. The problem is that the decision may be built on assumptions the buyer cannot see.

The best questions are practical. They do not require the buyer to become an engineer. They force the estimate to reveal its assumptions.

ReneWave reads a production estimate from the site outward. We start with usage, bills, operating rhythm, and the objective of the system. Then we review the production model: system size, annual and monthly kWh, roof and shading assumptions, losses, and whether the estimate explains what happens when production and consumption do not align.

We separate production from savings. We treat batteries only after backup needs, critical loads, nighttime use, and load profile are clear. We check whether the roof logic is realistic and whether the financial scenario depends on assumptions that still need confirmation.

The goal is not to make the estimate longer. The goal is to make it decision-ready: visible assumptions, realistic consumption match, clear battery logic where relevant, and no investment decision made from production alone.

Good production estimates reduce uncertainty. Weak estimates create false precision. The difference is not the chart style or the number of pages. The difference is whether the estimate explains how the production was modeled and how that production becomes useful for the site.