On-call pay for techs: stipends, minimums and FLSA rules

Start with two questions

On-call pay comes down to two separate questions. First, is the time a tech spends waiting for calls work time that must be paid? Second, how do you pay for the calls themselves, fairly and in a way techs accept? Companies that mix the two up tend to underpay in some weeks and overpay in others, and the policy gets argued every time someone has a bad night.

What federal guidance says about waiting

The Department of Labor's fact sheet on hours worked draws the line clearly. An employee who is required to remain on call on the employer's premises is working while on call. An employee who is required to remain on call at home, or who is allowed to leave a message where they can be reached, is not working, in most cases, while on call^[1]. The same fact sheet frames waiting time as either "engaged to wait," which is work time, or "waiting to be engaged," which is not, depending on the facts^[1].

The regulation adds an important limit. On-call time can be work time when the employee has to stay so close to the employer's premises that they cannot use the time effectively for their own purposes^[2].

Facts that can change the answer

The label "on call" doesn't decide anything; the restrictions do. Before you set a policy, ask how free your techs really are.

• How quickly must they respond? A requirement to be on the road within minutes limits what they can do far more than a callback within an hour.
• How often do calls come? If techs are called out most nights, the evening is hardly their own.
• Where must they stay? Rules about distance from the shop or service area restrict personal time.
• Can they trade shifts easily, or hand a call to a backup?
• Are there rules about alcohol, travel or activities during on-call periods?

The more restrictions, the more likely the waiting time is work time. Get advice if your rules are strict.

Calls are work time

Whatever the status of waiting time, time spent actually working is paid. That includes:

• Answering and screening calls from customers or the answering service.
• Phone troubleshooting, such as walking a customer through a reset.
• Driving to and working at the job, and the paperwork afterwards. Ask an employment lawyer how travel to after-hours calls is counted in your state.
• Calls to the backup, the manager or a supplier about the job.

Make recording easy: a time entry in the field app for every call, including phone-only calls. Unrecorded ten-minute calls add up across a season and become a back-pay claim.

Overtime math

After-hours calls often push a tech past 40 hours. Under the FLSA, covered employees must receive overtime pay for hours worked over 40 in a workweek, at not less than one and a half times their regular rate^[3]. The Act does not require overtime for weekend or holiday work as such^[3]; it is the total hours in the workweek that matter.

For scale, the median hourly pay of HVAC mechanics and installers was $29.33 in May 2025^[4], and electricians' median was $30.38^[5]. An overtime hour at time and a half on the HVAC median is $44.00.

Remember that some payments, such as certain bonuses or stipends, may need to be included in the regular rate when overtime is calculated. Your payroll provider can check how yours are treated.

Pay models compared

Call-out minimums

A call-out minimum guarantees a set amount of paid time for each call, even if the job takes twenty minutes. It recognizes that getting dressed, driving out and coming home costs the tech an evening.

• Set it per call, not per night, and say how back-to-back calls are counted.
• Decide whether phone-only calls get a smaller minimum.
• Apply it the same way to every tech, and put it in writing.
• Make sure the minimum is reflected in your after-hours pricing, so the call covers its cost.

Exempt and non-exempt staff

Most service technicians are paid hourly and are non-exempt, which means overtime rules apply. Some salaried managers who take on-call duty may be exempt, depending on their duties and pay. Classification is a legal question with real penalties if it is wrong, so get advice before treating anyone on call as exempt.

A worked week

1. 01

   Example setup

   Example: a fictional tech earns $30 an hour, works 40 regular hours Monday to Friday, and is on call Friday night to Sunday night for a flat weekend stipend set in the company policy.

2. 02

   Saturday call

   Example: he answers a no-heat call, spends 15 minutes on the phone and 2 hours on site including driving. The company's call-out minimum is 2 hours, so he records 2 hours 15 minutes.

3. 03

   Sunday call

   Example: a phone-only call to talk a customer through resetting a tripped breaker takes 20 minutes. He records it in the field app.

4. 04

   Overtime

   Example: his week now totals 42 hours 35 minutes, so the hours over 40 are paid at time and a half, and the payroll provider checks whether the stipend affects his regular rate.

5. 05

   Review

   Example: on Monday the service manager confirms both calls were logged and checks the rest rule for his Monday start.

Disputes that come up, and how to prevent them

Most on-call pay disputes are about small, repeated gaps rather than big decisions. A few rules prevent nearly all of them.

• "I took three calls on the phone and never got paid." Fix it with a one-tap time entry for phone-only calls, and a weekly check that on-call techs logged something or confirmed a quiet night.
• "The backup was on call too, but got nothing." Decide whether backups receive a smaller stipend, and pay them for any call they take.
• "My Saturday call took twenty minutes, but I lost the evening." That is what the call-out minimum is for. State it clearly.
• "Overtime didn't include my on-call hours." Run on-call weeks through the same payroll check every time, with the total hours shown on the pay stub.
• "Someone else always gets Christmas." Track holidays on the rotation and share them over the years.

Handle each question quickly and in writing. A tech who has to chase the same pay issue twice starts looking at other employers.

Explaining the policy to the team

Walk through the written policy at a team meeting, with a worked example for a quiet weekend and a busy one. Show exactly how a stipend, the call-out minimum and overtime combine on a pay stub. Give every tech a copy, and ask them to sign that they have read it. When the policy changes, repeat the walk-through rather than sending an email.

Write the policy down

1. Who is in the rotation and how it is scheduled; see how to build a fair on-call rotation.
2. Response time expectations and any restrictions during on-call periods.
3. The stipend, if any, and how weekends and holidays differ.
4. How calls are recorded and paid, including phone-only calls.
5. The call-out minimum and how back-to-back calls count.
6. Overtime treatment and who reviews it.
7. Which calls justify a truck roll at night, based on your emergency triage guide.

Keep good records

• Every on-call period, with primary and backup.
• Every call, with start and end time, whether it was phone-only and whether a truck rolled.
• Swaps, confirmed in writing.
• Pay calculations for on-call weeks, kept with payroll records.

Good records protect both sides. They also tell you whether your rotation is sustainable and whether after-hours work earns its keep, which feeds your billable hour rate. If many calls could have waited, better screening reduces both pay costs and tech fatigue; our guide on after-hours voicemail covers the alternatives.