GPC-compliant · EPA factors · built for city staff
Every city has a number.
This shows you yours.
Name your city and the grid region is picked for you. Answer plain questions while the dashboard builds itself. End with a report that tells the story, not just the numbers.
Not a mockup. This really works right now: a real GPC engine computing live figures.
City of Maplewood · FY 2024 · sectors → scopes → the number
computed live by the GPC engine
Hover or tab to a ribbon — every band is a real figure from the engine.
From city name to carbon story.
three steps · one afternoon
01
Pick your city
Name your city and state. TurboCAP pre-selects your EPA eGRID grid region and carries your population into every per-resident figure — attributed, not typed.
US Census ACS 5-year · EPA eGRID
02
Answer. It builds as you go.
One question at a time, with where-to-find-it context. Every answer re-runs the engine and another panel lights up.
154,500 t CO₂e
03
Read the story
Chapters, not spreadsheets: what your number is, where it lives, why, and what to do next, with the numbers one tab away.
≈ 9.4 t per resident · appendix included
GPC v1.1
BASIC & BASIC+ levels
EPA · eGRID factors
picked by grid region
Green Button XML
read exactly · VMT method
US Census ACS
auto-filled city context
IPCC AR5 GWPs
100-year, versioned
Done right, however you choose.
Do it yourself · With help · Done for you
The methodology is identical at every tier. What changes is how much TurboCAP does for you, through software, AI, and experts.
Build it yourself
Get step-by-step guidance and AI-powered answers as you go.
Get startedDo it yourself
154,500 t CO₂e
Experts help as you go
Get on-demand expert help, with human checkpoints and a final review.
With help
An expert builds it for you
Match with a dedicated analyst who delivers your inventory start to finish.
Done for you
In development
Automatic data feeds
Green Button (Download My Data) works today. UtilityAPI, StreetLight Data, Advan Research, Placer.ai are not connected yet — joining the list registers your interest, and a person follows up when a feed goes live. Nothing is charged, and no feed ever writes a figure into an inventory without your review.
Green Button (Download My Data)
In the product todayThe ESPI XML your utility's “Download my data” button produces, read exactly on the Data step — no AI, no credential.
Works today for any utility that offers the download. It is a file you fetch, not a connection: nothing refreshes on its own.
Fills: Commercial & institutional grid electricity · Commercial & institutional natural gas
UtilityAPI
Coming soonMetered electricity and gas by customer class, straight from the utility once an account holder authorizes it — the Green Button Connect layer.
Not connected yet. When live: the city authorizes its own accounts (municipal buildings, plants, streetlights); community-wide totals still need the utility's aggregate. Coverage depends on the utility, and collection is priced per meter-month.
Fills: Residential grid electricity · Commercial & institutional grid electricity · Industrial grid electricity · +8 more
StreetLight InSight
Coming soonVehicle-miles traveled inside the city boundary by vehicle class — the GPC Chapter 7 induced-activity method, with the miles measured instead of estimated.
Not connected yet. Requires a StreetLight subscription; the miles arrive as a modeled estimate, so the engine caps their data quality at “M” and the report says which fuel-economy anchors turned them into gallons.
Fills: On-road gasoline · On-road diesel
Advan Patterns
Coming soonWhere the people who visit the city come from and how commercial activity is trending — context for the story and the plan.
Not connected yet, and never a source of inventory figures: foot-traffic panels carry no distance, road or fuel, so no GPC number can be derived from them. This feeds the narrative, not the totals.
Fills no inventory source — story and plan context.
Placer.ai
Coming soonVisits, trade areas and visitor home block groups for the places that drive trips — context for the transportation chapter and CAP measures.
Not connected yet, and never a source of inventory figures: a visit count is not a vehicle-mile or a gallon. This feeds the narrative, not the totals. Requires a paying Placer account with the API add-on.
Fills no inventory source — story and plan context.
Tell us which utility and which feeds matter to you — it shapes what ships first.
Questions cities actually ask.
Is this actually GPC-compliant?
TurboCAP follows the Global Protocol for Community-Scale GHG Inventories v1.1, the standard behind CDP and GCoM reporting. Sources carry GPC reference numbers, notation keys (NO/IE/NE/C), and separate activity-data and emission-factor quality ratings, at the BASIC or BASIC+ reporting level.
Where do the numbers come from?
Emission factors from EPA's Emission Factors Hub, EPA eGRID by grid subregion, and IPCC defaults — weighed with AR5 100-year GWPs by default, or AR6 if your reporting program requires it, chosen per inventory. City context (population, households, income) auto-pulls from the US Census ACS, attributed on-screen. Factors are versioned and each inventory is pinned to its vintage, so a saved inventory recomputes identically later.
Can TurboCAP pull our utility and traffic data automatically?
Partly, today: your utility's Green Button XML (the “Download my data” file) is read exactly on the Data step, no AI involved. Automatic feeds are in development — UtilityAPI for metered electricity and gas, StreetLight for in-boundary vehicle-miles — and two context feeds, Advan and Placer.ai, that inform the story but can never produce an inventory figure. None of the four is connected yet; joining the list registers your interest and a person follows up.
What if we don't have data for a source?
Expected. The GPC has a notation system for exactly this: mark a source Not Occurring, Included Elsewhere, or Confidential and it appears in the report the way reviewers want to see it, instead of silently disappearing.
What do we get at the end?
A story, and the numbers behind it: a chaptered report that explains what your emissions are, where they come from, why, and what to do next, with the full source-level appendix one tab away and a print-ready export.
What happens to the files we upload?
TurboCAP runs on the Good Local Gov Data Vault in purge-after-run mode: raw files are read, cleaned, and structured for the run, only the approved numbers enter your inventory, and the originals are purged when the run finishes. It's a retention setting stated up front, and it's our default for city work.
Maplewood, FY 2024: 154,500 t CO₂e · ≈ 9.4 t per resident