[Seven Ways to Correctly Read a PVSyst Report | Which Numbers Should You Look At?]

PVSyst reports are a convenient document that consolidates predicted energy generation results onto a single page for review. However, in practice the reports contain many figures and terms, and it is common to stop at just looking at the annual energy yield without knowing where to start. That leaves you unable to grasp why that energy yield was obtained, where losses occur, and which assumptions should be revisited.

Once you can read the report correctly, it becomes much easier to validate designs, explain internally, report to clients, and compare post-construction performance. This article organizes and explains, for practitioners, the key numbers to focus on in a PVSyst report and the order in which to read them.

Table of Contents

• Assumptions to grasp before reading a PVSyst report

• 1. Look at solar irradiation as the input to incident radiation

• 2. Look at exported energy as the output of generation

• 3. Separate specific yield and PR when evaluating

• 4. Use the loss flow diagram to see where reductions occur

• 5. Don’t overlook the impacts of temperature, shading, and equipment constraints

• 6. Detect signs of anomalies from monthly variability

• 7. Confirm that assumptions match site conditions

• A reading order for reports that avoids confusion in practice

• Summary

Assumptions to grasp before reading a PVSyst report

When reading a PVSyst report, it is important not to view figures in isolation but to understand them as the flow from solar radiation entering the system, converting to electricity, and ultimately being exported to the grid. The report lists many figures, but what practitioners really want to know can be grouped into three main points. First, what are the conditions for how much solar irradiation the site receives? Second, at which stages and how much of that incoming irradiation is lost? Third, do the calculation assumptions match the site and design conditions?

Viewing the report from these three perspectives quickly clarifies the meaning of the numbers. Conversely, looking only at the annual energy yield or only at PR makes it difficult to judge the quality of the design. A large annual energy yield may simply reflect favorable irradiation conditions. A high PR does not guarantee a large total output if the location’s solar resource is small. In other words, it is important not to evaluate using a single metric.

Also, while PVSyst reports can be used to compare designs, you must align the assumptions when comparing. Differences in tilt, azimuth, capacity, loss settings, or irradiation data can change apparent rankings. Before reading a report, first be aware whether the document is for a simple energy check, loss analysis, or design comparison; that will set the priority for which numbers to read.

1. Look at solar irradiation as the input to incident radiation

When reading a PVSyst report, the first numbers to check are the input-side figures: in other words, the assumptions for how much solar irradiation the system receives. Skipping this and looking only at energy yields prevents proper fault isolation. You won’t know if low generation is due to weak incident radiation or poor conversion of received irradiation into electricity.

In practice, first confirm the irradiation figures for the array surface. It is important to look at the irradiance incident on the tilted installation surface according to actual installation conditions, not just horizontal-plane irradiation. Orientation, tilt angle, terrain, horizon conditions, and nearby obstacles appear here. Therefore, if the irradiation values are lower than expected, reexamine the incident radiation assumptions before doubting module performance.

Equally important is understanding how much of the incident irradiation remains usable. In PVSyst reports, comparing the irradiation incident on the array surface with the irradiation after adjustments for shading and angle of incidence makes it easier to grasp the magnitude of optical losses and shading effects. If this difference is large, first suspect nearby obstacles, row spacing, tilt conditions, morning/evening shading, or seasonal differences in solar altitude.

For example, if annual energy yield underperforms but the array-surface irradiation itself is low, that suggests site conditions rather than design are the main factor. Conversely, if array-surface irradiation is sufficient but the effective irradiation drops substantially, shading and optical loss treatment will be key. This input check alone makes the subsequent loss and generation figures much easier to interpret.

Besides annual totals, look at monthly trends in irradiation. If there is a significant winter dip, low solar altitude causing shadows may be the cause. If summer is unusually high, check how tilt and azimuth settings interact with the site’s seasonal characteristics. Incident irradiation is the starting point for everything; without understanding it, later interpretation will be unreliable.

2. Look at exported energy as the output of generation

After confirming input irradiation, the next numbers to view are the output-side figures. Practitioners are usually most interested in how much energy was ultimately exported to the grid. In PVSyst reports, it is important to distinguish at which stage a given energy figure is reported. Intermediate-stage energy and the final energy exported to the grid have different meanings.

Pay attention to the relationship between the energy produced on the array side and the energy finally exported to the grid. Array-side figures represent an intermediate stage of the energy generated by the modules. By contrast, exported energy is closer to the final result after conversion and equipment losses. If array-side numbers are reasonable but final exported energy is low, the problem is more likely on the equipment or grid side, or due to constraint settings, rather than irradiation.

A common mistake in practice is to look only at the annual energy figure and prematurely assume a module or installation issue. However, if there is a large gap between array output and grid export, factors such as conversion losses, cabling losses, output limitations, or downtime may be responsible. Being able to separate these causes makes it clearer whether designers, constructors, or operators should act.

Also, read the output numbers within the flow from input to output. If low export is due to low irradiation at the input, the remedy will differ from a case where irradiation is adequate but lost along the way. The former suggests reevaluating site or layout; the latter suggests reviewing equipment configuration or loss settings.

When comparing options, this perspective is useful as well. An option that appears to export more energy may simply differ in capacity assumptions, making direct comparison invalid. Always check equipment capacity and assumptions when reviewing exported energy. Output-side figures are prominent for business and reporting, but to interpret them correctly you must read them in relation to input-side figures.

3. Separate specific yield and PR when evaluating

Two commonly highlighted indicators in PVSyst reports are specific yield and PR. Both are useful but are not the same. Confusing them can lead to incorrect design judgments. In practice, it is very important to separate these two when reading the report.

Specific yield shows how much energy was produced per unit installed capacity. It makes comparisons across projects with different capacities easier and is suited for relative evaluation of design options. For example, even if capacities differ, specific yield helps determine which option produces more annual energy per unit capacity. It reveals differences that absolute plant energy may hide, showing productivity per unit of capacity.

PR, or performance ratio, indicates how effectively the received irradiation is converted into electricity. It is useful for assessing system health and efficiency while partially isolating site resource effects. If PR is low, suspect that loss settings or equipment conditions may need improvement. But a high PR does not guarantee a high annual yield: in a location with limited solar resource, good conversion efficiency may still yield a small total output.

Conversely, specific yield can be high while PR is low. That may mean site irradiation is very favorable, so total energy is large despite systemic inefficiencies. In short, specific yield helps understand the scale of results, while PR helps assess system quality.

Separating these two in internal or client explanations increases persuasive power. Specific yield links directly to project economics and revenue, while PR indicates design quality and loss management. Emphasizing only one can lead to a biased view. In practice, it is effective to use specific yield to grasp the big picture and PR to supplement with a measure of system health.

Also note that PR can look good even when it is optimistic. If loss settings are set too leniently, PR will be inflated, so always check loss breakdowns and assumptions as described later. Specific yield and PR are convenient summary metrics, but because they are summaries, you should examine the background that composes them.

4. Use the loss flow diagram to see where reductions occur

Perhaps the most practically useful part of a PVSyst report is the section showing the flow of losses. Here you can see, in sequence, how much of the incoming irradiation was reduced at each stage. This reveals the true nature of losses that annual energy or PR alone cannot show.

When reading the loss flow diagram, follow it from the top down. Incident irradiation enters the array surface, is reduced by optical corrections and shading, then further reduced by module temperature, mismatch, cabling, and finally passes through conversion stages and other constraints to reach exported energy. Tracing this flow makes it immediately clear which stages have the largest losses.

It is important not to treat all losses equally. Some losses are hard to avoid while others can be improved through design changes, construction quality, or equipment selection. Shading and row spacing relate to layout planning; temperature losses relate to ventilation conditions and mounting methods. Cabling losses can be mitigated through circuit and cable planning, and conversion losses relate to equipment configuration and rating balance. The loss diagram is like a map to find items with improvement potential.

In practice, after viewing the loss diagram, first identify the largest loss item and consider whether it is reasonable and whether it can be improved. Trying to tackle every loss at once scatters the discussion, but focusing on the largest impacts helps set priorities. When comparing design options, don’t just look at annual energy differences; look at where losses differ to explain why the difference arose.

The loss diagram is also an excellent communication tool. Among the many technical figures in the report, the loss flow makes it visually easy to understand where energy is being lost, so it is useful for aligning understanding with stakeholders. It works well not only among designers but also when sharing with contractors and non-specialist departments. Correctly reading a PVSyst report is not just about checking final figures but about extracting improvement points from the loss flow.

5. Don’t overlook the impacts of temperature, shading, and equipment constraints

Among the losses, temperature, shading, and equipment constraints have particularly large practical impacts. They affect not only annual totals but also seasonal and diurnal biases; missing them can lead to misreading the report.

First, temperature losses. PV systems can look favorable with high irradiation, but when ambient and module temperatures rise, conversion efficiency decreases. This means months with high irradiation often also have larger temperature-related losses. Therefore, if summer generation doesn’t rise as much as expected, it is premature to assume irradiation is lacking. If temperature losses are large in the report, review installation conditions, ventilation, and the assumed thermal environment.

Next, shading. Shading may appear small on an annual average but can have strong effects during winter or at dawn and dusk. Consider not only shadows from nearby obstacles but also inter-row shading and terrain undulations. Shading affects not just incident irradiation but also the shape of the generation curve and seasonal characteristics. If monthly generation looks odd, question whether the shading estimate is too lenient.

Another easily overlooked item is equipment constraints. Depending on the balance between installed capacity and conversion equipment, even when irradiation is strong there may be times when the equipment’s upper limits prevent full extraction of generation potential. If this persists, you may see good incident conditions but limited exported energy. When reading a report, pay attention to how much reduction is attributed to equipment constraints.

In practice, read these three factors not in isolation but as interrelated. For example, if summer yields are low, the response depends on whether the cause is low irradiation, temperature losses, or equipment constraints. If the decline is limited to winter, shading or installation geometry are more likely. PVSyst reports are intended to capture these factors structurally as well as in annual totals. Temperature, shading, and equipment constraints are especially important points that directly influence practical decisions.

6. Detect signs of anomalies from monthly variability

Annual totals are easy to understand but can hide subtle anomalies. That’s why checking monthly figures is important. In PVSyst reports, reviewing monthly energy, irradiation, and PR trends helps detect biases or anomalies that annual values miss.

A common oversight in practice is skipping detailed checks because annual energy falls within an acceptable range. Yet similar annual totals can hide unusual monthly patterns. For example, if summer underperforms and winter also shows a large drop, temperature losses and shading may be acting together. Conversely, if only certain months show abnormally high or low values, question the coherence of the weather data or loss settings.

Monthly checks are useful not only during design but also for post-construction performance verification and early operation assessment. When comparing simulation and measured results, annual comparisons can obscure the causes of discrepancies. Monthly comparisons reveal which season shows deviations and make it easier to separate shading, temperature, soiling, downtime, or constraints. Although PVSyst is a desktop calculation tool, its reports can be used to dialogue with actual performance.

Monthly figures are also important for client explanations. Annual energy alone makes it hard to intuitively explain why a figure was obtained. If you can present monthly trends, you can explain that summer has high irradiation but also stronger temperature impacts, while winter shows lower irradiation and solar altitude effects. This communicates better than presenting a single annual number.

When looking at monthly variability, don’t just note high and low months; assess whether the pattern is natural given geography, orientation, tilt, shading, and weather. If you can’t explain an anomaly, the report’s assumptions likely need rechecking.

7. Confirm that assumptions match site conditions

Finally, always verify the assumptions. No matter how attractive a report looks, if the assumptions are off the results will be too. In practice, confirming that the input conditions match the site is often more important than the computed numbers themselves.

First review orientation, tilt angle, row spacing, system capacity, and loss settings. These have a large effect on the report’s numbers. In sites with complex terrain, be cautious about whether simplifications assuming flat ground are appropriate. With undulating terrain, actual incident radiation and shadow behavior can change more than expected. Even if plans look fine, on-site morning/evening shadows or elevation differences can have a larger effect than anticipated.

Next, check how nearby obstacles and horizon conditions are modeled. If the positions of trees, slopes, or structures are approximated, the shading evaluation accuracy drops. Precision in obstacle position and height is especially important for assessing winter impacts. A neatly presented report is weak in practical explanatory power if its assumptions are coarse.

Also do not overlook soiling, the temperature model, cabling losses, equipment availability, and downtime assumptions. These may seem like small settings, but they accumulate and affect results. If loss settings are too lenient compared to reality, PR will look artificially high; if too strict, the system may be underestimated. What matters is not the absolute size of numbers but whether the assumptions can be justified.

Correctly reading a PVSyst report means questioning the numbers, not accepting them. Ask what site and design conditions underlie the figures. When documents move between design, construction, sales, and technical teams, insufficient assumption checks can cause divergence later. Treat the report as a tool for validating assumptions, not a finished product.

A reading order for reports that avoids confusion in practice

We have organized seven viewpoints so far, but in practice it helps to read in a set order to avoid confusion. The recommended order is: first check the project’s basic conditions, then the input irradiation, next the exported energy, then the key indicators, the loss flow, monthly trends, and finally return to verify assumptions. This sequence lets you naturally move from the overview to the details.

Start with basic project conditions because capacity and installation parameters alone can change the impression of numbers. Looking at energy without these leaves comparison assumptions undefined. Next check irradiation to establish incident conditions. Then examine exported energy to see how the output relates to the input.

After that, review specific yield and PR to tidy up the scale of results and system efficiency. Then inspect the loss flow diagram to dig into where differences arise. Look at monthly trends to check for unnatural biases. Finally, confirm assumptions to determine whether observed inconsistencies are due to settings or the design itself.

The advantage of this reading order is that it keeps discussions focused. Jumping directly into loss details scatters attention across stakeholders. But reading in the order input → output → key indicators → losses → monthly trends → assumptions helps build a common understanding of where problems occur. This order is especially useful for internal meetings and client briefings.

This order also helps when comparing multiple options. If you change where you look each time, you are more likely to cherry-pick favorable numbers. Reading in the same sequence each time preserves fairness in comparisons. Because PVSyst reports contain so much information, it is important for the reader to have a consistent order.

Summary

To read a PVSyst report correctly, don’t stop at annual energy. Rather, review the sequence from input irradiation, to exported energy, to specific yield and PR, to the loss flow, to temperature, shading and equipment constraints, to monthly variability, and finally to the assumptions. There are many numbers to check, but with a consistent reading framework the report becomes a practical tool to improve design decisions and communication rather than an opaque document.

For practitioners, the important thing is not to memorize numbers but to be able to explain why those numbers occur. The ability to read PVSyst reports translates directly into better design re-evaluation, stakeholder alignment, and post-construction verification. Mastering the seven viewpoints introduced here should at least reduce uncertainty about where to look first.

To improve report accuracy, it is important not only to set assumptions carefully on the desk but also to capture site conditions accurately. If the location of nearby obstacles, elevation differences, actual equipment layout, or as-built details are ambiguous, the simulation assumptions will also be ambiguous. When you want to streamline site surveys, using iPhone-mounted high-precision GNSS positioning devices like LRTK can make it quick and easy to capture location information in the field. Combining skill in reading PVSyst reports with accurate site understanding enhances both design credibility and on-site response capability.