120 Days Is How Many Weeks

You're staring at a calendar. Maybe it's a notice period at work. On the flip side, maybe it's a project deadline. Maybe you're counting down to a trip, or counting up from a surgery date. Whatever the reason, you need to know: 120 days is how many weeks?

The short answer: 17 weeks and 1 day. Because of that, or 17. 14 weeks if you prefer decimals.

But you didn't come here for a calculator. You came here because that number — 120 — keeps showing up in contracts, medical timelines, visa rules, and project plans. And knowing the exact* week count changes how you plan.

What 120 Days Actually Looks Like in Weeks

Let's get the math out of the way first.

120 ÷ 7 = 17.142857...

That's 17 full weeks. Plus one extra day.

If you start counting on a Monday, 120 days later lands on a Tuesday. Start on a Friday? So you'll hit 120 days on a Saturday. On the flip side, the day of the week shifts by one. Always.

Why the decimal matters

People round to 17 weeks and call it done. That said, that's fine for rough estimates. But if you're calculating a notice period, a visa overstay, or a medical milestone, that extra day isn't rounding error — it's the difference between compliant and in violation.

I've seen freelancers lose a week's pay because they thought "about 17 weeks" meant "17 weeks exactly." It doesn't.

Where 120 Days Shows Up in Real Life

This isn't a random number. It appears in specific, high-stakes contexts.

Employment and notice periods

In many countries, 120 days is a standard long-notice period for senior roles. Which means four months. That's 17 weeks + 1 day of transition planning, knowledge transfer, and — let's be honest — awkward goodbye lunches.

If your contract says "120 days' notice," don't count 17 weeks and stop. On the flip side, count the actual calendar days. HR will.

Medical and pregnancy milestones

120 days is roughly 17 weeks gestation. In real terms, that's the start of the second trimester for many counting methods. It's also when certain screenings happen, when "quickening" often begins, and when many people announce publicly.

But here's the thing: medical weeks aren't calendar weeks. Obstetric weeks count from LMP (last menstrual period), not conception. So "17 weeks pregnant" might only be 15 weeks since conception. The 120-day mark? That's a different number entirely depending on who's counting.

Visa and immigration rules

The Schengen 90/180 rule gets all the attention. But some long-stay visas, digital nomad permits, and residency applications use 120-day thresholds — either as a maximum stay without registration, or a minimum physical presence requirement.

Miss the 120-day mark by one day? Your application gets rejected. No appeal. No "close enough.

Project management and sprints

Agile teams love two-week sprints. Think about it: the ones who don't... That half-sprint at the end? Practically speaking, smart project managers build that extra day in as buffer. On top of that, 5 sprints. 120 days = 8.Here's the thing — it's where scope creep goes to die. ship late.

Financial quarters

120 days is almost exactly one financial quarter (90-92 days) plus a month. On top of that, it's the awkward in-between period when you're reporting Q1 results but already halfway through Q2 planning. Finance teams hate it.

How to Count 120 Days Without Losing Your Mind

Don't count on your fingers. Use the right tool for the job.

The spreadsheet method

=START_DATE + 120

That's it. Excel, Google Sheets, LibreOffice — they all handle date math natively. No formulas needed beyond addition.

Want to exclude weekends?

For more on this topic, read our article on how many years is 50000 hours or check out how many feet is 93 inches.

=WORKDAY(START_DATE, 120)

Want to exclude holidays too? Add a holiday range as the third argument.

The calendar method (for visual thinkers)

Print a 4-month calendar view. Also, put a dot on day 1. Count forward 120 dots.

Tedious? Yes. But sometimes seeing the weekends, holidays, and "blackout dates" laid out visually catches things a formula misses — like the company retreat that falls on day 87, or the three-day weekend that shifts your deadline.

The command line (for developers)

date -d "+120 days" "+%Y-%m-%d"

Works on Linux, macOS, WSL. Windows PowerShell:

(Get-Date).AddDays(120).

### The "count back" trick

Sometimes it's easier to work backward. If you must* be done by October 15, when do you start?

=END_DATE - 120

Same math. Different perspective. Often reveals that you should have started last week.

## Common Mistakes People Make With 120-Day Calculations

### Mistake 1: Confusing business days with calendar days

120 calendar days = 17 weeks + 1 day  
120 business days = 24 weeks (roughly 5.5 months)

That's a massive* difference. Contracts sometimes specify one, sometimes the other. Sometimes they don't specify at all — and that's when lawyers get paid.

If a contract says "120 days" without qualification, courts in most jurisdictions interpret that as calendar days. But don't bet your mortgage on it. Get it in writing.

### Mistake 2: Forgetting leap years

120 days starting January 15 hits May 14 in a normal year. May 15 in a leap year.

Does it matter? Day to day, for most things, no. For regulatory filings, tax deadlines, or statute of limitations? Yes. One day late is late.

### Mistake 3: Counting the start day as "day 1" vs "day 0"

This is the classic fencepost error.

- Inclusive counting: Day 1 = start date. Day 120 = 119 days later.
- Exclusive counting: Day 1 = the day after* start date. Day 120 = 120 days later.

Legal and medical contexts usually use inclusive counting. Project management usually uses exclusive. Because of that, programming languages? Almost exclusively exclusive (zero-indexed).

When in doubt, write out the actual dates. "From March 1 through June 28 inclusive" leaves zero ambiguity.

### Mistake 4: Assuming all months are 30 days

"Four months" ≠ 120 days. Not usually.

- Jan + Feb + Mar + Apr = 120 days (non-leap) / 121 (leap)
- Feb + Mar + Apr + May = 121 / 122
- Jul + Aug + Sep + Oct = 122

Only January through April hits 120 exactly (in non-leap years). Every other four-month combo is off by 1-2 days.

### Mistake 5: Ignoring time zones

If your 120-day deadline is "end of day" — whose end of day? 

A team split between

…New York, London, and Tokyo. If the contract merely says “end of day” without anchoring it to a specific zone, the same calendar date can represent three different moments in universal time. A submission made at 23:59 JST on the deadline day is already 08:59 UTC the next calendar date — potentially a full day late for a party operating in Greenwich Mean Time.

**How to avoid the trap**

1. **Specify the zone in the contract** – e.g., “all deadlines are 17:00 Eastern Time (UTC‑5/UTC‑4 depending on daylight‑saving).”  
2. **Use an unambiguous timestamp format** – ISO 8601 with offset, such as `2025-05-14T17:00:00-04:00`.  
3. **put to work libraries that understand zones** – In Python, `pytz` or the built‑in `zoneinfo`; in JavaScript, `Intl.DateTimeFormat` with `timeZone`; in SQL, `AT TIME ZONE`.  
4. **Test edge cases** – Run your date‑addition logic across the DST transition dates (second Sunday in March and first Sunday in November in the U.S.) to confirm you aren’t accidentally gaining or losing an hour.  
5. **Document the reference point** – If you’re counting from a timestamp that already includes a zone, make clear whether you add 120 *24‑hour* periods or 120 calendar* days (the latter may shift the wall‑clock time when DST changes).

---

### Quick‑reference checklist for a reliable 120‑day calculation

| Step | Action | Tool / Example |
|------|--------|----------------|
| 1 | Define **calendar vs. business** days | Contract clause; `NETWORKDAYS` in Excel |
| 2 | Choose **inclusive or exclusive** counting | Write out start + end dates to verify |
| 3 | Account for **leap years** | Use a date library; manual check if Feb 29 lies in range |
| 4 | Verify **month lengths** | Avoid the “4 × 30 days” shortcut; sum actual month days |
| 5 | Lock in a **time zone** | Store timestamps with offset; convert to UTC for comparison |
| 6 | Validate with a **visual calendar** | Highlight weekends/holidays; spot blackout dates |
| 7 | Cross‑check with a **command‑line or script** | `date -d "+120 days"` or PowerShell equivalent |
| 8 | Review for **fencepost errors** | Ask: “Is day 1 the start date or the day after?” |
| 9 | Get it **in writing** | Explicit wording prevents costly disputes |
|10| **Test** with known edge cases (leap year, DST shift, year‑end) | Automated unit test or spreadsheet scenario |

---

### Conclusion

A 120‑day interval seems simple at first glance, but the devil hides in the assumptions we make about inclusivity, leap years, month lengths, business versus calendar days, and—most subtly—time zones. By spelling out each assumption in the agreement, confirming it with a concrete date list or a reliable script, and anchoring every deadline to an unambiguous timestamp, you turn a potential source of litigation into a routine, repeatable calculation. Because of that, in short: **clarity plus verification equals confidence**. When you can point to a specific calendar view, a tested command, and a contract clause that leaves no room for interpretation, you’ve done more than just count days—you’ve protected the timeline itself.