Solar Project Handoffs: Sales to Design to Permit to Install

Most solar handoff failures are small at first. A missing site photo. An equipment assumption that never made it into the project record. A customer promise that design never saw. A revised plan set that permitting received but the field team did not.

The delay appears later, often in a different department.

Design has to stop and ask sales a question. Permitting submits the wrong revision. Procurement allocates equipment against an outdated design. The crew reaches the site with a project file that is technically complete but operationally wrong.

For U.S. solar installers, the fix is not simply more communication. It is a controlled handoff: the sending team proves the job is ready to move, the receiving team knows exactly what it is accepting, and incomplete work can be returned before it becomes downstream rework.

What is a solar project handoff?

A solar project handoff is the transfer of responsibility for the next part of the job, not just the transfer of files. The handoff is complete only when the receiving team has the information, approvals, current documents, known exceptions, and ownership needed to begin its work without rebuilding what the previous team already knew.

That distinction matters. Sales can attach a signed contract and still fail the sales-to-design handoff if the sold equipment, customer constraints, open site assumptions, and promised dates are unclear. Design can upload a plan set and still fail the design-to-permit handoff if nobody can identify the approved revision or the AHJ-specific submission requirements.

A good handoff answers four practical questions: What is now true? What evidence proves it? Who owns the next action? What should happen if a required input is missing?

Why do handoffs break inside U.S. solar operations?

Solar projects cross more organizational boundaries than a simple sales workflow suggests. A project can move through sales, site survey, design, engineering, local permitting, utility interconnection, procurement, warehouse allocation, installation, inspection, billing, PTO, closeout, and service. Some of those activities also run in parallel instead of following one universal sequence.

The U.S. Department of Energy includes design, permitting, installation, interconnection, sales and administrative work, supply-chain and inventory control, and operating overhead within solar soft costs. That is a useful reminder that handoff quality is not just a project-management concern. Poor transfers create labor, schedule, material, and administrative consequences.

Local variation adds another layer. DOE notes that permitting and inspection requirements differ across jurisdictions, and administrative errors and backlogs can delay projects. The next team therefore needs more than a generic status such as “design complete” or “permit ready.” It needs the exact project state and the evidence behind it.

The common failure is an implied handoff

An implied handoff happens when one team assumes another team now owns the job because a status changed, an email was sent, or a file was uploaded. Nobody explicitly confirms that the receiving team has accepted responsibility. The job looks like it moved, but the next action has no clear owner.

This is why “sent to design,” “submitted to permitting,” and “ready for install” should be treated as controlled states with acceptance criteria, not casual notes.

Use a handoff gate, not a handoff message

A practical handoff gate has five parts: a trigger, required inputs, acceptance criteria, a named receiver, and a return path. The gate does not need to make the workflow bureaucratic. Its job is to stop incomplete work from silently becoming the next team’s problem.

1. Trigger

Define what event starts the handoff. Examples include contract approved, design released for permitting, permit approval received, or field milestone verified.

2. Required inputs

List the minimum records the receiving team needs. Do not rely on “everything is in the folder.” Name the exact fields, documents, approvals, and exceptions.

3. Acceptance criteria

Define what must be true before the receiver accepts responsibility. This turns “looks complete” into a consistent operating rule.

4. Named receiver

Assign a person or role that owns the next stage. A department name by itself is not enough when a deadline or correction is waiting.

5. Return path

Allow the receiver to reject or bounce an incomplete handoff with a specific reason. A returned handoff is better than discovering the missing input after design, permitting, or installation has already spent time on the job.

What should the sales-to-design handoff include?

The sales-to-design boundary should protect the commercial promise before technical work begins. The designer should not have to reverse-engineer what the customer bought from a proposal PDF, CRM notes, text messages, and a salesperson’s memory.

Lock the sold scope first

The handoff should identify the contracted system scope, equipment assumptions, battery or storage scope where applicable, pricing adders that affect design, electrical or roofing work included in the sale, exclusions, and any customer-approved changes already made after proposal.

The important word is contracted. Design should know which details are promises and which are still assumptions that must be verified.

Carry site and utility facts into the project

The project should include the service address, utility, available consumption or bill data used for the sale, site-survey information already captured, roof and electrical observations, photos, access constraints, known main-panel or service concerns, and customer requirements that can change layout or equipment selection.

If the site survey is still pending, the handoff should say so explicitly. The design stage can then distinguish “ready for preliminary work” from “ready for final design” instead of treating all closed-won projects the same.

Transfer customer commitments, not just technical data

Sales may know about HOA concerns, aesthetic preferences, roof replacement plans, EV or battery plans, access restrictions, promised communication dates, or customer-requested timing. Those details can affect design, permitting, scheduling, and customer experience even when they do not appear on the bill of materials.

A strong sales-to-design acceptance rule is simple: the designer can explain what was sold, what remains unverified, and which constraints must be respected without calling the sales rep for basic project reconstruction.

What should the design-to-permit handoff include?

The design-to-permit handoff should answer one central question: which exact design is the company asking the AHJ to approve?

That sounds obvious, but design revisions create one of the easiest ways for a project to split into multiple versions. A designer can update equipment or layout while permitting still has the previous plan set. Procurement can begin from a newer equipment assumption. Sales may communicate a change to the customer before the project record is updated.

Identify the approved revision

The permit team should receive a clearly identified current design revision, equipment schedule, engineering or stamped documents where required, electrical information, site details, and any supporting documents the jurisdiction requires for the applicable project.

Do not assume one checklist works for every U.S. jurisdiction. DOE notes that local permitting and inspection requirements vary. The handoff system therefore needs a standard core plus AHJ-specific requirements.

Make changes visible before submission

If the final design differs from the sold scope or an earlier customer-approved version, the handoff should identify the change, approval status, customer impact, material impact, and any commercial decision that remains open. Permitting should not become the department that discovers an unapproved scope change.

Use completeness as a gate

The 2026 SolarAPP+ performance review provides a useful U.S. example of the value of structured inputs and review logic. In 2024, 861 installers submitted 37,393 permits through SolarAPP+, and the report found a typical participating project was permitted and inspected 12 business days sooner than projects using traditional processes.

Those are SolarAPP+ results, not Solar1 results, and they do not mean every permit process can be automated. The operating lesson is narrower: complete, structured information is easier to review than a project package that depends on someone noticing what is missing.

What should the permit-to-install handoff include?

Permit approval should not automatically mean “schedule the crew.” The permit-to-install handoff is really an install-readiness gate. It confirms that the approved project can be built using the documents, materials, site conditions, and dependencies the field team will actually encounter.

Start with the approved documents

The field team should receive the current approved plan set or issued-for-construction package used by the company, permit approval and relevant conditions, equipment specification, known inspection requirements, and clear notes about any project-specific constraint that changes how the installation should proceed.

If the AHJ approval is conditional or a correction is still unresolved, the project should not quietly appear install-ready because the calendar already contains a date.

Confirm material readiness against the approved design

Warehouse quantity is not enough. The required equipment must match the approved design, be available or allocated to the project, and have any substitution properly approved. A material substitution can create a new design, permit, utility, cost, or customer dependency.

Confirm the site is ready, not just the crew

Install readiness can also depend on customer access, roof work, electrical preparation, required subcontractor work, site conditions, utility or interconnection prerequisites where applicable, and the availability of the correct crew or equipment.

The field lead should be able to answer: What are we building? Which revision are we building from? What materials are assigned? What site exceptions are known? What evidence must we capture before the job can move to inspection, billing, or the next stage?

Why include the install-to-finance handoff?

The article title ends at install because that is where the physical delivery becomes visible. Operationally, the handoff chain does not stop there. Installation creates evidence that inspection, interconnection, finance, customer communication, closeout, and later service may depend on.

A crew message saying “done” is not a complete handoff. The project needs the actual work completed, photos or other required evidence, labor and material usage, installed equipment records where tracked, unresolved punch items, failed or partial work, and the condition required for the next billing or inspection action.

Separate complete from invoice-ready

An operational milestone and a billing milestone are related but not always identical. Finance should know what evidence or approval makes the project invoice-ready under the company’s contract rather than relying on a project manager to send a message days later.

The same field evidence can also support inspection preparation, change-order review, project costing, customer updates, and closeout. Capturing it once at the handoff prevents each downstream team from asking the field crew to reconstruct the job.

What does one small handoff miss cost?

The content plan for this article uses a deliberately simple example: one missing site photo can trigger a design question, a second site check, a revised drawing, a permit resubmission, a delayed install, and extra customer communication.

That chain is illustrative, not an industry benchmark. The point is that the cost of the original missing input is rarely equal to the cost of collecting that input. The expensive part is the number of downstream decisions that were made before the missing information became visible.

This is why handoff quality should be measured at the boundary, not only through final project delay. If a design package is repeatedly bounced back because basic sales or survey information is missing, the company can fix the upstream process before those defects become permit or install problems.

How should a solar installer measure handoff quality?

Do not start with a generic project-duration benchmark. Start with whether the receiving team accepts the handoff cleanly.

First-pass handoff acceptance rate

Track the percentage of handoffs accepted by the receiving team without being returned for missing required information. This is an internal quality metric, not a published industry standard.

Bounce reasons

Categorize why handoffs are returned: missing site data, unclear sold scope, missing customer approval, revision mismatch, AHJ requirement missing, material mismatch, incomplete field evidence, or another recurring cause. Repeated bounce reasons reveal which upstream control needs work.

Time waiting between teams

Measure how long a completed stage waits before the next owner accepts it. Separate waiting caused by an external organization from waiting caused by an internal transfer. They need different management responses.

Downstream rework linked to upstream handoffs

When a redesign, resubmission, reschedule, repeat visit, or billing delay occurs, record whether an earlier handoff defect contributed. The objective is not to blame the sending team. It is to find the control that would have prevented the same miss.

How do you handle changes after a handoff is accepted?

A handoff does not freeze the project forever. Customers change scope, site conditions appear, AHJs issue corrections, utilities request updates, equipment availability changes, and field conditions can require a new decision.

The control is to reopen the affected gate when a change invalidates something the next team already accepted. A changed inverter may reopen design review and material approval. An AHJ correction may reopen the design-to-permit boundary. A field discovery may create a new design, permit, customer, or change-order decision.

Do not hide this by simply replacing the old file. Preserve the reason for the change, current revision, approvals, affected downstream records, new owner, and new acceptance condition.

How is Solar1 being designed around handoff ownership?

Solar1 is being built as a complete solar-specific ERP for installers and EPC companies. Handoffs are one part of that broader operating model, connecting CRM and sold scope with surveys, design workflow, engineering, permitting, interconnection, procurement, inventory, field operations, finance, PTO, service, and management reporting.

The product direction is to make ownership changes explicit. When sales finishes its part, the project should carry the sold scope and open assumptions forward. When design is approved, the current revision should be the one downstream workflows use. When permitting changes the project, the affected teams should see the consequence. When field work is verified, inspection and finance should not need a separate reconstruction.

Solar1 is still under development, so this describes the operating model the product is being designed around. It does not mean every capability described in this guide is currently production-ready.

Build the gate before adding another reminder

Take one recently delayed project and walk backward through its boundaries. What did sales hand to design? What did design hand to permitting? What did the permit team hand to scheduling and field? What did the crew hand back to inspection and finance?

For every boundary, write the trigger, required inputs, acceptance criteria, receiver, and return reason. Then compare those rules with what actually happened on the project.

Download the Solar Handoff Checklist and use it on one live U.S. project before changing software or adding another status meeting. A good handoff should make the next team faster because it receives a decision-ready project, not another folder to investigate.