The Event tab on the Schedule Cycle form is used to add a Meal or Break event to a day in a Schedule Cycle. You can also define events that may not be used, such as when an employee is not allowed to take a break or a meal.
If the Meal or Break is configured to post automatically, the automatic event posting is triggered when the employee posts an event after the time of the scheduled automatic event. For example, if the automatic lunch is from 12:00 p.m. to 12:30 p.m., when the employee stops labor at 12:05 p.m., the automatic lunch will post. If you want to allow a punched meal or break to override an automatic one, see Meal/Break Override for the configurations needed. If you want to allow a punched meal or break to override an automatic one, see "Meal/Break Override" in your help file for the configurations needed.
See Also:
Add an Event to a Schedule Cycle
Modify an Event in a Schedule Cycle
Delete an Event from a Schedule Cycle
Event
These options are available: ATTENDANCE:BREAK and ATTENDANCE:MEAL. Typically, MEAL is used for meal breaks such as lunch, and BREAK is used for any other kind of break within the schedule
Posting Basis
This field determines when the Event will post. The following options are available:
STRICT: The Event has a specific start and stop time, regardless when the person clocks in or out. The start and stop times are defined in the Start Day, Start Time, End Day, and End Time fields
OFFSET: The Event will post for a specified number of hours after the raw timestamp of the most recent clock in, based on the Start Hours Offset and End Hours Offset. For example, the employee's schedule is 7 a.m. to 3:30 p.m. with an automatic half-hour lunch. The Posting Basis for the lunch is OFFSET, Start Hours Offset is 4, and End Hours Offset is 4.5. The employee clocks in at 6:45 a.m., which rounds to 7 a.m. based on his Rounding Policy. The OFFSET for the lunch event is based on the raw clock-in time, which is 6:45 a.m. Therefore the lunch posts from 10:45 a.m. to 11:15 a.m.
Required
Select from the following options to determine if the event is required for an employee:
MANDATORY: The employee is expected to post the Event.
OPTIONAL: The employee may post the Event but there will not be a violation if the Event is not posted.
PROHIBITED: The employee is not allowed to post the Event.
When Auto Event is set to AUTO or OVERRIDE, the Required field is always set to MANDATORY.
When Auto Event is set to PUNCH, you can select MANDATORY, OPTIONAL, or PROHIBITED.
Auto Event
This field defines how the Event will post. The following options are available:
AUTO: The Event posts automatically according to the Start Time and End Time or the Start Hours Offset and End Hours Offset.
OVERRIDE: The Event posts automatically unless it the employee posts it manually. For example, an employee is scheduled to work from 7:00 a.m. to 3:30 p.m. with a lunch break from 11:30 a.m. to 12:00 p.m. that is set to OVERRIDE. The employee works from 7:00 a.m. to 10:30 a.m. and then punches out for lunch. The employee returns from lunch at 12:30 p.m. The automatic lunch (11:30 – 12:00) will not post and the punched lunch (10:30 – 12:30) will remain. See Meal/Break Override for more information.
PUNCH: The Event posts only when the employee posts it manually.
Note: If you are using the Smart Clock feature, make sure you set Auto Event to PUNCH.
Start Day, End Day
Start Time, End Time
When you add or modify a Schedule Cycle Event, and the Posting Basis is STRICT, the Start Day, End Day, Start Time, and End Time fields will display. These four fields are used to define the date and time when the Event can post.
Start Day and End Day can be set to TODAY, YESTERDAY, or TOMORROW. For example, a schedule is from 10 PM Today to 7 AM Tomorrow. An automatic meal event is scheduled to post from 2 AM to 3 AM; both the Start Day and End Day are set to TOMORROW.
Start Time, End Time
These columns display in the grid section of the Schedule Cycle Event form. If the Posting Basis is STRICT, these fields show the date and time when the Event can start and end. The Start Time and End Time are defined by the Start Day, End Day, Start Time, and End Time fields when you add or modify a Schedule Cycle Event.
Start Hours Offset, End Hours Offset>
When the Posting Basis is OFFSET, these fields define the number of hours after the raw timestamp of the most recent clock in when the Event will start and end. For example, the Meal event has a Start Hours Offset of 4 and an End Hours Offset of 5. If the employee's raw clock-in time is 8 a.m., the Meal event will be posted from 12 p.m. to 1 p.m.
Start Early Margin
This whole number represents the number of margin units before a meal or break is supposed to start that a person can leave for a meal or break without receiving a violation notice. Margins are only used when Auto Event is set to PUNCH or OVERRIDE.
The Margin Unit field determines if the Start Early Margin is in hours, minutes, or seconds. The default value is minutes.
Start Late Margin
This whole number represents the number of margin units after a meal or break is supposed to start that a person can leave for a meal or break without receiving a violation notice. Margins are only used when Auto Event is set to PUNCH or OVERRIDE.
The Margin Unit field determines if the Start Late Margin is in hours, minutes, or seconds. The default value is minutes.
End Early Margin
This whole number represents the number of margin units before the meal or break is supposed to end that a person can return from the meal or break without receiving a violation notice. Margins are only used when Auto Event is set to PUNCH or OVERRIDE.
The Margin Unit field determines if the End Early Margin is in hours, minutes, or seconds. The default value is minutes.
End Late Margin
This whole number represents the number of margin units after the meal or break is supposed to end that a person can return from the meal or break without receiving a violation notice. Margins are only used when Auto Event is set to PUNCH or OVERRIDE.
The Margin Unit field determines if the End Late Margin is in hours, minutes, or seconds. The default value is minutes.
Margin Unit
This unit of time is used to define the Start Early Margin, Start Late Margin, End Early Margin, and End Late Margin. Select Hours, Minute, or Seconds.
The Schedule Cycle Event tab will always display the value in Minutes.
When you modify a Person Schedule Event, the form will display these values using the largest possible Margin Unit (Hours, Minutes, or Seconds) for which all the margin values can be expressed as integers. For example, you enter 120 Seconds for the margin values and click Save. When you modify the record, the margin values will display as 2 Minutes. If you enter 90 seconds for the margin values and click Save, the form will display the values as 90 Seconds when you click Modify.
Update Date, Updated By
These fields display when the record was created or updated, and the person who created or updated the record.
Click Main Menu > Administration > Schedules > Schedule Cycle.
Find the Schedule Cycle to which you want to add the event.
Select the Day in the schedule cycle to which you want to add the event.
On Event tab, click Add.
Enter information in the required fields and click Save.
Click Main Menu > Administration > Schedules > Schedule Cycle.
Find the Schedule Cycle that has the event you want to modify.
Select the Day in the schedule cycle that has the event you want to modify.
On Event tab, select the event you want to change and click Modify.
Modify the field values and click Save.
Click Main Menu > Administration > Schedules > Schedule Cycle.
Find the Schedule Cycle that has the event you want to remove.
Select the Day in the schedule cycle that has the event you want to remove.
On Event tab, select the event you want to remove and click Delete.
Click OK to confirm the action.