11 Solar Proposal Software Mistakes: Pre-Send Review Checklist

Proposal software can produce a polished document while the inputs, scope or revision remain wrong. Use this eleven-point review to find those problems before sending. It is a quality-control framework, not evidence that fixing a particular item guarantees a higher close rate.

Scope and evidence

SurgePV publishes this guide and sells solar software. Sources were checked on September 30, 2026. We have not conducted the original article’s claimed hundreds-of-proposals review or measured industry conversion, mobile-review shares or signing-time benchmarks. The checks below retain its useful eleven topics with practical evidence and explicit limits.

1. Unverified shading inputs

A roof image alone cannot establish obstacle heights, vegetation or a complete shading scene. Check source dates, geometry, horizon and relevant obstructions. PVsyst’s shading documentation distinguishes shading methods and their model treatment; it does not establish one universal error for every project.

Retain the scene, assumptions and production revision. If the site evidence is incomplete, identify that limitation instead of turning a preliminary model into a promised output. A production difference can also arise from weather, equipment, outages or other losses; shading is not automatically the cause.

2. Seasonal assumptions copied from one observation

An image or visit at one date and time is not a year-round shading result. Check the appropriate sun path, obstructions, vegetation assumptions and time treatment for the actual site. Do not use a fixed December-versus-June percentage as a universal climate rule.

Show monthly production if it helps explain the model. Separate an expected seasonal pattern from a guaranteed monthly delivery. Use the shade-report reading guide to organize the explanation.

3. Financial results without their inputs

State price, energy, tariff, export settlement, financing, operating costs, horizon and any assumed escalation or degradation. Bill reduction, cash flow, payback and NPV answer different questions. Include the outputs the customer and reviewer actually need rather than imposing a universal 25-year chart or every financial metric.

Test a flat-rate-escalation scenario where relevant. Separate conditional benefits from the base case. The lease/buy decision guide explains why ownership and payment structures must remain explicit.

4. An unreadable delivered document

Open the actual delivered proposal on intended devices. Check text, tables, controls, downloads, keyboard access and links. A PDF can be readable; an interactive page can be broken. The file format alone does not establish a customer’s experience.

Retain a saved version with the terms and values actually presented. Ask whether the customer can review and share it without losing context. No current mobile-review percentage or signing-delay estimate is established here.

5. Alternatives without a decision framework

Offer alternatives that answer the customer’s real questions, such as different scope, ownership or storage objectives. Explain the constraints and tradeoffs on consistent assumptions. There is no universal rule that two options convert while three do not.

Identify the recommended configuration and its basis, then show material alternatives where appropriate. Avoid an adjustable size slider that appears to authorize a configuration without the necessary design checks.

6. An unclear acceptance route

Explain what accepting the proposal means and which separate contract, review or conditions apply. If electronic signature is used, test identity, document version, countersignature, confirmation, retention and retrieval under the applicable process.

A third-party signature service is not inherently broken, and a native signature button does not automatically establish legal sufficiency. This review does not establish embedded SurgePV signatures or a universal conversion uplift from them. Confirm current product scope and applicable requirements.

7. Stale equipment, availability or warranty

Verify the actual manufacturer model and current regional documents. Check rating, configuration, availability evidence and warranty terms separately. A software database entry does not prove stock or that the quoted warranty covers the installation.

If equipment changes, review dependent layout, electrical, energy, BOM and proposal fields. Preserve the old version and release the revised one clearly. Use the material-change checklist.

8. Unverified or outdated incentives

For a new U.S. homeowner project in 2026, do not automatically apply the old 30% federal credit. Current IRS residential guidance states that the credit is unavailable for expenditures after December 31, 2025. Prior eligible credits and carryforwards are separate questions; commercial or third-party ownership requires a different review.

For state, utility and certificate programmes, verify status, technology, customer criteria, dates, application stage and settlement. A ZIP code lookup or a maximum advertised amount is not an approved award. Use the source-linked incentive finder for administrator discovery, then document actual eligibility and remaining conditions.

9. Company identity or proof that cannot be verified

Include the correct business name, contact, responsibility and relevant documents. Use real installation images and customer material only with appropriate rights and permission. Do not invent testimonials, credentials or local experience to fill a template.

The FTC’s advertising guidance discusses truthful claims and substantiation in the U.S. Its principles do not make a specific proposal approved or replace local requirements. A polished brand alone does not prove installation quality.

10. Follow-up without an agreed purpose or owner

Record the customer’s questions, preferred channel, next action and owner. Respect withdrawal and relevant communication rules. A scheduled reminder can help the team; an automated sequence is not mandatory for every customer.

An open event may have several causes and does not prove readiness to buy or permission for a late-evening message. Use genuine dates and constraints; do not manufacture urgency from unavailable equipment or an unverified incentive deadline.

11. A template that hides the customer’s actual decision

Match the explanation to known objectives and the actual project. Do not infer priorities from age or a broad customer segment. A homeowner may need ownership and monthly-cost clarity; a commercial reviewer may need tariff, procurement or lifecycle detail. Ask rather than assume.

For demand charges or storage, establish the interval and tariff method needed by that customer. No generic annual solar production figure proves a demand reduction. Keep tax and financial advice with the responsible reviewer.

Pre-send evidence checklist

• Project, equipment, design and proposal revisions match.
• Production inputs and unresolved site assumptions are visible.
• Financial inputs, conditional benefits and exclusions are stated.
• Equipment and warranty documents match the quoted scope.
• The delivered document is readable and its links work.
• Customer identity, acceptance conditions and next steps are clear.
• Supporting images, testimonials and claims have retained evidence.
• Changes and follow-up have named owners and appropriate boundaries.

Record failures, corrections and receiving-owner acknowledgement. Matching documents is useful but is not engineering approval, a permit or utility authorization.

Measure the cost of an error without inventing lost sales

Track observed rework, direct charges and confirmed outcomes. Illustration: Three corrected proposals each requiring two hours of work total six hours. At an assumed $40 hourly cost, that is $240 of allocated labour cost, before other expenses. It is not proof of cash avoided or lost contract revenue.

Do not multiply an assumed ten-point close-rate increase by contract price and present the result as the cost of a software mistake. Conversion depends on other factors and needs its own evidence. The quote-software buyer guide can help evaluate the workflow.

Request a SurgePV proposal demonstration against your actual requirements, using the proposal, design and financial workflow pages to prepare questions. Confirm supported outputs and handoffs rather than assuming automatic incentive verification, follow-up tracking or a shade-to-signature process.

Frequently Asked Questions

What solar proposal software mistakes should I check first?

Check source and revision consistency, shading and production assumptions, financial inputs, delivered-document readability, acceptance conditions, equipment and incentives. Keep customer questions and unresolved decisions visible. This is a quality review, not a proven conversion ranking.

Does a shade error explain every production shortfall?

No. Check geometry, obstruction and seasonal assumptions, but also reconcile weather, as-built equipment, outages, curtailment and other losses. A model difference needs investigation; it does not establish one universal shading penalty or a guaranteed bill impact.

Must every proposal use interactive output and native e-signature?

No. Test the actual delivered document and acceptance process for the customer and applicable requirements. A PDF can be readable, and a third-party signature service can be appropriate. A native button does not automatically establish legal sufficiency or higher conversion.

Should a 2026 U.S. homeowner proposal include an automatic 30% federal credit?

No. Current IRS guidance states that the residential credit is unavailable for expenditures after December 31, 2025. Prior eligible credits and carryforwards are separate questions; commercial and third-party ownership need a different review. Other incentives require current programme and customer verification.

How do I calculate the cost of proposal mistakes?

Track observed correction work, direct charges and confirmed outcomes. Keep allocated labour value separate from cash avoided. Do not assume that a lost sale was caused by software or present an unmeasured close-rate increase as recoverable revenue.

Does SurgePV automatically prevent all proposal mistakes?

That claim is not established by this review. Request a demonstration of the actual outputs, revision behaviour and handoffs required by your team. This guide does not verify native signatures, automatic incentive eligibility, follow-up tracking or guaranteed conversion results.