Evidence surfaced
8 items
County scorecard
Washington County, OH data-center scorecard
4 power records informed this scope; queue and grid proxy signals support screening viability.
Need the trust rules first? Review the public methodology. Need the launch-market view? Open the Ohio / PJM market summary.
Published as of Mar 12, 2026, 02:09 PM GMT+2
Release: Current published releaseMethodology: power-ready-sites-methodology-v1.1.0Confidence: Medium confidence (66 / 100)Recency: Current
Scorecard
Screening read at a glance
Treat this as an early diligence surface: enough to compare routes, not enough to claim site-level certainty.
Overall score
63.6
Confidence: Medium confidence (66 / 100)
Freshness: Current
Methodology version
power-ready-sites-methodology-v1.1.0
Trust snapshot
Confidence level: Medium confidence (66 / 100)
Source recency: Current
Signal recency by category
Use this strip to see which categories are current, which ones are starting to age, and which ones need a refresh check before deeper diligence.
Power: CurrentConnectivity: CurrentWater: CurrentHazards: CurrentLabor Demographics: CurrentIncentives: Current
See category-level source recency
- PowerRecently refreshed • 68d old
- ConnectivityRecently refreshed • 105d old
- WaterRecently refreshed • 105d old
- HazardsRecently refreshed • 77d old
- Labor DemographicsRecently refreshed • 78d old
- IncentivesRecently refreshed • 73d old
What geography is this?
County-level screening for Washington County, OH within the ohio-pjm launch market.
Publish source
Current published release is displayed directly on this page.
What this score means
This county page is an early-screening surface. It helps buyers compare power, fiber, water, confidence, and freshness signals before deeper diligence.
What can slow diligence here
- Screening outputs do not guarantee utility deliverability or energization timing.
- Parcel-level zoning, title, and entitlement diligence is outside this scoring model.
- Incentive eligibility may depend on case-specific legal and tax review.
Before you buy this pack
Verify the county proof first
Sample shortlist rows, export preview, and launchability evidence are visible before purchase. Use this county scorecard, the market summary, and the public methodology to confirm the pack is the right next step.
1. Review market context
Start with the launch-market summary so this county sits inside the broader shortlist and route context.
Open Ohio / PJM market summary2. Review methodology
Confirm how confidence, freshness, and evidence limits work before moving from public screening into a paid surface.
Review methodology3. Open the pack scope first
The market-specific offer page now carries the proof language, pack scope, and buying route for this market.
View Ohio / PJM Time-to-Power PackNext step: review pack scope or monitor
Sample shortlist rows, export preview, and launchability evidence are visible before purchase. Open the market-specific offer page first when you need proof and scope. Buy the pack when you need a concrete shortlist and export-ready diligence layer. Use the watchlist when you need recurring signal monitoring after initial screening.
Stay inside the market graph
Use the market summary and nearby counties and metros to continue screening this launch market with stronger internal context.
Evidence
Evidence highlights
Positive signals and constraints stay visible together so route confidence does not hide downside.
Several signals use bridged or proxy evidence. Use this score for early screening, then validate with direct utility and permitting diligence.
Positive signals
Power proxy supports shortlist potential
4 power records informed this scope; queue and grid proxy signals support screening viability.
Connectivity proxy supports network access posture
4 connectivity records indicate supporting network infrastructure proxies.
Labor support signal observed
2 labor records support staffing feasibility at county/metro scale.
Incentive bonus applied from available program registry
2 incentive records contributed to bonus scoring under current manual-first registry.
Constraints
Water risk penalty applied
2 water context records contributed to a risk penalty for screening conservatism.
Hazard risk penalty applied
6 hazard records indicate climate and event exposure requiring mitigation allowance.
Expand full evidence list
Power proxy supports shortlist potential
4 power records informed this scope; queue and grid proxy signals support screening viability.
Power • Fresh
Connectivity proxy supports network access posture
4 connectivity records indicate supporting network infrastructure proxies.
Connectivity • Fresh
Water risk penalty applied
2 water context records contributed to a risk penalty for screening conservatism.
Water • Fresh
Hazard risk penalty applied
6 hazard records indicate climate and event exposure requiring mitigation allowance.
Hazards • Fresh
Labor support signal observed
2 labor records support staffing feasibility at county/metro scale.
Labor Demographics • Fresh
Incentive bonus applied from available program registry
2 incentive records contributed to bonus scoring under current manual-first registry.
Incentives • Fresh
Geography bridge applied for power
power evidence was attached via state fallback for county scope.
Power • Fresh
Geography bridge applied for power
power evidence was attached via market fallback for county scope.
Power • Fresh
Limitations
This score helps early screening, not permitting approval, utility commitment, or parcel-level constructability.
- Screening outputs do not guarantee utility deliverability or energization timing.
- Parcel-level zoning, title, and entitlement diligence is outside this scoring model.
- Incentive eligibility may depend on case-specific legal and tax review.
Expand all limitations
- Screening outputs do not guarantee utility deliverability or energization timing.
- Parcel-level zoning, title, and entitlement diligence is outside this scoring model.
- Incentive eligibility may depend on case-specific legal and tax review.
- County score does not resolve parcel-specific utility engineering constraints.