8 Solar Design Details to Compare Before Choosing

Two solar proposals can show the same panel count and still describe different projects. One layout may use a recent site record while another uses imagery that still needs field verification. One production figure may include a planned electric-vehicle load while another reflects only historical usage. A roof image can look finished even when equipment locations, shade inputs, or electrical work remain open.

That makes the customer’s job narrower than “pick the best installer” and more useful than comparing totals alone. The customer needs to see what each design is trying to accomplish, what information shaped it, which decisions are visible, and what remains subject to review. A sales representative can guide that inspection without interpreting another provider’s intent or declaring its design wrong.

This article owns eight design details in that conversation. It does not cover price, financing, licensing, reputation, contract terms, warranties, service, or a complete provider award. Use the apples-to-apples solar quote checklist for the broader commercial comparison. The two unequal designs guide covers a comprehensive two-quote normalization. Customers evaluating an India-specific provider should use the separate solar company diligence guide.

The public sources cited here provide general U.S. consumer and technical context. They do not approve a site, installer, design, model, contract, or projected result. Project-specific decisions still belong to the responsible provider, qualified reviewers, authorities, utilities, and other approval parties.

What should customers compare before judging two solar designs?

Customers should compare the record behind each design: its objective, source data, revision, assumptions, configuration, review state, and unresolved conditions. Label every material field as measured, customer-supplied, modeled, assumed, or unresolved. Only then compare visible outputs. A polished roof image or production total cannot show whether two providers designed from the same project basis.

Start by placing the exact documents side by side. Record the provider, proposal date, design revision, commercial option, and any referenced attachments. If the revision is not printed, ask for an identifier rather than inventing one. This prevents a later email attachment from silently replacing the version the customer actually reviewed.

Then assign an evidence state to each important field:

The labels are not grades. “Measured” does not automatically mean suitable, and “assumed” does not automatically make a proposal unusable. A preliminary layout may reasonably contain assumptions if the document says so and explains when they will be checked. The problem begins when a provisional value is presented with the visual confidence of a verified fact.

The U.S. Department of Energy’s homeowner guide identifies roof age, shape, slope, and tree cover as relevant residential context and encourages custom estimates and bid comparison. The U.S. Federal Trade Commission’s consumer solar guidance also recommends detailed written bids with important system and offer information. Neither source selects a provider. Both support asking what record sits behind the visible proposal.

Keep each provider responsible for explaining its own work. If a competing proposal has no visible shade record, write “shade basis not visible in reviewed documents; provider clarification required.” Do not rewrite that as “no shade analysis was performed.” The first sentence describes evidence. The second claims knowledge you do not have.

Agree on the customer’s decision before opening the eight-detail worksheet. Is the immediate choice whether to continue due diligence, request revisions, compare a backup option, or select a contract path after separate legal and commercial review? The design conversation can inform that decision. It cannot settle every issue surrounding an installer.

Which eight solar design details deserve a side-by-side review?

Review eight details in order: sizing basis, site and revision record, array placement, shade treatment, equipment configuration, production-model basis, electrical interface, and verification status. For each, compare the source, current value, evidence state, owner, and change trigger. The goal is to expose meaningful differences and questions, not to award points or force every design into one shape.

Use this map to control the conversation:

1. Project objective, usage record, and sizing basis

A system size is an answer to a question. The question might concern historical electricity use, a planned load, available roof area, an ownership constraint, backup priorities, or another customer-approved objective. If two providers answer different questions, their capacity and production figures should differ. That difference is not automatically an error.

Ask each provider to identify the usage record, the period it covers, missing intervals, customer-supplied corrections, planned loads, and the rule used to turn those inputs into a proposed size. Keep historical and future-load scenarios separate. A planned electric vehicle, heat pump, facility expansion, or operating-hours change should not be blended invisibly into historical consumption.

FTC consumer guidance says system sizing and power depend on energy use and characteristics of the home, including sunlight and roof attributes. That is general U.S. context, not a sizing formula. The customer’s practical question is: “What usage record and project objective does this design answer, and which future changes are included?”

Record who accepted the objective and what would reopen it. If a new utility bill changes the usage history, the team should identify whether the layout, equipment, production model, financial view, and proposal require revision. A sales note saying “customer wants maximum solar” is too vague to govern those changes.

2. Site source, roof geometry, roof zones, and revision

A roof model should be traceable to a site source. That could include imagery, drawings, field measurements, customer records, or a combination. The comparison needs the source date, capture method where available, roof boundaries, modeled planes, significant obstructions, excluded zones, and design revision. It does not need a sales representative to certify measurement quality.

Ask: “Which site information created this roof model, what has been verified, and which revision am I seeing?” If a provider used preliminary imagery and plans a later survey, that is useful information when clearly labelled. If another used a different source date, the customer now has a reason for a visible geometry difference without assuming that one designer failed.

Check whether attachments tell the same revision story. The proposal, roof image, module count, equipment list, and production page should identify the current option or be linked through a controlled project record. If the layout changed after a site visit but the proposal still displays the former count, stop the comparison and ask the owner to issue a corrected package.

The internal solar design review checklist goes deeper into technical release. In a customer meeting, stay at the evidence boundary: source, date, revision, status, and unresolved site conditions.

3. Array placement, orientation, tilt, access, and omitted areas

The array map reveals design choices that a capacity total hides. Compare which roof planes are used, module orientation, tilt where applicable, edge and access assumptions, obstruction treatment, equipment dimensions, and intentionally empty areas. Do not assume that the design with more filled roof area is more suitable. Different objectives and constraints can produce different layouts.

Ask each provider to explain two things: why modules occupy the shown areas and why other apparently available areas remain unused. An omitted area might relate to a known obstruction, access route, roof condition, customer preference, conservative preliminary boundary, equipment geometry, or a fact still awaiting review. The provider that owns the design should name the reason.

Separate the visible arrangement from later approval. A preliminary proposal graphic can support a customer conversation without being ready for engineering, permitting, procurement, or construction. The release label should say what the layout supports today. Applicable rules, qualified engineering, equipment requirements, site conditions, and authority review determine what can progress later.

Use neutral language when layouts differ: “Design A uses the east plane while Design B leaves it open. We need each provider’s stated reason and current evidence.” Avoid “Design B wastes roof space.” The neutral version creates a question. The second version invents a judgment.

4. Shade treatment and its supporting evidence

“Shade included” is not enough for a comparison. Record how shade was represented, which objects were included, the source and date, the modeled time basis, and any vegetation or site condition that still needs verification. A roof image with colored overlays may communicate the result while hiding the inputs that created it.

Ask: “What shade evidence is included in this design, what was excluded, and what site change would require a new analysis?” Keep current objects separate from hypothetical changes such as future tree removal. If a scenario assumes pruning or removal, show the assumption, responsible party, timing, and what happens if the change does not occur.

Do not compare shade percentages or production effects until the relevant basis is visible. Providers may use different geometry, object sets, source dates, time steps, or model settings. A numerical difference can reflect different inputs rather than a direct measure of design quality. The solar access walkthrough provides a fuller customer explanation of sun access and output.

Return the design to its owner when a new obstruction appears, a tree assumption changes, or field information conflicts with the model. The update may affect placement, production, equipment, and proposal outputs. The customer should receive a new revision rather than a verbal assurance that the old result still applies.

5. Module, inverter, storage, and configuration identity

Panel brand alone does not identify a system. Compare manufacturer and model references, counts, power ratings shown in the proposal, inverter architecture and model, storage option where present, and the configuration associated with the current design. Mark alternates as alternates. Do not let a representative describe a substitute as though the customer already approved it.

DOE’s PV system design overview describes modules alongside mounting, orientation and tilt, inverters, storage where relevant, and balance-of-system components. The page is educational and does not approve a pairing. It supports a simple comparison rule: identify the equipment and configuration behind the output instead of stopping at panel count.

Ask: “Which exact equipment and configuration are assumed here, and what changes if an item is substituted?” A responsible answer should connect the equipment choice to the layout, energy model, electrical work, equipment list, and proposal as applicable. Compatibility and compliance remain with qualified reviewers and the parties responsible for the project.

If a proposal uses “or equivalent,” request the approved substitution process and the fields that will be rechecked. The customer does not need an improvised promise that any equivalent item produces the same result. The useful record names who can approve a change and which outputs must be regenerated.

6. Modeled production basis, losses, period, and uncertainty

Projected production is a modeled result, not a standalone fact. Put the input basis beside the final figure: system capacity, module and array configuration, tilt, azimuth, shade treatment, loss inputs, location or weather resource, modeled period, scenario, and current revision. Then note unresolved conditions that could move the result.

NLR describes PVWatts as an estimator for grid-connected PV energy production. Its v8 documentation exposes inputs including capacity, module and array type, losses, tilt, azimuth, location or resource data, and model configuration. Those references show why model basis matters. They do not validate any proposal or guarantee future production.

Ask: “Which inputs create this estimate, what period does it cover, and which inputs may change after verification?” If two results use different system sizes, shade evidence, loss assumptions, or weather sources, label the basis difference before discussing the totals. Do not reverse-engineer an undisclosed competitor model from its final number.

Keep customer-facing language precise. Say “modeled annual production for this scenario” if that is what the document shows. Do not shorten it to “the system will produce.” If a contract, warranty, or guarantee contains a separate commitment, the responsible contract or legal reviewer should explain that document. The model should not acquire contractual force through a salesperson’s phrasing.

7. Electrical interface, locations, routes, and open service work

The electrical detail belongs in the comparison even when the design is preliminary. Record the connection concept shown, inverter and storage locations where relevant, major route assumptions, known service information, and work still subject to survey or qualified review. Do not turn a concept drawing into a permit or construction approval.

Ask: “What electrical work does this proposal show, what is conditional, and which review can change it?” The answer should distinguish visible included work, allowances, exclusions, and unresolved service conditions according to the provider’s approved documents. If the competing proposal does not show that boundary, record a question for its provider.

An equipment location can affect more than appearance. It may interact with routing, access, environmental conditions, manufacturer requirements, site preferences, and authority or utility review. The sales representative does not decide those requirements in the comparison meeting. The rep records the current location, its evidence state, and the role that must confirm it.

If later review changes a connection point, equipment location, route, or service assumption, identify every affected artifact. That may include the layout, electrical workflow, equipment output, cost or allowance, schedule, and proposal. The customer should be told which revision supersedes the former one and whether a decision must be reopened.

8. Verification state, open assumptions, revision triggers, and ownership

The last detail governs the other seven. Every design should state what it is ready to support now, which reviews are complete, which assumptions remain open, who owns the next answer, and what event triggers a revision. A proposal-stage design and an installation-ready package are different releases, even if both look polished.

Ask: “What can I rely on this design to support today, and which open item would send it back for revision?” Good status language is specific: customer discussion, revised proposal, internal review, qualified engineering review, permit preparation, procurement, or construction release, as applicable to the provider’s workflow. The label itself is not an approval.

Do not accept “final” without a named purpose and owner. Final for a sales meeting may still be preliminary for engineering. Also record the return condition. New usage data, roof measurements, shade evidence, equipment substitution, electrical findings, or customer scope changes can reopen affected work.

This is the detail most likely to preserve trust after selection. If the customer proceeds, the accepted revision, assumptions, open items, and promised answers should move into delivery. A clean handoff does not erase uncertainty. It gives each unresolved condition an owner and a controlled path back to review.

How should a sales rep guide the design comparison?

A sales representative should control the record, not the verdict. Confirm the customer’s decision, identify each document, walk through the eight details in the same order, separate evidence from questions, and close with owners and revision triggers. The rep may explain this company’s approved records but should send provider-specific questions back to the provider that owns them.

Use a five-step conversation. It is deliberately slower than flipping between headline production figures and faster than attempting a full engineering review at the table.

1. Define today’s decision. Write the choice the customer is trying to make and the condition that could postpone it. A useful statement is “The customer is deciding whether the design information is clear enough to continue commercial and contract review.” Do not write “choose the best company,” because the eight details cannot settle every provider question.

2. Identify the materials. List provider, document title, date, revision, option, and attachments for every design. Ask whether a newer version exists. Keep screenshots and detached roof images tied to their source package. If two documents from one provider conflict, stop treating them as one offer until that provider identifies the current record.

3. Compare the eight details in one sequence. Give each provider the same fields and customer question. Record what the document visibly says before adding an explanation. Mark the evidence state. Do not let the meeting become eight mini sales pitches in which every difference is reframed as a strength.

4. Separate answers from return items. An answer has a source and an owner authorized to explain it. A return item needs a question, provider, due point, and decision effect. If your own design has an open electrical condition, name it as plainly as the open field in a competing design.

5. Close the revision loop. Summarize confirmed differences, unresolved fields, and the evidence each provider must supply. Name which answers could change the layout, equipment, production estimate, electrical work, or proposal. Issue a new revision when your controlled record changes. Do not patch a material change into meeting notes alone.

The representative should use ordinary language while preserving technical meaning. “This annual figure is modeled from these inputs” is clearer than reading a simulation report aloud. “The equipment location remains subject to site and electrical review” is more useful than “engineering will handle it.” The first versions tell the customer what the record means and what happens next.

Keep a visible parking area for commercial questions. Price, finance, incentives, contract language, warranty administration, company licensing, reputation, service, and schedule deserve their own records and responsible reviewers. Routing those questions is not avoiding them. It prevents the design worksheet from becoming a loose scorecard that mixes unlike evidence.

The rep should also make corrections in real time. If your proposal labels an assumption poorly, say so, record the owner, and replace the document. A comparison process loses credibility when it treats your missing field as harmless but a competitor’s missing field as proof of poor practice.

What should happen when a design detail is missing or different?

When a detail is missing, label it “not visible in reviewed materials” and request provider clarification. When values differ, compare their source, unit, period, scenario, and revision before interpreting the gap. Send contradictions to the record owner, pause any dependent conclusion, and issue a controlled update when verified information changes an affected design or proposal output.

A missing field has several possible explanations. The provider may hold it in another document, plan to verify it later, use a different name, consider it outside the present release, or have omitted it. The reviewed material alone cannot tell you which explanation is true. Keep the status factual until the provider responds.

Use three checks when values differ:

• Identity: Are the documents current, and do they describe the same property, option, system, and customer objective?
• Basis: Do the values use the same source, unit, time period, equipment configuration, and scenario?
• Release: Have the values passed the same type of review, or is one preliminary and the other released for a later purpose?

If those checks do not reconcile the difference, preserve it as an open item. Do not average two system sizes, choose the higher production figure, or assume that a more detailed-looking page has passed deeper review. Visual density is not an evidence state.

Illustrative example, not a customer case: Two proposals show different module counts. The customer initially thinks one installer has used the roof more effectively. The worksheet reveals that Proposal A uses twelve months of historical usage, while Proposal B includes a customer-supplied future load. Proposal B also shows a roof plane that Proposal A marks for site verification.

The sales representative does not declare either design oversized or incomplete. The rep records the different objectives, asks each provider to confirm its usage basis, and requests the reason for using or withholding the roof plane. The customer decides to wait for both answers before comparing production. If your company’s future-load assumption changes, your design owner revises the affected layout and model.

The example shows why comparison language matters. “Proposal B has more panels” is an observation. “Proposal B is more suitable” is a conclusion that requires the customer’s objectives and other review. “Proposal A ignored usable roof” is an unsupported claim until its provider explains the omitted area.

Use the unequal solar quote warning checklist if several commercial and technical fields are missing at once. Use the quote-comparison mistakes guide when the conversation starts turning unequal numbers into a premature ranking.

What copy-ready solar design comparison record can customers use?

Use one record with the decision, document identities, eight design rows, evidence states, provider questions, owners, and revision triggers. Give the customer a clean copy after the meeting. The worksheet should preserve confirmed differences without scoring them, distinguish unresolved fields from exclusions, and state what each current design is ready to support before anyone relies on it.

Copy this worksheet into the opportunity record or customer meeting note:

Customer decision today:
Questions outside this design review:
Condition that pauses the decision:
Provider A, document, date, revision, option:
Provider B, document, date, revision, option:
Provider C, document, date, revision, option:
1. Objective and sizing basis: source, period, planned load, target, evidence state
2. Site and revision: source, capture date, roof model, zones, revision, evidence state
3. Array placement: used areas, omitted areas, orientation, tilt, obstructions, access
4. Shade treatment: source, included objects, time basis, assumptions, verification step
5. Equipment configuration: module, inverter, storage, counts, option, substitution process
6. Production model: capacity, array inputs, shade, losses, resource, period, scenario
7. Electrical interface: concept, locations, route, service record, conditional work, owner
8. Verification status: permitted use, completed reviews, open items, release owner
Confirmed design differences:
Details not visible in reviewed materials:
Provider clarification questions:
Our corrections or return items:
Answer owner and due point:
Answer that could change the customer decision:
Events that require a new design or proposal revision:
Current record issued to customer:

The worksheet is a comparison record, not an approval form. Do not add a weighted score unless the customer has defined the decision criteria and responsible reviewers have approved the method. Even then, technical, commercial, legal, contract, and provider diligence should not be collapsed into an unexplained total.

After the meeting, give every return item one of four states: answered with a source, awaiting provider clarification, returned for internal review, or no longer material to today’s decision. Keep the original question visible. This prevents a vague response from being recorded as resolution and makes it easier to explain why a later revision was issued.

For your own offer, connect the accepted answer back to controlled artifacts. A new roof dimension may affect the roof model and layout. A different module can affect geometry, equipment output, electrical work, and production modeling. A revised usage objective can change capacity and financial scenarios. The design owner decides the affected review path; the sales representative ensures the customer sees the current released record.

SurgePV’s solar design workspace supports 3D roof modeling, solar array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. Those functions can help a solar company keep design basis and proposal records connected. Results still depend on source data, assumptions, equipment models, configuration, and review.

SurgePV does not compare or rank installers, validate third-party quotes, decide which design a customer should select, or approve engineering, permits, interconnection, contracts, finance, or warranties. Its outputs do not replace decisions by responsible engineers, authorities, utilities, lenders, insurers, contract reviewers, or other qualified parties. Product access is through a guided demo, not an advertised self-serve trial.

The record has done its job when a customer can point to a difference and ask the right owner a precise question. It has not done its job if the meeting ends with a winner but no one can identify which project basis, revision, or unresolved condition produced that result.

Frequently Asked Questions

What is the first solar design detail a customer should compare?

Start with the project objective and sizing basis. Confirm which usage record, time period, planned load changes, and customer priority each provider used. Two systems with different sizes may answer different objectives. Until that basis is visible, panel count, projected production, and price per unit of capacity can create a false comparison.

Why can two solar installers show different roof layouts?

The providers may be using different imagery, measurements, roof boundaries, obstruction records, access assumptions, equipment dimensions, design revisions, or placement choices. A visible difference does not prove that either layout is wrong. Ask each provider to identify its site source, revision, omitted areas, assumptions, and the review still required.

How should customers compare solar production estimates?

Compare the model basis before comparing the final number. Record system capacity, equipment and array configuration, tilt, azimuth, shade treatment, loss inputs, weather or resource source, modeled period, and unresolved site conditions. Treat each result as an estimate under stated inputs, not as a guaranteed outcome or proof of design quality.

Does a missing design detail mean a solar quote is incomplete?

Not necessarily. It means the detail is not visible in the material being reviewed. Label it as provider clarification required, ask the provider for the current record, and identify whether the answer could change the design or offer. Do not convert an absent field into a claim about the provider’s scope, competence, or intent.

Can solar design software choose the best installer?

No. Software can help a solar company connect its own roof model, layout, shade work, equipment, energy model, electrical workflow, and proposal for review. It cannot validate another provider’s design, decide which customer tradeoff matters most, guarantee an outcome, or replace engineering, authority, utility, lender, insurer, contract, and warranty decisions.