Optimization rules

The most common optimization rules that can be adjusted to fine-tune the scheduling outcome. They are selected when scheduling a period.

Allow overtime

The default is defined in the organization’s settings.

• Example: with working time 8–16, a task can start at 15:40 and end at 16:10 if overtime is allowed. If overtime is not allowed, the last task must always end before 16:00, so a task starting at 15:40 is no longer assigned.

overtime, working time end, last task

Shorten working hours

Allocator does not create breaks in the schedule by default, so by shortening the working time by the amount of breaks and workday disruptions (lunch break, phone calls, notes, etc.) you get a realistically scheduled day.

This rule is also the lever for dividing work more evenly — see the FAQ.

breaks, lunch, disruptions, realistic day

Re-optimize days

If this is not allowed, the confirmed tasks in the calendar and their order are not touched. When it is allowed, choose how far the optimizer may go:

• Don’t move tasks to others or remove — tasks stay with their familiar workers, but the order may change. Recommended for normal use.
• Tasks can be moved to others or removed — the algorithm may move tasks from one person to another or take them back to the task list. Use in connection with absences or bigger changes if there are problems fitting in all the tasks.

Removing never deletes anything. A removed task returns to the task list as reschedulable, keeping its original date, and can be scheduled again or dragged back manually.

When is “Tasks can be moved to others or removed” worth it? It pays off when days have been assembled by hand — tasks dragged from the task list or patched around absences — because the algorithm can then find a better arrangement across workers. If the days were already produced by a normal scheduling run, re-shuffling rarely improves them.

confirmed tasks, keep workers, clean slate, move tasks

overtime, breaks, rules, re-optimize, settings, fine-tune