The total time tracked (in hours) recorded on action cards.

The total cost of the tracked time, calculated by multiplying each user’s tracked hours by their individual cost rate.

The total billable amount for the tracked time, calculated by multiplying each user’s tracked hours by their individual bill rate.

The total amount of time (in hours) estimated on action cards.

The total cost of the estimated time, calculated by multiplying each user’s estimated hours by their individual cost rate.

The total billable amount of the estimated time, calculated by multiplying each user’s estimated hours by their individual bill rate.

The total hours from submitted, unsubmitted, pending, approved, changes requested and unapproved timesheets (filterable by each status).

The total cost of timesheet hours, calculated by multiplying each user’s hours by their cost rate.

The total billable amount of timesheet hours, calculated by multiplying each user’s hours by their bill rate.

The total cost of all billable timesheet hours, calculated by multiplying each user’s billable hours by their cost rate.

The total cost of all non-billable timesheet hours, calculated by multiplying each user’s non-billable hours by their cost rate.

Shows each user's timesheet status for the period: Approved, Pending approval, Changes requested, Unapproved or Unsubmitted. To add it, open Values, search for Timesheet status and select it.

When a pivot table reports on Time, uses User as the first row group and includes Timesheet status as a value, it lists every user in the workspace, not only people who logged time.

By default, the list includes external users (also invited users who have not joined yet) and removed users. To show fewer users:

Click a Timesheet hours or Timesheet status cell to open that person's timesheet for the week in a window, without leaving the dashboard.

This works when the pivot table:

In the window:

Grand total cells, and dashboards opened from a share link or export, don't open the window. In other layouts, a Timesheet status cell still opens Timesheets reporting if you have access to it.

The submitted timesheet hours as a leave type.

The total amount of resourced (scheduled) hours from the Resourcing app.

The total cost of the resourced hours, calculated by multiplying each user’s resourced hours by their cost rate.

The total billable amount of the resourced hours, calculated by multiplying each user’s resourced hours by their bill rate.

The resourced hours as time off.

Utilization is a metric that measures how much of a user’s available time is allocated to project work, compared to their total available hours.

Utilization (%) = ( (Estimated Time + Resourcing Estimates) − (Time Off + Holidays)​ ) / Available Hours × 100

If future repeats seem to be missing from a utilization forecast, check the workspace setting Include recurring action time in utilization dashboards under Settings → Apps → Time tracking. Workspace admins can enable it and set the Recurring action time look-ahead (months).

The setting allows normally hidden future recurring action instances into dashboard reporting. Future repeats with due dates are limited by the look-ahead period, measured from the current date. The default is 12 months, with a range of 1–120 months. Recurring subactions without their own due date are not excluded solely for lacking a date by this look-ahead rule.

The dashboard’s date range, project selection, and other filters still apply. On dashboards covering multiple workspaces, the owning workspace’s recurring-time settings govern the workspaces included in that dashboard.

This setting changes which action instances can contribute to reporting. It does not turn estimated time into tracked hours or submitted timesheets. See workspace recurring-action time settings for setup.

Total project budget assigned to the project through the Project Navigator.

Other costs added to the project through the Project Navigator.

Each “Budget Remaining” metric follows the same core formula:

Budget Remaining = Project Budget - (Other Costs + Total Calculated Value)

Project Budget - (Other Costs + Total Time Tracking Cost)

Project Budget - (Other Costs + Total Time Tracking Billed)

Project Budget - (Other Costs + Total Timesheets Cost)

Project Budget - (Other Costs + Total Timesheets Billed)

Project Budget - (Other Costs + Total Estimated Cost)

Project Budget - (Other Costs + Total Estimated Billed)

Project Budget - (Other Costs + Total Resource Estimates Cost)

Project Budget - (Other Costs + Total Resource Estimates Billed)

Timesheet Cost Budget Remaining / Project Budget x 100

Timesheet Billed Budget Remaining / Project Budget x 100

Resource Est. Cost Budget Remaining / Project Budget x 100

Resource Est. Billed Budget Remaining / Project Budget x 100

Estimated Cost Budget Remaining / Project Budget x 100

Estimated Billed Budget Remaining / Project Budget x 100

Time Tracking Cost Budget Remaining / Project Budget x 100

Time Tracking Billed Budget Remaining / Project Budget x 100

Estimated Billed Amount - (Estimated Cost Amount + Other Costs)

(Forecasted Margin / Estimated Billed Amount) x 100

List of stages available on this action card

List of rounds available on this action card

The total count of stages available on this action card

The user who is set as an approver

The active approval stage on the action card. Fully approved cards show Approved.

The current approval round on the action card. Fully approved cards show Approved.

Approvers still waiting to respond in the active stage. Unlike Approver, this field

focuses on who currently needs to respond.

Approvers assigned to the next stage in the current approval round.

The number of calendar-day boundaries since the active stage started, calculated in UTC. Weekends and holidays are included. The value is blank when the active stage has no start date.

Approval status for the active stage when Review Stage is not a row group. Fully approved cards show Approved.

The active stage’s approval due date when Review Stage is not a row group.

The active stage’s start date when Review Stage is not a row group.

The historical approval date for a review stage. This field is available on Review Stage rows, rather than projected onto Action or Project rows.

Proofing files associated with the action. Click a proofing file value to open it. Use the Proofing file filter to include actions with or without proofing files.

Example: Use Action rows with Current approval stage, Current approver, and Days in stage to identify approvals waiting for attention.

Hive calculates Formula and Table lookup custom field values each time it shows them. Hive does not keep these values. For this reason, a pivot cannot add, average or count them.

The Values list of these widgets does not show Formula or Table lookup fields:

A saved Pivot table or Numbers widget that uses a Formula or Table lookup field as a value shows N/A for that value. N/A tells you that Hive cannot calculate the value.

What to do:

To show Formula values on a dashboard, use a Heatmap widget. Heatmaps can use Formula fields as a value. See Use Formula Values in Dashboard Heatmaps.

On November 4, 2026, Hive changed how some Pivot table and Numbers widgets count actions, time and holidays. Saved widgets can show different numbers. You do not need to change your widgets. Not every widget changes.

A widget can change when it uses:

Projects reports with a Role name row group do not change.

With the new count, an action counts one time for each role of its assignees. Before, it counted one time for each assignee with that role.

Example: An action has two assignees. Both have the role Designer. The Designer row now counts 1 action. Before November 4, 2026, it counted 2.

With the new count, Hive counts each time entry under the role that the entry was logged with. If the entry has no logged role, Hive uses the person's current role.

Example: Ana logged hours as Designer. Then her role changed to Art Director. Her older hours stay in the Designer row.

With the new count, a holiday counts for a member when the member works for your company on the date of the holiday. Hive uses the first and last day of work in the member's settings.

Example: Your date range is October 1–31. Sam starts on October 15. A holiday on October 20 counts for Sam. A holiday on October 10 does not count.

Before November 4, 2026, Hive did not count holidays for a member who started or left during the date range.

Filters can be found on the right Chart Content menu of your widget. The Pivot Table widget allows the ability to filter by: