Every interconnection queue in the US is filled with entity names that follow a recognizable pattern: a location, a fuel type, and "LLC." White Oak Solar I LLC. Pecos Wind Holdings LLC. Cardinal Storage Project Company LLC. These are not companies in the traditional sense. They are SPVs - special purpose vehicles - and understanding what they are and why developers use them is the first step to understanding who actually sits behind any queue project.
What is an SPV?
A special purpose vehicle (SPV) - also called a special purpose entity (SPE) or project company - is a legal entity created for a single, defined purpose. In renewable energy, that purpose is almost always to develop, construct, finance, and operate one power generation project.
The SPV is a blank legal slate when it is formed. It has no prior assets, no liabilities, no credit history. It exists to be the counterparty to every contract related to one specific project.
At formation, a renewable energy SPV typically:
- Is a limited liability company (LLC) in the state where the project is located
- Has the developer (or a developer affiliate) as its managing member or controlling equity holder
- Has no employees - employees work for the developer parent, not the SPV
- Has a name that references the project location or a developer-internal code
Why developers use SPVs for every project
The SPV structure is not arbitrary. It solves several simultaneous problems in project finance and legal risk management.
Risk isolation. If the project fails, the SPV fails. The developer's other projects, corporate assets, and balance sheet are not automatically exposed. Lenders and tax equity investors demand this structure precisely because it limits their exposure to one project rather than the developer's entire portfolio.
Tax equity compatibility. The US production tax credit (PTC) and investment tax credit (ITC) require a specific ownership structure for the tax benefits to flow to the right party. A tax equity investor - typically a large bank - takes a percentage ownership stake in the SPV during construction and early operation to claim the tax credits. This requires a clean ownership structure at the project level, which SPVs provide.
Non-recourse project finance. Construction loans and term debt for renewable energy projects are typically structured as non-recourse debt at the SPV level. The lender's claim is against the project's assets and cash flows, not the developer's corporate balance sheet. Non-recourse debt requires a dedicated project entity to hold the assets.
Clean title chains. Real property - leases, easements, fee land - is held in the SPV's name. When the project is sold, the buyer acquires the SPV's membership interests (or sometimes the assets directly), and title passes cleanly without a full asset transfer.
Multiple counterparties, one project. A typical utility-scale solar project has a landowner lease, an interconnection agreement with the ISO, a power purchase agreement with the offtaker, an EPC construction contract, an O&M agreement, a lender, and a tax equity investor. Each of these counterparties is contracting with the SPV. If the developer used its corporate entity directly, a problem in one project could contaminate relationships with counterparties in all others.
How SPVs appear in interconnection queues
Every ISO queue entry names an "interconnection customer" - the legal entity that filed the application and will be a party to the interconnection agreement. That entity is almost always an SPV.
This is the fundamental challenge for queue intelligence. The queue record shows:
Interconnection Customer: Sage Mesa Solar 1 LLC
Queue Number: QF-2024-0042
State: New Mexico
Fuel Type: Solar
MW: 300
"Sage Mesa Solar 1 LLC" tells you nothing directly about the developer. To answer "who is actually developing this project," you need to trace from the SPV to its owner.
That tracing draws on other public records:
- State and local public records - business registrations, land records and permitting files kept by states and counties
- Federal regulatory filings - records filed with FERC, the SEC and EIA as a project and its owners move through the system
- Corporate disclosures - what companies themselves file and announce about their projects and subsidiaries
- News and announcements - useful context that supports an attribution but never confirms one on its own
- And many more - the list keeps growing
The SPV name itself is not evidence. It is the starting point for a research chain.
How developers name SPVs
Naming conventions vary by developer, but common patterns are interpretable.
Geographic names: "Sage Mesa Solar 1 LLC" or "Texas Panhandle Wind Holdings LLC" - names that reference the project location directly. Usually developer-neutral (doesn't tell you who the developer is from the name alone).
Developer code names: Some developers use internal project codes. "Enlight Renewable Energy TX2 LLC" - the parent brand appears directly in the SPV name. Easier to identify, but not universal.
Numbered series: "NextEra Energy Resources LLC" won't appear in the queue - NextEra uses project SPVs. But a series like "NER Wind Holdings I through VIII LLC" may cluster around a recognizable parent.
Generic names: Some developers use names that are entirely opaque - "Aspen Meadow Energy LLC" could be anyone. These take several independent public records to resolve.
Shell company chains: Larger transactions sometimes involve layered holding company structures. SPV → Project HoldCo → Regional HoldCo → Developer. Each layer adds complexity to the tracing process.
The SoS lookup: first stop in SPV research
For anyone researching a single project, the state Secretary of State's business registry is the natural first stop. Every LLC formed in the US registers with a state, and that registration is public: the entity's name, formation date, status and filing history, and in some states the people or companies that manage it.
A registry record is a lead, not an answer. Filings are often made by law firms or formation services on a client's behalf, and many SPVs sit several layers below the company that controls them. A name on a filing is worth corroborating before it is worth repeating. For what these records show and where they fall short, read Secretary of State LLC Filings.
What "Two sources agree" means
Load Factor states a confidence level with every developer attribution. An attribution reads "Two sources agree" only when two or more independent primary sources name the developer.
| Confidence level | What it means |
|---|---|
| Two sources agree | Two or more independent primary sources name the developer |
| Named in the queue | The grid operator's queue names the developer, and no second source does yet |
| Inferred | One source identifies the developer, and nothing contradicts it |
| Not identified | No evidence yet links the SPV to a developer |
The consequence: an SPV whose name closely resembles a known developer (e.g., "BrightNight Wind LLC") is not marked Two sources agree on the strength of its name. It is a reasonable working attribution, shown as inferred, until an independent public record agrees.
This conservatism is intentional. Over-attribution - guessing the parent from the SPV name - produces rankings that look clean but contain errors. Load Factor would rather leave a developer unknown than guess one from a name, and every attribution carries its confidence level.
SPVs in M&A transactions
SPVs are the unit of transaction in renewable energy M&A. When a project is acquired, the buyer typically acquires the SPV's membership interests - not the underlying assets directly. This means:
- The queue record continues to show the SPV name unchanged after a sale
- The developer attribution must be updated based on the new ownership
- Secondary market transactions (partial equity sales, tax equity recaptures) can layer additional complexity onto the ownership chain
Load Factor tracks M&A transactions that change SPV ownership, so the attribution for an affected project can be updated to reflect the new controlling entity.
Why SPV opacity creates market inefficiency
For investors, lenders, EPCs, and equipment vendors trying to identify project counterparties, SPV opacity creates a real market problem. The queue record names an entity that doesn't have a website, a credit history, a management team, or a track record. The underlying developer may be a well-capitalized IPP with a 20-project operating portfolio - or a newly formed entity with no assets.
The information asymmetry benefits well-resourced players who have the legal and research capacity to trace SPVs manually. It disadvantages market participants who cannot invest in systematic research infrastructure.
Queue intelligence tools - including Load Factor - exist specifically to reduce this asymmetry. By systematically tracing SPV-to-developer for thousands of projects and documenting the evidence chain, the attribution becomes available to market participants who couldn't produce it individually.
Frequently Asked Questions
What does SPV stand for in renewable energy? Special purpose vehicle. In renewable energy project finance, an SPV is an LLC created specifically to develop and own one power plant. It isolates the project's risk, assets, and contracts from the developer's other projects and corporate balance sheet.
Why do solar and wind developers use LLCs instead of developing projects directly? Tax equity structures for the ITC and PTC require project-level ownership by the tax equity investor. Non-recourse project finance requires a clean entity holding the project's assets. Risk isolation protects the developer's other projects if one project fails. LLCs are the standard legal vehicle for all of these structures.
How do you find out who owns a renewable energy SPV? Start with the state Secretary of State's business registry for the LLC itself, then look for independent public records that agree: grid-operator and federal filings, corporate disclosures, and state and local records. One record is a lead; two independent records that agree are an answer. Or open the project in Load Factor, where the developer and the evidence behind it are already shown.
What is the difference between an SPV and a holding company in renewable energy? An SPV holds one project. A holding company (HoldCo) owns equity in multiple SPVs. A developer's portfolio may be structured as Developer Parent → Regional HoldCo → Project HoldCo → SPV. Each layer exists for tax, financing, or operational reasons.
Can I find renewable energy SPV ownership in public records? Yes, partially. State business registrations are public everywhere, though what they disclose varies by state. Federal filings with FERC, the SEC and EIA are public. County land records are public but vary in accessibility. Pulling these together for thousands of projects, and checking them against each other, is what queue intelligence tools do.
Methodology
Load Factor identifies developers from public records: 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. A developer shows Two sources agree only when two or more independent primary sources name it; one source makes it inferred, and no evidence means not identified. The SPV is shown exactly as filed, and a parent company is named only when a public record proves it. For how this plays out on a single project, read Who Is Behind That SPV?.
Conclusion
SPVs are the fundamental unit of renewable energy project development. Every project in every interconnection queue is held by one. Understanding why they exist - risk isolation, tax equity, non-recourse finance, clean title - explains why queue research requires going beyond the queue record itself. The queue names the SPV. The evidence names the developer.
Browse queue projects with their developers to see who stands behind the SPVs across more than 41,000 queue projects, withdrawn included, with the evidence for each developer named. For how Load Factor identifies the developer behind an SPV, read Who Is Behind That SPV?.