Manage the Permission-to-Operate (PTO) step after interconnection approval and troubleshoot common delays
domain: solar.interconnection · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm all prerequisite steps are complete before requesting PTO: interconnection agreement executed, final electrical/AHJ inspection passed, and any utility-required meter or equipment change completed
Submit the PTO request through the same utility portal used for the interconnection application (e.g., PG&E's 'Your Projects' portal), attaching the final inspection card/certificate
Track the utility's stated PTO review window and follow up proactively rather than waiting for a status change notification, since PTO queues are a common installer-reported bottleneck
If PTO is delayed, check the most common root causes first: mismatched system details between the interconnection application and as-built inspection, missing signed interconnection agreement, or an incomplete/rejected meter service order
For projects near a program deadline (e.g., legacy NEM 2.0 grandfathering, which required PTO by April 14-15, 2026 to preserve old tariff terms), track PTO timing explicitly against that deadline, since PTO date — not application date — is what typically locks in tariff eligibility
Known gotchas
Tariff/program grandfathering is usually keyed to the PTO date, not the application or inspection date — a delayed PTO can knock a customer out of a legacy incentive or rate structure they were expecting
Discrepancies between the original interconnection application and the as-built system (equipment substitutions, capacity changes) are a frequent, avoidable cause of PTO delay — reconcile these before requesting final inspection
PTO turnaround times and required documentation are utility-specific and can change; don't assume the same timeline across different IOUs or municipal utilities
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?