Solution created for issue described below implemented 5/1/2015
---------- Forwarded message ----------
From: CalTime <firstname.lastname@example.org>
Date: Thu, Mar 12, 2015 at 3:55 PM
Subject: Important Information: Missed Punch False Error Report in CalTime
To Berkeley employees:
Some non-exempt ‘real-time’ employees (those required to report in real time when they start/stop work) and their supervisors may have noticed a false missed punch error that appears on the CalTime timecard when the employee actually did punch in and out correctly. We believe that this only impacts employees working multiple short shifts within the same day. This is a known technical issue with CalTime with a solution being determined to prevent this error from occurring. The CalTime team will notify you once the issue has been resolved.
WHAT YOU NEED TO KNOW:
The current miss-interpretation of the punches typically occurs when there is greater than 4.5 hours of time between the end of a shift and the beginning of the next shift in which the CalTime system thinks a punch from a meal break is missing. This error may be common for real-time employees with split shifts that are greater than 4.5 hours apart.
For Example: An employee punches ‘in’ at 7:00am and ‘out’ at 8:00am, then punches ‘in’ again at 1:00pm and ‘out’ at 2:00pm. The ‘out’ punch at 8:00am is seen as an ‘out’ for a meal break, and no ‘in’ from the meal break occurred within 4.5 hours.
Currently if two shift segments are within 4.5 hours of each other (or less) then the punches line up correctly in CalTime, and no error is recorded.
WHAT YOU SHOULD DO:
If a missed punch error appears on the timecard, the ‘real-time’ employee should notify their Supervisor immediately in order to have them edit the punch in CalTime.
Supervisors of real-time employees should continue to review time-cards and correct missed punches throughout the pay period. To quickly find your employees with missed punches (and to fix them, as necessary), use the Timecard Exception Genie. You can find instructions here.
We appreciate your patience as we work to resolve this issue.
The CalTime Team