> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/accreditation/time-tracking.md).

# Time tracking

Everybody has to put in their hours

The time track feature on our website allows moderators to easily track people's activities, whether it's for a specific [job](https://docs.eventication.com/event/planning/stations/substations/jobs.md) or general monitoring. Moderators can start and end tracking sessions with a simple click on a button.

The buttons to start, pause, resume or stop time tracks are placed at strategical places throughout the platform:

* on the index page of the time tracks (pause, resume and stop sit in the row menu)
* on the [check-in page](https://docs.eventication.com/event/accreditation/check-in-out/person-checkin-page.md) of each person (in the row menu of the "Time tracks" card)
* on the shift page of a certain job
* on the [location page](https://docs.eventication.com/event/accreditation/attendance/members.md#location) in the accreditation attendance tab

This feature provides a streamlined and efficient way to track time and monitor activities.

{% hint style="info" %}
After a time track is finished, the moderator can mark whether the work was **completed or not** and add a description.
{% endhint %}

{% hint style="warning" %}
You can only have **one** time track running at the same time per person.
{% endhint %}

### Pauses

A running time track can be paused and resumed, as many times as needed. The worked time of a time track is the time between its start and its stop **minus its pauses**, and that is the duration you see everywhere: on the time track page, in the lists, on the check-in page, on the kiosk, on the scan app and in the export. The time track page also shows the gross duration, the paused time and every pause with its start and end.

A paused time track is still a running time track: it keeps its "tracking" badge and gets a "paused" badge next to it, it still counts in the tracking numbers, and the person still cannot start a second one. Stopping a paused time track needs no resume first: the pause ends at the stop time and is shown as "until stop".

Pause and resume are single clicks, without a comment or confirmation. You find them wherever you find the stop button: in the footer of the time track page, in the row menu of the time track lists and of the "Time tracks" card on the [check-in page](https://docs.eventication.com/event/accreditation/check-in-out/person-checkin-page.md), in the row menu on the [location page](https://docs.eventication.com/event/accreditation/attendance/members.md#location), on the camera page, on the kiosk and on the scan app.

Moderators with the permission to edit time tracks can also add, change or remove pauses afterwards, on the edit page of the time track, with their own start and end times. Pauses cannot overlap, cannot start before the time track started and cannot end after it stopped.

Pausing is off by default. Switch it on per event in the [time track settings](https://docs.eventication.com/event/accreditation/settings/time-tracks.md). While it is off, no pause buttons are shown and existing pauses stay visible.

### New

Click the "*New*" button to start a new time track.

### Camera

Use your camera to scan a wristband via the <img src="https://55689121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMH0qx2kDusOMcs9TvihF%2Fuploads%2Fgit-blob-92fcef96a101f8e17fea2d499edb71830f393ed9%2Fcamera.jpg?alt=media" alt="" data-size="line"> button. After this you can start your camera and start registering new time tracks, or find one and stop it, pause it or resume it.

If you have any issues with your camera permissions, check our [help](https://docs.eventication.com/event/misc/camera-access.md) page.

### Export

If you have the permission to export time tracks, the download button in the header exports every time track of your event to a CSV file. The export opens in a window that shows you its progress, and once the file is ready a download button appears in that same window. You no longer have to wait for an email with a link.

The file contains, per time track: the person and the form and list they belong to, the job that was worked on, when it started and who started it, the start comment, the status (tracking, paused or finished), the duration in minutes (net of pauses), the gross duration in minutes, the paused minutes, the number of pauses, the pauses themselves as "from–to" times (an open pause ends in "…", a pause that was ended by the stop is marked "(stop)"), when it stopped and who stopped it (time tracks that were stopped automatically by the platform are marked as such), the stop comment, whether the work was completed, how many minutes that person was checked into the event on that day, and their tags.

Time tracks that are still running or paused have "-- ongoing --" in the four stop columns; their duration columns hold the values at the moment of the export.

An example, the header line and a finished time track with two pauses, the second one ended by the stop:

```
Who or what;Category;Form;List;Work;Start;Started by;Comment for start;Status;Duration in minutes;Gross duration in minutes;Paused minutes;Number of pauses;Pauses (from–to);Stop;Stopped by;Comment for stop;Work completed?;Minutes checked into event on day;Tags
Jane Doe;Member;-;-;Bars - Bar 10 - Dishes;September 25, 2026 20:17;John Smith;;finished;130;180;50;2;20:47–21:17, 22:57–23:17 (stop);September 25, 2026 23:17;John Smith;;true;123;crew
```


---

# 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://docs.eventication.com/event/accreditation/time-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.
