# PI Planning: preparing capacity before the event

> PI Planning: how to prepare each team's capacity before the SAFe event, avoid overload, and keep commitments.

- HTML: https://www.simpleworkload.com/en/methods/pi-planning
- Markdown: https://www.simpleworkload.com/en/methods/pi-planning.md

## How do you prepare capacity before a PI Planning?

Before a PI Planning, each team must know its net capacity for every iteration of the PI: available days, absences, run share, and shared people. The RTE consolidates these figures to detect conflicts between teams and ensure that commitments made during the event stay sustainable.

## Preparation checklist

- Collect absences and events for the next two or three months.

- Compute each team's capacity per iteration.

- Identify shared people and split their time.

- Reserve the run, innovation, and planning share.

- Spot cross-team dependencies in advance.

## During and after the event

- Compare commitments with the capacity displayed in the session.

- Adjust commitments that exceed capacity rather than assuming overtime.

- Track capacity consumed over the PI and correct if needed.

## FAQ

### Who prepares capacity?

Each team enters its availability; the RTE consolidates across the train.

### What if commitments exceed capacity?

Reduce scope, postpone items, or adjust capacity, but do not assume overtime.

### How long is a PI?

Often 8 to 12 weeks, meaning four to six iterations.

## Sitemap

- [Markdown sitemap](https://www.simpleworkload.com/sitemap.md)
- [XML sitemap](https://www.simpleworkload.com/sitemap.xml)
- [llms.txt](https://www.simpleworkload.com/llms.txt)
- [llms-full.txt](https://www.simpleworkload.com/llms-full.txt)