> 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/zeiterfassung-1.md).

# Time tracking

In this chapter, we explain the functions of time tracking and give you useful tips on the topic.

![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-La4YdZ1Gw5iHapqZfIo%2F-MRDw-CM1AF_17N-e5OS%2F-MRDw8WwALv2UEvsLj-m%2FMaschine05.png?alt=media\&token=a04848de-3b46-41c4-8da8-da2957e2419b)

Die Agenturverwaltung supports the following three ways to record working time:&#x20;

* **Timer:** For employees who switch back and forth a lot between tasks and work on different jobs throughout the day.&#x20;
* **Weekly view** For employees who prefer to record their times all at once at the end of a week or month&#x20;
* **Classic list:** The classic for anyone who wants to organize their working time blocks in a list

On the subpages you will find information and instructions on the types of time tracking

## Why time tracking at all?

The reasons for introducing time tracking are varied.

The most common reason is that recording work performed is simply necessary, for example in order to bill fee-based work based on effort.

However, time tracking can also be useful for learning from the numbers. It can be used to derive how profitably work is being done, and whether too much time may be invested in certain activities. **More information on this can be found in our** [**blog post**](https://www.dieagenturverwaltung.de/de-de/blog/3-tipps-bei-der-einfuhrung-der-zeiterfassung) **on this topic.**

{% @arcade/embed flowId="AhsfRmca60blCH4mw1m3" url="<https://app.arcade.software/share/AhsfRmca60blCH4mw1m3>" %}

## **Time tracking settings**

Functions in which users can record their working times can be configured:

{% content-ref url="/pages/6ad60844b9e6dcb9e9361a7bd64c4a76331d1c90" %}
[Functions](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/zeiterfassung/funktionen.md)
{% endcontent-ref %}

Configure recurring activities for time tracking and evaluate:

{% content-ref url="/pages/42834772b8b095b50b1bb44f01a75cc43d410262" %}
[Activities](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/zeiterfassung/taetigkeiten.md)
{% endcontent-ref %}

Which days are not worked in the company? Configure local holidays here:

{% content-ref url="/pages/0d7b97619410e6a29cdcd2439245dc2c448ea6c2" %}
[Holidays and company vacations](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/absences/feiertage-und-betriebsferien.md)
{% endcontent-ref %}

Configure a user's agreed weekly working time:

{% content-ref url="/pages/abf4d83ce064180263ef732980bd10587c42bbc3" %}
[Edit users](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/benutzerverwaltung/benutzer/benutzer-bearbeiten.md)
{% endcontent-ref %}


---

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