Skip to main content

Solar panel survey deliverables: roof context for design

A good solar report makes the roof “readable” for design and install decisions.

Related: solar survey reports · roof assessment guide · view sample report

The aim is clarity: roof context, obstruction evidence, and notes that remove guesswork when questions come up later.

1) Roof overview + scaling

  • Wide photos of each roof face
  • Reference shots that support scaling
  • Notes where layout constraints matter

2) Obstructions + constraints

  • Chimneys, vents, skylights, dormers documented clearly
  • Notes that explain the constraint (not just the photo)
  • Evidence grouped by category for fast review

3) Electrical evidence (where required)

  • Meter / cut-out / consumer unit photos
  • Main fuse rating and spare ways captured
  • Constraints highlighted early

How to use this page on a live job

Use this guide as a decision check, not as a generic reading page. The useful question is whether the evidence behind solar panel survey deliverables: roof context for design is strong enough for an installer, designer, or homeowner to move to the next step without another round of avoidable questions.

Before booking

Confirm what evidence is missing

For solar survey evidence, the weak point is usually not the headline requirement. It is the missing photo, document, measurement, or site note that stops the next person from trusting the job record.

During survey

Capture the detail once, then label it properly

A survey report should show what was seen, what was measured, what could not be accessed, and what still needs a design or installer decision. That keeps assumptions visible instead of hiding them inside a photo set.

After delivery

Use the report to reduce internal handover friction

The office, design, and install teams should be able to open the same report and understand the evidence path. If the page helps you spot what to ask for before survey day, it has done its job.

For a live project, pair this guidance with the sample report, deliverables, and guide price builder so the job is reviewed against the same standard Vertex uses for survey delivery.

The practical test is whether the page changes what happens next on a real property. If it helps your team ask for the right evidence, avoid a weak assumption, or brief the surveyor more clearly before the visit, it is supporting the job rather than adding another generic resource to the pile.

For Vertex, that means turning the article into action: check the evidence route, agree the scope, then capture the site detail in a report the next team can read without rebuilding the job from memory.