Solar Site Survey Evidence Package: What Design Teams Need Back From the Field

A site survey creates value when it resolves a decision, not when it produces the most photographs. Solar teams often discover that a detailed field visit still leaves design with a familiar list of questions: Which roof surface is this? Was the measurement observed or estimated? Does the panel image identify the service? Which obstruction changes the layout? Has anyone recorded the access condition that affects installation planning?

The answer is an evidence package designed before the survey begins. It translates a project’s open questions into observations that the next decision can use. It does not substitute for professional judgment, local rules, safety planning, engineering, manufacturer requirements, utility instructions, or the conditions of a particular site. It makes those activities easier to coordinate because the limits of the field record remain visible.

A Survey Brief Is Not a Generic Checklist

A generic checklist can prevent obvious omissions, but it cannot know which facts control this project. A residential screening scenario may need a clear view of usable roof surfaces and an electrical-service question. A commercial facility may require a much more specific understanding of operating constraints, access, roof work, metering information, or a utility route. A battery discussion can create a different set of load and resilience questions.

Begin with the next decision. Is the team preparing a revised concept? Confirming whether a proposal basis can progress? Gathering information for an appropriate technical review? Planning a field release? The answer determines the required evidence. Define the project’s scope and release boundary before requesting evidence. As a concrete vendor example, SolarPlus’s site-survey documentation separates building and roof information, electricity supply details, photos, route lengths, battery-location information and customer preferences. This shows why a single roof photograph cannot answer every workstream; it is not a mandatory field list for all jurisdictions or a claim about SurgePV functionality.

Turn Open Questions Into Field Prompts

The design or project lead should convert assumptions into explicit questions before the visit. Each question should say what observation will be useful and what the team must not infer from it.

This structure protects the surveyor as well as the next team. It prevents a request for “everything you can find” from turning into an assumption that the field person has certified matters outside their role or observation.

Make Each Observation Identifiable

An evidence package should allow a later reader to understand what they are seeing. For photographs, record the date, project/site identifier, a short description, and where possible the direction or area shown. For notes, identify who made the observation, whether it is first-hand or customer-provided, and the question it addresses. For measurements, say how they were obtained and whether the value is an observation, a supplied drawing value, or an estimate.

This is not a demand for perfect metadata. It is a way to avoid false precision. A roof photo can be highly useful without proving a dimension. A customer’s statement about a planned roof replacement can be relevant without becoming a project instruction. A panel image can prompt an electrical review without authorizing a configuration choice. State what the item supports now and what still requires a different process.

For hazards and structural questions, route the evidence to the appropriate professional. The U.S. DOE’s severe-weather design guidance ties site weather risk to engineering requirements and design review. A survey image can identify an exposed location; it does not establish wind-load capacity or verify an attachment design. Apply the relevant local requirements to your project rather than treating U.S. guidance as a universal rule.

Organize the Package Around Decisions, Not Media Types

Do not deliver one folder called “photos” and another called “notes” without a map. Organize the return around the decisions it informs. A simple package may have sections for roof/layout observations, electrical/route observations, access and operational constraints, customer-confirmed information, and open questions. Each section can link to the related image set or source record.

The structure becomes especially valuable when someone did not attend the survey. A designer can open “roof/layout observations” and see the evidence that changes the layout. A project manager can open “open questions” and see what prevents the next milestone. Procurement can avoid receiving an early material list without understanding whether a site observation has changed the basis.

Add an evidence index that another designer can use

The following is an original hypothetical format, not a completed customer survey. Keep the index alongside the images and notes so a new reviewer can locate the basis for a decision.

Record the evidence file name, capture date, author and relevant drawing reference in the working index. Do not turn a statement such as “not inspected” into a failed condition, or “no visible damage” into a certification. Both are observations with limits.

Restrict the package to the project information reviewers need. Store customer bills, contact details and interior photographs in the agreed project workspace with appropriate access rather than adding unrelated personal information to a general photo folder.

Record Negative Findings Carefully

“No issue found” can be dangerous when the survey scope was limited. Instead, record what was observed and the conditions of observation: “No visible obstruction observed on the photographed area at the time of visit,” for example. This statement has a defined meaning. It does not claim that no hidden, future, structural, electrical, or regulatory issue exists.

The same discipline applies to customer conversations at site. Capture what the customer said, identify it as customer-provided information, and route any matter that needs confirmation. It is more useful to write “customer reported planned roof work; confirmation required before final release” than to either ignore the statement or present it as verified scope.

Reconcile Survey Evidence With the Controlling Revision

The first task after a survey is not to redraw everything. It is to compare survey findings against the current project basis. Ask: did any observed condition change usable area, equipment route, scope, access plan, customer expectation, or a listed assumption? If yes, create a controlled decision or change entry and identify which records need review.

This prevents the common failure where a designer quietly updates a layout while the proposal, price basis, and material list remain attached to the earlier concept. The evidence package should support the survey-to-design process, while the responsible reviewer decides whether the finding needs a customer conversation or qualified assessment.

Route What the Survey Cannot Resolve

A well-run survey can produce more questions, and that is often a good result. The field record should state the unresolved issue, why it matters, the evidence currently available, and the required route. Examples may include a condition needing engineering assessment, an electrical question requiring appropriate review, a utility instruction to be confirmed, or an authority requirement outside the survey scope.

Avoid asking the surveyor to decide matters outside their assigned task. Their contribution is a clear observation and a well-defined question. The project lead then assigns the right reviewer and defines what output is needed before the next release.

Close the Loop With the Person Who Visited the Site

If a returned package raises a question, bring it back to the surveyor while the visit is fresh. Ask a bounded question: “Does image 14 show the north service wall?” or “Was the obstruction shown in image 8 visible from the roof surface?” Do not ask them to infer an answer they did not observe. The purpose is to preserve context before the project record becomes detached from the person who created it.

This short feedback loop also improves future briefs. When field teams see exactly how design used an image or note, they learn which labels and viewpoints make a later decision easier. When designers understand the conditions of a site visit, they are less likely to read a photograph as more complete evidence than it is.

Keep Customer-Provisioned Documents Separate

Customers may provide roof plans, equipment information, prior reports, or correspondence during a visit. Retain those documents, but label them as customer-provided unless the project has independently established another status. A useful package can say: “Customer-provided drawing received at survey; used as a reference pending confirmation of current conditions.” That small distinction preserves provenance and helps the next reviewer decide whether another source is required.

Use Survey Returns to Improve the Brief

Track why design returns survey packages. Were images unidentifiable? Were key panels not shown? Did notes lack dates? Did the survey not address the stated layout question? Were known conditions not reflected in the proposal? These patterns usually point to a briefing or handoff problem, not an individual failure.

Improve one upstream step at a time: add a project-specific prompt, show an example of useful evidence, require a source label, or clarify the release decision. Avoid turning a small internal sample into a universal performance claim. The goal is a better package for the next site.

Practical Next Steps

1. Start every survey with named decisions and open questions, not a generic media list.
2. Require each returned observation to state what it shows, when, where, and what it does not establish.
3. Compare survey findings with the controlling project revision before passing work to procurement or field teams.

Before evaluating SurgePV’s design workflow, bring a sample index, survey return and controlling design revision. Ask which inputs, attachments and outputs are supported for your team’s handoff. Discuss the requirements in a demo; do not assume the software validates a site observation or replaces professional review.

Frequently Asked Questions

What is a solar site-survey evidence package?

It is a structured set of survey observations and source records linked to the project decisions they support, rather than an unlabelled collection of photographs or notes.

Can remote imagery replace a solar site survey?

Remote information can support early screening, but it does not verify on-site conditions, access, electrical details, safety requirements, or other facts needed for a defined field or technical release.

Who should define solar survey questions?

The person responsible for the next design or project decision should define the questions, with input from field, engineering, operations, sales, or qualified reviewers where needed.