Employee Event
Employee Events are generated when Employee Points rules exceed the established parameters and trigger your progressive discipline program. These rules are part of Attendance Point Tracking, which is a process for recording and reporting attendance infractions. Employee Event work rules and Employee Points work rules determine attendance infractions by comparing discrepancies between employee's schedules and their actual time worked.
For example, an Employee Event may be recorded when an employee is assessed 10 points within a period of 180 days, for which your discipline program stipulates that an employee receive a written warning. A listing of an employee's exceptions can be found in the Events tab on the Review Time Card screen.
The Employee Events work rule type includes the following work rules:
Base Points Violation Event
Description | Generates an Employee Event based on the accumulation of violation points as configured. All options are configurable. | |
Parameters | Parameter | Description |
Action | Enter a custom action to be associated with the violation (for example, Verbal Warning, Written Notice). | |
Event Identifier | Numeric identifier for this event rule. This identifier can be duplicated to create groups of events. | |
Execution Priority | Defines the priority order in which the rule is run. The rule with the highest priority number runs first. For example, a rule with an Execution Priority of 4 will run before a rule with an Execution Priority of 3. | |
Number of Units | Number of units (summed points or counts of events) necessary for a violation to occur. | |
Unit Type | Type of unit to search for (for example, Event, Point). | |
Unit Group Identifier(s) | A custom identifier used to define a Point, Point Type, or Event group and may also be used to restrict the unit calculation. If this field is empty, all points or events will used used. | |
Number of Past Days | Defines how far back in time (number of days) points or events should be summed or counted. For example, if the Number of Past Days field is set to 365, the work rule will count all points or events that accumulated within the past 365 days. | |
"Marker" Event Identifier(s) | Defines the priority of events that, when found within the period of time defined by the Number of Past Days property, will restrict the time period being summed. | |
Adjust Range by Latest "Marker" Event | If the check box is selected, units that accumulated prior to the latest "Marker" event will not be counted. | |
"Marker" Event Must Exist | If the check box is selected, at least one event of the "Marker" events must be found within the date range. | |
Add Points from Last "Marker" Event | If the check box is selected, the points that were totaled on the last "Marker" event will be included in the point count. This is only valid when summing "Point" unit types. | |
Units Required after "Marker" Event | Number of units that must be found after the last "Marker" event. Note: If the Add Points from Last Marker Event check box is selected, this parameter is not applicable. | |
Document Template | Template to use when printing the document. |
Points Award Event
Description | Points Award Event | |
Parameters | Parameter | Description |
Action | Enter a custom action to be associated with the event. | |
Document Template | Template to use when printing the document. | |
Effective Date | The effective date the initial event will be checked against. Note:Â Only applicable if the Include Initial Event check box is selected. | |
Event Group/Item ID | A unique numeric or group identifier for this event rule. | |
Include Initial Event | If the check box is selected, an event is generated the first time the condition is met (after the effective date). | |
Number of Past Days | Defines how far back in time (number of days) points or events should be summed or counted. For example, if the Number of Past Days field is set to 365, the work rule will count all points or events that accumulated within the past 365 days. | |
Priority | Defines the priority order in which the rule is run. The rule with the highest priority number runs first. For example, a rule with an Execution Priority of 4 will run before a rule with an Execution Priority of 3. |