WEEKS in Zoho Sheet: whole weeks versus Monday-week boundaries

Date and Time Beginner to Intermediate Zoho Sheet

Calculate the weeks between two dates with Zoho Sheet WEEKS modes 0 and 1, with practical date-boundary examples.

Verification status: Official documentation referenced; example outcomes independently reasoned or arithmetically checked where stated. Not executed in Zoho Sheet. How formula examples are checked

Zoho Sheet WEEKS: count elapsed weeks or crossed calendar weeks

Quick answer: =WEEKS(C2;D2) counts whole seven-day blocks between two dates (mode 0, the default). =WEEKS(C2;D2;1) counts the difference between their Monday–Sunday calendar-week buckets. For Thursday January 1 to Monday January 5, 2026, mode 0 independently predicts 0 complete weeks, but mode 1 predicts 1 calendar-week boundary crossed. This contrast is the most important decision when using WEEKS.

Use WEEKS for interval reporting and scheduling rather than assigning a week number to a date; use WEEKNUM / WEEKNUM_ADD for the latter. The two purposes are not interchangeable. An interval of four days can cross one calendar-week boundary, while another interval of six days can stay inside a single Monday–Sunday week.

Documented Zoho syntax

=WEEKS(start_date; end_date; [mode])

Zoho’s official WEEKS page specifies:

Argument Required? Description Example
start_date Yes Date from which the interval begins. C2
end_date Yes Date at the interval’s end. D2
mode No 0 counts whole seven-day weeks, 1 counts Monday–Sunday calendar-week differences. Defaults to 0. 1

The same page expresses mode 0 as INT(number_of_days_difference / 7). That detail matters for intervals shorter than seven days and potentially for reversed dates: mathematical INT rounds down, not necessarily toward zero. Negative/reversed inputs remain a native Zoho test case; examples below use chronological start/end dates.

Mode 1 is not a claim that the start and end are a full week apart. It identifies the Monday-through-Sunday bucket containing each date and returns how many Monday boundaries separate those buckets. It can change when you shift an interval by a single day, even if the number of elapsed days stays constant.

Create the sample interval worksheet

Use the attached calendar-boundaries-practice.csv, but first convert ISO-formatted date text to genuine spreadsheet date values in your chosen Zoho locale. Put its header row in A1:G1. Use C for interval start and D for interval end; column B contains separate report dates for companion week-number tutorials.

Row ID C: Start D: End Elapsed calendar days
2 W01 2026-01-01 2026-01-05 4
3 W02 2026-01-05 2026-01-12 7
4 W03 2026-01-06 2026-01-11 5
5 W04 2024-02-27 2024-03-05 7
6 W05 2025-12-31 2026-01-01 1
7 W06 2025-12-28 2025-12-29 1
8 W07 2026-01-01 2026-01-31 30
9 W08 2026-10-11 2026-10-11 0

Step-by-step: compare both modes

  1. Add H1 Whole weeks (0), I1 Monday week difference (1) and J1 Elapsed days.
  2. Enter =WEEKS(C2;D2) in H2. Its omitted optional argument means mode 0.
  3. Enter =WEEKS(C2;D2;1) in I2.
  4. Enter =D2-C2 in J2 to check ordinary elapsed-day arithmetic. Format H:J as integers.
  5. Copy H2:J2 through row 9; cross-check the values against the independent standard-library calendar predictions, not a claimed native Zoho execution:
Row Start → End Days Mode 0 whole weeks Mode 1 Monday week difference
2 Jan 1 → Jan 5, 2026 4 0 1
3 Jan 5 → Jan 12, 2026 7 1 1
4 Jan 6 → Jan 11, 2026 5 0 0
5 Feb 27 → Mar 5, 2024 7 1 1
6 Dec 31, 2025 → Jan 1, 2026 1 0 0
7 Dec 28 → Dec 29, 2025 1 0 1
8 Jan 1 → Jan 31, 2026 30 4 4
9 Oct 11 → Oct 11, 2026 0 0 0

Example 1 — only four days elapsed but a week boundary crossed. January 1, 2026 is a Thursday. January 5 is a Monday in the next Monday–Sunday week. Mode 0 says there are zero complete seven-day blocks; mode 1 sees one Monday boundary.

Example 2 — a Sunday/Monday handoff. December 28, 2025 is Sunday, and December 29 is Monday. Although those dates are only one day apart, mode 1 independently predicts 1, while mode 0 predicts 0. Do not present a mode-1 result as the number of weeks someone has worked.

Example 3 — cross-year, but no Monday boundary. December 31, 2025 and January 1, 2026 belong to the same Monday–Sunday week. Mode 1 independently predicts 0 even though YEAR differs. This is why subtracting calendar-year week numbers is a poor replacement.

Zoho’s own reference gives =WEEKS("2/5/2020";"7/8/2020") → 22. Its text dates use a particular month/day interpretation; in a workbook, use actual date cells or DATE constructors instead of relying on ambiguous regional text.

Advanced application 1: flag a new reporting bucket

A team loads orders into C2:D9, where each row contains the first and last order date for a job. To mark any job that spans more than one Monday–Sunday bucket, independently evaluate:

=IF(WEEKS(C2;D2;1)>0;"Crosses week boundary";"Single week")

For row 2, the expected text is Crosses week boundary; for row 4 (January 6–11, 2026), expected text is Single week. This is useful for a weekly dashboard, but it does not mean a crossed bucket represents a full week of billable work.

Advanced application 2: separate full weeks from extra days

If a job is 30 days long, whole weeks and extra days should be reported separately rather than rounded to a misleading fifth week. With C8 = January 1 and D8 = January 31, 2026:

=WEEKS(C8;D8;0)

independently predicts 4 full weeks. The additional days formula:

=(D8-C8)-7*WEEKS(C8;D8;0)

independently predicts 2 extra days. Combine as a caption if needed:

=WEEKS(C8;D8;0)&" weeks, "&((D8-C8)-7*WEEKS(C8;D8;0))&" days"

Expected label: 4 weeks, 2 days. For reverse date order, validate intended sign convention before applying this formula; do not assume symmetric behavior for mathematical floor.

Errors, edge cases and auditing

  • Mode omitted: Defaults to zero, not mode one. If a colleague expects calendar-week boundaries, explicitly supply ;1.
  • End before start: Zoho states INT(days/7) for mode 0, but the native behavior for reversed dates and date serial systems was not executed during this research. Define whether negative intervals should be allowed, and consider an input rule requiring end_date >= start_date.
  • Inclusivity: The reference discusses difference between dates, not counting both endpoints as working days. If a policy calls for an inclusive interval, account for that explicitly before calculating weeks.
  • Dates stored as text: A CSV may display a recognizable date but still import as text. Check cell format, locale, and whether subtracting D2-C2 yields a day count.
  • #VALUE!: Zoho lists mismatched types as a typical cause; inspect date fields and numeric mode input.
  • #NAME!: Confirm spelling WEEKS and your formula separators. Do not substitute WEEKNUM; it answers a different question.
  • #REF!: Check for deleted or moved references. An error in a referenced DATE calculation will propagate.
  • Holiday/workday counts: WEEKS does not claim to exclude weekends or holidays. Use separately documented NETWORKDAYS / WORKDAY guides for business-day scheduling, subject to their independent validation.

Excel and other spreadsheet differences

Microsoft’s date difference guide demonstrates DATEDIF(...,"d")/7 for elapsed weeks in Excel. This can produce a fractional number, whereas Zoho’s WEEKS mode 0 uses the integer number of complete weeks according to its own help. To model whole seven-day weeks in an Excel workbook with chronological dates, =INT((D2-C2)/7) is an explicit alternative. It is not evidence that Microsoft Excel recognizes a function named WEEKS with Zoho’s two modes. For mode 1, compute the difference between the two Monday week-start dates, not simply the difference between WEEKNUM results around January 1.

Zoho’s browser reference uses semicolons; Excel examples often use commas. Zoho’s desktop beta statement broadly reports 400+ functions but does not confirm this individual function’s platform parity or a historical first-supported version. No mobile, offline, account-tier, or legacy spreadsheet runtime has been independently tested.

Official reference and verification

Verification status: Official documentation checked; example outcomes were independently reasoned or arithmetically checked where applicable. Not executed in Zoho Sheet.

  • No genuine Zoho Sheet screenshots are included; this guide does not use mock application images.