Configure Predictive Scheduling

Configure the system setting to enable predictive scheduling on the tenant.

1. In Administration > Application Setup > System Configuration > System Settings, select the Global Values tab.
2. Set the global.PredictiveScheduling.enabled key to True.
3. Click Tap Save.

Function access profile must be configured to allow managers to set up, view and edit predictive scheduling tags.

1. Go to Administration > Application Setup > Access Profiles > Function Access Profiles.

2. Select a profile and go to Manager - Common Setup > Schedule Configuration.

3. Set Predictive Scheduling Setup to Allowed.
4. Click Tap Save & Return.
5. Select a profile and go to Manager - Department Manager > Scheduling.
6. Set Delete Predictive Tags to:
   1. Allowed: Manager can delete a predictive tag by using the Delete option in the employee glance in the Schedule Planner
   2. Disallowed: Manager does not have the Delete option available in the employee glance and so cannot delete tags.
7. Set Restore Predictive Tags to:
   1. Allowed: Manager can restore a previously deleted tag by using the Restore option in the employee glance in the Schedule Planner
   2. Disallowed: Manager does not have the Restore option available in the employee glance and so cannot restore tags.
8. Click Tap Save & Return.

Define the tag to display in the Schedule for predictive scheduling rule violations.

1. Go to Administration > Application Setup > Scheduler Setup > Tag Definitions.
2. Click Tap Create.
3. Enter a Name and optional Description.
4. In Tag Color, select a color for this tag to display in the Schedule.
5. In Can Override Color, select Yes to allow managers to select a different color for their own view of the schedule tag. This setting does not affect the colors in the employees' calendars.
6. In Visible to Employees, select Yes to show the tags in employees' calendars.
7. In Tag Type, select Predictive.
8. Click Tap Save.

The system uses the schedule change criteria to specify which schedule actions to monitor and when these actions are done relative to the shift or schedule period start time.

1. Go to Administration > Application Setup > Scheduler Setup > Predictive Scheduling > Schedule Change Criteria.
2. Click Tap Create.
3. Enter a Name and an optional Description for the schedule change criterion.
4. In Schedule Change, select the schedule action to track.
• Shift Added — Tracks when a new shift is added or an existing shift is assigned to an employee.
• Shift Deleted — Tracks when an existing shift is deleted or unassigned.
• Shift Extended — Tracks when the duration of an existing shift is extended by more than the specified amount of time.
• Extended More Than (minutes) — Specify the minimum amount of time (in minutes) that the shift must be extended by in order to trigger the Shift Extended criteria. This field is required.
• Extended Less Than or Equal to (minutes) — Specify the maximum amount of time (in minutes) that the shift must be extended by in order to trigger the Shift Extended criteria. This field is optional.
• Shift Shortened — Tracks when the duration of an existing shift is shortened by more than the specified amount of time.
• Shortened More Than (minutes) — Specify the minimum amount of time (in minutes) that the shift must be shortened by in order to trigger the Shift Shortened criteria. This field is required.
• Shortened Less Than or Equal to (minutes) — Specify the maximum amount of time (in minutes) that the shift must be shortened by in order to trigger the Shift Shortened criteria. This field is optional.
• Shift Moved — Tracks when both the start time and end time of an existing shift change, but there is no change to the duration of the shift.
• Moved More Than (minutes) — Specify the minimum amount of time (in minutes) that the shift must be moved by in order to trigger the Shift Moved criteria. This field is required.
• Moved Less Than or Equal to (minutes) — Specify the maximum amount of time (in minutes) that the shift must be moved by in order to trigger the Shift Moved criteria. This field is optional.

The following two schedule change criteria parameters are only applicable to Los Angeles jurisdictions, to ensure that correct premium payouts are made in compliance with Los Angeles predictive scheduling legislation. You can configure a predictive scheduling rule that pays a different premium for shifts moved within the same day versus shifts moved to a different calendar day.

Select one or both of the following parameters to track the start time of moved shifts.

Note: These parameters are available only if the Shift Moved Parameters for Predictive Scheduling Schedule Change feature switch is enabled.

• Start time of moved shift remains on the same calendar day — Select this option to track schedule changes where a shift has moved within the same calendar day.
• Start time of moved shift is no longer on the same calendar day — Select this option to track schedule changes where a shift has moved to a different calendar day.
• Shift Moved and Extended — This criteria is only applicable to San Francisco jurisdictions. Tracks when both the start time and end time of an existing shift change, and the duration of the shift is extended.
  • Moved and Extended More Than (minutes) — Specify the minimum amount of time (in minutes) that the shift must be moved and extended by in order to trigger the Shift Moved and Extended criteria. This time represents the total amount of time that the shift has moved plus the amount of time that the shift has been extended. This field is required.
  • Moved and Extended Less Than or Equal to (minutes) — Specify the maximum amount of time (in minutes) that the shift must be moved and extended by in order to trigger the Shift Moved and Extended criteria. This time represents the total amount of time that the shift has moved plus the amount of time that the shift has been extended. This field is optional.
  Examples
  • An employee has a shift from 8a - 4p.
  • A Shift Moved and Extended criterion is configured to trigger when the moved and extended total is more than 90 minutes but less than or equal to 120 minutes: Moved and Extended More Than (minutes) = 90; Moved and Extended Less Than or Equal to (minutes) = 120.
  • If the manager changes the shift to 7:30a - 4:30p, the shift has been moved by 30 minutes and extended by 60 minutes. The criterion is not triggered because 30 minutes plus 60 minutes is not greater than 90 minutes.
  • If the manager changes the shift to 7:30a - 5p, the shift has been moved by 30 minutes and extended by 90 minutes. The criterion is triggered because 30 minutes plus 90 minutes is 120 minutes, which is greater than 90 minutes and less than or equal to 120 minutes.
• Shift Moved and Shortened — This criteria is only applicable to San Francisco jurisdictions. Tracks when both the start time and end time of an existing shift change, and the duration of the shift is shortened.
  • Moved and Shortened More Than (minutes) — Specify the minimum amount of time (in minutes) that the shift must be moved and shortened by in order to trigger the Shift Moved and Shortened criteria. This time represents the total amount of time that the shift has moved plus the amount of time that the shift has been shortened. This field is required.
  • Moved and Shortened Less Than or Equal to (minutes) — Specify the maximum amount of time (in minutes) that the shift must be moved and shortened by in order to trigger the Shift Moved and Shortened criteria. This time represents the total amount of time that the shift has moved plus the amount of time that the shift has been shortened. This field is optional.
  Examples
  • An employee has a shift from 8a - 4p.
  • A Shift Moved and Shortened criterion is configured to trigger when the moved and shortened total is more than 60 minutes but less than or equal to 120 minutes: Moved and Shortened More Than (minutes) = 60; Moved and Shortened Less Than or Equal to (minutes) = 120.
  • If the manager changes the shift to 7:30a - 3p, the shift has been moved by 30 minutes and shortened by 30 minutes. The criterion is not triggered because 30 minutes plus 30 minutes is not greater than 60 minutes.
  • If the manager changes the shift to 7a - 2:30p, the shift has been moved by 60 minutes and shortened by 30 minutes. The criterion is triggered because 60 minutes plus 30 minutes is 90 minutes, which is greater than 60 minutes and less than or equal to 120 minutes.
Note: If you configure both the Shift Moved and Extended and Shift Extended criteria or the Shift Moved and Shortened and Shift Shortened criteria in the same Predictive rule, configure a trigger priority so that only one bonus is paid out if both triggers occur. For more information, see Set up the predictive scheduling triggers:.
• Location Changed — Tracks shift location changes that occur at the specified Location Type during the change detection period.

  • In Location Type, select a location type that has been defined in Business Structure Setup > Jobs and Business Structure. Only those Location Types that are active as of the current day are displayed.

    When an employee's shift location is changed in at least one of the shift's segments, the system triggers a predictive penalty if any location is changed that has a Location Type with a hierarchy greater than or equal to the selected Location Type.

    Example:

    Suppose the defined Location Type hierarchy is Banner/District/Store/Department/Job, and the selected Location Type is Store because the organization only wants to trigger predictive penalties if the employee is moved to a different store.

    An employee has been scheduled to work at Eastern Seaboard/New York City/Downtown Store/Floor/Greeter when the schedule is posted. In this Business Structure path, the Downtown Store node has the Location Type of Store. If the employee is rescheduled to another job in Downtown Store, the system does not generate a predictive penalty. However, if the employee is moved to a store other than Downtown Store, the system generates a predictive penalty.

    For more information about Location Types, see Locations.

    Note: The system cannot evaluate Location Changed criteria for Location Types that have expired. If the specified Location Type has expired, you must edit the criteria to select a different Location Type.

5. In Shift Qualifier, select the shift profile set to filter the specific types of shifts you want to track. For example, you may want to track shifts of a certain length or on a certain day of the week. If no Shift Qualifier is specified, all shifts are tracked.
6. Under Change Detection Period, specify when you want changes to the schedule to be detected.
   Note: The employee's time zone, not the manager's, is used for time calculations when evaluating when schedule changes are made.
   1. In Detection Relative to Start Of, select either Shift or Schedule Period. The default setting is Shift.
   2. If you select Shift: 
      • Specify the interval of time and the units (minutes, hours, or days) for the change detection period. This interval is based on future schedule changes.

      For example, if you want changes to the schedule that occur between 24 hours and 168 hours before the start of a shift, enter 24 in Between (Greater Than or Equal To), enter 168 in And (Less than), and select Hours in Units.

   3. If you select Schedule Period, you can specify a rolling period for tracking changes. When a change occurs during the Edit Period, the dates in the schedule specified in the Schedule Change Period are tracked.
      1. Specify the start date in Edit Period Start and the end date in Edit Period End of the time period during which the manager can edit and save changes to the schedule.
      2. Specify the start date in Schedule Change Period Start and the end date in Schedule Change Period End.

      The Current Edit Detection Period dates and Current Schedule Change Detection Period dates display in the Change Detection Period section to help you track the current rolling period.

      Example: If you specify an Edit Period from 12/29/19 to 1/4/20, and a Schedule Change Period from 12/29/19 to 1/11/20, the rolling period dates that display on 1/13/20 would be: 

      Current Edit Detection Period: 1/12/2020 to 1/18/2020

      Current Schedule Change Detection Period: 1/12/2020 to 1/18/2020

   4. Select Detect Past Changes if you want to detect schedule changes to shifts that have already occurred.
7. Click Tap Save.
8. Configure additional schedule change criteria as needed.

Create predictive scheduling bonus rules to define how the bonuses are calculated.

1. Go to Administration > Application Setup > Scheduler Setup > Predictive Scheduling > Predictive Scheduling Bonuses.
2. Click Tap Create.
3. Enter a Name and optional Description.
4. In Bonus Pay Code, select a standard or money-based pay code from the list.

It s recommended that you create a pay code, such as Predictive Penalty, to use specifically for tracking predictive scheduling bonuses. For information about creating a pay code, see Paycodes.

5. In Bonus Amount, select the bonus type and amount:
   • Fixed amount — Enter the number of hours or the monetary amount for the penalty.
   • Percentage of total work time duration — Enter a percentage of the shift length for the penalty.
   • Percentage of modified work time duration — Enter a percentage of the modified shift length for the penalty.
   Note: You can modify an existing bonus, for example, if an incorrect bonus amount was configured. When a bonus is changed, the totalizer re-evaluates existing tags in the schedule and updates them to reflect the new bonus value. Tags included in signed-off periods are not updated.

6. In Wage Rate, select the wage type and amount

   • Percentage of regular wage rate — Enter a percentage of employee's regular wage rate to use for the penalty.
   • Other wage rate per hours — Enter a monetary amount to use for the wage rate for the penalty.
7. Click Tap Save.
8. Create additional bonus rules as necessary.

Create predictive scheduling rules using a combination of the schedule change criteria and the predictive scheduling bonus rules.

1. Go to Administration > Application Setup > Scheduler Setup > Predictive Scheduling > Predictive Scheduling Rules.
2. Click Tap Create.
3. Enter a Name for the rule.
4. In Version Effective Dates, select New Version.
5. In Effective Date, select the date on which the predictive scheduling rule takes effect. For example, you may need to configure the rule and set a date in the future for the rule go into effect due to upcoming legislation changes around predictive compensation.
6. Enter an optional Description.
7. Select Exclude employee initiated Self-Service requests if you want the system to ignore detecting schedule changes that are initiated by employees.
8. In Tag, select the predictive scheduling tag to display to managers in the schedule.

One or more predictive scheduling tags must be created before you can select it from the list. For more information about creating a tag, see Tag Definitions.

9. Set up the predictive scheduling triggers:
1. Under Predictive Scheduling Triggers, click tap Create.
2. In Priority, specify the priority that the trigger has over the other triggers in the list. You can enter an integer value greater than or equal to 1. A value of 1 is the highest priority. Lower numbers indicate a higher priority; higher numbers indicate a lower priority. For example, a trigger with a Priority of 1 has a higher priority that another trigger with a Priority of 4.​

This priority setting enables you to specify which criteria is used to pay out predictive scheduling bonuses when multiple Schedule Change Criteria are triggered simultaneously. The trigger with the highest priority is the one for which the bonus is paid out.

You can assign the same priority to more than one trigger. If multiple triggers have the same highest priority and are triggered simultaneously, the system adds the bonuses corresponding to the Schedule Change Criteria for those triggers and the total sum is what is paid out.

Note: When creating a new trigger, the default value is empty and you are required to enter a priority value. For existing triggers, a priority value of 10 is assigned by default.

3. Select a Schedule Change Criteria from the list.
4. Select a Predictive Scheduling Bonus from the list.
5. Click Tap Save. Add additional triggers if desired.

The predictive scheduling triggers are sorted in descending order based on the Priority.

10. Click Tap Save.

Apply the predictive scheduling rule to a location in the business structure using a location profile.

1. Go to Administration > Application Setup > Scheduler Setup > Location Settings > Location Profiles.
2. Click Tap New.
3. Enter a Name for the profile and an optional Description.
4. In Predictive Scheduling Rule, select a rule from the list to use for this location.
5. Click Tap Save and Assign to Location.
6. In Location Selection, select the location to assign the predictive scheduling rule to, then click tap OK.

By default, predictive compensation is paid to all employees when the process is enabled. You can configure the system to specify whether predictive compensation is paid out for specific employees.

1. Go to Maintenance > People Information.
2. Click Tap the employee's name to display their Person Record.
3. Click Tap Scheduling > Scheduler.
4. In the Process Predictive Scheduling Changes column, select one of the following:

• Note: This field can only be blank when no value has been assigned. Once you have set it to True or False, it cannot be set to blank again.

• True: Enables the predictive scheduling process for the employee, as of the specified Effective Date.
• Blank (Default): When left blank, the system behaves as if it were set to True, but you cannot select an Effective Date. The system uses the current date for the Effective Date.
• False: Disables the predictive scheduling process for the employee, as of the specified Effective Date .
5. Specify the Effective Date.

The Effective Date is the date on which predictive scheduling processing takes effect for the employee or on which predictive scheduling processing is no longer in effect. It references the date that edits are made to the schedule and not the date of the scheduled shift. The Effective Date can only be set to a date in the future (tomorrow or later); it cannot be set to the current date or a past date.

For example, if you disable the predictive scheduling process for an employee, and specify an Effective Date of 12/1/2021, any schedule edits made prior to 12/1 (regardless of the scheduled shift date) are processed through Predictive Scheduling.

6. Click Tap Save.

When shifts are edited, the Effective Date of the Predictive Scheduling Rule is determined by the system as follows:

• When a shift that is in the past is edited, the system uses the date when the shift started as the Effective Date.
• When a shift that either starts today or on a date in the future, the system uses the date that the edit was made as the Effective Date.

For more information, see the People Information > Scheduling help topic.

By default, a predictive scheduling rule assigned to a location is applied to all employees working at that location. You can configure the system to apply a different predictive scheduling rule for an employee when they work a job that has a predictive scheduling rule applied through a location profile.

1. Go to Maintenance > People Information.
2. Click Tap the employee's name to display their Person Record.
3. Click Tap Scheduling > Scheduler.
4. In the Process Predictive Scheduling Rule Override column, select the predictive scheduling rule to apply to the employee.
5. Specify the Effective Date for the rule override to take effect.
6. Click Tap Save.

For more information, see the People Information > Scheduling help topic.