Every services firm tracks a billable ratio somewhere, in a spreadsheet, a dashboard, or a manager's head. Far fewer firms trust the number, because the hours feeding it were logged inconsistently, reclassified after the fact, or never captured at all. Before you can improve a billable ratio, you have to be honest about what it is actually measuring.
In this guide
Billable vs non-billable time, defined The gray area: when client-related work still isn't billable Miscategorization mistakes that quietly skew your margins Healthy billable-ratio benchmarks by role How to improve the ratio without just demanding more hours Frequently asked questions
Billable vs Non-Billable Time, Defined
Billable time is any hour spent on work a client has agreed to pay for, whether that agreement is an hourly rate, a fixed-fee project, or a retainer. It includes the obvious things, coding a feature, drafting a campaign, running a workshop, but also client-facing work a lot of teams forget to log, like a scoped revision round, a status call the client requested, or research that was explicitly part of the deliverable.
Non-billable time is everything else: internal meetings, new business and proposal work, training, recruiting, admin, PTO, and the general overhead of running a services business. None of it is wasted time, a firm without sales, training, or internal process would not survive, but none of it can be invoiced to a client either. The billable ratio is simply billable hours divided by total hours worked over a period, and it is the single number that ties individual time entries back to firm-level margin.
The Gray Area: When Client-Related Work Still Isn't Billable
Most teams get the easy cases right. Where categorization actually breaks down is the gray area, work that is clearly about a specific client but isn't something the client asked for or would expect to be charged for. Internal sprint planning for a client's project, a debrief after a client call, an account team huddle to decide how to handle a tricky stakeholder, these all reference a real client and a real project, but they are internal operating overhead, not deliverable work.
A useful test is to ask whether the client would recognize the value if they saw the line item on an invoice. A revision the client requested passes that test. A meeting about how your own team should be staffed on the account does not, even though the client's name is all over the calendar invite. Getting this distinction consistent across the team, rather than left to individual judgment, is what makes a billable ratio trustworthy instead of just a number people argue about at review time.
Miscategorization Mistakes That Quietly Skew Your Margins
A billable ratio is only as good as the discipline behind the time entries that built it. A handful of habits show up again and again, and each one pushes the number in a direction that hides a real problem rather than surfacing it.
- Logging admin time against a client code to "look productive." This inflates the visible billable ratio for an individual while quietly eroding actual project margin, because the hours were never chargeable in the first place.
- Under-logging short interruptions. A five-minute Slack question or a quick email reply for a client rarely gets its own time entry, even though small billable moments add up across a week. Skipping them deflates both the ratio and real revenue.
- Bucketing everything under one generic project code. When billable and non-billable hours for the same client both land in a single code, nobody can see where the actual leak is, only that "the project ran long."
- Writing off scope creep as non-billable instead of flagging it. Extra client requests outside the original scope often get absorbed silently as "just part of the job," which erases the evidence that scope, not the team's speed, is the real margin problem.
- Reclassifying hours after the fact to hit a target. When a manager nudges entries between billable and non-billable near the end of a review period to make a number look better, the ratio stops measuring reality and starts measuring whatever story needs to be told that month.
A billable ratio that looks good on paper but was built on loose categorization is worse than no ratio at all. It gives leadership false confidence right up until the moment a project that "looked profitable" closes out with a real margin nobody saw coming.
Healthy Billable-Ratio Benchmarks by Role
There is no single correct billable ratio for an entire firm, because the right number depends heavily on someone's role, and holding everyone to the same target guarantees that some roles will always look like they're "underperforming" by design. What holds fairly consistently across agencies, consulting firms, and IT services teams is the general shape of the curve, not exact figures:
Delivery staff, the people actually doing the billable work, run highest, and in most healthy delivery-heavy teams that means the clear majority of a working week, commonly landing somewhere in the 70-85% range depending on how much unassigned bench time or internal QA the role includes.
Account and project managers sit meaningfully lower, because their job is coordination as much as delivery, status updates, resourcing, internal reviews, and client relationship work that often isn't chargeable. A ratio in the 40-60% range is a common and healthy pattern for this layer, not a sign the role is underutilized.
Leadership and partners run lowest of all, frequently under 30%, and that's expected rather than alarming, because a meaningful part of their job by definition is running the business: sales, hiring, strategy, and the operational work that makes everyone else's billable hours possible in the first place.
The mistake most firms make is applying one target ratio across every role and then wondering why account managers and leadership always "underperform" against it. Set separate, role-appropriate targets, and track trend direction over time rather than treating any single week's number as a verdict.
How to Improve the Ratio Without Just Demanding More Hours
The laziest fix for a low billable ratio is telling people to work more billable hours, and it's also the one most likely to burn out a team without fixing anything structural. The more durable levers sit on the other side of the equation, in scope, process, and overhead.
- Tighten scoping upfront, a clearly defined SOW with explicit deliverables and change-order terms prevents the slow, unbilled expansion of a project's real footprint
- Flag scope creep the moment it happens instead of quietly absorbing it, so it becomes a change-order conversation with the client rather than an invisible margin hit
- Automate the internal admin that eats into delivery time, timesheet reminders, status reporting, and invoice prep are classic non-billable time sinks that a connected platform can largely remove
- Move recurring internal tasks off senior delivery staff, junior or operations resources handling routine admin frees your highest-value people for billable work
- Set role-specific targets and review trends monthly, chasing a single bad week usually just pushes people toward the miscategorization habits above
Templates for recurring engagement types also help more than most firms expect, because rebuilding a project plan, a proposal, or a rate card from scratch every time is pure non-billable overhead that adds nothing new. Autovella bundles time tracking, invoicing, and project templates into one workflow specifically so that logged hours flow straight into a draft invoice instead of being rebuilt by hand, which removes one of the most common sources of unbilled and miscategorized time. You can see how the pieces fit together on the features page.
See how time and billing stay connected in Autovella
Get a live walkthrough of how logged hours turn into invoices without manual reconciliation.
Frequently asked
It depends on whether the work is inside the agreed scope or about running your business around that client. An internal sprint planning meeting, a status update your own team needs, or a discussion about how to staff the account is non-billable even though it is about a client, because the client did not ask for it and would not expect to see it on an invoice.
There is no single universal number, but the general pattern most services firms see is that delivery staff run highest, often somewhere in the 70-85% range, account and project managers sit lower because coordination work is non-billable, often in the 40-60% range, and leadership or partners run lowest, often under 30%, because their job includes running the business itself.
Focus on the denominator, not just the numerator. Tighten scoping so client work does not silently expand into unbilled hours, track and flag scope creep early instead of writing it off, and cut the internal admin load on delivery staff, timesheet chasing, manual invoice prep, status reporting, by automating it, so more of the workday is left available for billable work in the first place.