How Many Hours Worked in a Month: Tracking Actual Employee Time

How many hours worked in a month averages 173 for a full-time 40-hour week, ranging from 160 in a short February to 184 in a long July. That average is the planning figure. The actual hours worked each month depends on calendar weekdays, attendance, time off, and overtime, and the real number is what payroll needs.

Scheduled Hours vs. Hours Worked: Why They Are Never Quite the Same

Scheduled hours are the hours you put on the shift plan. Hours worked are what employees actually clock. The two numbers diverge for predictable reasons: an employee leaves 15 minutes early, someone calls out sick, a rush period pushes a shift to run long, a manager approves extra hours to cover a gap. None of those events are unusual, and none of them show up on a schedule in advance.

Payroll uses hours worked, not scheduled hours. If you run payroll from the schedule rather than actual punch data, you overpay employees who left early and underpay employees who stayed late. Both errors create problems. Underpayment is a wage violation. Overpayment is a payroll cost you did not budget and a conversation you do not want to have with employees who may not remember the shift you are disputing.

The monthly hours worked figure is the sum of every employee's daily clock-in-to-clock-out time, less unpaid breaks, across every shift in the month. That number is what goes to payroll and what drives overtime calculations at the weekly level. Scheduled hours are a planning tool. Hours worked are the payroll record.

What Drives the Monthly Hours Worked Count

Three factors shape how many hours employees work in a month:

• How many weekdays the month contains. A standard Monday-through-Friday, 40-hour schedule produces 160 hours in February 2026 (20 weekdays) and 184 hours in July 2026 (23 weekdays). That 24-hour swing is the baseline before anything else happens.
• Attendance and time off. PTO, sick leave, call-outs, and early departures all reduce the hours worked total below the scheduled figure. An employee using one week of PTO in July removes 40 hours from that month's worked count without changing the schedule.
• Overtime and extra shifts. Unscheduled overtime and voluntary extra shifts push hours above the scheduled total. A 184-hour July becomes a 200-hour month if two employees each pick up 8 extra hours to cover a gap.

For payroll accuracy, all three of these need to be captured in real time, not reconstructed from memory at the end of the period.

How Many Working Days Are in a Month and Why It Matters

In 2026, the 261 weekdays spread unevenly across 12 months, averaging 21.75 working days per month. Multiply by 8 hours per day and you get the 174-hour average. The actual spread:

• 20 working days in February (160 hours at 8 hours per day)
• 21 working days in May, August, and November (168 hours each)
• 22 working days in January, March, April, June, September, and October (176 hours each)
• 23 working days in July and December (184 hours each)

For a business that pays hourly wages, those 261 working days determine the annual labor cost at baseline schedule. Adding overtime or deducting absences adjusts the figure, but the calendar is the floor. Businesses that budget monthly payroll as a flat 173-hour monthly cost will run short in July and December and long in February. Using actual hours worked rather than a flat average eliminates that variance from your payroll accounting.

Shift-based businesses often think in shifts rather than days, but the principle is the same. A five-shifts-per-week employee on a 10-hour shift works 50 hours weekly. Multiply by 4.333 weeks per month and the monthly average is 217 hours. A month with five weeks of that schedule produces 250 hours. A four-week month produces 200. The calendar determines the difference, and tracking punches is the only way to capture it accurately.

How Payroll Uses Monthly Hours Worked

Payroll processing does not actually sum hours by month for most federal compliance purposes. The Fair Labor Standards Act calculates overtime at the weekly level, and payroll cycles are usually weekly, biweekly, or semi-monthly. The monthly hours total is an output of summing those weekly figures, not an input to overtime calculation.

Under 29 U.S.C. 207, overtime pay applies to hours worked beyond 40 in a workweek. An employee who works 50 hours in week one and 30 in week two earns 10 hours of overtime premium in week one. The monthly total is 80 hours, same as a coworker who split it 40-40, but the pay is higher. Payroll needs the weekly breakdown, not just the monthly sum.

The monthly hours figure becomes important for:

• ACA eligibility tracking. Under 26 CFR 54.4980H-1, an employee working 130 hours per month is considered full-time for employer health coverage purposes. Applicable large employers need this number to determine which employees must be offered coverage.
• Labor cost reporting. Monthly hours worked per department or location is a standard operations metric. It feeds budget vs. actual labor cost reports and helps identify locations running consistently over or under their hours target.
• PTO accrual. Many PTO policies accrue at a rate per hour worked. The monthly hours total is the multiplier for that calculation.
• Client billing. Service businesses that bill by the hour need hours worked by client or project, totaled by month for invoicing.

How Time Clock Systems Track Monthly Hours Worked Automatically

A time clock records a timestamp every time an employee clocks in or out. The system computes the difference between each pair of punches, subtracts any configured unpaid break periods, and adds the result to a running total. At the end of the pay period or month, the report shows actual hours worked per employee, broken down by regular and overtime, without any manual addition.

That is meaningfully different from a manual process. With manual time cards, employees write in start and end times, supervisors verify them, and someone (often the office manager or business owner) adds everything up. Each step introduces potential for error or dispute. An automated punch system eliminates the manual data entry, the addition, and the he-said-she-said disputes about when someone actually arrived.

A time and attendance platform also applies overtime rules automatically based on your jurisdiction. For most U.S. employers, that means flagging hours above 40 per workweek for overtime calculation. For California employers, it also means flagging hours above 8 per day. The system applies the rules to the actual punch data, so the payroll export is ready without manual overtime flagging.

The FLSA recordkeeping requirements at 29 CFR 516.2 require employers to keep daily and weekly hours records for each non-exempt employee. An automated time clock satisfies that requirement and keeps the records searchable and retrievable for three years (the standard retention period under 29 CFR 516.5). A folder of paper time cards technically satisfies it too, but responding to a wage claim or labor audit is much faster with a searchable digital record.

For teams that do not yet have a time clock system, Kloqk's free time card calculator lets you enter daily start and stop times, subtract breaks, and total hours per week. You can run it for individual employees to verify a specific paycheck or estimate the monthly total without a full system in place.

Building a Monthly Hours Tracking Routine That Actually Works

Most payroll problems that trace back to hours tracking share a common root: hours are captured inconsistently across the pay period and then reconstructed under pressure at the close. An employee remembers arriving at 8:15 but wrote down 8:00. A manager approved the shift change verbally but never updated the schedule. A punch-out was missed on a long Friday and nobody noticed until the biweekly total came out wrong. None of these are unusual, and none of them are malicious. They are just what happens when time tracking depends on memory and manual entry.

A consistent routine prevents most of them. Here is what that looks like in practice for a small hourly team:

• Real-time clock-ins. Every shift starts with a timestamped punch, not a written entry. The timestamp is objective and does not change based on memory.
• End-of-shift review. Managers confirm hours before leaving, not at the end of the week. Discrepancies are fresh and easy to resolve at the shift level.
• Weekly hours check. Before the workweek closes, verify each employee is within schedule. Catching a 42-hour week before payroll runs means one conversation, not a wage dispute six months later.
• Monthly hours report. Pull the monthly total at the end of the period, compare against the budget, and note which employees are consistently over or under. That pattern tells you about scheduling discipline, not individual incidents.

The monthly hours report is also where ACA eligibility management lives for businesses that employ variable-hour workers. A worker who averaged 31 hours per week over a 12-month look-back period qualifies as full-time under the ACA regardless of their scheduled hours. Seeing that in a monthly report before the measurement period ends gives you options. Seeing it on a penalty notice does not.

Most time clock systems can generate this report automatically. The question is whether you have one configured and whether your team is actually using it, not just whether the software is installed.

Common Monthly Hours Figures for Different Work Schedules

Here are the monthly hours averages for common schedule types, based on 4.333 weeks per month:

These are averages. Any individual month will differ based on the actual weekday count and the employee's attendance. The 173-hour full-time average is the right number for budget projections. The actual hours worked figure from your time clock is the right number for payroll.

If you are building a monthly labor budget and want to account for calendar variance, use the actual weekday count for each upcoming month rather than the 4.333-week average. For 2026, that means budgeting 160 hours per full-time employee in February, 176 in most months, and 184 in July and December, then adjusting for your paid holidays and expected PTO usage on top of the baseline.

The difference between a well-tracked hours worked record and a rough estimate is often subtle month to month. It compounds into a material payroll discrepancy over a year, and it becomes a compliance exposure if an employee disputes their pay and your records cannot show the exact hours behind the check.

Frequently Asked Questions

How many hours do employees work per month on average?

A full-time employee working 40 hours per week averages 173 hours worked per month (52 weeks divided by 12 months, times 40 hours). The actual count in any given month ranges from 160 hours in a short February to 184 hours in a long July or December, before accounting for time off, call-outs, or overtime.

How many working days are in a month on average?

On a standard Monday-through-Friday schedule, there are on average 21.7 working days per month (261 weekdays in 2026 divided by 12). Individual months range from 20 working days in February 2026 to 23 in July and December. Subtract company holidays to get actual scheduled working days.

How do I calculate total hours worked in a month?

Add up each employee's daily hours worked across every day in the month. Daily hours are the difference between clock-in and clock-out, less any unpaid break time. A time clock system does this automatically and generates a monthly total per employee. For manual calculation, a time card calculator can total a week at a time, which you then add across the four or five weeks in the month.

What is the difference between scheduled hours and hours worked?

Scheduled hours are what you put on the shift plan. Hours worked are what employees actually clock. The gap between the two comes from early departures, tardiness, call-outs, unscheduled overtime, and approved time off. Payroll uses hours worked, not scheduled hours. Tracking both lets you measure attendance and schedule adherence separately from payroll accuracy.

Does FLSA require tracking actual hours worked per month?

The FLSA's recordkeeping rules at 29 CFR 516.2 require employers to keep records of daily and weekly hours for each non-exempt employee. The requirement is weekly, not monthly, but most systems store daily punches and let you pull a monthly total at any time. Salaried exempt employees are not covered by the daily hours recordkeeping rule, though many employers still track their hours for project costing or PTO purposes.