What happens when an overload is detected at the department level?
Unlike the risk and capacity analysis for individual employees, departments (i.e., generic resources) do not use dynamic leveling. Instead, fixed time windows – such as weekly or monthly – are used for risk calculation.
Dynamic leveling, as applied to individual resources, would be too complex and computationally intensive at the department level and often not meaningful for planning accuracy.
Since planning at the department level does not involve specific individuals (it is usually not yet known who will take on the task), a more general approach is sufficient. The accuracy of the risk calculation can be precisely controlled via customization – for example, by selecting the time window to be considered, such as a week or a month.
Example: If the evaluation is set to a monthly basis, Can Do checks each month for departmental overload. If an overload is detected, a warning indicator is activated – including information on how many hours are missing in the respective month (e.g., for the department "G_External," approximately 347 hours are missing in June).
This precise indication is possible because no leveling takes place – the planned workload remains unchanged within the selected time window.
For individual employees, the calculation of risks and overloads is significantly more granular. Here, leveling always takes place, meaning Can Do considers the actual dates of the assigned objects rather than fixed time windows. This matching process is highly complex and described in a separate article. As long as leveling does not result in an overload, the indicator remains green – regardless of whether multiple tasks are planned in parallel or overlapping.