Skip to main content

Remaining Subtask Budgeted Hours

Updated yesterday



Purpose

To track the total number of budgeted hours remaining on open or in-progress subtasks, helping project managers monitor effort left to complete work and avoid time overruns.


Visualization Type

KPI

Liveboard

Capacity Dashboard

Tab

Subtasks

Function

Capacity



Filters

Includes
Tasks in Progress
Subtasks Budgeted Hours > 0

Excludes
Completed Subtasks


Need-to-know Glossary of Terms

  • Task Status - Current state of a task within a workflow (e.g. not started, in progress, with client, completed, etc.).

  • Subtask Status - Current state of a subtask within a workflow (e.g. not started, in progress, with client, completed, etc.).

  • Subtask Budgeted Hours - Total hours budgeted to a subtask.

  • Remaining Budgeted Hours formula - Calculated by subtracting the sum of the task logged hours from the sum of the task budgeted hours.
    sum ( Task Budgeted Hours ) - sum ( Task Logged Hours )

  • Remaining Subtask Budgeted Hours formula - - Calculated by subtracting the sum of the subtask logged hours from the sum of the subtask budgeted hours.
    sum ( Subtask Budgeted Hours ) - sum ( Subtask Logged Hours )


Report Structure Overview

  • Task Status filter - Filtered to exclude completed tasks

  • Subtask Budgeted Hours filter - Filtered to include subtasks with more than O budgeted hours

  • Subtask Status filter - Filtered to exclude completed subtasks

  • KPI Value - Remaining Subtask Budgeted Hours


Suggested Modifications

Want to add this KPI to your Insights homepage?
1. Hover over the KPI and select the ellipses button.
2. Select the option, Add to Watchlist.


Primary Use Case Scenario

A Project Manager reviews this report weekly to gauge how many hours are still budgeted for subtasks that haven’t been completed.


Actionable Insights

Clear visibility into the total effort left to deliver on active assignments and can serve as an early warning when remaining hours are too low relative to remaining work.

Did this answer your question?