# How do I schedule training when the grid is greener?

> Run training and batch AI jobs when grid carbon intensity is low: use forecasts, make jobs pausable with checkpoints, and keep deadlines as hard limits.

Source: https://greenai.guide/how-do-i/schedule-training-when-the-grid-is-greener/  
Updated: 2026-11-19

## In short

Find the jobs that can wait, such as training, fine-tuning, evaluation and batch inference, and start them when a carbon-intensity forecast shows the grid is cleaner. Save regular checkpoints so long jobs can pause when intensity rises and resume when it falls, within a firm deadline. Carbon-aware scheduling cuts carbon, not energy, so do it on top of efficiency work.

## Steps

1. List AI jobs that can wait hours without harm, with each job's real deadline.
2. Get a carbon-intensity forecast for the region where the job runs.
3. Start flexible jobs in the cleanest window that still meets the deadline.
4. Save checkpoints, including optimiser state, so long jobs can pause and resume.
5. Track energy per job as well as carbon, so scheduling doesn't hide growth.

**Most training jobs don't need to start the moment you press enter.** Moving them to cleaner hours lowers their
carbon with no change to the model.

## Where do forecasts come from?

- In Great Britain, the National Energy System Operator's Carbon Intensity API forecasts carbon intensity more than
  96 hours ahead for 14 regions.
- Electricity Maps provides real-time and forecast data for more than 350 zones worldwide.
- The Green Software Foundation's Carbon Aware SDK is a web API and command-line tool that draws on such data so
  software can "do more when the electricity comes from clean low-carbon sources and less when it does not".

## How do I handle long jobs?

The Green Software Foundation's pattern for AI workloads suggests pausing and resuming long-running training jobs
based on carbon-intensity thresholds where feasible. That needs regular checkpoints, including optimiser state, so
nothing is lost when a job stops. Measure the checkpoint overhead so the pauses don't cost more than they save.

## Common mistakes

- **Confusing carbon with energy.** Shifting a job doesn't make it use less; a falling carbon figure can hide rising
  energy. Track both.
- **Letting deadlines slip.** Make the deadline a hard limit, not a preference.
- **Scheduling against yearly averages.** You need hourly forecasts for the region where the job actually runs.
- **Scheduling tiny jobs.** The gain is in big, flexible runs, not every script.

You can also [choose a lower-carbon region](/how-do-i/pick-a-low-carbon-cloud-region/). See
[efficient training and inference](/practice/efficient-training-and-inference/).

## Sources

- [Carbon Intensity API](https://carbonintensity.org.uk/), National Energy System Operator (2025)
- [Carbon Aware SDK](https://github.com/Green-Software-Foundation/carbon-aware-sdk), Green Software Foundation (2025)
- [Use carbon-aware scheduling and region selection for AI workloads](https://github.com/Green-Software-Foundation/patterns/blob/main/docs/operations/carbon-aware-ai-scheduling.md), Green Software Foundation, Green Software Patterns (2025)
- [Electricity Maps data](https://www.electricitymaps.com/data), Electricity Maps (2026)
