Back to Blog
solar technology8 min read

Bifacial Solar Panel Design: Inputs and Review Workflow

Plan bifacial PV with documented module data, albedo, clearance and row geometry. Compare compliant scenarios and preserve an approved design record.

Rainer Neumann

Written by

Rainer Neumann

Editorial contributor · SurgePV

Keyur Rakholiya

Edited by

Keyur Rakholiya

CEO & Co-Founder · SurgePV

Published ·Updated

A bifacial design needs more than a rear-gain allowance in the proposal. The site surface, rack geometry, electrical configuration and modeling method must describe the same project before the structure and equipment order are fixed.

Answer: Design a bifacial PV system by documenting the module’s reference data, site reflectance, rear clearance, row geometry and obstructions. Check model applicability and electrical compatibility, then compare compliant scenarios using delivered energy and verified costs. Preserve input sources and uncertainty. No generic albedo, height or GCR value guarantees an annual gain, an optimal design or a P90 estimate.

SurgePV publishes this guide and sells solar software. This is a documentation-based design workflow, not a first-hand test or a claim of automatic engineering approval.

1. Define the project constraints and reference

Record usable roof/land area, access, structural limitations, equipment restrictions, export conditions and the required deliverable. Decide whether the comparison fixes module capacity, inverter capacity or available area. A wider layout may improve gain per module while reducing the number of modules that fit.

Use the bifacial panel definition for module specifications and the bifacial gain calculation for the energy denominator. This guide follows the design decisions from input collection to issue approval. For mounting-specific review questions, use the mounting-type comparison.

Specify whether the reference disables rear response on the same modeled array or represents another product/configuration. Keep tracking benefit separate from rear-response benefit. State the output boundary and time period in every comparison.

2. Collect the exact module and inverter data

Retain the supplied module’s front-side ratings, bifaciality definition, temperature coefficients, dimensions, loading/mounting instructions and warranty terms. A technology label such as TOPCon or HJT does not supply a universal set of coefficients or guaranteed financial advantage.

Document the inverter and string allocation. Evaluate voltage, current, equipment compatibility and applicable protection requirements independently of the expected rear gain. Rear illumination can change operating output; the model must use the appropriate equipment data and design method.

SAM’s module documentation separates module reference ratings from operating calculations and applies weighted rear plane-of-array irradiance in its bifacial model. Do not treat a weighted irradiance fraction as an annual energy-gain certificate.

Request the relevant manufacturer/test documentation for the actual module. This guide does not assert that one certificate, a construction type or an arbitrary standards list verifies every project requirement.

3. Document the reflecting surface and its uncertainty

Record which surface the rear can see, its extent and condition, and the evidence behind its albedo. Identify seasonal vegetation, snow, dirt, maintenance or surface replacement assumptions where relevant.

A surface photograph can document condition; it is not a calibrated reflectance measurement. A short favorable survey should not automatically become the lifetime average. Use an appropriate measurement or defensible data source, record its scope, and evaluate uncertainty with the reviewer.

If proposing a reflective treatment, include the installable area, drainage/environmental requirements, maintenance and current quotations. Do not promise a universal payback or apply an invented five-year degradation percentage.

Changing an albedo assumption is a sensitivity scenario, not a P90 calculation. A probability-of-exceedance assessment needs a stated uncertainty method and energy/time basis. Selecting a particular future-year albedo does not by itself establish a P90 value. See P50/P90 energy yield for the separate probabilistic task.

4. Define geometry with unambiguous units

Retain tilt/orientation, row pitch, table dimensions, clearance and rear obstructions. Distinguish the bottom edge of a fixed tilted table from the axis of a tracker. Verify the minimum clearance across the permitted operating positions, using the actual terrain and structure.

For a simplified symmetric table rotating about its center over level ground:

Lower-edge clearance = axis height − (table width / 2) × sin(rotation angle)

Assume an illustrative 2.0 m table width, 1.5 m axis height and 60° rotation. The calculated lower-edge clearance is 0.634 m, rounded. At horizontal it is 1.5 m. This explains why one horizontal-height input does not establish the closest operating approach to the ground.

The formula omits terrain, structural offsets, tolerances and module/rack details. It is not an approved tracker height or installation clearance.

For a simple regular-row convention, GCR = table width / row pitch. An illustrative 2.0 m width and 5.0 m pitch give 0.40. Record the software’s dimension convention before using that result; sloped width and horizontal projection cannot be silently interchanged.

5. Confirm model applicability before running variants

PVsyst’s bifacial modeling procedure documents regular-layout assumptions, height conventions, rear structural shading and mismatch treatment. It also identifies unsupported arrangements. Check that the chosen model covers the geometry actually being evaluated.

Do not infer that a 3D scene guarantees complete 3D rear illumination. Models can use a simplified rear calculation despite a detailed front-side scene. For irregular roofs, canopies or mixed geometry, document limitations and ask a qualified reviewer whether another method or cross-check is necessary.

Retain the rear-shading and nonuniformity assumptions rather than selecting an undocumented universal mismatch allowance. Different tools’ default percentages are not automatically equivalent physical quantities.

6. Compare scenarios without changing the baseline silently

Start from a frozen input record. Vary declared candidate values for surface, geometry or equipment. Record every dependent change, including module count, inverter arrangement and structural scope.

A useful comparison sheet contains:

Field Why it belongs in the record
Case identifier and changed inputs Makes the comparison reproducible
Weather and model/version Keeps resource and method consistent
Geometry and module count Exposes site-density tradeoffs
Delivered energy and defined rear contribution Separates gains from the complete output
Clipping and other loss categories Shows downstream limits
Verified installed and maintenance costs Supplies actual economic inputs
Uncertainty and excluded details Prevents a precise-looking result from hiding limitations

PVsyst’s bifacial results documentation separates rear irradiance and electrical contributions. Preserve the named report quantities and denominators when comparing results.

Do not choose a variant solely because its gain percentage is largest. Use the project’s declared objective, energy-value profile and cost assumptions. If multiple inputs change together, describe the complete option rather than attributing all benefit to rear illumination.

7. Issue an approved design and preserve the as-built basis

Before design freeze, reconcile the layout, structural requirements, electrical design and modeled inputs. Assign responsibility for unresolved assumptions. The issue package should retain component data, geometry, surface assumptions, calculation/model files, outputs and revision identifiers.

At installation, document any change in equipment, height, spacing or obstruction against the approved model. Re-evaluate material changes before reusing its forecast. Post-install review needs corresponding weather and meter boundaries; use loss analysis to avoid diagnosing a normal resource difference as failed rear performance.

When evaluating SurgePV’s design workflow, request a requirements demonstration of the inputs, supported rear method and exported revision record. This page does not establish automatic rear maps, linked financial scenarios, code-compliant string approval or a guaranteed calculation time.

Frequently Asked Questions

What inputs are needed for bifacial panel design?

Document module and inverter data, weather, site reflectance, row geometry, clearance, rear obstructions, electrical configuration and the required output boundary. Record sources, revisions and uncertain assumptions.

Is there a universal minimum bifacial mounting height?

No universal height establishes useful gain or a compliant installation. Review the actual structure, operating positions, terrain, model applicability and applicable project requirements.

Should Year-10 albedo be used as a P90 assumption?

Not automatically. Albedo sensitivity and long-term surface assumptions are separate from a probability-of-exceedance assessment, which requires a documented uncertainty method and period.

Does higher bifaciality guarantee a better project?

No. Bifaciality describes module response under stated reference conditions. Outdoor illumination, downstream limits, equipment fit, installed costs and the project objective also matter.

Can a software layout approve a bifacial design?

A layout or model output does not by itself approve the electrical, structural or commercial design. Qualified reviewers must check the relevant requirements, supported methods and issue record.

Sources reviewed September 30, 2026. Geometry examples are illustrative calculations; no first-hand project test is claimed.

Where this fits

This article is part of SurgePV's Solar Technology hub, which works through the topic from first principles to the decisions a project team actually has to make.

About the Contributors

Author
Rainer Neumann
Rainer Neumann

Editorial contributor · SurgePV

Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.

Editor
Keyur Rakholiya
Keyur Rakholiya

CEO & Co-Founder · SurgePV

Keyur Rakholiya is identified by SurgePV as its CEO and a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, testing claims, media appearances, and speaking engagements are not asserted without retained evidence.

Get Solar Design Tips in Your Inbox

Join 2,000+ solar professionals. One email per week - no spam.

No spam · Unsubscribe anytime

Book Free Demo

Choose which optional technologies SurgePV may use. Essential storage remains active for security and requested features.