Most agency leaders know their utilization rate by the time they’re looking at last quarter’s numbers. Some know it by month end. A smaller group knows it weekly.
Almost none of them know what it will be eight weeks from now.
Gap worth closing. Utilization as a measurement tells you what happened. Utilization as a forecast tells you what you can still do something about. Not the same use of the same number.
What is agency utilization rate?
Agency utilization rate is the percentage of available working hours that a team spends on billable client work.
Simple calculation: billable hours divided by total available hours, expressed as a percentage. A team member with 160 available hours in a month who logs 120 billable hours is at 75% utilization.
Standard definition, and it’s only the starting point. Useful utilization analysis requires choosing the right numerator and denominator, understanding what “available” means in your context, and deciding whether you’re tracking utilization as a historical fact or as a forward-looking forecast.
Types of utilization that matter at agencies
Not all agencies use the same definition. Three versions come up often enough to be worth distinguishing.
Billable utilization measures hours charged directly to client projects against total available hours. Most common in agency reporting. Most useful for understanding revenue-generating capacity.
Productive utilization includes both billable work and non-billable productive work (new business, internal projects, business development). Useful for understanding total team output. Can mask genuine capacity issues if non-billable work is growing.
Target utilization is the internal rate the agency is planning against. 75% target utilization means you’re planning for 25% of capacity to be absorbed by overhead, PTO, training, and the inevitable gaps between projects. Comparing actual against target surfaces whether you’re over or under plan.
For most project-level and firm-level decisions, billable utilization is the right metric. Use it consistently and connect it to the decisions it’s meant to inform.
Standard utilization benchmarks for agencies
Directional ranges:
Direct production roles (creative, development, strategy, analytics): 70-80% billable utilization is generally considered healthy. Above 80% runs a burnout risk and leaves little buffer for reactive work. Below 65% suggests overstaffing relative to current pipeline. The 70-80% range also provides the flexibility to absorb an unexpected client request or an internal project without immediately stressing the team.
Project management and account roles tend to run at 60-70%. These roles carry more coordination and overhead by design. A project manager consistently at 85% billable is likely doing work that should be delegated, or the account team is understaffed.
Agency leadership: 40-60% is often realistic and appropriate. Heavy client work at this level limits the management and business development capacity that sustains the firm. Not a problem to fix. A structural reality to plan around.
These are directional. Your own numbers, segmented by role type and tracked consistently, are more useful than any industry average. The trend matters more than the absolute.
Why utilization measurement isn’t enough
Knowing your utilization rate last month is useful. Mostly for explaining what happened. Rarely for changing what happens next.
Here’s where the measurement-only approach breaks down in practice.
Knowing your utilization rate next quarter is useful for making decisions while you still can. That’s a different exercise.
Monthly utilization reports answer: did we bill enough of our capacity last month? The answer usually surfaces after you’ve already made the decisions that drove it.
Utilization forecasting asks: given our pipeline, headcount, and planned capacity, what will our utilization look like in six to eight weeks? And if that number is below target, what are we going to do about it?
Decision lead time is everything. A utilization forecast that says you’ll be at 55% in eight weeks gives you eight weeks to fill the pipeline. The same discovery at month-end billing gives you nothing. The month is already over.
How to forecast utilization
A basic forward utilization model requires four inputs:
Current committed projects. For each active engagement, how many hours per week is the team committed to over the next eight weeks? This is your floor. It’s already sold and staffed.
Incoming pipeline. For deals likely to close in the next eight weeks (weighted by probability and expected start date), what headcount will they consume? A 70% probability deal that’s expected to close in three weeks contributes 70% of its staffing requirement to the forecast.
Planned capacity. Who is available, and at what percentage, over the forecast window? Subtract approved PTO, known commitments, onboarding load for new hires, and any significant internal project work.
Target utilization. What rate are you planning to run at? 75%? 78%? This is the standard against which you’re comparing the forecast.
Bringing these together gives you a forward view: at current pipeline and capacity, where is utilization heading? If it’s heading below target, you have time to act. If it’s heading above 85%, you have time to plan.
Most agencies have this data in multiple systems. Pipeline lives in the CRM. Headcount and PTO live in HR. Project staffing lives in resource planning. Resource forecasting tools exist specifically to connect these inputs without requiring a weekly manual assembly exercise.
What utilization forecasting enables
A utilization forecast changes what decisions you can make and when.
Hiring decisions become earlier. If the forward model says utilization will climb above sustainable levels in ten weeks, you have a data point for starting a hire now rather than after delivery quality suffers. Hiring decisions driven by a utilization forecast tend to land better than those driven by delivery emergencies. Different candidate pool, longer onboarding runway, different outcome.
Pipeline urgency becomes visible. If the forecast shows utilization dropping below target in six weeks, you have a specific trigger for the business development conversation. Not “we should probably be selling more” but “we have a capacity gap forming and we need pipeline to close by a certain date.” That level of specificity changes the energy of the conversation.
Pricing confidence increases. When you know you’ll have senior capacity available at a specific point, you can price and commit to work with more confidence. When you’re guessing at availability, the default is to overprice to hedge against scarcity, or underprice because the capacity appears available until it suddenly isn’t. Both create problems. Forward visibility reduces guessing.
Resource planning conversations change character. When the weekly resourcing meeting has a forward utilization view alongside the assignment schedule, the conversation can shift from “who is available next Tuesday” to “what’s the trend line over the next six weeks and what does it mean.” That shift takes time to build, but it produces fundamentally different decisions.
Common mistakes in utilization tracking
Measuring total hours rather than billable hours. If someone is available for 160 hours but the spreadsheets most agencies use count all hours worked including PTO, admin, and sick time in the denominator, the number is distorted. You end up with a utilization figure that looks fine and masks a real billing gap.
Not distinguishing role types. An overall agency utilization of 72% can obscure that creative is at 88% (overtaxed) while account management is at 58% (under-deployed or understaffed on the wrong end). Role-level visibility changes where you act. Overall-firm utilization is useful for executive reporting. It’s less useful for operational decisions.
Treating planned and actual as the same number. Planned utilization (what you intended) and actual utilization (what was logged) diverge. Both are useful. Confusing them produces a number that nobody can act on confidently.
Using utilization as the only financial health metric. High utilization at below-market rates doesn’t produce good margins. Low utilization on premium-priced retainers might. Utilization is one input to financial health, not a measure of it. Connect it to revenue, rate, and margin data to see the full picture.
Not building a reconciliation habit. A utilization number that gets reviewed once a month at the leadership meeting tends to produce one-month-lagged interventions. Teams that run a weekly utilization check, even briefly, catch small divergences before they compound. Resource forecasting discipline is a habit before it’s a system.
How to read a utilization number
A utilization number doesn’t tell you much in isolation. Here’s what to look for in the context around it.
Stable or volatile? A team running at 74% consistently is in a different position than a team that swings between 55% and 90% over the same period. Volatility suggests structural gaps in how work is pipelined and onboarded. Addressing volatility is a different problem than addressing a low floor.
Is it uniform or concentrated? If one team is at 90% and another at 60%, the average is 75% and looks fine. But one team is at risk of quality problems and the other is at risk of attrition or pipeline problems. Averages mask distribution. Distribution drives decisions.
Trending which direction? Month-over-month direction matters as much as the absolute number. Utilization declining from 78% to 72% to 66% over three months warrants action, even if 66% is still technically in the healthy range. A number that’s declining is a problem forming.
Where is the demand coming from? Utilization driven by over-delivery on existing accounts is different from utilization driven by new pipeline. One is a capacity management issue. The other is a growth signal. Both look the same in an aggregate utilization report, and both require a different response.
If your agency tracks utilization in arrears and wants to move toward a forward-looking view, the planning gap between pipeline and capacity is usually where to start. Most of the data already exists. Pipeline is in the CRM. Headcount and PTO are in HR. Project staffing is in the resourcing tool. Connecting those three data sources consistently is the exercise. We have run this analysis with agencies across size ranges. Happy to compare notes on what a forward utilization model looks like in practice.
Utilization measured is information. Utilization forecasted is leverage. Most agencies have the data to do both. What they’re usually missing is the habit of combining it on a weekly cadence, and the ownership structure that ensures someone acts on what it shows.
Frequently Asked Questions
For direct production staff (creative, strategy, development, analytics), 70-80% billable utilization is generally considered healthy. Below 65% suggests over-staffing or pipeline gaps. Above 85% runs a risk of burnout and delivery quality issues. For management and account roles, 60-70% is more typical because their work includes more coordination overhead. Agency leadership is often in the 40-60% range. The right target depends on your pricing, overhead model, and growth stage.
Billable hours divided by available hours, times 100. Available hours should exclude approved PTO, holidays, and any non-working days. The most common errors: including all hours worked (not just billable) in the numerator, or using total calendar hours instead of actual available hours in the denominator. Role-level calculation is more useful than firm-level aggregation for most decisions.
Billable utilization counts only hours charged directly to client projects. Productive utilization includes both billable work and non-billable productive work (new business, internal projects, R&D). Billable utilization is the cleaner metric for capacity and revenue decisions. Productive utilization is useful for understanding total team output, but it can mask genuine capacity issues if non-billable work is growing without corresponding revenue.
Six to eight weeks is the practical range. Far enough out to take action on what you find (start a hire, increase sales pressure, plan subcontracting) but close enough that the forecast is credible. Beyond twelve weeks, forecast accuracy for agency-type work degrades quickly because pipeline timing and scope are too variable. At the firm level, quarterly horizon planning makes sense for staffing decisions with longer lead times.
Project-based work by definition creates gaps between engagements. The transition periods between project close and project start are the structural cause of utilization dips. The other major driver is scope variance: projects that end sooner than expected leave team members with unplanned availability. Agencies that manage transitions actively (overlap resourcing, internal project buffer, new business pipeline cadence) have less utilization volatility than those that plan project-to-project without visibility across the portfolio.
Directly. Low utilization means you’re paying for capacity that isn’t generating revenue. High utilization above a sustainable ceiling means you’re degrading the capacity itself through burnout. At the target range (70-80% for production roles), you’re generating enough billable output to cover team costs and overhead with room for margin. Resource forecasting that connects utilization, pipeline, and cost structure gives leadership the visibility to optimize across all three rather than managing them as separate problems.