Time Tracking Questions Freelancers Always Ask, Answered

After years of freelancing, you'd think the time tracking thing would be simple. Start a timer, stop a timer, send invoice. Done. But it's never that clean, is it? There's always a weird edge case — that 12-minute email thread, the client revision that turned into a two-hour rabbit hole, the discovery call you forgot to log. Every freelancer I've talked to has a small pile of unspoken questions about how this all actually works. Here are the real ones, answered honestly.

Do I actually need to track time if I charge flat rates?

Yes — but not for billing. The purpose shifts.

When you charge a flat rate, you're essentially making a bet: "I think this project will take X hours, and Y dollars covers my time at a rate I'm okay with." If you never track, you have no idea whether that bet was right or wrong. You might be charging $800 for a project that consistently takes 24 hours of your actual working time. That's $33/hour. Not ideal.

Track your hours internally even on flat-rate work. Most freelancers who do this discover within two or three projects that they're systematically underquoting one type of work — usually the discovery and revision phases. You can't fix a pattern you can't see.

There's a secondary benefit: when a client asks "why does this cost so much?" you can pull up your actual tracked data and walk them through it. That's a much stronger conversation than trying to justify a number from instinct.

Should I bill for every little email and Slack message?

This is the most argued-about question in every freelance forum, and the answer depends on your contract and your relationship with the client.

Here's the practical reality: if you bill hourly, those five-minute check-ins add up. Twenty Slack messages per week at three minutes each is an hour of work you just absorbed silently. Over a month, that's four to five hours. At $100/hour, you've quietly gifted the client $400-500.

The cleanest approach: create a communication structure upfront. Some freelancers build a small retainer buffer into project estimates specifically for async communication. Others set a policy — something like "up to 30 minutes/week of async back-and-forth is included; beyond that is billed." Whatever you choose, write it in the contract before work starts. The worst version of this conversation happens after the project, when you're trying to retroactively charge for something the client thought was free.

On the pure mechanics: I log communication time in 15-minute blocks. If an email thread takes 8 minutes, I log 15. If it spirals into 22 minutes, I log 30. This isn't cheating — it accounts for context-switching cost, which is real and measurable.

What's the right rounding rule?

There's no universal standard, but the most common practices are rounding to the nearest 6-minute increment (1/10th of an hour, popular in legal and consulting fields), 15-minute increments, or just tracking actual minutes.

My honest opinion: round to the nearest 15 minutes for most freelance work. It's simple, clients understand it, and the rounding error averages out over time. If you worked 23 minutes, you log 30. If you worked 37 minutes, you log 45.

The one rule I'd push back on: always rounding down. Some freelancers do this out of anxiety — they feel guilty charging for a partial segment. Don't. You spent that time. The work happened. Rounding down consistently is just self-imposed income reduction dressed up as generosity. Round to the nearest increment, not always to the lower one.

If a client ever challenges your rounding, you should be able to show your raw time entries and explain your rounding policy. That's it. It's a standard practice and a reasonable one.

What do I do about time I can't remember logging?

Reconstruct it. Don't guess wildly, but don't throw it away either.

Look at your calendar, email timestamps, Slack history, file modification dates, browser history if you need it. Most of the actual evidence of your work is somewhere — you just have to piece it together. If you spent 90 minutes working on a design file, that file has a "last modified" timestamp. That's a data point.

Log reconstructed time with an honest note in your time tracking tool: "reconstructed from file history, approx. 90 min." Most clients will never see those internal notes, but if there's ever a dispute, you can explain your methodology. That's very different from making up a number.

Going forward: get into the habit of logging within 24 hours at the absolute latest. Every day you wait, you lose about 40% of your recall granularity. After three days, you're basically guessing. Daily end-of-day logging takes five minutes and saves a lot of reconstruction headaches.

What's the best time tracking tool for freelancers?

The honest answer is: the one you'll actually use.

That said, here's what actually matters when choosing:

• Friction: If starting a timer requires more than two clicks, you'll skip it when you're in flow. Tools like Toggl Track and Clockify both have browser extensions and mobile apps that get you to zero with one click. That matters more than feature lists.
• Project/client tagging: You need to be able to separate time by client and by project type. Without this, your reports are useless for understanding your own work patterns.
• Invoice integration: Some tools (Harvest, FreshBooks time tracking) pipe directly into invoicing. If you're spending 20 minutes per invoice manually transferring time entries, that's time you should be automating.
• Idle detection: A timer that stops when your computer goes idle and asks what to do with that time is genuinely useful. It catches the "I forgot to stop the timer when I took a 40-minute break" problem.

For pure time tracking, Toggl Track's free tier is hard to beat. For an all-in-one freelance operations tool, Harvest earns its $12/month if you also need invoicing and client-facing reporting.

Can I charge a client for time I spent fixing my own mistake?

Generally: no. If you made an error in your work and you're correcting it, that correction time is on you. Charging a client for fixing something you got wrong damages trust fast, and it should — they hired you for a deliverable, not a process.

There's nuance here though. A mistake because of unclear or changing client requirements? Different story. If the client sent you one brief, you built accordingly, and then they said "oh actually we meant something different" — that's a revision, not a bug fix, and revisions are billable depending on your contract terms.

Scope creep and mistake fixing are two different categories. Get clear on which one you're dealing with before you decide whether to log the time as billable.

How do I handle deep work vs. shallow work in my logs?

This is an underrated question. Two hours of focused writing and two hours of sitting in a client's Zoom meetings are both "two hours" on a timesheet, but they don't feel equivalent — because they're not.

For your own insight, consider tagging entries by work type, not just by project. Something simple: Deep (focused creation), Meetings, Admin, Research. Over time you'll see that your most billable, highest-leverage hours are deep work hours, and you might be bleeding more time to meetings and admin than you realized.

This also helps when you're pricing projects. If a client's project is meeting-heavy by nature (lots of syncs, feedback rounds, stakeholder check-ins), your estimate should reflect that. Meeting-heavy work pays differently than deep execution work because it costs you differently.

Should I show clients my raw time logs?

Only if your contract specifies it or if you offer it as a trust-building feature — and only after you've cleaned them up.

Raw logs have internal notes, accidental timer starts, reconstructed entries with asterisks. A client doesn't need to see all of that. What they need to see is a clear breakdown: date, task description, duration, total. Clean, summarized, professional.

Some clients explicitly want detailed time logs, especially agencies and enterprise clients used to hourly billing. If that's the case, factor in the admin time to produce clean reports and either include it in your rate or add a small reporting line item. "Reporting and admin: 0.5 hrs/week" is a completely legitimate entry.

Time tracking is one of those freelance skills that seems administrative but is actually strategic. The way you log, round, communicate, and analyze your time shapes your earnings, your pricing accuracy, and how much you can scale without burning out. Start treating it like the business tool it is, not just a chore you do before sending invoices.