12-Point Solar Site Assessment Checklist

Two assessors can visit the same roof and return with hundreds of photos, yet neither packet may be design-ready. One misses scale. The other does not identify which roof plane each image shows. Neither records whether the service photo belongs to the current project revision.

The problem is not effort. It is evidence structure. A useful site assessment connects each observation to a project, location, time, method, unit, source, uncertainty, and downstream decision. It also marks what the assessor could not safely or authoritatively determine.

This 12-point solar site assessment checklist defines a handoff for design-ready data. It does not authorize roof access, electrical work, drone operation, structural judgment, geotechnical interpretation, code decisions, utility conclusions, or engineering. The company safety plan, applicable rules, qualified reviewers, manufacturer instructions, and verified conditions remain controlling.

The solar site survey evidence package covers package organization. The permit-ready design workflow covers later design stages. Here, the job is the evidence acceptance boundary between assessment and design.

What does design-ready solar site data mean?

Design-ready solar site data is evidence accepted for a named design task. It identifies project, site, source, observation date, method, units, coverage, uncertainty, revision, and reviewer; includes required records; contains contradictions; and states remaining gaps and use restrictions. It does not claim the site or design is feasible, safe, compliant, approved, or construction-ready.

Name the output before collecting evidence. A preliminary roof-fit response, detailed layout, shading study, electrical model, structural review, proposal, permit set, procurement release, and construction package do not require the same data or authority. “Site survey complete” means little without that purpose.

DOE’s overview of solar photovoltaic system design basics describes PV systems through modules, mounting structures, power electronics, and, in some systems, storage. That system view explains why the packet needs more than roof dimensions. It does not define a private survey standard or validate any project.

The receiving designer should accept the packet explicitly. Upload completion is not acceptance. A complete form can still contain the wrong site, old images, ambiguous units, or evidence that cannot support the requested output.

Which 12 evidence groups belong in the checklist?

Cover 12 evidence groups: project identity and purpose, source provenance, usable surfaces and geometry, obstructions and setbacks, shading context, structural or ground conditions, electrical service and equipment, routes and connection areas, equipment placement and work access, governing requirements and external decisions, safety and access restrictions, and the reviewed gap-to-design handoff. Each group needs coverage, source, uncertainty, and ownership.

1. Project identity and assessment purpose

Record the normalized address, coordinates where appropriate, customer or account, site contact, property or parcel identifiers, project id, opportunity id, assessor, observation date, time zone, weather where it affects evidence, and requested output. Photograph a site identifier when policy allows.

Prevent cross-project contamination. Similar street names, multi-building campuses, unit numbers, adjacent parcels, and reused customer folders can attach good evidence to the wrong project.

2. Source provenance and collection method

For each evidence item, record who collected or supplied it, when, how, with which device or document, in what units, under what coverage, and with which limitation. Preserve originals separately from annotations and compressed exports.

If a dimension comes from imagery, a tape, a laser, a drawing, or customer report, state that method. Do not merge values into one “measurement” field without source identity.

3. Usable surfaces and geometry

Identify roof planes, ground areas, carports, canopies, façades, or other candidate surfaces using stable ids. Capture orientation, slope or tilt where within the approved method, boundary geometry, dimensions, surface transitions, elevations or relative levels, and enough overview context to place detail images.

Do not label a surface usable before structural, access, setback, ownership, shading, equipment, and other controlling questions are reviewed. The assessment records evidence, not final array capacity.

4. Obstructions, edges, and access features

Record parapets, ridges, hips, valleys, drains, vents, skylights, hatches, equipment, antennas, vegetation, adjacent structures, overhead conditions, walk paths, edge conditions, and other objects relevant to the requested design task. Give each object a location, dimensions where authorized, height or envelope where relevant, and image references.

An object can matter even when the preliminary layout avoids it. It may influence shade, access, maintenance, drainage, structure, safety, routing, or future work.

5. Shading and surrounding context

Capture the visible horizon, trees, buildings, roof objects, terrain, and seasonal or future-change limitations relevant to the approved shade method. Record observation time, tool, model source, imagery date, and any areas that were hidden or inaccessible.

Do not turn one clear photograph into an annual production conclusion. Shade modeling needs the selected method, geometry, time basis, weather or resource source, loss assumptions, and qualified review.

6. Structural or ground-condition evidence

For rooftop work, record visible roof type, covering, apparent age only when sourced, framing evidence accessible under the approved method, spans and spacing when actually observed, penetrations, visible distress, repairs, water signs, and areas not inspected. For ground work, record terrain, drainage evidence, surface condition, access, visible utilities, and available reports.

Site assessors should not diagnose structural capacity or geotechnical suitability unless qualified and authorized. Preserve observations and route the decisions.

7. Electrical service and equipment records

Identify service location, meter, main equipment, labels, ratings, available diagrams, visible conductors and raceways only within safe authorized observation, generation equipment, storage, transformers, disconnects, backup systems, and other relevant existing equipment. Photograph complete nameplates and the equipment context where permitted.

Never open energized equipment or enter restricted areas merely to complete a checklist. Missing electrical evidence is a gap for a qualified follow-up, not permission to exceed training or safe procedure.

8. Routes and connection areas

Map possible equipment, conductor, communication, grounding, and access routes as observations or candidates, not approved designs. Record length basis, elevation changes, penetrations, fire or access zones, hidden sections, congestion, existing services, and surfaces or spaces requiring additional review.

The point of interconnection and electrical routing require qualified design, utility, code, manufacturer, field, and authority decisions. The assessment makes site relationships visible.

9. Equipment placement and work access

Record candidate areas for inverters, batteries, disconnects, transformers, gateways, and balance-of-system equipment together with clearance, environment, access, security, noise, flood, ventilation, heat, ignition, and customer-use observations as applicable. Do not approve a location from space alone.

Also document delivery, staging, lifting, roof access, emergency access, and maintenance routes within the assessor’s authorized scope. Separate customer preference from accepted technical placement.

10. Governing requirements and external decisions

Collect current available utility, authority, permit, planning, fire, heritage, environmental, landlord, owner, insurer, program, and manufacturer records relevant to the named task. Identify their source, jurisdiction, date, revision, applicability status, and responsible interpreter.

The NFPA 70 development page identifies NFPA 70 as a United States electrical safety benchmark. The IEEE 1547 page identifies a distributed-energy interconnection standard. Neither page determines the adopted rule, edition, local amendment, utility practice, interpretation, or approval for this project.

11. Safety and access restrictions

Record access permission, site induction, hazards reported by the responsible site owner, roof or edge restrictions, electrical boundaries, confined or restricted areas, weather limits, traffic, animals, public interaction, and stop-work conditions under company policy. The assessor should know what not to collect.

OSHA’s construction rule on fall protection contains requirements for covered United States construction work. Applicability and the complete safety plan require qualified review. A content checklist cannot replace employer duties, hazard assessment, training, equipment, supervision, or a competent person’s decisions.

12. Gap register and accepted design handoff

Close the assessment with missing, conflicting, stale, inaccessible, low-confidence, and unauthorized items. Each gap needs the affected design decision, permitted preliminary work, owner, required evidence, priority, due event, and re-entry state.

The receiving designer reviews project identity, task, coverage, contradictions, and critical evidence, then accepts, narrows, holds, or returns the packet. Preserve that disposition with the assessment revision.

Run photo and measurement QA as separate checks

A photograph can be legible and still fail measurement QA. It may lack a scale, object id, direction, full equipment label, surrounding context, or a connection to the measurement record. Conversely, a dimension can look precise while its endpoints, plane, units, device, method, and environmental limitations are unclear.

Review images first for identity, coverage, legibility, sequence, context, original-file preservation, and privacy handling. Review measurements separately for object, endpoints, orientation, source, units, resolution, repeatability, device, calibration or verification process where applicable, and any transformation or rounding. Then check that the two records point to each other.

Use cross-views for critical objects. An overview locates the object, a medium view shows relationships, and a detail view captures the necessary label or condition. Do not turn this into a universal photo count. One clear evidence chain is more useful than many unlabeled images, and hazardous access should never be added merely to satisfy a content checklist.

Before leaving, compare the packet with the collection map. Confirm that every required object has an accepted record or explicit gap. A ten-minute controlled review at a safe location may reveal a missing context view that would otherwise require another trip, but no speed or revisit reduction is guaranteed.

How should the assessment be planned and handed off?

Plan and hand off the assessment in seven stages: define the design output, create the evidence contract, review available remote and provided sources, prepare a safe collection plan, gather and label observations, run completeness and contradiction checks, then obtain an explicit receiving disposition. Preserve originals, calculations, annotations, gaps, and revisions so later design changes can trace back to evidence.

1. Define the requested output. State what the designer must decide and the evidence classes required.
2. Create the collection map. Assign stable ids to buildings, surfaces, equipment, objects, routes, documents, and expected images.
3. Review existing sources. Inspect imagery, drawings, bills, equipment records, prior surveys, authority material, and known gaps before travel.
4. Authorize the collection plan. Confirm access, safety, privacy, device, drone, electrical, roof, weather, and qualified-person boundaries.
5. Collect with provenance. Link each item to source, time, method, units, object id, coverage, confidence, and limitation.
6. Run QA before leaving and before handoff. Check identity, scale, coverage, legibility, contradictions, required views, and unclosed gaps while corrective collection may still be possible.
7. Obtain receiving disposition. The designer accepts, narrows, holds, or returns the packet with exact reasons and re-entry evidence.

NASA describes configuration management as providing visibility into and control of changing characteristics. A site assessment is not a NASA program. The useful analogy is baseline control: site evidence, model inputs, design revisions, comments, and releases need stable identities so a later reviewer knows which observation supported which decision.

How should missing or conflicting site evidence be handled?

Handle missing or conflicting site evidence by preserving every source, classifying the gap, stopping only affected decisions, assigning a qualified owner, and defining the evidence needed for re-entry. Do not average conflicting dimensions, choose the clearest photo, or let a placeholder become a design fact. The packet should state what preliminary work remains allowed and which outputs are restricted.

Use five gap classes: missing, where no accepted source exists; conflicting, where sources disagree; stale, where a material site or project change may invalidate evidence; inaccessible, where observation was unsafe, unlawful, or outside authority; and insufficient, where source coverage or quality cannot support the decision.

Do not make the assessor responsible for resolving every technical question. Their job is to preserve the condition and route it clearly. A qualified reviewer may request a different measurement, manufacturer record, utility document, structural investigation, geotechnical work, electrical inspection, customer confirmation, or authority decision.

Illustrative workflow, not a customer case

A roof assessor records two different service ratings: one from an old drawing and one from a visible equipment label. The assessor does not select either value. Both sources enter the gap register with dates, image references, and the electrical-model decision they affect.

The designer accepts geometry work but holds the electrical output. A qualified electrical owner is assigned to verify the current service record. This example makes no customer, design, rating, feasibility, code, schedule, savings, or approval claim. It shows how one conflict can narrow the handoff without invalidating every observation.

Copy-ready 12-point site assessment handoff

Use this operating record with the detailed evidence files. Adapt collection fields and authority routes to the project, jurisdiction, hazards, output, and company system.

Attach an image index that includes object id, direction, purpose, timestamp, and source file. Annotated images should point back to untouched originals. If a tool changes metadata or compresses the file, preserve that transformation record.

Where can SurgePV support the handoff?

SurgePV’s repository-verified scope includes solar array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. Once the receiving team accepts the relevant site evidence, these functions can help carry controlled inputs into connected project outputs.

SurgePV cannot observe an unmeasured site, verify hidden conditions, authorize access, direct safety, perform structural or geotechnical work, inspect energized equipment, interpret adopted rules, certify equipment, approve engineering, or make utility, permit, manufacturer, field, or authority decisions.

Use the site survey data collection guide for field-record details, the solar designing platform for verified product scope, and the solar design workflow for what happens after evidence acceptance.

Frequently Asked Questions

What makes solar site data design-ready?

Solar site data is design-ready for a named output when its project identity, source, observation date, method, units, coverage, uncertainty, revision, and reviewer are visible; the required evidence is present or gaps are bounded; contradictions are resolved or held; and the receiving designer accepts the packet. Acceptance does not establish feasibility, engineering, safety, code compliance, or approval.

Can satellite imagery replace a solar site visit?

No universal rule makes satellite imagery or a site visit sufficient for every project. Remote sources can support a bounded preliminary task when their date, resolution, coverage, visibility, and limitations fit that task. Field evidence may still be needed for hidden conditions, dimensions, equipment, access, structure, safety, electrical details, obstructions, and changes after imagery capture.

Who should perform a solar site assessment?

Assign the work according to the project’s hazards, jurisdiction, contract, required measurements, and company authority. A trained assessor can gather approved evidence within their competence and safety plan. Structural, electrical, geotechnical, environmental, code, utility, engineering, drone, roof-access, and other regulated or safety-critical decisions require the appropriate qualified and authorized people.

Should the designer reject an incomplete site packet?

The designer should reject, hold, or narrow the request when missing or conflicting evidence prevents the named output from being prepared responsibly. The response should identify the exact gap, affected decision, acceptable source, owner, allowed preliminary work, and re-entry condition. A generic rejection wastes the visit; silent assumptions make the gap harder to detect later.

Can SurgePV verify all conditions at a solar site?

No. SurgePV can support solar layout, shading, energy-yield and financial modeling, electrical workflow, bill-of-materials output, and proposal generation from supplied project data. It cannot observe a site it has not measured, verify hidden conditions, direct site safety, perform engineering, interpret adopted rules, certify equipment, or replace utility, permit, field, and qualified review.

Design begins with an accepted question

A site packet becomes valuable when the receiving designer can answer three things: which decision this evidence supports, what remains uncertain, and what must happen before the next release. Photo count and form completion cannot answer those questions alone.

Treat the assessment as a controlled evidence handoff. That posture makes gaps visible early, respects field and technical authority, and gives later revisions a traceable source. It also lets a team accept useful geometry while holding one unresolved electrical or structural decision instead of pretending the entire site is either known or unknown.

That distinction keeps useful evidence available without hiding risk.