Promised vs. Produced Tracker · methodology
Our Promised vs. Produced Tracker (“Tracker”) is the central artifact of our methodology. Its purpose is to measure to what extent announced American factories actually result in output.
01 · What we record
For each individual project that is announced, we obtain the date of announcement, the promised completion date, and the scale of the project in terms of both promised capital (USD) and promised jobs (all if available).
When the project was first announced.
When the announcement said the project would be done.
The scale of the project, in USD.
The scale of the project, in jobs.
The first time the facility produces any goods related to what was promised for commercial purposes.
We also assign each project one of six current statuses:
An illustrative project, drawn the way the Tracker draws each row
02 · What counts
We consider factories that satisfy the following:
Located in a US state.
Covers a single physical facility, not a multi-site announcement — and tracks the specific promise made about that facility, not the facility itself.
Their announcement is published on or after January 1, 2017.
Their announcement promises either at least $1 billion in capital OR 2,000 new jobs (directly in the factory).
Produces in one of the following industrial sectors:
All others are categorized as “Other.”
03 · The pipeline
To collect the Tracker, we construct a pipeline with three layers: Source, Screen, and Verify.* Both Source and Screen are extracted agentically, while Verify — the Tracker in its final form — is a human-only gate.
We start with Source, where we search for a new project and collect URLs that contain information on both its initial announcement and its current status.
Passes on
Screen explicitly extracts the information from these links to provide provenance for our measured values on the factory’s development.
Passes on
Verify is where a human makes the final call and any remaining edits to add the new project to the Tracker, confirming that a human will have examined and verified all provenance from the links.
Passes on
Verify’s output, in its final form.
Keeping the agents controlled
Tools for the verifiers
Data fields in this table are bound by role
* Akin to ELT medallion pipelines in data engineering.
† Claude Code, using Opus 4.8 on high reasoning.
04 · The repository
Though we keep our methodology tighter for this work, we publish our Git repository to allow fair use and (agent-agnostic) additions to the Tracker.
| Promised | On the Tracker | In the repository |
|---|---|---|
| Capital | $1B | $100M |
| Jobs | 2,000 | 200 |
With that, we loosen our current criteria from $1B in promised capital to $100M, and from 2,000 promised jobs to 200, because as currently defined, the criteria cap the pool at 162 projects.
We also update the Tracker quarterly alongside our previous project, the Industrial Dollar, for public output on the Tracker page.
05 · Prior art
Existing work falls into three groups of trackers: those that record what was promised, those that follow what happened after the promise, and those that do some of both but within a single sector. The Promised vs. Produced Tracker brings these together by following each announced U.S. facility from promise to first output, across sectors.
06 · Limits
Nonetheless, this methodology does carry some limitations.