Ensure a California residential solar sale complies with current Solar Consumer Protection Guide disclosure and signature requirements
domain: solar.consumer-protection · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Use the current Version 4 (2025-published) California Solar Consumer Protection Guide — confirm the specific document version against cpuc.ca.gov/solarguide before using in a sales packet
Provide the customer the CSLB-created Solar Energy System Disclosure Document, including its one-page cover sheet showing total system cost, financing obligations, and a standardized bill-savings estimate
If the project will interconnect with PG&E, SCE, SDG&E, Bear Valley Electric, PacifiCorp, or Liberty, collect the customer's initials and signature on the Consumer Protection Guide itself as a mandatory step before submitting the interconnection application
Give the customer adequate time to read the Guide before signing — do not present it as a same-appointment rubber-stamp form
Honor the statutory cancellation window: at least 3 business days for standard customers, extended to 5 business days if the customer is 65 or older
Retain signed disclosure and cancellation-notice documentation in the project file in case of a later consumer complaint or CSLB inquiry
Known gotchas
The signed Consumer Protection Guide requirement is tied to specific utility territories (PG&E/SCE/SDG&E/BVES/PacifiCorp/Liberty) — confirm the customer's utility is on that list before treating the signature as mandatory versus best-practice
The senior cancellation window (5 business days for 65+) is longer than the standard window — sales staff defaulting to the standard 3-day window for a senior customer creates a compliance gap
Guide versions are periodically revised (Version 4 in 2025) — using an outdated PDF version in a sales packet can itself create a disclosure compliance problem
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?