Hours to Minutes

An Invoice Says 3.4 Hours; the Matter File Says Thirty-Four Six-Minute Blocks

Professional time is recorded twice over in two different number systems. The stopwatch, the calendar entry and the phone log all speak in minutes, base sixty. The narrative line on the bill, the rate card and the realisation report all speak in decimal hours, base ten. Between them sits the billing increment — usually a tenth of an hour — which quietly rounds everything that happens into a fixed block size before it ever reaches a client.

Conversion factor: 1 h = 60 min exactly, so multiply hours by 60. That is what makes the tenth of an hour so convenient — 0.1 h is exactly 6 minutes with nothing left over — and it is why a recorded 3.4 h reads as 204 minutes, or 3 hours and 24.

Why Two Number Systems Sit on One Timesheet

The work happens in minutes

A call runs seven minutes, a document review twenty-three, a diary entry forty-five. Nothing about the actual day arrives pre-rounded into anything.

The bill has to multiply

A rate is money per hour, so the recorded time must become a decimal before it can be multiplied. Sixty-based figures do not survive that step intact.

Sixty divides ten times, cleanly

Ten equal blocks of six minutes give a decimal with one place and no recurring fraction, which is exactly why the tenth beat every rival increment.

Rounding is a policy, not an accident

The increment is agreed in the engagement letter. It determines what a two-minute email costs, and over a month it moves more money than most people assume.

Reconciling Recorded Time With a Billed Figure

Most uses of this pair start with a query — a client asking what a decimal entry means, or a fee-earner checking that the practice-management system rounded the way the retainer says it should.

Type the decimal hours from the entry

Enter 3.4, 0.7 or 1.25 exactly as the line item shows it. A comma is accepted in place of the point, so an entry written 3,4 by a European system converts without editing.

Read the minutes and split off the whole hours

The minute total appears as you type. Subtract sixty for each whole hour to get the clock form a client understands: 204 minutes is 3 hours 24, and 0.7 h is 42 minutes flat.

Swap the pair to code a raw duration

Press the swap control (↔) for minutes → hours when you are going the other way: a 23-minute attendance becomes 0.3833 h, which the increment policy then rounds to 0.4.

Copy the clean figure into the narrative or the sheet

The copy control on each field returns bare digits with no unit and no spacing, which is what a billing narrative or a spreadsheet column of the day's entries needs.

The decimal point is not a colon: writing 2.30 for two hours and thirty minutes is the single most expensive typing habit in time recording. The system reads 2.3 h and bills 2 hours 18 — twelve minutes short on every entry it happens to. Two hours thirty is 2.5 h; three-quarters of an hour is 0.75, not 0.45.

Billing Increments and What a Three-Minute Call Costs Under Each

Every increment in common professional use, with its decimal value, its length in minutes, and what happens when a genuinely short task is recorded against it. The last column assumes the standard rule: any part of a block consumes the whole block.

Billing increment	Decimal hours	Minutes	A 3-minute call bills as
Whole minute (1/60 h)	0.0167	1	3 min — 0.05 h
Tenth (1/10 h) — the usual standard	0.1	6	6 min — 0.1 h
Sixth (1/6 h)	0.1667	10	10 min — 0.17 h
Fifth (1/5 h)	0.2	12	12 min — 0.2 h
Quarter (1/4 h)	0.25	15	15 min — 0.25 h
Half (1/2 h)	0.5	30	30 min — 0.5 h

The right-hand column is the whole argument in one place. The same three minutes of actual work is billed as three minutes, six, ten, twelve, fifteen or thirty depending on nothing but a clause in the engagement letter. That is why the tenth has settled in as the compromise: fine enough that short tasks are not grossly inflated, coarse enough that nobody is recording to the second.

What the Pair Does at Month-End

Decimal in, clock time out

A line item of 3.4 becomes 204 minutes while you type, which is the form to use when a client asks what an entry actually covered.

Raw durations back into billable decimals

Swapping the pair converts a 23- or 47-minute attendance into the decimal hours a time entry expects, before the increment policy rounds it.

Days and weeks for the annual figures

Both dropdowns cover every time unit, so an annual chargeable target can be read across into days or weeks without leaving the page.

Recurring thirds do not get lost

Values are kept to eight decimals, so the awkward increments — a sixth of an hour, a twelfth — stay visible instead of collapsing to a misleading 0.17.

Time-Recording Questions From the Billing Cycle

Why did the six-minute tenth become the standard increment?

Because sixty divides by ten without remainder, and almost nothing else about time does. Splitting an hour into ten blocks gives six-minute units and single-decimal-place values — 0.1, 0.2, 0.3 — that a person can add up on paper without error and a system can multiply by a rate without rounding artefacts. Try the same with twelve blocks and you get 0.0833; try eight and you get 0.125, which is exact but harder to read at a glance. The tenth won on arithmetic hygiene long before software made any of it automatic.

My entry says 2.30 — is that two and a half hours?

Not to the system. In decimal hours 2.30 means 2.3, and 0.3 h is 18 minutes, so the entry bills 2 hours 18 rather than the 2 hours 30 that was probably intended — a twelve-minute shortfall. Two hours thirty is 2.5. The confusion is easy to spot once you know the tell: any decimal fraction above .59 is unambiguous nonsense as clock time, while everything from .01 to .59 will pass silently and be wrong. When in doubt, convert the fraction to minutes and check it against the diary.

How much does quarter-hour rounding add over a month?

More than most people expect, because it compounds per entry rather than per day. Rounding up to the next block adds on average half a block, so a quarter-hour policy adds about 7.5 minutes to every entry against roughly 3 minutes under tenths. A fee-earner logging eight entries a day picks up around 60 extra minutes daily on quarters and about 24 on tenths; across 21.7 working days that is roughly 21.7 chargeable hours a month against 8.7 — a gap of some 13 hours arising from the increment alone, with no difference whatever in the work done.

What is a minimum billing unit, and how is it different from the increment?

The increment is the block size everything is rounded to; the minimum is the floor below which no task can be billed at all. They are often the same figure — a tenth-of-an-hour firm usually has a 0.1 minimum — but not always. A retainer might record in tenths while imposing a 0.3 minimum on telephone attendances, which means a two-minute call and a seventeen-minute call are billed identically at 18 minutes. The two settings have to be read together, because a small increment paired with a large minimum behaves like the large increment for everything short.

How do I total a day that mixes decimal entries and clock times?

Put everything into minutes first, add, then convert once at the end. Adding 1.75 h to "40 min" in a single column is where mistakes breed, because a spreadsheet will happily treat the two as comparable numbers. Convert 1.75 h to 105 minutes, add the 40 to reach 145, then divide by 60 for 2.4167 h — which the tenth policy records as 2.4. One conversion at the start and one at the end beats six mid-column conversions, and it leaves an audit trail a supervising partner can follow.