What happens after the solar site survey

Most solar installers already know how to run a decent site survey. The roof gets measured, the service panel gets photographed, the utility account gets checked, and the surveyor leaves with a phone full of photos. That is useful, but it is not where the margin is won or lost.

The problem usually starts after the truck leaves. A survey finding sits in a shared drive until a designer re-keys it, ops decides whether it changes the scope, sales calls the customer, and somebody issues a change order or a redesign. If that loop takes nine days, the site survey was not the bottleneck. The handoff was.

If you want the short answer to the solar site survey checklist question, it is this: capture the structural condition, service panel capacity, utility and interconnection constraints, equipment substitutions, and a complete photo set. Then make sure the result turns into a structured decision, not a photo dump.

That distinction matters because the same four surprises show up again and again: a structural issue, a service panel or interconnection issue, a utility constraint, or an equipment substitution. The cost is rarely in discovering them. The cost is in the time between discovery and a repriced, re-signed, redesigned, resubmitted job.

What a solar site survey checklist should cover

A good solar site survey checklist should be boring in the right way. It should force the surveyor to capture the facts that the designer, installer, and permit team will actually need later.

• Roof condition, layout, setbacks, and obvious structural concerns.
• Shading, obstructions, and mounting constraints.
• Service equipment size and condition, including the main panel and any subpanels.
• Rapid shutdown path and other electrical details needed for code-compliant design.
• Utility account information, tariff details, and interconnection constraints.
• Equipment locations, conduit paths, and likely trenching or routing issues.
• A complete photo set with enough context to identify the panel, meter, attic access, roof planes, and anything unusual.

That is the table stakes version. It is enough to keep obvious mistakes out of a proposal, and it is the right answer if the reader only wanted a form or template.

For the operational problem, though, the checklist is only the input. The valuable question is what happens when the survey finds something the proposal missed.

Follow one finding from the truck to the customer

Take a common example: the salesperson sold a residential solar site survey job at a system size that needs a 200A service, but the home has a 100A panel. The surveyor notices it, takes photos, and adds a note to the shared drive.

Now trace the job through the company.

• Day 0: The surveyor uploads forty photos and a few notes.
• Day 2: A designer opens the folder, finds the panel photos, and confirms the service upgrade is needed.
• Day 2 or 3: Ops or an estimator prices the panel upgrade and checks whether it affects equipment, labor, or permit scope.
• Day 3 or 4: Sales calls the customer and explains that the price or design has changed.
• Day 4 to 6: The customer thinks about it, asks questions, or waits for a revised proposal.
• Day 6 to 7: A contract amendment or solar change order goes out.
• Day 7 to 8: The designer updates the plan set.
• Day 8 or 9: The permit package is resubmitted.

That is one finding. Count the touches: surveyor, designer, estimator or ops, sales, customer, contract system, designer again, permit coordinator. Count the delays: waiting for the survey output, waiting for review, waiting for repricing, waiting for customer response, waiting for signature, waiting for redesign, waiting for resubmission. None of those are exotic. Together they are expensive.

If you run 20 to 400 installs a year, those days add up fast. They also hide the real issue. A company can have a strong survey form and still lose margin if the finding is trapped in unstructured photos and free text.

Why the handoff is manual

The handoff breaks because each system knows only part of the job.

The survey app or phone camera roll captures images and notes, but often not in a way the CRM can act on. The CRM may track sales stages, yet have no field for “redesign required,” the cause, the dollar impact, or whether the contract was re-signed. The design tool may hold the actual layout decisions, while the change order lives in a PDF, a contract platform, or an email thread.

That means no single record spans the path from finding to fix. The survey output is unstructured by default. Someone has to interpret it, decide whether it changes scope, price it, tell the customer, and push the rest of the job forward.

When that workflow is manual, every job gets its own mini-project. That may be tolerable at low volume. It becomes a margin leak when the same few causes repeat and nobody can measure them.

What to measure if you want to fix the right seam

If you cannot measure the seam, you will guess at the fix. Most teams guess wrong because they can see the survey photos, but not the cycle time they created.

Use definitions that two coordinators would compute the same way.

• Redesign rate: the share of surveyed jobs that require a design change after the site visit.
• Change order rate by cause: how often each finding, such as panel upgrade or roof issue, becomes a priced change.
• Change order rate by dollar: the total value of change orders divided by sold revenue or job count, depending on how you manage margin.
• Days from survey to permit submission: the elapsed time between the survey date and a permit-ready resubmission.
• Second-truck-roll rate: the share of jobs that require another site visit because the first survey missed something or did not gather enough detail.
• Proposal-predictable findings: the share of survey findings that a better sales question, utility bill review, or imagery review could have caught before contract.

The last metric is the most useful one for owners. If a finding is proposal-predictable, the fix may belong in sales or in your proposal process, not in the survey checklist.

That is how you separate a bad survey from a bad handoff. If the same issue keeps showing up after the truck roll, your checklist may be fine and your proposal is the weak point. If the finding is common, but the redesign loop is slow, the problem is downstream.

Fix the process in the cheapest order

The right sequence is usually not software first. Start by making the survey output structured enough to act on.

1. Replace the photo dump with typed fields

Your solar site survey form or template should force the surveyor to classify the finding, not just describe it. For example: service size, main breaker rating, meter location, roof obstruction, attic access, trenching issue, utility constraint, or equipment substitution.

That structure matters because it gives ops a field they can route on. It also makes reporting possible. A note buried in a caption does not.

2. Write redesign and repricing rules

Decide, in advance, which findings trigger a redesign, which trigger a note, and which trigger a price change. If a 100A panel on a job sold for a 200A service always requires a redesign and change order, write that rule down.

The mechanism is simple: clear rules remove the need for three people to improvise the same decision every week. The tradeoff is rigidity. You may need exceptions for edge cases, but exceptions should be the exception.

3. Link the finding to the proposal

If the proposal tool never learns what the surveys keep finding, it will keep selling the same surprises. Feed recurring findings back into sales questions, utility review, and imagery checks before contract.

This is where the loop compounds. Fewer surprises at sale means fewer redesigns, which means fewer change orders, which means less chance of losing the customer after the survey.

4. Integrate only after the rules are stable

At that point, integration becomes worth paying for. If the survey app can write a structured finding into your CRM, create a task for redesign, and open a change order request, the handoff gets shorter.

But integration does not fix a vague process. It only moves bad decisions faster.

Where the common tools stop

Most solar software owns a slice of the job, not the seam between slices. That is why teams still end up with photos in one place, scope changes in another, and the customer conversation somewhere else.

The table below is not a full product review. It is a practical way to see where each category usually stops.

The empty column is the argument. No single category usually owns the full path from survey finding to redesign, repricing, change order, and permit resubmission. That is the seam most installers feel, and the seam most software vendors leave partially covered.

Better has built solar proposal and operating software, including work with Sunny Energy. The recurring lesson is that the valuable system is rarely another design tool. It is the record that spans proposal, survey, redesign, change order, and permit. That is where the days and the margin go, and it is the seam no vendor fully owns. If you want to see where that fits in a broader operating model, start with Better’s energy work.

When to buy, and when to build

You should not build custom software because the current process feels messy. Build only when the economics justify owning the seam.

A simple test is this: estimate how many jobs per year require a redesign after the survey, multiply by the average days lost per job, and add the margin hit from change orders and second truck rolls. If that total cost is large enough to justify months of work, then a custom workflow may pay back.

For a smaller installer, especially one doing under roughly 100 installs a year with one design tool and one AHJ, the better return is usually simpler: tighten the survey form, write the redesign rules, and make the customer handoff explicit. That gets you most of the value without creating new software to maintain.

Build starts to make sense when the same findings repeat across enough jobs that the handoff itself has become a profit center or profit leak. At that point, you are not buying a nicer checklist. You are buying visibility into a process that already exists, just badly.

How to tell whether your problem is the survey or the seam

Take one recent job that needed a redesign. Trace it through your company and answer these questions:

• Where was the finding first captured?
• How many people had to interpret it before the customer heard about it?
• How many days passed before the proposal or contract changed?
• Was the change order priced the same day the issue was identified?
• Did the permit set need to be reissued, and who owned that step?
• Could sales have predicted the issue from the utility bill, photos, or a better upfront question?

If you cannot answer those questions from your current systems, the problem is not just the survey checklist. It is the path from survey to decision.

That is the useful next step for most solar installers. Standardize the survey, yes. But then measure what the survey found, how long it took to move, and whether your company turned that finding into a decision before it turned into lost time.

FAQ

What is a solar site survey for?

A solar site survey checks whether the sold system can actually be installed as designed. It verifies roof conditions, electrical capacity, utility constraints, access, and anything else that could change the layout, price, or permit path.

How long does a solar site survey take?

The field visit itself may take less than an hour or several hours, depending on the property and system complexity. The more important question for operations is how long it takes to turn the findings into a redesign, change order, and permit-ready package.

What should be on a solar site survey form?

At minimum, the form should capture roof condition, service panel details, rapid shutdown and routing issues, utility and interconnection data, equipment locations, and a photo set that makes the finding easy to act on.

Why does a solar site survey matter before installation?

Because the survey is where the proposal meets the real site. If the finding changes the scope and the company does not have a fast path to redesign and repricing, the job slows down or gets cancelled.