Utilisation Rates: The Metric That Quietly Rewards the Wrong Behaviour

Utilisation — billable hours as a proportion of available hours — is the central operating metric in professional services, and it is one of the clearest examples of a measure that becomes a target and stops measuring.

Monitask discusses productivity and efficiency in this resource.

For official productivity concepts and data, consult the U.S. Bureau of Labor Statistics productivity program.

It is not useless. It is dangerous in the way that a useful measure applied to individuals usually is.

What it measures

Time that could be charged to a client, as a share of time available.

That is a capacity and revenue measure. It is not a productivity measure, and the two get conflated constantly.

Two people at 85% utilisation may have produced entirely different value. One resolved a problem in four hours that the other would have taken twelve on — and the second has the better utilisation number.

What it incentivises

Once utilisation determines standing, bonuses or promotion, entirely rational behaviour follows.

Slower work. The efficient consultant is punished. There is no version of this metric that does not have that property.

Reluctance to hand over. Passing work to someone better suited reduces your number.

Avoidance of non-billable work that matters. Mentoring, training, tooling, documentation, business development, process improvement — everything that raises the organisation's long-run capability is invisible to the metric and costly to the individual.

Optimistic coding. Time that could plausibly be charged, is.

Hoarding. Holding work you cannot get to rather than releasing it, because releasing it lowers your number.

Presence over output. The measure counts hours, so hours are produced.

None of this requires anyone to behave badly. It requires only that people respond to how they are measured.

Where it still belongs

Utilisation is genuinely useful at the level it was designed for.

Firm and team capacity. Whether the organisation has the right amount of people for the work is a question utilisation answers well.

Pricing. Understanding delivery cost requires knowing where time goes.

Staffing decisions. Which teams are over- and under-loaded.

Trend detection. A sustained fall or spike is a signal worth investigating.

The failure is not the metric. It is applying an aggregate capacity measure to individual performance.

What to measure alongside it

If you use utilisation, these prevent the worst of the distortion.

Realisation. Billed versus billable — how much of the recorded time was actually invoiced and collected. Optimistic time coding shows up here, and it is the single most useful companion measure.

Outcome quality. Client satisfaction, rework, escalations, repeat engagement. Where speed is genuinely valuable, this is where it appears.

Non-billable time by category. Not as a residual, but as a tracked and valued category. Mentoring, tooling and improvement are investments, and treating them as leakage guarantees they do not happen.

Effective rate. Revenue per hour actually worked. Rewards efficiency, which utilisation punishes.

Distribution. Whether the same people are always at 95% while others sit at 60%. Averages conceal this, and it is where burnout begins. See burnout as an operational problem.

Practical fixes

Set a target that leaves room. A 95% individual target is a target for burnout and for zero improvement work. Leaving genuine space for the non-billable work you claim to value is the difference between a stated priority and a real one.

Budget non-billable time explicitly. "Twenty percent of your time is for mentoring, tooling and development, and it is expected" is a different instruction from "we value these things."

Do not tie individual compensation to utilisation alone. If it must feature, pair it with realisation and quality.

Watch the ratio of hours to outcomes, not hours alone.

Treat a sustained rise with suspicion, not satisfaction. Utilisation climbing while revenue does not is a sign of optimistic coding or of work stretching to fill time. Both are worth knowing about.

The overtime connection

For non-exempt staff, utilisation pressure produces a specific and expensive failure.

An employee under pressure to hit a billable target, who has already recorded their scheduled hours, has an obvious way to reconcile the two: do the work without recording it. That is unpaid work, the employer is liable for it, and the metric is what caused it. See off-the-clock work.

Where utilisation targets exist for non-exempt staff, monitor recorded hours against system access and email timestamps. A gap is not a discipline problem; it is a design problem in the target.

The one-line version

Utilisation is a capacity measure. Used on teams it informs staffing and pricing. Used on individuals it rewards being slow, discourages handing work over, and makes every investment in the organisation's future personally expensive.

If it must be used individually, pair it with realisation and outcome quality — and leave genuine room in the target for the work that has no client code.