Skip to main content
All CollectionsTime & LaborExceptions
Punch Alerts 101—A Comprehensive Breakdown of Notifications and Exceptions
Punch Alerts 101—A Comprehensive Breakdown of Notifications and Exceptions

A complete list explaining the types of notifications and exceptions you can set up within Fingercheck.

Jeffrey Mo avatar
Written by Jeffrey Mo
Updated over 3 months ago

Some terms such as punch notifications and punch exceptions may not be familiar to you. Though slightly different, both are forms of punch alerts.

  • A punch notification, when set up, contacts 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.


Notifications

Notifications send an email alert, text message, or push notification. The following options are available when creating an alert rule for an alert policy (SETUP tab > Policies > Alert Policies):

  • 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 Maximum 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 a 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).

  • PunchPhoto: Receive a notification to verify a photo after an employee punches.

  • NoMask: Receive a notification if an employee punches in without a mask.

  • HighTemp: Receive a notification if an employee punches in and has a high temperature.


Exceptions

Exceptions are displayed as a code-flagging exceptions on time cards and reports. The dashboard also displays exceptions (color coding them based on severity). The following options are available when creating an exception policy (SETUP tab > Policies > Exception Policies):

  • 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.

  • 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.

  • MissedScheduledOutPunch: An exception is triggered if an employee misses a scheduled out 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.

  • 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.

  • InOutJobMissMatch: An exception is triggered if the employee punches in to the wrong job.

  • InOutTaskMissMatch: An exception is triggered if the employee punches in to the wrong task.

  • UnscheduledShift: An exception is triggered if the employee punches in for an unscheduled shift.

  • UnscheduledDay: An exception is triggered if the employee punches in for an unscheduled day.

  • PunchPhotoNoMatchWithConfidence: An exception is triggered if the employee punches in and their photo doesn't match with confidence to the facial recognition photo in their profile.

  • PunchPhotoNoMatchWithMediumConfidence: An exception is triggered if the employee punches in and their photo matches with medium confidence to the facial recognition photo in their profile.

  • PunchPhotoNoMatchWithLowConfidence: An exception is triggered if the employee punches in and their photo matches with low confidence to the facial recognition photo in their profile.

  • PunchPhotoNoFaceDetected: An exception is triggered if the employee punches in and their photo is empty or doesn't show their face clearly.

  • StrictScheduleAfterShiftStart: An exception is triggered if you have strict time rounding set up in the employee's schedule to round punches after the start of a shift.

  • NotScheduledJob: An exception is triggered on the employee's timecard if an employee punches in for a shift and selects a job that is different from the job assigned to their scheduled shift.

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.


Thank you for using Fingercheck. If you have any questions on this article's topic, you can reach out to our team at 1-800-610-9501, or use the chat option below.

Did this answer your question?