Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

40. Permitting & Interconnection

Learning objectives

  • Assemble a permit-ready plan set.
  • Navigate the AHJ and utility approval tracks to PTO.

40.1 Two parallel approval tracks

AHJ (Authority Having Jurisdiction): the governmental body (typically a local building department) authorized to enforce codes, review permit applications, and conduct inspections for a given project location.
One-line diagram (single-line diagram): a simplified electrical schematic showing the system's components and their connections using single lines rather than individual conductors. It is a required permit document for PV systems.

Every grid-tied job runs two approvals at once:

  • AHJ (building department) permit: submit a plan set: site plan, one-line diagram, equipment specs with listings (Ch 21), structural documentation (Ch 25), electrical calculations (conductor/OCPD/voltage drop, Ch 16), and the label schedule (Ch 23). Plan review → permit → install → inspection.
  • Utility interconnection: submit an interconnection application → approval to install → post-install inspection/witness test → Permission to Operate (PTO), after which the system may legally energize and export.

40.2 Avoiding rejection

Permit rejections cluster around predictable errors. The most common are NEC 690.8 conductor-sizing mistakes (Ch 16, an estimated 30–40% of rejections), missing/incorrect labels for the adopted edition, and incomplete structural documentation. A clean, complete, edition-correct package is the cheapest way to keep a project on schedule.

40.3 Two parallel approval tracks

   ┌─────────────── AHJ PERMIT TRACK ───────────────┐   ┌──── UTILITY TRACK ────┐
   plan set (site plan, one-line, listings,             interconnection
   structural, calcs, labels) ─► plan review ─►          application ─► approval
   PERMIT ─► install ─► INSPECTION                        ─► install ─► witness ─► PTO
                          │                                                   │
                          └──────── system may legally ENERGIZE/EXPORT ◄──────┘
   ⚠️ top rejection causes: 690.8 sizing errors, wrong-edition labels, missing structural docs

Chapter 40 summary

Run the AHJ permit and utility interconnection tracks in parallel: a complete, code-edition-correct plan set (one-line, listings, structural, calcs, labels) earns the permit; the interconnection application earns PTO. Most rejections trace to sizing errors, label mismatches, or missing structural docs.

  • AHJ (Authority Having Jurisdiction): the governmental body authorized to enforce codes and conduct inspections; typically the local building department.
  • Plan set: the complete permit submission package (site plan, one-line diagram, listings, structural docs, calculations, label schedule).
  • One-line diagram: a simplified electrical schematic of the PV system required for permit submission.
  • PTO (Permission to Operate): the utility’s final authorization for a system to energize and export power to the grid.
  • Interconnection application: the utility’s approval process running in parallel with the AHJ permit track.

Full definitions: Appendix A (glossary).

Practice Problems: Chapter 40

  1. Name the two parallel approval tracks every grid-tied job runs.
  2. What document set does the AHJ permit track require?
  3. What milestone must occur before a system may legally energize and export?
  4. What are the three most common causes of permit rejection?
  5. Why run the two tracks in parallel rather than sequentially?

Solutions: Chapter 40

  1. The AHJ (building department) permit track and the utility interconnection track.
  2. A plan set: site plan, one-line diagram, equipment listings, structural documentation, electrical calculations, and label schedule.
  3. Permission to Operate (PTO) from the utility.
  4. NEC 690.8 sizing errors, wrong-edition labels, and missing/incomplete structural documentation.
  5. To compress the schedule: both approvals take time, so running them concurrently avoids serial delays.