HR & LegalDates

Counting working days for leave, deadlines and deliveries: three mistakes people make

2026-09-19 · 3 min read

Deadlines, delivery estimates, and leave requests frequently rely on the concept of working days. Despite how common this metric is in contracts and human resources policies, people routinely miscalculate the final date. These calculation errors lead to missed deadlines, late fees, and scheduling conflicts.

Understanding the standard conventions for counting time helps eliminate ambiguity. Below are three common mistakes people make when calculating working days and how to avoid them.

Mistake 1: Confusing calendar days with business days

A standard week contains seven calendar days but only five business days. When a contract stipulates a response time of "10 days," it is crucial to clarify which type of day applies.

If the agreement means calendar days, you simply count forward, including weekends. If it means business days, weekends are excluded, meaning a 10-business-day period spans two full calendar weeks. In legal and corporate contexts, "days" defaults to calendar days unless the document explicitly states "business days" or "working days." Assuming otherwise is a frequent source of missed obligations.

Mistake 2: Counting the starting day incorrectly

The most common mathematical error in date calculation involves the starting point. When an event occurs, people often count that exact day as day one. However, standard business convention dictates that the count begins on the day after the triggering event.

Consider a policy that requires action "within 5 business days." If you receive a request on Thursday, Thursday is day zero. Friday counts as day one. The weekend is skipped. Monday is day two, Tuesday is day three, Wednesday is day four, and Thursday of the following week is day five. The deadline lands exactly one calendar week later, not on the preceding Wednesday. Using Date Calculator makes this calculation easier, as it offers a specific option to either count or skip the first day based on your needs.

Mistake 3: Ignoring local public holidays

Business days exclude public holidays, but holidays are not universal. They vary wildly by country, region, and sometimes even by industry or municipality.

A vendor in another country operates on a different holiday schedule. If a project requires five working days, and their location observes a national holiday on Monday, the delivery pushes back by one calendar day. You cannot map your own local calendar onto an international partner. When computing deadlines across borders, Date Calculator automatically skips weekends for you, but you must manually subtract the relevant public holidays according to the local calendar of the party doing the work.

Month-based terms versus day counts

Confusion also arises when converting between months and days. "One month" and "30 days" are not interchangeable terms in business.

A deadline of "one month" from January 15 falls on February 15. A deadline of "30 days" from January 15 falls on February 14. The gap is largest around February: a 30-day count that starts on February 1 ends on March 3, while one month ends on March 1. Contracts should stick to one measurement system to maintain clarity. If you need to quickly check these differences, adding or subtracting months in Date Calculator will automatically apply month-end corrections to give you the precise date.

The importance of writing explicit dates

The simplest way to prevent calculation errors is to avoid relative timelines in external communication. While a contract template might mandate a "14-business-day review period," the cover email should translate that into a concrete date.

Instead of writing "Please reply in five working days," write "Please reply by close of business on Thursday, October 15." This removes all ambiguity. It forces the sender to do the calculation upfront and gives the recipient a fixed target, rendering any misunderstandings about holidays or weekends irrelevant.