> 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/reporting-in-der-projektverwaltung.md).

# Reporting in job management

Both on the customer, customer account and also on the job we find the most important metric in the "Report" tab.

{% embed url="<https://youtu.be/PfAE57cMbWg>?" %}

## agency service

This chart shows us how much of our agency service budget we have already used and how much budget - in the form of working hours - is still available to us.

The remaining hours quota is calculated from the hours incurred on the job so far. If the job continues at about the same pace, we would therefore have roughly 132 hours remaining here.

![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-La4YdZ1Gw5iHapqZfIo%2F-MQLRSCytY7nIfGMcICC%2F-MQLRm5NIhEvrptl35q5%2Fclip2.jpg?alt=media\&token=fd44060d-c3ff-4431-91cd-6d003cf962ad)

If no hours have yet been recorded on a job, this value is calculated from the average hourly rates of the price list in this context.

The value may also depend on the performance period selected above. For example, if an estimate with a performance period of one year included art direction calculated at EUR 12,000, this budget is distributed evenly over the performance period. For March, for example, only EUR 1,000 would then be available for art direction.

## external service

This chart shows us how much external service budget we still have and how much of it has already been used.

The value may also depend on the performance period selected above. For example, if an estimate with a performance period of 3 months included an external service value of EUR 3,000, this budget is distributed evenly over the performance period. For one of those three months, only about EUR 1,000 would then be assumed as budget.

<figure><img src="https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2FyRDUcPeFG7CfsZJt58kJ%2Fbeauftragtes_volumne.png?alt=media&amp;token=b7dbdcf1-fd0b-47e1-8d4c-5270f7a8fa50" alt=""><figcaption></figcaption></figure>

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

{% embed url="<https://www.youtube.com/watch?v=T48sakiPuRQ>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/reporting-in-der-projektverwaltung.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.