Which rounding interval should freelancers use? The short answer: the one you document and apply consistently. Most freelancers who bill by the hour round to the nearest 6 minutes (one-tenth of an hour) or the nearest 15 minutes. The specific interval matters less than you think. What matters is that you pick one, write it down in your contract, and apply it to every entry the same way.
One inconsistent invoice can undo months of trust. This guide covers the standard conventions, how to choose one that fits your work, and how to document it so clients never need to ask.
Table of Contents
- What does "rounding time entries" mean?
- Why does rounding come up so often?
- What are the standard billing increments?
- 6-minute vs 15-minute: which is right for you?
- Should you always round up, or round to nearest?
- How do you document your rounding policy?
- What happens when rounding adds up to real money?
- Is exact-second tracking ever better than rounding?
- Common rounding mistakes freelancers make
- Expert tips for fair, defensible billing
- A real-world example
- Billing-fairness checklist
- Frequently asked questions
What does "rounding time entries" mean?
When you track work time, you rarely finish at a clean interval. You start a task at 10:07 and stop at 10:41. That is 34 minutes. Do you bill 30? 36? Or 34 minutes exactly?
Time rounding is the practice of adjusting raw tracked durations to the nearest predefined interval before adding them to an invoice. Instead of billing 34 minutes, you might bill 30 minutes (rounded to the nearest 15), 36 minutes (rounded up to the next 6-minute block), or 34 minutes with no rounding at all.
Every approach can be legitimate. None of them is inherently dishonest. What creates disputes is not the rounding itself but the absence of a written rule.
Why does rounding come up so often?
Two reasons.
First, most client contracts quote an hourly rate, not a per-minute rate. Billing "0.567 hours" at €125 produces an odd number on the invoice. Clean fractions like 0.5 or 0.75 read better and are easier for a client to verify without a calculator.
Second, timers are imperfect. Every time you switch tasks, reply to a message, or lose focus for a moment, your raw time log picks up small fragments: 3 minutes here, 7 minutes there. Individually, those fragments feel wrong to bill as separate line items. Rounding bundles them into something legible.
The problem is not rounding. The problem is rounding without a stated rule.
What are the standard billing increments?
Three intervals dominate professional freelancing:
| Increment | Fraction of hour | Who uses it most |
|---|---|---|
| 6 minutes | 0.1 hr | Lawyers, accountants, some consultants |
| 15 minutes | 0.25 hr | Developers, designers, most freelancers |
| 30 minutes | 0.5 hr | Project-based work, broad estimates |
6 minutes (one-tenth of an hour) is the legal industry standard. It is precise enough to feel fair to clients and produces clean decimals on invoices. A 22-minute task rounds to 0.4 hours instead of 0.367.
15 minutes (one-quarter of an hour) is the most common choice among independent contractors and small agencies. It is easy to explain ("I bill in quarter-hour increments"), easy for clients to audit, and widely understood by anyone who has hired freelancers before.
30 minutes is uncommon for hourly billing but appears in project-based or retainer work where both sides care more about milestones than minute counts. For task-by-task hourly billing, 30-minute rounding tends to generate the most disputes because the over- and under-billing swings are large.
Anything coarser than 30 minutes (rounding to the nearest hour, for example) tends to produce invoices that feel inflated, especially on short tasks.
6-minute vs 15-minute: which is right for you?
Here is a quick decision framework:
Use 6-minute increments if:
- Your clients come from legal, finance, or enterprise consulting. They expect it. Anything coarser will look unusual.
- You frequently do very short tasks (under 10 minutes each). Rounding five 8-minute tasks up to 15 minutes each turns 40 minutes of real work into over an hour of billed time. That will create disputes.
- You want fine-grained billing that lets clients see exactly where time went.
Use 15-minute increments if:
- Your clients are startups, agencies, or small businesses. Fifteen minutes is the expected standard, easy to explain, and far less likely to generate questions.
- You mostly do longer deep-work sessions of one to four hours. At that scale, the difference between 6-minute and 15-minute rounding is trivial, so choose the simpler one.
- You want billing terms that are fast to read and sign.
The math is worth running once. On a 35-entry week, a consistent 15-minute rounding policy shifts your total by roughly two to four hours compared to exact billing. At €125 per hour, that is €250 to €500 in either direction. Over 50 billing weeks, the compound effect is meaningful. Know what you are choosing.
Should you always round up, or round to nearest?
This question matters more than the interval you pick.
Round up always (ceiling rounding): every entry rounds to the next full increment. A 7-minute task becomes 15 minutes. A 16-minute task becomes 30 minutes. This approach is standard in legal billing and is accepted there because it is disclosed in the engagement letter before work begins.
Clients who have never worked with a law firm may find ceiling rounding aggressive if it was not explained upfront. Use it only when you state it clearly in the contract.
Round to nearest (neutral rounding): a 7-minute task rounds to 0 (not billed separately) or 15 depending on whether it crosses the halfway point. A 22-minute task rounds to 15; a 23-minute task rounds to 30. This is the most defensible approach for freelancers who want billing to feel comfortable rather than adversarial.
Round down (floor rounding): unusual in practice. You absorb every partial increment, which quietly depresses your effective hourly rate over time. Some very client-focused freelancers prefer it on high-value relationships, but it is not a sustainable default.
The fairest default for most freelancing relationships: round to nearest, with a minimum of 6 or 15 minutes per entry. You do not eat tiny tasks entirely, but you are not systematically over-billing either.
How do you document your rounding policy?
This step is the one most freelancers skip, and it is the direct cause of most billing disputes.
Three places to state your rounding rule:
In your contract or scope of work. One sentence is enough: "Time is tracked in 15-minute increments, rounded to the nearest increment." If you use ceiling rounding, say so explicitly: "All entries are rounded up to the next 15-minute block." Put it near the billing rate, not buried in a definitions appendix.
On your invoice. Add a line near the billing terms: "Hours billed in 15-minute increments." Clients scan invoices quickly. Putting the rule where the numbers live removes any suggestion that you are hiding it.
In your first invoice or welcome email. For new clients, a brief note is good practice: "Just so you know, I log time to the minute and then apply 15-minute rounding when I create invoices. If you ever want to see the raw log, I am happy to share it."
That last offer matters. A freelancer who is willing to share the underlying time log is far more credible than one who only presents rounded totals. Make the offer before it is requested.
What happens when rounding adds up to real money?
Here is a concrete scenario.
A freelance developer works 35 client tasks in a week, billing at €100 per hour. The raw time log shows exactly 21.8 hours. Here is what happens under each rounding policy:
| Policy | Billed hours | Invoice total |
|---|---|---|
| Exact time | 21.8 | €2,180 |
| Nearest 15 minutes | 22.0 | €2,200 |
| Ceiling 15 minutes | 23.25 | €2,325 |
| Nearest 6 minutes | 21.9 | €2,190 |
| Ceiling 6 minutes | 22.2 | €2,220 |
The swing between the most conservative and most aggressive policy is €145 on a single week. Over 48 billing weeks, that is nearly €7,000 in either direction from the same actual work. Choosing a rounding policy is not a minor administrative detail.
Notice that ceiling rounding at 15 minutes produced a 1.45-hour overage on 21.8 actual hours: a discrepancy of about 6.6%. That is inside what most clients accept when the rule is disclosed upfront. Undisclosed, it is a dispute waiting to happen.
Is exact-second tracking ever better than rounding?
Yes, for some freelancers.
If you work in short increments, handle many clients in a single day, or have clients who want detailed evidence for every hour, exact-time billing is increasingly common. Modern tracking tools can present raw minutes on invoices without looking odd.
The argument for exact tracking: it is the most defensible position available. You cannot be accused of padding if the invoice shows 1 hour 37 minutes and the time log confirms 1 hour 37 minutes.
The argument against: invoices with decimal fractions confuse some clients. "1.633 hours" at €125 is €204.17. "1 hour 40 minutes" (rounded to the nearest 5 minutes) at €125 is €208.33. The difference is €4.17. Most clients would prefer the round number, and some would be confused by the decimal.
Practical middle ground: use exact time in your tracking tool, then decide at invoice time. If the raw number looks clean (1 hour 15 minutes, 2 hours exactly), bill it as-is. If it reads oddly, apply your standard increment. Document this as your default so clients know to expect it.
Common rounding mistakes freelancers make
Switching policies mid-engagement. Rounding to nearest for most entries and then ceiling-rounding on a large entry because it feels "more fair that week" is the fastest way to lose trust. Consistency is the entire point of having a policy.
Not setting a minimum entry size. Without a minimum, you can end up billing 15 minutes for a 30-second Slack reply because the next rounded increment is 15. Set a practical floor: tasks under 2 minutes do not get billed separately unless they accumulate into a bundle.
Rounding before reviewing for idle time. If your tracker captured time while you stepped away from your desk, rounding that inflated number up makes a bad situation worse. Review and trim your log for idle time before applying any rounding. An honest raw number is the only valid starting point.
Applying rounding to the total instead of each entry. Rounding the weekly total is less accurate and harder to audit than rounding each entry individually. Round at the entry level, every time.
Keeping no underlying record. If a client disputes an entry, you need to show raw data. "I billed 0.75 hours because I rounded 41 minutes to the nearest 15" is convincing. "I billed 0.75 hours and do not have the underlying log" is not.
Expert tips for fair, defensible billing
Start with an accurate log. Rounding is only as fair as the number you start with. A time log that includes hours reconstructed from memory, or idle time you forgot to remove, will produce a biased result no matter what rounding rule you apply. The baseline must be honest first.
Time-stamp everything. Your rounding policy is much easier to defend when the invoice line shows start and end times, not just a duration. "10:07 to 10:41, 34 min, billed 30 min (nearest 15)" is bulletproof.
Use one tool consistently. Switching between a stopwatch, a spreadsheet, and a browser extension means your raw data comes from three different systems with three different precision levels. Pick one tracker and stay with it.
Keep your rate and rounding in the same sentence in your contract. "My rate is €100 per hour, billed in 15-minute increments" is more credible than a rate in clause 2 and a rounding policy buried in an appendix.
Review your log before you invoice, not after. Catch idle time, duplicates, and misfiled entries when you can still fix them cleanly. Correcting a sent invoice is awkward. Catching an error before you send it is professional.
A real-world example
A freelance web designer takes on a six-week redesign project billed hourly. She bills in 15-minute increments, rounded to nearest, which she states in her contract. She uses an automatic tracker that logs every browser session while her timer runs, giving her a domain-level record of what she worked on: Figma, the client's staging site, relevant documentation.
On week three, the client emails to question an 8-hour invoice that feels high. She exports the week's time log, shares it, and walks them through the 15-minute rounding. Two entries draw attention: a 42-minute design session (billed as 45) and a 6-minute client email (billed as 15, the minimum). She explains both in one short reply.
The client accepts the explanation immediately. The evidence is there: domain-level activity matching each task, start and end timestamps, and the same rounding rule applied throughout. The invoice stands, unchanged.
This is the outcome of tracking accurately first and rounding transparently second.
Billing-fairness checklist
Before you send your next invoice, check every item:
- My rounding policy (interval and direction) is written into my contract
- The same rounding rule appears on my invoice or in my billing terms
- I applied the same rule to every entry on this invoice
- I reviewed the log for idle time before rounding
- I have raw time data (start time, end time, duration) to share if a client asks
- No entry was rounded up more than one full increment from its actual duration
- I can explain every line item from memory or from the log
If every box is checked, the invoice is defensible. If any box is empty, fix it before you send.
Frequently asked questions
What is the most common rounding interval for freelancers? Fifteen-minute increments are the most widely used standard for independent contractors and small agencies. Six-minute increments are common in legal and professional services. Either is appropriate as long as it is disclosed to the client before work begins.
Is rounding billable hours up considered dishonest? No, as long as you disclose the policy. Ceiling rounding (always rounding up to the next increment) is standard practice in legal billing and is accepted by clients who have been told about it upfront. Undisclosed ceiling rounding on large tasks is where disputes start.
How do I handle tasks shorter than my minimum billing increment? Group small tasks together. A common approach: tasks under your minimum increment are bundled under a category like "email and communication" and the bundle is rounded once at the entry level. Do not apply rounding to individual seconds and then round the bundle again.
Can I change my rounding policy mid-project? Only with the client's explicit, written agreement. Changing a billing convention mid-engagement, even to something more favorable to the client, should be communicated clearly. Undisclosed changes create confusion even when the intent is good.
What does a time tracker need to provide so rounding is fair? Accurate start and end timestamps at the task level, so you can round each entry individually and show your work. A log that only shows rounded totals cannot be audited after the fact. Look for a tool that gives you raw duration before any rounding is applied.
Do I need to round at all? No. Exact-time billing is increasingly common and is the most transparent option available. If your tracking tool logs to the minute and your clients are comfortable reading decimal hours, exact billing removes the rounding question entirely. The tradeoff is that some clients find decimal fractions harder to read than clean quarter-hours.
Conclusion
Rounding is not the problem. Inconsistency is.
Pick one interval: 6 minutes if you work in fine-grained segments or with professional-services clients, 15 minutes if you do longer deep-work sessions with agency or startup clients. Pick one direction: nearest for most freelancers, ceiling only when you disclose it clearly and your client's industry expects it. Apply that same rule to every entry, and write it into your contract before the first invoice goes out.
The freelancers who never get billing disputes are not the ones who bill the fewest hours. They are the ones who can show exactly where each number came from. A consistent rounding policy, grounded in an accurate underlying log, is the simplest way to become one of them.
If you want the most defensible baseline before you apply any rounding, start with a tracker that captures your work automatically and to the second. TimeRecord logs your active sessions and the root domains you visited while the timer ran, so you always have evidence behind each entry, and idle detection means you are not rounding inflated numbers to begin with. The free tier needs no credit card.