The Resources panel lets you preview how much work has been assigned.

With the Resource panel enabled, the workload of each resource (assignee) will be counted in hours and color-coded depending on the resource capacity. 

The workload data is filter-sensitive, i.e. only the tasks in the current view are included in the workload calculation. You can use Quick filters or the Search Box to filter out tasks and simulate different scenarios.

As a rule, the effort is distributed evenly throughout the duration of a task but you can change how it is distributed in the Resources module. To learn more go to Workload contouring.

Workload vs Capacity Thresholds

The same set of rules applies both to the Resources panel in the Gantt module and to the Resources module itself.

Capacity = 0

Capacity is equal to 0 when a resource is unavailable on a given day (because of Workload Plans, Holiday Plans, or individual Absences).

Capacity can equal 0 for an individual or a Team.

In that situation, in the Resource grid (resources module) and the Resource Panel (Gantt module), the App uses the following algorithm (applies only for tasks that have automatic contouring mode):

  • the task effort is distributed between non-working days of the resource if all days from the task's period are non-working days (sum of capacity from that period is 0),
  • The task effort is not distributed between non-working days of the resource if only a part of the task's period consists of non-working days (sum of capacity from that period is >0).
    In that case, task effort is distributed only between working days.

As a result, if capacity (of a resource or a team) is 0 and there are some tasks with effort estimation in that period:

  • in the Resource grid, the Workload cell is red, and it displays Workload distributed according to the above algorithm.
  • In the Resource Panel, the Workload cell is visible, red, and displays Workload distributed according to the above algorithm.

In the example below, you can see that a resource is overloaded, but you can't see why. To see the workload details you need to go to the Resources module and check the workload of the assigned tasks. 

In the example below:

  • Resource (Christopher) is absent for a whole week (11th to 15th of October)
  • For a task that falls only on the days he is absent, capacity has been evenly distributed
  • For a task that falls partially on his workdays and partially on the absent days, the workload is distributed only on the days he works (has a capacity).

When total availability of a Resource exceeds 100%, a warning will be displayed.

Effort Modes

The general rule is that effort is evenly distributed over the duration period. You can switch between two effort modes:

Original Estimate

Use this mode during the planning phase as the Original estimate of time tracking is used and it is assumed that assignees did not start logging work at this point.

In this mode, the Original Estimate of Time tracking is evenly distributed over the duration period. For example:

Remaining Estimate

Use this mode to monitor the project's execution, as the Remaining estimate of time tracking is used in this case. The remaining effort is evenly distributed starting from the current date. 

In this mode, the Remaining duration is evenly distributed over the remaining duration of the task, starting from the current date and the Spent time is evenly distributed over the past duration. In the example below, there is no logged work hence no effort indication before the current date marker.

Aggregations

Display the workload as aggregated values in the following intervals:

  • Daily
  • Weekly (weeks count starting from Monday through Sunday)
  • Monthly

For example, Cameron planned workload is 163h in September and as it exceed the 160h capacity it is indicated with red color: