Skip to main content
Case study (privacy‑safe)

Survey reports the next team can use without re-questions

This is the pattern we keep seeing: the site visit happened, but the next team still had to chase basic answers.

Details changed for privacy, but the problem is real.

Delivery timing: the report and organised photos are available in the portal immediately on completion of the visit. EPC is delivered by the next morning. If a calculation is required, it is delivered the next day.

Surveyor with iPad and homeowner at property with solar and heat pump

Surveyor with homeowner at the property — the kind of clear report structure this case study is about.

Where jobs usually start going wrong

Most delays come from missing evidence, vague notes, or photos dumped in the wrong place.

Problem

Evidence scattered

Photos exist, but aren’t grouped by purpose (access, routing, constraints), so the team still has to ask questions.

Problem

Assumptions undocumented

A designer can’t tell what was confirmed on site vs assumed later — so they pause or re-check.

Goal

Next person can act

The report should make it obvious what matters and what to do next.

What we capture and how we lay it out

We collect it once and lay it out so someone else can use it without a phone call.

Evidence

Photos grouped by decision

  • Access + constraints
  • Routing + entry points
  • Clear “why this matters” notes
Clarity

Assumptions made explicit

  • What was confirmed on site
  • What’s still to be decided
  • Where extra info is required
Delivery

Fast delivery

  • Report + organised photos: portal access immediately upon completion of the visit
  • EPC: delivered by next morning (when included)
  • Calculation outputs delivered next day when required

What made the report usable for the next team

The useful part of the survey was not only speed. It was that the next person could see the site facts, the limitations, and the questions still open without asking the surveyor to explain the job again.

Office review

The quote could be checked against evidence

Photos and notes were grouped around access, routing, equipment, and constraints, so the office could see what had actually been confirmed on site before quoting assumptions went too far.

Design check

Design could see what still needed a decision

A strong survey handover separates evidence from unresolved decisions. That reduces the risk of a designer treating a guess, a customer comment, or an unavailable area as confirmed survey fact.

Install planning

The install crew got context early

When access, route, and constraint photos are visible in the first report, installation planning can start before the job reaches the diary and before avoidable site-day surprises become expensive.

More real-world examples