How to Spot and Recover Billable Leakage

Billable leakage is the quiet gap between the work you do and the work you get paid for. No single lost half-hour feels significant, but across a team and a year it adds up to real money - often a month or more of revenue that was earned and never invoiced. Here is how to find it and close it.

The short version

Leakage is not a pricing problem, it is a recording problem. The work happened, it was worth billing, and it never reached the invoice because nobody wrote it down while it was still fresh.

  • Where it hides: forgotten time, small tasks, rounding down, absorbed scope, and late timesheets.
  • What it costs: 18 minutes a day across ten people is 60 hours a month. At $50 an hour that is $36,000 a year.
  • How to find it: a one-week diagnosis, described below. You do not need new software to run it.
  • What actually fixes it: capturing time as work happens, plus one reconciliation step before each invoice.
  • What does not fix it: screenshots and keystroke logging. Leakage is a memory gap, not a trust problem.

What billable leakage is

Leakage is billable hours that never reach an invoice. It is different from discounting: with a discount you choose to lower the price; with leakage the work simply disappears from the record before anyone decides anything. It shows up as a low realization rate - you billed less than you could have.

That distinction matters, because the two have opposite fixes. A discount is a commercial decision you can defend to yourself and revisit at renewal. Leakage is invisible, so it never gets revisited at all. It is the difference between choosing to give an hour away and never knowing you had it.

Where it hides

The usual suspects:

  • Forgotten time - work reconstructed days later from memory, always rounded down.
  • Small unlogged tasks - the five-minute call, the quick fix, the extra revision.
  • Rounding down - "call it half an hour" when it was closer to fifty minutes.
  • Scope creep - extra work absorbed instead of raised as a change.
  • Late timesheets - hours submitted after the invoice has already gone out.

Each one is individually defensible, which is exactly why the total goes unnoticed. Nobody ever decided to write off 60 hours; sixty people each decided to let one hour go.

What it costs

Leakage sounds abstract until it carries a number. These are the defaults in the Billable Leakage Calculator, which are deliberately modest - 18 minutes a day is less than one forgotten client call.

18 minlost per person per day
60 hlost across a team of ten each month
$36,000a year at an average rate of $50 an hour
$21,600recovered a year if you close 60% of the gap

Based on ten tracked people, 20 billable days a month, and an average rate of $50 an hour. Change any of those in the calculator to see your own figure.

The last number is the one worth sitting with. You are unlikely to recover all of it, and any article promising otherwise is selling something. Recovering half to two thirds is realistic, and on these inputs that is still more than a full-time salary.

Find it in one week

You do not need a new tool to run this diagnosis. You need one honest week.

1Ask everyone to log time as they work for five days, not from memory on Friday
2Compare that week’s hours against a normal week’s submitted hours
3List the work that appeared only in the honest week
4Check the last three invoices against approved hours for the same period
5Multiply the weekly gap by your billable weeks to size the year

The difference between those two weeks is your leakage, measured rather than guessed. In most teams the gap is concentrated in one or two categories, and that tells you which fix to apply first.

Close the gap

Leakage responds to habit and process, not surveillance:

  • Capture time as work happens, not at week’s end. This single change recovers most forgotten time.
  • Log small tasks too - they are the easiest hours to lose and the easiest to bill.
  • Reconcile before invoicing - compare approved hours with the draft invoice. An invoice and timesheet reconciliation worksheet makes the check routine.
  • Set a submission deadline so hours land before billing, not after.
  • Lock the period once it is approved, so a late correction cannot quietly change a number you have already invoiced.
  • Raise scope changes the day they appear, while the client still remembers asking.

Notice what is not on that list. Screenshots, keystroke counts, and idle detection do not recover a call nobody wrote down; they only tell you someone was at a keyboard. Leakage is a memory problem, and the fix is making the record easy to write while the memory is still there.

Measure it, then keep it closed

Track realization and utilization over time so leakage cannot creep back. A single clean month proves the fix worked; a stable trend proves it stuck. If the split between billable and non-billable work is unfamiliar, start with billable vs non-billable hours.

What is billable leakage?

Billable hours that were worked but never invoiced. The work happened and the client would have paid for it, but it fell out of the record before billing - usually because it was logged from memory, rounded down, or submitted after the invoice went out.

How much revenue does billable leakage cost?

It depends on your rate and team size, but the arithmetic is unkind. Eighteen minutes a day across ten people is 60 hours a month; at $50 an hour that is $36,000 a year. The Billable Leakage Calculator takes your own numbers and shows both the annual gap and what a realistic recovery rate is worth.

How do I know if my team has billable leakage?

Run one week where everyone logs time as they work rather than reconstructing it later, then compare that week against a normal one. The difference is your leakage. Checking recent invoices against approved hours for the same period usually confirms it.

Is billable leakage the same as low utilization?

No. Utilization measures how much of the available time was billable work at all. Realization measures how much of that billable work was actually invoiced. Leakage lives in the second gap, so a team can be fully booked and still lose a meaningful share of its revenue.

Does monitoring software stop billable leakage?

Not really. Screenshots and keystroke logging record presence, not what work was for which client. The hours that leak are the ones nobody wrote down, so the fix is making capture quick enough to happen during the work, not surveillance after it.

How quickly can leakage be closed?

The forgotten-time share responds within a week or two, because it only requires logging during the work instead of afterwards. Scope creep and late submissions take longer, since they depend on client conversations and a billing deadline everyone respects.

Sandtime.io helps you capture billable time as it happens and turn it into clean reports and invoice-ready totals - without screenshots or keystroke logging. A freelancer timesheet is enough to begin. It is free for unlimited users, so the whole team can stop the leak from day one. Browse the free tools and templates to get started.

About the contributors

Sandtime.io Editorial Team

Sandtime.io Editorial Team

Sandtime.io articles combine product knowledge, source research, and AI-assisted drafting. Every published guide receives human editorial review.

LinkedInWebsite
Przemysław Zalewski

Przemysław Zalewski

Sandtime.io engineer and Sanddev team member who reviews product accuracy, technical details, sources, and editorial quality.

LinkedInEmailSanddev profile