> 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/attendance-tracking.md).

# Attendance tracking

Legally compliant time tracking

Die Agenturverwaltung offers the option of pure attendance recording to meet legal requirements. If employees only record their attendance and do not make any entries in the time tracking, this can be used to maintain an hours account, but it does not create transparency about which internal efforts were spent on which job. Nevertheless, when the function is enabled both attendances can be recorded (via a button in the main menu) and times can be booked to jobs. However, it would no longer be necessary to book times to internal jobs to fill the hours, since only the times recorded by the attendance recording are decisive for the hours account.&#x20;

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

## Recorded attendances on the dashboard

{% embed url="<https://share.vidyard.com/watch/htrVMVrJUVhqyFazPzYytY>?" %}

## Switching from time tracking to attendance recording

The switch is made via Settings -> Time Tracking -> Enable Attendance Recording

If time tracking is switched to attendance recording during ongoing operations, a deficit occurs in the hours account. The reason for this is that from the moment of the switch, project-related time tracking is no longer taken into account in the hours account. The system therefore has no recorded working times yet, but still subtracts all working days according to the employment contract from the hours account. To balance the hours account, an adjustment must be recorded. This adjustment results from the sum of the hours account BEFORE the switch + the difference after the switch.&#x20;

An example: Maria's company switches to attendance recording. Before the switch, Maria's hours account shows a surplus of 66 hours and 10 minutes. After the switch it shows a deficit of 450 hours. To balance the hours account, an adjustment of 516 hours and 10 minutes must now be recorded. It is now back to the previous level and Maria can track her working time from here using the attendance recording.

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

## Viewing attendances

Under Reports -> Attendances a list of all attendances can be viewed. The entries can also be edited here.

<figure><img src="https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2Fvr1LvroPjVF7HDODxLws%2FAnwesenheitsliste.jpg?alt=media&amp;token=ff3defdc-7dd7-4d73-a697-c9032946a6b5" alt=""><figcaption></figcaption></figure>


---

# 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/attendance-tracking.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.
