> For the complete documentation index, see [llms.txt](https://wiki.dieagenturverwaltung.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/projekte/planning/capacity-planning.md).

# Capacity planning

Die Agenturverwaltung allows us to define at the job how many hours of a specific employee I plan for my job per week, month or day.

{% hint style="info" %}
The examples here refer to weekly planning. If you want to plan capacities in your company **by day** or **by month** please contact our support, we will switch the module for you:\
<info@dieagenturverwaltung.de>
{% endhint %}

<figure><img src="/files/626ca59418842a558274862a32b76d1ef8a99b1a" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}

## Why plan capacities?

Planning upcoming efforts on the job helps answer the following questions.

1\) Do the hours I will need from the team to implement my job fit my budget?

2\) Which colleagues even have time to work on my job?

3\) Are certain colleagues, teams or trades over- or underutilized?

4\) What is the completion status of my job?

It is *not* suitable for describing a weekly plan with detailed tasks. For that, [tasks](/die-agenturverwaltung-en/vorgaenge-1.md).
{% endhint %}

{% embed url="<https://youtu.be/2YPTv1XATqE>" %}

## The planning view on the job

Assuming we have an approved estimate in a job, our capacity planning initially looks like this:

<figure><img src="/files/38473e2feccb292c93392e8fc340927a1de91847" alt=""><figcaption></figcaption></figure>

No people are planned in this job yet, however we see that some hours have already occurred in the past (this value results from time tracking entries for this job). We also see how the hours incurred relate to the time budget that results here from our estimate.

<figure><img src="/files/460f7adb7c3c4e7608109b05d09155c56690a410" alt=""><figcaption></figcaption></figure>

If I add a person - here Maria Muster - I can see how many hours per week she is planned for my job and (smaller below) how many hours are still available to me at most for my planning in this job.

Important: The planning always refers to future periods (including this week) and is defined in weekly hours of a specific person for a specific job.

<figure><img src="/files/24e459f4c86ab52f06b39f1f3e877595be8a1548" alt=""><figcaption></figcaption></figure>

Now Maria has been scheduled for the next three weeks with 12 hours each.

{% hint style="info" %}
**Tip**

You can navigate between the values using the arrow keys
{% endhint %}

I see in the progress bar below that 36 h are now planned for this job in the future.

If my planning were finished here, that would mean I have completed 66% of the job, which results from the 36 h still to come. In this case I would only need about half of my estimated budgets.

Next we add Rüdiger to our job.

Rüdiger is only available for 3 more hours in week 52 - he is on vacation, the week has a public holiday and he is also already scheduled on other jobs.

The field is highlighted yellow because less than 20% of Rüdiger's available capacity can still be used for this job.

<figure><img src="/files/a2870515d98da2456e6d952dc32dd3bffb81eec5" alt=""><figcaption></figcaption></figure>

I can still schedule Rüdiger with 8 instead of 3 hours on my job, but that means Rüdiger would have to work overtime in week 52.

## Other views of the same data

### Dashboard tile

<figure><img src="/files/7026d409d6da1a42e1823f8ff33ec8462380a46d" alt=""><figcaption><p>Example of a user scheduled on two jobs</p></figcaption></figure>

### Team overview

How the utilization of the entire team looks is shown in the view under Reports > Team capacities

### Jobs of a user

Which jobs a particular user is involved in can be displayed and edited in the "capacity planning" tab in the user management in the details of a particular user.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/projekte/planning/capacity-planning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.