Policy Overview
Policy Overview
This document will reference individual settings for each section and tab on the Policy Update Form.
General Section
The General Section of the Policy Update Form includes basic settings such as Policy Description, employee tenure related settings which permit employees to automatically be moved from policy to policy based on the length of their employment with the company, and Pay Cycle Related settings which define Pay Period date ranges for the respective policy.
REQUIRED CONFIGURATION: The General Section, including settings on both the General Tab and Pay Cycle Tab, must be configured for every policy.
General Tab
Policies can be grouped together in such a way that employees will be automatically moved from one policy to the next after they have been with the company for a certain length of time.
Name The policy name is listed in the Policy Table and should describe the group of employees who will be assigned to the policy.
Class â A class is a group of policies. All policies in a single group must be assigned to the same class.
Default Class The default class refers to a secondary group of policies. If an employee assigned to the policy should be ineligible for all policies within the current class (or group) the software will search the default class for a policy matching the employeeâs tenure.
Employees Working From â The minimum length of time in years an employee must be with the company to be eligible for the policy.
Employees Working To â The maximum length of time, in years, an employee may work with the company and still be eligible for the policy.
Do Not Allow Breaks â If this option is enabled the Clock In / Clock Out Paid Break and Clock In / Clock Out Unpaid Break options will not be available within the employee or punch modules.
An example showing the proper use of classes and tenures is provided below. Notice how all values from 0 to 99 years are covered by the class.
| | | | | || | Policy Name | Class | Min Tenure | Max Tenure | | Full Time New Hires | Full Time | 0 | 1 | | Full Time Employees | Full Time | 1 | 99 |
General Tab Configuration Procedure:
- Do you have any employees that have different settings for overtime, schedule rules, break rules etc based upon how long they have been with the company?
- Yes? â Set a policy name and configure classes & tenures
- No? â Set a policy name and move on. Classes & Tenures are not required.
It is only necessary to configure classes and tenures if employees have different settings for break rules, scheduling rules, overtime rules etc based upon how long they have been with the company. If classes and tenures are deemed necessary be sure to span all tenure values from 0 to 99 years with each class as shown in the example above. Tenures must be continuous from policy to policy without gaps.
When configuring classes and tenures it often helps to understand the softwareâs logic. Employees will be automatically assigned to policies according to the following conditions:
- If an employee is no longer eligible for their current policy the software will search the current class (or group) of policies for a match. Remember the software looks at an employeeâs hire date to determine policy eligibility. IE: Employees who have been with the company for more than a year are no longer eligible for the New Hire Policy which has a tenure range of 0 to 1 years.
- If an employee is not eligible for any of the policies within the current class (or group) the software will search policies within the default class for a match.
Pay Cycle Tab
Start of Week â Specifies the starting day of the work week. This affects the âLast Weekâ and âThis Weekâ date settings used by Reports and the Timecard editor.
Pay Cycle â Specifies a rotation method for pay period dates which makes it possible for InfiniTime to automatically calculate and update Current and Last Pay Period dates.
Current Pay Period From Date â Specifies a start date for the Current Pay Period. The ending date for the current pay period and the last pay period dates will be calculated and filled automatically based upon the chosen pay cycle type.
Split Punches At â Determines how punches will be split. The available option scan be used to split hours on an overnight shift between the current and last pay period or the current or last week depending on the chosen option.
No. of Days until Edit Lockout â Specifies a number of days from the end of the last pay period after which it will no longer be possible to edit timecards in last pay period. For example:
| | | | | || | Last Pay Start | Last Pay End | No. of Days until Edit Lockout | Date Timecards for Last Pay will no longer be editable | | 09/21/2008 | 09/27/2008 | 5 | 10/02/2008 |
Time for Edit Lockout â Defines the time at which timecard activity for Last Pay Period will no longer be editable. If the Time for Edit Lockout was set to 8:00 AM in the above example it would no longer be possible to edit timecards for last pay period at 8:00 AM on 10/02/2008.
Pay Cycle Tab Configuration Procedure:
- What type of pay cycle does your company observe?
- Set the pay cycle appropriately.
- What day is considered the start of your work week?
- Set the start of week appropriately.
- What is the start date of your current pay period? Remember â InfiniTime is only concerned with date ranges for which employees are paid, not the actual date when employees receive their check.
- Set the Current Pay Period From Date appropriately.
- Click OK to save the new pay cycle settings.
- Select the Policy then click on Change to edit the policy again. Click on the Pay Cycle Tab to continue configuration.
- Confirm the Current and Last Pay Period Dates are correct.
- Do you have any employees that work overnight?
- Yes? â Lets say an employee is working overnight on the last day of the pay period. Should their hours all be associated with the current pay period or should they be split across the current pay period and the next pay period?
- All on the current? â Leave Split Punches to None.
- Split between current and next? â Set to End of Pay Period or End of week as desired.
- No? â Split punches does not apply, move to the next item.
Arbitrary Pay Periods: Some companies may have a pay period that does not follow one of the predefined pay cycle options or has arbitrary pay dates. In this case it will be necessary to configure a Custom Pay Cycle and change the Start Date and Custom Interval Amount each time the pay period length changes.
IE: A customer follows a 2 Week / 3 Week repeating pay Cycle.
A Custom Pay Cycle is used with a 14 Day Custom Interval for the 2 Week Pay Period.
A Custom Pay Cycle is used with a 21 Day Custom Interval for the 3 Week Pay Period.
The Custom Pay Cycle Interval must be changed in the policy each time the organization switches from the 2 Week Pay Period to the 3 Week Pay Period.
The only drawback to Custom Pay Cycles is the Last Pay Period dates are calculated based upon the settings used for the Current Pay Period. Therefore the âLast Pay Periodâ date range used for reports and the Timecard Table will not be correct.
Semi-Monthly Pay Periods: When configuring a Semi-Monthly Pay Period the user is prompted for the First and Second Pay Day. These labels can be misleading â the First Pay Day refers to the start day of the first pay period. The Second Pay Day refers to the start day of the second pay period.
IE: A customer follows a Semi-Monthly Pay Period where the 1st and 16th are always the starting days of the pay period. The first pay period ends on the 15th and the second pay period ends on the last day of the month.
Break Rules Section
The Break Rules Section includes settings related to tracking employee breaks. InfiniTime can be configured to track Paid Breaks, Unpaid Breaks, or both. Breaks can automatically be inserted, without requiring employees to punch in or out, through use of Auto Breaks. Alternatively, Change To Break settings can be configured to automatically insert paid or unpaid breaks in place of non-working periods up to a certain duration. The Break Rules section also includes both Paid Break and Unpaid Break limits which provide the InfiniTime Administrator with the ability to limit the maximum duration for Paid breaks and / or configure a minimum duration for unpaid breaks. With Change to Break, Auto Break, and Break Limit settings configured appropriately InfiniTime supports a wide variety of break configurations to meet the needs of any industry.
OPTIONAL CONFIGURATION: The Break Rules Section, including settings on the Change to Breaks, Auto Breaks, Paid Break Limits, and Unpaid Break Limits Tabs are optional.
Break Rules should only be configured if you wish to track Breaks for employees assigned to the respective policy.
Change to Breaks Tab
Change to break is used when employees are required to punch in and out for lunch. Change to break uses the duration of time an employee is clocked out and automatically changes the employee's punch to an unpaid or paid break as appropriate based on Change to Break configuration. Additionally, many companies track only a single break type, such as Paid Breaks or Unpaid Breaks, within InfiniTime. In this scenario only the First Change to Break settings must be configured.
First Change to Break If Less Than â If an employee is clocked out for a duration shorter than the value specified in this field the duration the employee was clocked out for will be changed to either an unpaid or paid break.
First Change to Break Type â Specifies the break type which will be associated with the First Change to Break.
Second Change to Break If Less Than â If an employee is clocked out for a duration shorter than the value specified in this field the duration the employee was clocked out for will be changed to either an unpaid or paid break.
Second Change to Break Type â Specifies the break type which will be associated with the Second Change to Break.
Allow Auto Break With Change to Break - When this option is checked, InfiniTime will perform Auto Breaks even if the employee has already taken a break according to Change to Break rules. For organizations which require employees to punch for breaks only if they leave the premises, this option should be unchecked. Refer to the Break Examples for additional details on how Allow Auto Break with Change to Break is used.
NOTE: All break related settings are entered in hours and hundredths of hours. For example, 30 Minutes must be entered as 0.50 Hours as shown below.
Change to Breaks Tab Configuration Procedure
- Are your employees required to clock in and out for all breaks?
- No? â Would you like to deduct an unpaid break automatically from your employees?
- Yes? â Skip to Auto Breaks Tab.
- No? â Your organization does not require breaks. Skip to Hours and Time Limits.
- Yes? â Do you track Unpaid, Paid Breaks, or both?
- One type? Configure First Change to Break
- Both Types? Configure First and Second Change to break
- First Change to Break Configuration:
- What is the longest duration employees are permitted to take as their break?
- Enter this duration, as hours, in the First Change to Break if Less Than Field.
- Set the First Change to Break Type to either Paid Break or Unpaid Break as appropriate.
- Second Change to Break Configuration:
- What is the longest duration employees are permitted to take as their break?
- Enter this duration, as hours, in the First Change to Break if Less Than Field.
- Set the First Change to Break Type to either Paid Break or Unpaid Break as appropriate.
Auto Breaks Tab
Auto break is used when employees are not required to punch in and out for lunch. Auto breaks can be configured to automatically deduct a specified amount of time from employees after they have worked a predetermined number of hours.
First Auto Break if More Than Hours â Employees must work the number of hours specified in this field before the automatic break will be applied to the employeeâs timecard.
First Auto Break Type â Specifies the break type which will be associated with the First Auto Break.
First Auto Break Amount â Specifies the break duration, in hours, which will be automatically inserted by the First Auto Break.
Second Auto Break if More Than Hours - Employees must work the number of hours specified in this field before the automatic break will be applied to the employeeâs timecard.
Second Auto Break Type â Specifies the break type which will be associated with the Second Auto Break.
Second Auto Break Amount â Specifies the break duration, in hours, which will be automatically inserted by the Second Auto Break.
Insert Auto Break only on Days with a Schedule - When this option is checked, Auto Breaks will only be inserted for employees on dates where the employee was scheduled to work. When this option is unchecked, Auto Breaks will be inserted on any day where the employee works the predetermined number of hours regardless of whether the employee had a schedule on the respective work day.
Auto Breaks Tab Configuration Procedure
- Would you like to automatically insert Unpaid or Paid breaks for employees?
- Yes? - Do you wish to automatically insert Unpaid Breaks, Paid Breaks, or Both?
- One Type? Configure First Auto Break.
- Both Types? Configure both First Auto Break and Second Auto Break.
- No?
- You do not require Auto Breaks. Skip to the Exceptions Section of this document.
- First Auto Break
- How many hours must employees work before the First Auto Break will be deducted? Set the 'First Auto Break If More Than' field to this value.
- Set the 'First Auto Break Type' field to the appropriate Break Type (Paid or Unpaid).
- Set the 'First Auto Break Amount' field to the desired break duration, in hours, which will automatically be inserted by the First Auto Break
- Second Auto Break
- How many hours must employees work before the First Auto Break will be deducted? Set the 'Second Auto Break If More Than' field to this value.
- Set the 'Second Auto Break Type' field to the appropriate Break Type (Paid or Unpaid).
- Set the 'Second Auto Break Amount' field to the desired break duration, in hours, which will automatically be inserted by the Second Auto Break
Paid Break Limits Tab
Paid Break Limits are used with Change to Break settings to enforce minimum and maximum break durations for Paid Breaks. By configuring paid break limits paid breaks can be configured with a minimum or maximum duration providing complete control over Paid Break Durations.
If Paid Break is More Than And Less Than â Defines the break durations to which Paid Break Limits will be applied. Paid breaks with a duration that falls between the âMore Thanâ and âLess Thanâ amount will be subject to paid break limits.
Break Length Is Allowed To Be A Minimum Of â Specifies a minimum duration for paid breaks. The minimum break length setting is commonly used with Unpaid Break Limits as employees will receive overtime if they do not take a break of a certain length though it is not as common for Paid Break Configurations.
Break Length Is Allowed To Be A Maximum Of â Specifies a maximum duration for paid breaks. The maximum break length setting is commonly used with Paid Break Limits in order to limit the break length employees will be paid for. Employees will be unpaid for any time in excess of the maximum break length specified in this field.
Maximum Daily Break Amount â Specifies a maximum paid break duration for a single day. For example employees are often permitted two 15 minute paid breaks. In this scenario the Maximum Daily Break Amount would be set to .5 resulting in a maximum of 30 minutes paid for breaks in a single day.
Rounding â Rounding for Paid Breaks is optional. If these options are configured Paid Break Durations will be rounded to the nearest Tenth of an Hour or Quarter of an Hour and then Paid Break Limits will be applied. This is often used when employee contracts specify employee hours must be rounded. An example configuration is provided below.
In the preceding example if an employee punched out for 17 minutes their break duration would first be rounded to 18 minutes and then Paid Break Limits would be applied. This results in a Paid Break Duration of 15 minutes (.25 hrs) and an unpaid duration of 3 minutes due to the Maximum Length setting.
Paid Break Limits Tab Configuration Procedure
- Does your organization require employees to punch in and out for paid breaks?
- Yes - Would you like to configure a Minimum Duration, Maximum Duration, or Both for each individual Paid Break?
- Minimum Duration - Configure the Break Length Minimum Amount as detailed below.
- Maximum Duration - Configure the Break Length Maximum Amount as detailed below.
- Both - Configure both the Break Length Minimum Amount and Maximum Amount as detailed below. The Break Limit Bounds must be configured appropriately to include all paid breaks.
- Would you like to configure a maximum daily amount, per employee, for all paid breaks? If the Maximum Daily Break Amount is configured, employees will not be paid for Paid Break durations in excess of the Maximum Daily Break Amount.
- Yes? - set the Maximum Daily Break Amount to the maximum permitted Daily Paid Break Duration. (IE: 0.5 for 30 Minutes Paid Break per day - or two fifteen minute breaks)
- No? - Leave the Maximum Daily Break Amount Field blank.
- No? - If employees do not punch for paid breaks, then the Change to Break settings should not be configured for Paid Breaks. Similarly, the Paid Break Limits Tab should not be configured. All fields on the Paid Break Limits tab should be left blank in this scenario.
- Minimum Duration:
- Configure the Paid Break Limit Bounds:
- What is the minimum duration of Paid Break which Paid Break Limits should be applied to? Set the 'If Paid Break is More Than' field to this value. (IE: 0.01 Hours)
- What is the maximum duration of Paid Break which Paid Break Limits should be applied to? Set the 'If Paid Break is less than' field to this value. (IE: 0.50 Hours)
- What is the minimum permitted duration for a single Paid Break?
-
Enter this duration, in hours, in the 'Break Length is allowed to be a Minimum Amount of' Field.
-
All Paid Breaks with a duration that falls within the Paid Break Limit Bounds with a duration less than the Minimum will be automatically set to the Minimum Duration.
-
Maximum Duration:
- Configure the Paid Break Limit Bounds:
- What is the minimum duration of Paid Break which Paid Break Limits should be applied to? Set the 'If Paid Break is More Than' field to this value. (IE: 0.01 Hours)
- What is the maximum duration of Paid Break which Paid Break Limits should be applied to? Set the 'If Paid Break is less than' field to this value. (IE: 0.50 Hours)
- What is the maximum permitted duration for a single Paid Break?
- Enter this duration, in hours, in the 'Break Length is allowed to be a Maximum Amount of' Field.
- All Paid Breaks with a duration that falls within the Paid Break Limit Bounds with a duration more than the Maximum Duration will be offset with unpaid hours on the last punch pair for the respective date to reflect the Maximum Paid Break Duration. Refer to the Break Examples for additional details.
Unpaid Break Limits Tab
Unpaid Break Limits are used with Change to Break settings to enforce minimum and maximum break durations for Unpaid Breaks. By configuring unpaid break limits unpaid breaks can be configured with a minimum or maximum duration providing complete control over Unpaid Break Durations.
If Unpaid Break is More Than And Less Than â Defines the break durations to which unpaid Break Limits will be applied. Unpaid breaks with a duration that falls between the âMore Thanâ and âLess Thanâ amount will be subject to Unpaid break limits.
Break Length Is Allowed To Be A Minimum Of â Specifies a minimum duration for unpaid breaks. Employees will not be able to take a break shorter than the duration specified in this field. For example if the Minimum Break Length is set to 30 minutes and an employee should take a 15 minute break the employee would be deducted 30 minutes rather than 15. The minimum break length setting is commonly used with Unpaid Break Limits as employees receive overtime if they do not take a break of at least a certain length.
Break Length Is Allowed To Be A Maximum Of â Specifies a maximum duration for unpaid breaks. Employees who take an unpaid break in excess of the Maximum Break Length specified in this field will be paid for any duration in excess of the maximum break length. The maximum break length setting is rarely used with Unpaid Breaks.
Unpaid Break Limits Type Configuration Procedure
- Does your organization require employees to punch in and out for unpaid breaks?
- Yes - Would you like to configure a Minimum Duration, Maximum Duration, or Both for each individual Unpaid Break?
- Minimum Duration - Configure the Break Length Minimum Amount as detailed below.
- Maximum Duration - Configure the Break Length Maximum Amount as detailed below.
- Both - Configure both the Break Length Minimum Amount and Maximum Amount as detailed below. The Break Limit Bounds must be configured appropriately to include all unpaid breaks.
- No? - If employees do not punch for unpaid breaks, then the Change to Break settings should not be configured for Unpaid Breaks. Similarly, the Unpaid Break Limits Tab should not be configured. All fields on the Unpaid Break Limits tab should be left blank in this scenario.
- Minimum Duration:
- Configure the Unpaid Break Limit Bounds:
- What is the minimum duration of Unpaid Break which Unpaid Break Limits should be applied to? Set the 'If Unpaid Break is More Than' field to this value. (IE: 0.01 Hours)
- What is the maximum duration of Unpaid Break which Unpaid Break Limits should be applied to? Set the 'If Unpaid Break is less than' field to this value. (IE: 0.50 Hours)
- What is the minimum permitted duration for a single Unpaid Break?
-
Enter this duration, in hours, in the 'Break Length is allowed to be a Minimum Amount of' Field.
-
All Unpaid Breaks with a duration that falls within the Unpaid Break Limit Bounds with a duration less than the Minimum will be automatically set to the Minimum Duration.
-
Maximum Duration:
- Configure the Unpaid Break Limit Bounds:
-
What is the minimum duration of Unpaid Break which Unpaid Break Limits should be applied to? Set the 'If Unpaid Break is More Than' field to this value. (IE: 0.01 Hours)
-
What is the maximum duration of Unpaid Break which Unpaid Break Limits should be applied to? Set the 'If Unpaid Break is less than' field to this value. (IE: 0.50 Hours)
-
What is the maximum permitted duration for a single Unpaid Break?
- Enter this duration, in hours, in the 'Break Length is allowed to be a Maximum Amount of' Field.
- All Unpaid Breaks with a duration that falls within the Paid Break Limit Bounds with a duration more than the Maximum Duration will be offset with paid hours on the last punch pair for the respective date to reflect the Maximum Unpaid Break Duration. Refer to the Break Examples for additional details.
- It should be noted that the Maximum Duration feature is rarely used for Unpaid Breaks as Unpaid Breaks are generally unpaid - even if the employee were to take an excessively long Unpaid Break the full duration of the break is still generally unpaid time.
Example Break Configurations
Unpaid Lunch w/ Change to Break
Employees at XYZ Manufacturing Co. are required to punch in and out for an unpaid lunch which is 30 minutes in duration. The first change to break should be set to 1 hour not .5 hours. By setting the change to break to 1 hour employees will not receive a longer break â it simply instructs the software to change the duration an employee is clocked out to an unpaid break as long as they are gone for less than an hour. If the employee should take a break for longer than an hour they will still be unpaid â the duration will simply not show as a break in the timecards.
| | | | | || | First Change to Break | First Change to Break Type | Second Change to Break | Second Change to Break Type | | 1 | Unpaid | | |
Paid Breaks & Unpaid Lunch w/ Change to Break And Paid Break Limits
Employees at ABC Manufacturing Co. receive two fifteen (15) minute paid breaks and a thirty (30) minute unpaid lunch. If an employee should take a long break any duration in excess of fifteen minutes should be unpaid. When using both the First and Second Change to Break options the first change to break must have a shorter duration. Additionally it is important to recognize Paid Break Limits only apply to break durations recognized as a Paid Break by Change to Break. With this in mind, the Change to Break settings for Paid Breaks must have a slightly longer duration than the desired break time.
To ensure paid breaks are limited appropriately the first and second change to breaks should be configured as shown below. In this way when an employee is clocked out for less than 20 minutes the duration they are gone for will be subject to paid break limits. When they are clocked out for more than 20 minutes and less than 1 hour the duration they are gone for will be shown as an unpaid break.
Change to Break Configuration
| | | | | || | First Change to Break | First Change to Break Type | Second Change to Break | Second Change to Break Type | | .33 | Paid | 1 | Unpaid |
Paid Break Limits Configuration
| | | | | | || | If Paid Break is More than | And Less Than | Minimum Break Length | Maximum Break Length | Maximum Daily Break Length | | .01 | .33 | .01 | .25 | .5 |
Break Examples
Examples of individual break durations and their respective Paid and Unpaid Time are shown below. Timecard records are shown for the highlighted examples.
Individual Break Examples
| | | | || | Break Duration | Paid Break Time | Unpaid Break Time | | 12 Minutes (.2 Hrs) | 12 Minutes | |
| | | | || | Break Duration | Paid Break Time | Unpaid Break Time | | 18 Minutes (.3 Hrs) | 15 Minutes | 3 Minutes |
| | | | || | Break Duration | Paid Break Time | Unpaid Break Time | | 45 Minutes (.75 Hrs) | | 45 Minutes |
Daily Break Examples
| | | | | | || | 1st Paid Break Duration | 2nd Paid Break Duration | Lunch Break Duration | Total Paid Time | Total Unpaid Time | | 12 Minutes (.2 Hrs) | 12 (.2 Hrs) | 35 Minutes | 24 Minutes | 35 Minutes | | 12 Minutes (.2 Hrs) | 18 Minutes (.3 Hrs) | 30 Minutes | 27 Minutes | 33 Minutes | | 18 Minutes (.3 Hrs) | 25 Minutes (.42 Hrs) | 45 Minutes | 30 Minutes | 58 Minutes |
Notice how the Paid Break from 2:00 PM to 2:18 PM exceeds the Maximum Paid Break Duration. The Timecard Table shows the full duration in the Regular Hours Column and the Paid Break Duration in the Break Column. The difference - 0.05 hours - is then deducted from the last Regular Hours Punch Pair on the day which in this case is 2:18 PM to 4:00 PM. Note that 2:18 PM to 4:00 PM is 1.70 Hours, the final total is 1.65 Hours after the Paid Break Duration in excess (0.05 Hours) of the Maximum Break Amount (0.25 Hours) is deducted.
Auto Break w/ Change to Break
Office Employees at ABC Manufacturing company are only required to punch out for lunch if they leave the office building. If employees choose to stay onsite a 30 minute break is automatically deducted from their timecard. If employees choose to leave the building they are required to punch out for lunch and are unpaid for the entire duration they are gone for. Employees are permitted 30 minutes for lunch.
Change to Break Configuration
| | | | | || | First Change to Break | First Change to Break Type | Second Change to Break | Second Change to Break Type | | 1 | Unpaid | | |
The âAllow Auto Break with Change to Breakâ box must be unchecked on the change to break tab.
Auto Break Configuration
| | | | || | First Auto Break if More than Hours | First Auto Break Type | First Auto Break Amount | | 6 | Unpaid | .5 |
Paid & Unpaid Breaks w/ Change to Break: It should be noted that many companies opt to not track paid breaks within InfiniTime.. Employees will be required to punch for unpaid breaks but can take paid breaks at their leisure. In this scenario it is only necessary to configure the First Change to Break for Unpaid Breaks.
Exceptions
Exceptions permit InfiniTime Administrators to track employee compliance with Schedules and other Time and Attendance related metrics such as industry specific rules. It is important to note that Schedules must be configured for most exception types to function. As of InfiniTime 7.08 exceptions can be configured in one of three ways:
- Company Wide Exceptions Only - Company Wide Exceptions are ideal for organizations who wish to track the same exceptions for all employees.
- Policy Based Exceptions Only - Policy Based Exceptions are ideal for organizations who wish to track different exceptions for each group of employees.
- Company Wide Exceptions & Policy Based Exceptions for Specific Categories of Employees - When used together, Company Wide Exceptions and Policy Based Exceptions make it possible for InfiniTime Administrators to define exceptions for the company as a whole and then define exceptions for specific groups of employees in the Exceptions Section of the Policy Update Form as needed. Using both Company Wide Exceptions and Policy Based exceptions provides the most flexible configuration. When using both Company Wide Exceptions and Policy Based Exceptions, it is important to note that Policy Based Exceptions override Company Wide Exceptions. For example, if only the Absent Exception were defined on an employee's policy and the Company Wide Exceptions included Absent, Tardy, Early, and Late Departure only the Absent Exception would be tracked for the employee.
Accessing Company Wide Exceptions
- Click on Lookups
- Click on Calculation Setup
.gif)
- Click on Exception Types
Insert
- Opens the Exception Type Update Form. Click Insert on the Exception Type Table to Define a new Company Wide Exception.
Change
- Opens the Exception Type Update Form for the selected Exception.
Delete
- Deletes the Selected Exception from the Exception Type Table. The exception will no longer be tracked for employees. Additionally, all previous occurrences for the selected exception will be removed from employee timecards upon the next recalculate.
Accessing Policy Based Exceptions
- Login to the Manager Module
- Click on Company on the pull down menu
- Click on Setup
- Click on Policies
- The Policy Table will be displayed.
- Select the Policy for which you wish to define Policy Based Exceptions and click on Change.
- The Policy Update Form will be displayed.
- Click on the Exceptions Section. The Policy Exception Type Table will be displayed.
Insert
- Opens the Exception Type Update Form. Click Insert on the Exception Type Table to Define a new Exception for all employees assigned to the respective Policy.
Change
- Opens the Exception Type Update Form for the selected Exception.
Delete
- Deletes the Selected Exception from the Exception Type Table. The exception will no longer be tracked for employees assigned to the respective policy. Additionally, all previous occurrences for the selected exception will be removed from employee timecards upon the next recalculate.
Exception Type Update Form
The Exception Type Update Form is used to add exceptions to the InfiniTime Software for both Company Wide and Policy Based Exceptions. The Exception Type Update Form includes two tabs. The general tab includes for all fields and settings related to the specific Exception Type while the Notifications Tab includes options related to sending notifications to employees and / or employee supervisors when exceptions occur.
Exception Type Update Form - General Tab
Type â Use the drop down box to select the desired exception type from those available.
Description â Enter a description for the exception. This description will be entered into the exception type table and will be used in the Timecard Activity Table and Exception related Reports. The description does not need to be the same name as the exception type, but should be related. For example âEmployee Not Presentâ for the Absent Exception. It should be noted that the exception name must be unique - even between Company Wide and Policy Based Exceptions. No two exceptions can have the same description.
Points â Enter a point value for the specified exception type. The exception point system is an optional feature that accrues a preset amount of points when an employee receives a specific exception. This preset amount is then added to any previous exception points the employee may have and can be viewed in the Employee Exception Points Report. This allows managers to take disciplinary measures for various point values.
Technical Note: The Exception Type Update Form also includes Exception Specific Fields which include prompts for details related to the selected Exception Type. For example, the Threshold Field is shown below which is used to adjust the exact threshold at which several exceptions trigger. For additional details on the Threshold Field, or other exception specific fields, please refer to the specific Exception Type as listed in the Available Exception Types section of this document for each individual exception type.
Exception Type Update Form - Notifications Tab
InfiniTime permits SMS (IE: Text Messaging) and Email Exception notifications to be configured on a per exception basis. Email and SMS notifications can be sent to either employees or supervisors at the discretion of the InfiniTime Administrator. Requirements for SMS and Email Notifications are outlined below.
Alert Supervisor Via SMS - If this option is checked, when the respective exception is triggered for an employee the employee's supervisor will receive a text message alerting the supervisor that the exception occurred.
Alert Supervisor Via Email - If this option is checked, when the respective exception is triggered for an employee the employee's supervisor will receive an email alerting the supervisor that the exception occurred.
Alert Employee Via SMS - If this option is checked, when the respective exception is triggered for an employee the employee's supervisor will receive a text message alerting the supervisor that the exception occurred.
Alert Employee Via Email - If this option is checked, when the respective exception is triggered for an employee the employee's supervisor will receive an email.
Send Alert Within - The 'Send Alert Within...Days' Option sets the duration of the time period during which InfiniTime will send Exception Notifications after an exception is triggered. For example, the number line below shows November 7th as a date an employee had the Missing Scheduled Punch Exception. The number line also shows the Sent Alert within...Days value for each day from November 7th to December 7th.
The Missing Scheduled Punch Exception triggers when an employee has a scheduled punch but does not have a punch within the bounds of the On Time and Late Grace Periods for a given scheduled Punch. The exception will trigger automatically if an employee forgets to punch in or out. Additionally, the Missing Scheduled Punch Exception would also trigger if a supervisor were to delete an employee's out punch prior to inserting an adjusted time. The Send Alert Within Days option should be set accordingly so that Exception Notifications received by managers communicate an actionable task.
NOTE: Most customers choose to leave the Send Alert Within setting at 0 Days to ensure exception notifications are only sent for exceptions that are triggered for today's date.
Technical Note: All Mobile Phones with support for text messaging (SMS) have a built in email address with the mobile provider which can be used to send text messages to the device via email. With this in mind, InfiniTime uses the Windows Simple Mail Transfer Protocol Service to send both SMS and Email Notifications.
Required Server Configuration for SMS and Email Notifications
-
The InfiniTime Server must have an active Internet connection at all times.
-
Power Management must be disabled on the Network Interface Card of the InfiniTime Server.
-
The InfiniTime Housekeeping Service must be started and running.
-
The InfiniTime Server does not need to have a user logged into the console. However, it must at least be powered on and idle at the Windows Login Splash Screen.
-
Your fully qualified domain name may need to be configured in the advanced delivery options of the Simple Mail Transfer Protocol Server within Internet Information Services Management depending on your domain policies and mail server's configuration.
-
The server must be granted permissions to relay email through the SMTP Virtual Server installed by InfiniTime.
-
Depending on your network configuration and domain settings it may be necessary to forward all outgoing email messages from the InfiniTime SMTP Virtual Server to a Smart Host. Generally the Smart Host will be a server running exchange on your local network. The smart host can be configured under Advanced Options of Delivery tab for the InfiniTime SMTP Virtual Server Properties.
Configuring SMS Notifications
- Determine the exact exception types for which InfiniTime should send Notifications for each instance the exception is triggered. For example, the Non-Arrival and Missed Scheduled Punch exceptions are popular choices for use with SMS Notifications.
- Check 'Alert Supervisor Via SMS' or 'Alert Employee Via SMS' as desired on the Notifications Tab of the Exception Type Update Form for each individual exception you wish to send notifications for.
- When using 'Alert Supervisor Via SMS' all employees assigned as Supervisors must have the following fields defined on their employee profile:
- Cell Number
- When entering the Employee's Cell Phone Number, enter only the 10 digit phone number as shown in the example below. Do not enter dashes.
- Cell Provider - Select the employee's cell phone carrier by clicking on the Lookup Magnify Glass and selecting the appropriate carrier. If the employee's cell phone carrier is not present in the list of Cell Phone Providers it must be added with the correct SMS Email Gateway address. The SMS Email Gateway address for a given cellular carrier can be obtained by contacting technical support personnel for the respective carrier or by sending an SMS text to any email address from a device on the respective carrier's network. Exception Notifications utilize the cell phone provider's SMS Email Gateway to send SMS Notifications to supervisors and employees.
- When using 'Alert Employee Via SMS' all employees must have the following fields defined on their employee profile:
- Cell Number - When entering the Employee's Cell Phone Number, enter only the 10 digit phone number as shown below. Do not enter dashes.
- Cell Provider - Select the employee's cell phone carrier by clicking on the Lookup Magnify Glass and selecting the appropriate carrier. If the employee's cell phone carrier is not present in the list of Cell Phone Providers it must be added with the correct SMS Email Gateway address. The SMS Email Gateway address for a given cellular carrier can be obtained by contacting technical support personnel for the respective carrier or by sending an SMS text to any email address from a device on the respective carrier's network. Exception Notifications utilize the cell phone provider's SMS Email Gateway to send SMS Notifications to supervisors and employees.
Cell Phone Provider Table:
Cell Phone Provider Update Form:
SMS Related Fields - Example Setup
Configuring Email Notifications
- Determine the exact exception types for which InfiniTime should send Notifications for each instance the exception is triggered. For example, the Non-Arrival and Missed Scheduled Punch exceptions are popular choices for use with Email Notifications.
- Check 'Alert Supervisor Via Email' or 'Alert Employee Via Email' as desired on the Notifications Tab of the Exception Type Update Form for each individual exception you wish to send notifications for.
- When using 'Alert Supervisor Via Email' all employees assigned as Supervisors must have the following fields defined on their employee profile:
- Email Address - Enter the Primary Email Address to be kept on file for the supervisor. Supervisor Email Exception Notifications will be sent to this email address. Some customers choose to use a single Distribution Group Email Address, configured on the Mail Server such that all InfiniTime Supervisors receive email messages sent to the group address, in this field.
- When using 'Alert Employee Via SMS' all employees must have the following fields defined on their employee profile:
- Email Address - Enter the Primary Email Address to be kept on file for the employee. If enabled, Employee Email Exception Notifications will be sent to this email address.
Email Notification Related Fields - Example Setup
Available Exception Types
The following exception types can be selected from the âTypeâ drop down menu when inserting exceptions. Each exception type performs a different function. Familiarize yourself with each exception before deciding to track them. This section is organized into a table layout as outlined below.
Exception Type | Exception Type, as listed in the 'Type' Drop Down Menu on the Exception Type Update Form. |
---|---|
Summary | Provides a short description of the exception's intended usage. |
Exception Type Specific Fields | Lists Exception Type Specific Fields, as displayed on the Exception Type Update Form, for the specific exception type. Available Exception Type Specific fields are outlined below. |
Additional Required Configuration | Lists any additional configuration, such as a specific Policy Setting, required for the exception to properly trigger. |
Exception Trigger | Details the exact trigger that causes the exception to occur. |
Exception Type Specific Fields
- Threshold
- The Threshold Field is used for many exceptions which trigger after a set number of minutes, hours, or days. Refer to the specific exception type below for additional details on how the threshold field is used for a given exception. Pay special attention to the unit displayed to the right of the Threshold Field which indicates wether the threshold is measured in minutes, hours, or days.
- Department
- The Department Field is used with the Non Arrival Exception to indicate a specific Department / Job / Task Combination to check for Schedules. Refer to the Non-Arrival Exception for additional details.
- Job
- The Department Field is used with the Non Arrival Exception to indicate a specific Department / Job / Task Combination to check for Schedules. Refer to the Non-Arrival Exception for additional details.
- Task
- The Department Field is used with the Non Arrival Exception to indicate a specific Department / Job / Task Combination to check for Schedules. Refer to the Non-Arrival Exception for additional details.
- Use Count as Day Worked for Other Activity Types - 'Use Count as Day Worked for Other Activity Types' toggles the method for determining which, if any, Other Activity Types count toward Consecutive Days Worked for purposes of the Consecutive Days Exception. If 'Use Count as Day Worked For Other Activity Types' is checked, Hours for Other Activity Types with the 'Count as Day Worked' option checked will count toward the Consecutive Days Exception and Hours for Other Activity Types with the 'Count as Day Worked' option unchecked will not count toward the Consecutive Days Exception. If 'Use Count as Day Worked for Other Activity Types' is unchecked, the user may select specific Other Activity Types to count toward the Consecutive Days Exception using the 'Other Activity Types Counted Toward Consecutive Days' Tab.
- Count Regular Hours toward Consecutive Days - 'Count Regular Hours Toward Consecutive Days' is used for both the Consecutive Days and Mandatory Rest Period Exceptions. If this option is checked, Regular Hours on a given date will count the date toward Consecutive Days worked for purposes of the Consecutive Days and Mandatory Rest Period Exceptions. If this option is unchecked, Regular Hours on a given date will not cause the date to be counted toward Consecutive Days Worked for purposes of the Consecutive Days or Mandatory Rest Period Exceptions.
- Count OT1 Hours toward Consecutive Days - 'Count OT1 Hours Toward Consecutive Days' is used for both the Consecutive Days and Mandatory Rest Period Exceptions. If this option is checked, OT1 Hours on a given date will count the date toward Consecutive Days worked for purposes of the Consecutive Days and Mandatory Rest Period Exceptions. If this option is unchecked, OT1 Hours on a given date will not cause the date to be counted toward Consecutive Days Worked for purposes of the Consecutive Days or Mandatory Rest Period Exceptions.
- Count OT2 Hours toward Consecutive Days - 'Count OT2 Hours Toward Consecutive Days' is used for both the Consecutive Days and Mandatory Rest Period Exceptions. If this option is checked, OT2 Hours on a given date will count the date toward Consecutive Days worked for purposes of the Consecutive Days and Mandatory Rest Period Exceptions. If this option is unchecked, OT2 Hours on a given date will not cause the date to be counted toward Consecutive Days Worked for purposes of the Consecutive Days or Mandatory Rest Period Exceptions.
- Count OT3 Hours toward Consecutive Days - 'Count OT3 Hours Toward Consecutive Days' is used for both the Consecutive Days and Mandatory Rest Period Exceptions. If this option is checked, OT3 Hours on a given date will count the date toward Consecutive Days worked for purposes of the Consecutive Days and Mandatory Rest Period Exceptions. If this option is unchecked, OT3 Hours on a given date will not cause the date to be counted toward Consecutive Days Worked for purposes of the Consecutive Days or Mandatory Rest Period Exceptions.
- Count OT4 Hours toward Consecutive Days - 'Count OT4 Hours Toward Consecutive Days' is used for both the Consecutive Days and Mandatory Rest Period Exceptions. If this option is checked, OT4 Hours on a given date will count the date toward Consecutive Days worked for purposes of the Consecutive Days and Mandatory Rest Period Exceptions. If this option is unchecked, OT4 Hours on a given date will not cause the date to be counted toward Consecutive Days Worked for purposes of the Consecutive Days or Mandatory Rest Period Exceptions.
- Consecutive Days - The Consecutive Days field sets the number of Consecutive Days Worked for purposes of the Consecutive Days and Mandatory Rest Period Exceptions. Refer to the individual exceptions below for additional information.
- Total Hours - The Total Hours Field is used with the Mandatory Rest Period Exception. The Mandatory Rest Period Exception will trigger if an employee works more than Total Hours within Consecutive Days without a certain number of consecutive off duty hours. This exception is useful for tracking employee fatigue levels and preventing potentially dangerous working situations.
- Off Duty Hours - The Off Duty Hours Field sets the number of Off Duty Hours, or consecutive hours during which an employee is punched out, required to reset the Total Hours Count for the Mandatory Rest Period Exception.
- Other Activity Types Counted Toward Consecutive Days - The 'Other Activity Types Counted Toward Consecutive Days' Tab sets Other Activity Types which will count toward the Consecutive Days, Mandatory Rest Period, and DOT Off Duty Rule Exceptions.
Exception Type | Absent |
---|---|
Summary | Clearly marks dates on which an employee was scheduled to work where the employee failed to punch in the Company Timecard Table as shown below. Like all exceptions, the Absent exception also appears on all exception related reports. |
Exception Type Specific Fields | N/A |
Additional Required Configuration | Employee's must have Schedules Defined for the Absent Exception to trigger. |
Exception Trigger | The Absent Exception will trigger under the following conditions: _ The Employee must have at least one Working Period Scheduled for the Date _ There must be no timecard punches or Other Activity Types set to Count as Day Worked present for the respective Date for the Employee * The Absent exception triggers at midnight on the next day if the above conditions are met. |
| Exception Type | Approaching DOT Consecutive Hours Rule One | | Summary | The Approaching DOT Consecutive Hours Rule One exception is intended to alert supervisors when employees are close to breaking the Department of Transportation (DOT) Hours of Service Rule 1 which states that employees may drive a maximum of 11 hours after 10 consecutive hours off duty. | | Exception Type Specific Fields | * Threshold |
| Exception Type | Approaching DOT Consecutive Hours Rule Two | | Summary | The employee is getting close to Breaking DOT Hours of Service Rule 2. A threshold can be set to signify when the approaching exception will fire in relation to the actual exception. IE: Approaching Rule 2 with a two hour threshold will cause the Approaching DOT Hours of Service Rule 3 exception to occur when an employee is within two working hours of breaking DOT Hours of Service Rule 2. | | Exception Type Specific Fields | * Threshold |
| Exception Type | Approaching DOT Seven Days Rule | | Summary | The employee is getting close to Breaking DOT Hours of Service Rule 3. A threshold can be set to signify when the approaching exception will fire in relation to the actual exception. IE: Approaching Rule 3 with a ten hour threshold will cause the Approaching DOT Hours of Service Rule 3 exception to occur when an employee is within ten working hours of breaking DOT Hours of Service Rule 3. | | Exception Type Specific Fields | * Threshold |
| Exception Type | Approaching Exceeded Accrued Time | | Summary | Occurs when an employee uses enough accrued time that their Remaining Accrual Balance is less than the threshold set for the exception. For example if an employee has 40 hours of vacation and the Approaching Exceeded Accrual Exception Threshold is set to 10 the exception will occur after the employee uses 30 hours or more. The Approaching Exceeded Accrual exception can only be viewed on the Employee Exception Detail Report as accrual exceptions are not related to employee timecards. When using the Employee Exception Detail report to view the Exceeded Accrual Exception the Date Range should match the Accrual Period for the Accrual Type in question. | | Exception Type Specific Fields | _ Threshold | | Additional Required Configuration | _ Accrual Types and Accrual Calculations must be configured. _ Accrual Types must be assigned to employees. _ Other Activity Types that deduct must be properly defined for each Accrual Calculation. | | Exception Trigger | * Triggers when Time Base + Time Accrued - Time Used is less than or equal to the Approaching Exceeded Accrued Time Threshold for a given accrual period. |
| Exception Type | Approaching Overtime | | Summary | The Approaching Overtime Exception warns supervisors when employees are within a certain number of hours from receiving Weekly Overtime. The Approaching Overtime Threshold should be set to the number of hours away from Weekly Overtime you wish to be notified at. For example, a Threshold of 8 Hours with a Weekly Overtime 1 Setting of > 40 Hours will trigger the Approaching Overtime Exception at 32 Hours Worked for a given work week. | | Exception Type Specific Fields | _ Threshold | | Additional Required Configuration | _ The 'Weekly Overtime If Over Hours' Policy Setting must be configured for OT1, OT2, OT3, or OT4 _ The Approaching Overtime exception will not trigger for Employees assigned to a policy without Weekly Overtime configured for OT1, OT2, OT3, or OT4. | | Exception Trigger | _ Triggers when Total Hours for a given work week + Threshold is greater than the Weekly Overtime Setting for OT1, OT2, OT3, or OT4 as set on an employee's policy. |
| Exception Type | Approved Overtime | | Summary | The Approved Overtime Exception triggers for any date with Approved OT1, OT2, OT3, or OT4 Hours. | | Exception Type Specific Fields | _ Threshold | | Additional Required Configuration | _ Overtime Must Be Approved must be enabled for one or more Overtime Types (IE: OT1, OT2, OT3, OT4) | | Exception Trigger | * Triggers for any date with Approved OT1, OT2, OT3, or OT4 Hours. |
| Exception Type | Consecutive Days | | Summary | The Consecutive Days Exception is intended for Employee Fatigue Tracking purposes. InfiniTime tracks the number of consecutive days worked by employees and triggers the Consecutive Days exception if employees have hours for valid Hours Types over a number of days, as specified by the Consecutive Days field, in a row. | | Exception Type Specific Fields | _ Use Count as Day Worked for Other Activity Types _ Other Activity Types Counted Toward Consecutive Days _ Count Regular Hours Toward Consecutive Days _ Count OT1 Hours Toward Consecutive Days _ Count OT2 Hours Toward Consecutive Days _ Count OT3 Hours Toward Consecutive Days _ Count OT4 Hours Toward Consecutive Days _ Consecutive Days | | Additional Required Configuration | N/A | | Exception Trigger | _ The Consecutive Days Exception Triggers as follows: _ + The Consecutive Days Exception Triggers if an employee has Valid Hours Types on a number of days in a row equal to consecutive days. + The Consecutive Days Exception triggers independently of the current Work Week. + The Consecutive Days Exception will continue to trigger every day after an employee works a number of days equal to Consecutive Days until the employee has a full day off with zero hours from Valid Hours Types. + Valid Hours Types are determined as follows: + - If 'Count Regular Hours toward Consecutive Days is checked, Regular Hours will be included in the consecutive days and total hours calculation. - If âCount OT1 Hours toward Consecutive Daysâ is checked, OT1 Hours will be included in the consecutive days and total hours calculation. - If âCount OT2 Hours toward Consecutive Daysâ is checked, OT2 Hours will be included in the consecutive days and total hours calculation. - If âCount OT3 Hours toward Consecutive Daysâ is checked, OT3 Hours will be included in the consecutive days and total hours calculation. - If âCount OT4 Hours toward Consecutive Daysâ is checked, OT4 Hours will be included in the consecutive days and total hours calculation. - If 'Use Count as Day Worked for Other Activity Types' is checked, Other Activity Types with 'Use Count as Day Worked' checked will be included in the consecutive days calculation. - If 'Use Count as Day Worked for Other Activity Types' is unchecked, Other Activity Types specified on the 'Other Activity Types that Count Toward Consecutive Days' will be included in the consecutive days calculation. - Other Hours for Activity Types specified on the 'Other Activity Types Counted Toward Consecutive Days' Tab (or Other Activity Types set to 'Count as Day Worked') will be included in the total hours calculation if the Other Activity Type is set to 'Allow Start Time Entry'. - Regular, OT1, OT2, OT3, and OT4 hours for Other Activity Types specified on the 'Other Activity Types Counted Toward Consecutive Days Tab' (or Other Activity Types set to 'Count as Day Worked') which are set to 'Count as Regular Hours' and 'Allow Start Time Entry' will be included in the Total Hours calculation according to the 'Count Hours Type Toward Consecutive Days' Options. |
| Exception Type | DOT Consecutive Hours Rule One | | Summary | Service Rule One as enforced by the Department of Transportation states 'Employees may drive a maximum of 11 hours after 10 consecutive hours off duty. Report a Rule 1 Violation if break is less than 10 hours.' InfiniTime tracks | | Exception Type Specific Fields | * Threshold - The Threshold for Approaching DOT Consecutive Hours Rule One should be set to 11 Hours |
| Exception Type | DOT Consecutive Hours Rule Two | | Summary | Employee may not drive beyond the 14th consecutive hour after coming on duty, following 10 consecutive hours off duty. Off-duty time does not extend the 14-hour period. Any working duration over 14 hours is considered a Rule 2 Violation. | | Exception Type Specific Fields | * Threshold - The Threshold for Approaching DOT Consecutive Hours Rule One should be set to 11 Hours |
| Exception Type | DOT Off Duty Rule | | Summary | Drivers using the sleeper berth provision must take at least 8 consecutive hours in the sleeper berth, plus a separate 2 consecutive hours either in the sleeper berth, off duty, or any combination of the two. In other words, there must be a minimum of ten hours from when the employee punches out on one shift before they punch in again. The DOT Off Duty Rule exception occurs if the employee should punch in before taking their full ten hour break. | | Exception Type Specific Fields | * Threshold - The Threshold for Approaching DOT Consecutive Hours Rule One should be set to 11 Hours |
| Exception Type | DOT Seven Days Rule | | Summary | Employee may not drive after 60/70 hours on duty in 7/8 consecutive days. A driver may restart a 7/8 consecutive day period after taking 34 or more consecutive hours off duty. The 7/8 day period is reset if there is a consecutive break of 34 hours at any point. If this rule is broken a Rule Violation is reported. | | Exception Type Specific Fields | * Threshold - The Threshold for Approaching DOT Consecutive Hours Rule One should be set to 11 Hours |
| Exception Type | Early | | Summary | Early is an employee performance related exception used to compare employee Clock In punches to their scheduled arrival time. The Early Exception Triggers if an employee punches in prior to their scheduled start time. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | _ Schedules must be configured for employees on a given date in order for the Early Exception to Occur for the respective date. _ Scheduled Grace Periods, as set on the Scheduled Time Tab of the Rounding Rules Section on the Policy Update Form, should be configured for organizations using Employee Performance Related Exceptions such as the Early Exception. Refer to the Scheduled Grace Periods section of this document for additional details. | | Exception Trigger | The Early Exception Triggers if an employees first punch on a given date is prior to the employee's Scheduled Start Time - On Time Grace Period. For example, if an employee is scheduled to work from 8:00 AM to 5:00 PM with a 5 Minute On Time Grace Period the Early Exception will trigger if the employee punches in prior to 7:55 AM. |
| Exception Type | Early Departure | | Summary | Early Departure is an employee performance related exception used to compare employee Clock Out punches to their scheduled departure time. The Early Departure Exception Triggers if an employee punches out prior to their scheduled departure time. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | _ Schedules must be configured for employees on a given date in order for the Early Exception to Occur for the respective date. _ Scheduled Grace Periods, as set on the Scheduled Time Tab of the Rounding Rules Section on the Policy Update Form, should be configured for organizations using Employee Performance Related Exceptions such as the Early Exception. Refer to the Scheduled Grace Periods section of this document for additional details. | | Exception Trigger | The Early Departure Exception Triggers if an employee's last punch on a given date is prior to the employee's Scheduled End Time - On Time Grace Period. For example, if an employee is scheduled to work from 8:00 AM to 5:00 PM with a 5 Minute On Time Grace Period the Early Departure Exception will trigger if the employee punches out prior to 4:55 PM. |
| Exception Type | Exceeded Accrued Time | | Summary | The Exceeded Accrued Time exception triggers when an employee has a negative accrual balance. The Exceeded Accrual exception can only be viewed on the Employee Exception Detail Report as accrual exceptions are not related to employee timecards. When using the Employee Exception Detail report to view the Exceeded Accrual Exception the Date Range should match the Accrual Period for the Accrual Type in question. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | _ Accrual Types and Accrual Calculations must be configured. _ Accrual Types must be assigned to employees. _ Other Activity Types that deduct must be properly defined for each Accrual Calculation. | | Exception Trigger | _ Triggers when Time Base + Time Accrued - Time Used is less than 0. |
| Exception Type | Excessive Pay Period Hours | | Summary | The Excessive Pay Period Hours Exception is useful for identifying employees who work over a certain number of hours, as defined by the Excessive Pay Period Hours Threshold, in a single Pay Period. The Excessive Pay Period Hours Threshold should be set such that when employees work over the number of hours defined by the threshold the Excessive Pay Period Hours exception will trigger. For Example, if you wish to know if an employee works more than 50 Hours in a single pay period the Excessive Pay Period Hours Exception should be set to 50 Hours. The Exception will then alert supervisors to review the respective employee's timecard or schedule to reduce overtime hours in the future and / or redistribute hours to other employees. | | Exception Type Specific Fields | * Threshold | | Additional Required Configuration | N/A | | Exception Trigger | Triggers if Total Hours for a Single Pay Period Exceed the number of hours set on the Excessive Pay Period Hours Threshold. |
| Exception Type | Excessive Weekly Hours | | Summary | The Excessive Weekly Hours Exception is useful for identifying employees who work over a certain number of hours, as defined by the Excessive Weekly Hours Threshold, in a single Work Week. The Excessive Weekly Hours Threshold should be set such that when employees work over the number of hours defined by the threshold the Excessive Weekly Hours exception will trigger. For Example, if you wish to know if an employee works more than 50 Hours in a single work week the Excessive Weekly Hours Exception Threshold should be set to 50 Hours. The Exception will then alert supervisors to review the respective employee's timecard or schedule to reduce overtime hours in the future and / or redistribute hours to other employees. | | Exception Type Specific Fields | * Threshold | | Additional Required Configuration | N/A | | Exception Trigger | Triggers if Total Hours for a Single Work Week Exceed the number of hours set on the Excessive Pay Period Hours Threshold. |
| Exception Type | Invalid Department | | Summary | InfiniTime includes a Valid Department list within the employee table. If valid departments are assigned to employees the Invalid Department exception can be used to track punches assigned to departments that are not considered valid for the employee. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | _ Valid Departments must be configured for all employees on the Valid Departments Section of the Employee Update Form | | Exception Trigger | _ Triggers when employee's Punch Into a Department not included in the Valid Departments List on the Employee's Profile. |
| Exception Type | Late Departure | | Summary | Late Departure is an employee performance related exception used to compare employee Clock Out punches to their scheduled departure time. The Late Departure Exception Triggers if an employee punches out after their scheduled departure time. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | _ Schedules must be configured for employees on a given date in order for the Early Exception to Occur for the respective date. _ Scheduled Grace Periods, as set on the Scheduled Time Tab of the Rounding Rules Section on the Policy Update Form, should be configured for organizations using Employee Performance Related Exceptions such as the Early Exception. Refer to the Scheduled Grace Periods section of this document for additional details. | | Exception Trigger | The Late Departure Exception Triggers if an employee's last punch on a given date is after to the employee's Scheduled End Time + Late Grace Period. For example, if an employee is scheduled to work from 8:00 AM to 5:00 PM with a 5 Minute Late Grace Period the Late Departure Exception will trigger if the employee punches out after 5:05 PM. |
| Exception Type | Late Meal Break | | Summary | Late Meal Break is an employee performance related exception used to determine if Meal Breaks are taken late. The Late Meal Break Exception triggers after a certain number of hours, defined by the Late Meal Break Threshold, where the employee has not yet taken a Break. Or, if an employee has taken a break, if the duration from the employee's first punch in to the employees first break punch exceeds the Late Meal Break Threshold. For Example, if the Late Meal Break Exception Threshold is set to 6 Hours the employee must take a break within the first six hours of their shift or the Late Meal Break exception will trigger. | | Exception Type Specific Fields | _ Threshold | | Additional Required Configuration | _ Change to Break Must be Configured for either Paid Breaks, Unpaid Breaks, or Both within Employee Policies in order for employee punches to automatically be changed to breaks. _ If Change to Break is not configured the Late Meal Break Exception will trigger for every working day with total working hours in excess of the Late Meal Break Threshold. | | Exception Trigger | _ Triggers if Total Hours Between Clock In and First Clock Out Exceeds the Late Meal Break Threshold OR * If Total Hours Between Clock In and Current TIme Exceeds the Late Meal Break Threshold and the employee has not yet punched out. |
| Exception Type | Long Break | | Summary | The Long Break Exception is an employee performance related exception which compares employee Breaks Lengths to their Scheduled Break Length. The Long Break Exception triggers if an employees actual break length is longer than the length of their scheduled break. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | _ Schedules must be configured and must included a Schedule Unpaid or Paid Break for employees on a given date in order for the Early Exception to Occur for the respective date. | | Exception Trigger | _ Triggers if an employee takes a Paid Break that is longer in duration than their Scheduled Paid Break. * Triggers if an employee takes an Unpaid Break that is longer in duration than their Scheduled Unpaid. |
| Exception Type | Mandatory Rest Period | | Summary | The Mandatory Rest Period Exception is intended for Employee Fatigue Tracking purposes. InfiniTime tracks the number of hours works by employees over a given number of consecutive days and triggers the Mandatory Rest Period if employees work over Total Hours within a given number of Consecutive Days without a certain number of consecutive Off Duty Hours. | | Exception Type Specific Fields | _ Other Activity Types Counted Toward Consecutive Days _ Count Regular Hours Toward Consecutive Days _ Count OT1 Hours Toward Consecutive Days _ Count OT2 Hours Toward Consecutive Days _ Count OT3 Hours Toward Consecutive Days _ Count OT4 Hours Toward Consecutive Days _ Total Hours _ Consecutive Days _ Off Duty Hours | | Additional Required Configuration | N/A | | Exception Trigger | _ The Mandatory Rest Period Exception Triggers as follows: * + The Mandatory Rest Period Exception Triggers if an employee works more than Total Hours hours for valid hours types in consecutive days. + Hours accumulated toward Total Hours are reset after a consecutive number of hours Off Duty where the employee is off the clock and is not working. + The Mandatory Rest Period Exception triggers independently of the current Work Week. + **The Mandatory Rest Period Exception will continue to trigger every day after an employee works more than Total Hours until the employee meets the consecutive number of hours Off Duty.** + Valid Hours Types are determined as follows: + - If 'Count Regular Hours toward Consecutive Days is checked, Regular Hours will be included in the consecutive days and total hours calculation. - If âCount OT1 Hours toward Consecutive Daysâ is checked, OT1 Hours will be included in the consecutive days and total hours calculation. - If âCount OT2 Hours toward Consecutive Daysâ is checked, OT2 Hours will be included in the consecutive days and total hours calculation. - If âCount OT3 Hours toward Consecutive Daysâ is checked, OT3 Hours will be included in the consecutive days and total hours calculation. - If âCount OT4 Hours toward Consecutive Daysâ is checked, OT4 Hours will be included in the consecutive days and total hours calculation. - Other Activity Types specified on the 'Other Activity Types that Count Toward Consecutive Days' will be included in the consecutive days calculation. - Other Hours for Activity Types specified on the 'Other Activity Types that Count Toward Consecutive Days' Tab will be included in the total hours calculation if the Other Activity Type is set to 'Allow Start Time Entry'. - Regular, OT1, OT2, OT3, and OT4 hours for Other Activity Types specified on the 'Other Activity Types that Count Toward Consecutive Days Tab' which are set to 'Count as Regular Hours' and 'Allow Start Time Entry' will be included in the Total Hours calculation according to the 'Count *Hours Type* Toward Consecutive Days' Options. |
| Exception Type | Missed Punch | | Summary | The Missed Punch Exception is intended to notify supervisors when employees miss a punch. The Missed Punch Exception can be triggered in two different ways, depending on if 'Enable Missed Punch Schedule Check' option on the Company Update Form is checked. The Housekeeping Service automatically checks to determine if the Missed Punch Exception should be triggered for employees on an hourly basis. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | _ Missed Punch Threshold on the General Tab of the Overtime Section on the Policy Update Form must be set _ Enable Missed Punch Schedule Check should be set as appropriate for your organization. If your organization does not use Schedules within InfiniTime this option can be unchecked. _ Schedules must be configured for employees on a given date in order for the Missed Punch Exception to trigger based on scheduled punches. | | Exception Trigger | If 'Enabled Missed Punch Schedule Check' is checked on the Company Update Form, the Missed Punch Exception will trigger in both of the scenarios below: _ Triggers if an employee is punched in for a duration that exceeds the Missed Punch Threshold on the employee's policy. _ Triggers if an employee does not have a punch during the Early, On Time, or Late Grace Periods for a given Scheduled Punch. If 'Enabled Missed Punch Schedule Check' is unchecked on the Company Update Form, the Missed Punch Exception will trigger as follows: _ Triggers if an employee is punched in for a duration that exceeds the Missed Punch Threshold on the employee's policy. |
| Exception Type | Missing Break | | Summary | The Missing Break Exception is a performance based exception which checks for a given number of work hours without a Paid or Unpaid break on a specific date. Schedules are not required for tracking the Missing Break Exception. The Missing Break Threshold should be set to the maximum number of hours an employee is permitted to work before taking a break. For example, if the Missing Break Threshold is set to 6 hours, employees may work up to 6 hours without taking a break. After the total working duration is 6 Hours and 1 Minute, the Missing Break exception will occur. | | Exception Type Specific Fields | _ Threshold | | Additional Required Configuration | N/A | | Exception Trigger | _ Triggers if worked hours on a date exceed the Missing Break Threshold without a Paid or Unpaid Break |
| Exception Type | Missing Scheduled Punch | | Summary | The Missing Scheduled Punch Exception assists supervisors with managing missed punches and is commonly used with Exception Notifications to notify supervisors and / or employees when an employee fails to punch according to their schedule. The Missing Scheduled Punch Exception is an employee performance related exception which requires schedules to be configured. | | Exception Type Specific Fields | _ Threshold | | Additional Required Configuration | _ Schedules must be configured for employees on a given date in order for the Missing Scheduled Punch Exception to Occur for the respective date. _ Scheduled Grace Periods, as set on the Scheduled Time Tab of the Rounding Rules Section on the Policy Update Form, should be configured for organizations using Employee Performance Related Exceptions such as the Missing Scheduled Punch Exception. Refer to the Scheduled Grace Periods section of this document for additional details. _ Exception Notifications require specific configuration on the InfiniTime Server. | | Exception Trigger | The Housekeeping Service checks to determine if the Missing Scheduled Punch should be triggered for employees each minute as follows: _ For employees with schedules on the current date, the Housekeeping Service will check to see if the Missing Scheduled Punch Threshold has elapsed for each scheduled punch. _ If the Scheduled Punch Threshold has elapsed for a specific scheduled punch, the Housekeeping Service will check to see if employee has a Punch within the Scheduled Grace Periods for the respective punch. _ If no punch is present the Missing Scheduled Punch Exception will trigger. For example, let us assume the following settings: _ John Smith is scheduled to work 8:00 AM to 5:00 PM on 8/16/2013 _ John Smith is an Operations Employee. _ The Operations Policy is configured as follows: + Clock In Grace Periods for Scheduled Time are set to: - On Time = 10 Minutes - Late = 10 Minutes + Clock Out Grace Periods for Scheduled Time are set to: - On Time = 10 Minutes - Late = 10 Minutes * The Missing Scheduled Punch Threshold is set to 15 Minutes Based on John's Schedule, InfiniTime will check for Punches to determine if the Missing Scheduled Punch Exception should be triggered at 8:15 AM and 5:15 PM due to the 15 Minute Threshold set on the Missing Scheduled Punch Exception. At 8:15 AM, InfiniTime will check for a punch during the Clock In Grace Periods for the 8:00 AM Scheduled Punch. Specifically, if John does not have a punch between 7:50 AM and 8:10 AM, the Missing Scheduled Punch will trigger. At 5:15 PM, InfiniTime will check for a punch during the Clock Out Grace Periods for the 5:00 PM Scheduled Punch. Specifically, if John does not have a punch between 4:50 PM and 5:10 PM, the Missing Scheduled Punch will trigger. |
| Exception Type | Non Arrival | | Summary | The Non Arrival Exception is intended for use with managing the arrival of multiple personnel for a given facility or location and is commonly used with Exception Notifications to inform management if no employees have arrived at a given facility. The Non Arrival Threshold controls exactly when InfiniTime will trigger the Non Arrival Exception if no employees have arrived on site. In order to track employees arriving at multiple sites, the Non Arrival Exception may be inserted multiple times with different values for the Non Arrival Threshold, Department, Job, and Task. | | Exception Type Specific Fields | _ Threshold _ Department _ Job _ Task | | Additional Required Configuration | _ Schedules must be configured for employees on a given date in order for the Non Arrival Exception to Occur for the respective date. _ Exception Notifications require specific configuration on the InfiniTime Server. | | Exception Trigger | InfiniTime checks to determine if the Non Arrival Exception should be triggered every minute as follows: _ First, InfiniTime determines the earliest scheduled Clock In Time for employees for the current date _ InfiniTime then checks to determine if the Non Arrival Threshold has expired. If the threshold is a negative value, the threshold will expire prior to the earliest scheduled time. If the threshold is a positive value, the threshold will expire after the earliest scheduled time. * If the threshold has expired, InfiniTime checks for the presence one or more punches in the respective Department, Job, Task combination set on the Non Arrival Exception. If no punches exist on the respective date for the Department, Job, Task combination then the Non Arrival Exception is triggered. For example, if the first employee is scheduled to arrive at Department 'Barista' for Job 'South Ave Coffee Shop' at 4:00 AM and the Non Arrival Threshold is set to 10 minutes, the Non Arrival Threshold will expire at 4:10. At 4:10, InfiniTime will check for the presence of one or more punches in Department 'Barista' for Job 'South Ave Coffee Shop' for all employees in the database. If no punches are present for 'Barista' / 'South Ave Coffee Shop' on the respective date then the Non Arrival Exception will trigger. It should be noted that Schedule Grace Periods are not used with the Non-Arrival Exception. InfiniTime checks for the presence of a punch in the department / job / task combination at any time on the respective date. A punch at 2:00 AM, 3:00 AM, and 4:05 AM would indicate that at least one employee was on site and would prevent the exception from triggering. |
| Exception Type | Outside Schedule | | Summary | The Outside Schedule Exception occurs when an employee's punches do not align with their schedule for the respective date based upon Clock In or Clock Out Schedule Grace Periods. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | _ Schedules must be configured for employees on a given date in order for the Missing Scheduled Punch Exception to Occur for the respective date. _ Scheduled Grace Periods, as set on the Scheduled Time Tab of the Rounding Rules Section on the Policy Update Form, should be configured for organizations using Employee Performance Related Exceptions such as the Missing Scheduled Punch Exception. Refer to the Scheduled Grace Periods section of this document for additional details. | | Exception Trigger | The Outside Schedule Exception is triggered for each individual punch if the punch does not fall within Schedule Grace Periods. For example, if an employee is scheduled to work at 8:00 AM to 5:00 PM with a Clock In On Time Grace of 10 Minutes and a Clock In Late Grace of 10 Minutes the employee's Clock In Punch is expected between 7:50 AM and 8:10 AM. If the employee punches in outside of this time, then the Outside Schedule Exception will trigger. |
| Exception Type | Overtime | | Summary | The Overtime Exception occurs on any date with hours in the Overtime 1, Overtime 2, Overtime 3, or Overtime 4 fields. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | N/A | | Exception Trigger | The Overtime Exception occurs for any Punch Pair with hours in the Overtime 1, Overtime 2, Overtime 3, or Overtime 4 fields. |
| Exception Type | Short Break | | Summary | The Short Break Exception is an employee performance related exception which compares the duration of actual breaks taken by employees to the duration of scheduled breaks. The Short Break Exception triggers independently for Scheduled Unpaid and Paid Breaks. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | _ Schedules must be configured for employees on a given date in order for the Missing Scheduled Punch Exception to Occur for the respective date. _ Change to Break must be configured within InfiniTime Policies to correctly change durations during which employees are off the clock to Breaks on the Timecard. | | Exception Trigger | _ Triggers if an employee takes a Paid Break that is shorter in duration than their Scheduled Paid Break. _ Triggers if an employee takes an Unpaid Break that is shorter in duration than their Scheduled Unpaid Break. |
| Exception Type | Short Paid Break | | Summary | The Short Paid Break Exception is an employee performance related exception which compares the duration of actual breaks taken by employees to the duration of scheduled breaks. The Short Paid Break Exception triggers only for Scheduled Paid Breaks. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | _ Schedules must be configured for employees on a given date in order for the Missing Scheduled Punch Exception to Occur for the respective date. _ Change to Break must be configured within InfiniTime Policies to correctly change durations during which employees are off the clock to Breaks on the Timecard. | | Exception Trigger | * Triggers if an employee takes a Paid Break that is shorter in duration than their Scheduled Paid Break. |
| Exception Type | Short Unpaid Break | | Summary | The Short Unpaid Break Exception is an employee performance related exception which compares the duration of actual breaks taken by employees to the duration of scheduled breaks. The Short Unpaid Break Exception triggers only for Scheduled Unpaid Breaks. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | _ Schedules must be configured for employees on a given date in order for the Missing Scheduled Punch Exception to Occur for the respective date. _ Change to Break must be configured within InfiniTime Policies to correctly change durations during which employees are off the clock to Breaks on the Timecard. | | Exception Trigger | * Triggers if an employee takes a Unpaid Break that is shorter in duration than their Scheduled Unpaid Break. |
| Exception Type | Tardy | | Summary | Tardy is an employee performance related exception used to compare employee Clock In punches to their scheduled arrival time. The Tardy Exception Triggers if an employee punches in after their scheduled arrival time. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | _ Schedules must be configured for employees on a given date in order for the Early Exception to Occur for the respective date. _ Scheduled Grace Periods, as set on the Scheduled Time Tab of the Rounding Rules Section on the Policy Update Form, should be configured for organizations using Employee Performance Related Exceptions such as the Early Exception. Refer to the Scheduled Grace Periods section of this document for additional details. | | Exception Trigger | The Tardy Exception Triggers if an employee's first punch on a given date is after to the employee's Scheduled Start Time + Late Grace Period. For example, if an employee is scheduled to work from 8:00 AM to 5:00 PM with a 5 Minute Late Grace Period the Tardy Exception will trigger if the employee punches in after 8:05 AM. |
| Exception Type | Unapproved Overtime | | Summary | The Unapproved Overtime Exception occurs on any date with unapproved hours in the Overtime 1, Overtime 2, Overtime 3, or Overtime 4 fields. | | Exception Type Specific Fields | N/A | | Additional Required Configuration | In order for the Unapproved Overtime Exception to trigger, one or more of the following settings on the Overtime Rules Section of an employee's policy must be enabled: _ Overtime One Must Be Approved _ Overtime Two Must Be Approved _ Overtime Three Must Be Approved _ Overtime Four Must Be Approved | | Exception Trigger | The Unapproved Overtime Exception occurs on any date with unapproved hours in the Overtime 1, Overtime 2, Overtime 3, or Overtime 4 fields. |
| Exception Type | Under Daily Hours | | Summary | The Under Daily Hours Exception occurs if an employee's total worked hours on a given date is less than the Under Daily Hours Threshold. | | Exception Type Specific Fields | * Threshold | | Additional Required Configuration | N/A | | Exception Trigger | The Under Daily Hours Exception compares the total number of hours worked on a given date to the Under Daily Hours Threshold. If an employee's total worked hours are less than the Under Daily Hours threshold the Under Daily Hours Exception will trigger. |
| Exception Type | Under Pay Period Hours | | Summary | The Under Pay Period Hours Exception occurs if an employee's total worked hours for a pay period are less than the Under Pay Period Hours Threshold. | | Exception Type Specific Fields | * Threshold | | Additional Required Configuration | N/A | | Exception Trigger | The Under Pay Period Hours Exception compares the total number of hours worked during a given pay period to the Under Pay Period Hours Threshold. If an employee's total worked hours are less than the Under Pay Period Hours threshold the Under Pay Period Hours Exception will trigger. |
| Exception Type | Under Weekly Hours | | Summary | The Under Weekly Hours Exception occurs if an employee's total worked hours for a work week are less than the Under Weekly Hours Threshold. | | Exception Type Specific Fields | * Threshold | | Additional Required Configuration | N/A | | Exception Trigger | The Under Weekly Hours Exception compares the total number of hours worked during a given work week to the Under Work Week Hours Threshold. If an employee's total worked hours are less than the Under Weekly Hours threshold the Under Weekly Hours Exception will trigger. |