Grid interconnection · Applicant side

Your application waits years. Don't let a preventable error add more.

Conkt verifies large-load interconnection applications against real utility, NEC, and IEEE standards — before they reach the utility. We catch the deficiencies that trigger multi-year restudy cycles.

No pitch — a 20-minute conversation to understand how this works on your side.

Interconnection Verification Report Reviewed by J. Alvarez, P.E.
8Findings
3Fail
2Needs review
~5–6 moRestudy avoided
FAIL

Transformer impedance on Sheet E-3 (6.75%) does not match the fault current calculation on Sheet E-7 (7.2%).

NEC 705.12(B)(2)(3)(a)
REVIEW

Protective relay coordination study not included for the proposed interconnection point.

IEEE 1547-2018 §6.5.1
PASS

Point-of-interconnection coordinates match the application form.

Utility Interconnection Manual §2.1

The queue is long enough already

Every deficiency notice sends your application back to the end of a process measured in years, not weeks.

~2,600 GW

U.S. grid interconnection backlog as of 2026 — capacity waiting in queue.

~8 years

Average time projects spent in the PJM interconnection queue before reaching commercial operation.

$650B+

2026 hyperscaler infrastructure capex that depends on getting large loads connected.

Built for the applicant, not the utility

Most interconnection tooling is built to help utilities process the queue. Conkt works on your side of the submission.

Utility-side tools

Screen applications after they arrive

Existing automation helps grid operators triage and study the applications already sitting in their queue. Useful — but it happens after your submission is already in, and after a deficiency has already cost you time.

Conkt

Verifies your package before you submit

We check your application against your utility's technical requirements, the NEC, and IEEE 1547 while you can still fix what's wrong — turning a months-long restudy cycle into an afternoon of corrections.

How the verification works

A real reasoning pipeline — not a checklist, and not an unreviewed AI guess.

1 · Intent

You describe the project — utility, load, voltage class, point of interconnection.

2 · Requirements

We extract structured requirements from your one-lines, load data, and equipment specs.

3 · Constraints

Those requirements are checked against the standards that actually apply to your project.

4 · Verification

You get cited findings — Pass, Fail, Needs Review, or Unknown — each traceable to a specific standard.

Every finding is reviewed by a qualified engineer before you see it. Our findings are a decision-support input for your team's review — not a certification, and Conkt is not the engineer of record on your submission.

Who we work with

Teams preparing large-load interconnection applications where a restudy cycle is measured in quarters.

Large-load developers

  • Data center and industrial facility developers
  • Projects where interconnection timing gates the entire build schedule
  • Teams navigating new state large-load tariff requirements
  • Multi-region portfolios facing different utility standards

Electrical & substation EPC firms

  • Firms preparing application packages on behalf of clients
  • Teams reviewing one-lines, load data, and equipment specs at volume
  • Engineers who've seen a deficiency notice cost a client months
  • Groups standardizing review quality across projects

Tell us how this works on your side

We're working with a small number of lighthouse partners. No pitch — a 20-minute conversation to understand where your applications actually run into friction.

Thanks — we'll be in touch within one business day.

We'll never share your project details. Conversations are confidential.