Every span between two dates can be written two ways: as weeks plus leftover days (10 weeks and 4 days) or as a single decimal number (10.57 weeks). The decimal form is tidy, sortable and spreadsheet-friendly, which is why payroll systems and project software love it. But that tidiness has a cost - the decimal hides the exact day a span ends on, and small rounding choices compound. This guide explains how decimal weeks are built, where they genuinely help, and where they will quietly lead you astray.
How decimal weeks are calculated
Divide the total day count by 7 and keep the fraction instead of splitting it off. Seventy-four days divided by 7 is 10.5714, which rounds to 10.57 weeks. Each leftover day contributes one seventh of a week, about 0.143, so the fractions follow a fixed pattern worth memorizing: 1 day is 0.14 weeks, 2 days 0.29, 3 days 0.43, 4 days 0.57, 5 days 0.71 and 6 days 0.86. When you see a decimal ending in one of those values, you can read the leftover days straight off it - 8.43 weeks is 8 weeks and 3 days wearing a different outfit.
The weeks between dates calculator shows the decimal figure next to the full-weeks-and-days figure, so you can cross-check one against the other. The days between calculator likewise shows a decimal weeks stat alongside the total days, which is the safest way to work: keep the exact day count in view and treat the decimal as a summary, never as the source figure.
Where decimal weeks earn their keep
Billing and timesheets. A contractor billing weekly can invoice 10.57 weeks at a weekly rate without inventing a separate daily rate for the odd days. Payroll systems that record leave in decimal weeks can deduct 0.43 weeks for a three-day absence cleanly. Comparing spans. Decimals sort and rank instantly: 12.86 weeks is plainly longer than 12.57, while "12 weeks and 6 days" versus "12 weeks and 4 days" needs a second look. Averages and statistics. Average project length, average time to hire, average recovery time - all of these come out of division anyway, and decimal weeks keep the unit consistent. In these jobs nobody needs to name the calendar date the span ends on, so nothing is lost by compressing the answer.

Where decimal weeks mislead
Deadlines and dates. A decimal cannot land on a calendar. "The filing is due in 10.57 weeks" does not tell anyone the due date; "10 weeks and 4 days from Monday the 5th" lands on a specific Friday. Any count that ends in an appointment, a court date, a due date or a delivery day should stay in weeks plus days. Pregnancy and ages. Milestones are set by completed weeks; 12.86 weeks invites someone to hear "nearly 13 weeks", and the difference matters at a scan or a dosing decision. Chained rounding. Decimals are usually rounded to two places, and each rounding discards up to half a hundredth of a week - about 50 minutes. Trivial once, but convert days to decimal weeks, average them, then convert back for a hundred employees and the drift becomes real money. False precision in reverse. Multiplying 10.57 by 7 gives 73.99 days; people then "correct" it to 73 or 74 depending on habit, and the two camps argue over a day that was never in the original count.
Converting back without losing a day
If a decimal week figure is all you have, multiply by 7 and round to the nearest whole day: 10.57 x 7 = 73.99, which is 74 days. Then, if the span started from a known date, add the days to that date rather than trying to add fractional weeks - a calendar understands 74 days, it does not understand 0.57 of a week. Keep at least two decimal places in any figure you store, and four places in anything that feeds payroll. And when you report a decimal, report the exact day count beside it at least once in the document; the person checking your work will thank you.
How many decimal places should you keep?
Two decimal places is the display standard, and it is fine for reporting - 0.01 of a week is about 1.7 hours, smaller than most decisions need. But storing and calculating deserve more care. Payroll and leave systems that round every entry to two places can drift: an employee who takes ten separate 3-day absences recorded as 0.43 weeks each has been charged 4.30 weeks, while the exact figure is 30 days, which is 4.29 weeks (30 / 7 = 4.2857). The difference is small - about a fifth of a day across a whole year of absences - but it always drifts the same direction, and auditors find one-directional drift suspicious. The safe pattern is to store the exact day count, compute in days, and convert to decimal weeks only at the moment of display. If a system forces you to store the decimal, keep four places (4.2857) so the rounding error per entry shrinks to a few minutes.
One quarter, three ways: a comparison
Take the first quarter of 2026, from January 1 to April 1. The day count is 90. In split form that is 12 weeks and 6 days; in decimal form it is 12.86 weeks. Now compare two more spans from earlier in this guide: 74 days is 10 weeks and 4 days, or 10.57 weeks; 176 days is 25 weeks and 1 day, or 25.14 weeks. Read the decimals alone and you can rank the spans instantly - 25.14 is plainly the longest - which is exactly the decimal form's strength. But ask a different question - "on what weekday does each span end if it starts on a Thursday?" - and only the split form can answer: 4 leftover days lands on a Monday, 6 leftover days on a Wednesday, 1 leftover day on a Friday. Neither form is better in the abstract. The skill is matching the form to the question before you start calculating, not converting afterwards and hoping nothing was lost.
The rule of thumb
Use decimal weeks when the answer feeds arithmetic - billing, averages, comparisons, budgets. Use full weeks plus leftover days when the answer feeds a calendar - deadlines, dates, ages, appointments. When in doubt, give both: "74 days, which is 10 weeks and 4 days (10.57 weeks)". It takes one extra second to write and removes every ambiguity this guide has described.
Frequently asked questions
What are decimal weeks?
Decimal weeks express a span as a single number instead of weeks plus days. Seventy-four days becomes 10.57 weeks, because 74 divided by 7 is 10.5714, rounded to two decimal places.
How do I convert days to decimal weeks?
Divide the day count by 7 and keep the fraction. Each leftover day adds about 0.143 weeks, so 1 day is 0.14 weeks, 3 days is 0.43, and 6 days is 0.86.
How do I convert decimal weeks back to days?
Multiply by 7. 10.57 weeks x 7 = 73.99 days, effectively 74. Because the decimal was rounded, expect to be within a fraction of a day of the true count, and use exact day counts for anything legal.
When should I avoid decimal weeks?
Avoid them for deadlines, due dates, ages and anything that must land on a specific calendar date. A decimal cannot tell you which weekday a span ends on; weeks plus leftover days can.
Is 0.5 weeks the same as 3.5 days?
Yes, arithmetically - half a week is 3.5 days. In practice a half day needs a time of day to land on, which is why date work is usually kept in whole days and decimal weeks are kept for money and time recording.
