
At Orangescrum, we actively listen to user feedback and continuously refine our features to make project management more efficient. This latest update brings key improvements to Team Utilization Reports and Profitability Reports, ensuring better accuracy and usability.
This latest release focuses on accuracy, clarity, and decision confidence, with major enhancements to Team Utilization Reports and Profitability Reports—two of the most business-critical views for project managers, PMOs, and leadership teams.

Our esteemed customers wanted a Team Utilization Report that compares Spent Hours vs. Company-Defined Working Hours instead of just comparing Spent Hours vs. Estimated Project Hours (which was already available).
We introduced this capability, enabling project managers and admins to analyze discrepancies between actual logged hours and company-defined working hours (e.g., 45 hours/week). However, an inconsistency emerged when viewing the report across multiple projects.
Originally, company-defined working hours (e.g., 45 hours/week) were displayed separately for each project, which incorrectly implied that employees were expected to work 45 hours per week per project rather than across all projects collectively. This misrepresentation led to inaccurate utilization calculations.
Clear Pain Statement
Many customers told us that comparing Spent Hours vs. Estimated Project Hours alone wasn’t enough. They needed visibility into how actual logged time compares against company-defined working hours (for example, 45 hours per week).
We introduced this comparison—but quickly discovered a reporting issue when multiple projects were involved.
What Was Going Wrong?
Previously:

Now, the company-defined working hours are displayed only when viewing the “All Projects” report instead of being repeated under each project.
Accurate Utilization Insights – Users can now properly track team utilization (based on actual logged hours across all projects, compared to the company-defined working hours.)
More Transparency – Project managers now get a clear, consolidated view of team workloads without any misrepresentation of working hours per project.

The Profitability Report, designed to measure project profitability based on Project Estimation Hours versus Task Estimation Hours, contained miscalculations. Project Estimation Hours were incorrectly computed, leading to unreliable profitability assessments.
Additionally, inaccuracies in Profit Margin % and Spent Hours calculations further impacted profitability insights.
Moreover, when exporting the report, only the headers were visible, while the actual data and metrics were missing.
What we achieved
Why This Was Critical
Inaccurate profitability data can lead to:
These improvements are especially valuable for:

We’re committed to making Orangescrum smarter, more accurate, and more powerful for all our users. Your feedback drives our improvements—so keep them coming!