> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to plan project capacity across a team
- URL: https://blog.jestor.com/plan-project-capacity-across-a-team/
- Published: 2026-09-16T18:53:39.000Z
- Updated: 2026-09-16T18:53:39.000Z
- Author: Bruno Bannach

To **plan project capacity**, you need two things visible at once: what is committed per period, and how much each commitment actually demands. In **Jestor**, projects can be viewed by date and by complexity, so an overloaded week is visible before it becomes one.

## Why capacity planning fails in practice

Most teams plan by counting projects. Five projects in a week sounds manageable until three of them are large and two of them share the same specialist.

Counting treats every project as equivalent, which is the assumption that causes the overload.

What proper visibility prevents:

- Several large projects landing in the same week
- One specialist committed across three parallel projects
- Deadlines accepted without checking capacity
- Overload discovered when work is already late
- No basis for negotiating a date with a client

## What to track for capacity

| Element            | What it tells you                  |
| ------------------ | ---------------------------------- |
| Project dates      | When commitments land              |
| Complexity or size | How much each demands              |
| Assigned people    | Who is committed where             |
| Required skills    | Whether one person is a constraint |
| Contracted hours   | The ceiling per engagement         |
| Hours consumed     | Whether estimates hold             |

## Step by step to build the view

1. **Record a complexity or size field** per project, even if it is a rough three point scale.
2. **Put projects on a calendar** by their delivery date.
3. **Group by assigned person**, to see individual load.
4. **Look for clustering**, both in dates and in specific people.
5. **Redistribute before accepting new work**, not after.
6. **Compare estimated against consumed hours** at delivery.
7. **Adjust your sizing scale** based on where estimates proved wrong.

## Why a rough size estimate beats none

Teams often resist estimating because precise estimation is hard. It does not need to be precise. A three point scale of small, medium and large is enough to reveal that four large projects are due the same week, which is the decision the view exists to support.

## Why choose Jestor

In **Jestor**, projects can be viewed as a board, a calendar by date or a dashboard by complexity and priority, all on the same records. Hours contracted and consumed sit on the project card with the remaining balance calculated automatically, and grouping a board by assigned person shows individual load without building a separate view.

## Frequently Asked Questions

### Do I need precise estimates to plan capacity?

No. A rough size scale is enough to reveal clustering. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Can I see load per person?

Yes, by grouping a board on the assigned user field.

### How do I know whether my estimates are realistic?

Compare estimated against consumed hours at delivery and adjust the scale.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.