How Many Working Hours a Month?

A full-time employee working 40 hours per week logs between 160 and 184 working hours per month, depending on how many weekdays the calendar gives you. The annual average is 173 hours per month, calculated by dividing 52 weeks by 12 months to get 4.33 weeks, then multiplying by 40 hours. For payroll budgeting, labor cost projections, and scheduling coverage, that 173-hour benchmark is the figure most managers rely on, while the actual monthly count can swing by 24 hours in either direction based purely on calendar math.

The Math: How to Calculate Monthly Working Hours

Start with one fact: a year has 52 weeks and 12 months. Divide 52 by 12 and you get 4.333 weeks per month on average. Multiply by a 40-hour workweek and you arrive at 173.3 working hours per month as the annual average. Most owners round that to 173 for day-to-day budgeting or use 2,080 annually (52 times 40), then divide by 12 when they need a consistent monthly figure for salary conversions or cost comparisons.

That average is useful for annual plans. For a payroll period that actually lands in a specific month, you want the real weekday count for that month, because it varies enough to matter on a tight margin.

Here is the full 2026 breakdown for a Monday-through-Friday, 40-hour schedule. These are raw weekday counts before any paid holidays are removed:

Subtract paid company holidays to get scheduled hours. Most U.S. employers observe between 6 and 11 paid holidays per year, reducing the annual total by 48 to 88 hours. November and December both look shorter in practice once Thanksgiving and Christmas are removed from the raw weekday count.

Part-time schedules scale the same way. A 20-hour-per-week employee averages 86.7 hours per month (4.333 times 20). A 24-hour-per-week employee averages about 104 hours monthly. Whatever the weekly scheduled hours, multiply by 4.333 for the monthly estimate.

Why Monthly Hours Change and What That Means for Your Team

The variation is pure calendar math. Some months have more weekdays than others. February 2026 has 20 weekdays because it starts on a Sunday and has only 28 days. July and December 2026 each have 23 weekdays. That is a 24-hour difference per employee, which equals three full working days, created entirely by the way the calendar falls.

Months that contain five occurrences of a particular weekday appear about four times per year. July 2026 has five Mondays, five Tuesdays, five Wednesdays, and five Thursdays. For employees on variable or flexible schedules, those extra days create more opportunity for hours to accumulate in ways managers do not always see coming. A manager tracking only the monthly total after the fact may not notice that two of those weeks tipped into overtime territory.

Leap years add one weekday every four years. 2024 had a Friday February 29, giving that February 21 weekdays, or 168 hours, instead of the usual 20. For most payrolls the impact is modest, but it shows up in annual labor cost comparisons if you do not account for it.

Shift-based businesses feel the variance more directly than salaried office teams. A restaurant scheduling a fixed number of shifts per week runs essentially the same labor cost every week. A business that pays for actual hours worked sees the full swing between a 160-hour February and a 184-hour July. For businesses with paid time off, an employee taking a week of PTO in July reduces that 184-hour month by 40 hours. Tracking scheduled hours separately from hours actually worked keeps the budget figure and the payroll figure from bleeding into each other.

How Monthly Working Hours Drive Your Payroll Budget

Take your average hourly rate, multiply by the difference in monthly working hours, and you have the wage variance per employee before taxes and benefits. At $16 per hour, the difference between February 2026 (160 hours) and July 2026 (184 hours) is $384 per full-time employee. For a team of 10, that is $3,840 more in base wages in July than in February, without any change in scheduling policy.

Benefits costs that scale with hours worked, such as retirement contributions tied to gross compensation or employer payroll taxes, also move with the monthly hours count. Fixed benefits like a flat health insurance premium per enrolled employee do not. Knowing which costs are variable and which are fixed helps you build monthly labor budgets that absorb the calendar variance without throwing off your forecasts.

Salaried employees simplify this because their gross pay does not change month to month. But for salary-to-hourly conversion, project costing, or cost-per-productive-hour analysis, the standard divisor is 2,080 hours per year. Divide by 12 to get 173.3 as a consistent monthly figure for those calculations.

Payroll services running on a biweekly cycle process 26 pay periods per year, and two of those periods land in the same calendar month twice annually. That creates months with three paychecks rather than two, which can feel like uneven payroll when the underlying hours are consistent. Semi-monthly cycles run exactly 24 periods per year and tie more cleanly to calendar months. Either way, accurate hours tracking is what keeps the numbers right regardless of pay cycle structure.

Does Overtime Change the Monthly Hours Count?

Overtime hours are worked hours, so they count in the monthly total. But federal overtime is calculated per workweek, not per month. Under 29 U.S.C. 207, an employer owes one and one-half times the regular rate for any hours an employee works beyond 40 in a single workweek. What happened in prior weeks or what will happen in future weeks does not factor into that calculation.

An employee who works 50 hours one week and 30 the next earns 10 hours of overtime pay in the first week. The two-week total is 80 hours, the same as a coworker who worked 40 and 40, but the paycheck is larger because of the overtime premium. Both employees show 80 hours for the period. The overtime pay is a function of how those hours were distributed across weeks, not the monthly sum.

Months with 23 weekdays increase exposure for teams already running close to 40 hours per week. July 2026 has five Mondays, Tuesdays, Wednesdays, and Thursdays. On a tight 40-hour schedule, the extra days just extend the month. For employees on variable hours, those extra weekdays create more opportunity to tip into overtime during one of those weeks without a manager catching it until after the paycheck is processed.

Catching overtime before it happens means watching weekly hours at the scheduling stage, not reviewing monthly totals after the fact. A time and attendance system that shows each employee's running weekly hours in real time lets you adjust shifts or get manager approval before someone crosses 40 hours in a week.

What Is the ACA Full-Time Monthly Hours Threshold?

The Affordable Care Act uses a different definition of full-time than most employers do for scheduling. Under 26 CFR 54.4980H-1, an employee who works 30 hours per week or 130 hours per month is considered full-time for purposes of employer health coverage obligations. Applicable large employers with 50 or more full-time equivalent employees must offer affordable coverage to those employees or face potential penalties.

The 130-hour monthly threshold is meaningfully lower than the 173-hour mark most owners use for scheduling. An employee at 30 hours per week averages 130 hours per month and triggers ACA coverage considerations even though most employers would not call that full-time. An employee at 28 hours per week averages about 121 hours per month and stays below the line.

Variable-hour employees, common in retail, food service, and seasonal businesses, may exceed 130 hours in some months and fall below it in others. The IRS allows applicable large employers to use a look-back measurement period method that averages hours over a defined window to determine eligibility, rather than checking each month in isolation. Accurate monthly hours tracking per employee is the data foundation for that calculation. For businesses below 50 full-time equivalent employees, the employer mandate does not apply directly, but knowing who regularly works above or below 130 hours monthly informs benefit offerings and reduces unintended eligibility gaps.

How Do You Track Monthly Working Hours Without the Manual Math?

For a two-person operation, a paper time card gets the job done. For anything larger, manual tracking introduces errors that compound quickly. Clock-in and clock-out times get rounded or estimated. Lunch deductions get forgotten. Overtime hours get miscounted. The errors tend to cluster at pay period boundaries when everyone is hurrying, which is exactly when accuracy matters most for payroll.

A time and attendance system records every punch with a timestamp, applies configured break rules automatically, flags unusual entries, and generates a monthly hours report by employee, team, or location. Regular hours and overtime hours appear as separate line items, which is what payroll processing needs. The system does not miss a shift or double-count a lunch deduction.

The FLSA recordkeeping rules at 29 CFR 516.2 require employers to keep records of daily and weekly hours for each non-exempt worker. A time clock system satisfies that requirement automatically and produces an audit-ready record without extra effort. Paper records and spreadsheets satisfy the requirement too, but they require consistent manual discipline and take longer to produce when someone requests records.

For quick calculations on individual employees or one-off verification, Kloqk's free time card calculator takes daily start and stop times, subtracts break durations, and totals hours for the period. It handles overnight shifts and partial-week calculations without requiring an account.

The practical break-even point for a full time and attendance system is usually somewhere between five and eight employees. Below that, manual tracking is manageable. Above it, the time spent compiling monthly hours reports and reconciling timesheet discrepancies costs more than a basic clock system. The real payoff is not just the hours total. It is real-time visibility into who is approaching 40 hours this week, a clean audit trail, and the elimination of the payroll errors that manual time tracking produces once a team grows past a handful of people.

Working Hours Per Month: Quick Reference

• Full-time annual total: 2,080 hours (52 weeks times 40 hours)
• Full-time monthly average: 173 hours (2,080 divided by 12)
• Shortest month in 2026: February at 160 hours (20 weekdays)
• Longest months in 2026: July and December at 184 hours (23 weekdays)
• Part time at 30 hours per week: 130 hours per month (ACA full-time threshold)
• Part time at 20 hours per week: 87 hours per month
• Overtime trigger: 40 hours in a single workweek, not a monthly total
• FLSA recordkeeping: daily and weekly hours required per non-exempt employee

Use 173 hours per month for budgeting and salary-to-hourly conversions. Use actual tracked hours for payroll. The gap between those two numbers, measured consistently over time, reveals your real overtime exposure and scheduling accuracy better than any monthly total on its own.

Frequently Asked Questions

How many working hours are in a month on average?

A full-time 40-hour workweek produces an average of 173.3 working hours per month. That figure comes from dividing 52 weeks by 12 months to get 4.33 weeks per month, then multiplying by 40 hours. Individual months range from 160 hours in a short February to 184 hours in months with 23 weekdays like July and December.

How many hours a month is full time?

For scheduling, most employers treat full time as 160 to 174 hours per month based on a 40-hour week. For health insurance eligibility under the Affordable Care Act, the federal threshold is lower at 130 hours per month or 30 hours per week. An employee at 30 hours per week averages 130 monthly hours and triggers ACA coverage considerations even if your company considers that part time.

How many hours a month is part time?

A 20-hour-per-week schedule averages about 87 hours per month. A 24-hour schedule averages about 104 hours per month. Under the ACA, employees working fewer than 130 hours per month or 30 hours per week are generally considered part time for benefits eligibility purposes.

Does overtime count in the monthly working hours total?

Yes, overtime hours are worked hours and count in the monthly total. But federal overtime under the FLSA is calculated per workweek, not per month. An employee who works 50 hours one week and 30 the next earns 10 hours of overtime pay in the first week, and the monthly total reflects all 80 hours regardless of how they were distributed.

How do I track monthly working hours accurately?

The most reliable method is a time clock system that timestamps every clock-in and clock-out, applies break rules automatically, and generates a monthly hours report by employee. Spreadsheets work for very small teams but introduce transcription errors, especially at pay period boundaries. A cloud time and attendance system keeps an audit-ready record that satisfies FLSA recordkeeping requirements without extra manual effort.