How to Review Water Risk for an AI Data Center
A site-diligence checklist for water sources, cooling design, permits, consumption, and operating limits.
Some compute jobs can move to another hour or region. Others must run when a user sends a request. Carbon-aware scheduling applies only when the workload has real flexibility and the operator has suitable grid data.
Average generation mix and marginal emissions answer different questions. Record the provider, region, time interval, forecast horizon, and method. If the scheduler uses a forecast, retain the forecast that was available when it made the decision.
if deadline_requires_start:
start_job()
elif forecast_is_current and lower_emissions_window_is_available:
queue_for_window()
else:
follow_default_schedule()The policy needs a maximum wait, a fallback for missing data, and a rule for capacity loss. A low-emissions forecast must not cause the job to miss its service requirement.
Report the actual run window and the baseline window used for comparison. Include any added data transfer, idle capacity, or repeated work. Do not report an avoided-emissions value without the baseline method and source data.
User-facing inference, urgent recovery work, fixed-location data, and continuously utilized capacity may have little scheduling freedom. In those cases, hardware efficiency, model design, cooling, or power procurement may be the relevant control.
Carbon-aware scheduling can reduce a workload's estimated emissions under a defined method. The result varies by workload, grid, window, baseline, and data quality. Measure those conditions before making a savings claim.
A site-diligence checklist for water sources, cooling design, permits, consumption, and operating limits.
A review checklist for workload energy, power sources, cooling, water, hardware use, and evidence.
How specialist analysis, review records, approval authority, and external action stay separate.