Validations in the Base Schedule
To be able to deal with shift warnings upfront when creating a shift, the Base Schedule features both preliminary and final validations. The shifts will be preliminarily validated against the employee's main agreement and against the current date. Once the shifts are rolled out in the Schedule, they are validated a second time but towards the actual date(s) they are rolled out for.
This system of dual validations is convenient in the case of, for instance, an employee having one agreement valid January 1 - July 1 and then another one July 2 - December 31. The two agreements may have different rules concerning maximum break time, max hours per day etc. In this scenario, if the Base Schedule is created and rolled out on January 1, the preliminary validations may result in a different amount of and/or other validation messages than the second validation.
Management of Validations
Validations appear during rollout. The flow is as follows:
- Build your Base schedule
- Click "Roll out" in the right upper corner of your base schedule and select the period across which you want to roll out the Base schedule.
- While waiting for the validation process to finish, you will be redirected to the Base schedule overview. In the "Status" column, a progress bar will indicate the completion of your base schedule's rollout. Once the validation is completed and in that same column, you will be notified about whether there are any shifts that have been prevented from being rolled out. To take a closer look at these shifts, click the base schedule in question. Your base schedule will now appear with validations in the side panel. The validations in question can also be found under the clock icon:
- The validations in the side panel are grouped by employee and shift. You can decide to take action on any of the below selections of validations:
- all validations in the base schedule
- all validations per employee
- all validations per individual shift.
In most cases you will have three options, and the options are indicated with icons:
The options are as follows, from left to right in the picture above:
- Accept the warning and roll out the shift(s).
- Don't roll out the shift(s).
- Roll out the shift(s), but unassign.
Once you've made your selection, you need to click "Roll out" at the bottom of the side panel to roll out the shift(s) in question.
The below list contains all validation messages presently available in Neo.
Shift break time exceeds the maximum allowed
Total time of the break(s) exceeds the maximum allowed as per defined in agreement/agreement template.
Employee does not have a role
You've rolled out the base schedule over a period which is prior to the employee's start date, agreement start date or role start date. Alternatively, you've rolled out the base schedule over a period which is after to the employee's end date, agreement end date or role end date. Note that Quinyx will require you to either delete or unassign the shift.
The employee has no valid agreement
There is no valid agreement for the employee on the selected date.
Employee not available
Employee not available as per defined in the agreement/agreement template.
Employee is not set to "employed" in "People" > "Employee details" > "Status" or on the staff card in Classic.
Two or more shifts are overlapping.
Employee missing skill(s)
Employee is missing one or more skills that have been defined as required for this shift type in shift type settings.
Max hours per day
Employee scheduled more hours per day than allowed as per defined in agreement/agreement template.
Break does not fulfil the minimum duration
Break is too short as per defined in the agreement/agreement template.
Shift length is less than minimum shift length
The shift is shorter than allowed as per defined in agreement/agreement template
Exceeding working time without break
Maximum working hours without break exceeded as per defined in agreement/agreement template.
Scheduled maximum consecutive days in a row
The employee has been scheduled more than the maximum consecutive days in a row as defined in the agreement/agreement template.
The shift has been scheduled on a bank holiday
The employee has been scheduled on a date that has been configured as a bank holiday in Classic, either in "Time" < "UT/Overtime/Bank Holidays" or in "Bank Holidays" on the agreement. Note: In order for this validation to occur, ensure "Schedule bank holidays" is unticked in "Rules for hours" on the agreement/agreement template.
Some shifts occasionally are not rolled out properly. We're continuously working on resolving this issue. When this happens, we recommend you accept the warning and roll out your base schedule again over the same period of time to see if the shift(s) still fail to rollout. If the shift(s) still fail after a few rollouts, please contact Support.