TL;DR: A calendar week is seven dates, weekend included. A business-day count skips weekends and often holidays, so “two weeks” and “ten business days” are not the same promise. State both numbers when an email could be read either way, and date the calendar-week side with the weeks from today calculator.
Saturday still exists inside a calendar week
From Monday, 2 November 2026 through Monday, 16 November 2026 is exactly two calendar weeks, 14 civil days. Inside that span you pass two Saturdays and two Sundays. If your office is closed those days, you still lived through them. A deadline written as “two weeks from Monday the 2nd” lands on Monday the 16th even if the 14th and 15th were empty of staff. The empty days do not pause the calendar. They only pause the work.
Five-day thinking compresses the picture. People multiply weeks by five and announce “ten working days” as if that phrase were a translation of two weeks. It is a different measurement that happens to use the word week in the same meeting. Ten working days from Monday, 2 November, with no holidays, lands later than Monday the 16th, because the weekends are skipped rather than counted. If you needed the 16th, the working-day count overshoots it. If you needed ten staffed days of effort, the calendar-week count undershoots it. Pick the sentence that matches the obligation.
A holiday deletes a business day and leaves the week intact
Imagine a public holiday on Wednesday inside one of those two weeks. The calendar span from 2 November to 16 November is still 14 days and still two weeks. The count of days the office is open drops by one. Anyone who promised “ten business days of processing” now has nine open days in that fortnight unless they extend past the 16th. Anyone who promised “a decision within two weeks” still owes the decision by the 16th, holiday or not, unless the policy explicitly says business days or “excluding public holidays.”
The calculator will not know your holiday list. It should not. Feed it a week count and an anchor; it returns a civil date. Then look at a holiday calendar yourself and decide whether the promise was civil or staffed. Adding “one extra week because of the holiday” without reading the policy doubles the wait for the customer and may still be the wrong repair. Sometimes the repair is one extra open day, which changes the weekday. Say that plainly.
An SLA that says “two weeks”
A vendor ticket promises a root-cause note “within two weeks of the Monday it was opened.” Opened Monday, 2 November 2026, the note is due Monday, 16 November 2026. The support lead who translates this to “ten business days, so the 20th” has rewritten the contract in a hallway. If the contract truly says weeks, the 16th is the date. If the contract says ten business days, the 16th is a misunderstanding and the later date is the one to compute with a business-day counter, not with a week adder.
Quote the source words in the ticket comment: “SLA text: two weeks. Anchor: Mon 2 Nov 2026. Due: Mon 16 Nov 2026.” Future you, and the customer, can see you did not invent a unit. If legal later confirms the master agreement says business days, you change the comment and the date together. You do not leave the old date under a new unit label.
Counting weekdays on your fingers drops dates
A common hallway method is to tap Monday through Friday twice and declare the second Friday the end of “two weeks.” From Monday, 2 November, two sets of weekdays end on Friday, 13 November, if you start tapping on the opening Monday and get confused about whether it counts. Or they end on Friday, 13 November versus Friday, 20 November depending on whether the opening day was tap one. Finger counts smuggle an inclusive-day argument into what looked like a week question. The week question has a boring answer: add 14 days, land on the same weekday, which is Monday, 16 November. The Friday you tapped is a different promise, “end of the second workweek,” and it should be labeled as a Friday on purpose.
If the stakeholder actually wants close of business Friday, choose Friday knowingly. Two calendar weeks from Monday is not that Friday. You might set an internal finish of Friday, 13 November so the customer-facing Monday, 16 November still holds. That internal Friday is 11 days after the Monday, not 14. Write “internal Fri 13 Nov; customer due Mon 16 Nov (2 calendar weeks).” The gap between them is the weekend you are using as buffer, not a mysterious calculator bias.
Put both figures in the mail you send
When readers may come from legal, from engineering, and from a storefront, one number will be misread. Use a sentence with both: “The calendar deadline is Monday, 16 November 2026, two weeks after Monday, 2 November. That span contains 10 weekdays if no holiday falls inside it, and fewer if one does.” You have not claimed the SLA is ten business days. You have shown the overlap so nobody has to do the conversion in anger.
Do the reverse when the source text is business days. “Ten business days from Monday, 2 November 2026, skipping weekends and listing the holiday we excluded, falls on [that computed date]. This is not the same day as two calendar weeks (16 November).” The contrast belongs in the email because it is exactly where arguments start. Leaving it implicit asks every reader to redo your arithmetic in a different unit.
Name which clock the deadline uses
Before you calculate, circle the noun in the source: weeks or business days. Then run only that noun’s method. Calendar weeks go through the homepage calculator and keep their weekends. Business days go through a work calendar that knows your holidays. Publishing one date under the other noun is how “two weeks” becomes a dispute. The math in each system is stable. The unstable part is the label you attach when you hit send.
