There are no blanket SolarAPP+ states. Coverage follows participating jurisdictions, supported product features, and project eligibility. A state can appear in the official table while most addresses still use another permit path.
That distinction matters for multi-state installers. A sales team may hear “SolarAPP+ is available in California” and promise an instant permit. The permit coordinator then discovers a missing jurisdiction, an unsupported battery, or a separate local filing step.
Direct answer. The official SolarAPP+ location table contained 474 rows across 18 state abbreviations on September 26, 2026. Those rows do not equal 474 active, full-featured permitting authorities. Verify the project address, the supported feature, and the system eligibility before scheduling around instant approval.
This guide shows that three-gate check. It uses the official SolarAPP+ availability page and its downloadable location table. Both were accessed on September 26, 2026.
- State presence is a discovery signal, not an eligibility decision.
- The official table listed 18 state abbreviations and 474 location rows at the research cutoff.
- Feature support can differ for PV, storage, main-panel upgrades, and main-breaker derates.
- SolarAPP+ approval may still require a separate submission and payment to the local authority.
- Utility interconnection remains a separate approval path.
Are there really SolarAPP+ states?
SolarAPP+ participation is usually local, even when a state appears in the location table. The table shows where at least one listed pathway exists. It does not establish statewide address coverage, identical features, or automatic local permit issuance. The responsible AHJ still controls the final route.
SolarAPP+ is an automated code-compliance review platform for eligible residential systems. Our SolarAPP+ glossary definition explains the basic platform. This article addresses the harder operational question: where can a specific project actually use it?
The distinction starts with the authority having jurisdiction, or AHJ. An AHJ is the agency enforcing the applicable building and electrical requirements. It may be a city, county, or another authorized body.
State laws and state agencies can shape the process. However, the address and local workflow still control the permit route. Colorado adds another variation because many table rows describe state electrical approval plus a separate building permit.
Use these terms precisely:
| Term | What it proves | What it does not prove |
|---|---|---|
| State appears in table | At least one official row uses that state abbreviation | Statewide SolarAPP+ coverage |
| Jurisdiction appears | A pathway is listed for that named location | Every address or feature qualifies |
| Application passes SolarAPP+ | The entered project passed the platform review | The AHJ permit is issued in every workflow |
| Local permit is issued | The AHJ completed its required permit action | Utility interconnection is approved |
| Utility approval is complete | The utility completed its applicable review | Building or electrical inspections are complete |
This vocabulary prevents a common schedule error. “Approved in SolarAPP+” and “permit issued” can be two different milestones.
Which states appear in the current official SolarAPP+ table?
The September 26, 2026 snapshot covered 18 state abbreviations. They were Arkansas, Arizona, California, Colorado, Connecticut, Florida, Iowa, Illinois, Louisiana, Maryland, Minnesota, Ohio, Oklahoma, Tennessee, Texas, Virginia, Washington, and Wisconsin. Counts below describe official table rows, not statewide participation. Coverage remains local within each state.
The official SolarAPP+ location CSV returned 474 rows. Download the source file for the underlying entries. Its HTTP metadata showed a March 23, 2026 modification date. Feature fields and qualifiers varied by row.
| State | Official rows | Coverage warning | Verification action |
|---|---|---|---|
| Arkansas | 1 | One row does not imply statewide coverage | Check the project address in the signed-in jurisdiction tab |
| Arizona | 7 | City workflows and supported features differ | Open the named city instructions before quoting a permit date |
| California | 289 | Three rows were marked Closed Pilot | Confirm the jurisdiction and current pilot status |
| Colorado | 137 | 131 rows described state electrical approval plus a separate building permit | Identify both electrical and building permit paths |
| Connecticut | 2 | Limited table presence | Verify the address and required local handoff |
| Florida | 1 | One listed row | Treat all other locations as unverified |
| Iowa | 1 | One listed row | Confirm address and product support |
| Illinois | 1 | One listed row | Confirm address and product support |
| Louisiana | 1 | One listed row | Confirm address and product support |
| Maryland | 7 | Several local rows, not a statewide finding | Check the exact county or city |
| Minnesota | 14 | Local participation varies | Check the exact jurisdiction and features |
| Ohio | 1 | One listed row | Confirm address and product support |
| Oklahoma | 1 | One listed row | Confirm address and product support |
| Tennessee | 1 | One listed row | Confirm address and product support |
| Texas | 4 | City pathways differ | Read the local portal and contractor rules |
| Virginia | 4 | Limited local table presence | Check the named locality |
| Washington | 1 | One listed row | Confirm address and product support |
| Wisconsin | 1 | One listed row | Confirm address and product support |
The table has two unusually large groups. California accounts for 289 rows. Colorado accounts for 137, but most Colorado rows carry a state-electrical qualifier.
Neither number should become a marketing claim about complete coverage. Three California entries were marked Closed Pilot. The table also included feature combinations that were not identical across rows.
Los Angeles illustrates the freshness risk. The current CSV did not contain a Los Angeles row at the research cutoff. That finding conflicts with older assumptions on the web and in legacy content. Verify the current official system before using any local LADBS SolarAPP+ instructions.
How should you read the official coverage table?
Read each location row as a dated lead for further verification. Do not total rows into an adoption claim without reviewing duplicates, pilot labels, state-level qualifiers, and feature fields. A row count measures table entries, not active full-service AHJs.
The table is useful because it narrows the search. It is risky when copied into sales copy without its qualifiers.
Use this four-part reading method:
- Read the jurisdiction name. Confirm whether it names a city, county, state office, or another entity.
- Read the subtitle. Look for pilot, closed, state-electrical, or separate-building-permit language.
- Read every feature field. Do not infer PV support from a storage field, or MPU support from a PV field.
- Open the linked location page. Compare its local instructions with the signed-in project lookup.
Do not add California and Colorado rows together and publish a national adoption percentage. The denominator would need a defined universe of eligible AHJs. The current table does not provide that denominator.
Avoid calling all 474 rows “active jurisdictions” for the same reason. Three rows carried a Closed Pilot label. Many Colorado rows described only the state electrical portion of a two-part permit path.
A careful coverage note should preserve four facts:
| Coverage fact | Safe wording |
|---|---|
| Observation date | ”The official table was checked on September 26, 2026.” |
| Row count | ”The download contained 474 location rows.” |
| State presence | ”Rows used 18 state abbreviations.” |
| Limitation | ”Rows do not prove statewide or full-featured availability.” |
That wording remains useful when quoted outside this page. It does not turn a location index into a broader claim.
Why does a state row not guarantee instant permitting?
A state row fails as a guarantee because four layers can change the result. The listed jurisdiction may not cover the address. The needed feature may be unavailable. The system may fail eligibility. The local agency may still require its own portal, fee, or permit action.
Consider what a permit coordinator needs to know before scheduling an installation:
- Which AHJ owns the project address?
- Does that AHJ currently appear in SolarAPP+?
- Does its row support the requested PV or storage scope?
- Does the project fit the national eligibility rules?
- Does the AHJ impose narrower local limits?
- What local filing, fee, or registration step follows the automated review?
- Which utility interconnection steps remain outside permitting?
A state-level label answers none of those questions by itself.
The US Department of Energy describes SolarAPP+ as an automated code review for eligible applications. Its SolarAPP+ overview, modified May 15, 2026, says more complex applications route to manual review. The same page says local permitting agencies can use the platform without charge.
The word “instant” therefore describes the platform review for an eligible submission. It does not erase every local administrative step. It also does not cover utility permission to operate.
How do you verify an address in three steps?
Use three gates in sequence: address, feature, and project. Stop when a gate fails and identify the alternate permit route. Passing all three supports a SolarAPP+ submission, but the local AHJ instructions still control permit issuance. Record each result in the project file.
Gate 1: Confirm the address and responsible AHJ
Start with the actual installation address. Do not select a jurisdiction from the mailing city alone. County boundaries, incorporated areas, and special districts can change the responsible agency.
Use the signed-in SolarAPP+ jurisdiction tab for the live check. The public availability page directs installers there for address and feature details. Save the result date in the project record because coverage can change.
Then confirm the same AHJ through the local permit portal or official agency page. If the two sources conflict, stop. Ask the AHJ which route applies before submitting or promising a date.
Gate 2: Confirm the requested feature
Match the project scope to the feature columns. Photovoltaic generation, solar plus storage, main-panel upgrades, and main-breaker derates are separate capabilities. A row can support one without supporting another.
Do not reduce the scope to “solar” when the design includes a battery or service change. The unsupported component can move the entire project to manual review.
Gate 3: Confirm project and local eligibility
Run the current SolarAPP+ eligibility checklist against the design. Then apply every narrower local rule from the AHJ. A project can satisfy the national platform rules and still fail the local route.
Use this working matrix:
| Gate | Question | Evidence to save | Result if it fails |
|---|---|---|---|
| Address | Is this address inside a participating jurisdiction? | Signed-in lookup result and AHJ confirmation | Use the local alternate process |
| Feature | Does the jurisdiction support every requested feature? | Current feature listing and local instructions | Remove the unsupported scope only if the project permits it, or use manual review |
| Project | Does the system satisfy platform and local eligibility? | Eligibility output, plans, equipment data, and local checklist | Correct the project data or use manual review |
The order matters. There is little value in testing detailed equipment eligibility for an address that cannot use the pathway.
How does the three-gate check work on real project types?
The same three gates produce different routes for a PV-only house, a battery project, and a Colorado address. These hypothetical examples show the decision logic. They are training scenarios, not actual permits or acceptance records. Each route also preserves a manual fallback.
Example 1: A listed city and PV-only house
An installer receives a lead for a detached house in a city shown in the public table. The design contains rooftop PV without storage or service work.
The permit coordinator first confirms the address inside the city boundary. The signed-in lookup returns the same AHJ. Gate 1 passes.
The coordinator then checks PV support for that jurisdiction. PV is enabled for the location. Gate 2 passes.
The project still needs Gate 3. The coordinator checks building type, service rating, busbar rating, system size, mounting, applicant type, and local conditions. If every item passes, the team can prepare the SolarAPP+ submission.
The team cannot yet call the city permit issued. It must complete the local handoff published by that AHJ.
Example 2: PV and storage in a PV-only pathway
Another house sits inside a participating jurisdiction. The design includes PV and a battery. The address passes Gate 1.
The live feature check shows PV support but no storage support. Gate 2 fails for the submitted scope. A national battery capacity limit does not change that result.
The team now has two possible actions. It can use the local manual path for the combined system. It can also ask whether separate submissions are allowed, but only the AHJ can confirm that route.
The team should not remove the battery from permit documents while keeping it in the installation scope. The drawings, application, contract, and installed system must remain consistent.
Example 3: A Colorado state-electrical row
A Colorado address appears under a row labeled for state-level electrical approval plus a separate building permit. Gate 1 does not prove one combined permit.
The coordinator identifies the electrical pathway and the building authority. It then records each portal, fee, required document, and inspection path.
Gate 2 covers the requested SolarAPP+ feature under the electrical route. Gate 3 tests the project. The separate building review remains open until its own authority completes the applicable action.
The schedule therefore has at least two agency paths. Calling the project “instantly permitted” after one approval would hide the unfinished building step.
Example 4: A listed city with a local exclusion
A project address is inside a participating city, and the feature appears supported. The local page excludes the project condition, such as a defined wind region or service change.
Gate 1 passes. The general feature check may also pass. Gate 3 fails because the local rule is narrower than the platform baseline.
The project moves to the local alternate route. The failed gate and official source should remain in the job record. That record protects later teams from repeating the same assumption.
These examples show why the gates are sequential but not interchangeable. Address coverage cannot cure a feature gap. National eligibility cannot override a narrower local rule.
Which residential systems can use SolarAPP+?
The current national eligibility page covers defined residential building types and electrical limits. Eligible projects can include detached one-family or two-family dwellings, qualifying townhomes, and certain accessory structures. Local AHJs can impose narrower requirements. The live checklist remains the project control.
The official SolarAPP+ eligibility page, accessed September 26, 2026, lists these platform boundaries:
- Detached one-family and two-family dwellings can qualify.
- Townhomes can qualify up to three stories with separate egress and individual utility production metering.
- Eligible accessory structures and accessory dwelling units can qualify up to three stories.
- Service ratings must be 400 A or less.
- Service disconnects and busbars must be 225 A or less.
- Systems can qualify up to 38.4 kW when the stated installation conditions apply.
- Each battery is limited to 20 kWh.
- Aggregate energy storage can reach 80 kWh, depending on battery location.
These values describe the current national platform scope. They do not override a city rule, adopted code, product listing, or site condition.
Older articles may cite a 25 kW ceiling. Do not copy that value into a current checklist. The official eligibility page at this research cutoff showed a 38.4 kW limit with conditions.
The eligibility result also depends on accurate inputs. Module, inverter, battery, service, busbar, mounting, and building data must agree with the permit drawings. A passed form cannot fix a conflicting plan set.
Our solar permit package submission checklist explains the wider document set. The SolarAPP+ result is one part of that record.
Which projects still need manual review?
The current platform scope excludes homeowner-installed, ground-mounted, multifamily, commercial, community-scale, utility-scale, and ballasted systems. These projects need another review path unless the governing agency publishes a separate applicable process. Local rules can exclude other project conditions.
The exclusion list matters because “residential” can hide several different building and applicant types. A system on a multifamily building does not become eligible because its capacity resembles a house. A homeowner submission does not become eligible because the equipment would pass an installer submission.
Common manual-review triggers include the following conditions.
- The address is outside a participating jurisdiction.
- The applicant type falls outside the platform scope.
- The building type is excluded.
- The array uses a ground mount or ballasted system.
- The electrical ratings exceed the current limits.
- The battery capacity or location falls outside the stated conditions.
- The requested feature is disabled for that jurisdiction.
- The local AHJ applies a narrower condition.
- Project data fails an automated check.
- The application contains a condition requiring staff judgment.
Manual review is not a failed project. It is a different permit route. Build both routes into operations so a non-eligible result does not halt the job.
The solar permit expediting guide covers decisions after a project needs a conventional review path. It also separates document preparation from agency control.
How do PV, storage, MPU, and MBD features vary?
SolarAPP+ feature support varies by jurisdiction. A listed location may support photovoltaic systems but exclude storage. Another may accept storage while limiting main-panel upgrades or main-breaker derates. Confirm every project component before selecting the automated route. The live jurisdiction record controls the choice.
PV means photovoltaic generation. Storage refers to an energy storage system paired with PV or submitted alone. A main-panel upgrade, or MPU, replaces or changes the service equipment. A main-breaker derate, or MBD, lowers the main breaker rating for the proposed interconnection arrangement.
Treat each feature as its own yes or no field:
| Project scope | Question for the live lookup | Drawing consequence |
|---|---|---|
| PV only | Does this jurisdiction accept the proposed PV pathway? | Match array, inverter, service, and connection data |
| PV plus storage | Are both PV and storage supported for this address? | Add battery location, capacity, listing, and required protection details |
| Storage only | Does the jurisdiction accept a storage-only application? | Do not assume a PV pathway covers it |
| Main-panel upgrade | Is MPU enabled under the local SolarAPP+ route? | Coordinate service equipment and local utility requirements |
| Main-breaker derate | Is MBD enabled for this jurisdiction and design? | Keep breaker ratings consistent across forms and drawings |
This check should happen before detailed drafting. A late feature mismatch can force new forms, different sheets, or a different submission portal.
Storage deserves its own document check. The solar and battery plan-set requirements explain the additional information a storage scope can require. SolarAPP+ availability does not remove those design obligations.
What does instant permit mean in Tucson, Phoenix, and Houston?
Tucson, Phoenix, and Houston show why one national promise fails. Each city uses SolarAPP+ within a local process. Applicants still interact with city systems, and each city publishes different limits, handoffs, or contractor requirements. The examples are not national templates.
| City | SolarAPP+ role | Local handoff | Important local limit |
|---|---|---|---|
| Tucson | Automated approval for eligible roof-mounted residential work | Submit through the Tucson portal for city permit issuance | Local criteria still apply, and published fee pages conflict |
| Phoenix | Accepts approved residential PV designs | Submit the checklist, diagram, and plot plan through Phoenix | Local pathway excludes batteries, ground mounts, MPU, and MBD |
| Houston | Uses SolarAPP+ in a city permit path | Upload confirmation through iPermits | Registered licensed contractors only, with a wind-speed exclusion |
Tucson uses a second city step
The City of Tucson residential solar page says an eligible roof-mounted project can use SolarAPP+. The installer must still submit through the Tucson portal. The city states that it issues the permit within 24 hours after that step.
Projects outside Tucson criteria use the traditional process. SolarAPP+ approval alone is not the final city permit.
Phoenix limits the local pathway
The City of Phoenix SolarAPP photovoltaic page accepts approved residential PV designs. The applicant still submits through the Phoenix permit portal.
Phoenix requires the checklist, diagram, and plot plan to agree. Its published local pathway excludes batteries, ground mounts, ballasted systems, main-panel upgrades, and main-breaker derates. A separate Phoenix Fire Department permit can apply to PV and storage work.
Houston adds contractor and wind conditions
The Houston Permitting Center announcement states that the city launched its SolarAPP+ path on July 15, 2024. Only registered licensed contractors can use it. Applicants upload the SolarAPP+ confirmation through Houston iPermits.
Houston excludes locations with a basic wind speed of 140 mph or higher from its SolarAPP+ pathway. That city-specific rule shows why national platform eligibility is not enough.
How much does SolarAPP+ cost?
The current SolarAPP+ fee page displays $35 for a solar permit application, $30 for add-on storage, and $30 for storage only. AHJ permit fees and payment-processing fees remain separate. Verify the amount in the live checkout because official pages currently conflict.
The SolarAPP+ installer fee page, accessed September 26, 2026, also says the first three revisions are free. Later revisions may trigger another application fee.
A separate SolarAPP+ fee workflow page confirms that platform fees do not replace AHJ fees. The payment sequence varies between standalone and integrated government technology workflows.
Tucson creates a live conflict. Its city page lists $35 for PV and $25 for PV plus storage. The current SolarAPP+ page lists $30 for add-on storage.
Do not resolve that $5 difference by guessing which page wins. Save the live checkout amount and the AHJ fee receipt in the project record.
Use four fee fields in estimating:
| Fee field | Owner | When to confirm |
|---|---|---|
| SolarAPP+ application | Platform checkout | Before application payment |
| Payment processing | Payment provider or platform | At checkout |
| AHJ permit | Local agency | Before customer price confirmation |
| Revision or resubmission | Platform and local agency | When the scope or review cycle changes |
This structure prevents the platform fee from being quoted as the total permit cost.
How does California law differ from SolarAPP+ adoption?
California law requires covered jurisdictions to implement an online automated permitting platform for eligible systems. The law allows a platform such as SolarAPP+, but it does not require every jurisdiction to use SolarAPP+ specifically. Statutory exemptions also exist. Address-level confirmation remains necessary.
California Government Code section 65850.52 is the governing source. The current statutory text, accessed September 26, 2026, displayed an amendment effective January 1, 2024.
The law addresses covered jurisdictions and eligible residential systems. It includes a 38.4 kW AC ceiling for the applicable category. Small-jurisdiction exemptions and other conditions remain part of the statute.
Three conclusions follow:
- Automated permitting in California is broader than SolarAPP+ branding.
- A legal duty to offer an automated platform does not prove one address appears in SolarAPP+.
- An automated permit does not replace utility interconnection approval.
Use the California AHJ solar permit guide for wider state and local permit context. Use the live SolarAPP+ lookup for the platform decision.
Does SolarAPP+ actually reduce permit time?
Historical NREL research found faster outcomes in its studied 2022 cohort. The result supports the platform concept, not a current promise for every jurisdiction. Local process design, project eligibility, and follow-on permit steps can change the schedule. Use local data for current forecasting.
The 2023 NREL second-year performance review examined 206 installers and 11,092 submitted permits during 2022. The official report says 708 were solar-plus-storage pilot submissions.
The report found that the median SolarAPP+ project was permitted and inspected 13 business days faster. It estimated about 9,900 AHJ staff hours saved during 2022. It also reported an inspection failure rate about 29 percent lower.
Those figures need their cohort label. The report warns that the studied AHJs may not represent other AHJs. It also does not establish current adoption or a guaranteed project timeline.
For scheduling, measure your own jurisdiction outcomes.
- Record the SolarAPP+ review completion date.
- Record the local portal submission date.
- Record the local permit issue date.
- Track the correction count and cause.
- Track inspection request and completion dates.
- Track utility interconnection milestones.
That breakdown reveals where time is actually spent. It also prevents an instant platform review from hiding a slower local handoff.
How should multi-state installers track coverage changes?
Build a dated jurisdiction register around addresses and features, not state labels. Recheck volatile fields before each submission. Preserve the source, access date, and local instruction link so operations can explain each routing decision later. One source date should follow every decision.
A useful register contains these fields:
| Field | Why it belongs in the register |
|---|---|
| Project address | Defines the actual coverage question |
| Responsible AHJ | Prevents mailing-city assumptions |
| Lookup date | Shows when the decision was valid |
| SolarAPP+ status | Records participating, unavailable, or uncertain |
| Supported features | Separates PV, storage, MPU, and MBD |
| Local portal | Captures the required handoff |
| Applicant restriction | Records contractor, license, or registration conditions |
| Platform fee | Preserves the checkout amount |
| AHJ fee | Keeps local charges separate |
| Manual fallback | Prevents an ineligible result from stopping the job |
| Reviewer initials | Creates accountability for the decision |
Recheck the table monthly for active sales territories. Recheck again before submission. A monthly snapshot supports planning, while the project-date check supports filing.
Add a coverage-change trigger to permit operations. A changed location row should prompt three questions:
- Which open projects use that jurisdiction?
- Which proposals contain a schedule assumption tied to that pathway?
- Which standard plan notes or intake forms need revision?
The register should never promise acceptance. It records the best current route based on official sources.
What should the permit package contain after eligibility passes?
A passed SolarAPP+ eligibility check starts document coordination. The form data, generated approval documents, drawings, equipment records, and local portal submission must describe the same project. A mismatch can still create a correction or rejection. Reconcile those records before upload.
Use this pre-submission control:
- Freeze the module, inverter, battery, and service-equipment selections.
- Match quantities and ratings across SolarAPP+, drawings, and equipment data.
- Confirm the site address and AHJ on every applicable document.
- Include the generated SolarAPP+ output required by the local workflow.
- Add every local checklist, plot plan, or agency form.
- Confirm permit fees and payment ownership.
- Keep utility interconnection documents in their separate workflow.
- Run a final sheet and attachment reconciliation.
The AHJ plan-set rejection guide explains document defects that automated eligibility does not eliminate. A clean SolarAPP+ result cannot reconcile inconsistent equipment data for the designer.
What can sales teams promise before the permit check?
Sales teams can promise a verification step, not an instant outcome. Say that the permit team will check address, feature, and project eligibility. Do not promise SolarAPP+ availability, local issuance, or a fixed permit date before that work is complete.
Replace broad language with project-controlled language:
| Risky statement | Safer operational statement |
|---|---|
| ”SolarAPP+ works statewide." | "We will verify the current pathway for your project address." |
| "Your permit is instant." | "Eligible applications can receive automated platform review, followed by required local steps." |
| "The system qualifies." | "The permit team will test the final equipment and site data against current rules." |
| "The fee is $35." | "We will confirm platform, processing, and AHJ fees before payment." |
| "SolarAPP+ covers the battery." | "We will confirm storage support for this jurisdiction and design.” |
The handoff from sales should contain the address, building type, applicant type, equipment scope, service rating, and storage details. Missing scope forces operations to repeat discovery after the schedule is discussed.
Add one field to the proposal record: Permit route status. Use controlled values such as unverified, SolarAPP+ candidate, manual route, and AHJ confirmed.
Only the permit team should move the status to AHJ confirmed. The supporting source and check date should sit beside that status.
When should an installer use a design partner?
Use a design partner when internal capacity or jurisdiction variation creates document risk. The partner should verify the permit route, coordinate project data, and prepare the required drawings. The AHJ still decides eligibility and acceptance. The partner cannot authorize the permit route.
Heaven Designs provides solar permit design support for installers managing residential and commercial work. Scope can include plan-set preparation and correction coordination. Project-specific authority requirements still control the final submission.
Ask a prospective partner four questions:
- Which source confirms the permit pathway for this address?
- How are unsupported SolarAPP+ features identified before drafting?
- How are form inputs reconciled with the final drawings?
- Who owns corrections when local instructions change?
Good answers refer to current project records. They do not rely on a permanent state list or guaranteed approval claim.
If you want us to review a project scope and required drawing package, contact the Heaven Designs team. Include the address, AHJ, system size, storage scope, and any service-equipment changes.
Frequently asked questions
Is SolarAPP+ available statewide in California?
No. California law requires covered jurisdictions to offer an online automated platform for eligible systems, subject to statutory conditions. It does not require every jurisdiction to use SolarAPP+ specifically. Confirm the project address and current local platform before filing.
Does SolarAPP+ approval mean the permit is issued?
Not always. Tucson, Phoenix, and Houston each require a local portal handoff after the SolarAPP+ step. The generated approval supports that local process, but the city still completes its required permit action.
Can a battery project use SolarAPP+?
Some battery projects can qualify. The national platform lists capacity and location conditions, while each jurisdiction controls supported features. Check storage support for the address before assuming a PV pathway covers the battery.
Can commercial solar use SolarAPP+?
The current national eligibility page places commercial systems outside the platform scope. Use the governing AHJ process for the project. Do not treat a similar system capacity as proof of residential eligibility.
Does SolarAPP+ replace utility interconnection?
No. SolarAPP+ addresses permit code review for eligible systems. The serving utility controls its interconnection review, agreements, metering steps, and permission to operate.
How often should an installer recheck coverage?
Review active-territory coverage monthly and verify each address again before submission. Also recheck after an AHJ announcement, platform update, product change, or failed eligibility result.
Final operating rule
Treat SolarAPP+ as a project-level permit route, not a state badge. The useful decision is specific: this address, this feature set, this system, and this AHJ process qualify today.
Record the evidence behind that decision. Keep a manual fallback ready. Then make the schedule promise only after the local handoff is understood.