How Many Work Hours in a Month? The Calculation Explained

A full-time employee working a standard 40-hour week logs approximately 173.33 work hours in a month, based on 2,080 annual hours (40 hours x 52 weeks) divided by 12 months.

The Standard Calculation and Where 173.33 Comes From

The 173.33 figure is not arbitrary. It comes from annualizing the federal 40-hour workweek across 12 calendar months. Under 29 U.S.C. § 207 of the Fair Labor Standards Act, overtime begins after 40 hours in a workweek. Annualizing that threshold gives the standard baseline:

• 40 hours per week x 52 weeks = 2,080 hours per year
• 2,080 divided by 12 months = 173.33 hours per month

This number appears in job postings, employee handbooks, and payroll systems because it is the consistent, calendar-independent baseline used across HR and finance. It smooths out the fact that months are not the same length. Some months have 19 workdays, some have 23. Using the annualized average gives a figure you can multiply by an hourly rate to estimate monthly labor cost without recalculating every month.

For employees on a 37.5-hour week, a schedule common in healthcare, professional services, and some government roles, the monthly average is 162.50 hours (37.5 x 52 divided by 12). The employer may still classify that as full-time, but the FLSA overtime clock starts at 40 hours per workweek regardless. The table below shows common schedule types and their annualized monthly averages:

Monthly work hours by schedule type (annualized average)

Schedule type	Hours per week	Annual hours	Average hours per month
Full-time standard	40	2,080	173.33
Full-time compressed	37.5	1,950	162.50
Part-time (30 h/wk)	30	1,560	130.00
Part-time (24 h/wk)	24	1,248	104.00
Part-time (20 h/wk)	20	1,040	86.67

Notice that 130 hours per month corresponds to 30 hours per week. That figure matters for compliance. According to the IRS Employer Shared Responsibility Q&A, an employee averaging 30 hours of service per week or 130 hours of service in a month is considered full-time for Affordable Care Act purposes. Employers with 50 or more full-time equivalent employees must offer qualifying health coverage to employees who meet that threshold. If you have part-time workers whose hours drift toward 130 per month, you need to catch it before your next ACA reporting period.

Does the Number Change When Months Have Different Days?

For hourly workers, yes. The 173.33 figure is a 12-month average. In any specific month, actual available working hours depend on how many weekdays that month contains. Across a calendar year, the weekday count (Monday through Friday) ranges from 19 to 23, creating a swing of up to 32 available hours between the shortest and longest months.

In 2026, the weekday count and corresponding hours for a standard 8-hour-day, Monday-through-Friday schedule break down as follows. February has 20 weekdays (160 hours); July and December each have 23 weekdays (184 hours). The other nine months land between 21 and 22 weekdays:

For scheduling and staffing budgets, thinking in weekday counts rather than monthly averages gives you a more precise picture. A restaurant with 15 hourly servers, each scheduled for 20 hours per week, has a different labor cost ceiling in a 23-weekday month than in a 20-weekday month. The extra three days represent 6 additional scheduled hours per employee, which adds up to meaningful cost variance when you are tracking labor as a percentage of revenue.

For salaried employees, the monthly swing in weekdays does not change pay. A salaried worker receives the same paycheck whether the month has 160 or 184 available hours, because the compensation is tied to an annual figure divided by pay periods. This creates a shifting cost-per-hour difference between salaried and hourly staff throughout the year. In a 23-weekday month, salaried employees effectively cost less per hour worked. In a short month, the reverse is true.

Holiday-adjusted workday counts can push February even lower and shrink months that contain federal holidays. If your team observes federal holidays, subtract one workday for each holiday that falls on a weekday in the month. The hours-per-month figure adjusts accordingly.

How Monthly Work Hours Affect Payroll and Labor Costs

Monthly hour counts sit at the center of several payroll and compliance calculations. Whether you run weekly, biweekly, semi-monthly, or monthly payroll, understanding the monthly total helps you catch errors before they become disputes.

Payroll frequency and monthly reconciliation. For biweekly payroll (26 periods per year), each pay period covers 80 hours for a standard full-time employee. Two months per year typically contain three biweekly pay periods. Your monthly labor expense in those months will be higher than in two-period months even if every employee worked the same schedule. This is a payroll calendar effect, not an hours anomaly, but it affects the monthly number you see on your profit-and-loss statement.

Overtime exposure by week, not by month. Under 29 U.S.C. § 207, employers must pay overtime at 1.5 times the regular rate for any hours beyond 40 in a single workweek. A 173-hour month could contain zero overtime (if the employee worked exactly 40 hours in each week of the month) or could contain multiple overtime weeks depending on how shifts are distributed. Monthly hour totals tell you what happened in aggregate; weekly totals tell you what you owe in overtime premiums.

ACA headcount and benefit eligibility. If you have 50 or more full-time equivalent employees, you are an Applicable Large Employer under the ACA. Per the IRS guidance cited above, part-time employees who average 130 hours of service per month count toward that full-time equivalent headcount and must be offered qualifying health coverage. Miscounting hours, whether because of manual tracking errors or ignored schedule overages, creates compliance exposure that surfaces at annual ACA reporting time. The 130-hour monthly threshold is exactly equal to 30 hours per week, so any employee scheduled for 30-plus hours needs to be tracked carefully.

Workers' compensation and labor cost ratios. In most states, workers' compensation premiums are calculated as a rate per $100 of payroll. Since payroll for hourly workers is directly tied to hours worked at a given pay rate, inaccurate monthly hour counts produce inaccurate premium calculations. The same problem appears in labor cost as a percentage of revenue: the ratio only works if the numerator is based on actual hours, not estimates or scheduled hours that did not reflect what happened on the floor.

Part-Time, Overtime, and Variable Schedules

Most small business teams do not run on a single schedule type. A mix of full-time, part-time, and variable-schedule employees creates a range of monthly hour profiles that all feed into the same payroll and compliance math.

A few things stand out when you look at this range:

• The gap between full-time schedules is small but real. A 37.5-hour employee averages 10 fewer hours per month than a 40-hour employee. At $20 per hour, that is $200 per month per person. For a team of 10, the annual difference is $24,000 in labor cost compared to a standard 40-hour team.
• Part-time employees average roughly half the monthly hours of a full-time worker. An employee at 20 hours per week logs 87 hours per month. If that employee's hours start climbing toward 130, you need to flag it before it triggers ACA full-time status and benefit obligations.
• Overtime workers carry a premium cost beyond the raw hour count. An employee averaging 45 hours per week logs 195 hours per month. Roughly 22 of those hours (5 per week x 52 / 12) are at 1.5 times the regular rate. At a $16 base rate, that overtime premium adds approximately $176 per month per employee compared to straight-time pay for the same total hours.

Variable schedules create the most forecasting risk. A worker whose hours fluctuate between 18 and 38 per week depending on business volume has a monthly total that cannot be accurately forecast from the posted schedule. The only way to know what that employee actually cost in a given month is to look at time records.

How to Track Actual Monthly Hours Instead of Estimating

The gap between an estimated monthly hour count and what actually happened is where payroll errors, overtime surprises, and compliance failures accumulate. A manager who assumes all employees hit their scheduled hours is carrying risk that only surfaces at payroll time or during an audit.

Three approaches to tracking employee hours per month, ranked by reliability:

Manual time cards and spreadsheets. Employees record start and stop times by hand, and a manager totals them up at the end of the pay period. This works for very small teams with predictable schedules, but breaks down when shifts vary, punches are missed, or employees forget to record their time. Errors compound across a month: a single missed 30-minute entry per week turns into a 2-hour undercount by month-end. For manual verification of any pay period, the free Kloqk time card calculator lets you enter shift start and end times and get an accurate total without building a spreadsheet.

Scheduling software as a proxy. Some managers pull scheduled hours as if they were actual hours worked. This is convenient but frequently wrong. Employees arrive early, stay late, cover for colleagues, or clock out when business slows. The variance between scheduled and actual hours commonly runs 5 to 15 percent in restaurants and retail. Multiplied across a team over a month, that variance produces payroll discrepancies and, in some states, wage claim exposure if actual hours exceeded what was recorded.

A dedicated time clock system. Employees clock in and out at the start and end of each shift. The system captures actual timestamps, calculates hours by employee and pay period, and can alert managers when someone is approaching overtime or has a missed punch. For hourly teams, this is the only approach that produces an accurate monthly hour count without manual reconstruction after the fact.

The choice of approach also affects how you handle payroll disputes. When an employee believes their paycheck is short, the conversation goes one of two ways: either you have a timestamped record of every punch, or you have an argument. A time clock system creates an audit trail that resolves disputes quickly and protects the business from wage claims. Many small business owners discover this value the first time a former employee files a complaint with the state labor board and they need to produce hour records for a specific pay period three months ago.

Kloqk's time and attendance platform handles this at no cost. Employees punch in through a shared kiosk, a mobile app with GPS location verification, or a PIN-based time board. Managers see live hour totals by employee, can approve or correct punches before the payroll run, and export a clean hours report for any date range. For a team of 15 hourly employees, the difference between estimated and accurate monthly hours routinely runs several hundred dollars in either direction. Removing the estimation step removes that variance from every pay period.

The 173.33-hour monthly average is the right figure for annual budgeting and labor cost benchmarks. For individual pay periods, overtime decisions, and ACA compliance, actual time records are the only number that holds up.

Frequently Asked Questions

How many work hours are in a month for a full-time employee?

A full-time employee on a standard 40-hour week averages 173.33 work hours per month. This comes from 40 hours x 52 weeks = 2,080 hours per year, divided by 12 months. The actual count in any specific month depends on how many weekdays it contains, which ranges from 19 to 23 in a typical year.

How do I calculate monthly work hours for payroll?

For hourly employees, add up actual clock-in and clock-out times for the month. For salaried employees, the monthly figure is the annual salary divided by 12 (or by 24 for semi-monthly payroll, 26 for biweekly). If you need a quick sanity check for a manual pay period, Kloqk's free time card calculator lets you enter shift times and get an accurate total without building a spreadsheet.

Does the IRS define a standard number of work hours per month?

The IRS does not set a universal monthly hour standard, but for Affordable Care Act purposes it defines full-time status as averaging 30 hours of service per week or 130 hours per month. Employers with 50 or more full-time equivalent employees must offer qualifying health coverage to employees who meet this threshold. This makes accurate monthly hour tracking a compliance issue, not just a payroll issue.

How many hours per month is considered part-time?

There is no single federal definition, but most employers treat under 30 hours per week as part-time. At 20 hours per week, an employee averages 86.67 hours per month. At 24 hours per week, the average is 104 hours. At 29 hours per week, the monthly average is 125.67 hours, just under the 130-hour ACA full-time threshold. Keeping variable-schedule employees reliably below 130 hours per month requires tracking actual hours, not just posted schedules.

How does overtime affect monthly work hours?

Overtime is calculated per workweek under the FLSA, not per month. An employee who works 45 hours in one week and 35 in the next has 5 overtime hours in the first week, even though the two-week average is 40. On a monthly basis, an employee working 45 hours per week averages 195 hours per month, roughly 22 of which are at the overtime rate. That premium adds real cost across a team, which is why weekly hour tracking matters as much as the monthly total.