Skip to content
Load Factor Docs
Open Load Factor

Guide

How sure are we? Confidence levels

What Load Factor's developer badges mean (Two sources agree, Named in the queue, Inferred, Not identified), how parents are verified, and how exact each map pin is.

  • Web app
  • Updated

Overview

Every developer Load Factor shows carries a badge that says how sure we are, and every link has a source you can open. This page explains the badges, so you can tell at a glance what you can rely on and what to check.

Three names behind every project

A queue project usually has three names behind it. Load Factor shows all three, side by side, at the top of every project page:

Name What it is Example
SPV / LLC The project company, exactly as filed. Developers create one for each project. Ragsdale Solar, LLC
Developer The company developing the project. EDP Renewables North America
Parent company The company that ultimately owns the developer, when a verified record shows it. EDP, S.A.

We always show the project company exactly as filed. We never "tidy" it into a brand name, and we only show a parent company when a verified record links it.

The developer badges

Badge What it means
Two sources agree Two or more independent official records name this company for the project. Copies of the same document count once.
Named in the queue The grid operator's own queue names this company for the project, and no second independent record does yet. It is the company of record, not a guess.
Inferred We show a developer on weaker support: a single record, supporting sources such as news, or records that disagree. The project page says which.
Not identified No developer is identified yet.
Tip:

Filter on the badge in Projects (the funnel icon, then the confidence section) to work only with developers where two sources agree, or to find the projects with no developer identified that are worth researching.

A badge can change in either direction. When a new record names the company, a project can move up to Two sources agree. When records disagree, it moves to Inferred until the disagreement is resolved. Projects you watch tell you when their developer is identified, changed or backed by a second source.

Parent companies

A parent company shows a Verified tag when an official record links the developer or the project company to it. Without one, the parent box stays empty: we don't guess.

Sources and their strength

On a project page, the Sources card lists every document and record behind the project, each with a strength:

  • Strong: official records filed with grid operators and with federal or state regulators.
  • Supporting: other public records, company filings and news coverage that back them up.
  • Lead: automatic matches and research leads: worth checking, never enough on their own.

Open any document from the card to read it yourself.

How exact is the map pin?

Every project's map carries a label that says how exact its pin is:

Label Where the pin is
Accurate project location On the project site.
Approximate POI substation location At the substation the project connects to (its point of interconnection).
Approximate POI line location On the transmission line the project taps into.
Approximate ZIP-level or city-level location At the centre of the ZIP code or city.
Approximate county-level location At the centre of the county: only the county is known.

In Projects, the full filter list (the funnel icon) has a location-accuracy section, so you can, for example, leave county-level pins out of a site screen.

Dates on a project

The chips under a project's name tell you how fresh it is:

  • Queue synced: when we last read the grid operator's queue for this project.
  • Queue row changed: when the operator last changed the project's queue entry.
  • Developer checked: when the developer attribution was last reviewed.

Queues are read every day.