We designed Fingercheck to be a user-friendly DIY time and attendance software. However, we're more than aware that some of the lingo used within our software can be a little cryptic. Take for instance the terms 'punch notifications' and 'punch exceptions.' Unless you're familiar with the inner workings of time and attendance software, you're probably not sure what both mean in relation to each other. What are they and how do they relate?
 
Though slightly different, both are forms of punch alerts. A punch notification, when set up, will directly contact you via email, text message, or push notification when an employee does or doesn't perform a specific punch or a specific punch pattern. A punch exception is a subtle alert (basically a code) that flags the employee's time card so when you review your time data, you can see the exceptions. Both are meant as tools to help you stay on top of your employees' attendance.
 
 Here is a full and complete list further explaining the types of notifications and exceptions you can set up within Fingercheck:
 
 Notifications: (E-mail Alert/Text Message/Push Notification)

  • Punch: Receive a notification after an employee performs a punch.
  • No Punch: Receive a notification if an employee has not performed a punch at all for the day.
  • MissedOut: Receive a notification if an employee missed a scheduled out punch.
  • LongBreak: Receive a notification if an employee has surpassed their allowed break time (this notification operates based on the break policy you set up). The notification is triggered once they punch back in.
  • MaxHours: Receive a notification when an employee works beyond a designated amount of hours. This notification operates based on a policy you set up called a Max Hours policy. The system uses the policy as a cap or to throw an exception. After an employee punches out if the amount of hours exceeds whatever the limit is, the alert will trigger.
  • InEarly: Receive a notification if an employee punches in early based on schedule (which you create).
  • InLate: Receive a notification if an employee punches in late based on a schedule (which you create).
  • OutEarly: Receive a notification if an employee punches out early based on schedule (which you create).
  • OutLate: Receive a notification if an employee punches out late based on schedule (which you create).

Exceptions: (Notifications are displayed as a code flagging exceptions on time cards and reports -- the dashboard also displays exceptions, color coding them based on severity)

  • Unscheduled: An exception is triggered when a punch is made by an employee not scheduled to work.
  • InEarly/Late: An exception is triggered when an employee makes an early or late 'in' punch.
  • OutEarly/Late: An exception is triggered when an employee makes an early or late 'out' punch.
  • MissingInPunch: An exception is triggered when an employee hasn't punched in for the day (no schedule needed).
  • MissingOutPunch: An exception is triggered whenever an 'in' punch is not accompanied by an 'out' punch.
  • ScheduledAbsence: An exception is triggered if there are no punches for an employee who is scheduled to work, signaling that they are absent.
  • MissedPunch: An exception is triggered if an employee has not performed a punch at all for the day.
  • MissedStartBreakPunch: An exception is triggered if an employee with a scheduled break does not punch out at their scheduled break start time (needs a break policy).
  • MissedEndBreakPunch: An exception is triggered if an employee with a scheduled break does not punch in at their scheduled break end time (needs a break policy).
  • LongBreak/ShortBreak: An exception is triggered if an employee takes a long or short break (needs a break policy).
  • LongMeal/ShortMeal: An exception is triggered if an employee takes a long or short meal (needs a break policy).
  • OverHours: An exception is triggered if an employee exceeds their maximum hours -- after an employee punches out, if the amount of hours they have worked exceeds their limit, the alert will trigger (needs a max hours policy).
  • UnderHours: An exception is triggered if an employee does not meet their scheduled hours -- after an employee punches out if the amount of hours they have worked is under their limit, the alert will trigger (needs a ? policy).
  • StrictScheduleBeforeShiftStart: An exception is triggered if you have strict time rounding set up in the employee's schedule to round punches before the start of a shift.
  • StrictScheduleAfterShiftEnd: An exception is triggered if you have strict time rounding set up in the employee's schedule to round punches after the end of a shift.
  • NoBreak: An exception is triggered if an employee does not take a break (needs a break policy).
  • NoMeal: An exception is triggered if an employee does not take a meal (needs a break policy).
  • MissedScheduledInPunch: An exception is triggered if an employee misses a scheduled 'in' punch.
  • OverScheduledHours: An exception is triggered if an employee is over their scheduled hours.
  • UnderScheduledHours: An exception is triggered if an employee is under their scheduled hours.
  • MissedScheduledOutPunch: An exception is triggered if an employee misses a scheduled 'out' punch.
  • StrictScheduleBeforeShiftEnd: An exception is triggered if you have strict time rounding set up in the employee's schedule to round punches before the end of a shift.

Additionally, Fingercheck can be programmed to send you a daily report containing all the exceptions triggered for the day. You can request a technician to help you with this, and they can set up the report to be sent to whoever you'd like at whichever time you'd like.

Did this answer your question?