SolardeckStart Free
Solar SOW guide

A solar SOW should protect the consultant and make the client responsibilities obvious.

Use this guide to define the advisory scope, deliverables, responsibilities, required inputs, acceptance criteria, and exclusions before the project drifts.

Best for

Solar consultants scoping feasibility, utility review, proposal packs, RFP support, or owner-rep advisory work.

Solar statement of work guide with phases, deliverables, owners, exclusions, and acceptance criteria
Solar advisory detail

What to include before the client sees the pack.

These sections are written to be useful in the workflow itself: intake prompts, document sections, review checks, and client handoff content.

SOW phases

Structure the work so the client understands the sequence.

Discovery and client input collection
Utility, usage, tariff, and site review
Advisory analysis, recommendation, document pack, and handoff

Responsibilities

Every deliverable should have a consultant responsibility and a client responsibility.

Client owns bills, site access, data, deadlines, and approvals
Consultant owns review, analysis, advisory recommendations, and deliverable preparation
Third parties own engineering, permitting, tax advice, incentives, or EPC pricing when excluded

Acceptance criteria

Define what done means before revisions begin.

Proposal pack delivered in agreed format
Assumptions and missing data documented
Client has a milestone tracker and approval path
Common questions

Questions about solar statement of work guide.

Clear answers help the consultant and client agree on what is known, what is assumed, what is excluded, and what should happen next.

What should a solar SOW include?

A solar SOW should include project background, phases, deliverables, consultant responsibilities, client responsibilities, required inputs, timeline, acceptance criteria, assumptions, exclusions, and approval terms.

How do you prevent scope creep in solar consulting?

Name exclusions clearly, tie each deliverable to acceptance criteria, list required client inputs, separate advisory work from engineering or EPC work, and keep the milestone tracker aligned to the signed SOW.

Should client responsibilities be in the SOW?

Yes. Utility data, bills, site access, tariff details, stakeholder approvals, and decision deadlines often determine whether the consultant can produce a credible recommendation.

Can Solardeck generate a solar SOW from intake?

Yes. Solardeck can generate a SOW from the same solar intake used for the proposal, assumptions, milestone checklist, client tracker, and PDF handoff.

Does Solardeck replace legal review?

No. Solardeck structures advisory scopes and deliverables, but consultants should use their own contract terms and legal review where needed.

Make it repeatable

Turn this guidance into a reviewed solar proposal workflow.

Solardeck turns intake answers into proposal sections, SOW phases, assumptions, missing-data requests, tracker items, and PDF-ready handoffs.

First proposal path

Capture a structured solar intake
Generate the advisory pack
Review assumptions and missing inputs
Share the portal and export the PDF
Start first proposal