Quick answer
Solar interconnection follow-up is effective when the developer distinguishes utility-controlled review stages from internal tasks it can actually complete. A scheduled call can reveal an outstanding document or missing response; it cannot approve grid connection or issue utility permission to operate.
A solar project may have its modules installed and inspections underway while grid connection is still pending. The unanswered question is rarely “Why has the utility not approved us?” It is often “Which step is actually waiting on the utility, and which step is waiting on our own team?”
A disciplined solar interconnection follow-up workflow separates those responsibilities. It helps project managers avoid chasing the wrong person, missing a request for more information, or reporting permission to operate before the utility has formally granted it.
Understand what interconnection does—and does not—mean
Interconnection concerns the requirements for connecting generation equipment to the electrical grid. In many distributed PV projects, the serving utility evaluates the application, technical information and associated approvals before granting permission to operate. The exact steps differ substantially by utility, project capacity and jurisdiction.
The U.S. Department of Energy’s solar energy guidance explains that grid-connected systems need a relevant interconnection agreement, with utility requirements that can include inspections. For other scales, the process may involve technical studies, network upgrades, agreements and system-operator requirements. Never assume that a passed municipal inspection by itself permits energisation.
Keep the labels explicit: application lodged, utility information request, customer response submitted, utility review in progress, agreement executed, meter or protection work pending, official PTO issued. These are illustrative stage names; the utility’s actual workflow is the authority.
Make a dependency register rather than an “awaiting utility” bucket
Use a separate task for every action your team controls: a corrected single-line diagram, inverter specifications, signed interconnection documents, proof of inspection, meter access arrangements or a requested technical response. Capture the exact official utility request, accountable owner, target internal response date and evidence sent.
Another set of tasks belongs to the utility or regulator. Their official statuses should be recorded from the relevant portal, letter or named authorised representative, without automatic inference. Link the two sets: a utility review cannot progress when its requested document remains with the EPC team, while the EPC team may have nothing further to do once a complete response is submitted.
For example, if a commercial rooftop project is awaiting a protection-setting clarification from its engineer, “awaiting utility” is misleading. The current blocker is the engineering response. A short owner check-in is more useful than repeated calls asking the utility for progress.
Schedule calls according to the next decision deadline
Group follow-ups into three categories. First, internal response calls ask engineers, installers or administrators whether assigned information is ready to submit. Second, submission confirmation checks ask the internal coordinator whether the material has actually been transmitted through the required channel. Third, official status reviews are performed by the authorised person using the utility’s procedures.
Set call dates from the project’s legitimate milestones and stated utility response deadlines. Do not claim there is one universal number of days for permission to operate. On a hypothetical Monday management review, the project lead may ask for an engineering update on Tuesday, verify the amended packet on Wednesday and await the utility’s formal acknowledgement thereafter.
Automated outreach to utility personnel may be unsuitable or restricted; the team should use designated contact methods. Routine AI calls are best directed toward properly informed internal and contractor task owners.
Ask for evidence and next action—not a guess about approval
An effective internal check-in asks: “Which interconnection request are you handling?”, “What specifically did the utility ask for?”, “Is the response prepared or actually submitted?”, “Where is the acknowledgement or reference?”, and “What action, if any, is outstanding on our side?” If the respondent can only estimate the utility’s decision date, record it as an estimate.
Consider an illustrative utility request for inverter documentation. The installer says the specification sheet is complete but the permit coordinator has not uploaded it. The correct project update is “document ready; submission outstanding; coordinator assigned.” Marking the issue “utility pending” would hide the next actionable task.
Another important question is whether the latest project design still matches the approved application. Material design changes must be assessed and submitted through the appropriate professional and utility procedures; a conversational agent should not alter electrical specifications or approve a deviation.
Connect your status calls to the board carefully
A proposed monday.com interconnection register can contain Project ID, Utility, Application reference, Required document, Internal task owner, Submitted-at date, Last official utility status, Next action, Estimated target date and PTO evidence. Add a clear distinction between “reported by team” and “verified from utility.” Limit edit rights for utility status and PTO to the people authorised to verify the official record.
The Autoza AI monday.com offering describes scheduled outbound calls, item updates, smart retries and summaries. It can potentially form part of the internal follow-up process after the team checks supported mappings and scripts; it does not provide an asserted direct utility portal integration or automatic PTO approval.
The proposed question set can be trialled on one workstream, with the project manager checking every AI-captured answer against source documents until the process is dependable. For more general sequencing ideas, monday.com’s project dependency guide explains the value of linking predecessor work and milestones.
Escalate connection risks to qualified humans
Utility protection, electrical testing, network upgrades and energisation all require the applicable authorised processes and qualified professionals. OSHA’s guidance on solar electrical hazards reinforces that electric-shock and arc-flash risks need formal controls, not informal assurances obtained by phone.
Set escalation triggers for an unexpected study requirement, conflicting approval information, an expired agreement, a design revision, missing inspection evidence or approaching contractual deadlines. The appropriate electrical engineer, project manager or authorised utility liaison decides the next step.
Do not energise equipment, instruct a crew to connect, or tell a customer they have PTO based on a call transcript. The team must verify the formal utility communication. If a person misses a scheduled internal call, log “unreachable”, retry within agreed limits and route critical items to the assigned manager.
Report useful progress to developers and customers
A strong weekly update differentiates “our outstanding actions” from “external review awaiting response” and “formal clearance received.” Include the last official status date, the next planned check, the name or role of the accountable owner, and any schedule implications under human review.
Do not promise that AI calling will accelerate utility processing. It may improve the timeliness and completeness of the developer’s own responses, but grid reviews and the issuance of PTO remain external decisions. Measure overdue internal information requests, time to submit corrections, status accuracy, and unresolved dependencies over several projects.
For a complete project picture, connect this register to the team’s solar permitting and field installation tasks, while keeping authority decisions separate from operational progress notes.
Operational checklist for this workflow
- Separate utility-owned stages from outstanding internal responses.
- Check whether requested documents are ready, submitted and acknowledged.
- Confirm official utility status from its stated source.
- Treat PTO and energisation as controlled human/utility decisions.
- Escalate study, design, safety or deadline changes without guesswork.
Frequently asked questions
What causes common solar interconnection follow-up delays?
Delays can involve incomplete or revised documentation, technical studies, equipment or meter arrangements, utility review backlogs, inspection evidence or internal response handoffs. The applicable causes depend on project and utility.
Can a solar AI check-in agent contact the utility and grant PTO?
No. The utility issues permission to operate under its formal process. Any utility enquiries should follow designated channels and appropriately authorised staff.
What should a PV connection approval checklist include?
Track application identifiers, outstanding technical requests, responsible internal owners, document submission acknowledgements, official utility stages, inspection evidence where required and formal PTO confirmation.
How do we distinguish a submitted response from an approved response?
Use separate fields for date and evidence of submission, official receipt or acknowledgement, current external review stage and any final decision. Never infer acceptance solely from the passage of time.
Can monday.com automate project follow-up while interconnection is pending?
Scheduled calls can collect updates from internal task owners and record progress in authorised fields using a configured workflow. Official utility decisions and technical approvals remain outside the caller’s authority.
Next step: test a focused workflow
Want more visibility into outstanding solar interconnection tasks? Explore Autoza AI and request a workflow discussion focused on internal owner updates and documented escalations.
Related reading
- Daily Solar Installation Crew Check-Ins: What Should Managers Ask?
- Solar Permitting and Inspection Follow-Up: A Project Manager Checklist
- Construction Daily Progress Updates: A Better Way to Hear From Field Crews
- Pre-Inspection Follow-Up: Which Construction Tasks Need a Phone Call?
- Autoza AI for monday.com: scheduled status calls
- Workflow automation services
- Daily Check-in Agent