Unequal Solar Quote Warning Checklist

Two solar quotes arrive for the same address. One prices a roof-only system from remote imagery. The other includes a battery, an electrical allowance, and a layout revised after a site visit. Their large totals look ready for a side-by-side chart. They are not ready for a ranking.

The first comparison question is not which quote wins. It is whether the quotes describe the same project closely enough for a price, production, savings, or financing comparison to mean anything. A fast warning screen prevents a sales representative from filling gaps, borrowing assumptions from the other provider, or turning a legitimate design difference into suspicion.

This unequal solar quote warning checklist owns that pre-comparison decision only. The complete guide to comparing solar quotes with different designs owns field normalization and tradeoff evaluation. The eight quote-comparison mistakes page owns the broader mistake taxonomy. Editors should consolidate these pages unless a separate warning-screen asset has a clear search and internal-workflow role.

The checklist produces one of three states: comparable, comparable with disclosed differences, or not comparable yet. It does not choose an installer, certify a design, interpret an agreement, recommend financing, or give engineering, legal, financial, tax, insurance, utility, permitting, warranty, or consumer-law advice.

What makes two solar quotes unequal before comparison?

Two solar quotes are unequal when they use materially different project identities, customer objectives, site records, design revisions, system boundaries, energy methods, scope definitions, commercial structures, time periods, or evidence states. A difference may be legitimate. It becomes a warning when the reviewer cannot identify the cause, source, owner, or effect on the proposed customer decision.

Start with project identity. Confirm the address, customer or account identifier, meter or facility boundary, ownership context, load record, roof or ground area, and requested job. A request for lower grid purchases, backup for named loads, a roof-only project, and a roof-plus-storage project are four different decision bases even when the same customer appears on every document.

Then confirm version identity. Record the site-data date, design revision, equipment revision, energy-model revision, commercial revision, and release state. A clean proposal can still be stale if the layout changed after its production chart, bill of materials, price, or customer image was generated.

NASA describes configuration management as a life-cycle discipline that provides visibility into and control over changes to functional and physical characteristics. A solar quote is not an aerospace system. The useful operating lesson is narrower: a reviewer needs to know which project configuration each customer-facing number represents.

DOE says in its homeowner solar guide that there is no universal solar solution and identifies the site, system, energy use, purchase or lease, utility rates, and treatment of excess generation as relevant conditions. Those conditions explain why two reasonable providers can produce different offers without either difference proving error.

Use the following screen before opening a price-comparison worksheet:

DOE’s photovoltaic system design basics describes a design through connected elements including modules, mounting structures, orientation, inverters, storage, and other balance-of-system technologies. That public overview does not validate a private design. It does show why a module count or one capacity figure cannot represent the whole project boundary.

Do not force every difference into a common value. One provider may omit a shaded plane, preserve another access route, specify storage for a documented backup job, or include work another provider leaves to the customer. The warning screen should reveal those distinctions and their consequences. Normalization begins only after the project definitions are visible.

Which warning signs require a hold instead of a ranking?

Hold the ranking when a missing, conflicting, stale, or unsupported field could materially change project identity, design, energy, scope, price, financing, customer obligations, safety, approval, or the meaning of a headline claim. A hold is also required when the sales representative lacks authority to reconcile the difference or cannot trace a value to its current source.

The hold applies to the affected comparison, not automatically to the entire customer conversation. A sales representative can acknowledge receipt, explain what is missing, request a narrow record, and name the next owner. The representative should not declare the other quote wrong or guess the favorable value while qualified review is pending.

FTC advertising and marketing guidance says advertising claims must be truthful, cannot be deceptive or unfair, and must be evidence-based. That is United States guidance, not a legal conclusion about a particular proposal. It supports a practical discipline: customer-facing comparisons need evidence at the point where the claim is made.

Financing deserves a separate stop rule. The Consumer Financial Protection Bureau’s August 2024 solar-financing issue spotlight discusses risks involving how solar-specific loans can present markups, fees, and confusing terms. It does not evaluate a current lender or customer offer. When finance structures differ, move the task to the financing-comparison guide and qualified reviewers.

Utility and savings assumptions need the same restraint. EIA explains that electricity prices reflect multiple factors and vary among customer types and locations. A quote that uses another tariff, customer class, escalation assumption, export treatment, or billing period may produce a different financial scenario from the same energy estimate. The sales representative should expose the difference, not decide which future assumption is correct.

Some differences should be disclosed rather than held. Different module brands, layout choices, service models, aesthetics, or warranty structures can remain comparable when each quote states the project consequence, evidence, and responsible party clearly. Use “comparable with disclosed differences” when the buyer can evaluate the real tradeoff without a missing load-bearing field.

The cost-per-watt tradeoff guide explains why one ratio cannot settle scope and design differences. Do not calculate a substitute ratio inside this warning screen. If source-bound price and capacity are not comparable, mark the ratio unavailable.

What records should a sales representative gather before screening?

A sales representative should gather the current quote files, project identifiers, customer objective, site and load records, design and equipment revisions, production basis, scope and responsibility schedule, price source, financing documents, warranty references, assumptions, exclusions, review state, and open questions. Gathering records is an intake job. Technical, contractual, financial, tax, and approval decisions stay with qualified owners.

The record request should be narrow enough to answer the warning. “Send everything” creates delay and still may not identify the controlling document. Ask for the exact design revision behind the annual production figure, the exact scope schedule behind the total, or the current lender document behind the opening payment.

Keep source and interpretation separate. A customer utility bill is a source record. A normalized consumption profile is a derived record. A proposed layout is a model object. A contract exclusion is a commercial term. A salesperson’s message about any of those items is not automatically the controlling evidence.

The FTC’s solar consumer guidance discusses system fit, costs, savings representations, purchase or lease structures, agreements, company questions, and pressure in the buying process. Its questions provide a useful intake frame. They do not validate a provider, offer, contract, financing product, or customer outcome.

DOE maintains solar resources for consumers that cover choosing and installing solar, rooftop potential, safety, and related decision subjects. Use public education to frame the questions, then use current project, provider, utility, lender, authority, manufacturer, and agreement records for the actual answer.

Assign one owner to every unresolved field. “Need finance details” is not owned. “Commercial coordinator requests the current financed amount and payment schedule from the named provider, then finance compliance reviews the customer view before release” is owned. Add the next event and the consequence if the record does not arrive.

Protect customer and commercially sensitive data. The comparison record rarely needs every personal field copied into a working sheet. Use controlled identifiers, restrict access, retain only necessary evidence, and follow the company’s privacy, security, consent, and retention rules. This article supplies no jurisdiction-specific privacy rule.

How do you run the unequal solar quote warning checklist?

Run the unequal solar quote warning checklist by fixing the customer decision, locking project and version identity, screening material fields, classifying differences, opening narrow evidence requests, assigning qualified owners, recording restrictions, and releasing one of three comparison states. Preserve both providers’ documented positions. The screen should make uncertainty visible without manufacturing a winner or delaying unrelated customer help.

Use one controlled record for the eight steps:

1. Name the decision. State what the customer is trying to compare now. It may be project scope, production basis, cash price, finance structure, service responsibility, or a documented bundle. Do not begin with “best quote.”

2. Lock project identity. Confirm customer, site, meter or facility scope, load record, objective, constraints, and option boundary. If the quotes solve different jobs, record that before reviewing totals.

3. Lock version identity. Record the site source date and the current design, energy-model, equipment, scope, price, finance, and proposal revisions. Expire screenshots, links, or attachments that represent older states.

4. Screen the load-bearing fields. Use the tables above to inspect system boundary, production basis, scope, commercial structure, customer duties, evidence state, and responsible reviews. Mark each field matched, different and disclosed, missing, conflicting, stale, or not applicable with a reason.

5. Classify each difference. A difference may be legitimate, explainable after a narrow record, material and unresolved, or outside the sales team’s authority. Do not use “red flag” as a verdict when the evidence supports only “different.”

6. Open the smallest useful request. Ask for the controlling document, source field, revision, method, or reviewer needed to resolve the warning. State why it matters and which comparison remains restricted.

7. Assign review and preserve restrictions. Give technical, finance, contract, tax, legal, warranty, utility, safety, marketing-compliance, and customer decisions to their responsible owners. Keep the affected ranking on hold until the disposition is recorded.

8. Release a comparison state. Use comparable, comparable with disclosed differences, or not comparable yet. Record the evidence cutoff, remaining unknowns, next action, release owner, and customer-safe wording. Then hand comparable offers to the full normalization process.

Use the following copy-ready operating record. Replace the brackets with controlled data. Do not publish it with blank fields, and do not convert a blank into zero, none, approved, or included.

Unequal solar quote warning record

Customer and controlled project ID: [record]

Decision being screened: [scope, production, cash price, finance, service, or other bounded decision]

Quote A provider, document, date, and revision: [record]

Quote B provider, document, date, and revision: [record]

Customer objective and site boundary shared by both: [yes, no, or unresolved with evidence]

Load-bearing fields screened: [identity, site, design, equipment, energy, scope, price, finance, utility, warranty, review]

Matched fields: [field, source, reviewer]

Legitimate disclosed differences: [field, provider basis, consequence, evidence]

Missing, conflicting, or stale fields: [field, affected comparison, current source state]

Narrow information request: [document, value, method, revision, or review needed]

Assigned owner and next event: [owner, action, event or date]

Restricted claims or rankings: [what cannot be said yet]

Current state: [comparable, comparable with disclosed differences, or not comparable yet]

Release owner, evidence cutoff, and customer-safe note: [record]

The output should be reconstructable. Another reviewer should be able to open the same source documents and understand why the state was released. If a later design, price, or finance revision arrives, reopen the affected rows instead of editing the conclusion alone.

How should missing information and legitimate differences be handled?

Handle missing information as an owned evidence request with a visible restriction, while preserving legitimate differences as documented tradeoffs rather than defects. Never fill a blank from another quote, assume the most favorable value, or pressure providers into identical designs. When the missing field could change the customer’s decision, keep the affected ranking at not comparable yet.

A useful request contains five parts: the exact missing field, the controlling record requested, the reason it affects comparison, the owner who will review it, and the statement that remains restricted. This gives the provider a fair chance to answer without accusing it of misconduct.

For example: “The annual-production figures cannot be compared yet because Quote B does not identify the design revision, model period, or shade basis behind its estimate. Please provide those fields from the current proposal record. Our energy-modeling reviewer will inspect the basis before we compare production.” That language describes the gap and next step. It does not declare the estimate inaccurate.

Legitimate differences need equally careful treatment. If one option omits a shaded plane and another includes it, retain the provider’s documented design basis, resulting capacity and energy implications, and evidence state. The customer may then compare the design thesis after qualified review. The screen does not force both providers to use the same module count.

Illustrative workflow, not a customer case

An illustrative residential comparison arrives with two current quotes. Both use the same address and load record. Quote A proposes a roof-only system and labels its layout as remote and preliminary. Quote B includes storage for named backup loads and uses a post-visit revision. The prices and production totals differ.

The representative first marks project objective as conflicting because one offer includes a backup job. The representative does not remove the battery price mentally or divide both totals by module capacity. Instead, the customer confirms that backup is an option, not a required base-case outcome.

The team requests a roof-only base case from Quote B or a clearly separated storage option. Design review confirms each current layout basis. Energy modeling records the corresponding revisions and output periods. Commercial review separates base project scope, option scope, cash price, and finance documents. The representative avoids choosing a winner.

The resulting state is comparable with disclosed differences for the roof-only base cases. Storage remains a separate option. Different layouts remain visible because each provider documents another placement choice. This example contains no real customer, price, production result, provider judgment, or approved design.

SurgePV can help keep connected project objects closer together. The repository source of truth 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 functions can support consistent internal scenarios and revision-aware proposal work.

SurgePV does not compare third-party providers, establish customer intent, validate another company’s quote, determine finance eligibility, interpret a contract, decide tax treatment, approve engineering, or make utility and permitting decisions. Results depend on source data, assumptions, equipment models, configuration, and responsible review. External approvals remain with the qualified professional, lender, insurer, utility, or authority that controls them.

Keep the editorial overlap visible too. This page has a narrow workflow role, but it still shares audience and vocabulary with the full non-equivalent-quote guide and the broad comparison-mistake page. A human content strategist should decide whether to index it separately, consolidate its warning asset into the stronger page, or use it as a noindex internal enablement resource.

Frequently Asked Questions

What is the first sign that two solar quotes are unequal?

The first sign is a mismatch in project identity or customer objective. Confirm the same address, meter or facility boundary, load record, roof or ground area, storage job, design revision, and requested outcome before discussing price. If those foundations differ, the quotes describe different projects and should not be ranked yet.

Should a sales rep calculate price per watt to compare unequal quotes?

No calculation should be improvised from incomplete fields. Price per watt can describe a defined price and capacity relationship only after both quotes use the same units and comparable scope. Storage, roof work, electrical upgrades, financing charges, exclusions, warranties, and review status can remain different even when the ratio is calculated correctly.

What should happen when a solar quote omits production assumptions?

Mark production as not comparable yet and request the design revision, capacity basis, model and version, resource and shade inputs, principal loss assumptions, analysis period, and output units. Do not insert another provider’s values or apply an arbitrary discount. Route material production questions to the responsible design and energy-modeling reviewers.

Can legitimate differences remain after the warning screen?

Yes. Providers may propose different equipment, layouts, scope, financing, service, or review paths for documented reasons. The screen should preserve those differences, identify their evidence and consequences, and classify the offers as comparable with disclosed differences when appropriate. It should not force identical designs or turn every difference into a red flag.

Can SurgePV decide which solar quote is better?

No. SurgePV supports solar array layout, shading analysis, energy-yield and financial modeling, electrical workflow, bill-of-materials output, and proposal generation. It does not validate a third-party quote, select an installer, approve a design, interpret financing or contracts, or replace qualified engineering, legal, financial, tax, utility, permitting, or customer review.

Release the comparison only after the warning is resolved

The most useful sentence a sales representative may say is “these offers are not comparable yet.” It is useful only when followed by the exact missing field, a fair request, an owner, and a bounded next step. Otherwise the hold becomes another vague delay.

Release comparable when the load-bearing fields match closely enough for the stated decision. Release comparable with disclosed differences when real tradeoffs remain visible and supported. Keep not comparable yet when a missing, conflicting, stale, or authority-sensitive field can still change the ranking.

The warning record is not the final comparison. It is the control that stops a polished side-by-side chart from answering a question the source documents never supported.