Seven: The Number Nobody Voted For
In the beginning — literally, in Genesis — God created the world in six days and rested on the seventh. That story, whether you take it as theology or literature, is the reason Western civilization organizes life in 7-day cycles. But the Hebrews didn't invent the 7-day week. They inherited it from Babylon, where astronomer-priests noticed the moon goes through four phases over roughly 28 days, and 28 divided into quarters gives you 7. They named the days after the seven visible celestial bodies — Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn — and those names survive in English (Sunday, Monday, Saturday) and Romance languages (mardi for Mars, mercredi for Mercury, jeudi for Jupiter, vendredi for Venus).
The 7-day week is an accident of Babylonian astronomy that got adopted by Judaism, then Christianity, then Islam, then European colonialism, and now governs everything from your Outlook calendar to your sprint board. Nobody ever held a referendum on 7. Nobody A/B tested it — well, two governments did, and the results were unambiguous. The most durable time unit in human civilization — more durable than any empire, any currency — is a number chosen because someone in Mesopotamia 2,600 years ago thought the moon moved in 7-day chunks. It doesn't. The lunar phase quarter is actually 7.38 days. But 7 was cleaner, and 7 had mystical resonance, and 7 stuck.
The Sprint Math Every Project Manager Does in Their Head
A two-week sprint. 2 × 7 = 14 calendar days. Your team works Monday–Friday, so that's 10 working days. Except there's a holiday in week two — down to 9. And Priya is on PTO Thursday–Friday of week one — now 7 working days of actual capacity for one developer. The client heard "two weeks" and put a meeting on their calendar for 14 calendar days from kickoff.
This is why project managers develop a twitch. The weeks-to-days conversion isn't just multiplication — it's a translation layer between three counting systems: the client's calendar (28 days in 4 weeks), the team's working calendar (20 days in 4 weeks), and individual availability (somewhere south of 20, unknown until mid-sprint). The formula never changes. The definition of "day" changes every time. A day in the client's mind is any square on the wall calendar. A day in the developer's mind is about 6 hours of uninterrupted coding between standup and the 3 PM meeting that should have been an email. These are not the same unit.
Experienced PMs learn to stop saying "weeks" and start saying "working days" as early as possible in a project conversation. "This will take 20 working days" is more honest than "this will take 4 weeks" — and it forces the client to do their own weeks-to-days math backward, which usually surfaces the weekend-and-holiday problem before it becomes a missed-deadline problem. For the reverse conversion, when you're translating the other direction, see our days to weeks converter.
Forty Weeks Is Two Hundred and Eighty Days
40 weeks × 7 = 280 days. That's the number every obstetrician carries in their head, and the one every expectant parent eventually Googles at 2 AM. Human pregnancy is measured as 40 weeks from the first day of the last menstrual period (LMP), not from conception. Since ovulation and conception typically happen around day 14 of the menstrual cycle, the actual gestation period is closer to 38 weeks — 266 days — from fertilization to delivery. The extra two weeks are a measurement convention, not a biological reality. They exist because LMP is a date women typically know, whereas conception date is almost always uncertain within a multi-day window.
This 280-day countdown explains why pregnancy is simultaneously "9 months" and "10 months." Divide 280 by the average calendar month (30.44 days) and you get 9.2 months. Count in 4-week blocks — as many pregnancy apps do — and you get 10 months. Both are correct, and both frustrate pregnant people who just want to know when this is going to be over. The due date has a ±2 week margin because conception timing varies, fetal growth rates vary, and babies don't carry calendars. The 280-day figure is the center of a distribution, not a deadline. For the reverse conversion, see our days to weeks tool. For months-to-days, use months to days (coming soon).
The Paycheck Calendar: Why Biweekly Means 14
"Biweekly" payroll: every two weeks. 2 × 7 = 14 calendar days between paychecks. 52 weeks ÷ 2 = 26 pay periods per year. Compare with semimonthly (twice a month, 24 periods): same annual salary, more paychecks (26 vs. 24), each slightly smaller. The two "extra" paycheck months — where you get three instead of two — seem unpredictable from an annual-planning perspective but are perfectly predictable if you count forward 14 days from your first pay date.
The biweekly system creates weird edge cases. If your pay period starts Monday and ends Sunday two weeks later, you've worked 10 days and been paid for 14 calendar days — weekends are paid. Start mid-period, and your first check is prorated by days-worked ÷ 10, not ÷ 14, because the denominator is working days even though the salary denominator is calendar days. Payroll software has to track both counts simultaneously; getting either one wrong produces angry employees and angrier tax filings. The weeks-to-days conversion is ×7. The weeks-to-working-days conversion is ×5 — or ×4, or ×6, depending on country, industry, and whether your company has adopted a 4-day workweek, which brings us to the next thing.
The Four-Day Rebellion
A growing number of companies — in the UK, Iceland, New Zealand, and tech sectors of the US and Canada — are experimenting with a 4-day workweek: 32 hours, same pay, same productivity expectations. The largest coordinated trial, run by 4 Day Week Global, found revenue held steady or increased at most participants, employee well-being improved, and resignations dropped. Whether it becomes standard or stays niche is an open question, but it's already scrambling the weeks-to-days math.
If your company switches to a 4-day workweek, a "1-week sprint" that used to be 5 working days is now 4. A "2-week project" goes from 10 working days to 8. Your annual working days drop from roughly 260 (52 × 5, minus holidays) to roughly 208 (52 × 4, minus holidays). That's 52 fewer working days per year — more than 10 full workweeks of capacity erased. The conversion factor from weeks to working days has changed, and nobody updated the spreadsheet. The root cause in every resulting postmortem is going to be the same sentence: "We assumed a 5-day week." For a deeper dive into how working days and calendar days interact in project timelines, see our time conversion guide.
Why the Seven-Day Week Is Unkillable
The French tried to decimalize the week in 1793. They replaced the 7-day week with a 10-day décade, with one rest day (décadi) every ten days instead of every seven. Workers went from 1 rest day in 7 to 1 in 10 — a 30% reduction in leisure time that they noticed immediately and hated passionately. The experiment collapsed after 12 years. The Soviet Union tried again in 1929 with the nepreryvka, a "continuous production week" that abolished weekends entirely and assigned workers staggered rest days on a 5-day rotation. Productivity tanked. Equipment broke more often (because no one had contiguous time for maintenance). Families couldn't coordinate shared days off. Stalin scrapped it in 1940.
These failures are instructive. The metric system replaced thousands of local measurement standards because measurement is a practical problem — a meter is a meter regardless of belief. But the week isn't just a measurement. It's a rhythm. It's the Sabbath, the Lord's Day, Jumu'ah — tied to religious observance in a way kilograms never were. It's the weekend that labor movements fought for. It's the cadence of school schedules, sports leagues, trash collection, and TV programming. Changing the length of the week requires changing all of these simultaneously, or accepting chaos. The 7-day week survived two revolutions designed to destroy it. It'll survive whatever calendar reform your startup proposes next.
The irony: despite all this cultural inertia, the 7-day week has no astronomical basis. The day is one Earth rotation. The month approximates the lunar cycle. The year is one solar orbit. The week is none of these — a pure social construct, arguably the most powerful one in history. More universal than any language, more durable than any state, more consistently observed than any law. Multiply by 7. It's never been anything else. It probably never will be.
days = weeks × 7
Worked Examples
1 week → 7 days
The base unit. One full 7-day cycle. Free trial length. Weekly standup interval. Enough time to decide a new job is a mistake — though most people need at least 2.
2 weeks → 14 days
The fortnight. Biweekly payroll. Standard vacation. Amazon Prime trial. A Scrum sprint: 14 calendar days, 10 working days, roughly 7 days of actual coding after meetings and code review.
3 weeks → 21 days
The "21 days to form a habit" myth (Maxwell Maltz, 1960; UCL researchers found the median is actually 66). A generous notice period. Three weekly sprints.
4 weeks → 28 days
Approximately one lunar month (actually 29.53 days). February in a non-leap year. The fake "month" project managers use — wrong 11 months out of 12 but too convenient to drop. 20 working days.
6 weeks → 42 days
A 4-week project that ran 50% over. A summer course. Lent (40 days not counting Sundays; 46 from Ash Wednesday to Easter). Minimum broken-bone recovery. When new parents stop answering texts.
12 weeks → 84 days
A quarter. 3 months simplified. Standard probation. A college semester. 60 working days — roughly how long a new engineering hire takes to become net-productive.
40 weeks → 280 days
Human gestation from LMP. The number every obstetrician memorizes and every expectant parent Googles at 2 AM. Due date ±13 days. For day-to-week pregnancy tracking, see days to weeks.
52 weeks → 364 days
One day short of a non-leap year, two short of a leap year. This 1-day gap is why January 1 shifts weekday each year. Close enough for payroll, not close enough for anyone who expects their birthday on the same weekday twice.
Common Weeks to Days
| Weeks | Days | Context |
|---|---|---|
| 1 week | 7 days | The base unit. Free trials. Weekly standups. |
| 2 weeks | 14 days | Fortnight. Payroll. Sprint. Vacation. |
| 3 weeks | 21 days | Notice period. Habit-formation myth. |
| 4 weeks | 28 days | Lunar month (approx). February. "One month." |
| 6 weeks | 42 days | Summer course. Broken bone recovery. Lent (approx). |
| 8 weeks | 56 days | Maternity leave (some countries). Two lunar cycles. |
| 12 weeks | 84 days | Quarter. Probation period. Semester. |
| 26 weeks | 182 days | Half year. Mid-year review cycle. |
| 40 weeks | 280 days | Full-term pregnancy (LMP). Academic year (approx). |
| 52 weeks | 364 days | 52 × 7. One day short of a year. |
Engineering Context
In software project management, the weeks-to-days conversion is where estimates go from useful to dangerous. A 4-week estimate sounds conservative — practically a month, plenty of time. Convert to days: 4 × 7 = 28 calendar days. Subtract weekends: 20 working days. Subtract two days of forgotten meetings: 18. Subtract the day the build server was down: 17. Subtract the half-day the senior dev spent unblocking a junior: 16.5. Your "4-week project" just became 16.5 working days of actual coding time, and the client still thinks they bought a month. The multiplier (×7) is never wrong. The definitions you multiply by it — of "week," "day," "available" — are wrong in subtle, compounding, project-canceling ways. This is why experienced engineers pad estimates by 50–100%. They're not lazy. They're doing the conversion in their head, then doing it again with realistic coefficients, arriving at a number actual humans can deliver. For related conversions: days to weeks (÷7), days to months (÷30.44), days to hours (×24), and months to days (coming soon).
More: days to weeks · days to hours · days to months · hours to days · Time Guide
Related Unit Converters
Frequently Asked Questions
How many days are in 2 weeks?
14 days. 2 × 7 = 14. But "2 weeks" means 14 calendar days in payroll, 10 working days in a standard Monday–Friday schedule, and anywhere from 10 to 17 vacation days depending on how you bookend weekends. The multiplication doesn't change — the definition of what you're multiplying does. A two-week notice period: 14 calendar days, roughly 10 working days for your colleagues to extract everything you know. A two-week vacation Monday-to-Friday-two-weeks-later: 12 calendar days for 10 PTO days. Same vacation booked Friday-to-Monday-two-weeks-later: 17 calendar days for the same 10 PTO days by capturing three full weekends. The ×7 is consistent. The strategy is not.
Why is pregnancy counted as 40 weeks but people say 9 months?
40 weeks × 7 = 280 days. Divide 280 by the average calendar month (30.44 days) and you get 9.2 months — about 9 calendar months and a week. The confusion comes from two competing definitions of "month": the calendar month (28–31 days, averaging 30.44) and the 4-week block (28 days exactly). 40 weeks ÷ 4 = 10 four-week months. So pregnancy is simultaneously 9 calendar months and 10 four-week months. Obstetricians use weeks because fetal development has precise weekly milestones — week 20 anatomy scan, week 24 viability threshold, week 37 full term — that would be hopelessly vague as "sometime in the sixth month." The 40-week count starts from LMP, not conception, adding roughly 2 weeks to the biological 38-week gestation. That buffer is why due dates are ±2 weeks and why first-time parents should never tell extended family the exact date.
Do work weeks count as 5 days or 7 days?
Both, and conflating them is the single most expensive mistake in project estimation. A calendar week is always 7 days. A standard work week is 5 days (Monday–Friday in the West, Sunday–Thursday in much of the Middle East). A 4-day workweek company works 4 days. A startup in crunch mode works 6 or 7. When your client says "deliver in 4 weeks," they mean 28 calendar days. When your engineering lead says "this will take 4 weeks," they mean 20 working days. The 8-day gap — nearly 30% of the timeline — is where projects die. The fix: never use weeks in a project plan. Use working days. Make the conversion explicit at the start, with everyone present, so the gap between calendar weeks and working weeks is visible before it becomes a missed deadline. For more, see our time conversion guide.
How many working days are in a year?
In a standard 5-day workweek: 52 weeks × 5 = 260 working days, minus public holidays (8–12 in Western countries) and PTO. A US employee with 10 holidays and 10 vacation days has 240 working days. A German employee with 12 holidays and 30 vacation days has 218. Under a 4-day workweek: 52 × 4 = 208 working days before deductions, about 188 after holidays and leave — 52 fewer working days than standard, or more than 10 full workweeks of capacity erased from the annual plan. The weeks-to-days multiplier (×7) doesn't answer any of these questions. It gives you the calendar-days ceiling. The floor — how many days anyone actually works — depends on labor law, company policy, and whether your CTO read that Iceland trial and decided to experiment.