Back to Blog
solar design 25 min read

Residential Solar Permit Design Services: 10 Gates

Use 10 gates to procure residential solar permit design services across AHJ research, roof and service inputs, storage, revisions, filing, and QA.

Keyur Rakholiya

Written by

Keyur Rakholiya

CEO & Co-Founder · SurgePV

Rainer Neumann

Edited by

Rainer Neumann

Content Head · SurgePV

Published ·Updated

Quick Answer

Residential solar permit design services should produce address-specific drawings and calculations for the current AHJ and utility route. Define permit, interconnection, structural, electrical, storage, professional-seal, filing, revision, and record boundaries before purchase. Accept the package only after cross-sheet reconciliation, authority-comment closure, field-change control, and editable final-file handover.

Residential solar permit design services convert site evidence, equipment, code, utility, and authority requirements into a project-specific submission. They do not sell a universal drawing template or guaranteed approval. The installer remains responsible for giving accurate field inputs and controlling changes through construction.

Quick answer: Residential solar permit design services should produce address-specific drawings and calculations for the current AHJ and utility route. Define permit, interconnection, structural, electrical, storage, professional-seal, filing, revision, and record boundaries before purchase. Accept the package only after cross-sheet reconciliation, authority-comment closure, field-change control, and editable final-file handover.

The US Department of Energy permitting overview explains that local permitting, inspection, and utility connection are distinct stages. Local governments use different rules and fees. A provider’s proposal should separate those duties just as clearly.

Residential Solar Permit Design Services: 10 Gates

Use ten gates from project classification through record-file acceptance. A gate closes only when the named evidence, reviewer, and responsibility are clear. Missing information should become a request for information, not a hidden design assumption.

GateDecisionAcceptance evidence
1Project profileAddress, occupancy, roof, system, storage, service, and work scope classified
2Authority routeCurrent AHJ, utility, code, amendment, permit, interconnection, fire, and filing path recorded
3Provider boundaryDrafting, calculations, engineering, seal, filing, comments, field support, and records assigned
4Site intakeRoof, framing, service, meter, equipment, photographs, and property evidence complete
5Design basisLayout, attachments, electrical architecture, equipment, operating modes, and assumptions approved
6Plan productionRequired sheets, calculations, schedules, labels, forms, and attachments prepared
7Cross-sheet QACounts, models, capacities, stringing, protection, structure, notes, and forms reconciled
8Submission and commentsFiling owner, status, fees, responses, revisions, and resealing controlled
9Field and inspection changesApproved-plan deviations, correction notices, substitutions, and as-built decisions logged
10Final handoverApproved, editable, record, comment, calculation, and source files indexed and retained

This page focuses on buying the design service. The PE-stamped solar plans guide covers professional-seal and responsible-charge decisions in more depth. The solar permit plan-set service guide covers plan-set procurement across broader project types.

Gate 1: Classify the Residential Project

Project type controls the evidence request. A simple sloped-roof PV array can follow a different route from storage, a service upgrade, or an unusual structure. Reroofing, ground mounts, generator integration, and systems on accessory buildings can also change the route.

Start with a profile sheet:

  • Exact address, parcel, owner, occupancy, and building type
  • Existing permitted structures, additions, solar, storage, generator, and service equipment
  • Roof covering, age or known work, condition, framing, slope, geometry, and access
  • Proposed PV, inverter, racking, attachments, MLPE, storage, backup loads, and controls
  • Electrical service, meter, main panel, bus, breakers, conductors, grounding, and point of interconnection
  • Required structural changes, reroofing, service work, trenching, new structures, or fire review
  • Intended AHJ, utility, permit route, interconnection route, and construction schedule

Do not classify a property from an aerial image alone. Confirm the legal address and jurisdiction. A postal city, county boundary, utility territory, and fire authority may not align.

Create complexity tiers for pricing and staffing. A provider may define standard rooftop PV, PV with service work, PV plus storage, unusual structure, and custom engineering tiers. The tier names matter less than written entry and exit conditions.

Gate 2: Build the Authority Register

An authority register identifies every body, current source, effective date, requirement, owner, and open question. It should be refreshed before submission and after a material delay or scope change.

Record:

  1. Building and electrical AHJ
  2. Fire authority where separate
  3. Utility or interconnection authority
  4. Adopted building, electrical, fire, residential, energy, and local amendment sources
  5. Zoning, historic, flood, wildfire, coastal, snow, wind, or other location controls
  6. Contractor and professional-licensure bodies
  7. Permit portal, forms, file standards, fees, signatures, and submission credentials
  8. Inspection, correction, closeout, and permission-to-operate routes

Do not copy a code edition from the last project. Record the source and adoption or effective date. Ask the AHJ when official material conflicts or leaves the project classification unclear.

The NCEES licensure route helps locate state boards. Each board and state law controls its jurisdiction. NCEES does not decide whether a specific residential plan needs a particular discipline or seal.

Three AHJ examples show why the register matters

Phoenix, Arizona currently accepts qualifying residential designs through SolarAPP+. Its official SolarAPP page lists eligibility limits. It also requires correlated approval documents, a three-line diagram, and plot plan. Phoenix identifies a separate fire permit route for PV and battery systems.

San Diego, California publishes Information Bulletin 301. The May 2026 page separates electrical, combination building, structural-modification, ground-mount, reroof, and other routes. It provides project-specific submittal and template information.

New York City publishes an owner solar checklist and related professional requirements. The page addresses registered design professionals, permits, licensed work, inspections, and closeout within New York City. It is not a rule for another city or state.

These examples do not form a national checklist. They show that route, professional involvement, documents, and closeout can differ. Use each page only within its named jurisdiction and current scope.

Gate 3: Separate Every Service Boundary

The phrase permit design can hide several transactions. List each one as included, excluded, optional, client-supplied, or third-party.

ServiceQuestion to settle before award
AHJ researchWho confirms jurisdiction, current adopted sources, forms, portal, and project path?
Utility researchWho confirms interconnection documents, equipment evidence, diagrams, settings, meter, and permission route?
DraftingWhich site, roof, layout, attachment, electrical, label, detail, and schedule sheets are delivered?
CalculationsWhich structural, electrical, loading, conductor, protection, grounding, or other calculations are included?
EngineeringWhich discipline, licence, responsible charge, review, seal, and liability scope apply?
Storage and fireWho covers equipment location, clearances, operating modes, backup, protection, fire documents, and review?
FilingWho creates accounts, pays fees, uploads, signs, communicates, and tracks status?
CommentsWhich AHJ and utility comment rounds are included, and which changes trigger new scope?
Field supportWho answers installer questions, reviews substitutions, responds to corrections, and updates plans?
CloseoutWho prepares approved, as-built, record, editable, and archive files?

A permit approval stamp is not the same as a professional engineer’s or architect’s seal. A provider should not sell a detached seal. Responsible professionals must control their work under the applicable law and board rules.

The proposal should name the actual professional or describe the assignment process without inventing availability. Verify licence and discipline through the responsible state board. Confirm professional liability and contract terms with qualified advisers.

Gate 4: Control the Installer Intake

The provider cannot produce an address-specific plan from incomplete or unreliable inputs. Use a required intake with source, date, collector, checker, status, units, and evidence link.

Property and roof inputs

Record address, parcel, owner consent, occupancy, building count, setbacks, easements, property lines, and access. Capture roof planes, slopes, azimuths, dimensions, edges, obstructions, equipment, and pathways.

Document covering, condition, known leaks, planned reroof, framing type, member size, spacing, span, supports, sheathing, attachments, and accessible evidence. Do not label an estimated framing value as field verified.

Photographs need orientation and labels. Include wide context, every roof plane, attic or framing evidence where safely accessible, meter, service, panels, labels, conductor paths, proposed equipment locations, and obstructions.

Electrical inputs

Record utility, service voltage, phase, meter, main rating, panel bus, main breaker, subpanels, feeders, grounding, and available spaces. Identify existing generation, storage, generators, EV charging, and the proposed connection point.

Use legible equipment labels and photographs. A hand-entered rating needs a checker. Flag damaged, obsolete, inaccessible, or unidentifiable equipment for qualified field review.

Equipment and operating inputs

Name exact modules, inverters, MLPE, racking, attachments, batteries, gateways, disconnects, transfer equipment, meters, and controls. Keep current datasheets, installation instructions, certifications, listings, compatibility documents, and warranties.

For storage, define grid-connected and outage modes, protected loads, transfer, generator interaction, shutdown, communications, and equipment locations. The plan must reflect the intended operating architecture, not a generic battery symbol.

Assumption and RFI control

Every missing input becomes an RFI with owner, due date, design effect, and response evidence. The designer should identify any temporary assumption and block submission when it affects safety, code, professional responsibility, or permit completeness.

The residential solar design workflow explains how survey evidence becomes a controlled design basis. The rooftop structural assessment guide covers roof and structural evidence boundaries.

Gate 5: Approve the Design Basis

The design basis is a short controlled record that precedes plan production. It should state the project route, source hierarchy, equipment, architecture, calculations, exclusions, and unresolved items.

Include:

  • AHJ, utility, route, source dates, adopted requirements, and open authority questions
  • Array geometry, setbacks, pathways, access, shade or obstruction treatment, and roof assumptions
  • Exact module count, DC capacity, inverter architecture, strings, MPPTs, and operating values
  • Racking, attachment, framing, loading, waterproofing, corrosion, and structural review basis
  • Service, point of connection, conductor, protection, grounding, labeling, and shutdown basis
  • Storage, backup, generator, EV, service-upgrade, and fire-review scope where applicable
  • Permit, interconnection, engineering, filing, inspection, and closeout responsibility
  • Sheet list, calculation list, attachments, forms, editable files, and naming/version rules

Freeze the baseline before drafting. When input changes, log the change and identify every affected sheet, calculation, form, attachment, and authority submission.

Do not let a sales proposal silently control engineering. Reconcile contracted equipment and system size, then retain the approved technical source.

Gate 6: Define the Deliverable Package

The exact sheet list varies, but a residential package may include:

  1. Cover, project information, scope, code and authority notes, symbols, and sheet index
  2. Site or plot plan with structures, property context, access, equipment, and required setbacks
  3. Roof plan with planes, slopes, obstructions, pathways, array, dimensions, and module count
  4. Attachment or mounting plan with framing basis, spacing, hardware, loads, and details
  5. Electrical single-line or three-line diagram with modules, strings, inverter, service, protection, grounding, meter, and interconnection
  6. Equipment schedules, conductor and protection fields, labels, placards, and calculations
  7. Storage and backup diagrams, locations, clearances, modes, protection, and fire details where included
  8. Structural calculations, electrical calculations, professional documents, and seals where required
  9. Exact equipment sheets, certifications, listings, compatibility evidence, and forms
  10. AHJ, utility, fire, filing, inspection, and closeout attachments required for the route

Define PDF sheet size, orientation, naming, bookmarks, editable format, file size, and colour. Record signature and portal constraints separately. A complete drawing can still fail upload rules.

The current SolarAPP+ portal is a route for participating jurisdictions and eligible projects. It does not replace the local AHJ’s eligibility and correlated-document requirements.

Utility interconnection is separate. PG&E’s current residential solar page distinguishes contractor application work from PG&E review, upgrades, and written permission to operate. Use it only for the applicable PG&E project and current tariff route.

Gate 7: Run Cross-Sheet QA

Quality control should be independent from initial drafting. Use a checker who can trace each field to source evidence and confirm changes across the package.

Reconcile counts and identities

Match address, owner, parcel, utility, AHJ, module count, DC capacity, inverter, battery, racking, and attachments. Reconcile service, meter, panel, and connection point across every sheet, form, calculation, schedule, and attachment.

Reconcile geometry and structure

Check roof planes, slopes, dimensions, obstructions, pathways, setbacks, module spacing, array boundaries, access, attachment locations, framing assumptions, spans, loads, and detail references. Verify that calculations use the same geometry and equipment.

Reconcile electrical design

Check module and inverter values, string counts, MPPT allocation, temperature conditions, conductors, ampacity, and voltage drop. Reconcile protection, disconnects, grounding, labels, service ratings, and the interconnection method.

Reconcile storage and controls

Check battery quantity, energy and power fields, BMS pairing, gateways, meters, CT direction, and transfer equipment. Reconcile protected loads, operating modes, shutdown, generator interfaces, locations, clearances, and communication wiring.

Reconcile authority and document fields

Check code and amendment notes, forms, signatures, professional information, licence, seal, dates, sheet revisions, equipment files, portal names, fee references, and submission identifiers.

Run PDF preflight after drawing QA. Check fonts, line weights, clipping, page order, hyperlinks where allowed, bookmarks, file size, signatures, and print legibility. Review at the size an examiner or field installer will use.

Gate 8: Control Submission, Comments, and Revisions

Define who creates the portal account, signs, uploads, pays, communicates, receives comments, and tracks status. Protect owner and contractor credentials. Do not share one account across unrelated clients.

The comment log should record:

  • Authority, project, submission and comment identifiers
  • Received date, reviewer wording, sheet or document affected
  • Assigned responder and required professional involvement
  • Proposed response, source, design effect, and commercial effect
  • Revised sheets, calculations, forms, attachments, and revision marks
  • Submitted date, authority response, closure status, and remaining action

Distinguish correction from redesign. A provider may include ordinary comments caused by its omission. It may charge for owner changes, equipment swaps, site changes, new storage, service upgrades, code changes, or new authority scope. The contract should say so clearly.

Professional revisions may require a responsible professional’s review and resealing. A drafting provider should not alter sealed work without the required professional process.

Phoenix currently instructs SolarAPP+ users to obtain a revised approval and submit correlated revised documents. San Diego and New York City publish their own amendment or revision routes. Do not transfer one process to another jurisdiction.

Gate 9: Control Field Changes and Inspection Corrections

The installer should build from the approved plan set and current issued permit. Keep the approved set available at the site in the required form. Mark field questions before work hides the condition.

A field-change request should identify:

  1. Existing approved condition
  2. Actual field condition
  3. Proposed change and reason
  4. Safety, code, structure, electrical, fire, warranty, and utility effect
  5. Affected sheets, calculations, equipment, forms, and approvals
  6. Responsible designer and professional review
  7. AHJ or utility amendment need
  8. Price, schedule, construction hold, and acceptance evidence

Do not treat an equipment swap as an administrative note. A module, inverter, battery, racking, attachment, service, or protection change can affect calculations, labels, certifications, layout, and authority documents.

Inspection corrections use the same control. Record the inspector’s wording, photographs where permitted, approved response, corrected work, revised plan or as-built need, reinspection, and closeout.

Gate 10: Accept the Final Record Package

Final handover should support construction, inspection, service, later reroofing, warranty, and future modification. Define retention period and access before the provider closes the job.

Require as applicable:

  • Issued and approved permit plan set
  • Utility interconnection documents and final status
  • Fire or storage approvals
  • Final calculations and professional documents
  • Comment and revision log
  • Field-change and inspection-correction records
  • Approved as-built or record set where required
  • Editable source files in the contracted format
  • Exact equipment documents, certifications, and compatibility records
  • Portal receipts, submission identifiers, fees, inspection, closeout, and permission records
  • File index, version history, naming convention, and archive checksum or integrity method

Test the archive. Open the editable and PDF files in a clean environment. Confirm fonts, references, attachments, external links, and revision history. Remove unrelated client data.

Set security requirements for transfer, storage, access, subcontractors, retention, deletion, breach response, and account closure. Permit files can contain addresses, electrical details, signatures, owner information, and professional credentials.

How to Select a Permit Design Provider

Issue the same RFQ and representative project pack to each candidate. Do not compare headline price or turnaround until scope and project tier are normalised.

Score:

  • Jurisdiction and utility research method
  • Residential roof, electrical, storage, and service-change competence
  • Intake quality and RFI discipline
  • Professional-licensure and responsible-charge process
  • Sheet, calculation, form, and equipment-document completeness
  • Independent QA and cross-sheet reconciliation
  • Comment, revision, field-change, inspection, and as-built workflow
  • Filing boundary and communication controls
  • File security, subcontractor, retention, deletion, and incident terms
  • Schedule basis, staffing, capacity, escalation, price, exclusions, and change orders

Run a pilot across representative work, not only the simplest roof. Include at least one standard PV project, one service or structural question, and one storage or custom case when those jobs are in scope.

Measure first-submission completeness, RFI usefulness, assumption count, error rate, rework, comment cause, and provider-controlled closure time. Also measure revision traceability, file usability, field questions, and total internal hours. Separate authority review time from provider-controlled time.

Normalise Price, Schedule, and Risk

Convert every proposal into the same scope table before comparing cost. A low drawing price can exclude authority research, calculations, professional review, filing, comments, storage, or editable files. Those exclusions move cost and delay back to the installer.

Record one-time setup, standard project, complexity tier, calculation, seal, expedited service, filing, authority fee, revision, redesign, site-change, and archive charges separately. State whether tax, portal fees, courier work, and licensed-contractor work are included. The solar permit plan-set cost guide provides a broader cost-normalisation method.

Test the quoted schedule from a defined start event. That event might require a complete intake, accepted purchase order, assigned professional, or cleared payment. Split provider production, installer response, professional review, AHJ review, utility review, correction, and inspection time. Do not present an authority’s review duration as provider-controlled turnaround.

Use a written service level for:

  • Intake review and first RFI
  • Initial coordinated plan set
  • Internal QA completion
  • Professional review when contracted
  • Filing confirmation when contracted
  • Comment acknowledgement and response
  • Field-change assessment
  • Final approved and editable archive

Price the expected portfolio, not one showcase file. Apply realistic shares for standard roofs, complex structures, storage, service work, equipment substitutions, comments, and cancelled projects. Add installer review time and rework. Compare the total controlled cost per accepted package.

The solar permit package checklist can become the acceptance schedule attached to the purchase order. Use the solar permit drawings guide to distinguish drawing content from calculations, forms, filing, and engineering. Use the solar permit expediting guide when submission tracking or authority coordination is a separate purchase.

Set remedies that match controlled failures. Examples include correction without added design fees, escalation after a missed response target, credit for repeated provider errors, or termination with usable work files. Do not penalise a provider for an authority delay outside its control.

Evaluating Heaven Designs

Heaven Designs publishes residential and commercial permit-design services for the United States and Canada. That page is a related-party provider statement. It does not prove current AHJ knowledge, utility fit, assigned professional, licence, insurance, turnaround, acceptance, price, capacity, or project outcome.

Disclosure: SurgePV promotes Heaven Designs through a commercial relationship. Apply the same jurisdiction research, licence, responsible-charge, intake, sample, QA, revision, security, schedule, price, reference, and acceptance gates to Heaven Designs and every alternative.

Review Heaven Designs’ published permit scope. Request a sample that matches the project’s roof, service, storage, authority, and professional-review profile. Choose another provider when its controlled evidence and pilot result are stronger.

Use the 24-hour permit plans guide when schedule is the dominant claim. Use the solar CAD design services guide when editable drafting production is the main purchase.

Final Acceptance Rule

Accept the service only when every controlled record tells the same project story. That includes the authority register, intake, design basis, plan set, calculations, comments, changes, and final archive.

A clean PDF is not enough. The provider must show traceable inputs, reconciled outputs, controlled revisions, correct service boundaries, and usable final files. The responsible AHJ, utility, professionals, inspectors, and licensed contractors retain their respective decisions and duties.

Frequently Asked Questions

What do residential solar permit design services include?

Scope may include site and roof plans, array layout, attachments, electrical diagrams, equipment schedules, labels, calculations, datasheets, forms, revisions, and final files. Confirm each item.

Does one residential solar plan template work nationwide?

No. State law, AHJ, utility, adopted codes, amendments, property, roof, service, equipment, storage, and submission route can change the required package.

What site data should an installer provide?

Provide verified address and parcel data, roof geometry and condition, framing, obstructions, photographs, service and meter details, equipment, cable route, and authority information.

Are structural engineering and a professional seal always included?

No. Requirements and scope vary by jurisdiction and project. Confirm discipline, licence, responsible charge, calculations, seal, revisions, and resealing with the AHJ and professional.

Is battery storage included in a standard PV permit plan?

Not automatically. Storage adds location, clearances, mounting, operating modes, backup loads, disconnects, protection, interconnection, fire review, equipment documents, and commissioning interfaces.

Can SolarAPP+ be used for every residential solar project?

No. Use depends on participating jurisdiction and project eligibility. The local AHJ may require correlated documents, separate permits, revisions, fees, or another review path.

How should AHJ comments and plan revisions be priced?

Define included comment rounds, correction scope, equipment swaps, site changes, authority changes, redesign, professional resealing, filing fees, response time, and change-order rules in writing.

Can a permit design provider guarantee approval?

No. The AHJ, utility, fire authority, licensing board, inspector, and other responsible bodies control their decisions. A provider can commit to defined quality and response work.

How should Heaven Designs be evaluated?

Apply the same jurisdiction research, licence, responsible-charge, intake, sample, QA, revision, security, schedule, price, reference, and acceptance gates used for every provider.

About the Contributors

Author
Keyur Rakholiya
Keyur Rakholiya

CEO & Co-Founder · SurgePV

Keyur Rakholiya is CEO & Co-Founder of SurgePV and Founder of Heaven Green Energy Limited, where he has delivered over 1 GW of solar projects across commercial, utility, and rooftop sectors in India. With 10+ years in the solar industry, he has managed 800+ project deliveries, evaluated 20+ solar design platforms firsthand, and led engineering teams of 50+ people.

Editor
Rainer Neumann
Rainer Neumann

Content Head · SurgePV

Rainer Neumann is Content Head at SurgePV and a solar PV engineer with 10+ years of experience designing commercial and utility-scale systems across Europe and MENA. He has delivered 500+ installations, tested 15+ solar design software platforms firsthand, and specialises in shading analysis, string sizing, and international electrical code compliance.

Get Solar Design Tips in Your Inbox

Join 2,000+ solar professionals. One email per week - no spam.

No spam · Unsubscribe anytime

Book Free Demo