Apples-to-Apples Solar Quote Comparison Checklist

Two solar quotes can share an address and still describe different projects. One may use a remote layout, another a site-verified revision. One may include electrical work, another an allowance. One may show cash price, another an opening payment from a financed offer. Putting those headline values in adjacent columns creates symmetry on the page, not comparability in the evidence.

An apples-to-apples comparison does not force providers to design the same system. It gives each material difference a common field, source, unit, evidence state, owner, and customer consequence. The customer can then compare documented tradeoffs without treating a blank as zero or a polished claim as proof.

Use the unequal quote warning checklist first. It decides whether a missing or conflicting field should stop the ranking. The non-equivalent solar quote guide explains the wider decision process. This article owns the normalization worksheet that follows a successful screen.

This is buyer-supporting information, not engineering, legal, financial, lending, tax, safety, warranty, utility, permitting, contract, or consumer-law advice. It does not choose a provider, declare a quote accurate, or promise project, production, savings, price, approval, or financing results.

What makes solar quotes comparable on an apples-to-apples basis?

Solar quotes become comparable when they describe the same bounded customer decision with traceable fields, compatible units, current revisions, disclosed assumptions, and visible differences. The offers do not need identical equipment or designs. They need enough shared structure for the buyer to understand which variation changes scope, evidence, risk, responsibility, price, or expected use.

Start with the decision. “Which quote is best?” is too broad. A customer may need to compare roof-only base projects, a storage option, service responsibilities, cash offers, finance structures, or production methods. Each is a different comparison view.

The U.S. Department of Energy’s Homeowner’s Guide to Solar discusses site conditions, roof and shade, energy use, ownership arrangements, installer selection, utility treatment, and other considerations. It does not validate a private quote. It supports the principle that a solar offer is conditional on more than one headline price.

Classify every comparison row:

• Matched basis: source fields and units describe materially the same decision.
• Comparable difference: the difference is documented, understood, and can be evaluated as a tradeoff.
• Needs normalization: a conversion, separation, or current source record is needed.
• Not comparable yet: missing, conflicting, stale, or authority-sensitive evidence can change the conclusion.
• Not applicable: the field genuinely does not belong to that option, with a stated reason.

Do not use blank, zero, “included,” or “standard” interchangeably. Blank means no usable value is present. Zero is a source-supported numeric value. Included means the quote assigns the item to its scope. Standard needs a named specification before it can support comparison.

The FTC’s consumer solar guidance tells shoppers to examine claims, agreements, companies, and payment arrangements. A comparison worksheet should link to those current records. It should not paraphrase them until material conditions disappear.

Which fields belong in a solar quote comparison checklist?

Include nine field groups: customer decision and project identity, site and load evidence, design and capacity, equipment and configuration, modeled energy, work scope and responsibilities, price and financing, warranties and service, and review or approval state. Each row needs a source, revision, unit, assumption, owner, and unresolved-condition field.

1. Customer decision and project identity

Record the customer or controlled project identifier, site, meter or facility boundary, building or land area, usage record, base-project objective, optional objectives, constraints, and decision date. Keep a base solar project separate from storage, roofing, EV charging, service upgrades, or other optional work unless the customer intentionally wants a bundle comparison.

If one quote addresses a different meter, building, ownership structure, load period, or backup objective, mark the difference before any price work. Do not “adjust” it away. Ask the customer to confirm the intended decision and have the responsible team update the project record.

2. Site and load evidence

List imagery, survey, photos, drawings, utility data, bills, interval data, observation dates, source identity, and evidence state. Remote and field-verified inputs may both be useful at different stages, but they do not carry the same verification meaning automatically.

Record missing or conflicting evidence rather than choosing the value that makes a cleaner comparison. A quote can remain preliminary while a provider awaits a survey. The worksheet should show the release limit and next verification.

3. Design, capacity, and system boundary

Record the current layout and revision, design release state, module count, DC capacity, inverter AC capacity, DC-to-AC relationship where supplied, storage power and energy separately, mounting context, relevant orientations, and other system boundaries. Do not add battery energy to PV power or compare an AC value with a DC value.

DOE’s PV system design basics describes connected elements such as modules, mounting, orientation, inverters, storage in some systems, and balance-of-system components. That overview does not approve either design. It explains why module count or nominal capacity alone cannot stand for the complete system.

4. Equipment and configuration

Capture manufacturer, model, rating basis, quantity, configuration, substitution terms, relevant certifications or documents, current availability state, and who provides or warrants the item. A brand name is not a complete equipment comparison.

Do not score equipment from marketing claims alone. If a difference matters to performance, compatibility, service, safety, code, warranty, or customer preference, route the exact question and documents to the responsible reviewer.

5. Energy model and output

Record the design revision, model and version, weather or resource basis, time period, shade method, equipment assumptions, loss categories, availability assumptions, degradation treatment where used, output units, and reviewer state. Keep modeled energy separate from measured past usage and future savings.

Two annual values can use different system sizes, weather files, shade treatments, loss assumptions, or reporting periods. Do not normalize by applying an arbitrary percentage. Ask each provider for the current basis, then have a qualified reviewer decide whether the outputs can be interpreted together.

6. Work scope, responsibilities, and exclusions

Create a responsibility matrix for design, surveys, engineering, permitting support, utility coordination, equipment, electrical upgrades, civil or roof work, installation, access, restoration, commissioning, monitoring, training, documentation, and service as applicable. Use included, allowance, excluded, customer-supplied, third-party, and unresolved.

“Turnkey” is not a substitute for the matrix. The word may sit over different assumptions. Preserve the current agreement or proposal language and route interpretation conflicts to authorized contract and legal reviewers.

7. Price and financing

Keep cash price, taxes, allowances, optional items, change mechanism, offer validity, deposits, payment events, and exclusions distinct. For financing, record the provider, current document, financed amount, fees, interest and payment terms, security features, conditions, dates, and responsible party only where supplied and appropriate.

The Consumer Financial Protection Bureau’s solar-financing issue spotlight discusses solar-financing structures and reported risks, including markups, fees, and confusing terms in some arrangements. It does not evaluate a current offer. Do not compare an opening monthly payment with a cash total or another loan without current documents and qualified review.

8. Warranties, service, and operating support

Record the provider, covered product or work, term, start event, exclusions, transfer conditions, claim path, labor or shipping treatment, monitoring responsibility, response commitment where documented, and current source. Several warranties may exist across manufacturer, installer, financier, or another party.

Do not collapse every warranty into the longest duration. The provider and coverage matter. A duration without the current terms cannot support a responsible comparison.

9. Evidence, review, and external decisions

For every material field, show whether it is customer-stated, observed, measured, modeled, assumed, quoted, reviewed, approved by a named role, pending, expired, contradicted, or unavailable. Separate company review from decisions controlled by engineers, lenders, insurers, utilities, authorities, manufacturers, and customers.

A proposal may look final while permitting, interconnection, structural, electrical, finance, or site questions remain open. The worksheet should preserve those states instead of turning proposal polish into an approval signal.

How do you run the apples-to-apples quote checklist?

Run the checklist by naming one customer decision, freezing current quote revisions, screening for blocking differences, mapping both offers to the same fields, normalizing only compatible units, routing specialist questions, recording unresolved evidence, and releasing a comparison state. The output should explain differences and restrictions without scoring providers or manufacturing a winner.

Use this ten-step sequence:

1. Define one comparison decision. Choose base project, storage option, production basis, cash scope, financing structure, warranty, or another bounded question.
2. Confirm project identity. Match the customer, site, meter or facility, load record, objective, option boundary, and constraints.
3. Freeze source packages. Record each quote, date, revision, design, equipment, model, scope, price, finance document, and evidence cutoff.
4. Run the unequal-quote screen. Hold any affected ranking when a missing or conflicting field can change the decision.
5. Populate the common field map. Transcribe source values, units, states, assumptions, and owners without silently interpreting blanks.
6. Normalize compatible units. Record the conversion formula, original value, unit, result, and reviewer. Do not normalize unlike scope or authority.
7. Classify every difference. Use matched basis, comparable difference, needs normalization, not comparable yet, or not applicable with a reason.
8. Route qualified decisions. Assign technical, finance, contract, tax, legal, safety, warranty, utility, permitting, and customer questions appropriately.
9. Write customer-safe explanations. State the fact, source, consequence, unknown, and next action without attacking a provider or claiming superiority.
10. Release and version the record. Name the comparison state, owner, evidence cutoff, permitted use, restrictions, next review, and superseded version.

Copy-ready apples-to-apples comparison worksheet

Attach source links, not screenshots without identity. Another reviewer should be able to open each current document and reproduce the state. If a later revision arrives, reopen only affected rows, update connected conclusions, and preserve the earlier version.

A reproducible unit-normalization check

Hypothetical values, not actual offers: Quote A lists 12 modules rated 450 W at STC, giving 12 × 450 = 5,400 Wdc = 5.4 kWdc. Quote B lists 5.4 kWdc. The declared DC capacities match after conversion, but this does not establish equivalent roof placement, inverters, energy, installation scope or evidence quality.

If both declared solar-only cash scopes genuinely match and each is 10,800 currency units, their declared ratio is 10,800 / 5,400 = 2 currency units/Wdc. If one total includes storage or another excluded work item, keep that bundle separate rather than inventing a subtraction. The calculation normalizes units; it cannot approve or rank either offer.

How should price, production, and savings differences be presented?

Present price, production, and savings as separate layers with their own sources, units, periods, assumptions, and limitations. Explain which design or scope created the difference, keep cash and finance structures distinct, and preserve uncertainty. A ratio or chart may summarize comparable inputs, but it must not erase equipment, responsibility, evidence, or approval differences.

Price

Start with scope parity. A lower total may exclude work, use an allowance, depend on customer action, or omit an option. A higher total may include work the customer does not need. Neither fact chooses the quote until the buyer understands the boundary.

Price per watt can be computed only from a declared price and compatible DC capacity. It still does not value storage, roofing, electrical upgrades, civil work, service, finance, warranties, or evidence quality. The cost-per-watt tradeoff guide explains that narrower use.

Do not create a “normalized price” by subtracting estimated values from another provider. Ask for separated option and allowance records. If the provider does not supply them, mark the field not comparable yet or compare only the supported bundle.

Production

Present modeled production beside capacity, layout, resource, shade, loss, period, and version. Do not convert modeled annual energy into guaranteed output. If one quote uses another model period or treatment, show the difference or request a comparable run.

Do not rank model quality from one headline result. A lower forecast may reflect a smaller system, conservative loss treatment, another shade basis, or different reporting boundary. A qualified energy-modeling reviewer should inspect the actual inputs and method.

Savings

Savings adds consumption, tariff, export, fixed charges, timing, escalation, future load, equipment behavior, finance, and other assumptions to the energy layer. Keep it separate so a disagreement in money is not misreported as a disagreement in production.

The U.S. Energy Information Administration explains that electricity prices reflect multiple factors and vary across locations and customer types. EIA does not select a tariff or future rate for a quote. Record each source and assumption and route current utility treatment to responsible reviewers.

Use a customer-facing explanation pattern:

Observed difference: [current source values and units].
Mechanism: [design, scope, model, tariff, finance, or other documented basis].
Customer consequence: [decision this changes].
Still unknown: [missing evidence or external decision].
Next action and owner: [request, review, or customer decision].

This pattern can explain a difference without using “better,” “worse,” “premium,” or “cheap” as substitutes for evidence.

Illustrative workflow: roof-only base case plus storage option

Illustrative workflow, not a customer case, quote, provider assessment, calculated result, or recommendation. Two residential offers use the same address and annual load record. Quote A shows a roof-only base project. Quote B bundles a roof project with storage sized for a stated backup objective. Their headline prices and capacity labels differ.

The reviewer does not subtract an assumed battery price from Quote B. The worksheet marks the option boundary not comparable yet and requests a separated roof-only base case or an itemized option from the provider. It also records PV DC capacity separately from battery power and energy.

Once both base cases are available, design records show different module placements. Each provider supplies its current layout revision and modeled energy basis. The technical reviewer preserves the different design theses rather than forcing an identical count. Scope rows reveal that one offer includes an electrical allowance while the other marks the work unresolved.

The base projects can be released as comparable with disclosed differences. Storage remains a separate customer decision. The electrical work remains an unresolved price and scope condition. No provider is ranked, and no unknown value is entered as zero.

Where SurgePV fits in quote normalization

SurgePV supports 3D roof modeling, solar array layout, shading analysis, energy-yield and financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. Those connected functions can help an installer keep its own scenario inputs and customer-facing output on a traceable revision.

Use the solar design review checklist to define internal review levels before presenting a scenario as current. Test changes in layout, equipment, shade, energy, electrical work, BOM, financial assumptions, and proposal output. Confirm that the affected objects update together and that superseded customer links are controlled.

SurgePV does not validate a third-party quote, determine customer intent, interpret contracts or warranties, recommend financing, verify tax treatment, approve engineering, or decide permit and utility outcomes. It cannot fill missing competitor evidence or choose an installer.

Results depend on source data, assumptions, equipment models, configuration, and review. Confirm software access, implementation, pricing, and commercial terms through a written quote. Human review remains required because quote comparison can affect technical, financial, contractual, and customer decisions.

Evaluate the solar designing workspace with two intentionally different internal scenarios. Change the target roof, module count, inverter configuration, shade basis, equipment selection, energy assumption, and optional scope one field at a time. Confirm that the proposal identifies the correct revision and that a reviewer can trace every displayed value back to its active project object.

Then test an incomplete case. Remove a load record, leave an electrical allowance unresolved, or return the design for more site evidence. The system should preserve the missing state instead of generating a customer-safe conclusion from a blank. This is a workflow acceptance test, not proof that the resulting design, price, production model, customer comparison, or external approval is correct.

Frequently Asked Questions

What should be compared first in two solar quotes?

Compare project identity and the customer’s decision first: the same site, meter or facility boundary, load record, roof or land area, base project, optional storage or other additions, and requested outcome. If those foundations differ, normalize the project definition or keep the offers visibly separate before comparing price or production.

Can price per watt make solar quotes comparable?

Price per watt can describe a declared price divided by a declared DC capacity, but it cannot normalize storage, electrical work, roofing, trenching, finance charges, warranties, service, exclusions, design evidence, or review state. Use it only after units and scope are comparable, and never let the ratio choose an installer.

How should production estimates be compared between solar quotes?

Record each design revision, capacity, model and version, resource and weather basis, shade method, loss assumptions, analysis period, degradation treatment, and output units. Compare results only after responsible technical review establishes a sufficiently similar basis. Do not copy assumptions between providers or present modeled production as guaranteed output.

How should financed and cash solar quotes be compared?

Keep cash price, financed amount, fees, interest and payment terms, security features, conditions, offer dates, and responsible parties in separate fields from design and energy. Compare current written documents on the same financing basis where possible. Route affordability, suitability, legal, lending, tax, and contract questions to qualified reviewers.

Can SurgePV rank competing solar quotes?

No. SurgePV supports solar modeling, design, electrical workflow, bill-of-materials output, financial modeling, and proposal generation. It does not validate a competitor’s documents, select an installer, interpret contracts or financing, approve engineering, predict utility action, or replace customer judgment and qualified technical, legal, financial, tax, safety, and jurisdictional review.