Professional services run on a tricky double bind. You’re paying for people’s time, so hours matter. But clients pay you for work delivered, so output matters just as much. That tension is what makes measuring productivity harder than it looks. Track it by hours worked and you reward bums on seats. Track it purely by tasks completed and you lose the connection to what you’re actually billing. Most firms feel this every time they try to work out whether a busy week was a profitable one.
The honest answer is that hours and tasks aren’t rivals. They’re two halves of the same number, and the practices that get the most out of their teams measure both together. Here’s how to think about each, where each one misleads you, and how to land on a view of productivity that actually reflects the value your team creates.
What productivity means when you bill for time
In a professional services practice, productivity is the conversion of paid time into delivered, billable client work. Not hours sat at a desk, and not tasks ticked off a list, but the overlap: time that produced something a client will pay for.
That definition matters because the two obvious metrics each measure only one side of it. Hours worked tell you how much capacity a person spent. Tasks completed tell you what got done. Neither one, on its own, tells you whether the time spent was worth the work produced. A senior accountant who bills six focused hours can easily out-earn one who logged ten scattered ones. Once you accept that, the question stops being “hours or tasks?” and becomes “how do I see both at once?”
Measuring by hours worked: what it shows and what it hides
Hours are the default for a reason. They’re simple to capture, easy to compare, and they give you a clear read on capacity, who’s at the wall, who has room, and where you’re quietly paying overtime. For billing models built on time, you need the hours regardless.
The problem is what hours quietly absorb. Time spent in meetings, chasing emails, switching between client matters, and the occasional trip to the kettle all get folded into “productive time” when you only count the clock. Longer hours start to look like more output even when they aren’t. A raw hours figure overstates real client productivity before you’ve adjusted for anything.
There’s a human cost too. When the metric rewards time on the clock, people stretch their hours to hit it, and stretched hours lead to burnout, which is the fastest way to lose the productivity you were chasing. Hours are a useful input. They’re a poor scoreboard.
Measuring by tasks completed: sharper, but not the full picture
Counting what actually got finished fixes a lot of what hours miss. When you measure tasks, distractions stop counting as work. You can see which jobs genuinely eat time, match people to the work they’re best at, and spot scope creep on a client engagement before it quietly swallows your margin. For practices that want to understand where effort goes, task-level detail is far more revealing than a timesheet total.
It comes with its own catches. Tasks are harder to capture cleanly, since someone has to record what they worked on, not just how long they were online. Done badly, it tips into surveillance, and nobody does their best work feeling watched minute to minute. And task data on its own can flatter or punish unfairly: meetings and client calls are real work, but they don’t always show up as a tidy completed task.
So tasks completed answers a question hours can’t, what did this time produce, but it leaves you needing the hours to make sense of it. Which points to the obvious move.
The real answer: measure time against what it produced
Stop choosing. The most useful view of productivity records the hours and ties every one of them to the client, matter, or task it belonged to. A detailed time entry is just an hour with context attached, and that context is what turns a timesheet into an actual measure of value: not “Priya worked nine hours” but “Priya spent six billable hours on the Henderson audit and three on internal admin.”
This is exactly where a purpose-built tool earns its place. MinuteDock is a time tracking and billing platform built for professional services, and it captures both halves of the productivity question in a single time entry: the duration, plus the client (a Contact), the Project, and the Task it relates to. Because the context is recorded as the work happens, you get the hours for billing and the breakdown for understanding where time goes, without anyone reconstructing their week from memory.
That breakdown is what lets you measure productivity properly. With detailed entries flowing in, MinuteDock’s reporting shows utilization, billable versus non-billable splits, and how time maps to revenue across people and clients. It’s worth knowing the benchmark you’re measuring against: billable utilization in professional services organisations sits around 69%, so the gap between hours paid for and hours billed is where a lot of quiet margin lives. You can only close a gap you can see.
Putting it into practice without killing morale
Measuring both hours and output only helps if the way you do it builds trust rather than eroding it. A few habits make the difference.
Tie objectives to billable time, not just to-do lists
When you set work for the week, frame it in terms of the client it serves and the time it should take, not just the task. “Complete the quarterly reconciliation for this client within their four-hour retainer” gives a person a target they can actually manage against. Setting Budgets per client or project up front, then tracking time against them in real time, keeps those targets honest and flags overruns while you can still do something about them.
Capture time as the work happens
The single biggest threat to accurate measurement is the Friday-afternoon timesheet scramble. Memory fades fast: delaying time entry can lose around 10% of billable time the same day, 25% after a day, and 50-70% after a week, and firms recording weekly instead of daily can lose up to half their billable time. A running timer and a quick end-of-day habit captures a far truer picture than reconstruction ever will.
Review by client and project, not by headcount
Looking only at who logged the most hours rewards the wrong thing. Reviewing time by client and project tells you which work is profitable, which engagements are slipping past budget, and where senior time is being spent on jobs a junior could handle. That’s a conversation about work, not a leaderboard about people.
Build non-billable time into expectations
If a third of the week realistically goes to admin, business development, and training, target utilisation has to reflect that. Setting expectations as if every hour is billable just manufactures stress and missed targets. Use your actual historical splits to set goals people can hit.
Keep budget conversations transparent
Nothing damages a client relationship faster than a surprise invoice, and nothing damages a team faster than feeling measured in secret. Sharing budget progress as work proceeds, internally and with clients, keeps everyone aligned. MinuteDock’s Goals track progress towards targets in real time as entries are logged, so there are no end-of-month shocks.
Handled this way, measurement stops feeling like monitoring and starts feeling like the practice simply knowing where it stands. For more on tightening this up in an accounting context, our guide on time management tips for accountants goes deeper on the day-to-day habits.
Frequently asked questions
What’s a good utilization rate for professional services teams?
Targets vary by firm and role, but most billable team members aim for a high, sustainable share of their hours on client work, with the industry benchmark sitting near 69%. Set role-based targets, track them weekly, and review by client and project so you spot under- or over-utilisation quickly.
How do delayed time entries affect billable hours?
The longer someone waits to log time, the more billable detail disappears, and the losses are steep once you pass a day or two. Encourage same-day entries with running timers and a simple daily submission habit to capture a fuller, more accurate picture of the work performed.
What’s the difference between utilization and realization rates?
Utilization measures how much of a person’s available time is spent on billable work. Realization measures how much of that billed time is actually collected after write-downs and discounts. Track both: utilization to manage capacity, realization to protect margin.
The bottom line
Measuring productivity by hours alone rewards time at the desk, and measuring by tasks alone loses the link to what you bill. The teams that get this right do neither in isolation. They record the hours and attach the context, so they can see not just how long the work took but what it produced and what it was worth.
That shift, from counting time to understanding it, is what turns a timesheet into a genuine measure of how a practice is doing. MinuteDock captures both in one place, and you can try it free to see where your billable hours are really going.
