Skip to main content
Auto-Fill Constraints

Detailed explanation of the constraints used by the auto-scheduler

Olaf Jacobson avatar
Written by Olaf Jacobson
Updated over 11 months ago

Minimum seat requirement

A schedule will only be generated if it meets the minimum seat requirement for each event. You can use this constraint if you want to be sure there are zero gaps left in your schedule. This means that no schedule will be created if it is not possible to fill all required seats.

Maximum working hours

Team members will not be scheduled for more hours than stated in their contract. This means that if you set the weekly contract hours to 32, this employee will not be scheduled for more than 32 hours per week.

Be aware that it can be that they will be scheduled for fewer hours, depending on the requirements of your schedule.

Use the checkboxes to select which contract hours should be taken into consideration by the solver. You can choose:

  • Daily

  • Weekly

  • Monthly

Minimum working hours

The minimum working hours constraint ensures that team members are scheduled for at least as many hours as stated in their contract. For instance, if a team member's contract specifies a minimum of 20 hours per week, the auto-scheduler will aim to schedule them for at least 20 hours.

You can specify whether this rule applies on a weekly or monthly basis using the checkboxes. Remember, depending on the requirements of your schedule, it may not always be possible to meet the minimum hours.

Working days

The contract days constraint ensures that team members are only scheduled for days that are considered contract days. This means that if a team member's contract specifies that they work from Monday to Friday, the auto-scheduler will not schedule them for shifts on Saturday or Sunday.

Role match

The role match constraint ensures that team members are only scheduled for shifts that match their assigned role. For instance, if a team member is assigned the role of a cashier, the auto-scheduler will not schedule them for shifts that require a cook.

If no role is required, it means all team members can be considered to fill the spot.

Overlapping leave

The overlapping leave constraint ensures that team members are not scheduled during their approved leave. If a team member has been granted leave for certain days, the auto-scheduler will respect this and not schedule them for shifts during this time.

Custom constraints

If you don't see the type of constraint that you need amongst these, we can create it for you in our Enterprise plan.

Did this answer your question?