Sold-to-Operations Solar Handoff Checklist: What Must Travel With the Job

This is a desk-research guide for installers and EPCs. It does not replace engineering, site verification, local code, utility requirements, manufacturer instructions, commercial judgment, or a project-specific review. Its purpose is to make sold to operations solar handoff decisions explainable before they affect a proposal, purchase, schedule, or handoff.

Start with a release package

The handoff should identify the current design, customer-facing proposal, scope, equipment basis, price or commercial record as appropriate, and current status. Avoid a handoff that consists only of a chat message and attachment.

Transfer site evidence and unknowns

Include photos, measurements, roof or electrical notes, access information, permit status, utility context, and items requiring confirmation. Unknowns are safer when explicitly owned than when omitted from the file.

Translate customer commitments

Installation and operations need to know what the buyer was told about scope, timing, exclusions, options, communications, and conditions. A promise made in a sales call can matter operationally even if it never reached a technical drawing.

Assign open decisions

For each unresolved item, name the decision, evidence needed, owner, deadline, and effect on release. Keep the original decision owner until an explicit transfer of responsibility is recorded; a packet upload does not assign technical authority.

Confirm material and document alignment

Check that the released equipment basis, bill of materials, layout, electrical documents, and proposal describe the same configuration. Mark previous versions as superseded.

Run a live handoff for complex work

A short cross-functional review can surface ambiguities that a document exchange misses. The purpose is to clarify the project, not to create an approval ritual for simple, well-defined work.

Keep the loop open after transfer

New site information should return through a change path that informs sales, design, and the customer when needed. Handoff is a controlled transition, not the end of collaboration.

Record the accepted commercial basis

“Sold” is a business status, not evidence that every prerequisite for delivery has been completed. Link the actual agreement or accepted offer and its scope, conditions and authorized parties. Do not infer permission to build, energize or change scope from a signature alone.

Preserve contradictory sales notes rather than editing them into an apparent agreement. Assign authorized commercial/legal review where terms or customer expectations differ. Operations can accept responsibility for a next task while retaining a separate hold on construction. Only safe, authorized independent work may proceed without bypassing required controls.

NASA’s interface-management guidance supports defining responsibility and changes across team boundaries as a management analogy. Hong Kong EMSD’s PV documentation guidance illustrates retained drawings, manuals and records in its local O&M context; it is not a universal sales handoff requirement.

For other stage transitions use the sales-design-operations-installation checklist. Verify proposal workflow outputs and manual transfer dependencies in the offered configuration rather than assuming native CRM or automatic delivery approval.

Frequently Asked Questions

What is the first sold to operations solar handoff check?

Start by identifying the current project facts, their sources, and the decision they support.

Can a workflow remove all solar project uncertainty?

No. It can make uncertainty visible, owned, and easier to review before it becomes a customer or delivery problem.

When should the record be updated?

Update it whenever a material site fact, configuration, scope, assumption, or customer commitment changes.