> For the complete documentation index, see [llms.txt](https://docs.timecord.dev/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.timecord.dev/docs/guide/statistics-and-time.md).

# Statistics & Time

This page explains how TimeCord measures and groups time, and the automations that keep the numbers clean. Most of it is set once and then works on its own.

### How tracking works

A **session** starts when a member clocks in (the **Clock in** button, or an admin/automation starting it) and ends when they clock out. Each finished session is stored as a start/end pair. Manual adjustments made with `/time` or `/timerequest` are stored separately so they can add or subtract time without affecting real sessions.

`/info`, `/leaderboard` and `/export` all report four totals: **daily**, **weekly**, **monthly** and **all-time**.

### Timezone

Daily, weekly and monthly totals depend on where the day boundary falls, so TimeCord groups them in a timezone you choose.

* Set it with `/timezone <IANA name>`, for example `Europe/Berlin` or `America/New_York`.
* The default is `UTC`.

{% hint style="warning" %}
If you leave this on `UTC` but your team is in another timezone, a shift that ends just after midnight local time may count toward the next day. Set your real timezone so daily and weekly totals line up with your team's calendar.
{% endhint %}

### Week start

Weekly totals need to know which day a week begins on. Set it with `/weekstart <day>` (Monday through Sunday). This only affects how weekly stats are grouped; it does not change anyone's recorded time.

### Warnings

Warnings created with `/warn` carry an expiry. A warning is **active** until its duration passes; after that it stops being counted or shown, and TimeCord removes expired warnings automatically in the background. `/info` and `/warn show` only ever show active warnings.

### Automatic clock-out (forgotten shifts)

People forget to clock out. If you enable **auto clock-out** in the dashboard (**Settings → General**, the "abmelden" option), TimeCord closes any session that has been open longer than the limit you set, records the time up to that point, and removes the on-duty role. This keeps a forgotten shift from running for days.

### History and long-term storage

TimeCord keeps recent sessions on the member so daily, weekly and monthly views stay fast, and it moves sessions older than a few months into long-term storage. Your all-time totals stay correct either way; nothing is lost. `/role reset` clears both recent and stored time for the selected members.

### Audit log

Every administrative action (hiring, dismissing, warns, manual time changes, automatic clock-outs, and more) is written to a permanent audit log. This is kept even if you delete the Discord log channel, so there is always a record of what happened.