The Overtime Profitability Test: When Extra Revenue Makes Field Service Less Profitable

An extra Saturday shift can add revenue and reduce profit at the same time.

That happens when management counts the invoice but not the overtime premium, payroll burden, drive time, dispatch support, parts, callbacks, schedule spillover, and fatigue exposure. The right test is incremental contribution from the extra work—not revenue per technician hour.

Overtime can be the best response to a short demand spike, an emergency, or a valuable backlog. It becomes structural when normal capacity never covers normal demand. Then the premium is financing a staffing or pricing problem.

Calculate the legal pay first

Finance should not estimate overtime from a simple wage multiple without payroll review.

Under the federal Fair Labor Standards Act, covered nonexempt employees generally must receive overtime pay for hours over 40 in a workweek at not less than one and one-half times the regular rate. The regular rate can include compensation beyond the stated hourly wage, and federal, state, local, union, prevailing-wage, travel-time, call, and contract rules may differ.

Use the payroll system's actual workweek, classification, hours-worked rules, and regular-rate calculation. Wage counsel or a qualified payroll adviser should review uncertainty. The business model begins with compliant pay; it does not decide who is exempt.

Build an incremental overtime P&L

For the approved overtime block:

Overtime contribution
= Net collectible revenue from incremental completed work
  – Overtime wages and required premiums
  – Employer payroll taxes and variable benefits
  – Parts, materials, permits, and outside services
  – Incremental travel, vehicle, dispatch, and support cost
  – Expected callback and warranty cost
  – Other cost caused by the overtime block

Then:

Overtime contribution margin
= Overtime contribution
  ÷ Net collectible overtime revenue

Use collected or supportable net revenue after discounts, membership terms, refunds, card fees, and expected bad debt. Do not use list price.

Count every overtime hour

Paid hours may include more than wrench time:

• Travel between required sites.
• Loading and required preparation.
• Dispatch meetings.
• Waiting controlled by the employer.
• Documentation and closeout.
• Callbacks.
• On-call or call-back time under applicable rules.

Separate:

Revenue productivity
= Completed revenue-producing job hours
  ÷ Total paid overtime hours

A crew paid for 40 overtime hours may produce 34 revenue-generating hours after travel, setup, and closeout. Price and schedule the 40, not only the 34.

Work through one weekend block

Assume four field technicians each work ten overtime hours. This example is hypothetical.

• Total paid overtime hours: 40.
• Productive completed-job hours: 34.
• Average net collectible revenue per productive hour: $210.
• Base hourly rate: $32.
• Assumed overtime rate for the example: $48, subject to actual regular-rate rules.

Net collectible overtime revenue
= 34 × $210
= $7,140

Incremental cost	Amount
Overtime wages: 40 × $48	$1,920
Employer payroll taxes and variable burden	$260
Parts and consumables	$2,000
Vehicle, fuel, dispatch, and travel	$500
Expected callback and warranty reserve from internal history	$370
Incremental administration and customer support	$250
Total incremental cost	$5,300

Overtime contribution = $7,140 – $5,300 = $1,840
Overtime contribution margin = 25.8%

The shift is contribution-positive in the base case. It still needs safety, fatigue, cash, and alternative-capacity checks.

If a weekend discount reduces net revenue per productive hour to $175, revenue falls to $5,950 and contribution falls to $650, or 10.9%. If callback cost also rises, the block may no longer clear the required margin.

Use internal callback evidence

Do not apply a generic “fatigue percentage” to revenue. Track the firm's actual outcomes by schedule pattern:

• Callback rate.
• Rework hours.
• Vehicle incidents and near misses.
• Recordable injuries.
• Customer complaints and refunds.
• First-time completion.
• Average job duration.
• Absence and turnover.

Calculate:

Expected callback cost per overtime job
= Observed callback probability for comparable overtime work
  × Average loaded callback cost

Segment by work type, shift, consecutive days, team, and season where enough evidence exists. A small sample is a warning, not a precise forecast.

NIOSH notes that work-related fatigue can slow reaction time, reduce attention, limit short-term memory, and impair judgment. Long or irregular hours, demanding work, stress, and heat can contribute. That makes fatigue a safety and operating constraint, not merely a payroll line.

If the reports show the symptom but not the cause, start with a free 20-minute Profit & Tax Leak Check. It is designed to find the financial issue putting the most pressure on the business.

Set a safety gate before the financial gate

No positive margin justifies an unsafe schedule.

Operations should define:

• Maximum shift and overtime hours consistent with applicable rules and risk.
• Minimum rest and consecutive-day limits.
• High-risk tasks that cannot be scheduled late or after specified exposure.
• Driving and travel controls.
• Heat, weather, lifting, electrical, confined-space, and other task-specific controls.
• Supervisor authority to stop work.
• Fatigue reporting without retaliation.
• Backup coverage and emergency response.

The limits should reflect the work, law, contracts, insurance, and safety expertise. Finance models only the schedules operations has approved as safe.

Compare overtime with alternatives

For the same demand, model:

Capacity option	Costs and risks to include
Overtime	Premium pay, fatigue, callback, travel, retention
Hire employee	Recruiting, training, benefits, ramp, future idle capacity
Use subcontractor	Rate, quality, availability, insurance, customer terms, margin
Reschedule demand	Customer delay, cancellation, churn, seasonality
Change service area	Lost revenue, drive density, customer concentration
Raise constrained-slot price	Conversion, customer relationship, dispatch priority

Overtime often wins for a short, well-priced spike because it avoids permanent capacity. Hiring may win when premium hours repeat and signed demand covers the employee after ramp. A subcontractor may win when scarce technical capacity is temporary. Compare whole economics, not wage rates.

Measure overtime by workweek and job

Payroll rules operate by workweek; profit is earned by job, customer, route, or service line. The model needs both.

Assign actual overtime premium and paid hours using a consistent costing policy. A technician may cross 40 hours on Thursday, making Friday jobs carry premium cost even if those jobs were scheduled normally. Management should see:

• Overtime dollars by employee and week.
• Premium cost by job or service under policy.
• Net revenue and contribution from overtime work.
• Drive and nonproductive overtime hours.
• Callback and warranty cost.
• Contract or customer recovery of premium cost.

Do not move premium to general overhead to preserve job margins. Do not blame the final Friday customer for a scheduling system that created the threshold earlier.

The job-costing framework should reconcile paid time, service revenue, parts, and callbacks at the same job level.

Identify structural overtime

Temporary overtime has a start and end. Structural overtime repeats because:

• Price does not ration constrained demand.
• The service area creates excessive drive time.
• Dispatch and parts availability waste normal hours.
• Hiring lags signed demand.
• Turnover removes trained capacity.
• Callbacks consume the next week's schedule.
• Membership or emergency commitments exceed staffing.
• Management uses overtime to avoid a permanent decision.

Track rolling eight- or thirteen-week trends. If the same roles exceed the approved pattern for several weeks, trigger a capacity review before fatigue, payroll, and turnover compound.

Add a break-even price for constrained work

For an overtime job:

Required net revenue
= Incremental overtime cost
  ÷ (1 – Required contribution margin)

If the weekend block costs $5,300 and the firm requires a 25% contribution margin:

$5,300 ÷ 75% = $7,067 required net revenue

The modeled $7,140 barely clears the gate. That tells dispatch not to add an unpriced discount or a distant low-density job to the block.

Contract, consumer, emergency, and pricing rules may limit changes. The calculation still exposes whether leadership is approving a service decision that sacrifices contribution.

Run a weekly overtime review

1. Reconcile approved and actual hours to payroll.
2. Separate productive, travel, setup, callback, and other paid time.
3. Match net revenue and direct cost to completed jobs.
4. Update the callback and warranty reserve from internal results.
5. Review fatigue and safety indicators with operations.
6. Compare overtime with hiring, contractor, routing, and pricing alternatives.
7. Set the next-week cap and named exception approver.

The useful conclusion is: “Saturday produced $1,840 of modeled contribution and cleared the safety gate, but only $650 under the proposed discount. The discount is rejected, the distant job moves to a normal route, and the recurring electrical queue triggers a hiring model.”

Sources

• U.S. Department of Labor: Fact Sheet 23—FLSA Overtime Pay Requirements
• U.S. Department of Labor: Fact Sheet 56A—Regular Rate of Pay
• U.S. Department of Labor: Fact Sheet 1—Construction Industry and Overtime
• CDC/NIOSH: Fatigue and Work
• CDC/NIOSH: Driver Fatigue on the Job

The home-service fractional CFO framework connects dispatch, technician economics, job margin, cash, and capacity. Fractional CFO support can build the weekly overtime test. The Profit & Tax Leak Check can identify whether premium labor, drive time, callbacks, pricing, or a capacity gap is causing overtime revenue to disappoint.