The Post-Site-Visit Solar Deal-Risk Checklist

A site visit creates a short window when physical evidence, customer context, and project assumptions can be reconciled before they scatter into separate systems. If the team skips that window, a missing roof photograph can become a design assumption, and a casual customer comment can become an unsupported sales promise.

This checklist is for solar surveyors, sales representatives, designers, and operations leads after a residential or commercial visit. It does not decide engineering, safety, permitting, utility, financing, or contract questions. It proposes a record of those questions, their owners and release boundaries. The record alone cannot prevent an incorrect release; the responsible team must apply its review and authority controls.

The Department of Energy homeowner guide identifies roof condition and shade among the practical factors buyers consider. A post-visit review should preserve those observations alongside electrical, access, usage, and commercial evidence rather than reducing the visit to a folder of photographs.

Build one record from many kinds of evidence

Keep the original survey form, photographs, measurements, drawings, customer notes, utility records, and prior remote model. The risk checklist points to these sources; it does not replace them. Record capture date, author, location, units, and any uncertainty needed to interpret each item.

Use explicit evidence states: observed, measured, customer-stated, inferred, assumed and unknown. Keep an inference (the team’s interpretation) distinct from an assumption used as a provisional model input. An object visible in a photograph is observed. A dimension taken with a stated method is measured. A future expansion described by the customer is customer-stated. A roof edge inferred behind vegetation is assumed. These states may all be useful, but they are not interchangeable. Retain the measurement method and limitations; a recorded value is not automatically a verified value.

For every issue, record its possible effect. Use categories such as feasibility, usable area, energy modeling, electrical scope, structural review, access, equipment, schedule, price, contract, and customer expectation. Then name the owner and the last responsible point for resolution.

Avoid a generic red-yellow-green score as the only output. One red issue can mean “field dimension missing” while another means “proposed scope may be outside customer control.” The owner needs the mechanism and next action, not only a color.

Check 1: confirm property, people, and project boundary

Start with identity. Confirm address, coordinates, building names, customer entity, site contact, utility accounts, and structures discussed. On a campus, mark which roofs, carports, or ground areas belong to the opportunity. On a shared building, distinguish customer control from physical proximity.

Compare the visit with intake. A surveyor may discover that the meter serves another building, a tenant controls only part of the load, or the proposed array area sits under a different owner. These are not drawing corrections. They can change the deal boundary.

Record who attended and what authority they claimed, without inferring legal authority from presence. The person who opens a roof hatch may not be able to approve roof work or contract terms. Route ownership and contract questions to the appropriate role.

Name structures consistently. Use the same building and roof-plane identifiers in photographs, roof models, electrical notes, bills, and proposals. “Rear roof” becomes ambiguous when a site has several buildings.

Pause customer-ready work when the project boundary is unresolved. Preliminary internal analysis can continue on a clearly labeled assumption if the responsible lead accepts it, but the proposal should not turn that assumption into a fact.

Check 2: reconcile roof or ground conditions with the remote concept

Compare the visit with the model used before travel. Mark changed roof edges, additions, equipment, skylights, drains, parapets, vegetation, terrain, fences, and neighboring features. Keep the prior model so the team can see the delta.

Record roof material and visible condition as observations, not engineering conclusions. A photograph can document cracking, ponding, repair areas, or a newer section. It does not by itself establish structural capacity or remaining life.

For ground-mounted concepts, note slope, drainage signs, access, vegetation, surface conditions, and visible conflicts. Survey and civil questions may require separate work. Avoid letting an overhead polygon imply buildable land.

Use the image and measurement naming plan from solar site survey data collection. A designer should be able to trace every updated boundary to a record rather than trusting an unlabeled sketch.

Classify changes by effect. A new vent can alter one module position. A missed roof extension can alter the entire concept. Prioritize review where the recommendation may change.

Check 3: separate shade evidence from shade interpretation

Document obstruction location, apparent height, observation point, date, time, and seasonal limitations. One site photograph shows one moment. It can confirm an object while remaining insufficient to describe its annual energy effect.

The Department of Energy solar radiation primer explains that solar radiation varies with location, time, season, weather, and surface orientation. Shading analysis therefore needs geometry and a stated method, not a casual impression that a roof looked sunny.

Record vegetation ownership and condition as separate commercial questions. A model can compare a current tree scenario with another defined scenario. It should not assume trimming or removal is permitted, affordable, permanent, or desired.

If a field instrument produced a shade record, retain its file and method information. If the team relies on geometry modeled from measurements, preserve those dimensions. State which objects remain uncertain.

Do not use shade as a catch-all explanation for empty roof area. Access, roof condition, structural concerns, equipment service, and customer preferences need their own labels.

Check 4: review electrical observations without overclaiming

Confirm equipment identity, location, visible labels, service arrangement, meter relationship, accessible ratings, routing observations, and image coverage. Transcribe carefully and retain the photograph. If a label is unreadable, mark it unreadable rather than guessing.

Treat field observation as an input to qualified review. Electrical feasibility, interconnection, protection, code, and equipment decisions depend on project specifics and applicable authority. A site checklist should route these questions, not answer outside the surveyor’s remit.

For covered U.S. workplaces, use the applicable safe-work procedures. OSHA maintains general resources for electrical safety and fall protection. This article is not safety training, and teams should follow applicable law, competent supervision, and site-specific controls.

Identify access limitations. Locked rooms, covered labels, energized conditions, tenant restrictions, or missing escorts can leave the electrical record incomplete. State what was not observed and the safe next step.

Tie electrical scope to the customer proposal carefully. A preliminary commercial discussion should not promise an interconnection path, upgrade scope, or approval before the responsible parties review current evidence.

Check 5: validate consumption and operating context

Confirm that the bills or interval files discussed at the visit belong to the site and meters in scope. Record period, unit, service, and any existing onsite generation or netting that may affect interpretation.

Ask about known operating changes with dates and status. New shifts, vacancies, electrification, fleet charging, production lines, efficiency work, and planned closures can make historical data less representative. Keep these as separate scenarios until the evidence supports inclusion.

Capture operating schedules as customer statements unless measured records support them. “The plant runs weekdays” is useful context but may omit holidays, seasonal production, standby loads, or overtime. Compare statements with the interval curve and resolve material conflicts.

Do not estimate missing annual consumption in the field and let it become the proposal basis. Assign data collection, reconstruction, and review to the relevant role. State what preliminary work may continue.

Link the cleaned profile, reconciliation, and approved scenario to the project. A photograph of one bill page is not a consumption model.

Check 6: record access, logistics, and constructability questions

Document visible access routes, staging possibilities, roof access, gates, working-hour limits, occupant constraints, material movement, and areas that may require protection. These observations support planning; they do not replace a construction or safety plan.

Separate fact from solution. “Roof hatch opening measured X by Y” is evidence when properly recorded. “Modules can be moved through the hatch” is a conclusion that depends on equipment, packaging, safe handling, and site controls.

Ask the customer about operating restrictions, shutdown windows, noise, parking, tenant coordination, and security procedures. Record who supplied the information and whether it is a request or approved condition.

Flag conflicts with the sales timeline. Restricted access, required escorts, seasonal operations, or roof work can affect schedule. Do not hide these issues to preserve an early date.

Assign logistics questions before final scope and price. A technically possible layout can still carry meaningful delivery work that the commercial package needs to address.

Check 7: compare customer statements with recorded scope

Read the surveyor’s notes for requests, priorities, objections, and promises. Customers may ask for a specific roof to remain clear, prefer certain equipment, expect future expansion, or describe a budget and timing constraint. Translate each statement into a project field or open decision.

Distinguish customer preference from accepted company commitment. A request becomes part of the controlled scope only after the authorized role evaluates and records it. Likewise, a salesperson’s informal statement should be checked against the approved offer.

Resolve contradictory statements. The facilities manager may expect a future load increase while finance plans a closure. The owner may favor maximum capacity while operations needs clear roof access. Do not choose the statement that supports the current concept; identify the decision owner.

Prepare a short customer confirmation where ambiguity matters. Restate the relevant understanding, requested decision, and next step. This is more useful than forwarding raw field notes.

The solar sales-design handoff should carry these priorities into modeling without turning them into unsupported technical facts.

Check 8: update scope, price, and schedule dependencies

Site evidence can change equipment quantities, labor assumptions, specialist work, travel, access, roof scope, electrical work, schedule, and proposal conditions. Create a dependency list before releasing revised commercial material.

Do not let one department absorb the change invisibly. If design reduces usable area, sales needs the reason and customer language. If commercial review changes equipment, design and energy modeling need the new controlled input. If a site condition requires investigation, scheduling needs the hold point.

Compare current and prior versions. Record which fields changed, why, and which outputs were rerun. Avoid editing only the customer document, because the model, bill of materials, and internal price record can diverge.

Use explicit validity dates for volatile inputs such as quotes and equipment availability. Confirm current pricing, implementation scope, access, and contract terms in writing. Avoid presenting a preliminary allowance as a final project cost.

When the effect is unknown, route it. A risk record can state “commercial impact pending electrical review” without inventing a number.

Check 9: protect safety and professional boundaries

Review whether the visit encountered restricted areas, energized equipment, roof access concerns, structural signs, hazardous materials, weather exposure, animals, traffic, or other conditions that require appropriate control. Follow the employer’s safety program and applicable requirements.

Do not ask a salesperson or surveyor to exceed training or authorization to complete a checklist. An inaccessible observation is a valid gap. The safe response is to identify the competent role and future access plan.

Keep photographs and notes appropriately controlled. Sites can contain personal information, security details, proprietary equipment, or tenant activity. Store evidence in approved systems with access suitable to the project and law.

Separate observed condition from diagnosis. A stained ceiling, corroded enclosure, or damaged surface can be documented. Determining cause, severity, compliance, or repair belongs to the qualified role.

The checklist’s purpose is to surface the boundary. It should never create pressure to claim evidence the visit did not safely obtain.

Check 10: release a decision log, not a photo dump

Hold a short review with sales, design, and the roles needed for material exceptions. Work from the risk record and evidence links. Decide whether each item is closed, assigned, accepted within a stated preliminary boundary, or blocking a dependent output.

Publish a change summary. Include confirmed changes from the pre-visit model, unresolved issues, responsible owners, dates, and outputs affected. Keep customer communication consistent with the internal decision.

Link accepted findings and their evidence revisions to the actual project basis. When evaluating Solar Designing, confirm how your team would reference that basis; do not assume the product provides a native evidence register or automatic release control.

Set review triggers. New utility data, a roof report, an electrical document, customer confirmation, or an engineering finding may require the model and proposal to be rerun. Attach triggers to the project instead of relying on memory.

Use the solar proposal pre-send checklist after these issues reach an appropriate status. A final document check cannot compensate for unresolved site identity or scope.

Archive the visit package without freezing it as eternal truth. Evidence has observation dates. Conditions and customer plans can change, so later decisions should confirm that material records remain current.

Run the checklist as a focused meeting

Begin with changed facts, not every photograph. Ask what the site visit disproved or complicated in the original concept. Then review issues that can alter feasibility, customer promise, scope, price, or schedule.

Keep one note-taker and one decision owner for each issue. Specialists can provide input without creating several competing risk lists. End with a read-back of blockers, permitted work, owners, and customer update.

Limit discussion of nonmaterial cosmetic differences. A model can be corrected later if the difference affects no current decision. Do not let low-impact drafting work obscure a missing meter boundary or unreviewed electrical condition.

Send the customer update promptly when the visit changed expectations. Explain the finding, why it matters, what the company is checking, and when the next update will arrive. Avoid promising the final answer before the assigned review.

What should happen immediately after a solar site visit?

Immediately after a solar site visit, the team should preserve original evidence, confirm that files and measurements are interpretable, compare findings with the pre-visit model, classify decision-changing differences, and assign every unresolved item. Customer-ready design, pricing, and schedule work should resume only within an explicit boundary, with dependent outputs, reviewers, and the next customer update recorded in the project record.

Start while the visitor still remembers which roof, room, label, and conversation each record represents. Upload the original photographs and forms into approved project storage. Preserve file metadata, add stable building and location labels, and link measurements to the features they describe. Do not rename an uncertain object into a confident diagnosis merely to finish the upload.

Run a completeness check before interpretation. Confirm that required photographs open, measurement units appear, orientation and location are clear, and the evidence answers the pre-visit questions. A complete package can contain adverse findings. An incomplete package lacks the evidence another role needs to understand what happened.

Then reconcile the visit with the controlled preliminary concept:

1. Confirm the property, customer, structure, electrical service, and project boundary.
2. Freeze the pre-visit model and proposal revision used to plan the visit.
3. Compare roof, ground, shade, electrical, access, consumption, and customer-scope evidence with that revision.
4. Record each difference as a specific finding with its source and evidence state.
5. Identify which layout, production, equipment, scope, price, schedule, contract, or proposal outputs could change.
6. Assign an owner and required reviewer; state what work may continue and what must pause.
7. Prepare customer wording for material changes and commit to a dated next update.
8. Update controlled source records, regenerate dependent outputs, and release a new revision after review.

Illustrative workflow example, not a customer result: A site package shows a roof feature that the preliminary model did not represent, and one photograph lacks enough context to determine its boundary. Operations preserves both records, assigns a focused follow-up to the field owner, and marks the affected roof area unavailable for customer-ready layout. Only after the responsible owner establishes that independent work is safe and authorized does design continue on an unaffected area. Sales sends reviewed wording explaining the pending decision and next contact date.

The example separates a useful partial release from false completion. The missing context does not force the company to abandon every piece of work, but it cannot silently become clear usable roof. The issue record carries the affected area and decision into the next handoff.

Use a short post-visit intake note:

Immediate post-site-visit handoff

Visit, project, and evidence-package revision: [identifiers]

Pre-visit questions answered: [list]

Material new observations: [source links]

Conflicts with current model or scope: [specific differences]

Missing or uninterpretable evidence: [item and owner]

Work allowed to continue: [named preliminary boundary]

Outputs paused: [design, model, price, schedule, contract, or proposal]

Required reviewers: [roles]

Next customer update: [owner and date]

Do not treat the meeting date as the package’s observation date. Individual photographs, measurements, documents, and customer statements can have different dates and authors. Keep those distinctions because later evidence may contradict only part of the visit record.

How should a solar team classify site-visit findings?

A solar team should classify a site finding by evidence state, decision effect, urgency, role, and the last point at which resolution is required. The record should distinguish observed, measured, customer-stated, inferred, and unknown information, then state which work may continue, which output must pause, what evidence closes the issue, and whether customer communication is required before the next release.

Begin with the evidence state. “Observed” means the condition appears in a retained record. “Measured” adds a value, unit, method, and location. “Customer-stated” preserves useful context without converting it to field verification. “Inferred” identifies the team’s interpretation. “Unknown” keeps the gap honest. One finding may have several linked records with different states.

Next classify the decision effect. Use named mechanisms instead of a generic risk score:

For routine decision triage, urgency follows the consequence and next dependent decision. An immediate hazard or emergency follows the applicable safety response rather than waiting for proposal priority. An unreadable electrical label may need immediate attention if pricing or design relies on the equipment record. A cosmetic roof-model difference can wait if it changes no current output. Record the last responsible point for closure so later teams know when a temporary boundary expires.

Avoid collapsing several findings into “site issue.” A disputed roof edge, missing service label, customer-requested expansion, and access restriction have different evidence and owners. Separate rows allow one item to close without implying that all four are resolved.

Use the issue disposition explicitly: close with evidence, accept within a restricted preliminary use, assign for resolution, or block a named output. “Monitor” is incomplete unless the record says who will monitor what evidence and which event triggers action.

When qualified review is necessary, route the observation without diagnosing it. Field staff can document a condition and its context. The responsible engineer, electrician, safety professional, authority, utility, lawyer, tax adviser, lender, contractor, or other qualified role determines significance within their remit.

What should a post-site-visit customer update include?

A post-site-visit customer update should explain what the team confirmed, what changed from the preliminary concept, why the change matters, which specialist or record is needed next, and when the customer will hear back. It should avoid internal risk language, unsupported conclusions, or a promise before technical and commercial reviewers have accepted the affected scope, price, schedule, or design boundary.

Write from the customer’s decision. They usually need to know whether the concept remains on the same path, which part is under review, what evidence the visit added, and whether they must provide anything. They do not need an unfiltered list of every photo-quality defect or internal routing note.

Use a copy-ready structure:

Post-site-visit customer update

Thank you for helping us document [site or project area].

The visit confirmed: [plain-language facts supported by the current evidence].

The preliminary concept needs review for: [specific finding and why it affects the next decision].

Our team is now checking: [named technical or commercial question without pre-judging it].

We need from you: [specific record or decision, or “no action at this stage”].

Your next update will arrive by: [date and contact].

The current concept remains: [allowed use and any material limitation].

Do not promise the technical answer inside the status message. “We are confirming whether the observed service condition changes the connection scope” is different from “an upgrade will be needed.” The first states the review. The second is a conclusion that needs the responsible evidence and authority.

If the visit corrected an earlier company statement, acknowledge the correction and replace the affected customer document. Explain which new evidence changed the basis. Quietly uploading another PDF leaves the buyer to discover the inconsistency and decide which version to trust.

Keep the update connected to the internal issue record. Sales should use approved wording and record customer responses that could change the project. A reply about planned roof work, operating changes, access, or ownership becomes customer-provided evidence that needs verification, not instant permission to close the issue.

When no material concept change exists, the update can still close the loop. Confirm that the visit package entered review, name the next project stage, and give a realistic next contact date accepted by the owning team. A status update can state the accepted next contact date without promising the technical outcome.

Store the message and its source revision with the project. If later evidence changes the conclusion, reviewers can see what the customer was told, issue a controlled correction, and avoid repeating an expired explanation.

Use risk statements that another role can act on

Write each issue as condition, possible consequence, and required response. “Electrical risk” is too vague. “Main service label was inaccessible; connection concept and any associated scope remain pending electrical review” tells sales what not to promise and tells the reviewer what evidence is missing.

Avoid prescribing an answer outside the observer’s remit. The field worker can document a damaged surface, access restriction, or unreadable label. The responsible specialist determines significance and response. This keeps the record useful without turning observation into diagnosis.

Add a customer-communication field. Some issues require immediate discussion because they change the concept. Others can wait for a qualified answer. Record the approved wording, owner, and update date so sales does not translate a technical note under pressure.

Track residual risk after a decision. Closing an issue for preliminary design may still leave a later hold point for engineering, authority, procurement, or construction. The close note should state that boundary rather than implying universal resolution.

Audit the evidence package itself

Check that photographs open, labels are readable, units are consistent, and every measurement maps to a location. Confirm that timestamps and building names agree across the survey form and files. A checklist cannot compensate for evidence nobody can interpret.

Look for missing negative evidence. If no roof interior, electrical room, or ground route was accessible, say so. Silence is easily mistaken for “no issue observed” when the condition was never seen.

Review privacy and security before wider sharing. Remove unrelated personal material where policy allows, restrict sensitive site details, and use approved project storage. Do not place the only copy in a private message thread.

Finally, compare the package with the pre-visit question list. A good visit may discover new issues, but it should also answer the questions that justified travel. Carry unanswered items forward with an owner instead of declaring the survey complete by calendar status.

Retain the evidence-package version used for each design release. If a later upload replaces a photograph or measurement, the team should know which earlier outputs relied on the superseded record. This version link makes targeted re-review possible and stops every new file from causing an unfocused restart.

Test the package from the next role’s chair. A designer should be able to locate the photographed condition, understand its orientation, identify the stated uncertainty, and see who owns resolution without calling the visitor for a translation. If that handoff fails, improve the record before dependent work resumes.

Results depend on source data, assumptions, equipment models, configuration, and review. Outputs support design and documentation workflows but do not replace approval by the responsible engineer, authority, lender, insurer, or utility.

Frequently Asked Questions

When should the post-site-visit review happen?

Review the evidence while the visit is still fresh and before dependent customer-ready design or pricing resumes. Set timing according to the project and responsible roles. Immediate safety or emergency action follows the applicable site process and must not wait for this commercial review.

Is every unresolved site item a deal blocker?

Classify each item by effect and decision stage. Some need a later verification point; others block an affected release. Only the responsible owner may authorize safe independent work, and a safety response can require a wider stop. Disclosure cannot waive required evidence, review or approval.

Who owns deal risk after a site visit?

Ownership should follow the decision. Field staff own clear capture and clarification, design owns model implications, sales owns customer communication, and authorized technical or commercial roles own approvals within their remit. One coordinator should maintain the shared risk record so issues do not disappear between departments or duplicate across private lists.

Should the customer receive the internal checklist?

Usually the customer needs a concise explanation of material findings, assumptions, choices, and next steps rather than the entire internal control document. Do not hide a decision-changing fact. Translate the relevant issue into plain language and keep the internal record linked to the evidence and approved customer communication.

What happens when new evidence contradicts the site visit?

Preserve both records, identify which observation is newer or more suitable, and assign a reviewer to resolve the conflict. Update the controlled project input, rerun affected outputs, and record what changed. Do not delete the earlier evidence or patch only the proposal, because dependent design and commercial records may remain inconsistent.