Most professional services firms know their utilisation rate in arrears. The number exists on Monday or at month-end after someone has exported hours, cross-checked them against capacity, and built a view in a spreadsheet or a PSA report. By the time it lands in front of a managing partner, the week it describes is already gone.
The value of a live utilisation dashboard is not the number itself. It is the two-week window it creates between seeing a problem and having to explain it in a board meeting.
What you are actually connecting
A professional services utilisation board needs three source types, and most firms already have all three.
Time-tracking. Harvest, Toggl Track, Replicon, Float, or entries in a PSA like Kantata or Workday. This is where hours live. The question is whether the hours are captured at the project and person level, and whether they are entered within the same week rather than backfilled at month-end.
Capacity. Headcount, planned leave, and bench allocation. Usually lives in a calendar tool or a staffing module. If it lives in a spreadsheet, that is the first thing to migrate: capacity is the denominator in every utilisation calculation and it needs to be live.
Pipeline. Upcoming engagements, their start dates, and their estimated hours. Usually in a CRM or a project intake tool. This is what feeds the forward-looking bench risk view.
Once these three sources share a person-week grain, the board can answer the questions partners actually care about.
The three tiles that matter
Live utilisation by person and team
Billable hours logged this week, divided by available hours this week, per person, per team, and per practice. The board shows the number mid-week, not at close-of-Friday.
A partner who sees on Wednesday that one team is tracking at forty percent can reallocate before the week is lost. A partner who sees it on Monday already lost the week.
Target versus actual sits side by side. If a team has a seventy-five percent target and is tracking at sixty, the gap is visible to the person who can close it, not just to the person running the end-of-week report.
Realisation rate by engagement
Utilisation tells you hours were worked. Realisation tells you how many of those hours were billed. The gap is write-offs, scope creep absorbed without a change order, and work completed but not yet invoiced.
Tracking realisation at the engagement level mid-project is the thing that prevents the margin conversation happening at closeout. If an engagement is at sixty percent realisation in week three, the PM can have the scope conversation in week four. That conversation is easier before the work is done.
Bench risk over the next four weeks
Forward utilisation: pipeline engagements with a confirmed start date against current bench and people whose current project ends within the window. The board shows who is at risk of going unbillable before it happens.
Most firms staff on hope: wait until a person rolls off, then find them something. Bench risk visibility moves staffing from reactive to two weeks earlier. That is usually enough to avoid the gap.
The reconciliation that always trips people up
The hardest part of building this board is not the connectors. It is agreeing what counts as billable.
Most firms have internal categories that are billed at different rates: client work at full rate, internal projects at zero, business development at a blended rate, training at partial. Before the dashboard goes live, we map every time entry category to one of four buckets: billable, non-billable, investment time, or admin. The board uses those buckets consistently across every calculation.
Without this agreement, two partners looking at the same utilisation number will come to different conclusions because they count different things. The dashboard surfaces that disagreement on day one rather than six months into a data governance project.
A secondary issue: time entries submitted late. If hours for Tuesday get entered on Friday, live utilisation on Wednesday looks low. We add a submission lag indicator to the board: each person's last entry timestamp. Anyone more than twenty-four hours behind gets a flag. This is not about discipline. It is about trusting the number.
What changes for the practice
The Monday partner review goes from "here is last week" to "here is this week so far." Partners spend the meeting on action, not on reading a status deck that describes a past they cannot change.
The end-of-month billing cycle shortens because write-offs are caught mid-engagement rather than post-closeout. One firm we worked with reduced average write-offs by four points in the first quarter, not because the team worked differently, but because the scope conversations happened earlier.
And the bench gaps that used to surface in emergency staffing emails get caught in the regular weekly review. Not every time, but often enough to pay for the build several times over.
What it does not fix
A utilisation board does not make people enter their hours on time. It makes late entry visible, which creates social pressure, but if the culture does not support prompt entry the board will lag. This is a people problem, not a data problem.
It also does not solve pricing. Knowing realisation is low tells you that write-offs exist. Understanding why they exist, and whether the fix is better scoping, better pricing, or better project management, requires the conversations the board enables, not the board itself.
