Idle time is the timer that kept running while you made coffee, answered a personal message, or zoned out after a long morning. It is the 12 minutes between finishing one task and focusing on the next. It is the 45-minute research rabbit hole that may or may not belong on this client's bill.
For most freelancers, idle time is invisible. It just becomes "hours worked." And that is a problem, because when a client eventually questions your invoice, idle time is exactly what they are looking at.
This guide gives you a practical framework for handling idle time: what to bill, what to discard, and how to set up your tools so the answer is automatic rather than a weekly guess.
Table of Contents
- What is idle time in freelancing?
- Why freelancers accidentally over-bill idle time
- What counts as billable idle time and what does not?
- How does idle detection work, and why should you use it?
- How do you handle the grey areas?
- How should freelancers round time entries fairly?
- How do you switch tasks without messing up your time log?
- What should you check before sending an invoice?
- What are the most common idle time billing mistakes?
- Expert tips: treat your time log as your professional record
- Case study: the 40-hour week that was not
- FAQ
- Conclusion
What is idle time in freelancing?
Idle time is any period when your work timer is running but you are not actively working on the task you billed it to. That definition sounds simple. What is not simple is identifying it inside a real workday.
Here are some examples:
- You start a timer for "client A / website redesign" and then spend 20 minutes answering emails for a different client.
- You hit start, make a coffee, check your phone, and sit back down 15 minutes later.
- You finish writing one section and sit staring at your screen, thinking about something unrelated to the project.
- You are waiting for a large file to render. The process takes 8 minutes and you scroll social media while it runs.
In all four cases, your timer says you were working. Your client will see those minutes on the invoice. Whether they should is a different question.
The working definition for billing purposes: idle time is any stretch you cannot honestly connect to productive effort on the task at hand. That is the test. Not whether you were physically at your desk. Whether you were doing client work.
Why freelancers accidentally over-bill idle time
Over-billing idle time is almost never intentional. It happens for a handful of predictable reasons.
Forgetting to stop the timer. You wrap up a task, get pulled into something else, and realize two hours later that the timer is still running. The extra time ends up in the log and later on the invoice.
Assuming "computer on equals work happening." If your time tracker just runs all day, it cannot distinguish a focused coding session from a 30-minute unrelated detour. You are trusting your future self to manually clean up the log, and future-self rarely does.
Reconstructing time from memory. When you fill in a timesheet at the end of the day or week rather than tracking in real time, you round up without realizing it. Research on professional services billing consistently shows that memory-based time records run above actual time spent. You do not intend to inflate your hours. You simply cannot remember what you forgot.
No review habit. Even with a decent tracker, if you never look at the log before invoicing, the idle time ships with the invoice untouched.
None of these are character failures. They are workflow failures. And they are all fixable.
What counts as billable idle time and what does not?
Not all idle time is equal. A simple spectrum makes the distinction clearer.
Clearly billable
- A build takes 6 minutes to compile. You are waiting for the output before you can continue. You are on the client's time.
- You are waiting for a client response that blocks your next step. You stay at your desk, available, ready to pick up the moment they reply.
- You need to think through a design problem. You step away from the keyboard to pace and think, then return to implement the solution. That thinking was part of the work.
Grey area (requires judgment)
- A short break of under 5 minutes taken mid-task. Most clients would find this reasonable, as long as it does not happen every 15 minutes.
- A research thread that started as a task requirement and drifted into curiosity. If it genuinely informed the work, it is arguable. If you ended up where you were going anyway, trim the excess.
- A client call that runs longer than expected. Client communication is generally billable, but it is better to set expectations upfront when calls are likely to be substantial.
Clearly not billable
- Personal breaks: coffee, bathroom, personal calls, social media.
- Time spent on another client's work while this client's timer runs.
- Business admin for your own practice: invoicing, marketing, bookkeeping, unless your contract explicitly includes it.
- The gap between "done with work" and "remembered to stop the clock." That time is yours to absorb.
The test for any unclear case: If my client could see a screen recording of exactly how I spent this time, would they consider it fair to pay for it? If yes, keep it. If you hesitate, discard it.
That test also works in your favor. If you can honestly answer "yes, that was client work," your invoice is defensible. If you cannot, the few minutes you save by keeping the time are not worth the trust you risk.
How does idle detection work, and why should you use it?
Idle detection is the single most practical tool for keeping a time log honest without requiring constant attention.
Here is how it works: the time tracker monitors for activity, typically keyboard input, mouse movement, or screen changes. When no activity is detected for a configurable window, the tracker flags you as idle. When you return and activity resumes, the tool presents a prompt: keep the idle time, discard it, or split the entry at the point you stepped away.
This single prompt catches the most common form of accidental over-billing: forgetting to stop the timer.
Most trackers offer a configurable idle threshold. A common default is somewhere between 5 and 15 minutes. If you frequently take short reflective breaks as part of your focus routine, a longer threshold suits you better. If you tend to drift for extended periods, a tighter threshold catches more.
The critical benefit: idle detection moves the decision to the right moment. You are not reconstructing from memory at invoice time. You are making a real-time call about a specific, fresh gap in activity, with the facts in front of you.
TimeRecord uses an 8-minute idle default and shows a keep/discard prompt when you return from a gap. This prevents idle periods from silently accumulating in your log. Pro users can adjust the threshold from 1 to 60 minutes to match their individual work rhythm. The extension runs in the background and captures the root domains of sites you visited while your timer ran, giving you a concrete activity record alongside the time entries to review before invoicing.
How do you handle the grey areas?
The spectrum above covers the clear cases. The grey areas are where freelancers lose the most client trust, and where judgment matters most.
Research rabbit holes
You are investigating a technical problem for a client. You open six browser tabs. You follow a thread from a GitHub issue to a forum post to a blog about something adjacent. An hour later, you have learned a lot but are not sure how much of it directly served the client.
A practical approach: ask whether the final direction of your work changed because of what you found. If it did, the research was billable. If you ended up where you were going anyway, or the exploration was mostly curiosity, trim the excess.
For long research sessions, a reasonable professional standard is to log the time you actually spent researching, but cap the billed amount at what a competent professional would have spent reaching the same conclusion. This is common practice in consulting and legal billing and protects both parties.
Meetings and client calls
Client calls are billable. This includes preparation time (reviewing notes, pulling up the project brief) and a reasonable wrap-up period (sending a follow-up summary, updating your task list with action items).
What is not billable: chit-chat you let run long out of politeness, or attending a meeting that had nothing to do with your deliverable.
Practical tip: start a dedicated timer when a call begins and stop it when you hang up. Do not rely on your project timer to capture call time accurately, especially if you started the project timer earlier in the day.
Waiting for processes
Waiting for a build, a file export, a test suite, or a deploy is generally billable if you are waiting on the output to continue your work and you remain available and attentive during the wait.
It becomes grey if the wait is long and you fill it with personal activity. A practical rule: if you are monitoring progress and ready to act on the result, bill the time. If you wander off and come back 40 minutes later to check if it finished, consider logging only the time you were genuinely engaged.
Short breaks
A 2 to 5 minute break during an active work session is a normal part of a productive day and acceptable on most professional invoices. Longer personal breaks belong to you. If your contract specifies a portal-to-portal or flat daily rate, follow the contract terms regardless.
When in doubt, trim. A client who receives a concise, accurate invoice trusts you more than one who gets a large number they begin to question.
How should freelancers round time entries fairly?
Rounding is separate from idle time but compounds the same trust problem when handled carelessly.
The standard for professional hourly billing: round to the nearest 6-minute increment (one-tenth of an hour). Legal, consulting, and accounting professions have used this convention for decades because it is granular enough to stay accurate and rounded enough to be practical for invoicing.
Some freelancers round to 15-minute increments. This is coarser but widely understood. If you use 15-minute rounding, apply it symmetrically: sometimes in the client's favor, sometimes in yours. Consistently rounding up erodes trust when a client notices the pattern.
The golden rule of rounding: whatever increment you choose, apply it consistently and disclose it. "I bill in 15-minute increments" stated in your contract is a professional norm. Silently rounding every 8-minute entry to 15 minutes is not.
Automatic time tracking with idle detection largely reduces the need for heavy rounding, because your log is already accurate to the minute. A modest round to the nearest 6 minutes from a precise, activity-verified record is reasonable. Rounding a rough memory-based estimate is where significant inflation tends to occur.
How do you switch tasks without messing up your time log?
A common source of "idle time" in the log is not idle time at all. It is the transition gap between tasks.
You finish a deliverable. You spend a few minutes checking what comes next, opening a new ticket, reviewing a spec file. Then you start the next task. Those transition minutes either land in the wrong place or disappear entirely.
If your tracker requires you to stop the current timer before starting a new one, that gap gets lost or accidentally tagged to the task you just closed.
Quick Switch is the workflow solution. Instead of stopping one timer and starting another, you change the active task directly and the old task closes at the exact moment the new one begins. No idle window. No gap. No time attributed to the wrong project.
TimeRecord has Quick Switch built into the browser extension. You open the popup, select the next task, and the handoff is seamless. The previous Client, Project, and Task closes with a clean timestamp, and the new one opens immediately. Your log shows exactly what you worked on and when, with no gaps to explain.
If your tracker does not support Quick Switch, the next best option is to stop the timer, make a note of the transition time, and immediately start the new one. The 2-minute manual gap is better than a silent accumulation of misbilled transition time.
What should you check before sending an invoice?
Before sending any invoice based on tracked hours, spend 10 minutes reviewing the log. This habit prevents disputes before they happen.
The pre-invoice checklist:
- Review every time entry for the billing period.
- Flag any entry longer than 3 hours without a visible gap. Did you actually work that stretch? If yes, note it. If not, adjust.
- Check entries that cross time boundaries or span unusual hours. Were you genuinely working during that window?
- Remove any entries from days you were not working (sick days, holidays, travel days).
- Verify every entry is attached to the correct Client, Project, and Task.
- Look for any entries that were tagged to this client but belong to a different project.
- After review: does the total reflect what you actually delivered, not just what the raw clock says?
This takes 10 minutes and it will save you from the "are you sure it was really 40 hours?" conversation.
TimeRecord's time log lets you filter entries by date range, client, and project, and it shows the root domains visited during each timer session alongside the entry. That domain list is your best reference for what you were actually doing. If the log shows your client's codebase, their project management tool, and technical documentation, that session holds up. If it shows a streaming site and social platforms, you know what needs trimming.
What are the most common idle time billing mistakes?
Running one timer for the entire day. This is the root cause of most idle time problems. A single timer from 9 AM to 6 PM captures everything: focused work, personal breaks, side tasks, distractions. The log looks like a full day of client work. Review it carefully and the reality is different. Fix: start and stop timers per task, or use a tracker with automatic idle detection.
Skipping the pre-invoice review. The time you spent tracking is only half the job. A raw log is raw data. An invoiced log should be reviewed data.
Setting the idle threshold too high. An idle threshold of 60 minutes means a 45-minute distraction session will never get flagged. Match the threshold to your actual work rhythm, not the rhythm you wish you had.
Logging entries without descriptions. Time entries without notes are hard to audit and hard to defend. Even a brief label like "refactored auth module" or "client call re: homepage direction" makes the log reviewable and credible.
Rounding every entry upward. If every 22-minute entry becomes 30 minutes, the inflation accumulates quickly over a month. Clients who look at multiple invoices notice patterns. Round symmetrically.
Billing for learning you should have already had. If a client is paying you to do web development, the time you spend learning a fundamental skill you should have brought to the project is typically yours. Time spent on client-specific technical challenges is theirs. The line is not always obvious, but the question worth asking is: "Is this something I should already know at the rate I charge?"
Expert tips: treat your time log as your professional record
The most experienced freelancers treat their time log the way lawyers treat billing records: as a contemporaneous professional document. Every entry is made close in time to the work, with a descriptive note, and reviewed before it leaves the practice.
That discipline has a secondary benefit beyond accurate invoices. It turns your log into evidence. If a client disputes an invoice, you are not arguing from memory. You have a timestamped, activity-supported record with enough detail to stand up to questions.
Specific tips from seasoned hourly billers:
- Log as you go, not at the end of the day. Memory degrades quickly for granular time decisions.
- Write at least a 3-word description for every entry. "Writing, section 2" is enough. Blank is not.
- Set a consistent idle threshold and leave it there. Changing it frequently creates inconsistency that is hard to explain if questioned.
- Review your log every Friday, not only at invoice time. Catching a bad week takes 10 minutes. Catching a bad month is harder.
- If you find an entry you cannot explain, trim it. The conservative edit is always more defensible than the optimistic one.
Case study: the 40-hour week that was not
Consider this scenario: a freelance developer wraps up a month's work and runs a review before invoicing. The raw log says 44 hours. But on review, 4 hours do not hold up: an afternoon flagged as "deep work" where the activity log shows mostly personal browsing, and an hour that should have been tagged to a different client's project.
The developer trims the log to 40 hours and invoices accordingly.
Here is what changed by doing that:
First, the invoice represents work they can defend in detail. If the client asks about any specific session, the answer is clear and documented.
Second, the next time the client asks "how long did that feature take?", the developer can say "about 3 hours" and mean it, because the log is clean.
Third, when the client renews the engagement the following month, they do so trusting that the hours are real. That trust is worth more over the lifetime of the relationship than the 4 hours on one invoice.
Now consider the alternative: invoice the raw 44 hours. The immediate payment is marginally higher. But when the client notices a pattern of high hour counts and starts asking questions, the honest answer would be "well, some of those might not be accurate." That is not a position any freelancer wants to defend.
Honest billing is not generosity. It is a long-term business practice.
FAQ
Should I bill for short breaks and bio breaks?
Short breaks of 2 to 5 minutes taken during an active work session are a normal part of any workday and most clients consider them reasonable. If a session runs for 90 minutes and you take one 3-minute break, keeping that time is not over-billing. Longer personal breaks, or frequent short breaks that collectively add up to a significant portion of the logged time, should be trimmed.
What should I do if I forget to stop my timer?
Trim the entry. Find the approximate time you actually stopped working and adjust the end time accordingly. If you are not certain when you stopped, the conservative approach is to trim to the last activity you can reasonably attribute to the task. A time tracker that shows activity data (like which websites were open during the session) makes this easier to reconstruct.
How do I explain idle time adjustments if a client asks?
You usually do not need to explain them, because your invoice should reflect the final reviewed total, not the raw log. If a client asks how you arrive at your hours, you can simply say that you track automatically and review before invoicing to remove idle periods. That is actually reassuring to clients. It shows them that your billing has a quality check, not just a running clock.
Is research time always billable?
Research that is directly necessary for the client's deliverable is billable. Research that is primarily for your own professional development, even if it happens during work hours, is generally not. The practical test: did this research change what you delivered to the client, or improve the quality of it in a way they specifically benefit from? If yes, bill it. If no, or if it is mostly background knowledge you are building for yourself, absorb it as part of your professional overhead.
What idle detection threshold should I set?
A threshold between 5 and 15 minutes works for most freelancers. If you take regular reflective breaks as part of a focus technique (stepping away to think through a problem), 10 to 15 minutes is more appropriate so legitimate thinking time does not get flagged. If you tend to drift into longer unproductive stretches, a tighter 5-minute setting catches more of that. The right threshold is the one that flags meaningful idle time without treating every micro-break as a billing problem.
Should I bill for client admin work like project onboarding or invoice management?
Generally no. Client admin, project setup, invoicing, and contract management are considered overhead and are typically absorbed into your rate rather than billed separately. If you expect to spend significant time on onboarding or ongoing admin for a specific client, the cleaner approach is to factor it into your rate upfront or agree in writing that it is billable. Billing for admin without prior agreement is one of the most common sources of invoice disputes.
Conclusion
Honest billing is not about billing less. It is about billing for what you actually did.
Freelancers with the fewest invoice disputes are not the ones who track the least time or the most. They are the ones who track accurately, review before invoicing, and can point to a specific, defensible record for every hour they charge.
That discipline starts with understanding idle time: what it is, why it accumulates, and how to handle the cases where the answer is not obvious. Set up idle detection so the obvious errors get caught automatically. Build a short pre-invoice review into your month-end workflow. Apply a consistent rounding standard and hold to it. When you are genuinely unsure whether a stretch of time was really client work, apply the screen-recording test: if you would be comfortable showing the client exactly how you spent those minutes, keep them. If not, discard them.
That is not just ethical billing. It is good business, repeated over time, with clients who come back.
If you want automatic idle detection with a keep/discard prompt built into your browser, TimeRecord is worth trying. The extension runs in the background, captures the root domains of sites you visited while your timer ran, and flags idle periods for review so your log arrives at invoice time already cleaned. Free to start, no card required.