🔴 Timesheet Page Shows Incomplete Logs / 00:00 Hours
This issue has two possible causes — check both before escalating.
Case 1: Grace Period Exceeded
Symptom
Dashboard shows all logs as complete (e.g. 4 logs for a whole day), but the Timesheet page shows fewer logs and the total computes as 00:00.
Why this happens
The Timesheet page only counts a clock-out as valid if it falls within the 1-hour grace period after the scheduled shift end. A log with a clock-out beyond that window gets excluded from the Timesheet computation, even though it still appears on the Dashboard.
How to resolve it
- Check the Dashboard to confirm all logs exist and note their timestamps.
- Identify which log has a clock-out beyond 1 hour of the scheduled shift end.
- Confirm this is the log missing from the Timesheet — this is expected behavior, not a bug.
- Have the employee (or their TL) submit a manual correction/clock-out request for that log so it falls within the grace period.
Case 2: Missing Time In/Out Entry
Symptom
Timesheet shows 00:00 because one or more required punches are missing — not a grace period issue.
Why this happens
A complete log requires:
- Whole day shift: 2 Time In + 2 Time Out entries
- Half day shift: 1 Time In + 1 Time Out entry
If any of these required punches is missing (e.g. employee forgot to clock out, or a break-in/break-out wasn't logged), the Timesheet page can't compute total hours and shows 00:00.
How to resolve it
- Check the Dashboard/ATS logs to count how many Time In / Time Out entries exist for the day.
- Compare against the required count for their shift type (2 in/2 out for whole day, 1 in/1 out for half day).
- Identify which specific punch is missing.
- Have the employee (or their TL) submit a manual log request for the missing punch, with the correct/actual time.
Still not fixed? (applies to both cases)
If the Timesheet still shows 00:00 or incomplete hours after correction, escalate to IT/Ops with: employee name, PH ID, date, all logged times, and scheduled shift.
No Comments