Billable vs Non-Billable Hours: What Actually Counts
Billable hours are the time you spend on work a client agreed to pay for. Non-billable hours are everything else you do to run your business — work that's real and often necessary, but that no client is paying for directly. Knowing which is which, consistently, is the foundation of accurate invoicing and a healthy utilization rate.
What counts as billable
If the work exists because a specific client hired you and falls within the scope you agreed, it's billable. That's broader than "heads-down time on the deliverable." It typically includes:
- The core deliverable work (design, code, writing, strategy)
- Calls, meetings, and project-related messages with the client
- Research and reading specific to the engagement
- Revisions and post-delivery fixes within scope
- Setup, deployment, and project admin the work genuinely requires
The test is simple: would this task exist if this client hadn't hired me? If no, it's billable.
What's non-billable
Non-billable time keeps your business running but isn't tied to a paying engagement:
- Sales: proposals, discovery calls with leads, pitching
- Your own admin: invoicing, bookkeeping, email triage
- Marketing: your site, content, social
- Learning and skill development
- Internal tools, planning, and breaks
Non-billable doesn't mean worthless — sales and learning are what create future billable work. It just doesn't go on a client's invoice.
The grey areas (decide these up front)
A few categories cause most billing disputes. Settle them in your agreement before the work starts, not on invoice day:
- Scope creep. "Quick" extra requests are billable — but only if you flagged them as such. Re-quote or note them when they happen.
- Revisions. Fixed-scope projects often include a set number of revision rounds; beyond that is billable.
- Travel. Often billable, often at a reduced rate. Agree the policy in advance.
- Rework from your own error. Generally non-billable — you don't charge a client to fix your mistake.
- Communication. A short check-in is usually billable; a long async thread definitely is. Don't let it slip into "free."
Why the split matters
Tracking the line between billable and non-billable does three things at once:
- Accurate invoices. You bill everything billable (no revenue leak) and nothing that isn't (no trust-eroding over-billing).
- A real utilization number. Billable ÷ total only means something if both are tracked. See billable utilization rate.
- Smarter decisions. When you can see how much time sales or admin actually eats, you know what to automate, delegate, or price into your rates.
How to track both without the overhead
The friction is that non-billable time is the time you're least likely to log — you're not going to start a timer for invoicing or email. So it goes uncounted, your utilization looks artificially high, and you never see where the day actually goes.
The fix is to capture the whole day automatically, then let billable status come from the project rather than a per-task decision:
- Passive time tracking records every app and document, billable or not, with no timer.
- Projects carry the billable flag, so a client project is billable and your "admin" project isn't — automatically.
- The billable total is ready to invoice; the non-billable total tells you the true cost of running the business.
That's how BillNotch handles it: track everything automatically, inherit billable from the project, and calculate billable hours without sorting entries by hand. See it for freelancers, or read how to track billable hours accurately and billable hours best practices.