Utilization vs Productivity vs Capacity: Formulas and Examples

What is the difference between utilization, productivity, and capacity?

utilization vs productivity vs capacity is a key topic in modern project management and teamwork. The three metrics differ in what goes on top of the fraction. Utilization and productivity both divide by hours; capacity does not divide at all.

The order matters because each one constrains the next. Capacity sets the ceiling. Utilization decides how much of that ceiling is converted into billable work. Productivity decides whether the billable work produces the expected output. A team can be at 90% utilization with terrible productivity, and it can have plenty of capacity at 60% utilization. Neither number is a verdict on its own.

How do you calculate utilization?

Utilization is billable hours divided by available hours, and the entire argument is about the denominator.

`Utilization % = (billable hours ÷ available hours) × 100`

Available hours are not 2,080 per person per year. That figure is gross paid hours, and using it guarantees a number that looks bad and means nothing. Subtract public holidays, paid time off, sick leave, training, and any explicitly non-billable internal time before you divide.

Worked example 1: one consultant, one year

A consultant has 2,080 gross paid hours. The year includes 10 public holidays (80 hours), 15 days of PTO (120 hours), and 5 days of training (40 hours).

• Available hours: 2,080 − 80 − 120 − 40 = 1,840
• Billable hours logged: 1,380
• Utilization: 1,380 ÷ 1,840 = 75.0%
• Same billable hours against gross hours: 1,380 ÷ 2,080 = 66.3%

That 8.7-point gap is why two consultancies can report wildly different utilization for identical work. Always ask which denominator is in use before comparing benchmarks. A 75% utilization on available hours is a healthy target for a consultant who also does proposals and internal work; 75% on gross hours implies closer to 85% of real available time, which is where queues start.

Two more definitions worth pinning down. Billable utilization counts only hours that appear on an invoice. Productive utilization counts hours spent on value-creating work, billable or not, including internal product work and R&D. A firm building its own software should track the second, or it will systematically under-invest in the thing that becomes its product.

How do you calculate capacity?

Capacity is the total number of hours a team can supply in a period, adjusted for the fact that nobody is 100% available.

`Capacity (hours) = Σ (headcount × available hours per FTE) × availability factor`

The availability factor is the share of available hours you are willing to commit to project work. It is a policy decision, not a measurement. Most delivery teams should plan at 75–85% of available hours and treat the remainder as the buffer that absorbs holidays, support, and the unexpected.

Worked example 2: a six-person consultancy quarter

Six consultants, one quarter. Available hours per person for the quarter: 460 (13 weeks × 40 hours, minus holidays and PTO).

• Gross capacity: 6 × 460 = 2,760 hours
• At an 80% availability factor: 2,760 × 0.80 = 2,208 sellable hours
• At a 75% utilization target on those hours: 2,208 × 0.75 = 1,656 billable hours
• At a $145 blended rate: 1,656 × $145 = $240,120 of delivery revenue

Now compare with the pipeline. Sales has committed 1,380 hours for the quarter. That is 83% of the 1,656 target, leaving 276 hours, or $40,020, unsold. The resourcing decision is not “are we busy”; it is “do we sell 276 more hours, or do we release a contractor for the quarter”. Two different actions follow from the same number, and both are legitimate.

Note what capacity is not. It is not the sum of everyone’s calendar. A person with 32 hours of meetings a week has 40 hours of nominal capacity and 8 hours of real capacity. Effective capacity subtracts recurring commitments first; nominal capacity is a spreadsheet fiction that produces optimistic promises.

How do you calculate productivity?

Productivity is output divided by labour input. The hard part is choosing an output unit you can measure without gaming it.

`Productivity = units of output ÷ labour hours`

For knowledge work, use a countable deliverable: onboarding packs completed, invoices processed, tickets resolved, releases shipped, reports produced. Then pair it with a quality measure, or the number will improve for the wrong reason.

Worked example 3: output per hour, before and after automation

A five-person operations team produces 480 onboarding packs per quarter and logs 1,920 hours.

• Baseline productivity: 480 ÷ 1,920 = 0.25 packs per hour, or 4 hours per pack
• After templating and a document-generation script, 540 packs in the same 1,920 hours
• New productivity: 540 ÷ 1,920 = 0.281 packs per hour, or 3.56 hours per pack
• Improvement: 12.5%, and 60 more packs without a hire

The honest follow-up question is whether quality held. If rework rose from 3% to 9%, the effective gain is smaller than it looks: 540 × 0.91 = 491 good packs against a baseline of 480 × 0.97 = 466. The improvement is real but roughly 5%, not 12.5%.

Worked example 4: productivity as earned value

For project work, productivity is often measured as value earned per unit of cost.

• Earned value: $180,000
• Actual cost: $150,000
• Cost performance index: 180,000 ÷ 150,000 = 1.20
• Interpretation: every $1 spent produced $1.20 of planned value, so the team is 20% more efficient than the baseline

Pair it with the schedule index. A CPI of 1.20 with an SPI of 0.85 means the team is spending efficiently while falling behind, which usually means scope was cut rather than work accelerated.

Why does high utilization reduce productivity?

Because work arrives in queues, and queues explode near full load. This is the single most useful thing to understand about utilization targets.

Under a simple queueing model, average waiting time grows with utilization by the factor ρ ÷ (1 − ρ). At 70% utilization the expected queue is 0.7 ÷ 0.3 = 2.3 service times. At 90% it is 0.9 ÷ 0.1 = 9 service times. A 20-point increase in utilization roughly quadruples the wait, before anyone is tired.

The practical consequence shows up in rework and context switching. Consider two patterns for the same consultant with 1,840 available hours.

Pattern A bills 221 more hours and delivers 25 fewer good ones. If you bill $145 an hour but the rework is absorbed, Pattern A looks better on the invoice and worse on the P&L. If the rework is billed to the client, you have a different problem, and it has a name.

This is also why utilization is a poor individual performance metric. It rewards people for being busy and punishes them for documenting, mentoring, or improving a process. Used as a target, it produces exactly what it measures: hours on timesheets.

Which metric should you use for which decision?

Two combinations do most of the work. Capacity ÷ target utilization gives the revenue ceiling for a period, which is the number to compare with pipeline. Productivity trend against a stable output definition tells you whether process changes are working, which utilization cannot, because utilization can rise while output falls.

How do you set a target you can defend?

Set the target from the bottom up, then test it against the queueing cost, and publish the definition alongside the number.

Start with the work that must be done but cannot be billed: proposals, account management, internal projects, training, one-to-ones. For the consultant in the first example, that is 460 hours a year, or 25% of available time. Utilization cannot exceed 75% without that work being displaced or done unpaid, so 75% is not a stretch target, it is arithmetic.

Then test the ceiling. If the team hits 90% for two consecutive months, look for the symptoms before celebrating: rising rework, slipping dates on fixed-fee work, holiday backlog, and voluntary turnover. Any two of those means the target is too high regardless of what the invoice says.

Finally, publish the definition in the same place as the number. “Utilization: billable hours ÷ available hours, where available excludes 80 holiday hours, 120 PTO hours, and 40 training hours per person” removes most of the argument in one sentence. Without that sentence, two managers will compute two numbers from the same timesheet and both will believe they are right.

Review the target quarterly, not monthly. Monthly noise produces monthly overreaction, and utilization targets that move every month stop being targets and become weather.

What are the trade-offs?

Precision versus comparability. A carefully computed available-hours denominator is more accurate and harder to compare with industry benchmarks, most of which use gross hours. Publish both if you report externally.

Utilization versus resilience. Higher targets raise short-term revenue and lower the buffer that absorbs sick days, spikes, and onboarding. Teams that plan at 85% and measure at 80% tend to hit both revenue and morale targets.

Productivity versus quality. Any output metric can be gamed by shipping more and checking less. Always pair the rate with a defect, rework, or satisfaction measure.

Capacity versus flexibility. Contractors add capacity in weeks and cost 30–60% more per hour. Hiring adds capacity in months and costs a fixed salary whether or not the pipeline holds.

Simplicity versus honesty. A single dashboard number is easy to communicate and easy to misread. Three metrics with clear owners beat one blended score that hides which lever moved.

What mistakes should you avoid?

Using 2,080 as the denominator. It understates utilization by 10–15 points and makes every team look underused.

Treating capacity as headcount. Six people is not a capacity figure. Six people × 1,840 hours × 0.8 is.

Measuring productivity without a quality counterweight. Volume goes up, rework goes up more, and nobody notices until the client does.

Setting a utilization target and calling it a productivity strategy. They measure different things; one can improve while the other falls.

Averaging utilization across mixed roles. A 95% billable consultant and a 35% billable operations manager average to 65%, which describes neither and misleads both.

Comparing benchmarks without checking definitions. A 78% utilization figure means three different things depending on whether the denominator is gross, available, or scheduled hours.

How does Doitify handle these numbers?

Doitify is our product, so treat this section as disclosure. Utilization, capacity, and productivity all depend on the same underlying data: who is assigned to what, how many hours it should take, and how much is left. Doitify keeps projects, tasks, sub-tasks, checklists, owners, due dates, and estimates in one workspace, and the workload view shows allocated hours against available capacity per person, per week.

The reports module covers work and performance reporting, so planned versus actual effort is available without exporting timesheets into a spreadsheet. That matters for the capacity question in particular: planned hours against a person’s real availability is a two-click read, rather than a quarterly reconstruction. Teams whose work is one project and three people will do fine with a spreadsheet that has the formulas above; the tool earns its place when capacity has to be checked weekly across several projects.

Conclusion

Utilization, productivity, and capacity are not three ways to say “busy”. Utilization is a commercial ratio with a denominator you must define out loud. Capacity is a planning ceiling measured in hours, not people. Productivity is an output rate that needs a quality check attached to it.

Use them in sequence. Start with capacity to know what you can promise, apply a utilization target you can sustain, then measure productivity to see whether the hours produced anything worth selling. A team that tracks all three, with the formulas written down, stops arguing about whether it is busy and starts deciding what to sell, hire, or stop doing.

If this post on utilization vs productivity vs capacity was helpful, you might also enjoy Roadmap vs Gantt Chart: Which Should You Use? and Free Capacity Planning Template.