Back to Blog
solar sales19 min read

6 Ways a Solar Proposal Can Drift After a Site Visit

Find six gaps between a solar site visit and the final proposal. Use a simple record to catch each change and explain it before you send.

Akash Hirpara

Written by

Akash Hirpara

Co-Founder · SurgePV

Rainer Neumann

Edited by

Rainer Neumann

Editorial contributor · SurgePV

Published ·Updated

Answer

A proposal drifts after a site visit in six ways. Field notes become cleaner assumptions, the layout changes without explanation, discussed equipment is swapped, models use different inputs, site conditions drop out of scope, and rough timing becomes a promise. Match each item to dated evidence, give open decisions an owner, and explain real differences before you send.

Last updated: November 2026

SurgePV publishes this post and sells solar proposal software.

The six drift points to check before you send a proposal after a site visit:

  1. Field observations become cleaner design assumptions.
  2. The layout changes without a customer-facing explanation.
  3. The equipment shown or discussed is replaced.
  4. Production or financial scenarios use different inputs.
  5. Scope, exclusions and site conditions disappear.
  6. Timing, approval or next-step language hardens into a promise.

Illustrative scenario, not a customer case: The customer remembers walking the property with the sales rep. They remember pointing at the clean roof plane (one flat face of the roof), asking where the inverter might go, and hearing what would happen next. Days later, the proposal arrives with a polished layout and exact-looking figures. It can still feel like a different project.

That mismatch is not always a mistake. Design review may find an obstruction that was hard to see from the ground. Equipment availability may change. A production model may use a better source than the first talk did. Trust breaks when a real change arrives with no reason. The proposal then shows the new state as if everyone had discussed it on site.

Call this site-to-proposal drift. It is a difference between what you discussed at the visit and the later customer document. That covers the property, the customer’s wishes, limits, assumptions, and next steps. It is not the same as proposal version control. The solar proposal version-control guide covers document identity, revision labels, change summaries, and the status of older copies. This guide covers the check you should run before the first proposal after a visit. Run it again whenever site information changes.

The check is called reconciliation. It means matching the proposal against what the visit record shows. The goal is not to put every field note on every proposal page. The goal is to make sure the proposal does not contradict what the customer saw. It also should not quietly drop an important condition. A sales rep should be able to explain what carried over, what changed, and why. They should also say what is still open and what the customer must decide now.

Use this guide together with the approvals and qualified reviews that your location, project, and documents require.

Keep the proposal tied to the site record

SurgePV supports roof modeling, layout, shading, yield and financial modeling and proposal generation in one project, so the proposal starts from the design, not a copy of it.

Book a Demo

Checking cost first? See the SurgePV pricing page.

If the visit turned up findings that should change how you sell, read site visit findings that change the conversation first. This guide starts once you are building the proposal.

Why does a solar proposal drift after the site visit?

A proposal drifts because many people make its pieces at different times. These pieces are the site talk, the field evidence, the design model, the equipment choice, the pricing scenario, and the customer document. Each handoff can simplify a note, swap an input, or close an open question. Without a matching step, the polished document hides this path. That hidden path is where buyer expectations split from the proposal.

A site visit produces several kinds of information at once. Some items are observed facts, such as an obstruction you can see in a dated photo. Some are customer statements, such as a preferred spot for the equipment. Some are early ideas, such as a possible panel layout you discussed while looking at the roof. Others are questions for a designer, electrician, engineer, roofer, utility, authority, lender, insurer, or other responsible party.

These kinds of information should not move downstream with equal weight. “Customer prefers the east wall” is a valid record of a wish. It does not prove the spot is suitable. “Rep showed panels on the south plane” records what the customer saw. It is not an approved layout. A good workflow keeps both the original statement and its decision status.

The U.S. Department of Energy’s homeowner solar guide says roof age, tree cover, roof size, shape, and slope can affect how well a roof suits solar. It tells readers to work with an installer for a custom production estimate. DOE’s separate PV system design overview explains that a full PV (solar panel) system has more than modules. Mounting and power electronics are part of the system. Some systems also have storage.

Before you build the proposal, sort every important site item:

Site-item state What the record can say What it cannot prove Release action
Observed and identifiable What was seen, where, when, and in which evidence A hidden condition, suitability, or technical effect without review Send it to the right proposal field and reviewer
Stated by the customer The customer’s wish, plan, limit, or supplied facts Ownership, permission, technical fit, or future certainty Name the source and test the affected assumption
Discussed as an option The early idea the customer saw or heard Final layout, equipment, output, price, or approval Label it preliminary and match it to the developed option
Inferred for a scenario The assumption, its source, its purpose, and the outputs it affects A confirmed site fact or a guaranteed result Keep the assumption visible and set a trigger to check it
Open for responsible review The decision needed, the evidence on hand, and the role in charge A conclusion outside the recorder’s authority Limit release or explain the dependency until it is settled

The solar project intake process helps a team define a usable project request before work starts. Matching the proposal to the site visit is a later control. It asks one question. After field evidence and later reviews changed the request, does the document you are sending still represent it?

What are the six ways a proposal can differ from what the customer saw?

Check six drift modes on purpose. Field observations become design assumptions. The array layout changes. Equipment changes. Production or financial inputs change. Scope conditions disappear. Tentative timing hardens into a promise. Each can be part of good project work. The failure is sending the difference with no traceable reason and no plain explanation for the buyer.

1. Field observations become cleaner design assumptions

Field notes are messy because real sites are messy. A photo may show part of an obstruction but not its full height. A rep may write “roof looks newer” with no document or qualified check behind it. An access area may be locked. When the design request is created, these limits can vanish. The model then looks more complete than the evidence behind it.

Keep observed, measured, supplied, modeled, and unknown conditions apart. Do not turn “not seen” into “not present.” Do not turn a customer’s plan to trim a tree into a finished fact. Record it as a scenario choice. If a size came from imagery and not a field measurement, keep that source attached to the model or project record.

Sandia National Laboratories’ PVPMC modeling guide walks through the steps to AC (alternating current) output. These steps include weather data, irradiance (sunlight strength), array orientation, shading and soiling (dirt) losses, and module and inverter models. The lesson for a sales rep is simple. An output is only as good as its inputs.

Ask: Which site evidence supports this proposal condition, and what limit remains? If the answer is “the designer probably handled it,” nobody can inspect the handoff.

2. The layout changes without a customer-facing explanation

The customer may have seen a first sketch, a tablet view, an annotated aerial image, or panels you pointed out on a roof plane. The final layout can differ for good reasons. You may have a clearer obstruction record, spacing, equipment setup, shade context, roof use, or a responsible review. Still, the customer’s reference point is the earlier picture.

Compare the two states side by side. Record which roof planes changed. Record whether the panel count or visible layout changed. Note what evidence or review caused the difference, and which related outputs you refreshed. Then decide what the customer needs to hear. “The design team updated it” is weak. Say instead: “The proposal uses the west plane, not the area we discussed. The review found an obstruction there that is not yet resolved. Here is what is still under review.”

The final layout still needs the design, engineering, code, utility, authority, and build review that applies. The matching step explains the change. That review approves the design.

3. The equipment shown or discussed is replaced

On site, a rep might show a type of module (solar panel). The rep might talk about an inverter plan. An inverter turns panel power into usable power. The rep might also point to a possible equipment spot or discuss storage. The proposal may later use a different model, setup, size, spot, or option. Stock, how well parts work together, buying policy, design decisions, and business choices can all change the result.

Keep a product example separate from a part that is proposed for the project. The site record should say if the equipment was only an example, the customer’s pick, assumed for modeling, or offered pending confirmation. When you review the proposal, compare equipment names and setup in several places. Check the site notes, the design output, and the financial scenario. Check the customer text too. Add the bill of materials (BOM, the parts list) where you have one.

When the proposal changes the option, explain the difference that matters to the buyer. Do not claim the new part is equal. Do not call equipment “the same” or “better” unless your team has a sound basis for the claim. Send fit and approval questions to the responsible reviewers.

4. Production or financial scenarios use different inputs

A site talk often uses rough numbers. These can be a guess at use, a bill the customer sums up out loud, a rate assumption, a possible system size, or a loose talk about financing. Later the proposal can show exact-looking figures for yearly output, offset (the share of use the system covers), payment, savings, or payback (time to earn back the cost). Those figures may rest on inputs the customer never saw.

Exact numbers do not remove doubt. Compare the proposal scenario to the talk record and the source files. Name the period of energy use, the modeled setup, and the weather or irradiance source where it matters. Also name the loss assumptions, the tariff or rate inputs (the price per unit of power), and any escalation or degradation assumptions you used. Add incentives, financing terms, and the scenario date. Which fields matter depends on the proposal. Each important figure should lead back to its real inputs.

If the new scenario has better support than the on-site estimate, use it. Then say what changed. Do not keep a weak input just to stay consistent. Do not hide a stronger input because the customer might ask a question. The solar design review checklist covers the technical review. The matching step covers the difference the customer sees after that work.

Worked example with hypothetical numbers (not a customer case): On site, the customer says they use “about 800 kWh a month”. (A kWh, or kilowatt-hour, is a unit of energy.) The rep notes 800 kWh × 12 months = 9,600 kWh a year. The bills the customer sends later total 11,400 kWh over 12 months. That is 11,400 − 9,600 = 1,800 kWh, or 18.75%, more than the spoken figure. Say the design models 8,000 kWh a year. Against the spoken figure, that is 8,000 ÷ 9,600 = 83.3% of yearly use. Against the bills, it is 8,000 ÷ 11,400 = 70.2%, about 13 percentage points lower. This is a yearly energy ratio only, not a bill saving. The customer heard the first figure on site and sees the second in the proposal. So the proposal should say that the bills replaced the spoken estimate.

5. Scope, exclusions, and site conditions disappear

The customer may have talked about reroofing, service work, or tree work. They may have raised an area you cannot reach, trenching (digging a trench for cables), or a separate building. Other topics are indoor access, a preferred equipment spot, or repair of the site after work. The proposal might show the array and price but leave the condition out of the visible scope. The buyer may reasonably read silence as included, solved, or not important.

Not every field note belongs in the proposal. Use this test. Could the item change what the customer thinks is included, excluded, assumed, pending, or supplied by someone else? If yes, put it in the proposal text or an attached note. If a qualified reviewer has not decided its effect, state the dependency. Do not fill the gap with a sales conclusion.

The questions teams should resolve before leaving a site covers the state of each item when you leave and who owns it. Check that every site exception appears in the proposal. None should vanish during design and pricing.

6. Timing, approval, or next-step language hardens into a promise

At the property, “we should have an update after design review” can become “installation in six weeks” in a proposal or follow-up. “We will submit it” can sound like “it will be approved.” An example equipment spot can sound settled. Tentative words often harden because the proposal template expects a clean next step.

Record the difference between four things: an internal target, a message to the customer, an outside dependency, and a firm promise. Name who controls the next decision. A sales rep may promise a status update on a set event. That is not a promise of design acceptance, permit approval, utility action, financing approval, equipment stock, install timing, or system performance.

Have a qualified reviewer check wording on timing, approval, and performance against your area’s advertising rules. For campaign claims that set expectations before the visit, see aligning marketing claims with the proposal.

Key Takeaway

A change after the visit is not the problem. A change with no reason, evidence or owner is. If you can say what carried over, what changed and why, the proposal still matches what the customer saw.

Use this release table to turn the six modes into actions:

Drift mode Evidence to compare Primary decision owner Customer-facing treatment before send
Observation to assumption Dated notes, indexed photos, measurements, model source Designer or responsible technical reviewer for design use Name the assumption and any check still needed
Layout change Site visual, current layout, change reason, affected outputs Design owner Show or sum up the visible change and the reason
Equipment change Discussion note, current equipment record, setup, BOM where it applies Design, buying, and business owners within their roles Name the proposed option and explain why it replaced the example
Scenario-input change Customer records, model inputs, financial inputs, current setup Modeling and business owners State the key inputs, the scenario status, and what replaced the early talk
Scope condition omitted Site exception, estimate scope, exclusions, dependencies Estimating or operations owner, with qualified review as needed Say what is included, excluded, customer-supplied, or pending
Timing or approval promise Visit recap, workflow status, outside dependencies, proposal wording Sales release owner plus the party that controls the decision Replace certainty with a next event and a named dependency

How should a sales rep reconcile the site visit with the proposal?

Match the proposal in eight steps. Freeze the site record. Identify what the customer saw. Map each important item to the proposal. Compare sources and states. Route exceptions. Refresh affected outputs. Write the customer explanation. Run a final release read. Sales owns clarity. Specialists keep their decision authority. The release owner records the result and any open dependency.

  1. Freeze the visit record. Give the evidence package a project ID, visit date, property reference, list of participants, and source index. Keep the first visual or notes the customer saw. Do not quietly rewrite a site statement after design work starts. Add a dated clarification instead.

  2. Write the customer’s reference points. List the roof planes, equipment examples, spots, output or price scenarios, scope conditions, and next steps the rep showed or described. Note how strong the words were: example, preference, preliminary option, pending review, or commitment. Memory is not enough for this step.

  3. Map important items to proposal locations. For each reference point, find the design object, equipment field, scenario input, scope paragraph, exclusion, schedule line, or delivery message that stands for it. One site item can affect more than one output. A layout change may need new production, pricing, visuals, and scope text.

  4. Compare source, value, and status. Mark an item matched when the proposal faithfully carries the current supported state. Mark it changed when a better source or an approved decision replaced the site state. Mark it open when review or evidence is missing. Mark it excluded only when it does not affect the customer’s current decision and you record the reason.

  5. Route every exception to a real owner. Write the decision needed, the evidence on hand, the missing input, the role in charge, and the effect on release. “Check electrical” is not a routable exception. This one is: “Electrical reviewer to decide what extra evidence is needed before this service condition shapes the proposed setup.” It keeps the limit of each person’s authority clear.

  6. Refresh connected outputs after a material change. Confirm that the layout, equipment record, modeled output, financial scenario, price, scope, exclusions, visuals, and proposal text all show the same project state. Do not hand-edit one customer figure to make it look like the earlier talk.

  7. Write the buyer-facing explanation. Start with what the customer will notice. Then say why it changed, what else changed with it, and what is still open. Avoid “updated for accuracy.” It hides the real difference and can make the customer doubt every earlier statement.

  8. Run the release read from the customer’s viewpoint. The sales release owner compares the visit recap and the proposal side by side. A separate design or technical reviewer confirms only the decisions in that role. The proposal is ready for customer talks when every important difference is matched, explained, or held in view as a dependency.

NASA’s requirements-management guidance covers tracing requirements and managing changes within NASA programs. Its configuration-management guidance covers naming configurations and controlling changes. It also covers tracking status and keeping product information in line with an approved configuration. The habit carries over. Keep the baseline, the reason for each change, the current state, and the approval owner on record. Do not rely on memory.

This process should stay in proportion. A simple home proposal does not need an aerospace system. It does need enough evidence that a rep can answer the customer’s natural question: “Why is this different from what we discussed at my property?”

What should a site-to-proposal reconciliation record contain?

A useful record has the site item and what the customer saw or heard. It lists the source and status. It shows how the proposal shows the item now. It names any difference, the reason, and the outputs it affects. It also names the decision owner, the release condition, and the explanation for the buyer. Keep it next to the project record. Then someone can review the proposal without rebuilding the visit from memory.

Copy this checklist into your team’s CRM (the tool where you track customers), design request, worksheet, or project platform.

Copy-ready reconciliation checklist

Field Entry
Project ID, site visit date, proposal ID and scenario
Sales release owner and design or technical reviewers
Customer decision this proposal supports
Item ID and category
What the customer saw or heard
Exact source, date and evidence reference
Site-state label: observed / customer-stated / discussed option / inferred / open
Current proposal page, field or object
Reconciliation state: matched / changed / open exception / excluded with reason
Difference and reason
Connected outputs checked
Decision owner and authority boundary
Release condition or blocked work
Customer-facing explanation
Resolution date and approver

Before you send, confirm that:

  • Every important site item has a reconciliation state.
  • Every changed item has a reason and a check of the outputs it affects.
  • Every open exception has an owner and a release effect.
  • Layout, equipment, modeled results, price, scope, visuals and wording all use one current state.
  • The customer explanation names the differences. It does not promise results that outside parties or open reviews control.

Do not use “excluded with reason” as a dumping ground for awkward information. The release owner should be able to show why the item does not affect the customer’s decision on this proposal. If the effect is unclear, send it down the open-exception route.

Illustrative example, not a customer case

At a made-up site visit, a rep shows a first array on the south garage plane. The rep records the customer’s wish to keep the main roof visually clear. A later photo review leaves the garage obstruction sizes unresolved. So the designer builds a scenario that uses part of the main roof.

The weak handoff sends the new image with no explanation. The reconciliation record instead says:

Item ID: LAYOUT-02
Customer reference point: Preliminary garage-plane visual shown during visit; main-roof visibility preference recorded.
Current proposal state: Mixed garage and main-roof scenario.
Reconciliation state: Changed, with one open exception.
Reason: Available evidence does not resolve the garage obstruction dimensions for the requested design stage.
Affected outputs checked: Layout, modeled production, equipment quantity, price, scope note, cover visual.
Owner: Design owner for scenario; field lead for missing evidence; sales owner for customer explanation.
Release condition: Present only as a preliminary comparison pending the recorded evidence decision.
Customer explanation: The proposal includes a main-roof portion that differs from the garage-focused view discussed on site. The team has not confirmed the garage obstruction dimensions for the requested stage, so this is a comparison scenario rather than a final location promise.

The example does not say which layout is suitable or likely to be approved. It shows how to keep the customer’s wish, the evidence gap, the current scenario, the owners, and the customer wording on one record.

Pro Tip

Before you build the proposal, write one sentence per important site item: what the customer saw, what the proposal now shows, and where the evidence is. Any item you cannot fill in is an open exception.

Use three exception routes:

Exception route Use it when Required control What sales can tell the customer
Clarify without revisiting You can settle the gap with a customer record, clear existing evidence, or a desk review Source, who answered, question, date, and the resulting change What was cleared up and how it changed or confirmed the proposal
Return or obtain new field evidence Current evidence cannot support the stage you need, and direct capture is safe and needed Access, permission, safety process, evidence need, visit owner, and a hold on later work Why more evidence is needed and what decision it supports, with no promise of the result
Release with a visible dependency The proposal can support a limited talk while a controlled decision stays open Named dependency, affected fields, banned uses, owner, and next update event What the scenario can be used to discuss and what is not yet decided

The clear proposal plan after a site visit can help the team decide whether to design, clarify, revisit, or stop. The record in this guide starts after you pick that route. It checks the proposal against what the buyer already saw.

Explain every change before you send

Compare the site record with the layout, equipment and scenario in one project, then send a proposal that says what changed and why.

See a Live Walkthrough

Checking cost first? See the SurgePV pricing page.

6
drift modes to check in this guide
5
site-item states in the sorting table
3
exception routes for open gaps

These counts describe the framework in this guide, not a survey result.

Where can software support reconciliation, and where must people decide?

Solar proposal software can link project inputs to 3D roof models, layouts, shading, yield, financial scenarios, electrical workflow, bills of materials, and proposals. People must still check sources, read site conditions, approve changes, apply local rules, and explain differences to customers. They must also get the right approvals. People, not the platform, decide release.

SurgePV supports 3D roof modeling, solar array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. Because these parts are linked, a reconciliation review is easier to inspect. A reviewer can compare the current setup, scenario, and proposal. They do not have to match unrelated files by filename.

The benefit depends on good workflow habits. Results depend on source data, assumptions, equipment models, configuration, and review. A linked proposal can still be consistently wrong if an unsupported site assumption enters the project and nobody challenges it. Software does not know that the customer read a rooftop visual as final. Your team must record that talk and test the later document against it.

Check which references, states, owners, and linked outputs your configured software can keep. Record any gaps in your approved project system. Keep four decisions with people:

  • whether the site evidence is good enough for its purpose;
  • what an observed condition means for design, scope, cost, schedule, or compliance;
  • which important difference the customer needs to understand; and
  • whether the proposal may be released for a defined decision.

SurgePV does not replace a site check, safe work practices, permissions, or engineering judgment. It does not replace code or contract review. It does not replace approval by the responsible engineer, authority, lender, insurer, or utility. A guided product review can show how the linked workflow runs. Your project team must still set and enforce its own reconciliation gate.

Frequently Asked Questions

What is site-to-proposal drift in solar sales?

Site-to-proposal drift is a gap between what you discussed at the visit and what the later proposal shows. This can cover the property, the customer’s wishes, site conditions, or promises. A gap may be fine. The risk starts when your team cannot link it to evidence, check its effects, or explain it to the customer before sending.

Who should reconcile a solar proposal with the site visit?

The sales rep should own what the customer is told. Design, estimating, finance, operations, and qualified reviewers own the decisions within their roles. One release owner should check each important site item. Each item is either matched, changed with a reason, held as an open exception, or left out with a clear explanation to the customer.

Does every difference require a new site visit?

No. A clear photo, a customer answer, a source document, a designer review, or a qualified assessment may settle the gap. Go back to the site only when you cannot get the missing evidence another safe way. You may also go back if the reviewer needs to see it in person. The record should say why the chosen route is enough for this stage.

Should the proposal repeat every site note?

No. Your internal field notes can hold more detail than the proposal. The proposal should carry the conditions, assumptions, exclusions, choices, and open items that change the buyer’s decision. The record you keep holds the full trail. It shows why each site note was included, sent for review, put off, or judged not relevant.

How can SurgePV support site-to-proposal reconciliation?

SurgePV can support 3D roof modeling, array layout, shading analysis, energy-yield and financial modeling, electrical workflow, bill-of-materials output, and proposal generation. Results depend on your source data, assumptions, equipment models, setup, and review. The software does not replace a site check. It also does not replace approval from the responsible engineers, authorities, lenders, insurers, or utilities.

Further Reading

Version identity and revision labels are covered in the solar proposal version-control guide. For choosing the next step after the visit, see the clear proposal plan after a site visit.

To check a proposal against its site record on your own project, book a demo or see the solar proposal software.

Review a Connected Site-to-Proposal Workflow

A guided demo shows how SurgePV supports project inputs, design, scenarios and proposal generation. Your team keeps its review and approval responsibilities.

Book a Free Demo

Sources

Primary research and reference material used for this desk-research article.

Where this fits

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

About the Contributors

Author
Akash Hirpara
Akash Hirpara

Co-Founder · SurgePV

Akash Hirpara 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; education, certifications, project totals, financial results, speaking engagements, and media appearances 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.