Why your ICX application keeps getting rejected (and how to fix it)
C&I Interconnection · Kriya Partners
Most C&I interconnection rejections aren't random. They follow patterns - and most happen before anyone at the utility has even looked at the technical merits of your project. Here's what's going wrong and how to fix it ahead of time.
Mistake #1
Assuming the study track before checking the feeder
A lot of C&I developers assume their system qualifies for simplified or Fast Track review based on system size alone. System size is only one factor. Grid conditions at the specific point of interconnection determine the track.
A 500 kW system on a healthy feeder might sail through screening. The same system on a feeder that's near capacity can trigger a full study. Projects exceeding 15% of feeder capacity, or those near voltage regulation equipment, often fail screening automatically no matter how neat and tidy the application is.
Before you submit: find out what's on that feeder. Many utilities publish hosting capacity maps that show available capacity by feeder - Xcel Energy's map is a good example of what these look like, and the DOE maintains a national atlas of utilities that publish them. Where maps aren't public, a direct call to the utility before submission usually gets you what you need. A full study for C&I typically runs 6 to 24 months - budget that in before you make any timeline commitments to clients.
Mistake #2
A single-line diagram that wasn't built for that utility
The SLD is the most reviewed document in your application package and the most common reason for rejection. Utilities check it against your equipment list, your application fields, and their own formatting requirements. Any mismatch - between documents, or between your SLD and what the utility expects to see - is a kickback.
- Missing elements: conductor sizes, OCPD ratings, all disconnects, grounding electrode system, point of interconnection
- Inverter model number and suffix that don't match the certification listing exactly - minor variants may not carry the same certification
- SLD not matching the equipment list (version drift between documents)
- Missing utility-specific notes, label conventions, or diagram callouts
- No PE stamp on systems that require one
Boilerplate SLDs don't work here. Each utility has formatting requirements that vary by territory. What cleared one utility's review last year may not clear a different utility this year - or the same utility after a checklist update.
Mistake #3
Load data that's estimated instead of actual
Utilities need to understand what's actually happening at the site: peak demand, load profile, how much solar output will be consumed on-site versus exported. Submitting estimates instead of actual 12-month interval data is a common rejection trigger - and one that often comes with a request to resubmit the whole package.
The specific issues:
- Peak load estimates submitted instead of utility billing data or interval meter data
- System output not reconciled with actual site consumption - if export exceeds the utility's threshold at that interconnection point, it gets flagged
- Transformer capacity ignored - undersized transformers on older sites can trigger required service upgrades that change project economics entirely
- Export limits not checked against the utility's tariff before submission
For C&I sites with complex loads - multiple meters, variable demand, EV charging, or battery storage - this section of the application needs more attention than a straightforward offset-only solar project.
Need help pulling accurate 12-month interval data for your site? Get in touch - it's something we can sort out before the application goes in.
Mistake #4
Equipment that isn't confirmed on the utility's approved list
Utilities check that every piece of equipment in your application is on their approved list with current certifications. This is granular, and it matters.
Inverters need to carry UL 1741 SA certification or meet IEEE 1547-2018 compliance. The exact model number and suffix on your application needs to match the certification listing exactly - not approximately. A slightly different inverter variant that looks the same but doesn't carry the same listing is a rejection.
A concrete example: the Enphase IQ7 family includes the IQ7, IQ7+, IQ7A, and IQ7X.
They look nearly identical in spec sheets and are often referenced interchangeably in proposals.
But they're distinct SKUs with different power output ratings, module compatibility ranges,
and certification scopes.
A utility's approved equipment list may include the IQ7+ but not the IQ7A,
or vice versa depending on when the list was last updated. Submitting an application with
the wrong variant - even one that's physically on the roof - gets kicked back.
The same applies across SolarEdge, Fronius, SMA, and every other major manufacturer
that ships multiple configurations under the same product line name.
Confirm every piece of equipment is on the utility's approved list before the application is built, not after. Rapid shutdown gear, disconnect specifications, and protective relay settings for larger systems all get checked. Don't assume - verify.
What clean looks like
A complete C&I application covers all of this before it goes in
Clean applications aren't built from templates. They're built around the specific utility, the specific feeder, and the specific site. Here's what that actually means in practice:
- Study track assessed before submission Feeder conditions checked - not just system size - against hosting capacity data or direct utility contact.
- SLD built for this utility Complete, utility-specific, with all required elements. Matches the equipment list and application form exactly.
- Load data from actual meter records 12-month interval data, not estimates. Export levels checked against the utility's tariff thresholds.
- All equipment confirmed on the approved list Exact model numbers and suffixes verified before the application is filed.
- PE stamp included where required Know the threshold for your utility and jurisdiction - don't assume it's not required.
- Utility-specific formatting followed Notes, labels, diagram conventions - checked against that utility's current requirements, not last year's.
The piece that's hardest to systematize: someone who knows that utility's review team and what they're actually looking for. Utilities have quirks. Review teams have preferences. That knowledge gets built over hundreds of submissions - and it's the difference between first-pass approval and a kickback that costs you two months.
Getting interconnection right the first time isn't complicated. It just requires building around the specific project, the specific utility, and the specific feeder - not a template.
Most rejections at completeness review are preventable. The ones that come back from technical review - wrong study track, load data issues, feeder constraints - take more work to fix. But both are avoidable with the right preparation before the application goes in.
Kriya handles interconnection end-to-end. We've submitted enough applications across enough utilities to know what they want - and we build packages around that.
