The billable/non-billable line is one of the most loaded decisions in freelance design. Draw it too tight and you leave money on the table. Draw it too loosely and a client gets an invoice for forty-five minutes of "reading your brief" and sends you an angry email.
Most freelance designers resolve this by feel, inconsistently, invoice by invoice. Which means that on a good month they're billing generously and on a bad month they're quietly absorbing three hours of revision calls. Neither is a business strategy.
Here's a clean framework you can apply consistently — and a category breakdown for the cases that almost everyone handles differently.
The one-question test
Before logging a session as billable, ask: "Would the client pay for this if it were the only thing on the invoice?"
A 2-hour wireframe session: yes, obviously. A 3-minute Slack message confirming a deadline: no, obviously. A 45-minute video call reviewing feedback from the client's own stakeholders: probably yes, depending on your SoW.
This question doesn't resolve every edge case, but it cuts the ambiguous middle dramatically. If the honest answer is "they'd think that was unfair," it goes in overhead. If the honest answer is "they'd pay for a meeting that long without question," it goes on the invoice.
"Would the client pay for this if it were the only thing on the invoice?" Yes → billable. No → overhead. Uncertain → check your SoW, then decide once and apply consistently.
The clear cases
Billable without debate:
- Design work — wireframes, visual design, prototyping, production files
- Meetings the client requested (kickoffs, reviews, stakeholder presentations)
- Research explicitly scoped into the project (user interviews, competitive analysis you're delivering)
- Revisions beyond the contractual rounds
- File handoff, annotation, and specification documentation
Non-billable without debate:
- Sales calls, pitching, and proposal writing for the project you're on
- Invoicing, admin, and bookkeeping for the engagement
- Your own learning and tool setup (unless scoped as discovery)
- Waiting for feedback you could have been productive during
- Short functional messages (under ~5 minutes)
The tricky middle cases
These are where inconsistency lives. Pick a rule for each and write it into your standard SoW once.
Email and async communication. A 5-minute reply confirming a decision: overhead. A 30-minute email that is effectively a written design brief or a strategy discussion: billable as a 0.5h session. The threshold isn't message length — it's whether the content is deliverable. If you re-read it in six months and it would appear in the project's decision log, you were working.
Revision rounds 1 and 2. If your SoW says "two rounds of revisions included," then these are pre-priced overhead — you already got paid for them in your project rate. Track them anyway (see below). Rounds three onward are billable at your hourly rate.
Meetings that drift. A scheduled one-hour kickoff that runs to ninety minutes at the client's insistence: bill ninety minutes. A scheduled one-hour call you let run long by bringing up tangents: bill one hour. Clients can tell the difference, and so can you.
Brief reading and onboarding. If the brief is forty pages and you need two hours to absorb it before you can start, that's billable as "brief review." If the brief is four paragraphs and you need fifteen minutes, that's overhead. The dividing line is whether the time investment was caused by the client's complexity or your own process.
Discovery and research. Explicitly scoped and deliverable research is billable. Self-education that makes you better at the project is overhead. "I spent two hours learning Figma's new component system" is overhead. "I spent two hours auditing the client's existing component library and documenting gaps" is billable.
Track both — bill only what fits
ClockSplit lets you label every session by project and client. Tag non-billable time under "Overhead" to keep your records clean and your hourly rate honest. Free forever.
Why you should track non-billable time anyway
The most common mistake freelance designers make is only tracking billable time. This is understandable — why log time you won't be paid for? — but it's expensive in the medium term.
Your overhead ratio — non-billable hours divided by total hours worked — is the single most important number for pricing new projects accurately. If you're working forty hours a week and only billing twenty-five, your "effective" hourly rate is sixty-two percent of your stated rate. That changes how you should price a fixed-fee project. It changes whether a retainer is profitable. It changes what "a raise" actually looks like.
Track non-billable under a label like "Overhead — [client]" or "Admin." Don't put it on invoices. But do look at it quarterly, because it will tell you things about your practice that no other metric will.
Document the line in your SoW, once
The cleanest way to stop relitigating this every invoice is to write your billability rules into your standard statement of work once. Something like:
"Billable time includes all design work, client-requested meetings, reviews, deliverable research, and revisions beyond two rounds. Async communication under fifteen minutes per exchange is absorbed into the project rate. Revision rounds one and two are included. Additional rounds are billed at the hourly rate."
Once it's in the document, you stop making a judgment call on every invoice — you just apply the rule. Clients respect consistency far more than generosity; what they don't like is feeling like the rules change between invoices.
The goal isn't to bill the maximum possible. It's to bill honestly, predictably, and in a way your client can audit without calling you. Set the rule. Apply it every time. Use ClockSplit to track both sides of the line. Your effective hourly rate will take care of itself.