Tracking billable hours is the difference between getting paid for the work you did and getting paid for the work you remember doing. Memory is generous to itself — a day that felt like eight hours of client work was probably six, with two hours of email, Slack, coffee, and the mental overhead of switching between them. Over a month, that gap is the difference between a profitable quarter and one you subsidize with unpaid labor.
This is a practical guide to doing it right: what to track, how to track it, how to turn it into an invoice, and the mistakes that cost freelancers money.
What counts as billable
The first mistake most freelancers make is not knowing what they're supposed to track. The rule is simpler than people make it:
Billable time is any time you spend working on a client's project that your contract says they're paying for.
That includes:
- Direct work — design, development, writing, consulting, whatever the deliverable is.
- Meetings with the client — calls, video chats, in-person reviews. If the client is on the call, the time is billable unless your contract says otherwise.
- Email and communication about the project — the back-and-forth on scope, feedback, revisions, and status updates. Most freelancers don't track this and it's where the most underbilling happens.
- Research specific to the project — reading docs, reviewing the client's existing codebase, competitive analysis scoped to their engagement.
- Revisions and review cycles — the second and third rounds that the original estimate assumed were included.
What's not billable:
- Admin and business development — invoicing, your own bookkeeping, pitching new clients, updating your portfolio.
- General learning and skill-building — a course, a tutorial, a conference. This is overhead your rate should absorb, not a line item.
- Context-switching and breaks — the 10 minutes between finishing one task and starting the next. This is your time, not the client's.
- Fixing your own mistakes — if you broke something and need to fix it, that's not the client's problem. Track it against an internal project so it shows in your reporting but not on the invoice.
The gray area is internal communication with your team about a client project. Most contracts bill it. Most freelancers don't track it. If you spent 30 minutes in Slack discussing a client's architecture decision, that's billable time on that client's project — track it.
Choose your billing increment
Before you start tracking, decide the unit you bill in. The common options:
- Exact time — every minute tracked is billed. Honest, precise, but produces invoices with awkward line items ("2h 17m") and requires careful tracking.
- Rounded to 15 minutes — the most common increment. 0–7 minutes rounds down, 8–22 rounds to 15, etc. Clean invoices, small rounding loss.
- Rounded to 30 minutes — common for consultants and lawyers. Bigger rounding, bigger loss, but simpler invoices.
- Rounded to 1 hour — common for senior consultants who bill in whole hours. Significant rounding loss if your work pattern is many small entries.
The trade-off is precision vs simplicity. If you do deep blocks of 2–4 hours per client per day, any increment works because the rounding is minimal. If your work pattern is interleaved — 20 minutes here, 15 minutes there, across multiple clients — the increment matters a lot. A 15-minute increment on interleaved work can add 10–20% more billable time than an exact-time log, because each small entry rounds up.
Pick one increment, put it in your contract, and stick to it. Switching increments mid-engagement is how you lose the client's trust.
Choose your tracking method
Three approaches, each with a trade-off:
Manual tracking — start and stop the timer
The most accurate for billing, because you decide what's billable in the moment. Start the timer when you begin client work, stop it when you stop.
The friction is the switching cost. If you switch between clients, tasks, and contexts all day, manual tracking means 20–30 timer starts and stops. The discipline holds for a week. By week three, the gaps start showing.
Best for: freelancers who work in long, focused blocks on one client at a time.
Automatic tracking — capture everything, sort later
Tools like Timing and Timemator capture which apps, documents, and websites were foreground, then you categorize the activity after the fact. The capture is passive — no timer to start or stop.
The strength is no forgotten hours. The weakness is that automatic capture records what you did, not which client to bill it to. Reading a code review in a browser tab doesn't tell anyone whether it was Client A's review or Client B's. The mapping back to billability still requires a moment of judgment.
Best for: freelancers who bounce off manual tracking, or whose work is concentrated on one client at a time so the attribution is unambiguous.
Hybrid tracking — timer for billable, auto for everything else
The pattern that works for most freelancers: use a manual timer for billable client work (because you need the client attribution), and let automatic or passive capture run in the background for personal awareness (where did your week actually go?). The two don't conflict — they answer different questions.
Ayron supports this hybrid model. The menu bar timer handles billable entries with explicit project and client selection. Idle detection catches forgotten timers. The AI weekly report turns the week's entries into a summary that reads like a status update — useful for catching gaps between what you tracked and what actually happened.
Best for: freelancers who bill hourly across multiple clients and need both accuracy and awareness.
The daily workflow
Whatever method you choose, the daily discipline is the same:
Start the timer when you start the work
Not five minutes later. Not when you remember. When you sit down to work on a client's project, the first action is starting the timer against that project. Not opening Slack. Not checking email. Start the timer, then context-load.
Why: the moment you decide what to work on is the only moment you have full clarity. Five minutes later you're in the file and the decision is lost. By Friday you're reconstructing Wednesday from memory, and memory is wrong.
Switch the timer when you switch contexts
When you shift from one client to another, from client work to admin, from deep work to a meeting — switch the timer. The switch is free at the moment your brain already context-switched; tracking it adds no additional cognitive load because the cost has already been paid.
The hard part is the in-between: the 5-minute Slack tangent, the 3-minute email check. Don't switch the timer for those — fold them into the surrounding block. If a tangent lasts more than 15 minutes, it deserves its own timer. Below that, it's noise.
Write one sentence before you stop
The single most underrated practice in time tracking: write one sentence in the note field before you stop the timer. Not a paragraph. One sentence: "Implemented retry logic for the webhook dispatcher; needs unit tests Monday."
That one line is what saves you on Friday afternoon when you can't remember what Wednesday was about. It's also what makes AI weekly summaries useful instead of generic, because it gives the report actual context to work with.
The weekly review
A 30-minute block, ideally on Friday morning. Three jobs:
1. Reconcile the week
Look at your tracked hours per client. Anything mistagged, mislabeled, or split across the wrong project — fix it now, while you remember. The cost of fixing it Friday is 30 seconds. The cost of fixing it next month is 30 minutes, if you can reconstruct it at all.
2. Check estimates against actuals
If you set estimates on your projects (and you should — see estimate-vs-actual tracking), this is the moment to look at where each project stands against its budget. A project trending 20% over estimate is a conversation you want to have on Monday, not after the invoice goes out.
3. Write or review the weekly summary
If you're using a tool with AI summaries, read the weekly report as a first draft. Catch the misallocations, fix the project names, add the context the AI missed. A first draft you edit is dramatically faster than a status report you write from scratch.
If you're doing this manually, write a one-paragraph summary per client: what got done, where the time went, and what's next. You'll need it for the invoice anyway.
Turn tracked hours into an invoice
The final step is the one most freelancers get wrong — not because it's hard, but because they leave it as a separate task that gets postponed.
Don't rebuild the invoice from scratch
The tracked hours are already categorized by client, project, and date. The invoice should pull from that data directly, not from a spreadsheet you maintain separately. The gap between your tracker and your invoice is where hours get lost, rates go stale, and reconciliation details drift.
If your time tracker includes first-party invoicing — Ayron does, Harvest does — use it. The line items on the invoice should match the tracked entries by name, rate, and total. If they don't match, something in your process is wrong.
Include the right details
A clean invoice line item for tracked time should show:
- Date or date range — when the work was done.
- Description — what the work was. The one-sentence notes from your timer are the source for this.
- Hours — in your chosen billing increment.
- Rate — your hourly rate for this client.
- Total — hours × rate.
Send it with a payment mechanism
An invoice without a payment link is a PDF that sits in an inbox. If your tool supports Stripe or another payment processor, include the payment link directly in the invoice. The faster the client can pay, the faster you get paid. Ayron's invoicing embeds Stripe links in branded PDFs; the invoice status flips to Paid the moment the charge clears.
Common mistakes that cost money
Not tracking email and communication time. If you spend 45 minutes on a client email thread about scope, that's billable. Most freelancers don't track it. Over a year, it's a week of unpaid work.
Rounding down instead of up. If your increment is 15 minutes and you worked 22 minutes, bill 30. If you worked 8 minutes, bill 15. The rounding goes in your favor — that's what the increment is for. Rounding down is a donation.
Waiting until month-end to reconstruct. The longer the gap between doing the work and recording it, the less accurate the record. Track in the moment, review weekly, invoice weekly or biweekly. Monthly invoicing from memory is how billable hours disappear.
Not tracking internal time. Create an "internal" project for admin, business development, and non-billable work. You won't invoice it, but you need to know how much of your week is unpaid overhead. If 40% of your time is internal, your billable rate needs to cover it — and you can't know that if you're not tracking it.
Forgetting to stop the timer. A timer that runs through a two-hour lunch break is either a billing error (if you don't catch it) or a reconciliation headache (if you do). Use a tool with idle detection — Ayron, Timing, and Tyme all handle this — so the app catches the gap and you confirm or discard.
The simplest next step
If you're not tracking today, start with one client engagement for one week. Don't change your behavior — just capture it. Track every hour, including email and meetings, in whatever tool is closest to hand. At the end of the week, compare what you tracked against what you would have invoiced from memory.
If even one of those numbers surprises you, you've found the thing tracking is actually for.
If you want a tool that handles the full loop — timer to estimate-vs-actual to branded invoice to Stripe payment — Ayron is built for it. Free to start, Pro is $12/mo annual.
FAQ
What is the best billing increment for freelancers? 15 minutes is the most common and the best balance of precision and simplicity. 30 minutes works for consultants who work in longer blocks. Exact time is honest but produces messy invoices. Pick one, put it in your contract, and stick to it.
Should I track non-billable time? Yes. Create an internal project for admin, business development, and learning. You won't invoice it, but you need to know how much of your week is unpaid overhead to price your billable rate correctly. If you don't track it, you're guessing.
Do I need a time tracking app, or can I use a spreadsheet? A spreadsheet works for the first week. By week three, the manual reconciliation, stale rates, and gaps between what you tracked and what you invoiced start costing more time than the tracking saves. A tool that closes the loop — tracking, review, and invoicing in one place — is the point where tracking stops being a chore and starts being a workflow. See the best time tracking apps for Mac for options.
How often should I invoice? Weekly or biweekly. Monthly invoicing from memory is where billable hours disappear. The shorter the gap between doing the work and billing for it, the more accurate the invoice and the faster the payment.
What if a client wants me to use their time tracking system? Some enterprise clients do. In that case, track in your own tool for your own records, then export the time data into their portal. Your tool is the source of truth; their portal is a formatting exercise. You still need your own records for margin analysis and AI summaries.
Can I track billable hours on my phone? Yes. Ayron's iPhone app includes a voice timer — "log 45 minutes to Acme, design review" — so you can capture time in a client meeting without opening a laptop. Most Mac-native trackers have iOS companions; web-first tools generally don't.
Ayron details are based on its public landing page and should be treated as marketing claims rather than independent product verification.