Ask "how many days are in a month?" and everyone knows the answer is 28 to 31. But ask "how many *working* days are in a month?" and the confident answers dry up. That second number quietly drives payroll calculations, team capacity planning, project deadlines, and billing — and it swings more than most people expect, from as few as 19 to as many as 23 in a standard month.
Getting it right matters. Estimate a delivery on the assumption of 22 working days and then hit a month with 19, and your plan is already a tenth short before anyone has done anything wrong. This guide explains what a working day is, why the count varies so much, how to calculate it, and the averages worth memorising.
What counts as a working day
A working day — also called a business day — is usually a weekday, Monday through Friday, on which normal business operates. Weekends are excluded, and so are public holidays. That last exclusion is where things get local: holidays differ by country, region, and even industry.
So the working-day count for a month is: total days, minus weekend days, minus any public holidays that fall on a weekday. A business days calculator handles the counting, but understanding the moving parts helps you sanity-check the result and plan around it.
Why the number swings so much
Two forces push the working-day count around: how many days the month has, and — more importantly — which day of the week the month starts on.
A 31-day month that begins on a Monday packs in five full working weeks plus a little more, landing on 23 working days. The same length month starting on a Saturday wastes its first two days on the weekend and yields fewer. February in a non-leap year, at 28 days starting on the right day, can drop to just 20 — and holidays can pull any month lower still.
| Scenario | Working days |
|---|---|
| 31-day month starting Monday | 23 |
| 30-day month starting midweek | 21 to 22 |
| 28-day February starting Saturday | 20 |
| Any month with two weekday holidays | 2 fewer than above |
The averages worth knowing
Across a full year, the numbers settle into useful averages. A common year has 365 days; subtract 104 weekend days and you are left with 261 weekdays. A leap year has 262. Public holidays then trim that down — many countries land somewhere around 250 to 253 actual working days per year.
Divide the weekday total by 12 and you get an average of roughly 21.75 working days per month. This is the figure payroll systems often lean on to keep monthly salaries even, and it is a handy mental anchor — though no individual month actually contains 21.75 days.
How to count a month's working days by hand
Start with the total days in the month
28, 29, 30, or 31 — establish the length first.
Subtract the weekend days
Count the Saturdays and Sundays. Most months have eight or nine weekend days depending on how the dates line up.
Subtract weekday public holidays
Only holidays that fall Monday to Friday reduce the count — a holiday landing on a Saturday does not, since that day was already excluded.
The remainder is your working-day count
What is left is the number of business days you can actually plan around.
The holiday step is the one people forget. A holiday that falls on a weekend is "wasted" from a day-off perspective and does not change the working-day maths at all — which is why some months feel like they have more days off than they really grant.
Calendar days vs working days for planning
When you promise something "in 20 days", the gap between calendar days and working days is enormous. Twenty working days is a full four-week stretch of effort; twenty calendar days is under three weeks and includes the weekends. Confusing the two is a classic estimation error, explored further in business days vs calendar days.
✓ The upside
- Working days reflect actual available effort, so estimates are more realistic
- Payroll and billing align with when work genuinely happens
- Capacity planning based on working days avoids over-promising
- It naturally accounts for weekends and holidays that calendar counts ignore
✕ The catch
- The count varies month to month, so you cannot use one fixed number
- Holidays differ by location, complicating multi-region teams
- It ignores part-time schedules, leave, and sick days, which further reduce real capacity
- Cross-border projects face different holiday calendars simultaneously
A month is a fixed box on the calendar. The working days inside it are what you actually have to spend.
Where the working-day count really matters
- Payroll and salaries — especially for daily-rate or hourly staff, where the exact count changes the pay.
- Team capacity planning — multiply working days by headcount to get available person-days for the month.
- Project deadlines — turning "40 working days of effort" into a real calendar end date, covered in planning a project timeline.
- Service-level agreements — "we respond within 3 business days" needs an agreed definition of business day.
- Invoicing and payment terms — "net 30 days" versus "30 business days" are meaningfully different promises.
A note on multi-region teams
The moment a team spans countries, "working days" fragments. A US public holiday is a normal working day in India, and vice versa. For distributed teams, capacity planning has to layer each region's holiday calendar separately — the shared working-day count is only the intersection where everyone is actually at their desk.
A worked example: quoting "30 working days"
Suppose you promise a client "30 working days". Starting on the first of a month with 22 working days, you use all 22, then carry 8 into the next month. If that month has 20 working days, you finish on its 8th working day — which, once the weekends in between are added back, can land nearly seven calendar weeks after you began. A client who heard only "30 days" might reasonably have expected it in half that time.
This gap is exactly why explicit language matters in contracts and estimates. Stating both the working-day count *and* the expected calendar end date removes the ambiguity, and it protects you when a run of public holidays quietly eats into the month's capacity. "Roughly 30 working days, so delivered by the 12th of next month" is a promise both sides can actually check.
- Working days are weekdays minus public holidays that fall on a weekday.
- A standard month ranges from about 19 to 23 working days, driven mostly by which weekday it starts on.
- A common year has 261 weekdays (262 in a leap year), averaging roughly 21.75 working days per month.
- Only weekday holidays reduce the count — those on weekends change nothing.
- For multi-region teams, working days must be counted against each region's own holiday calendar.