TimeRecord
← All posts

What Counts as Billable Time for Freelancers?

Know exactly which hours to bill and which to skip. A plain-language guide to billable vs non-billable time for freelancers, with real examples.

July 31, 2026 · 16 min read

Billable time is any work a client specifically asked for and agreed to pay you to do. If you spent that hour on their project, their problem, or their explicit request, it's billable. If you spent it running your own business, it almost certainly isn't.

That's the short answer. The trouble is that real freelance days don't come neatly sorted. You take a client call, then spend 20 minutes following up. You do research that's half for this project and half something you've always wanted to learn. You step away to make coffee and come back to find an hour has quietly passed on your timer.

This guide walks through what counts, what doesn't, and how to handle the messy middle ground honestly.

Table of Contents

What is billable time for freelancers?

Billable time is the time you spend doing work a client requested and is willing to pay for. The simplest test: if the client had watched you work during that period, would they consider it time spent on their behalf? If yes, it's billable. If not, it probably isn't.

This is a higher bar than "time I worked." Many freelancers work long weeks but only bill a fraction of those hours. That gap isn't failure; it's the reality of running a business. Admin, marketing, self-improvement, and bookkeeping all take time, but they're the cost of being in business for yourself, not a cost your clients bear.

A useful frame: your clients hire you to solve their problems. Your billable time is time spent solving those problems. Everything else belongs to your business overhead.

What is clearly billable?

These are the hours most freelancers agree belong on an invoice without debate:

Direct project work. Any time spent on the deliverable itself. Writing, designing, coding, editing, consulting, analyzing, building. If you're producing the thing you were hired to produce, you're billing it.

Client meetings with an agenda. A video call to review a design, a kickoff call to align on scope, a mid-project check-in where real decisions are made. Time spent in focused discussion with the client about their project is billable.

Revisions requested by the client. If the client asks you to change something within the agreed scope, revising is part of the job. Track that time and invoice it. (Revisions that fix your own mistakes are handled differently; see below.)

Research tied to the specific deliverable. You're building a landing page for a biotech company and you spend 45 minutes reading about CRISPR so you can write accurate copy. That research belongs to this project; bill it. The same applies to learning a specific tool the client's environment requires.

Feedback calls and review sessions. When you present work, walk through a prototype, or explain your decisions to the client, that's project time. Attending a client's internal meeting to give input counts too.

Short project-related messages. A few back-and-forth messages to clarify a task, request a file, or confirm a deadline are part of managing the project. If the combined exchange takes 10 minutes, capture it as 0.25 hours or fold it into the broader project block.

What is clearly not billable?

These activities matter for your business, but they don't belong on a client's invoice:

Business admin. Invoicing, bookkeeping, filing taxes, managing contracts, organizing your own files. These are costs you build into your rate, not line items on a client invoice.

Marketing and sales. Updating your portfolio, writing proposals, sending outreach emails, maintaining your professional profiles. Getting clients is your job; doing their work is theirs.

Discovery calls with prospects. The initial conversation to assess fit is a sales activity. Some freelancers offer paid consultations after a free first call; that's valid, but it must be agreed upfront, not added silently.

Professional development. Watching tutorials, taking courses, attending webinars, reading industry newsletters. Learning your craft makes you more valuable to future clients, but no single client pays for general professional growth. The exception: training on a specific tool a client explicitly asked you to learn for their project.

General research and tool setup. Setting up your own systems, evaluating software for your business, or reading broadly about a topic you should already know as a professional. These are business costs, not project costs.

Rework caused by your own errors. If you misunderstood the brief and have to redo work, absorbing that time is the professional choice. Billing for your mistakes damages trust faster than almost anything else.

Waiting time (usually). If you're waiting for a client to send a file or approve a deliverable, that wait isn't billable. You can work on something else during the gap, and if you genuinely can't proceed without the missing piece, that's a conversation about contract terms, not a line item.

How do the gray areas work?

Between "clearly billable" and "clearly not" sits a wide band of genuinely ambiguous time. Here's how to handle the most common situations.

Are client emails billable?

Short administrative exchanges (scheduling, file requests, quick yes/no answers) are generally absorbed into your project time rather than tracked separately. Long, substantive emails that require real thinking (reviewing a strategy, responding to a detailed brief, diagnosing a technical problem) are closer to consulting work and can be tracked.

A practical rule: if drafting a reply takes you more than 15 minutes, track it as project time. If it takes 2 minutes, let it go.

Are client meetings always billable?

Most of the time, yes. If you're in a meeting because of the project, you're working. Travel time to in-person meetings is a grayer area; many freelancers bill at least half their standard rate for significant travel. The key is that the client knows before the meeting, not after.

Social lunches or purely relationship-building calls with no agenda are harder to justify. Some long-term relationships include this as goodwill; just don't bill it without prior agreement.

Is project research billable?

Research is billable when it's specific to this client's problem and wouldn't have been done otherwise. Ask yourself: "Did I need to know this specifically because of this project?" If yes, bill it. If you've been meaning to learn this topic and the project gave you a good excuse, don't bill it (or bill only the genuinely project-specific portion).

Are revisions billable?

Revisions the client requested within the original scope: yes. Revisions that fix your own errors: no. Revisions caused by scope creep (the project keeps expanding beyond what was agreed) need a change order, not a billing decision made after the fact. Address scope changes upfront before doing the extra work.

What about prep and planning time?

Preparing for a meeting, reviewing a brief before starting, re-reading the client's notes after a few days off: these are project activities and generally billable. The threshold is whether this preparation is strictly for this client's project. Reviewing your own past work to refresh context is a judgment call; many freelancers track it, many don't. Consistency matters more than any single decision.

The idle time trap: when good intentions over-bill

One of the most common ways freelancers accidentally over-bill has nothing to do with dishonesty. It's idle time.

You start a timer, get into deep work, then step away to make coffee, handle a non-work phone call, or grab lunch. When you sit back down, your timer has been running for 45 minutes you weren't actually working. If you invoice that time, you've billed the client for your break.

Over a full month, these idle stretches add up quietly. You might log 42 hours but have genuinely worked 38. At even a modest hourly rate, that's a meaningful error on a single month's invoice. And experienced clients notice.

The professional fix is idle detection. A time tracker with this feature notices when you've been inactive for a set period and flags the gap when you return. You see a prompt: "You were away for 22 minutes. Keep or discard this time?" You decide. Nothing is trimmed without your input, and your final log reflects real work time.

TimeRecord handles this automatically. Its idle detection (default 8 minutes, adjustable up to 60 minutes on Pro) pauses tracking when you go inactive. When you return, it shows exactly how long you were away and lets you keep or discard the gap. You're always in control of the decision, and your records stay clean.

How to track billable hours without over-billing

The accuracy of your billing is only as good as your tracking method.

Start your timer when you start work. Memory degrades fast. Professionals who reconstruct hours at the end of the day or week routinely lose 10 to 20 percent of their billable time, and they also misattribute time: inflating some tasks while underreporting others. Tracking in real time prevents both problems.

Track in small chunks, consistently. The 5-minute email, the 12-minute quick fix, the unexpected client call that runs 20 minutes: capture all of it. These micro-tasks form a substantial share of any project's real time, and they disappear entirely when you try to remember your day at 6pm.

Use a structured Client/Project/Task system. When your time log is organized by what you were actually working on, billing becomes auditable. A client can see that 4.5 hours went to "Website redesign / Wireframes" and 1.2 hours to "Website redesign / Client feedback call." That level of detail answers billing questions before they become disputes.

TimeRecord organizes everything around a three-level hierarchy: Client, then Project, then Task. When you pull up a client's time report, you can hand it to them with confidence. The domain log (the websites visited while the timer ran) adds a layer of supporting detail: not surveillance, just quiet evidence that the time was spent working.

Use a privacy blacklist for personal browsing. If you sometimes handle personal matters while technically at your desk, exclude those sites from your tracking. TimeRecord's blacklist lets you add any domain; those sites are never captured, even during an active timer session.

What to include in your contract about billing

The cleanest way to prevent billing disputes isn't better tracking; it's clearer agreements. Before a project starts, establish:

Getting this in writing protects both parties. Clients know what to expect. You have clear authorization to bill what you've agreed to bill.

Common billing mistakes to avoid

Logging from memory at the end of the day. By 6pm, you can't accurately reconstruct where every hour went. Track in real time; your timer is more reliable than your memory.

Billing for mistakes. Rework caused by misunderstanding the brief or making an error erodes trust when clients notice. And they do notice.

Billing for idle time. A timer running through lunch produces an inflated total that doesn't reflect real work. Use a tool with idle detection, or be disciplined about stopping your timer when you step away.

Skipping small tasks. Many freelancers skip logging tasks that feel "too short." The 15-minute client email, the 20-minute bug fix, the 10-minute spec review are all real work. Track them. Over a month, habitually untracked small tasks amount to several lost hours of income.

Assuming the client remembers what they agreed to. Even with a signed contract, clients can be surprised by a bill. A brief note with your invoice ("Research for case study: 2 hrs, per project agreement") prevents confusion before it starts.

Using vague line items. "Design work: 12 hours" gives a client no way to assess your time. "Mobile nav redesign / wireframes and final CSS: 4.5 hrs" tells a story. Descriptive entries make invoices defensible.

Expert tips for honest, defensible billing

Track everything first, audit second. Let the timer run on everything. At the end of a session, spend two minutes reviewing your log and deciding what to bill and what to absorb. This is far easier than trying to make billing decisions in real time while also doing the work.

Create a short billing policy one-pager. Share it with every new client at the start of a project. Cover your minimum increment, your rate structure, how revisions work, and how you handle scope changes. Clients who understand the rules upfront rarely dispute invoices.

Keep your own record even when clients don't ask for it. You may not share your detailed time log with every client, but having it means you can answer any question instantly. The fact that you can show your work is often enough to prevent a dispute from forming.

Review your log before invoicing, not after. Before sending an invoice, spend five minutes scanning your entries: is every line correct, categorized, and clearly described? A small audit before invoicing prevents awkward corrections after.

Talk openly about gray areas. If you spent 90 minutes on research that could be interpreted as partly professional development, add a note. "Client-specific research on [topic] for case study section: 1.5 hrs." Transparency reads as professionalism, not weakness.

Billable hours checklist

Before submitting any invoice, run through this list:

Frequently asked questions

Is the time I spend on an initial discovery call billable? Usually not. A first-contact call to assess whether to work together is a sales activity. If the client specifically requests a paid consultation as part of their process, and you've agreed to that upfront, it can be billed. Make the terms clear before the call, not after.

Can I bill for travel time to a client's office? It depends on your contract. Many freelancers charge at least half their standard rate for significant travel, especially for cross-city or overnight trips. For nearby travel, practices vary. The rule is that the client knows and agrees before you invoice, not after.

What time increment should I use? Most freelancers and service firms use 0.25-hour (15-minute) increments. A 20-minute task rounds up to 0.5. A 7-minute task rounds up to 0.25. Some use 0.1-hour (6-minute) increments for more precision. Pick one and use it consistently; inconsistency is what triggers client questions, more than the increment itself.

Should I bill for time learning a tool a client requires? If the client explicitly requires a tool you've never used, and you're learning it specifically for their project, billing some of that time is reasonable. Be transparent on the invoice: "Onboarding with [tool] for project setup: 1.5 hrs." Don't bill for learning something you should already know as a professional.

How should I handle accidentally leaving my timer running? Don't invoice the full amount. Review your log before billing and trim any obvious periods where you weren't working. A tracker with idle detection handles this automatically: it prompts you when you return, and you decide whether to keep or discard the gap. If you're using a manual timer and notice the issue after the session, edit the entry before sending the invoice.

Is it ethical to bill for email? Short project-related emails: yes, folded into your project time. Long substantive responses that require real analysis: yes, tracked explicitly. Social check-ins, scheduling, or forwarding a quick file: usually absorbed. The guiding question is whether the email exists because of this client's project.

What's a realistic billable ratio for a full-time freelancer? Most full-time freelancers bill between 50 and 70 percent of their working hours. For a 40-hour week, that's 20 to 28 billable hours. The rest goes to admin, sales, professional development, and time between projects. This is normal; it's why your hourly rate needs to be meaningfully higher than the hourly equivalent of a salaried role doing similar work.

How do I handle a client who disputes my hours? Start with your time log: a structured record of what was tracked, when, and on what project and task. If your tracker also captured the domains you worked on during each session, that adds supporting context. Most disputes resolve quickly when a freelancer can produce a clear, organized record rather than just a number. If the dispute is genuine (a task took longer than expected, or there's a scope misunderstanding), address it directly rather than defending hours at all costs.

Wrapping up

Billing honestly isn't complicated, but it does require a system. The freelancers who never get pushback on their invoices aren't billing fewer hours. They're billing with clarity. Every entry is justified, every gray area is handled consistently, and their clients have no surprises.

The foundation of that clarity is accurate, real-time tracking. Not reconstructed logs or approximate totals: a live record of what you worked on, when, and for how long. That record is what turns an invoice from a number into evidence.

If you're looking for a time tracker built around that idea, TimeRecord captures your work automatically as you go: it logs the websites you use while the timer runs, organizes entries by Client, Project, and Task, and uses idle detection to prompt you whenever you step away. The free tier covers one client and three projects with no credit card required. You can also check the privacy policy to see exactly what's captured and what isn't.

Try it free

Bill the hours you actually worked

TimeRecord is a privacy-first automatic time tracker for freelancers, agencies, and consultants. It records your working time in the background and turns it into a timesheet your client can trust.

Get started