Solar, storage and EV projects often slow down before installation begins. The bottleneck is usually not the equipment—it is the gap between a technically workable design and the specific documents a local reviewer or utility expects to see.
Code adoption is local
National model codes create a common foundation, but states, counties and cities adopt different editions, amendments and review practices. A drawing set should identify the adopted requirements for the actual project location instead of assuming that a template accepted elsewhere will be accepted unchanged.
Utilities and AHJs answer different questions
The AHJ typically focuses on code compliance and safe construction. The serving utility may separately review interconnection, equipment ratings, protection, metering and energization details. Treating those reviews as one generic approval path can leave gaps late in the schedule.
Review emphasis changes by project and market
- Structural assumptions and attachment details may need more explicit documentation.
- Electrical calculations and single-line diagrams may receive greater scrutiny.
- EV sites add ADA, civil, trenching, foundation and utility coordination.
- Storage projects add equipment clearances, control diagrams and fire-code considerations.
A practical way to reduce revisions
- Confirm the project address, AHJ and serving utility at intake.
- Record the adopted code editions and known local amendments.
- Coordinate equipment data across plans, calculations and schedules.
- State design assumptions clearly so reviewers do not have to infer them.
- Complete an interdisciplinary QA review before delivery.
- Keep correction notices and revision history tied to the project record.