Counting Weeks for Projects, Pregnancy, and Paydays

A midwife, a payroll clerk, and a scrum master could look at the same stretch of calendar and count a completely different number of weeks. The midwife starts the clock two weeks before anything has actually happened. The payroll clerk insists that some years quietly contain an extra payday. The scrum master rounds everything to a tidy fortnight and calls it Sprint 4. None of them is wrong. They are each following a rule that makes sense in their world, and the rules do not agree.

Weeks feel like the most honest unit of time we have. A day is too short to plan around, and a month is a shape-shifter that runs anywhere from 28 to 31 days, but a week is always exactly seven days, no exceptions. That reliability is exactly why weeks turn up everywhere, and why the disagreements are never about the length of a week, only about where you start counting and what you do with the days left over. This guide walks through the arithmetic first, then the three domains where people trip: pregnancy, payroll, and projects.

The one thing every week has in common

Before the domains diverge, the shared foundation is worth stating plainly. A week is seven days. Always. Unlike months, it never changes length, never has a leap version, and never depends on which one you happen to be in. Every genuine disagreement about "how many weeks" therefore reduces to two questions: which day counts as day one, and what happens to the days that do not divide evenly by seven.

That second question is the sneaky one. Very few real spans divide cleanly into whole weeks. Between two arbitrary dates you almost always get a whole number of weeks plus a remainder of one to six days, and different people park that remainder in different places. Some ignore it, some round up, some report it separately. Getting a consistent answer means deciding your rule in advance and applying it the same way every time.

Counting whole weeks between two dates

The mechanics are simple division. Count the calendar days between your two dates, then divide by seven. The whole-number part is the number of complete weeks, and the remainder, a value from zero to six, is the leftover days that did not make it into a full week. Forty-five days, for instance, is six weeks and three days, because six sevens are forty-two and three are left over.

The only real trap is the day count itself, because month lengths and the odd leap day make it easy to be off by one before you even start dividing. If you would rather not track which months have 30 days and whether February is playing its 29-day card, a days between two dates walkthrough covers the by-hand method, and a calculator will hand you the raw day count to divide.

1. Get the calendar day count

   Count the days from the first date to the second. Cross-month and leap-year spans are where errors creep in, so lean on a date tool if the range is wide.

2. Divide by seven

   The whole-number result is your count of complete weeks. Forty-five days divided by seven is six, so six full weeks have passed.

3. Keep the remainder

   Whatever is left, from zero to six, is the extra days beyond the last full week. Decide once whether you report it, drop it, or round up, and be consistent.

4. State it in plain words

   Say "six weeks and three days" rather than "about six and a half." Halves hide the remainder and make the next person recount from scratch.

Pregnancy: forty weeks that begin before conception

Nothing confuses week-counting quite like pregnancy, because the count starts before the pregnancy does. By long-standing convention, gestational age is measured from the first day of the last menstrual period, the LMP, and not from conception. Since ovulation and fertilisation happen roughly two weeks after that period begins, a person who is "six weeks pregnant" actually carries an embryo closer to four weeks old.

This is not a quirk doctors cling to for fun. The date of conception is almost never known precisely, whereas the first day of the last period is something most people can report. Anchoring to the LMP gives clinicians a consistent, observable starting line, even though it bakes in a two-week head start that has nothing to do with an actual embryo. It is the single most common source of the "wait, how far along am I really?" confusion.

From that starting line, a full-term pregnancy runs about 280 days, which is exactly 40 weeks. That figure comes from Naegele's rule, a nineteenth-century shortcut that estimates the due date as the LMP plus one year, minus three months, plus seven days. Counted from conception rather than the LMP, the same pregnancy is around 266 days, or 38 weeks. Same baby, different starting gun.

The three trimesters

The 40 weeks are grouped into three trimesters, each roughly three months long. The exact boundaries wobble by a week depending on which health authority you consult, but the common map looks like this.

Payroll: why some years hide an extra payday

Payroll runs on weeks too, and it is where the leftover-days problem stops being academic and starts affecting bank balances. Employers pay on one of four common rhythms, and the difference between them is not just cosmetic. It changes how many paychecks land in a year and how evenly they arrive.

The four common rhythms

Here is where the arithmetic bites. Fifty-two weeks multiplied by seven days is 364, but a calendar year has 365 days, or 366 in a leap year. That leftover day or two does not vanish; it accumulates. Pay every week and most years give you 52 paydays, but every five or six years the leftover days push a 53rd payday into the calendar. Pay every fortnight and the same drift produces a 27th paycheck roughly once a decade.

Semi-monthly and monthly schedules dodge the problem entirely by anchoring to dates rather than to a seven-day cycle. Twice a month is always 24 payments; once a month is always 12. The trade-off is that semi-monthly pay periods are not equal in length. The stretch from the 15th to the last day of February is shorter than the same span in July, so the paydays are even but the intervals are not.

The 53-weekday wrinkle

The same leftover day that gives payroll its extra payday has a broader cousin worth knowing. Because a 365-day year is 52 weeks plus one spare day, exactly one day of the week occurs 53 times that year instead of 52. In a leap year there are two spare days, so two weekdays get their 53rd appearance.

A concrete example: 2024 was a leap year that began on a Monday, so it contained 53 Mondays and 53 Tuesdays. This is why "there are 52 weeks in a year" is a useful approximation rather than a fact. There are 52 weeks and one or two stubborn extra days, and those days are the reason the calendar slowly rotates through the week from one year to the next.

Projects: sprints, week six of twelve, and ISO weeks

Project work leans on weeks because they map neatly onto human attention. A two-week sprint is the backbone of most agile teams: long enough to finish something meaningful, short enough that the finish line never feels distant. Counting sprints is just counting weeks in pairs, and "we are in Sprint 4" is a friendlier status report than a raw date.

Progress is often framed the same way. "Week six of twelve" tells everyone instantly that a project sits at its halfway point, without anyone doing date subtraction. The catch is that a casual project week and a formal calendar week are not the same object. When teams span time zones or need to line up with finance and HR systems, informal counting is not precise enough, and that is where ISO week numbers take over.

The ISO 8601 standard numbers every week of the year from 1 to 52 or 53, always starting on a Monday, with week 1 defined as the week containing the year's first Thursday. It gives "week 37" a single unambiguous meaning that anyone, anywhere, can look up, which is why it underpins so much scheduling software. Our week number tool will tell you the ISO week for any date, and ISO week numbers explained covers the Thursday rule and why some years even reach week 53.

Weeks or exact dates, and which you should use

Weeks are a summary, and like any summary they trade precision for clarity. For cadence and communication they are excellent; for contracts and deadlines they can quietly mislead. The right choice depends on whether you are describing a rhythm or pinning down a single moment.

A week is the only unit of time humans invented from scratch. It answers to no moon and no season, only to our need to know when the market opens. Small wonder we cannot agree on where it starts.

Once you start looking, week-counting is everywhere, each domain with its own quiet convention.

• Health keeps score in weeks: gestational age, vaccination schedules, and recovery timelines are almost always given that way.
• Finance runs on cycles: pay periods, interest windows, and many billing terms follow a weekly or biweekly rhythm.
• Work plans in weeks: sprints, notice periods, and project phases are all reported and tracked by the week.
• Education counts forward in weeks: semesters, reading weeks, and assignment deadlines all march to the same beat.
• Personal life feels the countdown: a wedding, a holiday, or a race feels most real when measured in weeks remaining.