powerProxyScore
Proxy score for transmission proximity, queue activity, and substation headroom indicators.
Higher is better.
Methodology
How Bankable Time-to-Power Intelligence works
Deterministic component model: opportunity components add upside, risk components apply deductions, and confidence is aggregated separately from score.
This is the canonical public methodology for gpuleaseindex.com trust surfaces, launch-market pages, and the Time-to-Power Pack buying route.
Published as of Mar 12, 2026, 02:09 PM GMT+2
Release: Current published releaseMethodology: power-ready-sites-methodology-v1.1.0Confidence: High confidenceRecency: Current
Trust snapshot
Confidence level: High confidence
Source recency: Current
Score components
connectivityProxyScore
Proxy score for edge/fiber footprint depth and exchange adjacency; not a long-haul route guarantee.
Higher is better.
waterRiskPenalty
Penalty from baseline water stress and drought/regulatory exposure proxies.
Higher means more score deduction.
hazardRiskPenalty
Penalty for flood, heat, wildfire, storm, and drought exposure requiring mitigation budget.
Higher means more score deduction.
laborSupportScore
Labor support proxy from labor pool depth, unemployment, and migration context.
Higher is better.
incentiveBonus
Bonus from program breadth and estimated incentive magnitude.
Higher is better.
Confidence philosophy
high (min 80)
All critical families present with strong/medium coverage and no stale critical lineage.
medium (min 60)
At most one critical family is sparse/aging and geography linkage remains usable.
low (min 40)
Multiple family gaps or stale critical lineage materially weaken screening confidence.
unknown (min 0)
Insufficient lineage or timestamp quality prevents defendable confidence assignment.
Freshness philosophy
fresh (<= 14 days)
Critical family evidence is within expected recency windows.
aging (<= 35 days)
At least one critical family exceeds fresh window but remains screening-usable.
stale
Critical-family recency is degraded and should trigger caution for shortlist decisions.
unknown
Timestamp lineage is missing or unparseable.
What is in scope
- Published county and metro screening for launch markets.
- Current and LKG publish source labeling on public objects.
- Evidence-backed scoring with explicit limitations.
What is not guaranteed
- No guarantee of exact available MW at parcel boundary.
- No guarantee of interconnection agreement timing or upgrade cost.
- No guarantee of permitting, entitlement, or tax incentive approval outcomes.
Time-to-Power signal basis
How Time-to-Power Signal Basis Works
Timing confidence is derived from signal basis, not invented in copy. Every row in a Time-to-Power Pack is assigned one of five basis levels. The level determines how the energization window was derived and how much trust the timing claim can carry.
1
High confidenceDirect queue match
DirectThe exact queue ID from the sample row matches a TTPS entry directly. No normalization, prefix stripping, or decorator removal was needed.
High confidence — the energization window is derived from actual TTPS probabilities for this specific queue position.
2
Medium-High confidenceNormalized queue match
NormalizedThe queue ID required normalization (stripped decorators, PJM/ERCOT prefix handling, whitespace cleanup) but still resolved to a unique TTPS entry.
Medium-High confidence — the underlying TTPS probabilities are still queue-specific after normalization.
3
Medium confidencePack band proxy
Band proxyNo queue match was found. The row's TTPS band (A/B/C/D) was used as a proxy to derive an energization window from band-level fallbacks.
Medium confidence — timing is usable for pack framing, but proxy rows need visible separation from queue-linked rows.
4
Low-Medium confidenceISO proxy
ISO proxyNo queue match and no band were available. The ISO-wide average was used as a proxy to assign a fallback energization window.
Low-Medium confidence — timing depends on proxy basis. Use for early screening only, then validate with direct diligence.
5
Low confidenceUnresolved
UnresolvedNo timing basis could be assigned. The row lacks a queue ID, a recognizable band, and a matchable ISO context.
Low confidence — timing basis is thin. Do not support stronger TTPS claims until direct utility or queue confirmation is obtained.
Proxy basis is real and visible
When a row uses band-proxy or ISO-proxy basis, that fact is displayed on every surface that shows the row — compare pages, weekly-change pages, and pack previews. Proxy basis is never hidden behind better copy.
Queue-linked
Direct and normalized queue matches are queue-linked. The energization window comes from actual TTPS probabilities for that specific queue position.
Proxy basis
Band-proxy and ISO-proxy rows use fallback windows derived from band averages or ISO-wide averages. These are visibly labeled wherever they appear.
Unresolved
Unresolved rows have no assignable timing basis. They do not carry an energization window and should not support timing claims.
Energization window derivation
When a row is queue-linked (direct or normalized), its energization window is derived from the actual TTPS probabilities (12-month, 18-month, and 24-month likelihoods) for that queue entry. When the row is proxy-based, the window is derived from band-level fallbacks: band A maps to ≤18 months, band B to 12–24 months, band C to 18–36 months, and band D to >36 months / high risk. ISO-wide proxies use the ISO average across all known queue positions.
This taxonomy exists so every public surface — compare, weekly-change, watchlist, and offer pages — uses the same definitions for timing basis and confidence.
Launch-market route
Apply the methodology to the launch route
Use the methodology to understand what the public scores mean, then move into the strongest market, county, and metro pages before taking the paid next step.
Priority market
Texas
Texas is the strongest launch anchor for speed-to-power screening, with the clearest near-term route into Time-to-Power-Pack-first commercial intent.
Use county and metro scorecards to separate attractive ERCOT narratives from real interconnection, curtailment, and water constraints.
Priority counties
Priority metros
Start with the Texas Time-to-Power Pack, then move into watchlist monitoring.
Priority market
Georgia / Atlanta
Georgia-Atlanta is a real launch anchor alongside Texas because Atlanta demand gravity is commercially meaningful and the county / metro trust layer is now strong enough to support Time-to-Power-Pack-first intent.
Do not collapse Georgia-Atlanta into one clean story. Fulton, Coweta, Cherokee, and the Atlanta metro still need to be compared directly before assuming the region is equally ready or equally fast.
Priority metros
Treat Georgia-Atlanta as a launch-ready anchor, but earn the Time-to-Power Pack through county and metro comparison before moving into transaction-support diligence.
Priority market
Carolinas
The Carolinas are a real public market, but they work best as an honest beta route where county and metro comparison builds trust before the Time-to-Power Pack carries commercial weight.
Do not present the Carolinas as a fully uniform launch anchor. Metro and object quality can still vary, so public copy should keep confidence limits and beta honesty visible.
Use Carolinas county and metro pages to build trust first, then move into the Time-to-Power Pack or watchlist only after the route is convincing enough for deeper diligence.
Controlled coverage
Ohio / PJM
Ohio-PJM is strategically important because PJM / power / queue relevance makes it commercially meaningful, but the public story should stay explicit about where authority is mixed and where confidence is still earned page by page.
Do not present Ohio-PJM as more authoritative than the current evidence warrants. Keep mixed-authority power caveats visible and avoid implying that public relevance equals uniform execution certainty.