Depending on the fact that the employee is scheduled to work or not the missing punch logic behaves differently as follows:  
*For an employee without a schedule or for add hoc punches outside of the schedule the work time will be generated only for paired clock punches since this is the only information that tells worked time
*For employees with schedules the worked time is generated by their schedule and clock punches will adjust this time 
*The following screens are designed to reflect the Missing Clock Punches:
**[WETMCP] - Review My Missing Clock Punches
**[WMTMCP]/[WSTMCP] - Review Missing Clock Punches

*There are new filters added to the Missing Clock Punches screen to allow user to see Day Details as follows:
**Missed Punch [Time Code|TIME_CODE]
**Only INs and OUTs
**No Punch on Prediction


*The page [Helper Time Rule|HELPER TIME RULES] lists time rules that may be used to assist with Missing Clock Punches. 

!!Missing Punches for Scheduled time
The identification of missing punches for scheduled time has two components:  

# In/Out prediction 
# Missing punch [time code|TIME_CODE]

In/Out prediction is based on the following information:
* Set up in [IDWR] (Details Tab)
** Track work punches toggle is ON
** We predict that will have an IN punch at the beginning of the shift and an OUT punch at the end of the shift
* Track meal punches toggle is ON
** We predict that will have an OUT punch before meal and an IN punch after the meal;
** This is usually set up in cases where meal time is unpaid, and an employee needs to punch out/in for lunch
*Gap in time between work times
**We predict an IN punch after each gap in time;
**By default the system considers a new shift if the gap between work times is more then 2 hours;
**If this gap in time needs to be overridden, please use [MAX BREAK TIME|TR_MAX_BREAK_TIME] rule.

*Note
  If business need requires uneven clock punches, the prediction will not help to identify missing punches. In this situation we recommend to set up the [MISSSED PUNCH|TR_MISSED_PUNCH] time rule as a second indicator for possible missing punches

* Below are the expected results when we track meal time. 

[{Image src='Track Meal Punch.jpg' width='600' align='center' link='attach/Track Meal Punch/Track Meal Punch.jpg'}]


__Note__ - Example #17 should be ignored in Clock Punch situation; it does not make sense here.

;Attention:
For Split Shift - if there is a need to clock IN/OUT for additional time on split time in order to have the time generated, that time needs to be scheduled because otherwise time for those clock punches will not be generated.
For example, clock IN at 2:00 pm and clock OUT at 4:00 pm; you need to add the time in split time (add an ad hoc time exception from 2 pm - 4pm), otherwise time for that clock punches will not be generated.

[{Image src='More Ex Track Meal.jpg' width='600' align='center' link='attach/More Ex Track Meal/More Ex Track Meal.jpg'}]
      
 As of 20081124 we support [Float Meal|FLOAT MEAL] functionality.
 In order to have in place this functionality, in [ITSS] meal time should be defined as “Float Lunch” 

[{Image src='Float Lunch.jpg' width='600' align='center' link='attach/Float Lunch/Float Lunch.jpg'}]