The math of technician turnover
The trade press puts annual turnover in field service at roughly 35%, with replacement cost averaging around $15,000 per departed tech when you count recruiting, onboarding, and productivity loss during ramp-up. That figure is conservative for skilled trades. Industry research consistently shows that replacing a salaried employee runs 6 to 9 months of salary on average, with technical positions landing in the 100-150% range. For an HVAC tech at the BLS-verified 2024 median wage of $59,810, that's $30,000 to $50,000 per departure — and senior techs with brand-specific factory training and EPA 608 Type II push the high end.
The indirect costs are larger than the direct ones. Per Salesforce's 2024 survey of field-service workers, 74% of mobile workers report workloads continuously increasing, and 57% report burnout. The Service Council's 2024 Voice of the Field Service Engineer survey found only 42% of techs expect to stay in their roles for the duration of their careers. When a senior tech walks, the remaining team absorbs the load — and the second walk follows the first within months.
A 30-tech operation with 28% annual turnover loses about 8 techs per year. At $35K each, that's $280,000 — every year — that doesn't show up on a P&L line. Most ops managers know the number is big. Few have computed it.
The lever most operations don't pull. Wages matter. They're not the only lever. Per the Service Council's research, techs leave because the work feels unfair, chaotic, and bureaucratically burdensome — long before they leave for the wage bump. The three killers below are all operational, all fixable, and all sit outside the HR budget.
Killer #1: Unfair workload distribution
Senior techs gravitate toward the easy commercial PMs and the high-margin work. Junior techs end up with the no-cool walk-ups in 95-degree heat, the basement service calls, the long-drive residentials. Within six months of unmonitored cherry-pick, the senior techs are over-loaded with their preferred work and the junior techs are burned out on the leftovers.
Both groups are on their way out. The senior techs walk because the workload they cherry-picked into still doesn't feel manageable — they're getting all the premium customers, but they're also working every weekend the dispatcher couldn't cover. The junior techs walk because they look at the senior techs' assignments and conclude they'll never get there. The "career path" the company promised exists on paper, but the daily evidence says it doesn't exist on the schedule.
The fix is structural, not motivational. Cherry-pick prevention rules — built into the dispatch engine, configurable per company — distribute work fairly by tech, by skill level, by drive time, or by revenue, depending on what your operation needs. Equal distribution doesn't mean identical assignments; it means the senior tech gets the commercial work their certifications justify and the junior tech gets a realistic path to that work with deliberate skill-building exposure along the way.
The political payoff matters too. When a senior tech complains they're getting all the hard jobs, the ops manager has reason codes to point to. When a junior tech complains they never see commercial accounts, you can show them the rebalance landing them on a commercial PM next Tuesday with a senior tech on a ride-along. That's the conversation that retains both ends of the experience curve.
Killer #2: No visibility into the day's plan
Ask a tech on Sunday night what their Monday looks like. In most operations, the answer is some version of: "I'll find out when I get the call." The dispatcher knows. The board knows. The system knows. The tech doesn't know — until they're starting the truck.
That information asymmetry is corrosive. Techs are craftspeople, not Uber drivers. They want to plan their day: the parts to load, the order of stops, when they'll grab lunch, when they'll be home. When they don't have visibility, they can't plan, and they can't manage their own day. They feel managed instead of professional. Per the Service Council research and Salesforce's 2024 field-service workforce survey, this lack of context is one of the most consistent dissatisfaction drivers — Salesforce found 47% of techs report appointments don't go as planned because of customer miscommunication, missing parts, or unaccounted-for travel time. Most of those misses trace back to information the tech didn't have until the moment they showed up.
The fix is a mobile experience that puts the day in the tech's hand the night before — or first thing in the morning — with full job context, customer history, asset history, parts they're likely to need, and the live arrival window. When the dispatcher reassigns mid-day, the tech sees the change immediately, in context, with the reason codes that explain why their day shifted. Native iOS and Android, fully offline so it works in basements and crawl spaces, syncs when signal returns.
The retention math here is subtle but consistent. Techs who can plan their day stay longer than techs who can't. The first month with real visibility tells the senior tech the company sees them as a professional. That's what the recruiter on the phone can't compete with.
Killer #3: Excessive drive time
Industry estimates put the average field-service tech at roughly 55 miles per day between job sites — about 1.5 to 2 hours per day in transit. Most of that is unavoidable. A meaningful chunk isn't.
Manual dispatch can't optimize across skills, proximity, workload, and SLA simultaneously — a dispatcher holds maybe two of those factors in their head at a time. The result is consistent over-driving: senior techs sent across town when a journeyman was closer, criss-crossing service areas because the dispatch board doesn't see geography, return trips for parts that should have been on the truck the first time. Industry experience suggests teams running manual dispatch waste 20-30% of drive time relative to what intelligent matching produces.
For the company, that's lost billable hours. For the tech, that's an hour or more of unpaid windshield time per day — and at the end of a long week of long drives, the tech's perception isn't "we lost productivity," it's "I'm paying for the dispatcher's mistakes with my evenings." Drive time bleeds into family time. Family time is what techs trade jobs for.
The fix is intelligent dispatch that factors drive time into matching alongside skills and SLA. Teams typically see around 20-30% less drive time once dispatch evaluates proximity AND skills AND workload AND customer preference together. On a 30-tech operation, a 25% drive-time recovery is roughly four full-time-equivalent hours reclaimed per week per tech — hours that go back to the customer (more billable capacity) or to the tech (earlier home time). Both outcomes lower turnover. The company gets better margin; the tech gets their evenings back.
The bonus killer: bureaucratic friction
Per Salesforce's 2024 field-service survey, admin tasks take up 30% of an average technician's working hours — slightly more than the 29% delivering actual service. Per the Service Council's earlier research on the same population, paperwork is consistently ranked as the least favorite part of a tech's day.
This is the slow-burn killer. No single paper timesheet, missing photo upload, or duplicate data entry is a quitting offense. The cumulative weight of dozens per day, every day, for years, is. Techs got into the trade to fix things, not to fill out forms. When the form-filling exceeds the fixing, they look around.
The fix is a mobile app that captures source data once, where the work happens — clock in and out tied to GPS at the job site, photos and signatures attached to the work order in real time, parts pulled from the truck stock without re-entering them on a separate sheet, notes that travel with the asset history so the next tech doesn't ask the customer the same question. None of these individual capabilities is dramatic. Stacked, they reclaim 30-60 minutes of a tech's day — and they signal that the company invested in tools that respect the tech's time.
That signal matters more than the time savings.
What good software changes
The operational fixes for the three killers (and the bonus) live in software the company chooses, not policies the HR team writes. The list is short and concrete:
- Cherry-pick prevention — dispatch fairness rules, configurable per company, that distribute work by tech, by skill level, by drive time, or by revenue
- Reason codes on every assignment — the tech can see why they got the job; the dispatcher can defend the decision; the ops manager can adjust the rules
- Live mobile dispatch board — the day's plan in the tech's hand, updated in real time when the schedule shifts, with full customer and asset context
- Drive-time-aware matching — proximity factored into every assignment alongside skills, SLA, and workload
- Native, offline-first mobile app — works in basements and crawl spaces, syncs when signal returns, captures photos and signatures without losing data
- Source-of-truth time tracking — clock in and out at the job site, hours-against-job captured live instead of reconstructed from memory at the end of the week
- Asset history at the technician's fingertips — model, serial, refrigerant type, warranty, and full service history visible before they walk into the job
- Auto-generated PM schedules — maintenance work populated from the customer's contract without the dispatcher rebuilding the calendar each quarter
None of these features individually retain a tech. Together, they remove the daily frictions that drive techs out — and replace them with the day-to-day signal that the company invested in tools that respect the work.
The retention math
Imagine a 30-technician operation with 28% annual turnover — typical for the trades. That's about 8 walks per year. At a midrange replacement cost of $35,000 per tech (between the industry-standard 6-9-months-of-salary benchmark and the trade-press estimate of $15K direct), that's $280,000 per year in turnover cost, plus the indirect cost of the gaps during ramp-up.
| The retention math | Before | After |
|---|---|---|
| Annual turnover rate | 28% | 18% |
| Walks per year (30 techs) | ~8 | ~5 |
| Direct replacement cost ($35K/tech) | $280,000 | $175,000 |
| Annual savings | — | $105,000 |
A 10-percentage-point turnover reduction — from 28% to 18% — saves roughly $105,000 per year on a 30-tech operation. Most retention studies suggest that's an aggressive but achievable target when operational frictions are addressed in tandem with reasonable wage benchmarks. The savings exceeds the cost of any field-service software on the market by a wide margin in year one alone.
What you can do this month
Three actions you can run before the end of the month, with no budget approval required:
- Audit one week of dispatch fairness. Pull the assignments by tech for the last seven days. Look for patterns in who gets the high-margin work, who gets the long drives, who gets the no-cool emergencies. The pattern will tell you whether your cherry-pick problem is real or imagined.
- Run a tech-side ride-along. Spend a day in the truck with one of your senior techs. Not to inspect them — to feel the friction. The paper timesheet at lunch, the call to the office for the part they didn't know was needed, the second drive across town that an algorithm could have avoided. You'll come back with a list.
- Ask the question directly. A 15-minute one-on-one with three of your senior techs: "What's the part of your day that you'd most want me to fix?" Most ops managers don't ask. The techs already know the answer. They've been waiting for the conversation.
These three steps cost nothing and surface the operational fixes that retention software will deploy. They also tell your senior techs you're paying attention — which itself is a retention move.
The retention conversation, reframed
The retention conversation in the trades is dominated by wages and career-path programs. Both matter. Neither addresses the three daily frictions — unfair workload, no day visibility, excessive drive time — that quietly drive techs out months before the recruiter's call. Those frictions are dispatch problems disguised as HR problems, and they're fixable in weeks, not quarters.
FSM Navigator's intelligent dispatch engine evaluates SLA urgency, skills, proximity, and workload — admin-tunable from day one. Cherry-pick prevention keeps assignments fair across your team. The native mobile app puts the day's plan in the tech's hand, works offline in basements and crawl spaces, and captures source-of-truth time and photo data without paper double-entry. Works from day one — no training period, no black box.