Skip to content
LOAD FACTOR
Back to Insights
Methodology

Who Is Behind That SPV? How We Trace Interconnection Queue Developers

Published May 1, 2026 • 7 min read • Load Factor team
Share this

Most interconnection queue filings do not tell you what you actually need to know.

They will tell you a queue number, a substation, a county, and a legal applicant name such as Prairie Wind Holdings LLC or Fox Squirrel Solar LLC. What they often will not tell you is whether that entity is the true developer, a project-specific SPV, a holdco, a sell-down vehicle, or simply the narrow legal wrapper used to move the interconnection request through the process.

That is why Load Factor has accumulated 200,444 evidence records across 15+ public source types. The goal is not to guess ownership from branding or make aggressive parent-company assumptions. The goal is to answer a narrower, more useful question with evidence: who is behind this queue position, and what exactly supports that conclusion?

Why SPVs dominate interconnection queues

SPVs are normal in project development. Developers use them for ring-fencing, financing, tax structuring, portfolio sales, and risk management. An interconnection request filed under an SPV name is not suspicious. It is routine.

The problem is that routine SPV usage creates an intelligence gap. An analyst screening a market, an EPC qualifying leads, or a lender underwriting a development portfolio cannot act on Fox Squirrel Solar LLC the same way they can act on a known developer platform with a track record across ISOs.

That gap widens because no single public source solves it cleanly.

  • Grid-operator queue data may show the project and the interconnection customer, but not the sponsor structure.
  • Federal filings may confirm a legal counterparty, but not the broader ownership chain.
  • State business records may show a registration, but not commercial control.
  • Plant and regulatory records may name related entities, but not on every project.
  • News coverage can be directionally useful, but it is not authoritative on its own.

The only defensible way through that mess is to assemble a chain of evidence and weigh it by source quality.

Load Factor's evidence model starts with source quality, not narrative confidence

Not all public records deserve the same weight. An official record that names the interconnection customer for a specific queue position is stronger evidence than an article that mentions a company somewhere near a project, and Load Factor weighs them accordingly.

The operating rule is simple: when two or more independent primary sources agree, Load Factor can mark a developer attribution Two sources agree. News and other context can support an attribution, but never confirm one on its own. If the evidence is partial, indirect, or mixed, the platform keeps that ambiguity visible instead of flattening it into a false certainty.

That distinction matters because "developer" can mean at least three different things in practice:

  1. The legal interconnection customer named in the filing.
  2. The project SPV that controls the queue position.
  3. The parent or sponsor platform that ultimately develops, finances, or sells the asset.

Load Factor does not collapse those layers unless the evidence supports the collapse.

A real example: AE2-148 in PJM

One useful example is PJM project AE2-148, a 397.3 MW solar project in Madison County, Ohio.

In Load Factor's current evidence snapshot, that project has:

  • 15 evidence records
  • 5 independent families of public record
  • a developer attribution two sources agree on

The current resolved record identifies the interconnection customer and best-known developer as Fox Squirrel Solar LLC. The explanation is explicit: official interconnection records from the grid operator and federal filings both name it.

Here is what the evidence chain looks like at a high level.

Step 1: anchor the project in authoritative queue records

Primary records establish that AE2-148 is the right project and that Fox Squirrel Solar LLC is the named interconnection customer. In this case they come from two families: grid-operator filings and federal regulatory filings.

Those records do two things that matter commercially. They connect the legal entity name to the actual queue number, and they remove ambiguity about whether the LLC is really associated with the project or merely mentioned nearby in a secondary source.

Step 2: add commercial context without overstating certainty

The same project also carries context from two more families: plant and market data, and news coverage.

Those records introduce related names including Leeward Energy, EDF Renewables, and Enbridge in project-adjacent context. That is useful intelligence. It tells you that the project lives inside a broader commercial ecosystem and may connect to sponsor-level activity not visible in the queue filing alone.

But this is the key methodological point: that context does not override the legal identity the primary records establish. Load Factor still treats Fox Squirrel Solar LLC as the queue-side developer record two sources agree on because that is what the authoritative documents support. The sponsor narrative can be explored, but it should not be forced into the legal attribution field without stronger corroboration.

That is what rigorous SPV developer identification looks like in practice. It is not just "find the biggest company name in the article and use that." It is establish the queue-side identity first, then layer context carefully.

Confirmation requires agreement, not intuition

Load Factor's confirmation method is deliberately conservative.

The platform confirms a developer when two or more independent authoritative sources agree. That means the evidence is not resting on one article, one guessed match, or one unverified record. It also means some projects remain unresolved longer than a more aggressive product would allow.

That trade-off is intentional.

For a market-intelligence platform, false precision is worse than visible uncertainty. If a queue filing names an SPV and the rest of the evidence is noisy, the right answer may be "SPV named by two sources, parent not yet proven." If a state record suggests a link but the queue-side records do not, the right answer may be "possible sponsor context, not enough for attribution." If two strong sources disagree, the right answer may be "contested."

In other words, Load Factor is built to preserve the audit trail, not hide it.

Why this matters for diligence, origination, and market mapping

SPV tracing is not an academic exercise. It changes how teams work.

For investors and lenders, it is a control check. You need to know whether the developer claiming a queue portfolio actually controls the positions they are marketing.

For developers, it is competitive mapping. A county may look fragmented by SPV names even though the underlying activity is concentrated in a handful of sponsor platforms.

For EPCs and service providers, it is a lead-generation filter. Outreach based on interconnection customer names alone is often inefficient because the commercial decision-maker sits above the SPV.

For advisors, it is the difference between thematic commentary and defensible market analysis. "There are 40 solar projects in this cluster" is a useful starting point. "Four sponsor families account for most of that MW" is the commercially relevant conclusion.

The moat is not the queue row. It is the evidence chain.

Queue data by itself is increasingly commoditized. The hard part is not collecting a row. The hard part is identifying the entity behind it, scoring the quality of the attribution, and showing enough source detail that another professional can verify the work.

That is the point of Load Factor's methodology. It is not trying to sound certain. It is trying to be auditable.

Methodology

This post uses Load Factor's canonical product context of 200,444 evidence records across 15+ public source types, in families such as grid-operator filings, federal regulatory filings (FERC, SEC, EIA), corporate disclosures, state and local public records, plant and market data, news and announcements, and many more. The AE2-148 example is drawn from Load Factor's current evidence snapshot for PJM project AE2-148: 15 evidence records from five families and an attribution two sources agree on. Load Factor confirms an attribution when two or more independent primary sources agree. News supports an attribution but never confirms one. Every attribution shows its confidence level and the sources on file, and we are re-grading any that claims more than its sources support.

Conclusion

The central problem in interconnection queue research is not lack of data. It is lack of verified identity. SPV names are everywhere, but evidence-backed developer attribution is not.

That is why Load Factor treats developer identification as a forensic workflow rather than a lookup table. The queue filing starts the research. The evidence chain finishes it.

To inspect queue records directly, browse projects on Load Factor. To see how the evidence shows up in the product, visit Features. For the market view that makes this work commercially useful, read US Interconnection Queue by the Numbers and The 10 Most Active Solar Developers in MISO.

Share this

Load Factor tracks 38,000+ interconnection queue projects, withdrawn included, across 16 North American markets, with the evidence behind every developer it names.

Next step

See your market in 30 minutes.

A walkthrough of the projects, developers and evidence in the markets you work in.

Get the weekly brief

Queue movement, newly identified developers and the week’s deals, every Monday. Read past issues

Book a 30-min walkthrough