Skip to main content

Utilisation Detail

Learn about the Utilisation Detail Dashboard

Edition: Business + Insights Pro Add-on, Enterprise + Insights Pro Add-on
​User-level: Permissions are set at an Organisation level by System Administrators
​Who this is for: Resource managers, studio managers, project managers


Dashboard Explained

The Utilisation Detail page (Resources dashboard) is a single table with one row per staff member. It shows Utilisation % next to the hours behind it: Contracted Hours, total Timesheet Hours, and the split of those hours into project, internal and leave time. When a summary dashboard raises a question about a specific person's utilisation, this is where the answer is found.
​
​

How to use it

Use Utilisation Detail when investigating a specific staff member's utilisation pattern flagged in the Heatmap or Trend view. Compare Total Project Hours against Total Hours to see how much of their recorded time was billable-project work at all, then check the Chargeable vs Non-Chargeable split within that. High Internal Hours may indicate a workload or timesheet-discipline issue worth a conversation. This page doesn't break down hours by individual project — for that level of detail, use Timesheet Detail.
​

Understanding your data

Column

What it shows

Calculation

Utilisation %

Share of available time spent on client project work

Timesheet Hours | Project divided by the denominator set in your organisation’s settings: total recorded hours or Contracted Hours, with or without leave removed (same four methods as the Utilisation Trend page)

Contracted Hours

Hours the staff member was expected to work

Non-casual chargeable staff: Hours Per Week ÷ 5 × Monday–Friday work days between employment and termination dates (public holidays not removed). Casual chargeable staff: their actual recorded hours. Non-chargeable staff: none

Total Hours (Timesheet hours)

All time recorded

Every timesheet entry: client projects, internal projects and leave

Total Project Hours (Timesheet Hours | Project)

Time on client projects

Time on projects not flagged as internal projects. Includes No Billing stages. This is the “utilised” time

Chargeable (Timesheet Hours | Project | Chargeable)

Client project time on billable stages

Client project time on stages whose fee type is not No Billing

Non-Chargeable (Timesheet Hours | Project | Non-Chargeable)

Client project time on non-billable stages

Client project time on stages with the No Billing fee type

Internal Hours (Timesheet Hours | Internal | Ex Leave )

Internal time other than leave

Time on internal projects, excluding stages named exactly “Leave”

Internal Leave (Timesheet Hours | Internal | Leave)

Leave booked on timesheets

Time on internal projects, on stages named exactly “Leave” (not leave requests)

All columns count only staff records, exclude data-import transactions, and filter by the staff member’s own office when the Office slicer is used.

What changes the numbers on this page

Control

Options (default selections)

Approval Status buttons

Approved, Draft, Submitted (all three selected)

Is Active

Active

Is Casual

No

Is Chargeable

Chargeable

Slicers

Date, Staff Name, Week Start, Week End, Primary Rate Name, Office (active only), FY (FY2026), FY Qtr (FY2026), Month, Reports To, Team

Fixed filters

Staff records only (Is Staff); Month Category is Current, History or Future

Unlike Utilisation Trend, this page has no Date Hierarchy or Slice by buttons, and its FY and FY Qtr slicers default to FY2026 rather than FY2027. The same staff member can therefore show a different Utilisation % on the two pages until the date slicers match.

Notes

  • Chargeable versus non-chargeable depends on the stage fee type set in Synergy. “Leave” depends on the stage name being exactly “Leave”. Internal time is time against the Internal Project. Corrections to any of these are made in Synergy.

  • Draft and submitted time are included by default, so figures can change as timesheets are approved.

  • Data refreshes every 60 minutes, it's not live.

Did this answer your question?