ANTE User ManualTime Tracker Logs
Time Tracker Logs is the manager-facing view of everyone's Time Tracker activity — the sidebar widget employees (and even non-employee accounts, like a project manager) use to time how long they spend on a task. The browse table shows one row per employee per day; clicking a row opens every segment of that day.
Every figure on this page is task-allocation time — minutes from Time Tracker's closed segments, tracked purely for the sake of knowing where work went. It never reconciles with attendance/DTR time and must not be read as payroll hours. A segment that is still running is excluded from the totals until it closes.
Accessing Time Tracker Logs
- In the sidebar, go to Manpower.
- Click Timekeeping Logs to expand the menu.
- Select Time Tracker Logs.
Permission required: the Time Tracker Logs permission (MANPOWER_TIME_TRACKER_LOGS_ACCESS). If the menu item is not visible, ask your administrator to grant it.
The Time Tracker Logs List
The table shows activity from the last 7 days by default, one row per employee per day.
Columns
| Column | Description |
|---|---|
| Employee | Name, avatar, and employee code (falls back to the username for accounts with no employee record) |
| Date | The calendar day the segments fall on (the server's local day) |
| First Start | The time the day's first segment began |
| Last End | The time the day's last segment closed, or a Running badge if a segment is still open |
| Tracked Time | Total minutes across the day's closed segments only — never a running estimate |
| Tasks | Number of distinct tasks worked on that day |
| Segments | Number of tracked stretches of work, with the number of sessions shown underneath (see Segments and Sessions) |
| Status | Completed, Running, or Auto-closed — see Understanding Status |
Filters
- Date range — defaults to the last 7 days
- Employee
The browse window cannot span more than about 92 days. Picking a wider range keeps your start date and pulls the end date in to fit.
Search
Search by Employee Name or Employee Code.
Understanding Status
| Status | Meaning |
|---|---|
| Completed | Every segment for the day closed normally — none is still running and none was auto-closed. |
| Running | At least one segment for the day is still open — the employee has not stopped Time Tracker yet. |
| Auto-closed | At least one segment was closed automatically rather than by a normal Stop or Switch Task action — either the idle prompt or the nightly sweep closed it. Takes priority over Running when both apply. |
Opening the Day Detail
Click any row to open the day's detail dialog for that employee. It shows the employee's name and code, the date, the day's Total (closed minutes only), and every segment worked that day.
Each segment shows:
- The task title (or "Untitled task" if the task has none)
- Its start and end time — end shows Running with a live elapsed timer (updating roughly every 30 seconds) if the segment has not closed yet
- The project and/or engagement the task belongs to, when set
- A mode chip — Attendance (a real time-in/time-out punch), Kiosk (the employee was already clocked in at a facial kiosk), or Task-only (no attendance record at all, e.g. a non-employee account)
- An Auto-closed badge on segments the system closed rather than the employee — see Segments and Sessions below
- Its duration on the right, or the live elapsed time while still running
If the employee tracked nothing that day, the dialog shows "No tracked time on this day".
Segments and Sessions
A segment is one continuous stretch of work on a single task. A session is one continuous run of Time Tracker from Start to Stop — if the employee switches tasks mid-session without stopping the timer, that one session produces several segments, one per task. The Segments column shows the segment count with the session count underneath, so you can tell "5 segments, 1 session" (five task switches in one sitting) apart from "5 segments, 5 sessions" (five separate times the employee started the timer).
A segment is auto-closed instead of stopped normally in two cases:
- Stopped at last activity — the employee answered the idle prompt with "I stopped a while ago," so the segment (and the attendance punch, if any) closed at their last recorded activity instead of the moment they answered.
- Auto-closed at last activity — the employee never answered the idle prompt, so the nightly sweep truncated the segment at its last recorded activity.
Both reasons show as the same Auto-closed badge in the browse table's Status column; the day detail dialog spells out which of the two happened for each segment.
About These Figures
Tracked Time here comes entirely from Time Tracker's own closed segments — it is a record of task allocation, not a time clock. It is deliberately decoupled from attendance/DTR and must never be presented as, or substituted for, payroll hours. A segment still running contributes nothing to the day's total until it closes, so a day that looks "short" may simply still be in progress.
For the employee-facing side of Time Tracker — starting, switching, and stopping a timer — see Track Work Time.
Troubleshooting
Time Tracker Logs is not visible in the sidebar. You do not have the Time Tracker Logs permission. Ask your administrator to grant it.
An employee's day never shows Completed. Check the Status column — a lingering Running status means a segment is still open (the employee has not stopped the timer), and it will either close normally or get picked up by the idle prompt or the nightly sweep and turn into Auto-closed.
Tracked Time does not match the employee's attendance hours. That is expected — see About These Figures. Tracked Time is task allocation, attendance/DTR is the payroll source of truth, and the two are never meant to match exactly.