Time Management
How to Explain 6-Minute Time Rounding to Clients Without Sounding Like You’re Padding
6-minute time rounding is a billing language, not a magic trick. Freelancers who cannot explain it end up either donating minutes or sounding like they inflated the week.
The awkward moment is familiar. You send a report that says 0.2 hours for a twelve-minute Slack huddle, or 0.3 hours for a thirteen-minute hotfix. A conscientious client asks why the numbers do not match the clock on their phone. If your only answer is “that’s just how the tool works,” you have already lost the conversation.
Say this first: rounding is an agreed increment, like a minimum line item. The original minutes still exist. You are not hiding a second timesheet. You are translating messy real work into a unit both of you can multiply by a rate.
This is a time-tracking post for consultants and independent contractors. You can run the conversation in any honest tracker. The last section is how to keep the increment visible so Friday does not become a debate.
Why 0.1 hours exists in the first place
Six minutes is one-tenth of an hour. Lawyers, accountants, and a lot of professional-services shops standardized on that increment because to-the-second invoices are unreadable, and to-the-hour invoices are unfair. 0.1 is small enough that a real task still shows up. It is large enough that you are not arguing about fifty-three seconds of “thinking.”
Clients already understand increments in other industries. Parking is sold in blocks. Contractors bill half-days. Your increment is just smaller, because knowledge work arrives in twelve-minute fragments.
What clients do not understand — until you say it — is the direction. Rounding up is the usual professional-services convention: a 10-minute call becomes 12 minutes (0.2h at a 6-minute increment). A 13-minute fix becomes 18 minutes (0.3h). If you never name the direction, the client fills the silence with “padding.”
What you are actually selling when you round
You are not selling extra minutes. You are selling a clean unit plus the overhead that never fits a stopwatch: unlocking the laptop, finding the ticket, writing the two-sentence recap, switching back to the next client. Those crumbs are real. They are also why “I only bill exact elapsed” quietly underprices the week.
The increment is a policy. The original duration is evidence. Keep both. If a client ever wants to see how a 0.3 landed on the page, you should be able to open the raw minutes without reconstructing the day from memory.
A 6-minute rounding pocket card
- 1–6 minutes → 0.1h
- 7–12 minutes → 0.2h (10 minutes becomes 12)
- 13–18 minutes → 0.3h (13 minutes becomes 18)
- 54–60 minutes → 1.0h
Fifteen- and thirty-minute increments exist too. They are easier to explain and harsher on a client who hired you for lots of small pokes. If your work is mostly workshops and half-day blocks, a coarser increment may be honest. If your work is interrupt-driven support, six minutes is usually the increment that still looks like the real week.
Put the increment in the engagement, not in the invoice footnote
The worst time to explain rounding is after the PDF is sent. The best time is the same paragraph where you name the rate. One or two sentences is enough:
“Time is billed in 6-minute (0.1 hour) increments, rounded up. You will see both the time I actually spent and the billable increment on reports.”
That sentence does three jobs. It names the unit. It names the direction. It promises visibility. You can still choose not to bill a particular poke — courtesy writes to zero are a relationship decision, not a rounding decision. Do not use “I rounded” as a cover for “I decided this was free.” Those are different conversations.
If the client’s own procurement policy says tenths, you are aligning with them. If they have never thought about increments, walk one example on a kickoff call: “A ten-minute review becomes 0.2. A fifty-five-minute working session becomes 1.0, not 0.9-and-change.” People relax when they can predict the math.
Scripts for the three questions you will actually get
“Did you add time I didn’t use?”
“No. I recorded the real duration. The invoice uses a 6-minute increment so line items stay in tenths of an hour. A ten-minute call is 0.2, not 0.17. The raw minutes are still in the report if you want them.”
“Why not bill exact minutes?”
“Exact minutes turn the invoice into a spreadsheet argument. Tenths let us review the week by task without reconstructing every start and stop. If a week is mostly long blocks, the increment barely moves the total. If a week is twenty small pokes, the increment is how those pokes stay visible instead of disappearing.”
“Can we use a different increment?”
Yes — if you agree before the work starts. Some retainers prefer 15 minutes because the client thinks in quarter-hours. Some fixed-price projects should not invoice increments at all; they should track actuals internally so you know whether the price was sane. Do not change the increment mid-month because one line looked ugly. Change the policy, then apply it to the next period.
What to stop doing
- Rounding in your head and typing the rounded number as if it were elapsed. You just destroyed the audit trail. When the client asks, you have nothing to show but a shrug.
- Mixing increments across clients without saying so. One client on tenths and one on quarters is fine. Surprise is not.
- Using a coarse increment to paper over bad estimates. Rounding does not fix a project that is underwater. It only chooses the unit you report in.
- Hiding the increment in a footer no one reads. If it affects money, it belongs next to the rate.
If you already run a weekly close, this is a two-minute add-on: glance at billable vs original totals before you generate the invoice. A week where those two numbers diverge a lot is a week of many small entries — worth a sentence in the email, not a defensive novel. The reports worth running every week are more useful when the increment is boring and declared.
How MinuteShark keeps both clocks honest
When you are ready to stop doing the increment in a notebook, use a tracker that stores the original duration and shows the rounded value as billable — not one that overwrites history.
In MinuteShark, time rounding is off by default. An admin turns it on and picks 6 minutes (0.1h), 15, 30, or a custom interval. It always rounds up. A 10-minute entry becomes 12; a 13-minute entry becomes 18. History can show a BILLABLE badge when rounding is on. Reports carry a grand total and a rounded billable total. Invoices generated from a report inherit that billable math, including named tax lines if you need them. The original minutes stay stored.
The setup lives next to rates, not buried in a dark pattern. Start with the time rounding guide, then the billable rates and reports guides when you are ready to turn a week into a PDF. That is the whole trick: the client conversation is a policy. The software should make the policy visible instead of improvising it on Friday.