Solar Scope of Work Template: What Every SOW Must Include

A homeowner in Phoenix signs for a 9 kW rooftop system. On day 2 of the install, the crew finds rotten decking under the old shingles. The customer says fixing it is “part of the job.” The installer says it is not in the contract. Nobody checked the scope of work, because the scope of work was 3 sentences long. That single argument now costs more than the margin on the whole project.

Large construction projects typically run 80% over budget and 20 months behind schedule, according to McKinsey & Company (2016). Solar is not exempt. Soft costs — the paperwork, change management, and dispute time around the physical install — still account for roughly 65% of US residential system prices, according to NREL (2024). A disciplined scope of work is the cheapest tool that attacks that number.

This guide gives you a complete solar scope of work framework for residential and C&I contracts: the 10 sections every SOW needs, the exclusions list that prevents most disputes, the change-order triggers to price upfront, and payment milestones that protect cash flow. It assumes you already have a contract wrapper — if not, start with our solar contract template and treat this post as the deep dive on its scope clause.

In this guide:

• What a solar SOW is, and what it is not
• The 10 sections every solar SOW must include
• The exclusions list that protects your margin
• Change-order triggers to define before signing
• Payment milestone structures for residential and C&I
• How C&I scopes differ from residential scopes
• Why detailed SOWs close more deals, not fewer

What a Solar Scope of Work Is (and Is Not)

A scope of work (SOW) is the part of a solar contract that answers one question: what exactly will the customer receive, and what exactly will they pay for? It converts a sales conversation into an enforceable delivery list. Everything the crew does, every piece of equipment installed, and every permit filed traces back to this document.

The SOW is not the proposal. A proposal sells the outcome — savings, payback, aesthetics. The SOW defines the inputs. It is also not the full contract. The contract carries legal terms like warranties, indemnity, and dispute resolution. The SOW sits inside the contract as its operational core, usually as an exhibit.

A useful mental model: the proposal wins the deal, the contract allocates legal risk, and the SOW prevents the arguments. When a dispute reaches arbitration, the SOW is the first document both sides read. Vague language like “install solar system as discussed” resolves against whoever drafted it, in nearly every jurisdiction we have operated in across 50+ countries.

The SOW also drives your internal operations. Design teams size from it. Procurement orders from it. Crew leads schedule from it. If your SOW says “28 modules” and your design file says 30, one of them is wrong, and the customer signed only one. That is why the strongest EPCs generate the SOW directly from the same solar design software file that produces the layout and bill of materials.

The 10 Sections Every Solar SOW Must Include

A complete solar SOW has 10 sections, in this order: project overview, design deliverables, equipment specification, installation scope, electrical scope, permits and interconnection, exclusions, change-order rules, payment milestones, and acceptance criteria. Skip any one of them and you have left a door open.

1. Project overview

One short paragraph: customer name, site address, system size in kW DC and kW AC, expected annual production in kWh, and target dates. Include the design file reference and version. If the layout changes later, the version number is how you prove which design was current at signing.

2. Design deliverables

List every document you will produce: site survey report, shading analysis, structural assessment, single-line diagram, string sizing, and permit plan set. State the format and the approval workflow. A physics-based shading report from a solar shadow analysis software is worth naming explicitly, because it becomes the production baseline if output is ever disputed.

3. Equipment specification

Name the exact module, inverter, and racking models, with quantities and wattages. Add an “or equivalent” clause with a definition of equivalent: same or better efficiency, same warranty tier, and customer approval in writing. Supply-chain substitutions are the single most common silent contract breach in residential solar.

4. Installation scope

Describe the physical work: array location by roof plane, attachment method, conduit runs (interior or exterior), trenching if any, and cleanup standard. “Exterior EMT conduit, painted to match” prevents the ugliest argument in residential solar: the customer who expected hidden wiring.

5. Electrical scope

Define the interconnection method — load-side breaker, supply-side tap, or line-side connection — plus any panel work included. This is where the main panel upgrade (MPU) question lives. If the MPU is excluded, say so here and again in exclusions. Redundancy on this point is deliberate.

6. Permits and interconnection

State who files what: building permit, electrical permit, utility interconnection application, and incentive registrations. Name the authority having jurisdiction (AHJ) and the utility. Assign responsibility for re-inspection fees if the first inspection fails because of site conditions outside your control.

7. Exclusions

The most important section in the document. Covered in full in the next section.

8. Change-order rules

The pricing method, approval process, and schedule impact for any deviation. Covered in detail below.

9. Payment milestones

Amounts, trigger events, and payment terms. Also covered below.

10. Acceptance criteria

Define “done”: passed inspection, utility permission to operate (PTO) applied for or received, monitoring live, and a walkthrough sign-off. State whether final payment is due at substantial completion or at PTO — utilities control PTO timing, and your cash flow should not.

Exclusions: Where EPCs Win or Lose Margin

An exclusions list is a written statement of work you will not do. It is the most valuable page in any solar SOW, because most disputes are not about what was promised — they are about what the customer assumed. Poor data and miscommunication cost the US construction industry an estimated $1.8 trillion in 2020, according to Autodesk and FMI (2021). Assumption gaps are the solar version of that problem.

Our field-tested exclusions list for residential work:

• Main panel or service upgrade (price per amp of service if triggered)
• Roof repair, re-roofing, or decking replacement (price per sheet of decking)
• Tree trimming or removal
• Structural reinforcement of rafters or trusses
• Utility transformer, meter, or service-drop upgrades
• Asbestos or hazardous-material abatement
• Interior wall, ceiling, or drywall repair after conduit runs
• Landscaping, irrigation, or fence restoration
• Monitoring subscription fees beyond year 1
• Snow removal from the array (maintenance, not installation)

Each exclusion needs 2 parts: the statement, and the unit price if triggered. “Decking replacement excluded — billed at $95 per 4×8 sheet if required” kills the negotiation before it starts. The customer signs knowing the number. Your crew lead calls the office, not the customer’s lawyer.

Change-Order Triggers You Must Define Upfront

A change order is a written amendment to the SOW that adjusts price, scope, or schedule. The triggers that cause them are predictable — we see the same 6 across residential and C&I work:

1. Hidden roof damage found after module removal or during attachment.
2. AHJ-required electrical upgrades, usually a main panel upgrade or grounding change.
3. Customer-requested layout changes after design approval — moving the array, adding modules, swapping equipment.
4. Utility-required changes to interconnection method or equipment after the application is filed.
5. Site-access failures: locked gates, unlisted tenants, vehicles blocking the roof zone.
6. Structural findings that demand engineering reinforcement before attachment.

For each trigger, the SOW should state 3 things: the pricing method (unit price, cost-plus percentage, or fixed schedule of rates), the approval deadline (we use 48 hours, written), and the schedule impact (days added per trigger type). If you manage this process across many projects, our guide to solar change order management covers the workflow and documentation side in depth.

One discipline matters more than the others: no verbal change orders. Crews that “just take care of it” donate margin and destroy the paper trail. Front-end planning discipline of exactly this kind is why projects with defined scope processes outperform on cost and schedule, a finding the Construction Industry Institute (2016) has documented across capital projects for decades.

Payment Milestones That Protect Cash Flow

Payment milestones tie cash to verifiable events, not to calendar dates or goodwill. The rule is simple: never let receivables exceed completed work. If you have installed $40,000 of labor and equipment, you should hold at least $40,000 of customer payments.

Typical residential structure (3–4 milestones):

Typical C&I structure (5–8 milestones):

Two traps to avoid. First, weighting payments to completion — the classic “20% deposit, 80% at PTO” residential deal — turns the installer into the customer’s bank for 60–90 days. Second, making the final payment contingent on events you do not control, like utility PTO or incentive disbursement. The median US residential install-to-PTO timeline still runs several months, a delay tracked in Lawrence Berkeley National Laboratory’s Tracking the Sun (2024). Bill at substantial completion instead, and hold back only a small PTO retainer.

Residential vs C&I: How the SOW Changes

The 10 sections stay the same. The depth, annexes, and risk allocation change completely. Residential SOWs run 4–8 pages. C&I SOWs routinely run 20–50 pages with annexes, because more parties touch the work and more money sits behind every assumption.

Three C&I-only items deserve emphasis. First, shutdown and crane windows: a carport or rooftop install on an operating facility needs written site-access hours, and missing a window can cost a week. Second, monitoring and SCADA integration: commercial owners expect fleet-level data feeds, and the protocol (Modbus, SunSpec) belongs in the SOW. Third, liquidated damages: if the owner wants delay damages, cap them as a percentage of contract value and balance them with an early-completion incentive.

The underlying design work also scales. A 2 MW rooftop needs production-grade yield modeling and bankable financials, the kind handled in the same workspace as the layout with a generation and financial tool. If your C&I pipeline outsources detailed engineering, firms like Heaven Designs cover permit-level plan sets — the SOW should then name who owns design liability.

The Myth That Detailed SOWs Scare Customers

The conventional sales wisdom says: keep the contract light, close fast, and sort out details later. Our take, after 1+ GW delivered: this is backwards. A detailed SOW closes more deals at better margin, and the light contract is what creates the nightmare customer.

The reasoning is selection, not paperwork. A customer who reads 6 pages of scope and signs is a customer who understands what they bought. A customer who refuses to read it was going to dispute the deck repair, the conduit run, and the final invoice regardless. The SOW filters them out before they cost you a crew week.

There is also a trust effect. Buyers comparing 2–3 quotes notice when one installer itemizes decking rates and panel-upgrade pricing and the others say “we’ll figure it out.” Itemization reads as experience. Transparency on exclusions is the same transparency that makes a strong proposal convert — see our breakdown of common solar proposal software mistakes for the sales-side parallel.

The exception worth admitting: for very small jobs — a 4-module garage system, a service call — a 10-section SOW is overkill. Use a 1-page simplified SOW that keeps only equipment, exclusions, and payment terms. Match document weight to job size, but never below the exclusions list.

Turning the SOW Into a Repeatable Template

A template is only useful if the 50th project uses it as faithfully as the 5th. Three practices make that happen.

Generate the SOW from the design file, not from a blank page. When the module count, inverter model, and BOM come straight out of your solar design platform, the equipment section cannot drift from what engineering approved. The same logic applies to the sales side: a solar proposal software that carries design data into the contract eliminates the retyping errors that create phantom scope.

Version your template and log every field edit. When a dispute teaches you something — a new exclusion, a better unit price — add it to the master template the same week. Our template is on version 14. Each version exists because a project paid for the lesson. If subcontractors execute parts of your scope, push the same exclusions into their subcontracts; our guide to solar subcontractor management covers that flow-down.

Review the SOW at handoff, not at signing. The 30-minute internal meeting between sales, design, and the crew lead — walking the SOW line by line before the contract goes out — catches mismatches while they are still free to fix. Scope discipline is a handoff discipline.

Conclusion

A solar scope of work is not legal padding. It is the operating manual for the project, and the exclusions and change-order rules inside it are what stand between a signed contract and a margin-eating dispute. The 10-section framework above works from a 6 kW rooftop to a 2 MW carport — only the depth changes.

Three actions to take this week:

• Audit your current SOW against the 10 sections. If exclusions, change-order triggers, or acceptance criteria are missing, add them before your next contract goes out.
• Write unit prices into every exclusion. Decking per sheet, MPU per amp, trenching per foot. Priced exclusions convert disputes into routine change orders.
• Connect the SOW to the design file. Generate equipment and layout sections from the same source as your proposal, so what the customer signs is what the crew installs.

Frequently Asked Questions

What is a scope of work in a solar contract?

A scope of work (SOW) is the section of a solar contract that defines exactly what the installer will deliver: design, equipment, installation labor, permits, utility interconnection, and commissioning. It also defines what is not included, through an explicit exclusions list. The SOW is the reference document whenever a customer, subcontractor, or inspector disputes what was promised.

What should a solar SOW exclude?

Common exclusions include main panel upgrades, roof repairs or re-roofing, tree removal, structural reinforcement, utility transformer or service upgrades, asbestos abatement, landscaping restoration, and monitoring subscriptions beyond the first year. Every excluded item should name the unit price if the customer later asks for it, so the change order is priced in seconds instead of negotiated from scratch.

How many payment milestones should a solar project have?

Most residential solar contracts use 3 to 4 milestones: a deposit of 10–20% at signing, 40–60% at equipment delivery or installation start, and the balance at substantial completion or permission to operate (PTO). C&I projects use 5 to 8 milestones tied to design approval, procurement, mobilization, mechanical completion, interconnection, and final acceptance. Never let receivables exceed completed work.

What triggers a change order in solar projects?

The most common change-order triggers are hidden roof damage found at tear-off, main panel or service upgrades required by the authority having jurisdiction (AHJ), customer-requested layout changes after design approval, utility-required equipment changes, and site-access problems. A good SOW lists these triggers explicitly and states the pricing method and approval deadline for each.

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

A C&I SOW adds sections a residential SOW does not need: prevailing-wage or labor terms, shutdown and crane windows, structural engineering sign-off, SCADA and monitoring integration, utility studies, insurance requirements, liquidated damages, and formal acceptance testing. Residential SOWs run 4–8 pages; C&I SOWs routinely run 20–50 pages with annexes.

Is a scope of work legally binding?

Yes. Once incorporated into a signed contract, the SOW is a binding part of the agreement. Courts and arbitration panels treat it as the primary evidence of what the parties agreed to deliver. This is why vague SOW language — “install solar system as discussed” — almost always resolves against the party who drafted it. Have counsel review your template once, then reuse it.