logr.work
Time tracking··7 min read

Billable vs non-billable hours

What counts as billable, what does not, why the gap quietly costs you money, and how to shrink it without working more hours.


Every hour you work falls into one of two buckets: hours a client pays for, and hours nobody pays for. That sounds obvious, but most freelancers and small agencies never actually draw the line. They track (roughly) how long a project took, invoice some of it, and quietly absorb the rest — the "quick call," the third round of revisions, the proposal that took a full afternoon. Understanding the difference between billable and non-billable hours, and seeing both in your time data, is the fastest way to find out where your margin is going.

Definitions

Billable hours are hours spent on work a client has agreed to pay for. The agreement matters more than the activity itself. Writing code, designing a landing page, editing a video — these are billable when they're part of a contracted scope and you're allowed to invoice them.

Non-billable hours are everything else you do to keep the business running: writing proposals, sending invoices, bookkeeping, learning a new tool, marketing yourself, internal meetings. This work is necessary, but no client pays for it directly. Its cost has to be covered by the rate you charge for billable hours — which is why non-billable time isn't "free time," it's overhead baked into your pricing. If you've never done that math, the hourly rate calculator for freelancers walks through it.

There's also a third, messier category: activities that are billable or non-billable depending on what your contract says. Client calls are the classic example. Some contracts include them in the hourly work; some treat them as free relationship maintenance; some cap them. The problem isn't which answer you pick — it's not picking one at all.

Classifying common activities

Here's how typical freelance and agency activities usually break down. Treat the "depends on contract" rows as a to-do list: each one is a clause you should settle before the project starts.

ActivityClassificationNotes
Core project work (design, code, writing, etc.)BillableThe contracted deliverable itself.
Client calls and meetingsDepends on contractBillable if your agreement says time spent on the project includes communication. Say so explicitly.
Revisions within agreed scopeBillableIf your contract includes "two rounds of revisions," those rounds are part of the paid work.
Revisions beyond agreed scopeDepends on contractShould be billable as change requests — but only if your contract defines the original scope clearly.
Writing proposals and estimatesNon-billableSales cost. You're pitching, not delivering.
Sales calls and follow-upsNon-billableSame — this is the cost of acquiring the client.
Invoicing and payment chasingNon-billableAdmin. Worth minimizing (see below), never worth billing.
Bookkeeping, taxes, contractsNon-billableBusiness overhead.
Learning and skill developmentDepends on contractGenerally non-billable. Exception: research a specific project requires (e.g., learning a client's proprietary API) is often billable if agreed upfront.
Commuting / travel to client sitesDepends on contractCommonly billed at a reduced rate or covered as expenses — but only if negotiated in advance.
Internal team meetings (agencies)Non-billableStandups, retros, planning that isn't tied to one client's deliverable.
Project management on a client's projectDepends on contractAgencies often bill PM time as a percentage or a fixed line item. Freelancers usually fold it into their rate.

Two patterns are worth noticing. First, almost everything in the "depends" column becomes billable only if it was agreed before the work happened. Retroactively billing for calls or travel is a losing argument. Second, the non-billable rows never go to zero — the goal is to make them visible and keep them proportionate, not to eliminate them.

Where margin quietly disappears

The classification table above is the theory. In practice, margin erodes in the gray zone between billable and non-billable — through work that should be billable but never gets invoiced.

Small favors. "Can you just tweak the header?" takes fifteen minutes. So does the next one, and the one after that. Individually, each favor is too small to invoice without feeling petty. Collectively, across a few clients and a few months, they add up to unpaid workdays. Because the work never got tracked, you can't even see how much you gave away.

Scope creep. Revisions round three, four, and five. A "small" extra page. A feature that was "implied." Scope creep is billable work reclassified as non-billable by default — because nobody stopped to say "that's a change request." Without a clear scope definition and a time log to point at, pushing back feels confrontational, so most people don't.

Untracked communication. If calls and emails are contractually billable but you don't record them, you effectively donate them. A two-hour weekly call over a three-month project is 24+ hours of work that vanishes from the invoice.

The common thread: none of this is a negotiation problem first. It's a visibility problem. You can't defend, bill, or reduce time you never recorded. That's why the fix starts with tracking discipline — the habits in how to track billable hours accurately apply directly here.

Making non-billable time visible (without billing for it)

The point of tracking non-billable hours is not to sneak them onto invoices. It's to know your real numbers.

The simplest mechanism is a billable flag on every tracked session: same timer, one extra bit of information. In Logr, each session carries a billable flag, so the dashboard shows billable hours alongside total hours — you see at a glance that last week was 34 hours of work but only 21 of them were billable, without maintaining a separate log.

Once both numbers are visible, you can:

  • Price correctly. If a third of your working time is overhead, your billable rate must cover it.
  • Spot creeping clients. A project whose non-billable share keeps growing is a project with a scope or communication problem.
  • Negotiate from evidence. "We've spent nine hours on out-of-scope revisions this month" is a very different conversation than "it feels like a lot."
  • Compare projects honestly. A high-rate project with heavy unbilled overhead can earn less per real hour than a modest one that runs clean.

For agencies, this visibility matters even more, because non-billable time multiplies across people — every internal meeting costs one hour per attendee. Time tracking for small agencies covers the team-level version of this.

Reducing non-billable overhead

You can't eliminate non-billable work, but you can shrink it:

  • Templatize proposals and contracts. Most proposals reuse 80% of the same structure. Stop rewriting it.
  • Systematize invoicing. Invoicing is pure overhead; every minute spent on it is unpaid. A repeatable process — or a tool that generates the invoice from your tracked billable hours — cuts it to minutes. The workflow in how to invoice a client as a freelancer is a good baseline.
  • Batch admin. One weekly admin block beats scattering bookkeeping and email across every day.
  • Convert "depends" items into contract clauses. Every gray-zone activity you settle upfront — calls, travel, extra revisions — moves hours from unpaid to paid.
  • Cap free favors explicitly. A line like "minor requests up to 30 minutes per month are included" turns goodwill into a defined, bounded benefit instead of an open tap.

A quick self-audit checklist

  • Does every tracked session have a billable / non-billable flag?
  • Does your contract state whether calls and meetings are billable?
  • Is the revision limit written down, with a rate for extra rounds?
  • Do you log small favors even when you don't bill them?
  • Do you know last month's billable vs total hours?
  • Does your hourly rate account for your non-billable share?

Utilization rate: the one number to watch

Utilization rate is the share of your working time that's billable:

Utilization rate = billable hours ÷ total working hours × 100

If you worked 160 hours last month and 104 were billable, your utilization is 65%. There is no universal "correct" number — a solo freelancer doing their own sales and admin will naturally run lower than an agency employee with work handed to them. What matters is knowing your number and watching its trend. A falling utilization rate means overhead is growing, a client is creeping, or your pipeline work is ballooning — all things you want to catch early, not at tax time.

Utilization also feeds directly back into pricing: your billable hours have to generate your entire income, so the lower your utilization, the higher your billable rate needs to be.

The line is yours to draw

Billable versus non-billable isn't a fixed taxonomy — it's a set of decisions you make in your contracts and then enforce with your time data. Define the gray-zone activities before each project, flag every session as billable or not, watch your utilization rate, and revisit your rate when the numbers shift. The work you don't bill for will always exist; the goal is to choose it deliberately instead of discovering it in a thin bank account.

Turn tracked hours into a paid invoiceLogr does both in one screen. Free forever, or self-host it.