Schedule validations

Updated 2 months ago by Leigh Hutchens

The below article refers to when you're editing your schedule in our interface, not when doing so through our APIs.

When creating shifts in Schedule, Quinyx will validate the shift details against agreement settings and unit settings. These validations take place any time an existing is edited or a new one is added, be it in the Notifications panel or directly in Schedule. These validations also take place for absence shifts, including when creating leaves and when approving leave applications. If the user chooses to carry on with creating or editing a shift despite having received a warning message, Quinyx will log this circumvention.

The following validations exist in Schedule:

Validation message
Description

Break does not fulfil the minimum duration

Break is too short as per defined in the 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.

Employee not available

Employee not available as per defined in the agreement/agreement template.

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.

Employee missing skill(s) on task level

Employee is missing one or more skills that have been defined as required for a task in shift type settings.

Employee’s nominal hours for the schedule period have been exceeded

The employee's nominal hours for the schedule period have been exceeded. When determining whether or not the nominal hours have been exceeded, Quinyx considers:

  • Worked hours for those shifts that have a punch. If you’re using the “Generate salaries on tasks” setting then tasks’ “Count as worked hours” setting is considered.
  • Scheduled hours for shifts that have no punch. If you’re using the “Generate salaries on tasks” setting then tasks’ “Count as scheduled hours” setting is considered.
  • Quinyx currently doesn't consider punches without shifts/tasks.

All of the above holds true regardless of whether the shift in question is in the past or in the future, as long as it’s within the schedule period in question.

Employment ended

Employee is not set to employed in People < Employee details < Status.

Exceeding salary limit of employee's cost period

The shift you're adding exceeds the salary limit set up on the cost period. This feature is mainly used to support scheduling of minijobbers in Germany. The warning is overridable. The cost period is set up in the "Working hours and periods" section of the agreement templates.

Exceeding working time without break

Maximum working hours without break exceeded as per agreement/agreement template.

Late schedule change

You're editing the given employee's schedule within the notice period defined in Rules for hours < Schedule changes in agreement templates.

Max hours per day

Employee scheduled more hours per day than allowed as defined in agreement/agreement template.

Max scheduled hours per week exceeded

Employee scheduled more hours per week than allowed as defined in agreement/agreement template.

Minimum weekly rest requirement not met

Employee scheduled more hours per week than allowed as defined in agreement/agreement template.

Number of shift breaks exceeds the maximum allowed

The limit of number of breaks per shift as defined in Account settings < Group management < [name of unit] < Advanced unit settings < Breaks/shift is exceeded.

Overlapping shift

Two or more shifts are overlapping.

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.

Shift break time exceeds the maximum allowed

Total time of the break(s) exceed(s) the maximum allowed as per defined in agreement/agreement template.

Shift length is less than minimum shift length

The shift is shorter than allowed as per defined in agreement/agreement template

The employee has no valid agreement

There is no agreement for the employee on the selected date.

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.

Read more about base schedule validations here.

How Did We Do?