Minutes in, decimal hours out
Sometimes you do not have hours and minutes — you just have minutes. A task took 95 minutes, a meeting ran 50, a machine sat idle for 23. This converter turns pure minutes into decimal hours directly: 95 minutes is 1.5833 hours, ready for any timesheet, invoice or log that expects a decimal. Type a number and both the decimal hours and the equivalent clock time appear immediately.
The formula is a single division by 60, since there are sixty minutes in an hour. 37 minutes ÷ 60 = 0.6167 hours. That is the entire math — the tool's job is to remove every other step: no splitting minutes into hours-and-remainder first, no fraction reduction, no rounding in your head. The result carries four decimal places, which is finer than any payroll system needs, so whatever rounding policy your employer applies happens on their side, not in your arithmetic.
Raw minutes arrive from everywhere: a phone stopwatch stopped at 42:18, a project app that exports task duration as 173 minutes, a parking receipt stamped 87 minutes, a therapy session notes field that just says 50. None of those formats survive contact with a payroll field or an invoice line that demands hours. The converter treats all of them the same way — one number in, a decimal out — which is why it doubles as the cleanup step between however time was captured and however it has to be reported.
The 0–60 quick chart timesheet day deserves
Below the converter you will find the full minutes-to-decimal chart from 1 to 60 minutes. The payroll-power values are worth knowing by heart: 15 minutes is 0.25, 30 is 0.5, 45 is 0.75, and the awkward ones — 7 minutes (0.1167), 23 minutes (0.3833), 38 minutes (0.6333) — are exactly why the chart exists. Scan the row, copy the decimal, move on.
Employers that round to the nearest quarter hour effectively snap every punch to 0.00, 0.25, 0.50 or 0.75. If your company rounds to the nearest tenth instead, the tenth values (6 minutes = 0.1, 12 = 0.2, 18 = 0.3, and so on) are the ones to keep open while you audit a timesheet. Either way, the chart turns a page of punches into a page of decimals in about a minute.
Payroll: what 37 minutes is actually worth
Here is the calculation a payroll clerk runs dozens of times a week. An employee stayed 37 minutes past shift end. 37 ÷ 60 = 0.6167 hours, which the company policy rounds to 0.62. At $24.50 an hour, that overtime chunk is 0.62 × $24.50 = $15.19 — or $19.16 once the 1.5× overtime multiplier applies. Multiply the same 37-minute habit across a 40-person crew for a month and the rounding rule alone swings the payroll by hundreds of dollars.
This is why payroll software stores time as decimals and never as hours-and-minutes: money multiplies cleanly against 0.62, and badly against '37 minutes.' When a paycheck looks off, the fastest audit is to take the total minutes you believe you worked, convert with this page, and compare the decimal against the one printed on the stub. If the minutes match but the decimal does not, the dispute is about rounding policy, not arithmetic — a much easier conversation to win.
The same math scales to a week. Say an employee logs overtime in three bursts: 37 minutes on Tuesday, 22 on Thursday, 53 on Friday. Converted individually that is 0.6167 + 0.3667 + 0.8833 = 1.8667 hours; total the minutes first and you get 112 ÷ 60 = 1.8667 hours — the two routes always agree, which is a useful check when a supervisor and a payroll system report different weekly totals. The disagreement is never in the division; it is in whether rounding happened per day or per week, and at $24.50 an hour that single policy choice is worth about a dollar per employee per week in either direction.
HR punch clocks: 8:12 to 16:47, decoded
A typical raw punch pair reads 8:12 in, 16:47 out. Before anyone touches a decimal, subtract the times: 8 hours 35 minutes on the clock. Knock off a 30-minute unpaid lunch and the paid time is 8 hours 5 minutes — and now the minutes part needs this page: 5 ÷ 60 = 0.0833, so the day goes into the payroll system as 8.08 hours at a tenth-rounding company, or 8.0833 unrounded.
HR teams doing this by hand for a stack of paper timecards usually run the same loop: difference the punches, strip the break, convert the leftover minutes to a decimal, key it in. The leftover minutes are almost never 15, 30 or 45 — they are 5, 22, 41, 53 — which is exactly the long tail this converter and chart exist for. For a full week of punches, the time card calculator does the differencing and totaling in one pass and multiplies by the hourly rate to estimate gross pay.
The failure mode in that manual loop is almost always the same: someone converts the whole 8 hours 35 minutes — including the lunch — or converts the 35 minutes as 0.35 instead of 0.5833, because '35' and '.35' look like they belong together. They do not. Thirty-five minutes is 35/60 of an hour, and the chart below makes that visible: find 35 in the minutes column and the decimal column says 0.5833. Keeping the chart open while keying a batch of timecards is the cheapest accuracy upgrade an HR desk can make.
Legal and consulting billing: the 6-minute increment
Law firms and consultancies traditionally bill in tenths of an hour — the famous 6-minute increment. Under that convention every task is rounded up to the next 0.1: a 4-minute client call bills as 0.1 hours, a 13-minute contract review bills as 0.3 (because 13 ÷ 60 = 0.2167, which rounds up to the next tenth), and a 47-minute deposition prep bills as 0.8. At a $350 hourly rate, that 4-minute call is a $35 line item.
The decimal makes the invoice readable. '0.3 hours — reviewed amended clause' means something a client can check; '18 minutes' invites a dispute about whether the review really took that long. Billing assistants converting a day of narrative time entries keep a minutes-to-tenths strip next to the keyboard: 1–6 minutes is 0.1, 7–12 is 0.2, 13–18 is 0.3, and so on up to 55–60 being 1.0. The chart below covers every one of those rows to four decimals, so you can see the exact value before your firm's rounding-up rule bites.
Watch how a morning adds up. Six entries: 4-minute call (0.1), 22-minute document review (0.4), 9-minute email exchange (0.2), 31-minute client meeting (0.6), 6-minute filing (0.1), 47-minute deposition prep (0.8). The raw minutes total 119 — 1.9833 exact hours — but the billed total is 2.2 hours, because each entry rounds up separately. At $350 an hour the increment system turns that morning into $770 instead of $694.17, which is precisely why clients negotiate over billing increments and why every timekeeping app shows the tenth, not the minutes.
A day of billing shows why the conversion discipline matters. Six entries — 4, 11, 13, 27, 38, 47 minutes — total 140 raw minutes, which is 2.3333 hours. Billed in 6-minute increments they become 0.1 + 0.2 + 0.3 + 0.5 + 0.7 + 0.8 = 2.6 hours. That 0.2667-hour gap, 16 minutes, is the increment system doing exactly what it was designed to do, and at $350 an hour it is a $93 difference on a single ordinary day. Clients who audit legal invoices run this exact comparison, so a firm that can show raw minutes beside billed tenths has nothing to explain.
Medical billing: 15 minutes = 1 unit
Nurses, therapists and coders live in a different decimal world: the 15-minute unit. AAPC guidance for timed CPT codes ties billing to how many 15-minute units a service occupies, so a 50-minute physical therapy session is not '0.83 hours' on the claim — it is 3 full units plus 5 leftover minutes, and whether those leftovers can join other minutes to bill a fourth unit depends on the payer's 8-minute rule.
Even so, the decimal conversion is the working step underneath. Coders reconciling a day sheet convert minutes to hours first — 50 minutes is 0.8333 hours — to sanity-check that the unit count is plausible against scheduled time, and clinic managers comparing therapist productivity across sites do it in decimal hours because units differ by payer. When a 15-minute unit system and an hourly payroll system meet in the same clinic, someone is doing this conversion at the boundary every single day.
The 8-minute rule is where the decimals get concrete. Under Medicare-style guidance, a single leftover chunk needs at least 8 minutes to bill as its own unit — so 22 minutes of a timed service is 1 unit (15 + 7, and 7 is not enough), while 23 minutes is 2 units (15 + 8). Across mixed services the leftover minutes can pool: 7 minutes from one code plus 9 from another make 16, which bills one more unit. In decimal terms the boundary is 8 ÷ 60 = 0.1333 hours — a number nobody writes on a claim form, but the threshold every coder's cheat sheet is built around.
Manufacturing: downtime minutes into OEE hours
On a production floor, downtime is logged in minutes because that is how fast things happen — a jam cleared in 4 minutes, a changeover that ate 38, an unplanned stop of 127. The OEE report at the end of the week speaks hours. So the shift supervisor's log becomes: 4 minutes = 0.0667 hours, 38 = 0.6333, 127 = 2.1167. Add them and the line lost 2.8167 hours across the shift, which against a 480-minute (8-hour) planned production time is an availability hit of about 35 percent.
The reason plants bother with decimals instead of leaving everything in minutes is that OEE, cost-per-unit and maintenance KPIs all divide by hours. A maintenance team arguing for a $12,000 parts upgrade will phrase the case as 'this failure mode costs 11.4 hours a quarter,' not '684 minutes' — hours are the currency the budget meeting understands. The minute-level logs are the evidence; the decimal hours are the argument.
The dollar version of that argument needs the same conversion. If a line runs at a loaded cost of $1,400 per hour and last quarter's jam-related stops totaled 684 minutes, the decimal version — 684 ÷ 60 = 11.4 hours — turns into $15,960 of lost capacity. Put '684 minutes' in a slide and the room shrugs; put '11.4 hours, $15,960' and the parts upgrade gets approved. Every reliability engineer who has won that meeting did the divide-by-60 step first, usually with exactly the chart sitting below this paragraph.
Students and labs: 105 minutes into a lab report
Lab courses and research logs often ask for duration in decimal hours because the downstream math — reaction rates, dosage-per-hour, equipment booking — is decimal. A bench session that ran from 9:10 to 10:55 lasted 105 minutes, which is 105 ÷ 60 = exactly 1.75 hours. That clean answer is luck; the next session might run 98 minutes (1.6333), and writing '1.63 h' on the report instead of 'about an hour and a half' is usually what the rubric rewards.
The same habit pays off in field work and study tracking. If you logged 42 minutes of observation on Monday, 67 on Wednesday and 55 on Friday, the week totals 164 minutes = 2.7333 hours — the format a timesheet-style research log or a grant effort report wants. Convert each entry as you go with the tool above and the weekly sum is simple addition.
A practical note on precision: report two decimals on coursework (1.75, 1.63) unless the template asks for more. Four decimals — the 1.6333 this converter gives you — is the honest exact value, but graders and booking systems both round to hundredths, so 98 minutes is 1.63 h on the form even though the clock says 1.6333. Keep the four-decimal figure in your own log; when six sessions sum to 602 minutes, dividing the total (602 ÷ 60 = 10.0333 h) avoids the drift that comes from adding six individually rounded numbers.
Rounding rules: quarter hour vs tenth hour
Two rounding conventions dominate timesheets, and they produce different paychecks from identical minutes. Quarter-hour rounding snaps everything to 0.00, 0.25, 0.50 or 0.75: 7 minutes becomes 0.25 under the common 7-minute rule, but 6 minutes becomes 0.00. Tenth-hour rounding snaps to 0.1 steps: 6 minutes is 0.1, 12 is 0.2, 38 minutes (0.6333) becomes 0.6. Neither is wrong — but if your stub shows 0.6 and you expected 0.75, the disagreement is the policy, not the math.
The safest workflow is to always record the exact decimal first — four places, straight from the converter — and apply the rounding rule as a visible second step. That way, when someone asks where a number came from, you can show the unrounded value, the rule, and the result. Auditors love that chain; it is also the fastest way to spot a timesheet that was rounded twice.
In the United States the quarter-hour convention has a specific regulatory shape: the Department of Labor's 7-minute rule lets employers round punches to the nearest quarter hour, so a punch at 8:07 can count as 8:00 and a punch at 8:08 becomes 8:15 — provided the practice averages out neutrally over time rather than always shaving the employee. Knowing that, the chart below reads differently: minutes 1–7 map to .00, 8–22 to .25, 23–37 to .50, 38–52 to .75, and 53–60 round up to the next whole hour. If your stub's decimals never fall outside those bands, your employer is quarter-hour rounding; if you see 0.1 and 0.3, it is tenths.
Auditing a timesheet with the chart
The chart works as a verification tool, not just a lookup. Add up the minutes column of a handwritten timecard, find that total's decimal equivalent, and compare it with what the payroll system printed. A mismatch almost always means a rounding rule or a typo — and now you know which side it came from.
A quick example of the audit in action: a timecard shows daily minute leftovers of 41, 17, 55, 29 and 8 across five shifts — 150 minutes of odd time on top of the whole hours. The chart turns 150 into 2.5 hours. The payroll export says 2.25. That quarter-hour gap is the company rounding each day down separately (41→0.5 is fine, but 17→0.25, 55→0.75, 29→0.5, 8→0.0 sums differently), and once you can point at the exact row where the totals diverge, the fix takes one email instead of a week of back-and-forth.
Need the reverse direction — decimal back to minutes? The decimal to time converter turns 0.62 back into 37 minutes instantly. For HH:MM entries like 7:48, the decimal hours calculator handles both directions, the decimal time conversion chart lists every 15-minute increment up to 12 hours, and the homepage converter covers the general case. Everything runs in your browser, nothing is stored.
Payroll Rounding Rules by Country
The United States federal standard under the Fair Labor Standards Act is the 7-minute rule: a punch within 7 minutes of a quarter-hour boundary rounds to that quarter hour, so 8:07 counts as 8:00 and 8:08 counts as 8:15. California adds a sharper edge — some jurisdictions treat 6 minutes as the rounding threshold and require rounding to the nearest tenth of an hour (0.1) rather than the nearest quarter, meaning a 6-minute punch registers as 0.1 hours and nothing shorter rounds up. The decimal arithmetic is identical; only the snap-to grid changes.
In the United Kingdom the typical payroll convention rounds to the nearest 6 minutes, which is 0.1 hours — the same tenth-hour increment used in legal billing. An employee who leaves 4 minutes early is docked 0.1 hours; one who stays 7 minutes late earns 0.1 hours of additional pay. The 6-minute boundary is low enough that most short overruns get captured, which is why UK payroll systems often display hours to one decimal place rather than two.
Australia commonly rounds to the nearest 8 minutes on timesheet entries, reflecting the 0.1333-hour threshold. A finish time of 7 minutes past the hour rounds down to zero, while 8 minutes rounds up to 0.1 hours — slightly more generous to employees than the US or UK models. Germany operates on a 15-minute grid exclusively: all entries snap to 0.00, 0.25, 0.50 or 0.75, and any minutes between grid points vanish or compound in the direction the rounding rule specifies. For cross-border payroll the safest practice is to record exact minutes in the source system and let each country's rule apply at export — which is exactly the workflow this converter supports.
Converting Timesheet Totals, Not Single Shifts
A common trap in weekly timesheet arithmetic is converting each shift to a decimal independently and then adding the decimals. The results are mathematically correct, but each conversion introduces a rounding step, and those rounding steps accumulate in one direction across the week. Consider three shifts logged as 12.4 hours, 7.8 hours and 9.1 hours — those are already in decimal form, but the same problem appears with raw minute totals.
Take a more concrete case: three minute-heavy shifts of 745 minutes, 468 minutes and 546 minutes. Convert each individually: 745 ÷ 60 = 12.4167, 468 ÷ 60 = 7.8000, 546 ÷ 60 = 9.1000. Rounded to two decimals: 12.42 + 7.80 + 9.10 = 29.32 hours. Now add the minutes first: 745 + 468 + 546 = 1,759 minutes, then divide once: 1,759 ÷ 60 = 29.3167 hours — 29.32 when rounded to two decimals. The answers match here because 468 and 546 divided cleanly, but the agreement is coincidental. When none of the individual shifts divide evenly, the per-shift rounding accumulates a small error in the weekly total.
The practical rule is: sum all the minutes for the week first, divide the total by 60 once, and apply the rounding rule to the single result. This approach is what payroll software does internally, and it is why a payroll system's weekly total occasionally disagrees with an employee's hand-added column of daily decimals — the software summed the minutes; the employee summed the rounded decimals. Neither is wrong in isolation, but only one is the authoritative number. When an audit is needed, the minutes total divided by 60 is the tiebreaker.
Common Mistakes When Reading a Decimal Timesheet
The most persistent mistake is reading 0.5 hours as 50 minutes. It is not. Decimal fractions of an hour are fractions of 60, not fractions of 100: 0.5 hours is 30 minutes, 0.25 is 15 minutes, and 0.75 is 45 minutes. The error happens because the digits after the decimal point look like cents — 0.50 feels like fifty cents, so the brain fills in fifty minutes. The cure is to never read a decimal timesheet digit-by-digit; always multiply the decimal part by 60 to get the minute equivalent, or use the chart on this page to translate back.
The second common mistake is misreading the larger fractions: 0.33 is 20 minutes, not 33; 0.67 is 40 minutes, not 67. A nurse logging 0.67 hours of patient contact time wrote down 40 minutes of care, not 67 — and if that distinction matters for a billing audit, reading it as 67 is a meaningful error. The decimal-to-minutes direction of this converter exists precisely for this check: type 0.67 and confirm 40 minutes appears before filing the claim.
A third mistake involves values above one: 1.75 hours is 1 hour and 45 minutes, not 1 hour and 75 minutes. Seventy-five minutes would be 1.25 hours. The whole-number part is always exact hours; only the decimal fraction requires the multiply-by-60 step. For values like 2.33, the breakdown is 2 hours and 20 minutes — a fact that is obvious once you apply the rule, but easy to misread as 2 hours and 33 minutes on a printed timesheet. Keeping a minutes-to-decimal chart visible while entering or reviewing time entries is the simplest safeguard against all three of these mistakes.