This article explains the process Kelloo uses to decide whether to show an alert against a project or resource.


Note: This article refers to projects. Depending on your configuration, you may see alternate terminology used in your environment. 




Resource view


In the example below Antonio and Ella both work 5 days per week. So the Project Manager role has a capacity of 10 days.


  • Antonio is allocated 8 days work so is over-allocated.
  • Ella is allocated 4 days work so is under-allocated.
  • But collectively the role of Project Manager is over-allocated (12 days in total allocated).


So both Antonio and the Project Manager role are flagged as over-allocated.




Calculations in detail:


If a resource's allocations for a week exceed the resource's capacity the week, the resource will be flagged as over allocated for the week.


If the role's total allocations for a week exceed the role's total capacity* for the week, the role will be flagged as over allocated for the week.


* Capacity of the role is the capacity of the resources in the role. Projects below the cut off line are excluded, any capacity adjustments are included.







Project view and sprint view


Continuing with the example above, in project view all of Antonio's work for w/c April 4th is flagged as over-allocated


This is because his total work for the week exceeds his capacity for the week. So one of the work items needs to be re-scheduled.





Calculations in detail:


If a resource's allocations for a week exceed the resource's capacity for the week, the resource will be flagged as over allocated for the week.


If the role's total allocations for a week exceed the role's capacity* for the week, the role will be flagged as over allocated for the week.


* Capacity of the role is the capacity of the resources in the role. Projects below the cut off line are excluded, any capacity adjustments are included.





Priority view


Priority view works a little differently. Because work is ranked by priority, it will show you which projects get impacted first by over allocation issues. 


So, if we look at this in priority view. We see that Antonio's work on the Kelloo Release project is flagged as over-allocated. 


Based on the priority of the work, Antonio has sufficient capacity to complete the higher priority CRM Project work. But runs out of capacity on the lower priority work.





Calculations in detail:


For each resource and role, Kelloo checks the over allocation status of each resource assignment.


To do this, it sums up all the higher priority work up to and including the resource assignment it is checking.


If the total work up to this resource assignment exceeds the capacity of the resource OR the capacity of the role* for the period the work is considered over allocated. 


* Capacity of the role is the capacity of the resources in the role. Projects below the cut off line are excluded, any capacity adjustments are included.