Skip to main content

Utilisation Trend

Learn about the Utilisation Trend 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: Principals, resource managers, directors


Dashboard Explained

The Utilisation Trend page (Resources dashboard) uses one measure for all three visuals, Utilisation %, which shows the share of available staff time spent on client project work. How “available time” is defined depends on your organisation’s utilisation settings.
​

How to use it

Use Utilisation Trend in monthly leadership reviews to report on resourcing efficiency by office or another slice dimension. There's no fixed target line on this page — agree a target with leadership separately and compare it manually against the trend. Drill from Slice into individual Staff Name rows in the table to see who's driving a slice-level trend, or use Utilisation Heatmap for the colour-coded monthly view of the same drill-down.

Understanding your data

Visual

Measure

Broken down by

Bar chart

Utilisation %

Office (or the Slice by choice) for the selected period

Line chart

Utilisation %

Month (or the Date Hierarchy choice) and Office (or the Slice by choice)

Table

Utilisation %

Month, Office and Staff Name

How Utilisation % is calculated

The top of the calculation is always Timesheet Hours | Project. The bottom depends on two organisation settings, Utilisation Field and Utilisation Include Leave:

Visual

Organisation setting

Measure used

Calculation

All three visuals

Total Hours, leave included

Utilisation % | Total Hours

Project hours ÷ all recorded timesheet hours

All three visuals

Total Hours, leave not included

Utilisation % | Total Hours Ex Leave

Project hours ÷ (all recorded hours − timesheet leave hours)

All three visuals

Contracted Hours, leave included

Utilisation % | Contracted Hours

Project hours ÷ Contracted Hours

All three visuals

Contracted Hours, leave not included

Utilisation % | Contracted Hours | Ex Leave

Project hours ÷ (Contracted Hours − timesheet leave hours)

Leave is treated as included if the setting has no configured values.

Two organisations with identical timesheets can show different utilisation if their settings differ.

Building blocks

Visual

Component

How it’s calculated

All three visuals

Timesheet Hours | Project

Time recorded on client projects. Internal (including leave) and Non-billable Projects are left out; time on No Billing stages is included. This is the “utilised” time

All three visuals

Timesheet Hours | Total

All time recorded by staff, on client, Internal & Non-billable Projects alike

All three visuals

Timesheet Hours | Internal | Leave

Time on Internal Projects, on stages named exactly “Leave”. This is leave as booked on timesheets, not leave requests

All three visuals

Contracted Hours

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

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

Notes:

  • Leave is identified by stage name, not the leave-stage flag. Timesheet leave is counted only on an Internal Project stage named exactly “Leave”. A stage named “Annual Leave” (even if flagged as a leave stage in Synergy) is counted as other internal time. With an “Ex Leave” method, that leave is then not removed from the denominator, so utilisation looks lower. Rename the stage in Synergy to fix this.

  • Timesheet leave and leave requests are different. This page uses leave added on timesheets. Leave requests (SynergyHR) that are yet to be approved are held and counted separately and aren’t used here.

  • Casual staff are excluded by default (Is Casual | Alt = No). If they are included under a Contracted Hours method, their contracted hours equal their recorded hours.

  • The FY and FY Qtr slicers default to FY2027 on this page, but to FY2026 on Utilisation Detail. The same person can show a different Utilisation % on the two pages until the date slicers match.

What changes the numbers on this page

Control

Options (default)

Approval Status

Approved, Draft, Submitted (all three)

Is Active | Alt

Active

Is Casual | Alt

Yes, No (No)

Is Chargeable | Alt

Chargeable

Date Hierarchy

FY, FY Qtr, Month, Week Ending, Week Start (Month)

Slice by

Office, Team, Reports To, Primary Rate, Staff Name, Total (Office)

Slicers

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

Fixed filters

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

Did this answer your question?