Back to Blog
solar software6 min read

Commercial Solar Design Software: EPC Checklist

Use this EPC checklist to evaluate commercial solar design software on geometry, simulation, electrical review, tariffs, reports and revisions.

Nirav Dhanani

Written by

Nirav Dhanani

Co-Founder · SurgePV

Rainer Neumann

Edited by

Rainer Neumann

Editorial contributor · SurgePV

Published ·Updated

Answer

Choose commercial solar design software by the project deliverables it must support, not a universal capacity threshold or a bankability label. Test site geometry, shading and energy models, electrical documentation, tariff analysis, required reports and revision handling. Confirm the actual authority, utility and financier requirements. Compare a connected platform with specialist tools using the same verified inputs, reviewed outputs and full operating costs.

Last updated: November 2026

SurgePV publishes this post and sells solar design software. This guide is a desk-researched procurement framework, not a platform ranking or a claim of lender endorsement.

Commercial teams often use separate layout, simulation, electrical, financial and proposal tools. That can work when the interfaces and revisions are controlled. A connected platform may reduce some transfers, but neither architecture automatically removes errors or supplies professional approval. Buy against a defined commercial project and a reviewed output.

Key Takeaway

Buy on the deliverables each recipient needs, not on a capacity threshold or a bankable label. The authority, utility and financier each define what they accept.

See the commercial design workflow on your brief

Bring a real project and a material revision, and check the outputs against your own acceptance list.

Book a Demo

Checking cost first? See the SurgePV pricing page · No commitment required · 20 minutes

Define the project and release before the demo

Record the site jurisdiction, mounting type, roof or land evidence, equipment basis, service and connection information, load accounts, commercial structure and intended deliverable. A preliminary comparison needs a different evidence set from a permit submission or a financing review.

Do not infer electrical voltage, engineer-seal requirements, interconnection studies or finance conditions from a generic 50 kW or 500 kW threshold. Identify the actual adopted rules, utility process and responsible reviewers. A commercial rooftop is not automatically in a regional transmission-operator queue.

Ask each recipient what they need to decide. The authority may require a particular drawing package; the utility may require separate application data; the owner or financier may require an economic or uncertainty analysis. Retain these requirements in the evaluation brief.

Seven capabilities to evaluate against the actual scope

1. Site geometry and constraints

Test roof planes, slope, obstructions, exclusions and source dates for a rooftop. For a carport, test canopy geometry and the structural handoff. For ground mount, test terrain, row geometry and the proposed mounting configuration. Do not assume the software supports every project type because it accepts the site address.

Imagery can inform a model without confirming concealed construction, current roof condition or structural capacity. Identify which measurements and specialist findings remain pending. Exclusion areas need a source and reviewer; an automatic setback is not proof of local compliance.

2. Shading and energy-model scope

Ask how near-field obstructions, horizon effects and row shading are represented. Record weather source, time basis, equipment models, losses, output boundary and software version. Check whether unsupported configurations are rejected or silently simplified.

SAM’s PV model documentation distinguishes detailed module/inverter modeling from PVWatts-style preliminary analysis. It illustrates why a model’s inputs and purpose matter; it does not certify another vendor’s output. A paid license alone cannot establish a universal accuracy percentage.

3. Electrical documentation and qualified review

Demonstrate the equipment schedule, configuration and diagrams needed for the project. Ask which calculations are performed, which inputs control them and which checks remain outside the tool. The array’s DC string design and the inverter’s AC phase arrangement are different questions.

Use manufacturer limits and the applicable project requirements for the responsible review. A generated diagram is not a seal, a permitting decision or permission to energize. Confirm who resolves discrepancies and controls changes after professional review.

4. Load, tariff and commercial modeling

Annual generation is not automatically annual avoided purchases. Record the meter boundary, interval units and timestamps, imports, exports, existing generation and planned loads. Specify the actual tariff and settlement terms.

The DOE utility-rate guide separates energy, demand and fixed charges and discusses time-based and other billing components. Suitable time-resolved data must support a demand-saving claim; there is no universally correct interval for every tariff. Retained charges and export rules belong in the model.

Specify cash-flow perspective and analysis period. Owner cash flow, project cash flow and debt-service analysis are not interchangeable. Taxes, incentives, financing terms and discount assumptions need a source and responsible reviewer rather than a universal default.

5. Required reports and uncertainty

Ask the intended recipient for the report content and acceptable methodology before selecting a package. “Bankable” is not a software certification. A reference report or vendor validation may help the recipient evaluate the method; it does not guarantee acceptance of this project.

P50 and P90 are modeled exceedance thresholds for a declared quantity and period. P90 is not a generation guarantee or a standard percentage haircut from P50. A one-year result must not be presented as a lifetime-average result.

SAM’s uncertainty documentation distinguishes input uncertainty, interannual weather variability and combined results for its Year 1 annual-energy analysis. Ask a candidate to document the scope and distributions of its own analysis. Do not combine correlated uncertainties as independent quantities without justification. The P50/P90 explainer provides further interpretation.

6. Proposal and document revision handling

Introduce a material change after the initial layout, estimate and proposal exist. Check which outputs update, which require a rerun or review and which exported files remain stale. An integrated application does not necessarily update an already downloaded PDF or notify every recipient.

Require a visible project identity, revision, source set, intended use and open-condition list. Preserve superseded outputs as required while making their status clear. Do not interpret a revised price as proof that every technical output has been reconciled.

7. Commercial access and operating cost

Obtain a dated quote for the demonstrated plan. Record users, project or report charges where applicable, paid imagery, API access, integrations, support, training, renewal, export rights and access after cancellation. Do not assign a credit model or current price to a vendor without evidence.

Compare specialist and integrated options using equivalent reviewed outputs. Include implementation, administration, review, revision and migration effort. Cost per project needs a declared period and denominator; repeated options and revisions should not be mistaken for completed projects.

Run your acceptance pack on a live project

Walk through geometry, energy, electrical and proposal outputs in one demo, using the tests in this guide.

Book a Demo

Checking cost first? See the SurgePV pricing page · No commitment required · 20 minutes

Use a project-specific acceptance pack

Test Evidence to retain What prevents acceptance
Geometry and scope Source records, model and exclusions Unsupported mounting or unresolved critical dimensions
Energy Model/version/input register and reviewed report Hidden assumptions or unmatched output boundary
Electrical Equipment basis, drawings and reviewer disposition Unsupported configuration or unreconciled calculations
Financial Actual tariff, settlement and cash-flow basis Missing load timing or unverified incentive/finance terms
Revision Changed-input record and affected-output list Stale estimate, simulation or proposal
Operations Quote, permissions, exports and support terms Required capability absent or inaccessible
7
capabilities to test
6
acceptance checks
3
charge types in a tariff: energy, demand, fixed
2
exceedance levels: P50 and P90

The first two figures count items in this guide’s own checklist. The tariff charge types come from the DOE utility-rate guide linked above, and P50 and P90 are defined in the uncertainty section.

Pro Tip

Score each candidate with the same permissioned project and the same revision. Record which outputs updated on their own and which needed a manual rerun.

Run a representative permissioned project rather than relying only on a prepared sales example. Reconcile model differences with your existing process; agreement within an arbitrary percentage is not proof of actual production or lender acceptance. Obtain authorized feedback from the people who will use the outputs.

Keep training or pilot outputs labeled. Do not ask a customer to sign a test document as a substitute for technical validation. Preserve existing source files and required deliverables before migration; keep legitimate specialist tools where their role remains necessary.

Apply the same test to SurgePV

Evaluate the commercial design workflow with your project brief, a material revision and required output list. Confirm the functions demonstrated, limits, professional-review interfaces and current contract terms. This article does not promise automatic code compliance, P90 generation, structural analysis, report acceptance or a timed end-to-end delivery.

The broader software selection checklist covers general procurement. This page focuses on commercial project interfaces and recipient requirements. To test the workflow yourself, book a SurgePV demo or read how solar proposals are produced.

Frequently Asked Questions

Does every commercial solar project require P90?

No. Confirm the required analysis with the project owner, financier and technical adviser. If exceedance estimates are needed, specify the period, energy boundary, uncertainty scope and methodology; the software label alone is not proof of acceptance.

Does a generated single-line diagram replace engineering review?

No. Confirm its scope, equipment basis, calculations, configuration and revision, and route it through the required qualified review and authority process.

Can annual production establish demand-charge savings?

No. Demand billing depends on the actual tariff and site load timing. Use suitable interval data and generation profiles, retaining any ratchet, fixed, standby or other applicable charges.

Is an integrated platform always cheaper?

No. Compare equivalent reviewed deliverables using actual license quotes, add-ons, implementation, integration, production, review and rework costs. Reduced task time is not automatically a cash saving.

How should I test a candidate platform?

Use a permissioned representative project and introduce a material revision. Check the geometry, model inputs, electrical package, financial basis and proposal together, then verify the exported files and unresolved conditions.

Where this fits

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

About the Contributors

Author
Nirav Dhanani
Nirav Dhanani

Co-Founder · SurgePV

Nirav Dhanani is identified by SurgePV as a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, conversion results, and market-expansion claims are not asserted without retained evidence.

Editor
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.

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.