EN

Calendar Tools: ISO Week, Weekday, Decimal Time

Three small calendar tools on one page : the ISO 8601 week number for any date, the day of the week a given date falls on, and a decimal-to-clock time converter (and back) — handy for reading a timesheet or an export that states a duration as decimal hours (7.5 h) instead of hours and minutes (7 h 30 min).

Calculator

Date
Date
Decimal hours → hours:minutes
Hours:minutes → decimal hours

How these three tools are calculated

ISO 8601 week: week 1 is the week containing the year's first Thursday; weeks start on Monday

Decimal hours → hours:minutes: hours = integer part, minutes = (decimal part) × 60

ISO 8601 week numbering doesn't just slice the year into 7-day chunks starting 1 January — it guarantees that every week belongs entirely to one calendar year or the other, whichever holds most of its days. That's why 1 January can fall in week 52 or 53 of the previous year.

Why ISO 8601 numbers weeks this way

ISO weeks do not start on 1 January. They start on Monday, and week 1 is the one that holds the year's first Thursday.

Thursday sits in the middle of a Monday–Sunday week. If that Thursday belongs to year Y, at least four of the seven days do too, so the whole week is assigned to Y — even when it began on a Monday in December. The same rule, worded differently: week 1 always contains 4 January. Well, that is why a Friday, Saturday or Sunday New Year's Day is still last year's week, not week 1.

PHP's W (week) and o (ISO year) follow this exactly. So do we.

ISO week versus calendar week

Open the same early-January date in a US calendar app, in default Excel, and here. You will not always get the same week number.

A lot of North American software — and Excel's WEEKNUM with its default return_type of 1 — treats Sunday as day 1 and calls week 1 “whatever week contains 1 January”, even if that stub is only a Thursday and a Friday. ISO will not have it. A week is seven days, Monday to Sunday, belonging to one ISO year. Around New Year the two schemes can disagree by one, or by a whole year number. Also, WEEKNUM(date, 2) starts on Monday but still pins week 1 to 1 January; that is still not ISO.

Pick one convention for the team and write it down. Mixing a US export with a European rota is how January reports go missing.

Why businesses use week numbers

Construction programmes, NHS rotas, warehouse shifts, sprint boards: “w/c 12 January” or “week 3” is shorter than a date range and survives a change of calendar year. UK project plans still talk in weeks more often than in months. Invoicing cycles, timesheet periods and weekly payroll runs line up on the same grid. A purchase order “for week 14” is unambiguous once everyone agrees it is the ISO week — and a mess if they do not.

Week numbers also sit neatly next to working-day counts when you are planning around bank holidays.

“Next week” means three different things until the first day is named.

Day of the year in software and logistics

Day of year (the ordinal date) numbers the days 1 through 365, or 366 in a leap year. 1 February is day 32; 31 December is 365 or 366.

Programmers know it as %j, or PHP's z (zero-based, which is why this page adds one). ISO writes it as 2026-032. Climate files, satellite passes, batch numbers on a shop floor: a single integer sorts and subtracts without anyone parsing a month name. Warehouses use it for catch dates and internal use-by marks, especially where the civil month means nothing operationally. It is not the astronomical Julian day (the running count from 4713 BCE). People borrow the word “Julian” for both; the arithmetic is not the same.

Once you cross 31 December, day-of-year will not give you a duration. Use the date duration calculator for that.

Why timesheets and payroll use decimal hours

A timesheet that stores 7.50 + 8.25 + 6.00 can be summed in one cell. Hours and minutes cannot — you hit sixty every time. UK payroll software and most professional-services time recording (law, consulting, engineering) keep duration as hours to two decimal places, then multiply by a rate. 7.50 on the export is 7 hours 30 minutes on the clock. HMRC does not mind either notation; the spreadsheet does.

The same hours feed seniority and working-time calculations — different question, same raw duration.

Just do not read the decimals as minutes.

7.5 hours is 7 h 30 min, not 7 h 50

7.5 h means seven and a half hours. That is 7:30, not 7:50.

The point splits whole hours from a fraction of an hour, not from minutes. You multiply that fraction by 60. Treating 7.5 as “seven hours fifty” is the classic mix-up: fifty minutes would be 7.833… h. Paste 7.50 into a rota as 7:50 and you have given someone twenty minutes, or taken them away.

hours = integer part  ; minutes = (decimal part) × 60

  • 0.25 h → 15 min
  • 0.5 h → 30 min
  • 0.75 h → 45 min
  • 0.1 h → 6 min (one tenth of an hour)

7.50 is not 7:50. 1.10 h is not 1 h 10 min — it is 1 h 06 min. If a spreadsheet mixes the two notations, convert before you add.

53-week ISO years

Most ISO years have 52 weeks. A few have 53. Not a bug — a leap week.

You get 53 when 1 January is a Thursday: week 1 then starts on the previous 29 December, and enough of the following December is left for a 53rd week. You also get 53 when 1 January is a Wednesday in a leap year (the extra day shoves the year-end Thursday along). 2015, 2020 and 2026 all qualify. In 2026, 1 January is a Thursday, so week 53 runs Monday 28 December 2026 to Sunday 3 January 2027.

A capacity plan built on “52 × 5 working days” is a week short those years.

Stopwatch time to decimal

Minutes and seconds follow the same conversion, one unit down. 3 min 30 s is not 3.30 min; it is 3.5 min, because 30/60 = 0.5. A lap of 1:15 (one minute fifteen) is 1.25 min, not 1.15. Labs, time-and-motion studies, race exports still ship min:s; a spreadsheet wants a single number. Reverse it the obvious way: decimal part × 60 gives seconds.

decimal minutes = minutes + seconds / 60

With hours:minutes:seconds, turn the seconds into a fraction of a minute first, then fold the lot into decimal hours.

Every rung on the ladder is the same: × 60 going down, ÷ 60 going up.

WEEKNUM versus ISOWEEKNUM

Excel ships two different week-number functions. They do not agree in January. Or in late December.

WEEKNUM(date) with no extra argument uses Sunday as day 1 and makes week 1 the week that contains 1 January. ISOWEEKNUM(date) (Excel 2013 and later) follows ISO 8601: Monday start, week 1 contains the first Thursday. There is a middle setting, WEEKNUM(date, 21), which is ISO as well — and another, WEEKNUM(date, 2), which starts on Monday but still ties week 1 to New Year's Day. Well, that last one looks European and is not. A pivot table that mixes WEEKNUM from a US workbook with ISO weeks from a UK one will double-count or drop the turn of the year.

If the workbook is for Europe, use ISOWEEKNUM and write it in the header so the next person does not “fix” it.

ISO year and calendar year are not the same

The week number is only half the label. The year that goes with it can differ from the civil year on the date itself.

29, 30 and 31 December often fall in week 1 of the next ISO year. 1, 2 and 3 January often fall in week 52 or 53 of the previous one. PHP's o is the ISO year; Y is the civil year. They part company on those days, and that is what this page prints as two separate rows. Filter a report on calendar year 2027 and you will quietly drop Monday–Thursday of week 53/2026 if 1 January 2027 is a Friday — which it is.

Store both. A week number without its ISO year is not a key.

Tenths of an hour on a timesheet

UK professional-services firms often bill in tenths of an hour: six-minute units. 0.1 h = 6 min. 7.3 h is 7 h 18 min, not 7 h 30 min.

Payroll systems that go to two decimal places are working in hundredths (0.01 h = 36 seconds). A tenth is exact in that scale (0.10); six minutes is exact. Seven minutes is not: 7/60 = 0.1166… h, which rounds to 0.12 h (7 min 12 s) or 0.11 h (6 min 36 s) depending on the package. That is why a clock-in of 7:07 can become 7.12 on the payslip without anyone mistyping. The working-time calculator keeps the raw hours; the rounding rule is your software's, not the clock's.

If you are filling a timesheet, round to the unit it actually uses — tenths or hundredths — before you add the week up.

Related calculators