Architecting Split-Shift Scheduling Patterns for Extended Hours Coverage with Part-Time Staff

How-To-Articles
1

Architecting Split-Shift Scheduling Patterns for Extended Hours Coverage with Part-Time Staff

What This Guide Covers

This guide details the configuration of complex split-shift schedules within NICE CXone WFM to manage extended hours coverage using part-time agents. You will configure custom shift templates, enforce availability constraints, and utilize the Optimization Engine to generate schedules that minimize overtime while maintaining strict Service Level Agreement (SLA) adherence during peak and off-peak windows.

Prerequisites, Roles & Licensing

  • Licensing Tier: NICE CXone WFM Advanced or Ultimate (Optimization Engine required). Standard WFM allows manual scheduling but lacks the algorithmic capability to balance split-shift constraints efficiently at scale.
  • Permissions:
    • WFM > Scheduling > Edit Schedule
    • WFM > Scheduling > Create/Edit Shift Templates
    • WFM > Staffing > Edit Staffing Requirements
    • WFM > Optimization > Run Optimization
  • External Dependencies:
    • Defined Skill Groups mapped to the queues requiring extended coverage.
    • Configured Break Policies that allow for split-break assignments.
    • Established Agent Availability records for part-time staff indicating their max daily hours and preferred split-shift windows.

The Implementation Deep-Dive

1. Configuring Split-Shift Templates with Hard Constraints

The foundation of split-shift scheduling lies in the definition of the shift template itself. Unlike standard continuous shifts, a split shift requires explicit definition of the “on” and “off” periods within a single calendar day. In NICE CXone, this is managed through Shift Templates and Work Patterns.

Creating the Split Shift Template

Navigate to Admin > WFM > Shift Templates. Create a new template named Split-Evening-PartTime.

The critical configuration here is the Time Intervals. You must define two distinct work blocks.

The Trap: Many administrators attempt to create a single 8-hour shift and manually insert a 4-hour break in the middle. This is architecturally incorrect for split shifts. A break is a paid or unpaid pause within a continuous employment window. A split shift is two separate work windows. If you model it as a single shift with a long break, the Optimization Engine treats the entire block as a single resource unit. It cannot split the agent into two independent resource pools for different peak windows. This results in “dead air” where the agent is marked as “on shift” but not working, wasting capacity during the morning peak.

Correct Configuration:

  1. Set Shift Type to Split.
  2. Define Work Block 1:
    • Start: 09:00
    • End: 12:00
    • Duration: 3 hours
  3. Define Work Block 2:
    • Start: 16:00
    • End: 20:00
    • Duration: 4 hours
  4. Set Total Daily Hours: 7 hours (System calculates this, but verify it matches your labor rules).

Architectural Reasoning: By defining discrete work blocks, the Optimization Engine recognizes that this agent is available for Queue A during 09:00-12:00 and Queue B during 16:00-20:00. This allows the engine to place the agent in the most critical skill group for each specific window, maximizing utility per FTE (Full-Time Equivalent).

Enforcing Minimum Rest Between Blocks

Configure the Rest Period between Work Block 1 and Work Block 2.

  • Minimum Rest: 4 hours
  • Max Rest: 12 hours

The Trap: Setting a flexible rest period without a maximum can lead to scheduling anomalies where the engine pushes the second block too far into the night to satisfy a late-evening peak, violating labor laws or union contracts regarding night shifts. Always cap the maximum rest to ensure the shift ends within business operating hours.

2. Defining Staffing Requirements with Granular Intervals

Split shifts are only valuable if the staffing requirements reflect the volatility of demand across the day. If your staffing profile is flat, a split shift offers no advantage over a standard shift. You must configure Staffing Profiles with high-resolution intervals.

Configuring the Staffing Profile

Navigate to Staffing > Profiles. Create a new profile named ExtendedHours-Granular.

  1. Set Interval Duration to 15 minutes.
    • Why 15 minutes? Split shifts often target specific “micro-peaks” (e.g., post-lunch support at 13:00 or pre-close rush at 19:00). Hourly intervals smooth out these spikes, causing the optimizer to understaff the peak or overstaff the trough. 15-minute granularity allows the engine to align the start/end of split blocks precisely with demand curves.
  2. Import or manually enter the Required FTEs for each 15-minute slot.
    • Ensure the data reflects the net available agents. If your shrinkage is 20%, the required FTEs must be inflated accordingly.

The Trap: Using “Average” demand instead of “Percentile” demand (e.g., 90th percentile) for split-shift windows. Part-time split-shift agents are often less experienced or have higher variability in handling time. If you schedule to the average, you will miss SLAs during the split-shift windows. Schedule to the 90th or 95th percentile for these specific windows to buffer against performance variance.

3. Configuring Agent Availability and Preferences

The Optimization Engine cannot schedule an agent for a split shift if their availability record does not explicitly permit it. Part-time staff must have their Availability records configured to match the split-shift windows.

Setting Individual Availability

Navigate to Staffing > Agents > [Agent Name] > Availability.

  1. Clear all existing availability for the target days.
  2. Add Availability Block 1:
    • Start: 09:00
    • End: 12:30 (Includes buffer for break/prep)
  3. Add Availability Block 2:
    • Start: 15:30 (Includes buffer for break/prep)
    • End: 20:00

Architectural Reasoning: The buffers (09:00 vs 09:00 start, 12:00 vs 12:30 end) are critical. They allow the Optimization Engine to place the agent in a shift that starts at 09:00 but ends at 12:00, even if the agent is technically available until 12:30. Without this buffer, the engine may reject the split shift template because the template end time (12:00) does not perfectly align with the availability end time (12:00) if there are any rounding errors or timezone discrepancies.

Enforcing Daily Hour Limits

In the Agent Settings, set Max Daily Hours to 7 and Max Weekly Hours to 28 (for a 4-day work week).

The Trap: Failing to set a Min Daily Hours constraint. If you do not set a minimum, the optimizer might schedule a part-time agent for a single 1-hour block on a low-demand day, leaving the rest of their availability empty. This creates administrative overhead for payroll and reduces the agent’s sense of stability. Set Min Daily Hours to 4 to ensure that if an agent is scheduled, they receive a meaningful portion of their shift.

4. Running the Optimization Engine with Split-Shift Constraints

With templates, staffing, and availability configured, you must now configure the Optimization Profile to prioritize split-shift utilization.

Configuring the Optimization Profile

Navigate to Scheduling > Optimization Profiles. Create a new profile named SplitShift-Optimized.

  1. Objective Function: Set to Minimize Overtime and Maximize Schedule Adherence.
  2. Constraints:
    • Enable Split Shifts Allowed.
    • Set Max Split Shifts Per Day to 1. (Allowing more than one split per day creates excessive context switching for the agent, reducing quality.)
    • Set Min Continuous Work to 2 hours. (Prevents the engine from creating “micro-shifts” of 30 minutes, which are operationally unviable.)

The Trap: Ignoring the Skill Coverage constraint. If your part-time staff are multi-skilled, the optimizer might place them in a low-volume skill group during their first block and a high-volume skill group during their second block. This is acceptable. However, if they are single-skilled, ensure the staffing requirements for that specific skill group are high during both split windows. If the demand for Skill A is low at 16:00, the engine will not schedule the agent for the second block, leaving the agent with only a 3-hour day. This violates the “Min Daily Hours” constraint and causes schedule rejections.

Solution: Use Skill-Based Staffing Requirements. Ensure that the staffing profile for the specific skill group held by the part-time staff reflects the demand during both split windows. If the demand is low in one window, consider cross-training the part-time staff to a secondary skill that has high demand in that window.

Executing the Optimization

  1. Navigate to Scheduling > Optimization.
  2. Select the Week and Group (e.g., “Part-Time Evening Support”).
  3. Select the Optimization Profile: SplitShift-Optimized.
  4. Click Run Optimization.

Architectural Reasoning: The engine will now iterate through thousands of possible schedule combinations. It will prioritize placing agents in split shifts only if it reduces the total number of FTEs required to meet the staffing profile. If a full-time agent can cover the gap more efficiently, the engine will prefer the full-time agent. This is why you must segment your optimization by group. Run optimization for “Full-Time Staff” and “Part-Time Split Shift Staff” separately to ensure the part-time pool is fully utilized before spilling over to full-time overtime.

Validation, Edge Cases & Troubleshooting

Edge Case 1: The “Ghost” Availability Error

The Failure Condition: The Optimization Engine returns an error stating “No valid schedule found for Agent X,” despite Agent X having availability and a valid split-shift template.

The Root Cause: Timezone mismatches between the Shift Template, Agent Availability, and Staffing Profile.

  • The Shift Template is defined in UTC.
  • The Agent Availability is defined in Agent Local Time.
  • The Staffing Profile is defined in Queue Timezone.

If the Agent is in EST and the Queue is in PST, a 09:00 EST shift is 06:00 PST. If the Staffing Profile expects coverage at 09:00 PST, the engine sees no overlap.

The Solution:

  1. Standardize all configuration to UTC for internal logic.
  2. In the Staffing Profile, ensure the timezone is set to the Queue’s Operational Timezone.
  3. In the Agent Availability, ensure the timezone is set to the Agent’s Local Timezone.
  4. In the Shift Template, use Relative Times (e.g., “Start at 09:00 Local”) rather than absolute UTC times. This allows the template to adjust automatically based on the agent’s location.

Edge Case 2: Break Policy Violations in Split Shifts

The Failure Condition: The generated schedule places a 30-minute break in the middle of the 4-hour rest period between Work Block 1 and Work Block 2.

The Root Cause: The Break Policy is configured to assign breaks based on “Total Shift Duration” rather than “Work Block Duration.” If the policy states “Agents working > 4 hours must take a 30-minute break,” the engine sees the total shift as 7 hours and attempts to insert a break. It cannot insert the break within the work blocks (as they are too short) and defaults to the rest period.

The Solution:

  1. Create a Custom Break Policy named Split-Shift-Breaks.
  2. Set Break Trigger to Work Block Duration > 2 hours.
  3. Set Break Assignment to Within Work Block.
  4. Assign this policy to the Split-Evening-PartTime shift template.
  5. Ensure the Rest Period between blocks is excluded from break calculations by setting Include Rest Period in Break Calculation to False.

Edge Case 3: Skill Coverage Gaps During Transitions

The Failure Condition: SLA breaches occur during the transition from Work Block 1 to Work Block 2 (e.g., 12:00-16:00).

The Root Cause: The part-time staff are offline during this gap, and the full-time staff are not sufficiently covered. The Optimization Engine optimized for the split windows but ignored the gap.

The Solution:

  1. Review the Staffing Profile for the gap period (12:00-16:00).
  2. Ensure the Required FTEs for this period are met by full-time staff or other part-time groups with different shift patterns.
  3. If the gap is consistent, consider staggering the split shifts. For example, Group A works 09:00-12:00 and 16:00-20:00. Group B works 10:00-13:00 and 17:00-21:00. This creates overlap during the transition periods, reducing the risk of SLA breaches.

Official References