Workforce Engagement Management

Hi @Paul Wood,

Can't wait to see this one in action, will save us hours when entering Time-Off requests.

We were previously unable to use "Full-Day" as it marked all staff starting their shifts at Midnight GMT, regardless of their designated shift (AM (05:00 to 06:59 start), Day (07:00 - 10:59), Afternoon (11:00 - 17:59), Midnight (18:00 - 00:00), which meant the system would only pay day shift penalties.

Just confirming the rosters are created using the confines of the work plan?

Regards

Wayde

hi @Wayde Masters, 

It is worth noting that the Time Off activity will still span 00:00 - 00:00 for a full-day request, but it will have a start and end time associated with it.

Paul

Hi @Paul Wood,

Can't wait to see this one in action, will save us hours when entering Time-Off requests.

We were previously unable to use "Full-Day" as it marked all staff starting their shifts at Midnight GMT, regardless of their designated shift (AM (05:00 to 06:59 start), Day (07:00 - 10:59), Afternoon (11:00 - 17:59), Midnight (18:00 - 00:00), which meant the system would only pay day shift penalties.

Just confirming the rosters are created using the confines of the work plan?

Regards

Wayde

hi @Wayde Masters, 

It is worth noting that the Time Off activity will still span 00:00 - 00:00 for a full-day request, but it will have a start and end time associated with it.

Paul

Hi @Paul Wood,

Can't wait to see this one in action, will save us hours when entering Time-Off requests.

We were previously unable to use "Full-Day" as it marked all staff starting their shifts at Midnight GMT, regardless of their designated shift (AM (05:00 to 06:59 start), Day (07:00 - 10:59), Afternoon (11:00 - 17:59), Midnight (18:00 - 00:00), which meant the system would only pay day shift penalties.

Just confirming the rosters are created using the confines of the work plan?

Regards

Wayde

Hi @Paul Wood,

We attempted the Full-Day Time Off, and tested it on an already published week, so we could see how it impacts our Payroll Export File.

The Agent was scheduled Monday to Thursday - 12:00 - 20:00, an Afternoon shift, which would attract an afternoon penalty payment if worked, therefore, while on leave, Australian Industrial Relation rules require them to be paid the same penalties, so that they are no worse off for going on leave.

Friday was a Day off, then Saturday & Sunday were 10:00 -18:00 shifts.

The Full-Day Time off correctly identified the shift as 12:00 - 20:00, but then when applied to the schedule, applied from 00:00 - 00:00

When the Payroll Export File has been created, it has then listed the shifts as 09:30 - 17:30 (An 8 hour shift)

09:30 = Midnight GMT + 09:30 (Our Local Time-zone in Adelaide Australia).

The problem is that an 09:30 shift does not attract any penalties, which would result in under-paying our staff member, and then open us up to SIGNIFICANT regulatory fines for under-paying workers (Google - Woolworths, JB Hi-Fi, to see how serious our regulators are about underpayment of workers).

The Friday shift shows as 09:30 - 09:30 - Zero hours, but preference would be for the record to not exist at all, the same as if no shift was in Genesys WEM

Saturday and Sunday show as 09:30 - 17:30, rather than the original 10:00 - 18:00

To correct this issue we need to make it a partial day and manually enter a start and end-time, to ensure we meet our reporting obligations.

We really need this feature to ONLY apply the Time off to the segments as dictated by the workplan.

Because the Export File to our Payroll system MUST reflect the correct shift ranges as determined by the work-plan, to ensure the correct payment of all penalties and allowances.

Please let me know if you need more info to clarify requirements.

Regards

Wayde

hi @Wayde Masters, 

It is worth noting that the Time Off activity will still span 00:00 - 00:00 for a full-day request, but it will have a start and end time associated with it.

Paul

Hi @Paul Wood,

Can't wait to see this one in action, will save us hours when entering Time-Off requests.

We were previously unable to use "Full-Day" as it marked all staff starting their shifts at Midnight GMT, regardless of their designated shift (AM (05:00 to 06:59 start), Day (07:00 - 10:59), Afternoon (11:00 - 17:59), Midnight (18:00 - 00:00), which meant the system would only pay day shift penalties.

Just confirming the rosters are created using the confines of the work plan?

Regards

Wayde

hi @Wayde Masters, 

It is worth noting that the Time Off activity will still span 00:00 - 00:00 for a full-day request, but it will have a start and end time associated with it.

Paul

Hi @Paul Wood,

Can't wait to see this one in action, will save us hours when entering Time-Off requests.

We were previously unable to use "Full-Day" as it marked all staff starting their shifts at Midnight GMT, regardless of their designated shift (AM (05:00 to 06:59 start), Day (07:00 - 10:59), Afternoon (11:00 - 17:59), Midnight (18:00 - 00:00), which meant the system would only pay day shift penalties.

Just confirming the rosters are created using the confines of the work plan?

Regards

Wayde

Why does the activity code still span the full day? It really should only reflect the start and end time and not show in the activity counts for the full 24 hours. 

hi @Wayde Masters, 

It is worth noting that the Time Off activity will still span 00:00 - 00:00 for a full-day request, but it will have a start and end time associated with it.

Paul

Hi @Paul Wood,

Can't wait to see this one in action, will save us hours when entering Time-Off requests.

We were previously unable to use "Full-Day" as it marked all staff starting their shifts at Midnight GMT, regardless of their designated shift (AM (05:00 to 06:59 start), Day (07:00 - 10:59), Afternoon (11:00 - 17:59), Midnight (18:00 - 00:00), which meant the system would only pay day shift penalties.

Just confirming the rosters are created using the confines of the work plan?

Regards

Wayde

The full-day activity is there to block out the day so that nothing else can be scheduled, for environments with extremely felxible work plans it could be possible to have Leave 9:00 - 17:00 and still be scheduled a shift before 9:00 or after 17:00. As you can imagine if the employee had booked a trip and was not available to work for the full 24 hour period this would create confusion and frustraion.

Blocking out the full day and providing the start/end times for the replaced or estimated shift provides the business with the reportability and the employee the reassurance that they have the full day booked off.

Paul

Why does the activity code still span the full day? It really should only reflect the start and end time and not show in the activity counts for the full 24 hours. 

hi @Wayde Masters, 

It is worth noting that the Time Off activity will still span 00:00 - 00:00 for a full-day request, but it will have a start and end time associated with it.

Paul

Hi @Paul Wood,

Can't wait to see this one in action, will save us hours when entering Time-Off requests.

We were previously unable to use "Full-Day" as it marked all staff starting their shifts at Midnight GMT, regardless of their designated shift (AM (05:00 to 06:59 start), Day (07:00 - 10:59), Afternoon (11:00 - 17:59), Midnight (18:00 - 00:00), which meant the system would only pay day shift penalties.

Just confirming the rosters are created using the confines of the work plan?

Regards

Wayde

Hi,

Tested and when the schedules are published, it still picks 00:00 - 0:00 hrs, and only the shift duration is getting updated as per paid hours which was the situation even earlier. So, what's the change from the old setup?

Regards,

Anupama

------------------------------
Anupama Kumar
Workforce Officer
------------------------------

The Time Off Limits are only calculated based on the start/end time, rather than the full 24 hours.

For historical reporting, the Time Off Request is updated with the start/end time of the shift that was replaced. This is a legal requirement in some regions to demonstrate that the shift being replaced was in line with the shifts for the week/planning period. 

When requesting a "full-day" it is assumed that the employee will not be available to work for the BU Calendar date of the request.

To honour this, the Time Off request is still added to the schedule as a full-day 00:00 - 00:00 (BU time) marker, with the start and end times added to the details for better limit calculations and insights for the Admin/Supervisor.

In very flexible scheduling environments or 24/7 operations, there are scenarios where marking "just the shift" as Time Off could result in a shift being created before/after the period marked as Time Off. This could result in confusion and frustration as the employee could be away and not able to attend any shift that day, not just the hours that they would have been scheduled for.

Hi,

Tested and when the schedules are published, it still picks 00:00 - 0:00 hrs, and only the shift duration is getting updated as per paid hours which was the situation even earlier. So, what's the change from the old setup?

Regards,

Anupama

------------------------------
Anupama Kumar
Workforce Officer
------------------------------

Hello Paul,

I am testing the new version of the Time Off limits available for specific time frames. I would like to provide my teams the ability to take time off only for those who work Monday to Friday from 09:00 to 18:00, and I have set the limits accordingly. However, I still observe that for the other time frames and days where there are no limits, the tool automatically fills in with zero, and in the employees' calendars, all days of the month are marked with "Short Wait List."

In my opinion, there is no differentiator between scenarios where there are no time-off limits posted, and the employee cannot submit any time-off requests, and those where limits exist, but the spots have been filled and the employee is indeed on a waiting list.

So, to be more specific, can I set it up so that my employees can only register for days off during the time frames I have specified, while being completely restricted from submitting requests for the other time frames?

Thank you,

Ema Ispas

Hi @Ispas Ana Emanuela, 

This sounds like a combination of zero limits and zero paid hours. If someone applies for leave on a "day off" or non-work day, the automation approves the request as a protective measure, since there are 0 paid hours affecting 0 limits; the request is non-impacting, and the employee's day off is "locked in" and protected from possible schedule changes. 

To add harder limits, you could use the Override Dates within the Time Off Plan. 

For the days that you want to limit you can either add a complete block or a manually reviewed marker so that the request can't be auto-approved.

To help further, please raise a care ticket, and one of our team will review your specific requirements and configuration to help you achieve your outcomes.

Hello Paul,

I am testing the new version of the Time Off limits available for specific time frames. I would like to provide my teams the ability to take time off only for those who work Monday to Friday from 09:00 to 18:00, and I have set the limits accordingly. However, I still observe that for the other time frames and days where there are no limits, the tool automatically fills in with zero, and in the employees' calendars, all days of the month are marked with "Short Wait List."

In my opinion, there is no differentiator between scenarios where there are no time-off limits posted, and the employee cannot submit any time-off requests, and those where limits exist, but the spots have been filled and the employee is indeed on a waiting list.

So, to be more specific, can I set it up so that my employees can only register for days off during the time frames I have specified, while being completely restricted from submitting requests for the other time frames?

Thank you,

Ema Ispas

Hi,

Thank you, Paul. I already opened a case last week (Case #0004113715), and it would be great if your team could get involved.

Regarding the proposed solution, when you have approximately 400 MUs and 2-4 Time-off Plans, and the limitation for weekends, for example, is applied individually to each weekend, the manual workload for the workforce team becomes considerable. Therefore, I expected the new feature to automate this filtering process, allowing requests to be submitted only in areas where the WFM analyst has already determined it is acceptable to post days off, without requiring further manual intervention or APIs.

Please consider developing this feature in the future so that there is a clear differentiation between situations where the available spots are filled (resulting in a zero) and situations where no requests can be submitted at all (resulting in a blank or zero).

Hi @Ispas Ana Emanuela, 

This sounds like a combination of zero limits and zero paid hours. If someone applies for leave on a "day off" or non-work day, the automation approves the request as a protective measure, since there are 0 paid hours affecting 0 limits; the request is non-impacting, and the employee's day off is "locked in" and protected from possible schedule changes. 

To add harder limits, you could use the Override Dates within the Time Off Plan. 

For the days that you want to limit you can either add a complete block or a manually reviewed marker so that the request can't be auto-approved.

To help further, please raise a care ticket, and one of our team will review your specific requirements and configuration to help you achieve your outcomes.

Hello Paul,

I am testing the new version of the Time Off limits available for specific time frames. I would like to provide my teams the ability to take time off only for those who work Monday to Friday from 09:00 to 18:00, and I have set the limits accordingly. However, I still observe that for the other time frames and days where there are no limits, the tool automatically fills in with zero, and in the employees' calendars, all days of the month are marked with "Short Wait List."

In my opinion, there is no differentiator between scenarios where there are no time-off limits posted, and the employee cannot submit any time-off requests, and those where limits exist, but the spots have been filled and the employee is indeed on a waiting list.

So, to be more specific, can I set it up so that my employees can only register for days off during the time frames I have specified, while being completely restricted from submitting requests for the other time frames?

Thank you,

Ema Ispas