How many hours do you actually work in a month?
Sounds like a simple question. But ask five people and you'll get five different answers — and at least three of them will be wrong.
I've seen freelancers undercharge by thousands because they used a bad formula. Even so, i've seen HR teams build entire payroll models on a number that doesn't exist in reality. And the "standard" number floating around — 160 hours — is a myth. A convenient lie we tell ourselves because the math is clean.
Here's the short version: a typical full-time month is closer to 173 hours. But "typical" is doing a lot of heavy lifting there.
Let's break down where the numbers come from, why they shift, and how to calculate the one that actually applies to you.
What Is a Work Month, Really?
Most people start with 40 hours a week. and plenty of other places. Clean. And s. Easy. On the flip side, multiply by four weeks and you get 160. That's the standard full-time baseline in the U.Wrong.
A month isn't four weeks. That's why it's 4. 33 weeks on average. Sometimes 4.Even so, 43. February laughs at your four-week assumption.
The actual math
Forty hours a week times 52 weeks a year equals 2,080 hours. Divide that by 12 months and you get 173.33 hours per month.
That's your baseline. Not 160. Not 168.173.33.
But almost nobody works 173.33 hours every month. The calendar doesn't cooperate. January might have 23 workdays. February might have 20. August might have 22 — but two of them are holidays where I live.
Workdays vs. hours
Some countries and contracts define things in days, not hours. The math shifts:
- 5-day workweek × 52 weeks = 260 workdays a year
- 260 ÷ 12 = 21.67 workdays per month on average
- At 8 hours a day, that's the same 173.33 hours
But again — holidays, vacation, sick leave. The "on paper" number and the "on timesheet" number rarely match.
Why It Matters (And Where It Goes Wrong)
You might be thinking: Okay, so the number is 173-ish. Why does the decimal matter?*
It matters when money's involved.
Freelancers and contractors
Say you charge $100/hour. That said, you quote a monthly retainer based on 160 hours. That's $16,000.
But the client expects 173 hours of availability. You just gave away 13 hours — $1,300 — because you used the wrong denominator.
Flip it: you quote based on 173 hours. The month has 20 workdays (160 hours). Which means client feels shorted. You look like you overpromised.
Either way, trust erodes.
Payroll and budgeting
HR teams build annual salary models on 2,080 hours. That's fine for exempt employees. But for hourly? For overtime thresholds? For PTO accrual calculations?
If your payroll system assumes 160 hours/month but the month has 184 work hours (hello, March with zero holidays), your accrual rates drift. Your budget drifts. By December, you're explaining a variance nobody saw coming.
Project planning
"Three months of work" means wildly different things depending on your starting month.
- Jan–Mar: ~520 hours (minus holidays)
- Jun–Aug: ~520 hours (minus vacations)
- Nov–Jan: ~480 hours (thanksgiving, christmas, new year)
Same "three months.On top of that, " Forty hours of difference. That's a full work week. Practical, not theoretical.
How It Works: Calculating Your Real Number
Stop guessing. Here's how to get the number that actually applies to your situation.
Step 1: Start with the annual baseline
2,080 hours = 40 hrs/week × 52 weeks
This assumes:
- No unpaid time off
- No holidays
- Perfect 5-day weeks all year
Nobody lives here. But it's the anchor.
Continue exploring with our guides on what is the symbol for inches and how many dimes in 5 dollars.
Step 2: Subtract paid holidays
U.S. federal holidays: 11 days × 8 hours = 88 hours
Some companies observe more. Some less. Check your actual calendar.
Step 3: Subtract PTO (vacation + sick)
Standard U.S. package: 15 days vacation + 5 days sick = 20 days × 8 = 160 hours
Europe? Now, often 25–30 days vacation alone. That's 200–240 hours gone before you blink.
Step 4: Do the math
2,080 – 88 – 160 = 1,832 actual work hours per year
Divide by 12 = 152.67 hours/month average
That's your real* average. Not 173. Not 160. 153.
But — and this is critical — no single month hits 153. Some hit 120. Some hit 184. The average is a planning tool, not a prediction.
Step 5: Build a monthly calendar (the only way to be precise)
| Month | Workdays | Holidays | Net Days | Hours @ 8/day |
|---|---|---|---|---|
| Jan | 23 | 1–2 | 21–22 | 168–176 |
| Feb | 20 | 1 | 19 | 152 |
| Mar | 23 | 0 | 23 | 184 |
| Apr | 22 | 0–1 | 21–22 | 168–176 |
| May | 23 | 1 | 22 | 176 |
| Jun | 22 | 1 | 21 | 168 |
| Jul | 23 | 1 | 22 | 176 |
| Aug | 22 | 0 | 22 | 176 |
| Sep | 22 | 1 | 21 | 168 |
| Oct | 23 | 1 | 22 | 176 |
| Nov | 22 | 2–3 | 19–20 | 152–160 |
| Dec | 23 | 2–3 | 20–21 | 160–168 |
Build this once. Update it yearly. Use it for every quote, every
estimate, and every resource allocation meeting.
Applying the Data: From Spreadsheet to Strategy
Knowing your hours is useless if you don't use them to drive decision-making. Here are three ways to apply these precise numbers to your workflow.
1. The "Buffer" Method for Project Deadlines
Never schedule a project to end on a Friday in December if you haven't accounted for the holiday dip. If a project requires 500 hours of work, don't divide by 173 (the standard "month" math). Divide by 153 (your real average).
If you use the standard math, you'll think the project will take 2.2 months. That 0.If you use the real math, it will take 3.8 months. 4-month difference is the difference between hitting a deadline and missing it by two weeks.
2. Capacity Planning for Teams
When assigning tasks to a team, stop thinking in "headcount" and start thinking in "available hours." If you have a developer who is taking two weeks of vacation in July, their capacity for July isn't 176 hours—it's 96.
If you plan your sprint based on a full 40-hour week for every person, your sprint will fail. Use the monthly calendar to adjust your velocity expectations before the month even begins.
3. Budgeting and Profitability
For agencies and service providers, "hours" are "revenue." If you bill a client for a fixed monthly retainer based on a standard 173-hour month, but your team is actually only working 153 hours due to holidays and PTO, your margins are thinner than you realize.
Accurate hour tracking allows you to see the true cost of a project. It helps you realize that a "low-margin" project might actually be a "loss-leader" simply because you failed to account for the seasonal dip in labor availability.
Conclusion: Precision is a Competitive Advantage
Most project managers and business owners operate on "vibes" and "averages." They assume every month is a monolith of productivity, and they act surprised when the calendar intervenes.
By moving away from the theoretical 173-hour month and embracing the reality of your specific calendar, you stop reacting to variances and start predicting them. You gain the ability to set realistic deadlines, manage client expectations with confidence, and protect your profit margins from the inevitable ebb and flow of the year.
Stop guessing. Day to day, start counting. The calendar is already written; it's time you started reading it.
