Map utility programs and effective application requirements.
Permitting and PTO / Utility interconnection
Solar utility interconnection workflow
Give interconnection work its own governed record and deficiency loop instead of hiding it inside a generic project status.
Record
01Utility
02Utility program
03Interconnection application
04Deficiency
Current reviewIdentify the utility program
Configured during assessment- 01Identify the utility programCurrent decision
- 02Review application requirementsNext controlled handoff
- 03Prepare and submit the packageNext controlled handoff
- 04Resolve deficiencies and conditionsNext controlled handoff
Why this workflow breaks
Utility programs differ in required forms, technical details, review steps, meter actions, and construction dependencies. A single status field cannot explain what was submitted, what is deficient, or what work can proceed.
Solar1 starts by documenting the decisions and failure paths. Configuration follows only after the operating boundary is understood.
Workflow sequence
Keep the handoff visible from first review to accepted outcome.
- 01Identify the utility program
- 02Review application requirements
- 03Prepare and submit the package
- 04Resolve deficiencies and conditions
- 05Record construction and meter decisions
What to configure
Specific controls, qualified by implementation.
Configure submission packages, evidence, acknowledgments, and deficiency responses.
Record approval-to-construct, meter, inspection, and activation dependencies separately.
Route open utility actions to a named owner with source correspondence.
Assessment output
A shared definition of the records, owners, and acceptance checks.
Records in scope
- Utility
- Utility program
- Interconnection application
- Deficiency
- Meter action
Roles in the decision
- Interconnection coordinator
- Project manager
- Electrical reviewer
Checks before rollout
- Catalog active utilities and program variants.
- Define proof for submission and deficiency closure.
- Separate approval-to-construct from final activation.
Questions to settle
Questions to settle before configuring utility interconnection.
Is interconnection the same as permitting?+
No. They may share documents and dependencies, but the authority, requirements, decisions, and evidence should remain identifiable.
Can one utility have several programs?+
Yes. Program, system, tariff, and market differences can be modeled after the current requirements and ownership are confirmed.
How are utility deficiencies tracked?+
Each deficiency can retain its source, owner, requested response, submitted evidence, status, and relationship to the application.
Next step