Interconnection Workflow

Assemble, validate, and submit interconnection packets — then track every RFI to closure.

(Coming next)

Interconnection applications take weeks to assemble and months to close. Developers chase missing documents, re-format drawings, answer RFIs across email threads, and manually track approval status. Gridline automates packet assembly, validates completeness, submits to utilities, and tracks every RFI through to final approval.

Inputs

What you provide to start an interconnection run:

Project documents — Site plans, electrical diagrams, equipment specs, photos
Application forms — Utility-specific PDFs or web forms (varies by jurisdiction)
Compliance certificates — UL listings, IEEE 1547 certs, installer licenses
Property records — Deeds, leases, easements, property tax documents
Technical studies — Load flow analysis, fault current studies (if required)
Utility templates — Pre-filled forms from utility portals (when available)

All inputs are versioned. If the utility changes requirements mid-process, you can regenerate the packet with updated templates.

Controls

The guardrails that ensure nothing gets missed:

Completeness check

Gridline validates that all required documents are present before submission. Missing documents halt the run — you can’t submit an incomplete packet.

Format validation

Each utility has format requirements (PDF page size, CAD file types, naming conventions). Gridline enforces these rules. Non-compliant files are flagged for reformatting.

Version control

When utilities issue RFIs requesting revised documents, Gridline tracks which version of each document was submitted. Old versions are archived, new versions clearly marked.

Deadline tracking

Interconnection applications have response deadlines for RFIs. Gridline surfaces upcoming deadlines and flags overdue responses.

These controls prevent the most common causes of interconnection delays: incomplete packets and missed RFI deadlines.

Pipeline

The workflow that runs from packet assembly to final approval:

1. Ingest

Upload project documents, application forms, and compliance certificates. Files are categorized by type (technical, legal, compliance).

site_plan.pdf, electrical_diagram.dwg, deed.pdf → stored + categorized

2. Extract metadata

Pull key identifiers from documents: project address, system size, inverter model, installer name. Validate that metadata is consistent across all documents.

Documents → extracted metadata → consistency check

3. Assemble packet

Populate utility-specific application forms with extracted metadata. Organize documents according to utility requirements (table of contents, section dividers, page numbering).

Forms + documents → assembled packet (PDF or zip depending on utility)

4. Validate

Run completeness check (all required docs present?) and format validation (correct file types, sizes, naming?). Flag any issues for correction.

Assembled packet → validation checks → issues flagged or approved for submission

5. Submit

Upload packet to utility portal or email to interconnection coordinator (depends on utility process). Capture submission timestamp and confirmation number.

Validated packet → submitted to utility → confirmation number logged

6. Track RFIs

Monitor utility responses. When an RFI arrives, parse the request, link it to the original packet, and surface the specific documents that need revision.

RFI received → parsed → linked to original docs → response due date flagged

7. Respond to RFIs

Upload revised documents. Gridline generates a response letter summarizing changes, attaches updated docs, and resubmits to utility.

Revised docs uploaded → response letter generated → resubmitted with version tracking

8. Close

When utility issues final approval, log the approval date and permission-to-operate (PTO) status. Archive the complete packet + all RFI correspondence.

Final approval received → PTO date logged → full packet archived

Artifacts

Every interconnection run produces 10-15 auditable outputs:

Core artifacts (always generated):

assembled_packet.pdf — The complete interconnection application packet
submission_confirmation — Timestamp + confirmation number from utility
metadata_extract.json — Structured data pulled from all input documents
validation_report — Completeness check + format validation results
table_of_contents.pdf — Auto-generated TOC with page numbers
rfi_log — Complete history of all RFIs and responses
approval_certificate — Final PTO approval from utility

Optional artifacts (depending on workflow):

rfi_response_letter.pdf — Generated for each RFI response
version_diff — Shows what changed between packet versions
deadline_calendar.ics — RFI response deadlines in calendar format
utility_correspondence — All emails and portal messages with utility
resubmission_packet.pdf — Updated packet after RFI responses
compliance_checklist — Utility-specific requirements marked complete

All artifacts are timestamped and linked to the specific interconnection application.

Demo

Interconnection workflow is under development. Request early access to see a prototype.

Request early access →

What’s different from manual interconnection

Before Gridline:

2-4 weeks assembling initial packet
Manual document checklists (easy to miss items)
RFIs tracked in email threads or spreadsheets
Hard to find which document version was submitted
Deadlines missed due to lack of visibility
No systematic way to handle resubmissions

With Gridline:

Packet assembled in hours (automated form population)
Automated completeness validation (can’t submit incomplete packet)
RFIs parsed and linked to original documents automatically
Full version history with diffs between submissions
Deadline tracking with automatic reminders
Re-run workflow with updated docs, old versions archived

Why this matters

Interconnection delays are the #1 bottleneck in community solar deployment. Applications sit for months waiting for RFI responses because developers can’t find the right document or miss a deadline.

Gridline turns interconnection from a manual coordination nightmare into a tracked, auditable process. You know exactly what was submitted, what the utility asked for, and what’s due when.

Roadmap details

Phase 1 (Q1 2025): Packet assembly + validation for top 10 utilities (ConEd, National Grid, Eversource, etc.)

Phase 2 (Q2 2025): RFI parsing and response generation

Phase 3 (Q3 2025): Multi-utility support (50+ utilities covered)

Phase 4 (Q4 2025): Automated utility portal integration (where APIs available)

Interconnection is next after billing. If you want to shape this workflow based on your utility’s requirements, get in touch.