Every permit, every jurisdiction — tracked in one place.
Map jurisdiction requirements, permit status, corrections, inspections, interconnection, and PTO ownership around the same project record.
Currently onboarding a first group of early-access installers.
Built for the permit — not a free-text status field.
A useful permit workflow needs more than a status field. It needs requirement sources, owners, documents, review windows, corrections, and project dependencies.
Identify the jurisdiction requirements, source records, forms, and review details your permit team needs for each project.
Define statuses, owners, correction loops, documents, and follow-up rules before configuring a shared queue.
Map building permit and utility interconnection records separately while preserving their relationship to the same project.
Every active permit, across every project, in one queue
Assess the submission dates, statuses, owners, review windows, and correction records your coordinators need, then configure the shared queue around that process.
See how it comparesLook up a jurisdiction's rules — don't rebuild them from memory
Define the source and update process for setbacks, equipment constraints, utility forms, and other jurisdiction context before relying on it in a permit packet.
Compare AHJ coverageThe two workflows a solar permit actually runs
Map the building permit and utility interconnection as separate workflows tied to one project, with explicit owners, dependencies, and acceptance checks.
Permit workflow areas to settle before configuration.
Permit rollout
Carry each requirement into the right implementation phase.
Assessment, configuration, validation, and ongoing operation each answer a different part of the permit workflow.
| Capability | Assess | Configure | Validate | Operate |
|---|---|---|---|---|
| Jurisdiction sources and requirement ownership | Included | Partial | Partial | Included |
| Permit statuses, owners, and review windows | Included | Included | Included | Included |
| Correction and resubmission process | Included | Included | Included | Included |
| Interconnection and PTO milestones | Included | Included | Included | Included |
| Packet documents and version history | Included | Included | Included | Partial |
| Billing or scheduling dependencies | Included | Partial | Included | Partial |
Included means the topic is a primary focus in that phase. Partial means it may be revisited as the rollout develops.
Common questions
Solar permitting — answered directly.
How does Solar1 look up AHJ requirements?
The workflow assessment identifies the jurisdiction sources, fields, forms, and review details your team relies on. The available data source and update process for your rollout are confirmed before configuration.
Can Solar1 track permit status across multiple active projects?
A configured permit queue can be scoped around submission date, status, owner, review window, open actions, and correction records. The exact fields and notifications are agreed during assessment and validated before wider use.
Does Solar1 handle both the building permit and the utility interconnection?
The assessment treats the building permit and utility interconnection as distinct workflows related to the same project. Their stages, owners, dependencies, and any billing or scheduling effects are configured to the agreed process.
What causes solar permit rejections, and how does Solar1 help?
Common correction causes vary by jurisdiction and project. During assessment, document versions, requirement checks, equipment records, review ownership, and the correction process can be mapped so the configured workflow reflects how your permit team works.
Track every permit. Stop chasing status in your inbox.
Bring the permit and interconnection process you run today. We will map the records, owners, exceptions, and configuration a rollout would require.