Skip to content
LOAD FACTOR

About Load Factor

Public. Just in pieces.

Who is really building a power project is never written down in one place. We go get every piece, link them until it makes sense, and show you the receipts.

Diagram: scattered fragments of public records (grid operator filings, federal filings, contract reports, state and county records, plant and market data, corporate disclosures, press releases, and many more) flow together into one project record. The record has four lines: the queue entry; the project company, with the exact SPV or LLC name as filed; the developer, marked Two sources agree when two or more sources name it; and the parent, shown only if a record proves it.

ISO / RTOGrid operator filingSTATEState recordCOUNTYCounty recordFEDERALFederal filingFEDERALContract reportSTATERegulatory recordCOMPANYPress releaseMARKETPlant and market dataCOMPANYCorporate disclosureCOUNTYLocal public recordONE PROJECT RECORDQUEUE ENTRYQueue ID, size, substationPROJECT COMPANY, AS FILEDExact SPV or LLC nameDEVELOPERTwo sources agreePARENTOnly if a record proves itEVERY LINK HAS A SOURCE ISO / RTOGrid operator filingSTATEState recordCOUNTYCounty recordFEDERALFederal filingFEDERALContract reportSTATERegulatory recordCOMPANYPress releaseMARKETPlant and market dataCOMPANYCorporate disclosureCOUNTYLocal public recordONE PROJECT RECORDQUEUE ENTRYQueue ID, size, substationSPV, AS FILEDExact SPV or LLC nameDEVELOPERTwo sources agreePARENTOnly if a record proves it
Scattered public records in. One project record out. Every line is a source you can check.

The count

Live numbers, rounded down.

Rounded down on purpose: rounding up is how numbers start lying. Inside the product you get the exact figure.

38,000+queue projects, withdrawn included
16North American markets
270,000+pieces of evidence
79kinds of source
21,000+projects with a developer on file, withdrawn included
1,800+data-center sites

From the team

Why we’re like this.

Every kind of source in this note is one we actually pull from. More on where the pieces come from further down.

Here’s what hooked us.

Open any interconnection queue and you get a row: a queue number, some megawatts, a substation, a county. Sometimes a company name. Usually it’s an LLC named after a creek, a road or a small animal, set up for this one project. No website. No logo. No phone number.

But somebody is behind that LLC. A developer is spending real money on land, studies and deposits, and there is often a bigger company above them. And here’s the part that still gets us: the answer is almost always public. It’s just never in one place.

The pieces are out there, just scattered. A line in a federal filing. An entry in a state record. A file at the county office where the project sits. A contract report. A company disclosure. A press release. And many more. Every one of them is public. None of them sits next to the others, and not one is labelled “the answer.”

Each piece on its own is a shrug. Linked together, they’re an answer you can defend.

So that’s the job: go get every piece and link them until it makes sense. Across 16 markets, every filing we can find. So far that’s 270,000+ pieces of evidence from 79 kinds of source, behind 38,000+ queue projects, withdrawn included. And because power only matters where it lands, we map the demand and the wires too: data-center sites, transmission lines and substations.

Obsessive? Completely. We’re data freaks on purpose. A developer name without a source is a rumor, and people make real calls on this data: where to site, what to buy, who to call.

The rule we care about most is the boring one. If we can’t prove it, we don’t say it. When we don’t know who is behind a project, the page says unknown. We’d rather show you a blank than a guess.

And if you catch us wrong, tell us. We’ll go read the filing. Honestly, we’ll enjoy it.

The Load Factor team

Where the pieces come from

All public. Never in one place.

Every piece comes from the public record. A few of the families are below. Each one is read on its own terms, tied to the exact entity it names, and cited on the record it supports.

Grid-operator interconnection queues

The starting row for every project: PJM, MISO, ERCOT, CAISO, SPP, NYISO, ISO-NE and the Canadian operators, 16 markets in all.

Federal regulatory filings

What energy companies file with federal regulators, FERC above all.

Corporate disclosures

What public companies file with the SEC about themselves and the businesses they own.

State and local public records

State agencies, utility commissions and county offices: the public record closest to the ground.

Plant and market data

Federal plant data from the EIA, plus wholesale and contract prices for the power itself.

News and announcements

Financings, sales and power deals, as announced. Good context. Never enough on its own to confirm anything.

A snapshot. We read 79 kinds of public source so far, and the list keeps growing.

How we know

Follow one project all the way up.

Every project resolves the same way, one link at a time: the queue entry, the project company exactly as filed, the developer, and a parent only when a record proves it. Each link carries its sources and says how sure we are.

Two sources agreeTwo or more independent sources name the developer.
Named in the queueThe grid operator’s queue names it; no second source yet.
InferredWeaker support so far, shown with its source.
Not identifiedNothing on file yet, and we say so.
One project, link by linkThe method
  1. 01 · Queue entryWhat the grid operator publishes

    A queue ID, a size, a fuel, a substation, a status. Sometimes an LLC name. Never the whole story.

    As the grid operator published it
  2. 02 · Project company, as filedThe SPV or LLC, spelled exactly as filed

    We don’t tidy it up or swap in a brand. The filed name is evidence, so it stays exactly as filed, every word of it.

    Exact name, as filed
  3. 03 · DeveloperThe company actually doing the work

    Marked Two sources agree only when two independent primary sources name it. One source makes it inferred, or named in the queue when that source is the grid operator’s queue. None means not identified.

    Two independent sources to confirmNews supports, never confirms
  4. 04 · ParentWho owns the developer, if a record says so

    Named only when a public record proves it. A lookalike name or a shared address is not proof, and a hunch never is.

    Proof, or nothing
Sources and confidence on every linkSee it in Load Factor Pulse

The rules

Five things we’re obsessive about.

None of them are clever. All of them are non-negotiable.

  1. Every name has a source.

    If a developer, an SPV or a parent appears on Load Factor, the record behind it sits right next to it. No source, no name.

  2. SPV names, exactly as filed.

    We never rename a project company to the brand we think is behind it. The filed name is evidence, and tidying it up destroys the evidence.

  3. We never guess a parent.

    A parent company appears only when a public record proves it. A hunch, a lookalike name or a shared office address doesn’t count.

  4. Two sources agree means exactly that.

    Two independent primary sources naming the same company. The grid operator’s queue alone is named in the queue; any other single source is inferred. No source is not identified. Every project shows its confidence level: two sources agree, named in the queue, inferred or not identified.

  5. We re-grade what overstates.

    Automation finds a lot, fast, and not all of it is right. Every attribution shows its confidence level and the sources on file, and we are re-grading any that claims more than its sources support.

Keep digging

Go deeper, or check our work.

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