Reporting Actuals, Planned, and Budgeted Hours

[#1]

It would be really useful to be able to report the Planned, Budgeted, And Actual hours booked per project by Job Role/Resource by Month (allocation date) . Currently i have to run a resource estimate report and/or a Finance report and compare. This is difficult because a) these reports do not have the same reporting attributes and b) it makes it difficult to track to plan.

[#2]

Agreed! Currently, I export the information out of the Resource Planner, but that does not give me all of the information I am looking for without quite a bit of manual effort. It would be great to be able to see how much we are budgeted to/actually spending on each project by month, all in one place!

[#3]

Totally agree - This report is absolutetly required for organizations that are maturing and trying to improve the accuracy of their planning and estimation processes! We currently have a resource allocation report with allocation date, project, role, and budgeted hours and an Hours report with actual hours, owner, owner role, owner home team, entry date and project (and some project custom fields) - we export both - merge the files in Tableau so that the dates, projects and roles are in sync - create our workbook so that it filterable by team, project (+metadata), and/or role - we add the viz to a WF dashboard and add the dash to folks' layout templates. - It would be sooo much easier if we could access the Hours object via the Project from the resource allocation report.

[#4]

Up voting this! We look at Budgeted, Planned and Actual data (from hours, revenue and/or expenses) as an invaluable way of tracking project & program metrics. We have spent a lot of time with WF team members and they have all confirmed that this makes sense and would be useful, but they are not available in the same report and it's not something that custom coding in reports can solve.

Having to do this in multiple reports (and, by extension, dashboard views) makes it very hard to compare apples to apples and, overall, undercuts the power of the data available and auto-magic of WF reporting. It is also manual, time consuming, and frustrating for the team knowing that the data points are in the system.

if there were a combined Project + Budgeted Hour report, that feels like it could solve.