Utility Rejects Interconnection Application Response SOP

Purpose

A rejected interconnection application is not a permit problem, it is a schedule problem with a customer standing in the middle of it, and how the shop handles the rejection decides whether that customer sees a two-week correction or a silent multi-month stall. Two things make this expensive to get wrong. Resubmitting the whole design package when the utility flagged one line item invites a reviewer to find something new, on a resubmission that may not even preserve the original queue position. And where the customer's utility is transitioning between compensation tariffs, the clock that locks in the better rate usually runs on the original submission date, so treating a rejection as a fresh start can cost the customer a tariff they already qualified for. This procedure fixes the response: capture the utility's actual stated reason, fix only what was cited, verify the queue and clock impact in writing rather than assuming it, and never let the customer hear a completion date the shop does not control.

Scope

Covers the shop's response from the moment a utility interconnection application comes back rejected, returned for correction, or flagged for supplemental review, through resubmission, escalation and customer communication.

Does not cover the standard interconnection filing process itself, owned by the permit and utility interconnection process SOP, which this procedure resumes from at the point of rejection. Does not cover an electrical commissioning failure at the inverter once equipment is energized, a different event owned by its own troubleshooting tree. Does not cover the busbar and backfeed arithmetic itself, owned by the 120 percent rule reference, or state-specific tariff and interconnection detail, owned by that state's own reference card.

Roles and responsibilities

Procedure

Step 1 - Intake the rejection notice within a committed window and capture the utility's stated reason word for word. Log the notice within one business day of it arriving, copying the utility's own language rather than paraphrasing a call to their support line. Acceptance: the utility's own written reason, or reason code, captured verbatim in the file. Wrong looks like relying on a phone summary from whoever answered the queue; a summary drops qualifiers, and a resubmission built on a dropped qualifier repeats the same missing item. Hazard: none, this is document intake.

Step 2 - Classify the rejection before touching the design package. Administrative, a missing signature, a mismatched address or an incomplete form, is a same-week fix. Technical, an equipment-list mismatch, a busbar or sizing defect, or a single-line diagram gap, needs design or field involvement. Capacity, a stated hosting-capacity or queue constraint, needs a supplemental study and is the longest fix. Acceptance: one category assigned with the utility's own cited reason mapped to it. Wrong looks like treating every rejection as administrative and resubmitting the same design with a cover letter; most utilities count that as a new review rather than a correction, which can cost the customer their place in the queue. Hazard: none.

Step 3 - For a technical rejection, route the fix to the process that already owns it, and correct only what was cited. A busbar or backfeed defect is checked against the panel's actual rating and the 120 percent rule math, not re-derived here. An equipment-list defect is checked against the utility's current approved list, which changes and must be re-checked, not assumed from the last job on that utility. A single-line or documentation defect goes back to design for that one drawing. Acceptance: the corrected package resolves the specific defect cited, with nothing else in the package changed. Wrong looks like resubmitting a full redesign when only one line item was flagged, which hands a second reviewer a reason to find something new. Hazard: none at this step; the physical verification, where one is needed, happens at step 5.

Step 4 - For a capacity or hosting rejection, get the study requirement and its timeline in writing before promising the customer anything. Acceptance: written confirmation from the utility naming the required study and its stated timeline. Stop rule: no completion date goes to the customer until the utility confirms that timeline in writing; a shop-promised date it does not control is the single biggest driver of an angry callback on this rejection type. Hazard: none, this step is a written request and a wait, not field work.

Step 5 - Where the rejection cites an as-built mismatch, verify it in the field before resubmitting, and treat a busbar-rating check as energized work. Confirm the as-built equipment, inverter model, disconnect location or panel busbar rating, against the submitted drawing; where the disputed figure is the main panel's busbar rating, open the panel's dead front, prove the enclosure dead per live-dead-live, and read the busbar's stamped rating directly rather than trusting the original permit set. Acceptance: as-built and drawing agree line for line, with the busbar rating read and recorded where that was the cited item. Wrong looks like correcting the drawing from the original job notes rather than a fresh field read; equipment gets swapped mid-project more often than the paperwork catches. Hazard: opening a dead front exposes the bus; the enclosure stays open only as long as the reading takes, and closes with the dead front reinstalled and the panel restored to normal before the tech leaves.

Step 6 - Resubmit, and log the queue-position and clock impact in writing rather than assuming either. Acceptance: the new submission date recorded, and written confirmation from the utility on whether this resubmission keeps the original queue position and clock or resets both. Stop rule: where the utility's portal or contact does not clearly answer that question, escalate to a named utility interconnection contact rather than assume a correction preserves position; guessing wrong here is exactly what creates a missed deadline downstream. Hazard: none.

Step 7 - Reset the customer's timeline honestly, and where a tariff transition is in play, name the actual date that governs it. Where the customer's utility is mid-transition between compensation tariffs, confirm for that specific utility's program whether the date locking in the earlier tariff is the original submission date, the resubmission date, or the eventual interconnection agreement date, rather than assuming submission date always qualifies. Acceptance: the customer given a written, honest schedule range with its source, and the tariff-lock date confirmed with the utility rather than assumed from a different job. Wrong looks like reassuring the customer with a completion date pulled from memory of a different utility's timeline. Hazard: none.

Step 8 - Escalate on silence past a stated follow-up interval, and close with feedback where the root cause was systemic. Follow up in writing if the utility has not responded within 10 business days of a resubmission or a study request; escalate to a named utility interconnection contact or the state's utility complaint process if a second follow-up also goes unanswered. Where the rejection traced to a design or estimating gap, a system sized against a circuit already known to be capacity-constrained, feed that back to design the same week. Acceptance: follow-up sent on schedule, escalation logged if needed, design feedback logged where warranted. Wrong looks like letting a resubmission sit unconfirmed for weeks because no one owns the follow-up date. Hazard: none.

The record this produces

One rejection-response record per application: the utility's verbatim rejection reason, the category assigned, the correction made against the specific cited defect, any field verification with its reading, the resubmission date with the utility's written confirmation of queue and clock impact, the tariff-lock date confirmed for that utility's program where relevant, and the follow-up and escalation log. Where the root cause was systemic, a design feedback note closes the loop for the next proposal on that circuit.

Worked pass

A 9.5 kW DC, 7.6 kW inverter residential system, submitted for interconnection on a 200 A service. The utility rejects it, citing supplemental review required: verify service panel busbar rating and confirm compliance with interconnection sizing limits on this circuit.

Step 1: the rejection notice is logged the same day it posts, its exact wording captured rather than a phone summary. Step 2: the busbar clause reads as technical, the sizing-limits clause reads as capacity; both categories are logged against the one notice.

Step 3: the busbar math is checked against the submitted design: 200 A panel, 200 A main, a 40 A PV breaker at the opposite end of the bus, 200 plus 40 equals 240, exactly 120 percent of the 200 A bus, the standard passing case for a 7.6 kW inverter's 31.7 A continuous output. The design was compliant as submitted; nothing to correct here.

Step 4: the capacity clause is followed up in writing. The utility confirms a hosting-capacity study is required on that circuit, with a stated 6 to 8 week timeline. No completion date goes to the customer yet.

Step 5: since the busbar figure was the cited item, a tech opens the panel's dead front, proves it dead, and reads the busbar's stamped rating directly: 200 A, matching the submitted drawing. The dead front is reinstalled and the panel restored before the tech leaves.

Step 6 fails. The utility's portal shows the resubmission as received but does not state whether it preserves the original queue date or restarts it. The coordinator does not assume; the stop rule runs, and the case escalates to the utility's named interconnection contact rather than guessing. The contact confirms in writing three days later that a documentation resubmission on an already-open capacity study keeps the original date.

Step 7: the customer is told the honest range, the study's confirmed 6 to 8 week window, not a shop-estimated date. This utility is not mid-tariff-transition on this program, so no tariff-lock question applies; the file notes that this was checked rather than assumed.

Step 8: a written follow-up goes out at 10 business days into the study window with no update; the utility responds the same week with an on-track status. The busbar rejection reason is logged for design, since this is the second job this quarter where a reviewer flagged a busbar rating already correct in the original submission, worth confirming against the utility's current review checklist.

References

• The 120 percent rule reference for the busbar and backfeed math itself.
• NFPA 70E-2021, 120.5 for live-dead-live verification and 29 CFR 1910.333(b)(2) for electrical work practices (29 CFR 1926.417 in construction).
• See related: the permit and utility interconnection process SOP for the standard filing sequence this procedure resumes from, and any state-specific interconnection or tariff reference for the customer's utility's transition rules.
• The customer's utility's own published interconnection procedures and equipment list, which the shop must re-check per submission rather than assume unchanged.