Every consultancy reports utilisation. It is the first number in the board pack and the one the founders check on their phones. And in most firms it is a lagging indicator: it tells you, in the second week of the month, how billable the team was in the month that has just ended, when nothing can be done about it.
That is not a problem with the number. It is a problem with when you look at it.
The two utilisations
There are two numbers hiding under the one word. Actual utilisation is what the timesheets say: billable hours divided by the hours somebody could have worked, after leave. Planned utilisation is what the resource plan says: the billable hours booked for the weeks ahead divided by the same denominator.
Most firms report the first and do not compute the second, because the plan lives in a spreadsheet that does not know about leave, rates or targets, and nobody is going to divide a spreadsheet by hand every Monday.
But planned utilisation is the one you can act on. If the plan for three weeks' time shows the engineering team at fifty-five per cent, that is a sales conversation to have now, or an internal project to start now, or a hire to delay. By the time actual utilisation reports fifty-five per cent, the weeks are gone.
What it takes to plan it
Planned utilisation needs three things to be true at once.
The plan has to be against real budgets. A block on a planner that says "Client X" is not enough; it has to say which budget, at what rate, so the hours turn into money and the budget knows it has been committed.
Leave has to be in the same place. A person on holiday in week six is not available in week six, and a plan that does not know that reports a utilisation that cannot be reached.
And the plan has to know what actually happened. When the timesheet for last week arrives, the planned days for last week should give way to the logged ones, so the plan is always the future and the timesheet is always the past. Otherwise the same day is counted twice, once as planned and once as done, and the number is fiction.
What changes when you have it
The Monday meeting changes shape. Instead of "what was utilisation last month?", the question is "where is the plan thin?" and the answer is a list of people and weeks. Sales knows which skills are free and when, so it sells into the gap rather than into the pile-up. Hiring is timed against the plan rather than against a feeling.
And the month-end number stops being a surprise, because it is what the plan said it would be, adjusted for what actually happened, and you have been watching it move for weeks.
The honest caveat
A plan is only as good as the discipline of keeping it. A planner that is updated quarterly is a report with extra steps. The firms that get value from planned utilisation are the ones where booking a person onto a budget is how work gets assigned, not a record of a decision made elsewhere. That is a habit, and the tool has to make the habit cheap: a block should take seconds to place, and the numbers should move as it lands.
That is the case for putting the plan, the leave, the budgets and the timesheets in one system. Not because one system is tidier, but because utilisation only becomes a plan when they can see each other.
Bitmap computes planned and actual utilisation from the same budgets, plan, leave and timesheets.