Attendance History
Attendance History is a log of every employee clock-in and clock-out punch, with time, location, and time-tracking point.
How to Access
Menu: Time Tracking → Attendance History.
Route: /time-tracking/history
Quick actions:
Overview
Every card tap or code entry at a time-tracking point creates a transaction: employee, date, time, event (arrival or departure), location, and point. This page shows those transactions as they are — without matching them against a work schedule.
That is why history is the first place to check when the Attendance Sheet looks wrong: it answers the question "was there a punch at all?".
Punches for today are shown by default.
Filters
| Filter | Description | Required |
|---|---|---|
| Date from | Start of the period, to the minute | Yes |
| Date to | End of the period, to the minute | Yes |
| Employee | Search by employee name | No |
| Event | All, Arrival, or Departure | No |
| Sort by date | Descending (newest first) or ascending | No |
| Rows per page | 20, 50, or 100 | No |
List Columns
| Column | Description |
|---|---|
| # | Row number |
| Date | Punch date |
| Time | Punch time |
| Employee | Who punched |
| Event | Arrival or Departure |
| Location | Location the point belongs to |
| Checkpoint | The checkpoint where the punch was made |
Rows are colour-coded by event: arrivals green, departures red. The total number of matching transactions is shown above the table.
Tips
- Consecutive duplicate punches (two arrivals with no departure between them) are a common cause of an inflated attendance sheet. Sort ascending and review the whole day.
- If an employee has no records at all, verify that they have an identifier issued and are linked to a time-tracking point.
- The employee filter matches on substring — part of a last name is enough.
Related
- Attendance Sheet — hours worked with schedules applied
- Employees at Work — who is on shift now
- Visits (Time Tracking) — visits report for a period