Work Hours in a Month: 2026 Planning Guide for Field Service Owners

It’s the last week of May. The owner of a 10-tech HVAC shop in Phoenix is running capacity calculations for June 2026. He has 22 working days. At 8 hours per technician per day, that equals 176 hours per day, or roughly 1,760 labor hours across the team for the month. He schedules installations against that same capacity and books maintenance contracts accordingly. But by the second Friday, he is about 200 hours short. The spreadsheet didn’t account for Juneteenth, and time is also being lost in untracked workflow - toolbox talks and JSAs still being completed on paper and rebuilt for each job.

Below are the real 2026 numbers, the hidden deductions that field service owners often fail to model, and the workflow steps that help recover lost hours.

June 2026 has 22 weekdays (Monday June 1 through Tuesday June 30). One falls on a federal holiday: Juneteenth, Friday June 19, per the U.S. Courts 2026 holiday schedule. In our customer base, the shops that pre-load federal holidays into the dispatch calendar in January are the ones not scrambling for capacity in mid-June. That gives 21 paid workdays, or 168 hours per full-time tech - 1,680 across the Phoenix owner's 10-tech crew before anyone gets sick, takes PTO, or runs over on a callback.

The 168-hour ceiling is not the actual number of available hours. PTO, certification renewals, travel time between locations, and safety documentation all reduce the usable total. The four sections that follow break each of these down.

Three factors adjust the monthly total before the calendar is opened:

• Weekday count. In 2026, monthly working capacity ranges from 20 weekdays in February to 23 in July, which translates to roughly 160–176 working hours per technician in a standard 8-hour day model.
• Federal holidays. Eleven federal holidays fall on Mondays in 2026, each removing 8 hours from the monthly capacity.
• Compliance overhead. Based on our experience with 8-tech shops, JSAs, toolbox talks, incident logs, and certification check-ins consume a significant portion of the workweek - time that is not reflected in calendar-based capacity planning.

The first two are arithmetic. The third is where forecasts break down. In Quora discussions on JSAs as a key onboarding and training tool, owners describe Job Safety Analysis as the basis of their new-hire orientation process. However, it is typically created in a haphazard way on paper, then re-walked with every new employee, making it nearly impossible to consistently roll out across teams. The ad hoc nature of JSAs is precisely what causes the hour leak.

Here’s a month-by-month breakdown of the 2026 calendar, including federal holidays and their impact on operating hours:

Source: LeaveBoard 2026 US Working Days Calendar; U.S. Courts 2026 Federal Holiday Schedule. Private employers set their own holiday policies - the table reflects standard federal observances.

The most common pay-slip calculation is (40 hours × 52 weeks) ÷ 12 months = 173.33 hours per month. HR systems use this figure to determine salaried compensation and accrual rates. It should be used for payroll purposes only, not for calculating dispatch capacity.

The 173.33 figure assumes a frictionless month: zero holidays, zero PTO, zero compliance overhead, zero drive time. For a BLS-tracked construction workforce averaging 39.3 weekly hours, the real number lands closer to 170 across the year. Across our shops, the pattern is that owners who plan against a flat 173 consistently overbook by 5 to 10 percent. For field service crews subject to FLSA rules on travel and on-call time, the planning number you actually want is the calendar-specific monthly total minus a 10 to 15 percent operational deduction. Per DOL Fact Sheet #22, travel between job sites during the workday counts as hours worked - exactly where that operational deduction shows up. In our customer base, shops that don't track inter-site drive time end up eating it as unbilled labor. The Phoenix owner's 168 ceiling is real; his usable number is closer to 142.

August 2026 will have 21 working days (with August 1 falling on a weekend), and there are no federal holidays. This results in 168 available technician hours - the same as June 2026 - despite August having 31 calendar days compared to June’s 30.

A common fallacy: longer calendar months do not mean more capacity. This is not the case. For HVAC businesses, August is typically a peak-demand month where overtime increases on top of the same 168-hour baseline, rather than expanding it. Planning should be based on working days and available labor hours, not calendar length.

A longer calendar month does not mean more available hours. August has more calendar days than June but the same paid workday count.

Three steps work for any month, in any year:

• Count the number of weekdays (Monday through Friday) in the month.
• Subtract any national or company-observed holidays that fall on a weekday, particularly Mondays.
• Multiply the resulting number by the standard working hours per day (typically 8 hours).

Applied to 2026:

• June: 22 weekdays minus 1 holiday (Juneteenth) = 21 × 8 = 168 hours per tech.
• July: 23 weekdays minus 1 holiday (Independence Day observed Friday July 3) = 22 × 8 = 176 hours per tech.
• November: 21 weekdays minus 2 holidays (Veterans Day, Thanksgiving) = 19 × 8 = 152 hours per tech, the tightest billable month of the year.

In a five-tech crew, the gap between your most productive month (176 hours per technician, 880 total) and your most constrained month (152 hours per technician, 760 total) is 120 hours of labor capacity. This is not a rounding error. At a $100 blended service rate, that represents $12,000 of billable capacity that is not available in months like February and November. Most owners do not plan around this structural gap.

If your techs complete timesheets on paper at the end of each shift and drop them at the office on Monday morning, the monthly total of hours is whatever Friday morning admin says it is. This becomes a problem when pay, job costing, and overtime exposure all rely on the same figure.

The majority of Field Promax customers come from spreadsheet-based systems, paper timecards, or QuickBooks-only setups. Our experience shows that the first accurate monthly hour total is only visible about 30 days after moving away from paper timecards. This is the point when the office stops reconciling and backfilling clock-in disputes. An HVAC contractor reviewing Field Promax on the QuickBooks App Store described timecard management as easy and precise, calling it software every service company should have.

The compliance aspect is part of it. After years of working with paper-JSA shops, we've found that completion rates decline noticeably by Thursday and Friday of each week - the forms exist, but they rarely make it back to the office intact. Shops we work with that switch to a digital JSA module with mandatory fields and missed-form notifications recover much of this compliance loss, since the system cannot close the work order without the completed form. Apply those recovered hours to the Phoenix owner's June math and the 200-hour shortfall shrinks substantially - provided the digital workflow is actually adopted in the field .

Mobile-app adoption is the single biggest predictor of a successful rollout in our customer base. If the mobile app does not stick with the techs, the digital timecard total is no more reliable than the paper one.

Across roughly 30-40 mid-sized multi-trade contractors, we’ve seen a consistent transition from paper binders for compliance to electronic workflows, the inflection point is almost always an audit, not a productivity goal.

Our team has observed that a multi-trade contractor with field employees subject to OSHA safety rules underwent an annual review but was unable to produce safety training records for several teams when requested.

What the agency found

The documentation existed in fragments across binders, supervisor email folders, and old training packets, but pulling it into a single response packet took days. The agency cited the gap and issued a penalty large enough to fund a digital rollout twice over.

The issue that kept recurring during the post-mortem was inconsistent ownership of compliance responsibilities across the team. This is a theme we’ve frequently seen in Quora discussions on field service compliance ownership:

• The compliance officer believed the supervisors had filed them.
• Supervisors assumed the office did.
• The office assumed that certifications were recorded at the time of hire.

The remedy wasn’t a new policy. The leadership team moved safety documents from paper binders into a centralized digital system, where completion dates, signatures, and certifications were logged by technicians and accessible at any time.

What happened after

Subsequent audits went smoothly with records pulled in minutes rather than days. Crews initially resisted the added sign-off steps, and office staff spent weeks back-filling historical training data before the system was current. Pattern observed across multiple operators in this vertical.

Once monthly hours are accurate, the downstream calculations fall into place. For the Phoenix owner's 10-tech HVAC operation working 168 hours in June, the total capacity will be 1,680 hours. Shops running multiple verticals can feed that 1,430-hour figure directly into job costing and payroll without retyping a timesheet. That is the number to quote contracts against, plan overtime against, and feed into scheduling and dispatch decisions.

Shops that track compliance overhead digitally recover 10-15% of hours that paper-based workflows absorb - directly expanding the billable capacity the spreadsheet promises.

For owners running multiple verticals, team management and QuickBooks integration close the loop: clocked hours feed payroll, job costing, and the monthly P&L without anyone retyping a timesheet.

The question owners ask most about monthly hour planning is not about the calendar. It is some version of 'why does my crew's clocked hours never match what I budgeted?' From 15 years of customer conversations, the answer is almost always the same: the plan assumed a tech spends zero time on safety paperwork, and reality is several hours a week per tech.

The industry treats compliance overhead as a tax you eat. It is not. It is overhead you can recover, but only when the JSA, the toolbox talk, and the certification log live in the same mobile workflow as the work order.

• Joy, Founder, Field Promax

The impact on revenue is clear. Here’s how billable capacity - and the gap it creates - plays out across different utilization rates over an average 168-hour period:

Sources: Attainment Labs Technician Utilization Benchmarks; Gomocha Field Service Utilization Rate Analysis, 2026.

Monthly total work hours are not a fixed number. They are a planning tool that must account for the 2026 calendar, the federal holiday schedule, your PTO policy, and the compliance overhead that is placed in the dispatcher's hand. Keep that number accurate and the downstream decisions - payroll, job costing, overtime, capacity quoting become straightforward. Get them wrong and you find out the second Friday of the month.

The shops we work with that have the cleanest monthly hour numbers share three habits: timecards on the mobile app, digital JSAs and toolbox talks, and a dispatcher who reviews planned-versus-clocked hours weekly. Pick the one that fits your operation now and add the others as the system beds in.

Hours are more important than most owners realize when it comes down to compliance. Field service technicians are not exempt from overtime requirements under the FLSA. The U.S. Department of Labor has confirmed in a series of Opinion letters that field services technicians do not qualify for administrative or professional exemptions. They are eligible for overtime for all hours worked more than 40 hours in a week.

A number of states and Canadian provinces have stricter daily overtime rules that trigger before you reach 40 weekly hours.

• California: Overtime after working for 8 hours in a single day; double-time following 12 hours of work in a day.
• Nevada: Daily overtime after 8 hours (for employees below 1.5x minimum wage threshold)
• Alaska: Daily overtime after 8 hours
• Federal FLSA (most states): Only Weekly overtime ,and after 40 hours
• Ontario, Canada: Overtime after 44 hours of work per week
• British Columbia, Canada: Daily overtime after 8 hours or 40 hours per week
• Alberta, Canada: Daily overtime after 8 hours or 44 hours per week

In peak-season forums, techs routinely describe clocking 55-60 hours per week once travel time is included - a real overtime exposure that owners who budget only for 40-hour weeks absorb as an unplanned cost. Those who are paying for peak season overtime they never budgeted for, and techs who end up walking because of it.

Make your summer overtime budget prior to June, not during it. July has 176 available hours and high demand at the same time. If you have a five-tech HVAC team working 50-hour weeks across July's four weeks, you'll get around 200 overtime hours, on top of your regular pay - with 1.5x rates. This cost should be built into your service agreement pricing, not absorbed as a surprise on the mid-month payroll.The shops we work with that have the cleanest monthly hour numbers share three habits: timecards on the mobile app, digital JSAs and toolbox talks, and a dispatcher who reviews planned-versus-clocked hours weekly. Pick the one that fits your operation now and add the others as the system beds in.

The 2026 calendar does not consider your trade's seasonal curve. Knowing where your peak demand falls against available hours each month is the key to distinguishing between a planned busy season and a chaotic one.

Source: Field Promax customer base patterns; LeaveBoard 2026 US calendar.

Continue with:

• Field Safety, Compliance, and Data Protection for Trade Shops
• Time Tracking for Field Service: Where It Meets JSAs, OSHA, and the Daily Timecard
• 15 Minutes in Decimal: What It Actually Means for Field Service Payroll
• Field Employee Attendance Tracking: The JSA and Compliance Guide