9 Solar Site Visit Tasks Beyond Measurements

Consider an illustrative visit: the rep returns with roof dimensions, photographs, and a note that says “panel.” The designer still cannot tell which building the customer meant, whether the utility record matches it, why one roof face was excluded, who must approve the next meeting, or what the homeowner expects next.

The gap starts in the visit record and can carry into design. A solar site visit brings the customer, property, available records, visible conditions, and next decision together. Measurements matter, but they do not establish the customer’s objectives, authority, source identity, or expectations.

This article is not safety, workplace, access, privacy, structural, electrical, engineering, permitting, utility, insurance, contract, tax, financing, or legal advice. A qualified owner must define who may enter, observe, photograph, measure, touch, open, diagnose, or approve anything at a real property. Stop when access, training, authorization, conditions, or professional scope do not support the planned work.

The solar site survey checklist owns detailed field observations. The guide to reducing repeat site visits owns evidence completeness and return causes. Use this page for the sales job around that field work: align the people, records, constraints, decisions, and handoff before the rep leaves.

What should be decided before a solar site visit begins?

Before a solar site visit begins, decide what the visit must accomplish, who authorized it, who may participate, which areas and records are in scope, which safety and privacy controls apply, and what evidence the next owner will accept. A calendar event is not a work plan. The visit needs a decision boundary, stop conditions, and a receiver.

The first task is to confirm purpose, access, permission, and decision boundary. “Visit the property” is not a purpose. A residential visit might support a preliminary sales conversation, an approved field survey, a record-reconciliation step, or preparation for a qualified technical review. Those purposes can require different people, tools, access, evidence, and customer expectations.

Write the intended release before the visit. Is the next output an information request, a preliminary layout, a design request, a proposal revision, a specialist referral, or a no-go decision? Name what the visit cannot establish. This prevents the rep from turning an observation into a promise because the customer asked a reasonable question in the driveway.

NASA’s technical-planning guidance describes defining the work to be performed, its products, resources, schedules, and technical activities in NASA programs. It does not govern a solar site visit. The useful process analogy is narrow: plan the work from the output and acceptance need, not from a generic activity label.

Use a pre-visit control table:

The Occupational Safety and Health Administration’s recommended safety-management practices describe a proactive approach to identifying and controlling hazards through a workplace safety and health program. It does not authorize a person to access a roof or electrical equipment. The company needs its own competent safety process for the actual work and jurisdiction.

Do not let a sales target weaken a stop rule. If the approved visit does not include roof access, the rep does not improvise roof access. If electrical equipment may only be handled by a qualified person, the rep does not open it for a better photograph. A complete visit can legitimately end with “access unavailable” or “qualified review required.”

Confirm the customer’s understanding before collecting more data

Tell the customer why each activity is planned, what information may be recorded, who receives it, and what the likely next step is. Use the company’s approved language. If the customer changes the scope, asks to exclude an area, withdraws a permission, or introduces a new stakeholder, record the event and route it under the approved process.

The customer may reasonably believe a site visit means the roof has passed, the price is final, construction is scheduled, or approval is likely. Correct that expectation without retreating into vague disclaimers. Say which output is being prepared, which decisions remain open, and who owns them.

Which records and site conditions should the rep reconcile?

Reconcile the customer, property, utility, project, and source records against what is available at the visit. Then document accessible constraints and obstructions beyond geometry. Every item needs a provenance state such as customer-stated, source-recorded, observed, measured, modeled, conflicting, unavailable, or awaiting qualified review. Never merge those states into a single “verified” label.

The second task is to verify the customer, property, source records, and current versions. An address can identify a parcel without identifying the intended structure, meter, account, tenant space, or decision-maker. Ask the customer to confirm the project boundary in ordinary language, then compare that answer with the authorized records. Do not ask the customer to settle title, utility, ownership, or legal questions outside their knowledge.

The third task is to capture constraints and obstructions beyond geometry. The sales rep may notice visible roof features, vegetation, neighboring objects, work areas, access constraints, planned renovations, tenant operations, sensitive spaces, or equipment locations. Record only what the approved process allows. The observation should name where it was made, from what viewpoint, when, by whom, and what remains hidden.

The fourth task is to record electrical and route observations without implying approval. A rep can document the location and visible identification of an accessible item if trained and authorized. That is not a conclusion about condition, capacity, code compliance, suitability, interconnection, routing, or scope. Electrical and structural decisions must go to qualified reviewers under the applicable process.

Use evidence states consistently:

The Department of Energy’s homeowner solar guide organizes a homeowner’s solar process around energy efficiency, solar potential, options, needs, bids, financing, and work with an installer. It does not approve a specific project. For a sales rep, the practical point is to keep the customer’s decision context connected to the property and proposal inputs rather than collecting roof information in isolation.

Photographs need identities. “IMG_1842” is not an evidence description. Associate each approved image with the project, date, observer, location, direction, subject, purpose, permission state, and related question. Preserve the original under the company’s retention and access rules. Add corrections rather than silently replacing history.

The site-visit mistake guide offers diagnostics for unlabeled media and uncertainty in the customer conversation. The point is not to collect more photographs. It is to create fewer ambiguous records.

Reconcile energy and project inputs without pretending they are complete

The sixth task is to reconcile usage records and missing inputs. Confirm which service, period, account, tariff record, interval file, bill page, or customer-supplied document is being discussed. Record the source and date. Do not infer that one bill covers every structure or that a copied annual total is current, complete, or suitable for a particular model. Distinguish consumption in kWh from power or billed demand in kW, and identify whether interval values are energy per interval or average power. Preserve dates, interval duration, time zone, import/export meaning, and missing periods for the receiving analyst. A billed demand peak is not an energy total, and a meter record does not by itself establish total facility consumption when behind-the-meter generation or storage is present.

If the customer does not have the requested record, assign a next action. The customer might retrieve it through an approved channel, the utility account owner might provide it, or the project might proceed only to a bounded preliminary output. “Missing” is a real state. It should not become a number the rep estimates on the spot.

What customer and stakeholder questions should the visit resolve?

Use the visit to clarify the homeowner’s objectives, timing, priorities, stakeholders, and decision authority. Ask what decision comes next, what constraints could change it, who must review the answer, and which evidence they need. Do not turn rapport into technical approval or pressure. A useful conversation narrows the next decision and exposes unresolved ownership.

The fifth task is to clarify customer objectives, timing, and project priorities. “Save money” or “go solar” is too broad for a handoff. Ask what the customer is trying to compare or decide. They may care about a roof renovation, equipment location, appearance, budget boundary, ownership plan, electrical work, operating continuity, timeline, future load, or how household members will review a proposal.

Separate a preference from a requirement. “I would prefer not to see panels from the street” is a preference worth preserving. “Panels are prohibited there” is a different claim and needs its own authority and evidence. “I hope to install before an event” is a desired timeline, not a schedule commitment.

The seventh task is to identify stakeholders, approvals, and decision authority. Ask who owns or occupies the property, who controls the relevant account, who will compare proposals, who can authorize records and access, and which outside parties may need to act. Record the answer as customer-stated until the responsible process verifies what must be verified.

Stakeholder discovery is not an invitation to collect unnecessary personal information. Use approved fields, explain their purpose, and follow the company’s privacy, access, retention, correction, and deletion procedures. A spouse, co-owner, tenant, landlord, facilities contact, finance contact, insurer, lender, utility, permitting authority, engineering reviewer, or contractor may affect the workflow, but the rep should not declare their rights or approval requirements from memory.

The Department of Energy’s rooftop solar permitting and inspection page explains that local solar permitting and inspection processes are used to address applicable safety and code requirements. It does not establish the path for every jurisdiction or approve a project. Record the project’s actual authority path as unresolved until current local evidence and qualified owners establish it.

Ask decision-shaped questions:

1. What do you want to be able to decide after the next deliverable? This defines the job of the proposal or follow-up.
2. Which building, service, account, and customer situation are included? This tests whether the project record names the same thing the customer means.
3. What changed since the first conversation? New roof work, loads, equipment, occupants, ownership plans, or timing can invalidate earlier assumptions.
4. Which outcome matters, and what would make the option unacceptable? This exposes tradeoffs without promising results.
5. Who else needs to understand or approve the next step? This prevents a proposal from arriving without its real audience.
6. Which records can you provide through an approved method? This turns missing information into an owned request.
7. What should happen if the site evidence conflicts with the preliminary discussion? This prepares the customer for a transparent revision rather than a surprise.
8. What contact method and timing should the team use under the approved process? This protects the customer’s preferred next interaction.
9. What is the smallest useful commitment after today? This can be a record request, review meeting, specialist visit, revised concept, or decision to pause.

Do not ask all nine mechanically. Select the questions that serve the declared visit purpose, and record the answer in the project system with its source and date. A conversation is not complete because every CRM field contains text.

How do you close open questions and hand the visit to the next owner?

Close the visit by reviewing open questions, assigning each one to an owner and evidence requirement, and agreeing on the next handoff. The receiving role should accept, conditionally accept, return, or reroute the package against written criteria. Departure is not acceptance. A photo folder, signed note, or completed appointment status cannot substitute for receiver confirmation.

The eighth task is to close open questions with owners and evidence requirements. Read back the important customer-stated facts, preferences, changes, and missing records. Let the customer correct the conversation. Do not ask them to certify facts they cannot know or sign away uncertainty.

Create an open-question register before leaving:

The ninth task is to agree on the next handoff and receiver acceptance criteria. Name the sender, receiver, package, due event, acceptance test, possible return reason, and customer communication owner. A due event can be “after the current bill is received” or “after the qualified reviewer accepts the field record.” Avoid dates the evidence and responsible owner cannot support.

NASA’s technical risk-management guidance describes identifying, analyzing, planning, tracking, controlling, and communicating technical risk in NASA programs. It does not define solar project risk. The transferable discipline is to keep an unresolved condition visible with an owner and response instead of allowing it to disappear between teams.

The post-visit deal-risk checklist covers the commercial review after the appointment. The solar sales-to-design handoff guide covers the receiving workflow. Use them as separate controls: one asks what changed in the deal, and the other asks whether design received a usable request.

Use a departure review, not a memory test

The field person and receiver should review the package while clarification is still possible. The receiver does not need to approve technical suitability at departure. They need to determine whether each required record is present, identified, readable, internally consistent, and within the visit’s purpose.

Define these dispositions in a manual record or a demonstrated configured workflow; this checklist does not imply that every software platform provides or enforces them. Allowed dispositions should be explicit: accepted for the declared next output, conditionally accepted with named gaps, returned for a bounded correction, rerouted to a qualified owner, or stopped. “Complete” should never be the only button.

What copy-ready record makes the nine site-visit tasks usable?

Use one site-visit decision record that links the visit purpose, permission, property identity, source states, visible constraints, customer objectives, stakeholder roles, open questions, and receiver disposition. The record should show what was observed and what remains unresolved. Copy it into the approved system, adapt it to local requirements, and preserve its revision history.

Copy-ready solar site-visit decision record

Illustrative workflow, not a real property, customer, installer, survey, finding, design, promise, or result. A rep visits a home for an approved ground-level sales and record-reconciliation appointment. The calendar description says “site survey,” but the work order does not authorize roof access or opening electrical equipment.

The rep confirms the intended building, learns that the customer expects to replace part of the roof, and discovers that the usage document on file belongs to a service the customer does not recognize. The rep records those statements with their source, photographs only approved accessible subjects, and does not diagnose the roof or equipment.

Before departure, the rep reads back the project boundary and next step. The design receiver conditionally accepts the customer and property record, returns the usage question to the account owner, and routes roof and electrical questions to qualified reviewers. The sales owner tells the customer that a proposal release is not yet scheduled because required inputs remain open.

Nothing in this example proves that the project is suitable, that another visit is unnecessary, or that the process improves conversion. It shows how the nine tasks keep unsupported conclusions out of the customer conversation while still moving the record toward a defined decision.

SurgePV’s design and proposal workflows includes 3D roof modeling, solar array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. Outputs depend on source data, assumptions, equipment models, configuration, and review.

Evaluate the current configured workflow with an isolated, sanitized project: check how accepted inputs, unresolved questions, output identities, and a changed source record are represented. Agree which relationships software supports and which require the team’s manual controls. It does not authorize property access, inspect a roof, validate permission, determine structural or electrical suitability, approve a permit, establish utility requirements, give legal or financial advice, or replace the responsible professional and authority review.

Complete the visit record with observations, customer objectives, unresolved questions, named owners, and the receiver’s disposition. The receiving team should be able to distinguish usable inputs from questions that still need evidence or qualified review.

Frequently Asked Questions

What should a solar sales rep accomplish during a site visit?

The rep should complete the visit’s approved sales and evidence objectives: confirm identity and scope, understand the customer’s decision, document accessible conditions and constraints, reconcile available records, identify stakeholders, record unresolved questions, and secure an owned next step. Technical, safety, structural, electrical, permitting, and contract conclusions remain with qualified owners.

Should a solar sales rep inspect the roof or electrical service?

Only within the company’s approved role, access, training, safety, and jurisdictional rules. A sales rep can record permitted observations and identify questions, but should not enter restricted areas, open equipment, diagnose conditions, or imply professional approval. Qualified field, electrical, structural, engineering, safety, and authority reviewers decide what inspection is required.

What homeowner questions belong in a solar site visit?

Ask what decision the homeowner wants to make, which property and account are in scope, what changed since prior conversations, what outcomes and constraints matter, which records are available, who else participates, and what next step is acceptable. Avoid questions that pressure a commitment or invite unsupported technical, financial, legal, or approval promises.

How should site visit photos and notes be organized?

Tie each approved photo or note to the project, visit date, observer, location, direction, subject, purpose, source state, and related question. Distinguish customer-stated, observed, measured, copied, modeled, and unresolved information. Follow approved permission, privacy, retention, access, and security rules, and preserve the original record when corrections are added.

When is a solar site visit complete?

A solar site visit is complete for its declared purpose when required evidence states are recorded, access limits and conflicts are visible, customer and stakeholder questions have dispositions, and the receiving owner accepts the handoff or returns a specific exception. Departure does not prove roof suitability, electrical adequacy, permit approval, savings, production, or project acceptance.