Guide
Timesheet rounding means adjusting recorded work time to a fixed increment, such as 6 minutes (0.1 hour) or 15 minutes, by rounding to the nearest unit, up or down. Keep raw times and round once, when you report. Timing lists report rounding on Mac. Harvest, Toggl and Clockify capture timer minutes for billing. Dayflow keeps a visual record of the day to check entries against.
Timesheet rounding means adjusting recorded work time to a fixed unit, such as 6 or 15 minutes, before it goes on a timesheet, report or invoice. A rounding rule sets the unit, the direction you round and the stage at which you round.
Most people get it wrong because they treat it as one setting. It is really three decisions. The third one, where in the process you apply the rule, often changes the final number more than the increment does.
A note before we start: this guide is published by Dayflow, and our app is one of the tools in the table near the end. Nothing here is legal advice. If you round hours for employees, the rules depend on where you work.
Suppose your timer says you spent 1 hour and 23 minutes on a task. Few invoices or payroll systems want “1:23”. They want a decimal like 1.4 or a quarter-hour figure like 1.5. Rounding is the rule that turns one into the other.
A complete rounding rule answers three questions:
Many policies add a fourth element that is not rounding at all: a minimum charge, such as “any phone call is billed as at least 15 minutes.” It often gets bundled into the rounding rule, but it behaves differently, as the next section shows.
The rule only works if the raw minutes are accurate to begin with. Rounding takes a number and makes it tidier. It cannot fix a number that was wrong in the first place.
These four practices get lumped together, and people mix them up in both directions. Some freelancers think any rounding is padding. Some managers think a minimum charge is just rounding.
| Practice | What it does | Tied to real minutes? | Normally disclosed? |
|---|---|---|---|
| Rounding | Converts recorded minutes to a fixed unit by a stated rule | Yes | Yes, in a policy or contract |
| Padding | Adds time that was not worked | No | No, which is the problem |
| Minimum charge | Sets a floor per task or interaction | Partly | Yes, in engagement terms |
| Estimating | Fills in time from memory after the fact | Loosely | Rarely |
Rounding vs padding. Rounding follows a rule anyone can check against the raw record. Padding has no rule. If a reviewer can take your raw times, apply your stated policy and get your invoice total, you are rounding.
Rounding vs minimum charges. A minimum charge sets a floor per item. A two-minute call billed at a 15-minute minimum goes up by 13 minutes regardless of the rounding direction. Keep the two rules separate in your policy so each can be explained on its own.
Rounding vs estimating. This is the quiet one. If you write “about 2 hours” at the end of the day and then round it to 2.0, the rounding is accurate and the input is a guess. A clean decimal makes a guess look more precise than it is.
Start with the increment. Each common one has a typical home:
Next, the direction. Rounding to the nearest increment pushes some entries up and some down, so the errors tend to cancel over a week. Rounding up always adds time. Rounding down always removes it. Ties, such as exactly 3 minutes on a 6-minute rule, need their own line in the policy. “Ties round up” is the usual choice.
Here is how rounding up to tenths of an hour works, since it is the most common billing convention:
| Minutes worked | Billed (rounded up to 0.1 hour) |
|---|---|
| 1-6 | 0.1 |
| 7-12 | 0.2 |
| 13-18 | 0.3 |
| 19-24 | 0.4 |
| 25-30 | 0.5 |
| 31-36 | 0.6 |
| 37-42 | 0.7 |
| 43-48 | 0.8 |
| 49-54 | 0.9 |
| 55-60 | 1.0 |
Finally, the scope. Per-entry rounding applies the rule to each line on the timesheet. Per-day rounding totals the day first and then rounds. Per-period rounding totals the whole invoice or pay period and rounds once.
The finer the scope, the more the increment matters. A 15-minute round-up rule applied to a single weekly total moves it by at most 14 minutes. The same rule applied to twenty small entries can move it by hours.
If you bill or report time, write your rule out with these five decisions. It takes ten minutes, and it settles most disputes before they start.
If the policy is for employees, add a sixth step: have someone qualified in your jurisdiction review it before you use it.
This is a made-up example to show the mechanics. The tasks and minutes are invented.
A freelance developer logs five entries for one client on a Tuesday afternoon:
| Entry | Raw minutes | Nearest 15, per entry | Up to 15, per entry | Up to 6, per entry |
|---|---|---|---|---|
| Client email | 7 | 0 | 15 | 12 |
| Bug fix | 22 | 15 | 30 | 24 |
| Status call | 38 | 45 | 45 | 42 |
| Quick invoice question | 4 | 0 | 15 | 6 |
| Design review | 52 | 45 | 60 | 54 |
| Total | 123 (2.05 h) | 105 (1.75 h) | 165 (2.75 h) | 138 (2.3 h) |
Now round the 123-minute total once instead:
Here is what the example shows:
Same afternoon, same work, and the billed time ranges from 1.75 to 2.75 hours depending on the rule. That is why the rule belongs in writing.
Rounding lots of tiny entries. If your day is split into many short entries, per-entry rounding swamps the real time. Group related work into one entry per task, or round per day.
Rounding twice. A tracker rounds each entry, and then the invoice rounds the total again. Each step looks harmless, but together they push the number further than either rule intended. Pick one stage.
One-way rounding nobody agreed to. Always rounding up without telling the client, or always rounding down on staff hours, is where rounding stops being a convenience. If it only ever moves in one direction, it needs to be disclosed and accepted.
Throwing away the raw times. Once only rounded numbers exist, you cannot answer a simple question like “how long did that call actually take?” Keep the unrounded record, even if nobody else ever sees it.
Quietly rounding down your own time. Freelancers often shave entries to look efficient. Over a month, that lowers your effective rate more than you would expect. The real hourly rate calculator shows what you actually earn once unbilled minutes are counted.
Rounding a reconstruction. The biggest error usually happens before rounding. If you forgot to start the timer and rebuilt the afternoon from memory on Friday, a perfect rounding rule just formats a guess. Capture time as it happens, or keep something you can check against later. Our guide to a Mac timesheet without manual entry covers ways to do that.
Mixing increments without labeling them. Using 0.1 hour for one client and 15 minutes for another is fine. Forgetting which is which, and invoicing one client on the other’s rule, is not. Note the increment on each client record.
Rounding is a reporting decision. The tool’s real job is to capture accurate raw minutes and then let you apply your rule once. The details below come from each vendor’s own pages as checked on October 4, 2026. For a wider look at the category, see our guide to choosing a time tracker for Mac.
Harvest is built around timers, daily and weekly timesheets and invoicing, with expense tracking included even on the free plan. If you are comparing it with other options, see our list of Harvest alternatives for Mac.
Toggl (formerly Toggl Track) offers manual and real-time timers, timesheets and calendar integrations. Billable rates require a paid plan. We compare it with Mac-native options in Toggl for Mac.
Clockify covers timer, timesheet, calendar and kiosk entry, plus an auto tracker in the desktop app. Invoicing and approvals start on the Standard plan. See Clockify for Mac for how it runs on a Mac.
Timing is a Mac-only automatic tracker. Its pricing page lists billing status tracking and customizable reports with report rounding. We compare it in our Timing alternative page.
Of these vendor pages, only Timing’s lists rounding. For Harvest, Toggl and Clockify, rounding behavior was not part of what we checked, so confirm it in each vendor’s documentation before you rely on it.
| Tool | What it does for this | Price |
|---|---|---|
| Harvest | Timers, daily and weekly timesheets and calendar tracking capture raw minutes. Invoicing and expense tracking are built in. | Free: $0 forever (1 seat, 2 projects). Teams: $9 seat/month ($108 per seat, billed annually), or $11 seat/month billed monthly |
| Toggl | Manual and real-time timers, timesheets and calendar integrations. Billable rates and team reports are on paid plans. | Free for up to 3 users. Starter: $9 per user per month billed annually, or $12 per user per month billed monthly |
| Clockify | Timer, timesheet, calendar, kiosk entry and auto tracker. Invoicing and approvals are on Standard and above. | Free for up to 5 users. Basic: $3.99 per seat/month billed annually, or $4.99 billed monthly |
| Timing | Automatic tracking of apps, websites and documents on Mac, with billing status tracking and report rounding | No free tier. Professional: $9 per month billed annually, or $11 per month billed monthly. 30-day trial, no credit card required |
| Dayflow | Records the screen at one frame every 10 seconds and has AI write the day into a timeline. It does not round time or create invoices. | $0, MIT licensed. Optional Pro at $20 a month |
Dayflow is our product. It fits on the input side of rounding. It is a free, open-source Mac app for macOS 14 or later that keeps a timeline of what you actually worked on, so you can check a timesheet entry against the record instead of your memory. Recordings and the timeline are stored on your Mac, analysis can run on-device with local AI, and you can export a date range as Markdown.
It does not fit the output side. Dayflow has no rounding, no invoicing, no payroll approvals and no team reports. Its AI summaries can also miss or misread work, so check them before you bill from them.
If you want rounding applied inside your reports on a Mac, Timing is the better tool, since report rounding and billing status tracking are on its listed feature set. If you need to turn tracked time straight into invoices, Harvest does that from its free plan, and Clockify does it from Standard upward. Dayflow can sit alongside either one as a record to check against, but it will not replace them for billing.
Timesheet rounding is a rule, not a fudge. A good one names the increment, the direction and the scope, keeps minimum charges separate and is written down where everyone affected can read it. Round once, preferably on totals rather than on every small entry, and always keep the raw minutes.
The most common way rounding goes wrong is not the arithmetic. It is the input. A tidy 0.1-hour figure built on a remembered guess is still a guess. Get the raw time right first, by timer, automatic tracker or a record you can review, and the rounding rule becomes the easy part.
It depends on where you work, the type of employee and any contract or union agreement in place, so nobody can give a single answer, and this guide is not legal advice. If you set a rounding policy for staff, ask an employment lawyer or your local labor department before you apply it. Whatever you decide, keep the original clock-in and clock-out times alongside the rounded figures.
It is a convention for rounding to the nearest quarter hour. Times 1 to 7 minutes past a quarter round down, and times 8 to 14 minutes round up. Over many entries it tends to balance out, which is why some employers use it. Whether it is allowed for your workplace depends on your jurisdiction, so check local rules before you adopt it.
Six minutes is one tenth of an hour, so every entry converts to a clean decimal like 0.1 or 0.7 with no fractions. That makes invoices easy to total and audit. The convention spread from law firms to consultants and accountants who bill by the hour. Many firms also round each entry up to the next tenth, which is a choice the engagement letter should spell out.
If your durations are stored as time values, MROUND rounds to the nearest increment, CEILING rounds up and FLOOR rounds down. For example, CEILING(A2, "0:06") rounds a duration up to the next six minutes in Excel. If you store decimal hours instead, round to 0.1 or 0.25 using the same functions. Keep the unrounded column and add the rounded one next to it.
No. Dayflow records your screen at one frame every 10 seconds and has AI write a timeline of the day, but it does not round time, track billable hours or create invoices. If you want rounding built into your reports on a Mac, Timing is the better fit, since its pricing page lists report rounding along with billing status tracking.
Yes. Put the increment, the direction and any minimum charge in the proposal or contract, for example "billed in 0.1-hour increments, rounded up per task." Clients rarely object to a clear rule they agreed to in advance. They do object when an invoice shows four 15-minute charges for quick emails they never expected to pay for.
Pick one place and only one. Rounding in the tracker and then again on the invoice compounds the effect and makes the numbers hard to explain. Most people get cleaner results by tracking raw minutes and applying the rule once when they build the report or invoice. That way the raw record stays intact if you ever need to recheck it.
Not if it is a disclosed rule that the client or employer accepted. Rounding up per entry is common in professional services and is effectively a pricing decision. It becomes a problem when it is hidden, when it is applied only in one party's favor without agreement, or when it is used to cover time that was never worked.
Yes. Automatic trackers capture time as you work, often in many short segments. Rounding each segment would distort the total badly, so it usually makes sense to group activity into tasks or projects first and round the grouped totals. Check how your tool applies rounding before you trust its rounded reports.
Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.
Download for MacOS macOS 14+ · MIT licensed · no account required