Displaying suggested times

In most cases, the HTML Clock presents “suggested” time values for each scheduled swipe. Under normal circumstances, the suggested times reflect the timestamp of the scheduled swipe record itself.

In these circumstances, the suggested times do not reflect the timestamp of the scheduled swipe record:

  • If a scheduled swipe has a null timestamp, no suggested time is possible. In these cases, the employee is presented with a “?” value.
  • If an employee has missed their Meal Start swiping event and performs a Meal End initiating swiping event, the HTML Clock will present a suggested meal start time equal to the current time minus the duration of the employee’s scheduled meal break. For example, if an employee is scheduled for a meal break from 12:00-13:00 and the employee swipes a meal end at 13:30 without having previously swiped their meal start, the HTML Clock will present the missed meal start with a suggested time of 12:30.
    Note: This updating of the meal start time is only possible when the meal-related scheduled swipes for the charge date being evaluated are not null. If they are null, it means the employee’s swiping activities thus far are so off-schedule that the originally scheduled meal times no longer apply. When this occurs, the HTML Clock instead suggests a meal start time equal to the timestamp of the initiating meal end minus thirty minutes.