This case study describes an ongoing effort to resolve a contractual discrepancy. Resolution efforts are continuing, and this page will be updated as appropriate.
Case Study: Enforcing a Residential Solar Contract
How a consumer navigated contract enforcement in a technically complex market
1. Purpose of This Case Study
This case study documents how a residential solar customer attempted to enforce a clear contractual commitment using standard consumer protection pathways. It is presented as a procedural example, not a complaint, and is intended to support consumer education and policy discussion.
2. The Contractual Commitment
The installer’s written proposal expressly stated that the installed solar system would include per-module (panel-by-panel) monitoring through the manufacturer’s monitoring portal. This representation appeared consistently across multiple proposal versions issued over time.
3. The Problem Encountered
After installation, the customer discovered that the system provided only aggregate system-level monitoring and did not support per-module visibility. Because monitoring access is controlled by the installer and platform configuration, this limitation was not reasonably discoverable at commissioning.
Timeline of Events (Neutral Summary)
| Date | Event | Effect |
|---|---|---|
| Proposal phase | Installer proposals repeatedly state per-module monitoring | Consumer relies on written feature set when selecting installer |
| Installation completed | System commissioned with aggregate-only monitoring | Limitation not reasonably discoverable at handover |
| Post-installation | Installer provides documentation describing per-module monitoring | Reliance reinforced |
| Follow-up inquiry | Consumer asks about using per-module monitoring | Documentation withdrawn as “sent in error” |
| Written admission | Installer confirms proposal language was incorrect | Contractual non-performance acknowledged |
| Mitigation offered | Nominal monetary offer | No delivery of promised functionality |
| Resolution efforts ongoing | Consumer seeks contractual remedy | Matter remains unresolved at time of publication |
4. Post-Installation Reinforcement of Reliance
After installation, the installer provided system documentation that included full instructions for per-module monitoring. When the customer indicated that they were looking forward to using this functionality, the installer later advised that the documentation had been sent in error and that the installed system architecture did not support per-module monitoring.
This sequence reinforced the customer’s reasonable belief that the promised functionality existed and delayed discovery of the contractual shortfall.
5. Installer Acknowledgement
In subsequent correspondence, the installer acknowledged that the reference to per-module monitoring in the proposal was an error and confirmed that the installed system could not deliver that functionality. The installer also stated that, prior to a recent platform change, the inverter systems they commonly deployed did in fact support module-level monitoring.
6. Nominal Mitigation vs Contractual Performance
The only mitigation offered was a small monetary amount that did not correspond to the cost or functionality of delivering the promised monitoring capability. No proposal was made to modify the system architecture to provide equivalent performance.
This raised a core question: when a contracted feature cannot be delivered, what constitutes an adequate remedy?
7. Escalation Pathways
The customer pursued resolution through:
- direct engagement with the installer,
- documentation of contractual commitments and admissions,
- and preparation for formal dispute resolution.
This case illustrates how enforcement responsibility often shifts to consumers even where contractual terms are clear.
8. What This Case Demonstrates
- Technical complexity amplifies information imbalance
- Template-based proposals can propagate material errors
- Some system capabilities are undiscoverable until after installation
- Admission of error does not automatically result in correction
- Consumers bear the burden of enforcement
9. Transparency and Redaction
Personal identifiers have been removed. Public filings and written correspondence are referenced where permissible. This case study is presented for educational and policy purposes.
This case study reflects one example and does not imply that similar outcomes occur in all residential solar projects.