Utilization vs realization rate: the key difference

Utilization rate and realization rate both measure how well an agency turns time into revenue, but they measure different stages of it. Utilization is the share of your team's available capacity that goes to billable work. Realization is the share of that billable value you actually invoice and collect. Tracking one without the other hides half the story. You can be busy and still under-bill, or bill cleanly on work nobody had capacity to do. This post defines both rates, shows why they diverge, and explains how to read them together.

What utilization rate measures

Utilization rate is the percentage of a person's available working time that goes to billable client work. A designer who logs 30 billable hours in a 40-hour week is at 75% utilization. The other 10 hours cover internal meetings, admin, pitches, or gaps between projects.

Utilization looks at the input side of the business: how much of the capacity you pay for turns into billable hours. It answers one question. Are we filling the time we pay for with work we can charge for? A low number means capacity is sitting idle or going to non-billable work. It says nothing about whether that billable work was priced well or actually invoiced. That is the part realization covers.

Utilization is usually the first operational number an agency watches, because billable time is what the business sells. If yours is low and you want practical ways to lift it, see our guide on how to increase your billable utilisation rate. This post stays on the difference between the two rates rather than how to move either one.

What realization rate measures

Realization rate is the percentage of your billable value that you actually invoice and collect. You can log time as billable and still not turn all of it into revenue, because of write-offs, discounts, scope caps, or hours that never make it onto an invoice.

There are two common ways to frame realization. The hours version is billed hours divided by billable hours. The value version is invoiced revenue divided by the value of that time at your standard rate. Both answer the same question: of the billable work you did, how much became money?

Say a consultant logs 40 billable hours at a standard rate of $200, which is $8,000 of billable value. The client had agreed a cap that meant you invoiced $6,800. Realization is 85%. That 15% gap is work you did, could have charged for, and gave away.

Realization looks at the output side. A low number means value is leaking after the work is done, through discounts, write-offs, or uninvoiced time, rather than through idle capacity. Utilization and realization sit at opposite ends of the same pipeline: one measures whether the work happens, the other measures whether it gets paid for.

Utilization vs realization rate at a glance

The quickest way to hold the two apart is to line up the formula and what a low number is telling you.

The formulas make the split clear. Utilization is measured before the invoice, in your time data. Realization is measured at the invoice, against what you could have charged. A single dashboard number for either one, read alone, tells you nothing about the other.

Why the two diverge

The two rates diverge because they measure different stages, so a problem at one stage does not show up in the other. High utilization tells you the team is busy on billable work. It does not tell you that the work was invoiced at full value. Because the rates sit at different points, you can land in four situations:

• High utilization, high realization. The team is busy on billable work and you invoice most of its value. This is the target.
• High utilization, low realization. Everyone is slammed, but discounts, write-offs, and uninvoiced hours mean a large share of that work never becomes revenue. The team is busy while its output leaks on the way to the invoice.
• Low utilization, high realization. Capacity is sitting idle, but the billable work you do get through is invoiced cleanly. This points to a pipeline or scheduling problem rather than a billing one.
• Low utilization, low realization. Capacity is idle and the little billable work you do leaks value before it reaches an invoice.

This is why utilization alone misleads. A dashboard showing 85% utilization looks healthy until you learn realization is 70%, which means nearly a third of the billable work is being given away. The reverse holds too. Strong realization on a half-idle team still leaves margin on the table, because there was not enough billable work to invoice in the first place. Each rate sets a ceiling the other cannot lift on its own.

Reading them together

Read utilization and realization side by side, because each one caps what the other can deliver. Utilization sets how much billable work exists. Realization sets how much of it becomes revenue.

Multiply them and you get a rough measure of how much of your paid-for capacity turns into invoiced work. A team at 80% utilization and 85% realization converts about 68% of its available capacity into billed value. Move either number and the combined figure moves with it. That combined figure is often a truer read on agency health than either rate on its own, because it captures both idle time and leaked value in one number.

The next metric downstream is your effective hourly rate, what you actually earn per hour once every hour is counted. Utilization and realization explain most of the gap between your rate card and that effective rate: idle capacity on one side, leaked billable value on the other.

Reading the two rates together only works if both come from the same data. Utilization lives in your time tracking. Realization lives in what you invoice. When those sit in separate tools, you end up comparing last month's timesheet export against this month's billing, and the picture is always stale. Pike connects logged time to project billing, so utilization and realization update from one source as the work happens. See how time tracking feeds both numbers.

Common mistakes

Tracking only utilization is the most common error. It is the easier number to pull, so agencies watch it and assume a high value means a healthy business. A busy team that writes off a third of its work looks fine on a utilization chart and is quietly unprofitable underneath it.

Treating a high number as automatically good is the next trap. Utilization sustained near 100% often means non-billable work is going untracked, or the team is heading for burnout. Realization at 100% can mean you never flex on price, which is not always the right call for a long-term client relationship. Both rates have a healthy range, not a maximum to chase.

Averaging across the team hides the imbalance that matters. A group at 75% utilization can be two people at 95% and two at 55%. The average looks acceptable while individuals are either overloaded or idle. The same applies to realization, where one heavily discounted account can drag the whole number down.

Comparing exports from separate tools is a data problem, not a measurement one. If your timesheets and your invoices live in different systems, the two rates never line up in time, and you are always reading history. Connected data is what makes reading them together possible in the current week rather than after the month closes.

Confusing realization with effective hourly rate or margin is the last one to watch. Realization measures how much of your billable value you invoice. Effective hourly rate measures what you earn per hour once all hours, billable or not, are counted. Margin measures what is left after cost. They are related, but each answers a different question, and using one as a stand-in for another buries the specific problem you need to fix.

Frequently asked questions

See both rates in Pike

Utilization and realization are only as accurate, and only as current, as the time and billing data behind them. Pike keeps logged time and project billing in one place, so both rates reflect the current week rather than last month's export. Compare plans and see what is included on the pricing page.