Solar Site Survey Data Collection: What to Capture Before Final Design

A solar site survey is not successful because it produces a large photo folder. It succeeds when the next person can use the evidence to make the correct decision without repeating the visit or guessing what the surveyor meant. For installers and EPCs, that means planning the survey around decisions: can a preliminary layout be refined, what needs specialist review, what must be explained to the customer, and what cannot proceed until further evidence is obtained.

This is a desk-research field-workflow guide. It is not a substitute for safe-work procedures, local requirements, engineering, structural assessment, electrical inspection, utility rules, manufacturer instructions, or professional judgment for an individual site. The U.S. Department of Energy’s homeowner guide to going solar describes common steps in a solar project; it does not establish a field-survey method for every building or jurisdiction.

Design the Survey Backwards From the Next Decision

The first question is not “what does the form ask for?” It is “what will the project team decide after this visit?” A residential preliminary design may need roof features, access observations, electrical photographs, and a clear record of what remains unverified. A commercial screening project may need information about load behavior, operating constraints, roof use, meter arrangements, and the people who control access. A battery conversation may involve different questions from a grid-tied PV proposal.

Write the expected output at the top of the survey brief. Examples include:

• refine an indicative roof layout after field confirmation;
• prepare a request for engineering or specialist review;
• identify whether more energy data is needed before commercial modeling;
• prepare a customer proposal that states its site and scope boundaries;
• determine that a project should pause while an access, roof, electrical, or authority question is resolved.

This framing changes the quality of the visit. It prevents a field colleague from collecting details that no one uses while missing the one observation that would change the system concept. It also makes it legitimate to record “not observed” or “access unavailable.” An honest gap is better than an inferred fact presented as a survey result.

Set Up the Visit Before Arriving

The survey begins in the project record, not in the parking lot. Review what the team already has: address, customer objective, bills or interval data if relevant, imagery, existing drawings, proposal history, equipment discussion, prior site notes, and known constraints. Bring only questions that change the next decision.

Confirm the site contact, access arrangements, areas that may be photographed, safety requirements, and whether another party needs to attend. For an occupied commercial property, ask about operating hours, restricted zones, shutdown limitations, roof use, planned works, and the location of electrical records. For any site, do not assume that the person who opens the door can confirm structural, electrical, ownership, utility, or authority facts.

A useful pre-visit brief separates statements from evidence. “Customer says the roof was replaced recently” is a statement. A dated project document or qualified assessment may be evidence for a different decision. Preserve both, but label them correctly. This reduces the chance that an oral comment is carried into a final design as though it had been verified.

Capture Evidence, Not Just Images

Photos are powerful because they preserve context, but only if the reader can understand what they show. Every important image should have a simple label: date, location or orientation, subject, and why the image matters. “IMG_2217” does not help a designer recognize whether a panel photograph belongs to the main service, a subpanel, a neighboring structure, or an unrelated piece of equipment.

Use a consistent sequence. Start with site identity and approach. Then capture array areas, edges and visible obstructions, relevant access paths, equipment locations, electrical areas, meters where appropriate, and any condition that contradicts the current design basis. Pair a wide context image with a closer detail when the relationship matters. Avoid photographing personal or sensitive information unnecessarily, and follow the property’s access rules.

The National Renewable Energy Laboratory’s photovoltaic research resources provide broad technical context for PV. They cannot determine whether a particular roof, service, or structure is suitable. A survey record should therefore describe what was seen, not leap from an observation to an unsupported conclusion. “Visible conduit route is not confirmed” is a strong note. “No electrical work required” is not a field observation unless the responsible review has made that determination.

Organize Field Information Into Four Evidence Groups

Grouping observations prevents the survey from becoming a long, unprioritized checklist. Four groups cover most early solar field work while leaving room for project-specific additions.

1. Site, Space, and Access

Record the physical identity of the area under consideration. Note building sections, roof planes, ground areas, adjacent features, access routes, apparent obstructions, planned works disclosed during the visit, and restrictions on installation or maintenance access. Capture dimensions only with the method and limitations understood; a rough measurement should not masquerade as a final dimension.

For rooftop work, do not make structural conclusions from a walk-through. A survey can identify questions for the responsible review, such as visible roof changes, access limitations, or unclear building information. It cannot replace the assessment required by project scope or local rules.

2. Array Conditions and Shading Context

Document visible roof features, skylights, vents, plant equipment, parapets, neighboring structures, trees, and seasonal or time-specific limitations that the project needs to consider. State the observation time and view. A tree observed from one direction at midday does not prove an annual shading profile.

This is the appropriate place to use Shadow Analysis as part of a connected workflow. A tool can model a defined design scenario from its inputs. The field team still needs to verify what exists on site and the project team must decide whether the available evidence supports the intended release.

3. Electrical and Equipment Context

Record accessible electrical labels, panel locations, meter locations, visible equipment, space constraints, and the source of any service information. Do not open equipment, perform electrical work, or infer ratings outside the authorized and qualified scope. If a detail must be interpreted by a licensed or qualified person, capture the evidence and route the question rather than converting it into a design choice in the field.

The field note should answer: what did we observe, where is it, what source supports it, and what decision is blocked or affected? It should not diagnose a system from a photo alone.

4. Customer Operations and Project Constraints

A technically possible layout can still fail commercially if it conflicts with the customer’s operating reality. Ask about access windows, roof-use plans, business continuity needs, equipment deliveries, landlord or tenant roles, noise or visual concerns, outage tolerance, and decision deadlines. These are not engineering facts, but they shape whether the proposed approach is usable.

Keep stated needs in the customer’s own terms. “Customer wants backup” may mean different things to different people. The next action may be to clarify critical loads, desired operating behavior, and the evidence required before a battery scenario is modeled.

Record Unknowns as Findings

An incomplete observation is itself a survey result when it changes what the team can responsibly do next. Common examples include inaccessible roof zones, missing electrical documentation, unclear meter relationships, unavailable interval data, planned reroofing, uncertain tenancy, and a customer request that exceeds the stated scope.

Write each unknown in a format that creates motion:

This approach avoids an unhelpful binary between “survey complete” and “survey failed.” A visit can provide valuable evidence while still identifying work that must happen before the next release.

Make the Handoff Reviewable

The surveyor’s job is not finished when the files sync. A useful handoff includes a short summary written for the person making the next decision. Lead with what changed from the planning basis, what is confirmed, what remains open, and what output is appropriate now.

For example: “The preliminary layout can be refined on the east and south roof sections based on observed features. The west section was not accessed and remains excluded. The electrical information photographed requires qualified review before final configuration. Customer reports a re-roof discussion next year; sales to clarify timing before final contract scope.” This is far more useful than “survey completed, photos attached.”

Attach the survey to the relevant project version. If new evidence changes the layout, module count, equipment location, or financial inputs, update the design basis and record who approved the revision. A solar design software workflow can make inputs and outputs easier to keep together, but it cannot decide whether a field note is sufficient for a technical, contractual, or regulatory release.

Use a Short Survey-to-Design Review

Before a detailed proposal or technical package is released, hold a brief comparison between the initial basis and the field record. Ask:

1. What observed fact changes the proposed layout, equipment, scope, or customer narrative?
2. Which source materials are current enough for this release?
3. Which early inputs remain planning assumptions?
4. Does any finding require engineering, electrical, structural, utility, contractor, or authority review?
5. Does the customer-facing explanation state the remaining conditions clearly?

This does not need a meeting for every simple job. It does require an owner. Without one, the organization relies on people remembering which picture contradicted which early note.

Build a Field Form That Encourages Good Judgment

A form should prompt evidence collection, not force false answers. Use “observed,” “not observed,” “customer stated,” “document supplied,” and “requires review” as valid response types. Keep mandatory fields limited to project identity, visit date, surveyor, intended output, and safety or access outcomes. Then make project-specific prompts conditional.

For example, a field form could show battery questions only when the opportunity includes storage, or commercial operation questions only when the site is non-residential. This reduces rushed checkbox behavior and gives the surveyor more time to document what actually changes the design.

After several projects, inspect the reasons for re-visits or late changes. If a specific question repeatedly appears after design begins, add it to the pre-visit brief. If field data is consistently hard to interpret, improve the photo labels or handoff summary. Do not use a small internal sample to make broad claims about project outcomes. Use it to improve the team’s own evidence flow.

A Practical Solar Site Survey Checklist

Use this as a starting point and tailor it to the site, authority, contract, and safety requirements:

• Confirm project identity, visit purpose, contact, and permitted access.
• Review known information and list the decisions the visit must support.
• Capture site, array-area, access, obstruction, equipment-location, and electrical-context evidence with clear labels.
• Distinguish direct observation, customer statement, supplied document, and unresolved question.
• Record site or operational conditions that could change scope, price, model inputs, installation approach, or customer expectations.
• Route any structural, electrical, utility, authority, or safety question to the appropriate responsible reviewer.
• Produce a short handoff statement describing what can proceed and what remains conditional.

The checklist does not certify a project. It makes the survey useful to the people who must design, communicate, and review the next step.

Frequently Asked Questions

What information is collected during a solar site survey?

The scope varies, but a survey commonly records site identity, usable areas, obstructions, access, roof or ground observations, electrical information, photographs, customer constraints, and the open questions that affect the next project decision. Each item should retain its source and observation date.

Can satellite imagery replace a solar site survey?

Imagery can support an early layout or planning conversation, but it cannot by itself verify physical access, site condition, dimensions, electrical details, or jurisdiction-specific requirements. Treat imagery-derived information as appropriate planning evidence, not a field verification.

Who should review solar site survey findings?

The appropriate reviewer depends on the finding and project scope. Field observations should be routed to the qualified designer, engineer, contractor, utility, authority, or other responsible role needed for the next decision. For a customer discussion, Solar Proposals can keep the presentation connected to the current project record.