The Complete Guide to Capturing Every Billable Hour

If you bill clients by the hour, your income depends on two separate skills. The first is doing the work. The second is capturing the work, which means getting an accurate record of every billable minute into a system where it can be reviewed, described, and invoiced. Most professionals are excellent at the first skill and quietly terrible at the second, and the gap between the two is money leaving the practice every week.

This guide is about closing that gap. We will walk through where billable time actually leaks, why recording time as it happens beats reconstructing it later, how manual and automatic tracking genuinely compare, and how to build a capture workflow that turns recovered hours into revenue on your next invoice. None of this requires heroic discipline, only a system that works the way your day actually works.

The capture problem, stated plainly

Almost nobody who bills hourly believes they are losing significant time. The days feel accounted for, and the timesheet at the end of the week looks plausible. A plausible timesheet and a complete timesheet, however, are very different documents.

Billable time does not leak in large, memorable blocks. Nobody forgets the four-hour drafting session or the ninety-minute client meeting, because those events have a beginning, an end, and usually a calendar entry. Time leaks in small, interstitial pieces: the phone call taken while walking to the car, the email answered between meetings, the text message that turned into a fifteen-minute back-and-forth about a real client matter. We covered the five most common leaks in detail in Why You're Losing Billable Hours, but the short version is that the time you lose is the time that happens away from a running timer.

Where billable time actually leaks

Phone calls

Client calls are the single most reliable source of lost billable time, for a simple structural reason: they interrupt you. A timer-based workflow assumes you decide when work starts. A phone call decides for you, and by the time you have answered the question and agreed on next steps, starting a timer feels beside the point. A professional who takes even a few short client calls a day accumulates real hours of unrecorded work every week.

Text messages

Texting used to be personal. It is now a normal channel for client work, and in many practices it is the channel clients prefer. The work is real: you are reading, thinking, and giving advice. But no one has ever felt natural starting a timer to answer a text, and so this category of work is almost universally unbilled. The conversations are also scattered across the day in one-minute and three-minute fragments, which makes them nearly impossible to reconstruct afterward.

Email

Email is the sneakiest leak because it disguises analysis as administration. Skimming a newsletter is not billable. Reading a client's forwarded contract, thinking through the implications, and writing a careful three-paragraph reply absolutely is. The two happen in the same inbox, and a manual timer demands a start-and-stop decision at every switch. Almost nobody makes it, and the billable email time dissolves into the general fog of "doing email."

Travel

Whether travel time is billable depends on your engagement terms, but for many professionals, drive time to a client site, a courthouse, or an on-site meeting is legitimately chargeable, and mileage is reimbursable on top of it. Travel time leaks for the same reason call time leaks: you are occupied while it happens. You cannot take notes at highway speed, and by the time you arrive, the meeting has your full attention and the drive is already forgotten.

Small tasks

Finally, there is the psychology of the small task. A two-minute status update, a quick document check, a one-line answer to a client question: each feels too small to log, so it never gets logged. But if you bill in six-minute increments, as most legal and many professional practices do, those tasks are not too small at all. A two-minute task rounds to 0.1 hours under standard increment rules. Skipping it is not modesty. It is a discount you never agreed to give.

Why contemporaneous capture beats reconstruction

There are two ways to produce a timesheet. You can record time contemporaneously, meaning at or near the moment the work happens, or you can reconstruct it later from memory and whatever evidence survives. Everyone agrees the first way is better. Almost everyone practices the second, because reconstruction feels efficient: do the work now, tidy the records on Friday.

The problem is that memory is not a recording. It is a reconstruction of its own, and it degrades quickly and predictably. By the end of the day you have already lost the short interactions. By the end of the week you are working from a skeleton: calendar entries, sent email, and a general impression of being busy. Studies of professional timekeeping consistently find that time recorded after the fact understates what was actually worked, and that the gap widens the longer the delay. Notice the direction of the error: people remember the big blocks and forget the fragments, so delayed timekeeping is not a neutral inaccuracy but a systematic discount, and you are the one funding it.

There is a second advantage to contemporaneous records that has nothing to do with completeness: defensibility. When a client questions an invoice, a line item created at the moment of the work, with a timestamp and a duration, is simply a stronger document than one composed from memory days later. You can walk the client through exactly what happened and when. Disputes tend to evaporate when the record is specific, and specific records are a natural byproduct of contemporaneous capture.

Manual versus automatic capture: an honest comparison

Manual tracking means you decide when to record: you start a timer or you write an entry. Automatic tracking means software observes the work happening and creates the entry for you. Each approach has a domain where it genuinely wins, and pretending otherwise helps nobody.

Manual tracking wins on deliberate, scheduled work. When you sit down for a three-hour drafting session, starting a timer costs you two seconds and captures the block perfectly. Manual tracking also works on any platform and for any kind of work, including thinking, reading on paper, and in-person meetings, because it depends on your intention rather than on anything a device can observe.

Manual tracking fails on interruptions, and interruptions are precisely where the leaks live. Every category in the previous section shares one trait: the work starts without your permission. Calls arrive, texts arrive, email demands attention between other tasks, and travel occupies your hands and eyes. A system that depends on you pressing a button at the moment you are least able to press it will always miss this work. That is not a discipline problem. It is a design mismatch.

Automatic capture attacks exactly that mismatch. On Android, an app can, with your explicit permission, observe the activity that corresponds to client work: a call connecting, a message conversation, time spent in an email app, a drive to a client location. TrackTime's Android app does precisely this. It times inbound and outbound cellular calls and matches them to clients automatically. It captures SMS conversations and incoming RCS messages in Google Messages. It tracks time spent working in Gmail and Outlook and attributes it to the right client. It records drive time and mileage for client trips. All of it happens in the background, whether or not you remembered that the work was happening.

Two honest limits belong in this comparison. First, automatic capture of calls and messages is an Android capability. iOS does not allow any app to observe calls, message notifications, or which app is in the foreground, so genuine automatic capture of this kind is technically impossible on an iPhone. Second, automatic capture observes device activity, so it cannot see the work that happens entirely in your head or on paper. The realistic best practice is a hybrid: automatic capture for the interrupt-driven communication work it is built for, and quick manual entries for deliberate focus work. The two approaches cover each other's blind spots.

Privacy deserves a direct word here, because "software observes your communications" reasonably raises eyebrows, especially for professionals handling privileged or confidential matters. The design question is what gets stored. TrackTime stores metadata only: who the interaction was with, when it happened, and how long it lasted. It never stores message contents or email subject lines. That is all the information an accurate, billable time entry needs.

Building a capture workflow that actually holds up

Knowing where time leaks is not the same as fixing it. What fixes it is a workflow, meaning a small set of habits and tools arranged so that capture happens by default rather than by heroics. Here is a workflow that works, in five steps.

1. Decide what counts before the week starts. Write down, once, your policy on the gray areas: whether travel is billable and at what rate, how you treat short calls, whether email review counts, and what your minimum increment is. A one-page policy converts these judgment calls into defaults, and defaults get followed. Our guide on time tracking apps for lawyers covers how legal-specific increment rules interact with tool choice if you bill in tenths of an hour.
2. Automate the interrupt-driven work. Put the communication channels on automatic capture so that calls, texts, email time, and drives record themselves. This is the single highest-leverage change, because it removes the button-press from exactly the moments when pressing a button was never going to happen. If you carry an Android phone, this is a solved problem today.
3. Track deliberate work manually, at the moment it starts. For scheduled, intentional blocks such as drafting, research, and meetings, start a timer or log the entry when the block begins, not at the end of the day. The rule that makes this stick is simple: the entry is part of starting the work, the way saving a file is part of writing it.
4. Review daily, in five minutes. Once a day, look at everything that was captured, both automatically and manually. Confirm the client attribution, merge fragments that belong together, discard anything personal, and add a one-line description while the context is still fresh. Captured entries in TrackTime land in the web dashboard for exactly this kind of review and adjustment before anything reaches a bill. Doing this daily instead of weekly is the difference between editing a fresh memory and reconstructing a stale one.
5. Close the loop weekly. Once a week, scan the completed entries against your calendar and task list, and ask one question: is anything missing? Because the automatic layer has already caught the communication work, this check takes minutes, and what it usually surfaces is the offline work that no system can see. Add it while the week is still recent.

Notice what this workflow does not require: remembering to start a timer during a crisis, or an hour of Friday-afternoon archaeology. Automation carries the load where attention fails, and attention is spent where it adds value.

Invoicing the recovered time

Capture only pays off when the hours reach an invoice, and recovered time raises a few practical questions that deserve straight answers.

First, the mechanics. Apply your increment rules consistently: if you bill in six-minute increments, a four-minute call becomes 0.1 hours and an eleven-minute call becomes 0.2 hours, and this should happen uniformly across every entry rather than ad hoc. Give each entry a description that states the activity, the matter, and the purpose, because a specific line item is both more professional and less disputable than "phone call." Then itemize the communication entries rather than burying them in a lump sum. A client who sees "Call regarding contract revision, 0.2 hours" understands exactly what they are paying for. TrackTime's built-in invoicing generates the invoice directly from your reviewed entries, so recovered hours flow to a bill without a second tool.

Second, the client-relations question: will clients push back when previously invisible time starts appearing on invoices? In practice, the opposite tends to happen when the change is handled openly. Tell clients that you have improved your timekeeping so invoices now reflect actual work performed, including calls and correspondence. Detailed, specific line items build more trust than vague block entries ever did, and clients are far more accepting of accurate bills than of surprising ones.

Third, the arithmetic that makes all of this worth doing. Take a deliberately modest example. Suppose your rate is $200 per hour and better capture recovers just thirty minutes per working day, which is two short calls and a handful of client emails. That is $100 per day, roughly $2,000 per month, and on the order of $24,000 per year, recovered from work you were already doing. Run the same numbers at your own rate and your own honest estimate of daily leakage. The result requires no new clients and no extra working hours.

Frequently asked questions

How much billable time does the average professional actually lose?

Any precise universal number would be invented, so we will not offer one. What research on timekeeping consistently shows is the direction and the mechanism: time recorded after the fact understates real work, the understatement grows with delay, and short, interrupt-driven tasks are lost at a far higher rate than long scheduled blocks. The reliable way to learn your own number is to run automatic capture alongside your normal habits for a week and compare the result against what you would have written down.

Is automatically captured time legitimate to bill?

Yes, provided you review it. Automatic capture is a contemporaneous record of work that actually happened, which is more defensible than an entry composed from memory days later. The professional judgment stays where it belongs: you review every captured entry, decide whether it is billable under your engagement terms, and write the description. Automation captures the time. You decide what goes on the bill.

Can iPhone users get automatic capture of calls and texts?

No. iOS does not allow any third-party app to observe call activity, message notifications, or which app is in the foreground, so automatic capture of communication time is technically impossible on an iPhone. This is an operating system restriction, not a gap any vendor can engineer around. iPhone users can still apply everything else in this guide, including the capture policy, prompt manual entry, and daily review, and TrackTime's web dashboard and invoicing work from any browser. Full automatic capture, however, requires an Android phone.

What does automatic tracking store about my communications?

Check this carefully for any tool you consider, because the answers differ. TrackTime stores metadata only: who the interaction involved, when it occurred, and how long it lasted. Message contents and email subject lines are never stored. That is sufficient to create an accurate time entry while keeping the substance of privileged or confidential communications off our servers.

Find out what a week of real capture looks like

You cannot bill the hours you never captured, and willpower has had decades to solve this problem without success. The fix is a workflow where the leakiest work records itself and your attention goes to review and billing instead of recollection. Start a free 7-day TrackTime trial, put the Android app on your phone, and compare one week of automatic capture against your usual timesheet. The gap between the two is the raise you have been giving away.