Answer
A solar quote can stall at six transfers: discovery to project brief, site evidence to design, layout to sales, production results to explanation, commercial inputs to a scenario, and reviewed proposal to customer follow-up. For each transfer, record the requested decision, evidence, open assumptions, sender, receiving owner and acceptance response. Measure waiting and correction separately before changing the process.
A quote can wait in a designer’s queue even when the designer is ready to work. The missing item may be the correct building, a usable bill, a decision about an option, or permission to release a preliminary estimate. Sending more messages does not identify which decision is blocked.
This guide reviews the six transfers before a homeowner receives a solar quote. It retains discovery, roof evidence, layout, production, commercial assumptions and final follow-up as separate work objects. The proposed acceptance checks below are team procedures, not requirements imposed by a software product or a substitute for qualified project review.
Give each transfer an acceptance test
A handoff should say what the receiver is being asked to produce, which evidence supports it, which assumptions remain open and who may resolve them. “Please quote this roof” is insufficient if the building, energy basis or customer-selected option is unclear.
| Transfer | Minimum working record | Receiving check | Return reason to record |
|---|---|---|---|
| Discovery to brief | Customer goal, property/meter, requested option, current commitments | The requested comparison and scope are identifiable | Conflicting site or option |
| Site evidence to design | Dated images, source measurements, known constraints and unknowns | Evidence is usable for the requested release level | Missing or inconsistent source |
| Layout to sales | Scenario identifier, reviewed revision, equipment and open conditions | Visual and quantities describe the same option | Stale or unlabeled visual |
| Production to explanation | Model run, equipment/layout basis, period and assumptions | Estimate matches the scenario being discussed | Different run or time basis |
| Commercial inputs to scenario | Quote revision, payment basis, conditions and exclusions | Totals and assumptions belong to the chosen option | Unresolved commercial input |
| Reviewed proposal to follow-up | Exact sent version, recipient, permitted use and next owner | Customer can identify the requested next decision | Missing release or next action |
The receiving owner may accept, return with a specific question, or accept a clearly bounded preliminary use if authorized. Record that response. A message received in an inbox is not evidence that the work was accepted.
1. Turn discovery notes into a usable brief
A conversation may contain several alternatives: a smaller array, a battery option and a financing question. Identify which one the first quote must answer. Keep customer preferences separate from site facts and professional conclusions.
Record commitments already made. If sales has mentioned a panel count, savings estimate, completion date or eligibility condition, the receiver needs the statement and its basis. The designer should not learn about it after producing a conflicting visual.
Use the sales-to-design handoff guide for the wider relationship between these teams. This page focuses on where the pre-customer quote packet is waiting or being returned.
2. Turn roof and electrical evidence into design inputs
A roof photograph, utility bill, obstruction measurement and service detail answer different questions. Label the source, date, project object and limitation of each item rather than placing them in an unexplained attachment folder.
Ask the responsible reviewer what can be produced from the available evidence. A concept layout may use an explicitly stated assumption; a commitment requiring field or technical confirmation should not inherit that assumption as if it were verified.
Do not prescribe a universal clearance, electrical setting or approval sequence here. Applicable site conditions, equipment instructions, jurisdiction requirements and qualified findings govern the individual project. The design intake checklist addresses the complete acceptance packet at this boundary.
3. Make the preliminary layout reviewable by sales
Return a labeled layout with its scenario, revision, equipment basis and unresolved conditions. Sales should be able to distinguish an optional battery or alternate array area from the base offer without interpreting the designer’s private notes.
If a visual changes, identify the affected quantities and customer-facing explanations. Ask the receiving owner to acknowledge the changed option. Replacing an image in a folder does not establish that a previously exported proposal uses it.
Keep recurring customer questions as specific intake improvements. A repeated question about the preferred roof area may call for a clearer discovery field; it does not justify inserting generic reassurance into every proposal.
4. Explain the production result for the same scenario
A generation figure belongs to a model run and its inputs. Keep the equipment, layout, weather basis, shading representation, analysis period and relevant assumptions associated with the result. Distinguish an estimate used for option comparison from a contractual guarantee.
The US Department of Energy’s homeowner guide discusses considering roof conditions, energy needs, installer offers and purchase arrangements. Use that as homeowner decision context, not validation of a particular site model or proof of a universal sales sequence. Current incentives and local approvals require separate verification.
When a condition needs confirmation, assign a next action with an owner and agreed response point. “Designer to confirm the obstruction before the revised option is released” is actionable. “Follow up on shade” leaves both the decision and recipient unclear.
5. Connect commercial inputs to the chosen option
Confirm that equipment, quantities, price, payment structure and exclusions refer to the same offer. Keep tariff, consumption, incentive and finance assumptions dated and attributable. Do not let a headline savings number conceal a missing source or an unresolved condition.
The technical reviewer need not approve a lender’s terms, and the salesperson should not silently change a model to match a desired payback. Route each decision to its responsible owner. The financial-assumptions audit supplies a more detailed input register for this part of the packet.
6. Release an exact proposal with an owned next step
Open the actual PDF or customer link beside the reviewed records. Confirm recipient, option, visible revision, scope and the requested decision. A current editor view can coexist with an older export.
Use the pre-send checklist for the final release check. Save the version sent, its source revisions, recipient, send date, release owner and next action. Acceptance by the customer is a later boundary, with its own technical, commercial and delivery conditions.
Diagnose waiting before changing the workflow
Review recent opportunities with different scopes, including one that moved smoothly and one that required correction. Record request time, usable-input acceptance, active-work intervals, return reason and reviewed-output delivery. Separate waiting for the team, waiting for the customer, external dependencies and correction work.
Compare like-for-like requests. A preliminary residential option and a complex revised battery scenario may require different evidence. A change in project mix can alter elapsed time without proving the handoff became better or worse.
Illustrative example: sales requests an array-plus-battery option, but the design packet contains only the base array. The receiving designer returns one precise scope question. The owner confirms the intended option, issues the revised brief and records which downstream visuals and commercial assumptions need review. The example identifies a control; it makes no claim about time saved or conversion uplift.
The project handoff worksheet provides blank fields for owners, revisions, open assumptions and next actions. Use your own project evidence rather than treating the worksheet as benchmark data.
Evaluate the product at the actual transfer
SurgePV’s proposal page describes generating customer proposals from project design information. That is vendor-reported product scope. In a guided demo, bring a redacted scenario and ask which fields change after an equipment substitution, how the exported option is identified and which checks remain with your team.
Do not infer automatic approval, complete revision history or a guaranteed business result from a connected workflow description. Evaluate the account and deliverable you would actually use.
Frequently asked questions
Who should accept a solar quote handoff?
Name the person responsible for the receiving decision. Acceptance means the packet is usable for that stated purpose; it does not transfer authority to approve engineering, financial or contractual decisions that belong to another reviewer.
Should missing information always stop a preliminary quote?
Not always. An authorized preliminary option can carry a visible planning assumption and a verification owner. Stop a commitment that depends on a material unknown, or change the requested decision so it no longer implies that the unknown is resolved.
How do we distinguish a handoff delay from slow design work?
Record when the request was sent, when the receiver accepted usable inputs, when active work began, and when a reviewed output was returned. Track correction time and external waiting separately; elapsed time alone does not identify the cause.
Can proposal software remove human review?
No. Test the actual transfer from project inputs to customer output, including changed equipment and scenario labels. A connected editor does not establish that site evidence, technical assumptions, finance terms or approval authority have been reviewed.
Sources
Primary research and reference material used for this desk-research article.
