Summary of Issue
All team members work a standard 7.5‑hour day, but only a portion of that day is allocated for project work (e.g., 25%, 50%, etc.). In Resource Management, however, the system currently interprets allocations as a percentage of the full 7.5 hours, instead of the project‑eligible portion of a person’s day.
This causes Resource Management to misrepresent a resource’s available project hours and incorrectly calculate actual hours when allocations are imported from project timelines.
Current Behavior
- All staff have a standard full-time schedule of 7.5 hours/day.
- A team member may only be available for projects at, for example, 10% utilization, meaning they should have 0.75 project hours/day.
- When timeline allocations (expressed as % of a standard workday) are imported, Resource Management calculates actual hours against the full 7.5 hours rather than the utilization-adjusted project hours.
- Differentiate between allocation % and Utilization %
- Currently Resource Management is treating this as one in the same.
Example
- Team member attends a 1-hour meeting → shown as 13% on a timeline (1 ÷ 7.5).
- The resource’s project availability is 10% of 7.5 = 0.75 project hours/day.
- Resource Management incorrectly applies 13% to 0.75 instead of recognizing the actual 1 hour worked.
- Result: RM shows 0.10 hours instead of 1.0 hour.
Impact
- Project actuals are under-reported.
- Capacity and utilization metrics become inaccurate.
- Tracking of true time spent on project work is distorted.
- PMs cannot reliably forecast or assess project workload across the portfolio.
Requested Enhancement
Goal:
Enable Resource Management to calculate available project hours based on utilization percentage, while still recognizing that allocation percentages from project timelines are based on a standard 7.5‑hour workday.
We request the following enhancements:
1. Availability Calculation Option Based on Project Utilization
Introduce a system setting that allows Resource Management to compute daily project availability such as:
Available Project Hours = Standard Workday Hours × Project Utilization %
Instead of treating the full 7.5 hours as available for project calculations.
2. Correct Interpretation of Imported Allocation Percentages
Allocation percentages imported from project timelines should be interpreted as:
% of a standard 7.5‑hour workday—not as a percentage of adjusted, utilization-based availability.
3. Updated Actual Hours Calculation Logic
When allocation % is imported, Resource Management should compute:
Actual Hours = Allocation % × Standard Workday Hours (7.5)
—not
Actual Hours = Allocation % × Utilization-adjusted available hours
This ensures 1 hour of real work is logged as 1 hour, regardless of utilization percentage.
4. Optional Override at Resource or Project Level
To support flexibility, allow organizations to specify whether a resources project availability should be based on:
- Standard full-time hours,
- Utilization-adjusted project hours, or
- A custom per-resource project capacity.
Expected Outcome
- Actual project hours logged match real time spent.
- Utilization reporting accurately reflects % of project capacity used.
- Timeline imports no longer produce distorted numbers.
- PMs get reliable forecasting, capacity, and workload reporting.
