ClockTally

Choosing a Timesheet Rounding Policy

Last updated June 10, 2026

A timesheet rounding policy snaps clock punches to a fixed increment — in practice, the nearest 5, 6, or 15 minutes. Federal regulation accepts rounding only when it is neutral: over time, minutes rounded in the employee's favor must roughly cancel the minutes rounded away. Any setup that only ever shortens paid time fails that test.

First question: should you round at all?

Rounding exists because mechanical punch clocks made exact-minute payroll tedious. That constraint is gone. Every modern timekeeping system records punches to the minute and totals them without anyone touching a calculator, so paying from exact punch times is now the simplest option — and the only one with zero compliance surface, because there is no rounding to defend. If you are setting up timekeeping for the first time, exact time should be your default, and you should need a concrete reason to depart from it.

The reasons that still hold up are narrow: aligning payroll with tenth-of-an-hour client billing, matching a legacy payroll import that expects rounded totals, or smoothing trivially noisy punches at a shared kiosk. "We've always done it" is not on the list. If none of those apply, stop here, pay exact minutes, and skip the rest of this guide with a clear conscience.

The three defensible increments

The federal rounding regulation, 29 CFR 785.48, names three increments employers have historically used: the nearest 5 minutes, the nearest tenth of an hour (6 minutes), and the nearest quarter hour (15 minutes). The load-bearing word in each case is nearest. Nearest-increment rounding is symmetric — a punch is as likely to gain time as to lose it — which is what lets the swings average out to zero and keeps the policy on the right side of the regulation.

Comparing the options

Policy Max swing per punch Pros Cons
Exact minutes (no rounding) 0 min Nothing to defend or audit; matches what employees see Totals rarely land on clean numbers; no billing alignment
Nearest 5 minutes 2 min Minimal drift; few disputes Doesn't map to decimal hours; little practical benefit over exact
Nearest 6 minutes 3 min Punches land on tenths of an hour; payroll matches tenth-hour invoices Unfamiliar to employees used to quarter hours
Nearest 15 minutes 7 min Familiar; simplest mental math on paper timesheets Largest swings; most likely to draw complaints and audits

Why always-down rounding is the policy to avoid

The configurations that create real exposure are the one-way ones: rounding every clock-in up to the next increment, every clock-out down to the previous one, or rounding only when the result reduces paid hours. Under any of these, no punch can ever add a minute in the employee's favor, so the gains-and-losses averaging the regulation depends on is mathematically impossible. The policy clips paid time on every single shift, the clipped minutes accumulate in payroll records you yourself maintain, and those records become the evidence in a back-wage claim.

Subtler versions carry the same flaw. A grace period that forgives early clock-ins but rounds late clock-outs down is one-way rounding wearing a friendlier name. So is a symmetric written policy paired with scheduling that herds punches into the losing half of each window. The test is empirical, not textual: compare rounded totals against raw punch totals across a few pay periods. If the gap consistently points the same direction, the policy is not neutral in practice, whatever the handbook says.

The 6-minute case: billing in tenths

Law practices, accounting firms, agencies, and consultancies commonly bill clients in tenths of an hour. If your invoices count time in 0.1-hour units but payroll rounds to the quarter hour, the same afternoon produces two different totals, and reconciling them is a recurring chore. Rounding punches to the nearest 6 minutes makes the two systems speak the same language: a punch pair of 9:02 to 11:34 rounds to 9:00–11:36, which is exactly 2.6 hours — billable as 2.6 and payable as 2.6 with no conversion step. (Our decimal hours converter handles the h:mm-to-tenths arithmetic when you need to spot-check.)

What drift costs over a year: a worked example

Suppose a 12-person crew works 5 shifts a week for 50 weeks — 3,000 shifts a year. A misconfigured one-way policy that clips an average of just 4 minutes per shift removes 3,000 × 4 = 12,000 minutes, which is 200 hours of unpaid work per year. At $16 per hour that is $3,200 in raw back wages — and the true exposure is larger, because some of those clipped minutes belonged to weeks already past 40 hours, where they should have been paid at time and a half, and federal wage claims can reach back over multiple years of identical payroll runs.

Now run the same crew under a neutral nearest-15 policy. Each shift swings up to 7 minutes in either direction, but the swings cancel: a typical employee's rounded total lands within a few minutes of actual time each pay period, and the year-end gap is statistical noise around zero. Same increment, same clock — the entire difference is direction. You can verify this on your own punch data by running a week through the timesheet rounding calculator, which shows rounded and exact totals side by side under each increment.

How to document the policy

  1. Write it down. State the increment, the mode (nearest — never up-only or down-only), and whether rounding applies to each punch or to the day's total. Ambiguity here is what turns a payroll question into a dispute.
  2. Put it where employees can find it — the handbook and the onboarding packet — and have the timekeeping system configured to match the written text exactly. A policy that says "nearest quarter hour" while the software rounds clock-outs down is worse than no written policy at all.
  3. Keep the raw punches. Store actual punch times alongside rounded totals. They are your proof of neutrality, and discarding them removes your only defense.
  4. Audit quarterly. Pull rounded versus actual totals for the period. A near-zero net gap means the policy is working; a persistent one-way gap means fix the configuration and true-up the affected pay before anyone else finds it.

Frequently asked questions

Is time clock rounding legal for employers?

Under federal law, yes — 29 CFR 785.48 accepts rounding to the nearest 5 minutes, tenth of an hour, or quarter hour, on the condition that employees are fully paid for all time worked over time. Requirements elsewhere can be stricter, so confirm the rules for each location where you have employees before adopting a policy.

Which increment should a small business pick?

If nothing forces a choice, don't round — exact minutes is the cheapest policy to run and the only one that can't drift. If you bill clients in tenths, use nearest 6 minutes. Pick nearest 15 only if a legacy process genuinely requires quarter hours, and audit it more often because its swings are the largest.

Can we round clock-ins up and clock-outs down?

No. That arrangement can only ever reduce paid time, so it cannot average out and fails the neutrality condition the regulation imposes. Every defensible policy rounds to the nearest increment in both directions on every punch.

Should rounding apply per punch or to the daily total?

Either can be neutral. Per-punch rounding is what most systems do and what employees can verify themselves; total-rounding produces one small adjustment per day instead of two to four. Whichever you choose, name it explicitly in the written policy so the math is reproducible.

Does rounding change overtime?

It can. Overtime is computed from rounded hours, so a week that rounds to 40.1 hours owes overtime even if raw punches total 39:58 — and the reverse. This is one more reason to audit net drift: clipped minutes near the 40-hour line are the most expensive kind. See the federal overtime basics guide for how the threshold works.

What's the 7-minute rule, and is it a separate policy?

It is the same thing as nearest-15-minute rounding: punches 1–7 minutes past a quarter round back, 8–14 round forward. The 7-minute rule guide walks through the full rounding map punch by punch.

Related tools and guides