Skip to main content

FAQ, special cases and common pitfalls

Common pitfalls when interpreting or calculating utilization, in particular weekend work, public holidays or incomplete settings.

Why does utilization on weekends show more than 100%?​

By default, no target hours are stored for weekends. The system uses the weekly average of the working days (Mon–Fri) as the base, so weekend bookings count as additional output.

  • Example: 100% level = 40 h / week → average 8 h / day. 4 h Saturday → 4 h on top = 150% for that day.
  • Note: the display is technically correct: it shows extra output beyond regular working time, not overload.

Why do values in the year view differ from day / week / month?​

The day, week and month views only count a day if a booking exists. The year view, on the other hand, counts every day with stored working hours, even without a booking.

  • Example: Saturday with 8 h target time, no booking → year view shows 0% for that day, week view does not show it at all.
  • Solution: only store target hours for days that are actually worked. No target time on the weekend if it is off.

Why do public holidays distort utilization in the year view?​

Public holidays currently have working hours stored and are treated as working days by the system. Without a booking, the day shows 0% and artificially lowers weekly / yearly utilization.

  • Solution: record public holidays manually as an absence (type "public holiday"), ideally centrally at the start of the year as recurring entries. We are working on representing this correctly at system level.

Why are Saturday and Sunday hidden in the utilization chart?​

Purely for readability. The bookings are still included in the calculation; only the display omits these days.

Why is the level of employment not taken into account automatically?​

The stored level (e.g. 80%) currently does not feed into the utilization calculation; the calculation is based on full-time target hours.

  • Example: 80% level = 32 h / week. If the person is booked for 32 h, the system shows only 80% even though they are factually fully utilized.
  • Solution: model reduced levels via absences, e.g. a free Friday at 80% level as a weekly recurring entry.

Why does the percentage in the first row differ from the utilization chart?​

The values in the first row are rounded for display reasons (space). The calculation is correct in both cases, only the visual is rounded. A more precise display is in the works.

Why does utilization show 0% even though there are bookings?​

Without stored target hours, the calculation has no basis. The booking is saved but not set in relation to anything.

  • Solution: store working hours before planning starts.

Why do temporary employees have no effect on utilization?​

Temporary employees are deliberately not included in the capacity planning of the own workforce. We are working on making this setting configurable.

Why does utilization show more than 100% although no vacancies are booked?​

A booking can exceed the stored target time, producing utilization above 100%.

  • Example: target 8 h / day, booking of 10 h → 125%.
  • Use: overload can be shown deliberately (overtime, weekend work) but should remain visible.

Are departing employees still counted in utilization?​

Yes, the departure date is currently not taken into account. This can distort long-term planning. We are working on automatically excluding employees after their departure date.

All employees are booked, why isn't utilization at 100%?​

Most often the duration of the bookings or the disposition rate is wrong. For 100%, every person must be fully booked over the target time (e.g. 8 h / day at 100% level).

  • Example: only 4 of 8 hours booked, or disposition rate at 50% → utilization below 100%.
  • Solution: check the bookings individually; duration and disposition rate must match.
Last updated on