Solar Site Survey Process: What to Capture and What to Escalate

A solar site survey should leave the next reviewer able to explain what was observed, what was only reported, and what still needs a decision. If the output is a folder of unlabeled images and an enthusiastic verbal handoff, the team has not finished a survey; it has moved uncertainty downstream.

This guide is desk research for installers and EPCs. It is not a substitute for workplace safety obligations, local code, utility requirements, engineering, roof assessment, electrical design, or authority review. OSHA’s solar fall-hazard guidance addresses roof edges, skylights, hatches and task-dependent fall protection. Its solar electrical guidance identifies electrical exposure and training requirements. These are U.S. references; use the applicable local requirements and competent roles for the actual site.

Start Before the Assessor Travels

The survey process begins with a review of what is already known. Sending someone to an address without a purpose encourages duplicate questions and missing evidence. The project owner should prepare a one-page brief that distinguishes customer statements, existing documents, remote observations, and gaps.

The brief needs a specific intended output. A preliminary residential proposal may require a smaller evidence set than a permit-ready drawing. A battery discussion has different questions from a simple grid-connected screening. A commercial facility with unusual operating hours may need interval data and stakeholder input before a financial scenario is meaningful.

Ask the customer for documents in plain language. “Please send the latest complete bill” is more actionable than “provide energy information.” Explain why: a short estimate may help initial discussion, while a dated bill or interval record is needed to examine a particular load or tariff question. Evidence collection works better when the customer knows the decision it unlocks.

Establish Safe, Lawful Access First

No survey checklist overrides site safety rules. Confirm access arrangements, induction needs, escort requirements, restricted areas, relevant weather considerations, roof access rules, and emergency information before work begins. Stop where conditions exceed the assessor’s authority, training, or the agreed plan.

Avoid boilerplate language such as “roof safe” unless the responsible process has actually made that determination. An assessor can record observed access conditions, signs, photos, and questions; those records do not replace a competent safety assessment or a site-specific work plan. The distinction matters because early commercial pressure can make an informal walk-around appear more conclusive than it is.

Capture Evidence in a Reviewable Order

A useful capture sequence follows the way a reviewer will reason about the site. Begin with identity and context, then record the physical areas involved, then electrical and operational observations, and finally unresolved constraints. Give every photo a useful filename or record reference. An image named “IMG_3281” needs an index that identifies its subject and location. The original file can remain useful when that context is retained.

SolarPlus’s site-survey documentation provides a vendor example of separating building, roof, supply, route, battery-location and customer information. Adapt your capture form to the project rather than assuming every tool or jurisdiction uses the same fields.

1. Confirm the Project Context

Record the visit date, people present, access boundaries, customer objective, and any changes since the initial discussion. If the customer says a roof replacement is planned, note whether that is a confirmed schedule, an idea, or a condition requiring follow-up. If a tenant occupies the site, identify the party who can authorize the next stage. These are commercial facts, but they can change a technical route.

2. Document Array Areas and Exclusions

Map roof planes, obstructions, penetrations, plant, pathways, obvious drainage features, and areas the customer says must remain clear. Do not decide code clearances from a generic memory. Capture enough evidence for the applicable design and authority process to make its own decision. Where a feature cannot be measured safely, record that limitation rather than estimating a precise value from a photo.

3. Record Electrical Evidence Carefully

Record accessible equipment identifiers, meter locations, visible service context and routes relevant to the defined scope. Opening equipment or carrying out electrical tests requires the appropriate competence, authorization and safe work arrangements; a general survey request does not grant them. State what the image shows, not what it proves. For instance, “label photographed at panel A” is a defensible record. “Final interconnection capacity confirmed” is not, unless the competent utility and electrical processes have confirmed it.

4. Surface Operational Constraints

Commercial customers often know facts that an image cannot reveal: shutdown windows, production periods, roof-warranty conditions, future equipment, fleet electrification plans, landlord approvals, or maintenance restrictions. Ask for these in an interview section and note who supplied the statement. Such information can determine whether a technically feasible layout is commercially workable.

Separate Observations From Conclusions

This is the discipline that makes a survey useful. An observation has a source: photograph, measured note, customer statement, drawing, or inspector record. A conclusion applies a standard, design rule, or professional judgment to that source. Combining them hides the review path.

The distinction is especially important for customer-facing material. A proposal may show a concept and outline the next verification step. It should not quietly replace that verification. Clear status labels make the sales conversation more credible because the customer can see what will happen next rather than discovering a condition after a number has been treated as final.

Use a Stop-and-Escalate List

The surveyor should have permission to pause. Typical escalation triggers include uncertain structural condition, inaccessible areas that control the layout, unclear ownership or roof rights, missing electrical information, visible conflicts with planned work, safety concerns, unusual equipment, conflicting utility information, or a request beyond the agreed scope.

Each trigger needs a route: who owns the next question, what evidence is required, and whether preliminary work can continue. “Ask engineering” is too vague. A usable record says, “Electrical service documentation required before final equipment selection; owner: project coordinator; input: current one-line and qualified review.”

Preserve the Evidence Chain After the Visit

Survey information ages quickly when it is detached from its source. Put the visit date on the brief, keep original files in a controlled location, and record when a drawing or customer statement supersedes an earlier item. A later designer should not need to infer whether a roof photograph predates a reroof or whether an equipment label came from the correct building. Where an issue is resolved, retain the resolution source as well as the original question. This creates a traceable path from field observation to project decision without pretending that every early record is permanent.

For portfolios and repeat work, a short naming convention helps: project identifier, capture date, area or equipment reference, and evidence type. The point is retrieval, not bureaucracy. A clear file name and issue reference can prevent a crew, estimator, or reviewer from using a nearly identical image from a different building.

Close the Survey With an Issue Log

The finish is not the last photo. It is a handoff that another person can use without reconstructing the visit. Create an issue log with a source, status, owner, due date, and project impact. Make the link between an issue and an output explicit.

Use the survey evidence-package guide to index the returned material. The responsible team still decides whether the evidence is adequate for the next release. For the capture topics themselves, use the site-survey checklist.

Review the workflow against one real project

Before evaluating SurgePV’s design workflow, bring a survey brief, returned evidence and controlling revision. Ask which project-input and output functions are available for your handoff. Discuss the requirements in a demo; software does not certify the observations or replace responsible review.

Frequently Asked Questions

What is the purpose of a solar site survey?

Its purpose is to collect and classify the site evidence needed for a stated project decision, while making unknowns and specialist questions visible.

Does a site survey approve a solar installation?

No. A site survey is an evidence activity. It does not replace engineering, authority approval, utility approval, safety planning, or installation controls.

How long does a solar site survey take?

There is no responsible universal duration. It depends on property complexity, access, documents, system scope, safety controls, and the decisions the visit must support. Set the scope before scheduling rather than promising a time without context.

What happens after the site survey?

The team reviews the evidence, resolves or labels gaps, updates the design brief, and chooses the next output: a qualified concept, more evidence collection, specialist review, or a controlled release.