THE METHOD, MADE CLEAR
A date count with visible rules.
Workdaycount counts calendar dates that match weekdays you select, within a start/end span and explicit endpoint rules. You can remove manually entered dates, then inspect the complete counted and skipped lists.
What “working day” means in this tool
The name is a shorthand for your selected schedule. Monday–Friday is the illustrative default, not a definition of a legal business day or everyone’s working week. Saturday and Sunday can be selected. All seven can be selected, and selecting none gives a valid count of zero.
No public-holiday calendar is downloaded or inferred from your country. A Monday holiday counts if Monday is selected and you do not manually exclude that date. Conversely, a manual Saturday exclusion changes nothing when Saturday is already unselected. The site does not decide whether a date is a holiday, an entitlement day or a permissible deadline.
Dates have no clock time here
Inputs are four-digit-year Gregorian dates in YYYY-MM-DD form, from 0001-01-01 through 9999-12-31. The RFC 3339 full-date definition documents the year-month-day representation. This tool accepts that date form only, without a time, offset or time-zone name.
The calculation walks civil dates using month lengths and leap-year rules. It does not add 24-hour timestamps or convert a local midnight to another time zone. A daylight-saving clock change therefore cannot create, remove or duplicate a date in the count. The result is a number of calendar dates, not a duration in elapsed hours.
The Gregorian rules are applied consistently throughout the supported range, including years before local adoption of that calendar. That is a proleptic Gregorian model, not a historical calendar-conversion service. Do not use it to interpret a document written under another historical calendar.
Decide how endpoints behave
The start must be on or before the end. Include start date and Include end date are independent switches. Turning one off removes that endpoint before the weekday and manual-date checks. It does not shift the named input date to a different day.
For a range whose start and end are the same date, there is only one date. Both inclusion switches must be on for it to remain eligible. If either is off, that date is skipped once under the endpoint rule. It is not counted once for the start and again for the end.
The supported full span is at most 3,660 calendar dates, measured before endpoint exclusions. A longer span is rejected rather than partially counted. If you split a longer period into separate calculations, ensure adjacent segments do not overlap or leave a date out; the tool does not combine projects for you.
Apply rules in a clear order
Every date in the full entered span receives one outcome. First, an excluded endpoint is skipped. Otherwise, an unselected weekday is skipped. Otherwise, a manually listed date is skipped. Every remaining date is counted. A skipped date is assigned just one reason, so the reason totals partition the span.
Full span = counted dates + endpoint skips + weekday skips + manual skips
This ordering also explains manual-exclusion review. A manual entry cannot remove an already excluded endpoint or an already unselected weekday a second time. It is labelled as not applicable for that reason. A valid manual date outside the full span is recorded as outside the range.
Worked example: the default two-week selection
19–30 October 2026, both endpoints included
The full span contains 12 calendar dates. Monday–Friday contributes ten selected weekdays; Saturday 24 October and Sunday 25 October are skipped. The example manually excludes Monday 2026-10-26, removing one otherwise selected date.
The final count is 9 dates. The skipped list has three dates: two unselected weekdays and one applied manual exclusion. The balance is 9 counted + 0 endpoint skips + 2 weekday skips + 1 manual skip = 12.
Turning off both endpoint switches also removes Monday 19 October and Friday 30 October. The manual exclusion remains applied, producing 7 counted dates. These example dates are fixed for reproducibility; they are not a live schedule or today’s date.
Deduplicate manual dates before removing them
Enter exclusions one per line, or separated by commas or whitespace. The same valid YYYY-MM-DD date entered twice becomes one unique exclusion. A duplicate-entry count records the repetition, but that date can reduce the selected count at most once.
For example, enter 2026-10-26 twice, 2026-10-24 once and 2026-11-01 once against the default range. There are four entries and three unique dates. Only 26 October applies. The Saturday is already outside the selected weekdays, and 1 November is outside the entered span. The result remains nine counted dates.
An invalid date such as 2026-02-30 is an input error even if it would be outside the range. It is not silently discarded. There may be up to 5,000 date entries including duplicates and at most 60,000 characters in the field. Empty manual input simply means no manual exclusions.
Leap days and year boundaries
The US Naval Observatory’s Gregorian leap-year explanation describes the divisible-by-four rule, with century years excluded unless divisible by 400. Thus 2000 has 29 February, while 1900 and 2100 do not. Invalid leap dates are rejected.
For an all-weekday selection from 2024-02-28 through 2024-03-01 with both endpoints included and no manual exclusions, the count is 3: Wednesday 28 February, Thursday 29 February and Friday 1 March. Excluding 29 February manually leaves two.
For 2026-12-31 through 2027-01-02, an every-day selection counts 3. A Monday–Friday selection counts 2: Thursday and Friday. The Saturday is skipped. No special holiday is assumed for 1 January.
Read the date audit, not just the total
The date audit offers All dates, Counted only and Skipped only views. It displays 50 rows per page to keep long ranges usable on a phone. A zero-row filter says no dates in this view; it is not a calculation error. Previous and Next stay within the available pages.
The summary’s manual review shows up to the first 50 unique exclusions and their application status. Complete text and CSV reports include every date and every unique exclusion review, regardless of the displayed filter or page. CSV uses a record_type column to distinguish summary, calendar-date and manual-exclusion-review records; it is a local report rather than an import format.
Copy report offers the same full text through a selectable field if clipboard access is unavailable. No report is sent to anyone by this site. The calculation does not connect to a calendar, request time-zone permissions, create events or keep a saved-project history.
Correct inputs without carrying stale results
A blank date, an impossible date, a reversed range or a range above the cap clears usable results and date rows and disables exports. Restore example returns both endpoints, the weekday selection and the manual date to the example. Reloading also starts with those defaults; there is no saved-query date state.
Keep the rule summary with any count you use elsewhere. This calculator does not interpret employment agreements, legal filing rules, holiday substitutions, business cut-off times or jurisdiction-specific deadline conventions. It makes an explicit civil-date selection reproducible.