Solar Scope of Work Template: Deliverables and Responsibilities

A solar scope of work should let the customer, designer and delivery team identify the same promised work. If a proposal shows one array and the equipment schedule describes another, the template has not resolved the mismatch. Establish the accepted design reference before issuing the scope.

Use the framework below to prepare a project-specific scope exhibit. It is an editorial planning template, not a jurisdiction-ready contract. Applicable consumer protections, licensing, payment restrictions, contract terms and professional responsibilities still need appropriate review. Start with the solar contract template guide for the broader agreement, and keep the scope’s references consistent with it.

What belongs in the SOW rather than the proposal?

The proposal explains the offered system and its assumptions. The SOW records included deliverables, boundaries, responsibilities and completion conditions. The full agreement addresses legal and commercial terms. None should silently contradict the others.

For an explicitly hypothetical mismatch, the signed equipment schedule lists 28 modules while a later working design lists 30. That difference does not authorize procurement or installation. Identify the governing revision, investigate the change and obtain the required project-specific disposition. Preserve both records and their history.

The U.S. federal FAR 8.405-2 identifies work description, location, performance period, delivery schedule, standards and special requirements for statements of work in its ordering context. It is not a rule for every private solar contract. Those categories nevertheless offer a useful completeness check.

Ten sections to adapt to your solar project

These are suggested review categories, not a universal legal format or prescribed order. Add project-specific annexes and remove inapplicable entries only after checking dependencies.

1. Project overview and governing references

Record the customer, contracting parties, site and authorized work areas. Identify the design, layout, equipment schedule and proposal by document ID, revision and issue date. Distinguish module capacity in kW DC, inverter capacity in kW AC and modeled energy in kWh; capacity is not annual production.

Label modeled production as an estimate with its assumptions and output boundary. Record target dates, dependencies and the person authorized to reconcile conflicting documents. Do not let “latest drawing” substitute for an exact reference.

2. Design deliverables and review responsibilities

List the survey, shading assessment, structural information, electrical drawings, stringing information and permit documents actually included. For each, define format, recipient, preparer, reviewer and required release state. A preliminary customer rendering is different from an issued construction drawing.

A shading analysis can support an energy estimate, but its presence does not create a production guarantee or structural approval. Record which inputs are verified and which require further investigation.

3. Equipment specifications and substitutions

Identify applicable manufacturer/model references, quantities, ratings and supporting documents. List batteries, mounting assemblies and balance-of-system items where included. The DOE system-design overview describes mounting, inverters and storage alongside PV modules; the scope should reflect the actual complete system.

Define the route for a proposed substitute. Matching wattage or warranty length alone does not establish electrical compatibility, mounting suitability, certification, installation compliance or agreed customer acceptance. Obtain technical and commercial dispositions before updating the accepted schedule.

4. Physical installation boundaries

Reference array locations, mounting design, cable routes, trenching, access, protection of existing property and cleanup responsibilities. Record customer-facing appearance decisions without using them to override technical requirements. If an exterior conduit finish is offered, specify that agreed finish rather than assuming the customer expects hidden wiring.

Separate installation work from remedial roof, structural or hazardous-material work. Do not promise that a sales visit has established roof fitness.

5. Electrical work and connection responsibilities

Reference the qualified design’s connection arrangement and the applicable service equipment work. Identify any included upgrade, shutdown coordination, testing and responsible electrical reviewer. An excluded service upgrade still needs a route for resolving a project that cannot proceed without it.

Do not select a connection method through a generic template. Local rules, utility requirements and the actual equipment configuration govern technical review.

6. Permits, utility processes and other applications

Name the actual permitting authority, utility and application responsibilities. Separate preparing/submitting documents, obtaining a permit, passing inspection, completing utility processes and receiving permission to operate. Assign fees, responses to comments and required customer information through the reviewed agreement.

An application submitted is not an approval received. A contractor cannot promise an external authority’s decision simply by putting a date in the scope.

7. Included, excluded and unresolved interfaces

Use explicit labels: included; excluded with another responsible party; separately priced allowance; or unresolved and blocking. Explain what happens if an unresolved item becomes necessary. Avoid an exclusion that hides a prerequisite for safe, lawful completion.

8. Change requests and authorization

Identify who may request, assess and authorize a change, what evidence is required, and how cost, schedule, technical and customer effects are recorded. State the contract-specific notice and decision requirements rather than inventing a standard response deadline.

9. Payment events and conditions

Use the agreed, lawfully reviewed payment structure. Define the event, evidence, amount, invoicing condition, due date and any retention or financing dependency. Do not insert industry-wide deposit percentages or assume installed cost must equal customer cash already collected.

10. Completion, acceptance and closeout

Define each completion state separately: physical work, testing, inspection, external authorization, customer handover and unresolved punch-list items. State required records and the acceptance role for each. Customer acknowledgment does not replace an inspection, technical review or utility permission.

Review these ten potential scope gaps

The original template’s exclusions list is useful as a review prompt, not a list to exclude automatically:

• main panel or service changes;
• roof repair, re-roofing or decking replacement;
• tree work;
• structural reinforcement;
• utility transformer, meter or service works;
• asbestos or other hazardous-material handling;
• interior finishes disturbed by installation;
• landscaping, irrigation or fence restoration;
• monitoring subscriptions and ongoing support;
• snow removal or other maintenance services.

For each applicable item, name the included work or the other responsible party, evidence needed, pricing basis if agreed and effect on readiness. A unit price may suit a defined task; a complex upgrade may require a separately reviewed quote. Do not invent a decking price or price a service upgrade solely by amperage.

Discuss these interfaces while site information can still be checked, then reconcile the written scope before signing and delivery handoff. A conversation does not replace the governing record.

Six change triggers to route through review

These are candidates, not measured rankings of the most frequent changes. A trigger opens a review; it does not automatically establish entitlement to extra payment or extra days. Preserve the notice, scope comparison, pricing basis, schedule assessment and decision. The change-order management guide covers the operating register; solar change orders covers pricing and contractual questions.

Do not instruct crews to accept informal changes as a substitute for required authorization. Equally, a commercial hold is not a reason to ignore immediate safety duties or actual authorized emergency instructions. Route those situations to the responsible people and record what occurred.

Make payment milestones observable

Use a blank milestone schedule rather than preset percentages:

Examples of events to consider include an authorized start, accepted design deliverable, specified equipment delivery, defined installation stage and accepted closeout. Their use and payment terms depend on the actual agreement and applicable law. Placing a purchase order is different from receiving equipment; substantial completion is different from permission to operate.

Forecast supplier payments and expected collections separately in the installer cash-flow guide. Accounts receivable are billed amounts outstanding, not cash received, and cash collection is not proof of completed or accepted work. Do not change an agreed final-payment condition merely to improve a cash forecast.

Residential and commercial differences to check

Both projects may need qualified structural/electrical review, permits and documented testing. Neither is exempt because of a customer type. Commercial sites may introduce more interfaces, but required depth follows the actual work, jurisdiction and agreement.

Do not infer fixed document lengths, workmanship warranty durations, project schedules or financial “bankability” from system size. External professional reviews remain separate from software outputs.

Copy-ready scope worksheet

Use one row per deliverable or interface; repeat the table for each work package.

Three controls keep the worksheet reusable. First, reference accepted design data and reconcile the fields rather than assume copying prevents drift. Second, version the master template and project-specific changes without overwriting signed history. Third, review before issue and again at the delivery handoff, checking which prerequisites and external approvals remain open.

Evaluate SurgePV design outputs and solar proposal workflows for the document preparation tasks you need. Confirm actual configuration and exports in a demo. These outputs do not draft jurisdiction-ready legal terms or prove that every signed scope field matches the installed project.

Frequently Asked Questions

What is a scope of work in a solar contract?

A solar scope of work records the project-specific deliverables, work boundaries, responsibilities and completion conditions. It should identify the governing design and equipment references and explain included, excluded and unresolved work. Reconcile it with the full agreement; the template alone does not establish legal enforceability or external approval.

What should a solar SOW exclude?

Do not automatically exclude a standard list. Review roof and service changes, structural work, utility works, hazardous materials, restoration, monitoring and maintenance. Label each applicable interface as included, excluded with another responsible party, separately priced or unresolved. Identify prerequisites and a reviewed change route rather than inventing default unit prices.

How many payment milestones should a solar project have?

There is no universal number or percentage schedule. Choose lawful, agreed milestones with defined events, evidence, amounts, invoice conditions, due dates and any retention or financing dependencies. Distinguish equipment ordered from delivered, installation completion from inspection and utility permission, and outstanding invoices from cash received.

What triggers a change order in solar projects?

Possible triggers include new roof or structural findings, authority or utility comments, customer changes and access restrictions. Each requires an impact assessment against the accepted scope. A trigger does not automatically authorize extra payment or delay: apply the actual notice, pricing, review and authorization requirements.

How is a C&I scope of work different from a residential one?

Commercial projects may add tenant coordination, shutdowns, crane access, monitoring interfaces or formal owner acceptance. Required scope depends on the site, work, jurisdiction and agreement. Residential projects may also require qualified engineering, inspections and testing; neither project type has a universal document length or warranty duration.

Is a scope of work legally binding?

A scope exhibit may form part of a binding agreement, but its legal effect depends on incorporation, the complete contract, applicable law and the facts. Do not infer enforceability from using this template. Obtain appropriate jurisdiction-specific review when drafting or changing commercial and legal terms.