7 Tips for Using PVSyst Output in Proposal Documents

Table of Contents

• What to grasp before incorporating PVSyst output into a proposal document

• Tip 1: Choose outputs by working backwards from the proposal objective

• Tip 2: Never present numbers alone—always include the assumptions

• Tip 3: Look at monthly trends and loss breakdowns, not just annual generation

• Tip 4: Arrange comparison cases so the reasons for differences are clear

• Tip 5: Always link shading and 3D scene results to numbers

• Tip 6: Don’t overload with jargon—translate terms for the reader

• Tip 7: Include uncertainties and next verification items in the proposal

• Summary: Connecting PVSyst results to on-site proposals

What to grasp before incorporating PVSyst output into a proposal document

Running simulations in PVSyst yields a lot of information: annual generation, PR, monthly generation, loss trees, shading analysis, various settings, and more. In practice, when so much information is available, there is a tendency to try to put everything into the proposal document. However, what matters in a proposal is not the quantity of information. It’s that the reader clearly understands what can be learned and what decisions can be made. PVSyst outputs are hard to communicate if simply pasted in as-is; how you organize them can greatly change their value.

In proposal documents, the reader is not always familiar with PVSyst. Internal approvers, sales staff, clients, and construction personnel all have different informational needs depending on their roles. A technical person may be interested in loss breakdowns and assumptions, but decision-makers often want to know whether a plan is advantageous overall, what the risks are, and what should be checked next. If you don’t consider these differences in your audience when using PVSyst outputs, the numbers may be correct but the document won’t convey the message.

Also, PVSyst results depend strongly on input assumptions. A nice-looking annual generation figure means different things depending on whether the assumptions are idealized or reflect site conditions. In a proposal, it’s more important to be able to explain why a number was adopted than to show a high number. Presenting results without explaining assumptions weakens the document when conditions change later.

Furthermore, PVSyst outputs have value within the flow of a decision-making process rather than as standalone items. For example, showing only annual generation doesn’t tell a reader whether that figure is high or low, how it differs from alternatives, or which losses are driving the result. Conversely, if annual generation, monthly generation, loss breakdowns, shading conditions, and assumptions are organized into a single narrative, PVSyst outputs become very strong supporting material. The following sections organize seven concrete tips to achieve that.

Tip 1: Choose outputs by working backwards from the proposal objective

When using PVSyst outputs in a proposal, the first step is to clarify the proposal objective. Whether you want to show annual generation, explain the advantages of multiple options, demonstrate shading impacts, or convey the validity of a rough estimate will determine which outputs to use. Because PVSyst provides a lot of information, you may be tempted to include everything, but if the objective is vague and results are simply listed, the reader won’t know what to focus on.

For example, if the purpose is site comparison, what you need first are each option’s annual generation and where the differences come from. In that case, loss trees and monthly generation differences are useful supporting information. On the other hand, for an internal initial approval document, it’s better to concisely state assumptions while summarizing expected annual generation, key risks, and items for additional verification rather than showing many detailed settings and technical terms. PVSyst is versatile, but if you don’t define its role according to the proposal objective, the persuasive power of the numbers will be dispersed.

Working backwards from the objective also makes it easier to decide what not to include. PVSyst has many detailed report items that may be technically meaningful but become noise in a proposal. For example, including a long list of parameters or graphs that don’t affect the decision can bury the key conclusions. In practical documents, being focused on the information needed for decision-making is more valuable than showing more data.

Therefore, before creating the proposal document, it’s effective to summarize in one sentence what you want the reader to decide from the document. Once that sentence is decided, it becomes clear which outputs to extract from PVSyst and in what order to present them. To avoid failure in proposal documents, don’t start by browsing PVSyst results—first define the proposal objective and then select only the necessary outputs.

Tip 2: Never present numbers alone—always include the assumptions

When including PVSyst outputs in a proposal, never show numbers in isolation; always present them together with the assumptions. Annual generation and PR figures may look convincing at first glance, but if it’s unclear what assumptions produced those figures, explaining changes later becomes difficult. In practice, the reliability of a number depends more on the conditions under which it was estimated than on the number itself.

For example, when presenting an annual generation figure, briefly note which meteorological data point was used, how azimuth and tilt were set, how much shading was assumed, and how loss factors and utilization losses were treated. Doing so greatly strengthens the document. Because PVSyst numbers faithfully reflect assumptions, presenting numbers without them causes readers either to overtrust the figures or to distrust them.

Listing assumptions also makes it easier to explain differences between options. If one option’s annual generation is higher, is that because the site is more favorable, the azimuth differs, or shading is smaller? Including assumptions helps readers understand. If you present numbers alone, it’s unclear what is being compared, and even well-organized PVSyst results lose persuasive power in a proposal.

A practical approach is to place a short assumption summary near the results. You don’t need to insert a lengthy settings list, but at minimum include the installation location, azimuth, tilt, shading conditions, and the basic approach to major losses so the reader can grasp the context. To make the most of PVSyst numbers in a proposal, don’t let the numbers stand alone—link them to their assumptions.

Tip 3: Look at monthly trends and loss breakdowns, not just annual generation

When using PVSyst results in a proposal, don’t stop at annual generation. Annual generation is the most straightforward metric, but in practice it often doesn’t sufficiently explain differences between options. Two options may have similar annual generation but very different monthly profiles or loss breakdowns, which changes their engineering implications. One of PVSyst’s strengths is that it allows you to trace not only annual values but also their internal composition.

For example, one option may look advantageous on an annual basis but suffer a significant drop in winter generation. Another option might be slightly worse annually but more stable month-to-month. These differences reflect shading impacts, azimuth, tilt, PCS settings, temperature loss assumptions, and other condition differences. Showing monthly trends in a proposal allows you to explain options as features rather than just winners and losers.

Also, examining the loss tree or loss breakdown quickly clarifies why a certain generation value emerged. Is shading the dominant factor, is temperature loss primary, are PCS limitations active, or are wiring and utilization losses influential? If you can organize this, readers will understand the background behind the numbers. In practice, this information is especially useful when explaining differences—not just that one is higher or lower but why the difference exists.

Therefore, in proposals present annual generation as the main indicator but supplement it with monthly generation characteristics and the main loss breakdowns as needed. You don’t have to include every graph or screen, but present what supports your conclusion. If you use PVSyst outputs in a proposal, show not only the annual figure but also the components of that figure to the extent necessary.

Tip 4: Arrange comparison cases so the reasons for differences are clear

How you arrange comparison cases in a proposal using PVSyst results is very important. In practice, when showing multiple options you may be tempted to list them by annual generation ranking only. But that doesn’t explain why the order is what it is. To use comparison cases as real proposal material, you must present them in a way that makes the reasons for differences obvious. Because PVSyst handles many conditions, the reader won’t know what is being compared unless you organize the differences intentionally.

For example, if Plan A varies in azimuth, Plan B varies in tilt, and Plan C varies in PCS conditions, explicitly stating what variable each plan changes makes the significance of the differences easier to read. Conversely, if multiple conditions change simultaneously between options, it’s hard to tell where the annual generation difference comes from. In practice, the clarity of the comparison objective and variable organization strongly affects the proposal’s readability.

When explaining differences, it’s effective to use not only annual generation differences but also monthly differences and loss breakdowns. For instance, noting that Plan A has less winter shading while Plan B shows higher summer temperature losses makes the characteristics concrete. PVSyst outputs are easy to compare, so instead of a simple ranking table, structure the presentation to show why the ranking occurred.

A practical tip is to briefly state for each comparison case what was changed and what was held constant, then explain which indicators moved as a result. This helps readers link the numbers to the design conditions. If you want to make strong use of PVSyst outputs in a proposal, having more comparison cases is not necessarily better; the key is to present them so the reasons for differences are visible.

Tip 5: Always link shading and 3D scene results to numbers

Among PVSyst outputs, shading analysis and 3D scenes are visually intuitive and easy to use in proposals. However, because they’re visually clear, people sometimes include just the images and stop there. In practice, simply presenting 3D scenes or shading diagrams is insufficient; you must explain numerically how those visuals affect annual or monthly generation.

For example, if you show building shading or self-shading between rows in 3D, also indicate in which seasons and to what extent that shading is effective, whether it appears as a winter difference, and what the annual impact is. Without that, readers may see shading but can’t judge how much it affects the acceptance of the plan. The purpose of showing shading in PVSyst is not only to make it easy to understand visually but to convey the magnitude of its impact.

Also, it’s more effective to select screens that reveal the primary causes of shading than to include many overly detailed images. If the buildings, slopes, or row spacing that cause shading are visible and you can explain which months’ generation differences those causes lead to, that’s sufficient for a proposal. In practice, whether a polished 3D model looks good is less important than whether the model substantiates the numerical differences.

Therefore, when including shading or 3D scenes in a proposal, always link them to annual generation differences, monthly differences, or the loss breakdown. PVSyst’s visual information is a powerful tool, but if it’s not tied to numbers it often only leaves an impression. The tip is to show not just how shading looks but how much generation difference that shading produces.

Tip 6: Don’t overload with jargon—translate terms for the reader

When using PVSyst outputs in a proposal, avoid overloading the reader with technical terms. PVSyst screens include many terms that may be understood by practitioners but are difficult for other readers. Terms like Near Shading, mismatch, utilization loss, PR, and DC/AC ratio may be clear to engineers but unfamiliar to decision-makers, sales staff, or clients without explanation. In a proposal, you should preserve accuracy while translating expressions into terms the reader can understand.

For example, instead of simply showing PR, describe it as an indicator of the power plant’s operating efficiency; explain Near Shading as the effect of nearby equipment or buildings casting shadows. It’s not necessary to avoid technical terms entirely, but using them without explanation leads readers to either follow only the numbers or skip them entirely. In practice, the role of a proposal document is not to flaunt technical prowess but to help the recipient make a decision.

Also, tailor how you present numbers to the reader. Rather than listing values down to many decimal places, communicate only the differences that are meaningful for comparison in a clear way. Don’t paste PVSyst results verbatim; reorganize them to match what you want to say and the audience. In practice, clarity of meaning matters more than excessive detail.

Therefore, when preparing a proposal, consider who the readers are and rephrase for expressions they can easily understand. You don’t have to remove all technical terms, but at least provide an explanation so the meaning is graspable on a first read. The key to leveraging PVSyst outputs in a proposal is not to line up numbers and jargon but to translate them into words that support the reader’s decision.

Tip 7: Include uncertainties and next verification items in the proposal

When using PVSyst outputs in a proposal, don’t forget to state uncertainties and next verification items. In practice, when a nice-looking number appears, there’s a temptation to present it as if final. But PVSyst results are estimates based on current assumptions and may be updated as site checks and detailed design progress. Hiding that fact undermines credibility; organizing and showing it upfront actually increases trust in the document.

For example, note that shading conditions may change depending on the accuracy of site verification, azimuth and tilt may need re-evaluation after site grading is finalized, and soiling or utilization losses can be adjusted with a clearer maintenance plan. Writing this down makes readers less likely to overtrust the numbers and clarifies the proposal’s precision. In practice, it’s stronger to specify what remains uncertain and what should be verified next than to conceal uncertainty.

Also, listing the next verification items helps the proposal lead to action rather than merely reporting. If readers know what to check—confirming the positions of obstacles on site, finalizing layout details, re-evaluating PCS capacity, reviewing maintenance access routes—they are more likely to decide. PVSyst results should be used not as a one-time display but as material that connects to subsequent design actions.

Therefore, at the end of the proposal briefly summarize which assumptions the results depend on, which parts have room for update, and what to check next to improve accuracy. This makes PVSyst figures easier to treat as practical decision material rather than definitive values. A proposal needs not only a completed answer but also a roadmap that includes the next verification steps.

Summary: Connecting PVSyst results to on-site proposals

What is common to the seven tips above is not to simply paste PVSyst outputs and call it done. Choose the outputs needed for the proposal objective, present numbers together with assumptions, look at monthly and loss breakdowns as well as annual generation, arrange comparison cases so their differences are clear, link shading and 3D scenes to numbers, translate technical terms for the reader, and include uncertainties and next verification items. If you follow this flow, PVSyst outputs become not just technical documentation but proposal materials that support decision-making.

For practitioners, the goal is not to show the highest number. What matters is being able to explain which assumptions produced the number, how reliable it is, and the strengths and weaknesses of each option. PVSyst is multifunctional and can output a lot of information, so how you organize it greatly affects the quality of the document. Selecting the information needed for decisions is far more important than increasing the quantity of numbers.

Also, to genuinely increase a proposal’s persuasiveness, don’t rely solely on desk simulations. PVSyst figures gain practical meaning when site boundaries, slopes, obstacles, access paths, existing equipment, and maintenance routes are organized. Iterating between site conditions and simulation results to check how realistic they are determines proposal quality.

In that sense, when you want to secure position checks and coordinates more reliably on site, using an iPhone-mounted GNSS high-precision positioning device such as LRTK is a natural consideration. If site position information and conditions are easier to organize, you can more naturally connect PVSyst annual generation, shading conditions, and layout assumptions to the proposal. By improving desk-level comparison accuracy with PVSyst and supporting on-site accuracy with LRTK, a proposal becomes closer to a practical, site-rooted recommendation rather than a mere simulation report. Using PVSyst outputs skillfully is not just a technique for showing numbers; it is a practical capability to connect desk work and site work so the recipient can make a decision.