Atlas
  • All-in-one
  • Solutions
  • Compare
  • Pricing
PricingGet started
  1. Atlas
  2. Guides
  3. Utilisation and Realisation: The Two Numbers That Run a Firm
August 15, 2026·10 min read·Professional Services, Economics, Utilisation

Utilisation and Realisation: The Two Numbers That Run a Firm

A firm at ninety per cent utilisation and seventy per cent realisation is working flat out to lose money, and its dashboard is green.

Utilisation is the proportion of a person's available time that was spent on client work. Realisation is the proportion of that client work which was actually billed and collected. They are usually reported separately, often by different people, and the relationship between them is where the profitability of a professional services firm actually lives.

The reason they must be read together is that each can be improved by damaging the other, and both improvements look like progress. Push utilisation and you staff people onto work they are not suited to, which produces rework that is written off, and realisation falls. Push realisation by billing only clean, well-scoped work and utilisation falls as people sit between engagements. A firm managing one number in isolation is playing a game against itself.

Defining utilisation so the number means something

Utilisation is arithmetically simple and definitionally contentious. The numerator is time on client work. The denominator is where firms differ, and the choice changes the number by ten points or more.

  • Against total hours: client hours divided by all hours worked. Rewards overwork, because a person billing forty hours in a sixty-hour week scores lower than one billing forty in forty-five. Avoid.
  • Against contracted hours: client hours divided by the standard working week. The most common and usually the right choice, because it measures against what the firm actually bought.
  • Against available hours: contracted hours less holiday, training and approved internal commitments. The most honest for judging an individual, and the hardest to compute consistently.
  • The rule that matters more than the choice: pick one, define it in writing, and never change it mid-year, because a comparison across a definition change is meaningless and will be made anyway.

What realisation actually captures

Realisation is the value billed divided by the value of the time recorded at standard rates. If a consultant records forty hours at a standard rate of two hundred and the firm bills six thousand, realisation is seventy five per cent. The missing quarter went somewhere, and where it went is the most useful management information a firm has.

It leaves in four ways, and they have very different causes. A fixed fee that under-ran the effort is a scoping or pricing failure. A discount granted at sale is a commercial decision taken by somebody who probably did not see this number. Rework is a quality failure. A write-off at billing is a partner deciding the client will not wear the full amount, which is usually one of the other three arriving late.

A firm that reports realisation as a single percentage has a symptom. A firm that reports it split by those four causes has a diagnosis, and the four have different owners: pricing, sales, delivery quality, and the billing partner.

The combination that tells you what to do

Read together, the two numbers point at a specific action, which is why neither is useful alone.

  • High utilisation, high realisation: the healthy state. The risk is burnout and the correct response is capacity, not congratulation.
  • High utilisation, low realisation: the dangerous state, and the most common in growing firms. People are busy on work that is not converting to fee. Look at scoping and at fixed-price estimation before you look at the people.
  • Low utilisation, high realisation: usually a pipeline problem rather than a delivery one. The work being done is good and there is not enough of it.
  • Low utilisation, low realisation: a structural problem. Something is wrong with what the firm sells or who it sells to, and no amount of scheduling will fix it.

Where the numbers go wrong

The most common corruption is time recorded to fit the target rather than to describe the week. Once people understand that utilisation is measured and consequential, the number becomes a report on behaviour rather than on work, and the firm loses the only data it had. The defence is not surveillance, it is making the target a team-level expectation rather than an individual scorecard, and treating an unusual figure as a question rather than a verdict.

The second is counting business development as client work because it feels productive. It is investment, it should be visible, and folding it into utilisation makes the firm unable to see what it spends on winning work.

The third is measuring realisation on billing rather than collection. Work billed and never paid is realised on paper and worth nothing. On engagements where collection is genuinely at risk, the number to watch runs through to cash.

Reading them at engagement level, not just firm level

Firm-level averages hide the engagements that are destroying value, because a portfolio of eight healthy engagements and two catastrophic ones averages to fine. The management action is always at engagement level, so the reporting should be too.

The practical version is a monthly view of every live engagement with recorded effort against budget, value billed against value earned, and the drift on both. Two numbers per engagement, read every month, catch the problem while the engagement can still be repriced. The same information at year end is a post mortem.

Keep reading

  • Rate Cards and How Engagement Margin Actually Moves
  • Engagement Management Software: What It Actually Has To Do
  • Professional Services Automation: What To Look For, and What To Ignore
  • Billing Milestones, Work in Progress, and Where Margin Quietly Leaves
  • Earned Value for Professional Services, Without the Ceremony
  • PSA, Project Management and Client Portal: What the Categories Actually Mean
  • Free PDF tools
  • The all-in-one work OS

FAQ

Questions, answered.

What is a good utilisation target?
It depends on the role and any single benchmark quoted without that context is misleading. Delivery staff carry the highest targets, managers carry lower ones because they are selling and supervising, and partners lower still. What matters more than the number is that it is set per role, that internal time is visible rather than hidden, and that it is not raised in response to a bad quarter, which is how firms burn people out.
Should utilisation targets apply to individuals?
Set them at team level and use individual figures as a diagnostic. Individual targets tied to compensation reliably produce time sheets that meet the target, and once that happens the firm has lost its measurement instrument in exchange for a number that no longer means anything.
How does realisation differ from margin?
Realisation compares what you billed against what the time was worth at standard rates. Margin compares what you billed against what the time actually cost. A firm can have strong realisation and poor margin if it is staffing work with people who are too expensive for it, which is why senior-heavy delivery on a well-priced engagement can still lose money.
How often should these be reviewed?
Monthly at engagement level, because that is the cadence at which something can still be done. Weekly is noise on most engagement lengths and quarterly is a retrospective. The exception is a fixed-price engagement burning faster than planned, where weekly is justified until the burn is understood.

Ready when you are

One workspace, not ten.

Atlas replaces the stack with one platform for tasks, projects, CRM, contracts, e-signature, PDF tools, and analytics. Start free.

Get started freeSee pricing
AtlasWork, planned itself.

The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

All systems operational
  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

Product

  • Overview
  • PDF tools
  • Diagram tools
  • People & HR
  • Integrations
  • Marketplace
  • Pricing

Resources

  • Guides
  • Glossary
  • Compare
  • Docs
  • API reference
  • Support
  • Changelog
  • Status

Company

  • About
  • Careers
  • Press
  • Contact

Legal & trust

  • Trust center
  • Security
  • Privacy
  • Terms
  • DPA
  • GDPR
  • SLA
  • Refunds
  • Google API data
Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
PrivacyTermsSecurityStatus