Solar Site Assessment Methods: Drone, Satellite, and Field Survey

Satellite imagery is useful for deciding whether a solar opportunity deserves more work; it is not proof that a site is ready to build. A drone can add detail, and a field visit can resolve questions that neither image source can answer. The operating rule for installers and EPCs is to match the assessment method to the decision, record its limits, and avoid converting an early image into an unspoken construction assumption.

This is a desk-research workflow guide. It does not replace local aviation rules, site safety controls, structural or electrical assessment, utility requirements, authority review, or professional judgment. The U.S. Department of Energy Solar Energy Technologies Office and NREL photovoltaic research are useful technical starting points; neither source verifies an individual roof.

What Each Assessment Method Can Actually Prove

Site assessment fails when teams speak about “the survey” as if all evidence had the same weight. A customer-supplied roof photo, public aerial imagery, a drone capture, and a technician’s measurements have different dates, viewpoints, limitations, and legal conditions. The useful question is not which is best in the abstract. It is what a reviewer can responsibly conclude from each source.

The FAA’s uncrewed aircraft systems guidance illustrates why a drone should not be treated as a casual camera. Jurisdiction, airspace, property permissions, operating category, weather, observer arrangements, and operator responsibility can matter. Outside the United States, different national and local rules apply. Record the applicable route rather than copying a foreign checklist.

Begin With a Decision Statement

Before booking a visit, write a sentence that names the decision and the evidence threshold. “Check the roof” is not a decision statement. “Determine whether a preliminary 80 kW rooftop scenario may be shown with roof dimensions and service capacity marked provisional” is one. So is “confirm whether the proposed array area conflicts with rooftop plant access before layout issue B.”

The statement prevents over-surveying and under-surveying. A sales screening may only need enough information to decide whether to request bills and propose a conversation. A permit package needs a much higher evidence standard. A construction release has a different one again. When those stages are blurred, teams either dispatch too early or make commitments on data that was only suitable for a lead conversation.

An assessment request should name: the intended deliverable; the site identifier; documents already reviewed; questions to resolve; safety and access arrangements; responsible person; required photographs or measurements; and conditions that require the assessor to stop and escalate. This is a better handoff than a calendar invitation with an address.

Use Satellite Data as a Screening Layer

Remote imagery is fast because it can be reviewed before anyone travels. It is helpful for spotting large roof planes, nearby trees, parapets, carports, rough access routes, or obvious shade sources. It also helps the sales, design, and operations teams discuss the same visible context. It does not make a measurement, roof condition, ownership boundary, service rating, or utility export position true.

Treat every remote measurement as a planning assumption until a source appropriate to the project stage confirms it. Imagery dates matter. A roof may have been re-covered, an HVAC unit added, a tree removed, or a neighboring development built since capture. Perspective matters too: a feature that appears minor in a nadir image may create a meaningful clearance or access conflict on site.

For a commercial lead, add a short confidence note beside the early layout: “roof geometry derived from imagery; plant, roof condition, and access not verified.” This is not defensive wording for its own sake. It tells the customer and the internal reviewer what the drawing can and cannot support.

Plan Field Work Around Evidence, Not Habit

A reliable site visit is a targeted evidence collection exercise. The assessor should not be sent to “get everything” without knowing why each item matters. The list below separates common evidence classes; exact needs depend on jurisdiction, building type, system scope, and the professional roles involved.

Do not ask an assessor to make conclusions outside their competence. A photo of a roof does not establish structural capacity. A panel label may inform a later qualified review but is not automatically a completed electrical design. The project record should say “observed,” “customer stated,” “planning assumption,” or “verified by the responsible role,” rather than compressing all information into a misleading green status.

Decide Whether a Drone Adds Information

Drone imagery is valuable when it will answer a named question more safely or clearly than ground observation and when the operating plan is lawful. For example, it may document visible rooftop congestion, help distinguish an obstruction from a shadow in older imagery, or capture a viewpoint that assists a qualified reviewer. It should not be ordered because “drone survey” sounds more complete.

Set a pre-flight question list. Examples: Is there an unmodeled roof level? Are the apparent skylights actually skylights? Is the array area interrupted by equipment not shown in base imagery? Is there a visible pathway conflict that needs the site team’s input? If the answers would not change a decision, the flight may add cost and data without reducing risk.

The drone record still needs provenance: date, location, operator, relevant permissions, file location, and a note on what cannot be inferred. Keep privacy, site access, and safety requirements within the proper operating process. Never imply that a visual capture is a structural report, a code approval, or permission to proceed.

Turn Findings Into a Controlled Handoff

The value of an assessment is lost if photos remain in a chat thread and the design file contains different assumptions. Close each assessment with a short decision log. It should name what changed, what remains unknown, who owns each open item, and which output may now be issued.

Use three statuses for significant inputs:

• Confirmed for this stage: a named source supports the intended use.
• Scenario assumption: the team may explore it, but it must remain visible in the output.
• Release blocker: work can continue only after a specified person obtains or reviews the required evidence.

This approach makes Solar Designing more useful because model inputs, assumptions, and proposal explanations can remain connected. Software does not inspect a roof or replace responsible review. It can, however, reduce the chance that a field finding is forgotten when a layout or customer document changes.

A Practical Escalation Matrix

Frequently Asked Questions

Is a drone survey required for every solar project?

No. The project should use the least complex method that produces evidence fit for the next decision. A drone may be useful for specific visible questions, but it introduces operating, permission, and data-management responsibilities.

What should a solar site survey report include?

It should identify the site, purpose, source files, captured observations, unanswered questions, limitations, and the recommended next action. The exact technical content must reflect the jurisdiction and responsible professional roles.

Can remote imagery support a customer proposal?

Yes, as long as the proposal clearly distinguishes scenario inputs from confirmed conditions. It should not imply that imagery alone verified roof, electrical, structural, access, utility, or authority requirements.

Who owns unresolved site questions?

Assign each one to a person or role, a required evidence type, and a decision date. “To be confirmed” without an owner is not a workable control.

Put the Method Behind the Promise

For the next project, do three things: write the next decision before selecting the assessment method; store the source and limitations beside each important input; and issue outputs only at the evidence level they can honestly support. That discipline improves communication before it improves speed.