Understanding Trackforce Schedule Exceptions

In this article we will go over the various scenarios encountered with time punches processed from Guardtek / m-Post and into Smartforce.

 

How to Access the Schedule Exceptions Page

To access the Schedule Exceptions page:

1. Log onto the Trackforce Valiant web portal as an Admin or Supervisor.

2. Hover over the TLM Module and click Schedule Exceptions in the Time Collection section. 

mceclip0.png

3. The exceptions for the current week will be displayed on the following page.  To view the exceptions before that clear the filter on the left side.

mceclip1.png

Types of Exceptions

Punch Was Too Early

If the punch action in question was recorded too early, the following message will be displayed:

mceclip2.png

In this particular example, the Clock Out action recorded at 5:28AM on 9/1/22 was done too early for the employee's scheduled shift.  This exception is usually generated when the time associated with the punch is outside of the configured Allow Range values for the site in question.  For more information on configuring the Allow Range rules in Smartforce please see the following article:

Understanding Punch Rules in Smartforce

 

Punch Was Too Late

If the punch action in question was recorded too late, the following message will be displayed:

mceclip4.png

In this particular example, the Clock In action recorded at 7:04AM on 8/30/22 was done too early for the employee's scheduled shift.  This exception is usually generated when the time associated with the punch is outside of the configured Allow Range values for the site in question.  For more information on configuring the Allow Range rules in Smartforce please see the following article:

Understanding Punch Rules in Smartforce

 

Clock In Punch Already Exists

If a Clock In punch action was recorded at a time when the employee is already punched in for the shift in question, the following message will be displayed:

mceclip5.png

In this particular example, the Clock In action recorded at 12:06PM on 9/1/22 was recorded when another Clock In action had already been previously recorded for the same shift.  This exception is usually generated when the employee accidentally punches in for their shift more than once.

 

Already Clocked Out

If a Clock Out punch action was recorded at a time when the employee has already punched out for the shift in question, the following message will be displayed:

mceclip6.png

In this particular example, the Clock Out action recorded at 11:00PM on 8/31/22 was recorded when the employee was already clocked out of the scheduled shift.  This exception is usually generated when the employee accidentally punches out more than once at the end of their shift.

 

No Schedule Found

If a punch action was recorded at a time when no shift details exist for that employee at that time in Smartforce, the following message will be displayed:

mceclip7.png

In this particular example, no scheduled shift details could be associated with the Clock Out action recorded at 4:36PM on 8/31/22 by the employee in question.  There are a number of scenarios that can cause this type of exception to occur, however in most cases the first step that should be taken is to check the scheduled shift details on the date in question for that employee and verify whether they are successfully punched in and out at that point in time.

 

Was this article helpful?
0 out of 0 found this helpful

Articles in this section