> 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/finanzen-1/kva/planning.md).

# Budget planning

![](/files/30b71f2bace8e9eeee33d1855c22081f50a3c4c9)

Planned budgets for agency service and external service can also be defined on the estimate. They behave exactly the same as on the job.

{% content-ref url="/pages/0e3aa535369a9c8afa84ff961796bcfe144fe2a9" %}
[Job planning](/die-agenturverwaltung-en/projektverwaltung-1/projekte/planning.md)
{% endcontent-ref %}

If the estimate belongs to a job, the Planned Budgets of the estimate are also displayed in the job.

If the estimate does not yet belong to a job and is later assigned to a job, the Planned Budgets of the estimate are automatically carried over into the job. The same happens if the estimate is later assigned to a different job.

## Application scenarios

If I have switched the budgets for agency service and external service to "Planned Budgets" in the "Planned Budgets" tab of my job, the report for my job shows the values for my agency service, working time and external service budgets as the sum that I have stored here on the estimate in the "Planned Budgets" tab.

{% hint style="info" %}
In this way I can define the available agency service and external service budget of my team, regardless of the price at which I offered the service to the customer.
{% endhint %}

Even if a job does not consider the Planned Budgets but instead the agency service and external services calculated in the estimate, it can make sense to document the Planned Budgets of the estimate before the estimate is created.

This way it becomes clear which efforts will be incurred in implementing the estimate and pricing the offer becomes easier as a result.


---

# 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/finanzen-1/kva/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.