When using Resource Reporting > Allocation Details, many times you may notice the Allocated Hours return as more than the Capacity and still there are Available hours (also known as overallocation). From the report at first glance, this seems to be an error in logic, yet the report is correct!

* Capacity - (Confirmed + Allocated) = Availability 

SCENARIO: Expectation: 171 - (136 + 43) = -8 , but actual availability is showing 11. How is this possible?

November (Monthly): 

November (Weekly):

The report returned results that do not consider over-allocation on individual days. Days that are over-allocated in hours do not rollover into the next day.

This means you could have the first four days in the week allocated for 9 hours a day, and the last day for only four. The result in this simple example would be that you were allocated for 40 and still had four hours available (considering you had an eight hour work day).

In the Allocation workbench resource finder an overallocation warning for Adam is given, but still shows available hours:

To test this, engineers will click on the Allocated number result in the Resource Report, which displays the respective Resource Allocation Daily records. These records are the most granular records that tell us where hours are allocated per day (for a particular user and task). Below is an example from Nov 16th - Nov 22nd: 

Below is a graphical representation of the month, broken down by week:

In the above, you can see in the New York release, if an overallocation occurs, the availability will be 0 for the day and additional allocated hours won't carry over for the total availability. 

In the Orlando release, you would see a negative amount thus updating the availability as well. 

This is standard behavior in the New York release of our product. 

Orlando release and later, shows negative availability and related details for overallocation.