Hiring and retaining field employees — sales reps, field service technicians, and other mobile workers — requires a fundamentally different playbook than traditional office-based HR. On this episode of The Keys, Cardata's Lee Adam spoke with Tim Sackett, top 10 global HR influencer and author of The Talent Fix Volume 2, about why field talent burns out fast, how HR leaders build trust by getting out of the office, and why mobile-first technology — including mileage tracking and reimbursement tools — directly impacts retention.

Why Field Hiring Is Fundamentally Different

Traditional hiring assumes a predictable environment: apply online, interview, onboard, sit at a desk. Field roles break that model entirely. As Sackett explains, field jobs come with ultimate flexibility and ultimate responsibility at the same time — employees may set their own schedule, but they're also "on" well beyond a typical 9-to-5, often responding to clients or issues at 9 p.m.

Because of this, HR leaders can't evaluate field candidates the same way they evaluate office hires. Sackett recommends:

• Testing candidates' capacity for the lifestyle early — not just their skills, but their tolerance for a job that "never leaves you"
• Getting HR out of the office and into the field to understand what the role actually demands, rather than relying on secondhand reporting
• Recognizing that field employees often meet HR with suspicion ("why are they here, what did I do wrong?") — trust has to be built through consistent, visible presence, not once-a-year check-ins

The Biggest HR Mistake: Big-Bang Program Rollouts

One of the clearest takeaways from the conversation: don't design a large program in isolation and roll it out to the entire field team at once. Sackett describes this as one of the most consistent failure patterns in HR — spending months building a solution, launching it company-wide on a single date, and watching it fail because it wasn't tested with the people who'd actually use it.

Instead, his recommended approach is structured testing:

• Pilot a change with one location, one leader, or one team
• Measure the result — good or bad — and report it back
• Let other teams see the results and ask to adopt it, rather than having it imposed on them

This creates a "test and share" culture where field leaders feel like change agents rather than recipients of top-down mandates.

Standardization Doesn't Mean Identical Treatment

A recurring myth in HR: if you accommodate one employee's need, you have to offer it to everyone. Sackett pushes back directly on this. There's no legal requirement to treat every employee identically in terms of flexibility or benefits — only in terms of pay for the same role. He shares two real examples:

• A field employee who needed Saturday mornings off was told "no" on principle, and left for a competitor — despite data later showing fewer than 5% of employees actually wanted that same flexibility
• A manufacturing client assumed shift flexibility would create chaos, but frontline supervisors — not corporate HR — knew exactly how to rearrange shifts to solve a real retention problem

The lesson: talk to the people actually doing the work before assuming a policy change will cause disruption.

Building Cross-Functional Buy-In (HR, Finance, Operations)

When HR wants to introduce a new flexible benefit — like a vehicle reimbursement program instead of a company car, for example — getting Finance and Operations aligned is often the hardest part. Sackett's advice:

• Speak Finance's language. Instead of citing generic HR ROI statistics, ask the CFO directly what they believe it costs to replace an employee. Build the business case around their number, not an industry benchmark they don't trust.
• Frame retention in terms Operations already cares about — reduced hiring cycles, faster ramp time, and less operational disruption.
• Avoid "vendor math." Vague ROI promises from technology vendors erode credibility with finance leaders. A business case built collaboratively with the CFO carries far more weight than a number handed down from a sales deck.

Mobile-First Technology Is a Retention Issue, Not Just a Convenience

Perhaps the most tactical part of the conversation centered on mobile technology for field employees — and how poorly designed tools quietly drive attrition.

Sackett is blunt about a common failure: companies build their tech stack around desktop-based office employees, then bolt on a "mobile-optimized" version for field teams as an afterthought. The difference in usability, he notes, is stark — and field employees notice.

A specific example discussed at length: manual mileage tracking and expense reporting. Field employees who spend extra hours per week manually logging mileage or filling out Friday expense reports experience this as an unnecessary tax on their time — on top of already long hours on the road. Poor process design here isn't a minor annoyance; it's a documented driver of turnover to competitors who make the process effortless.

Key technology principles for field-heavy organizations:

• Build the process into the technology — not around it. Low adoption is rarely a "bad technology" problem; it's usually a failure to embed the tool into the actual workflow.
• Automate wherever possible. Auto-capture and auto-submit features (for mileage, expenses, etc.) remove friction and reduce the risk of employees forgetting to submit for reimbursement — which directly affects satisfaction and retention.
• Allow flexible usage patterns. Some employees want to check a tool daily; others want to "set it and forget it." Effective mobile tools should accommodate both without requiring heavy customization.
• Use configuration, not customization. Sackett draws a sharp distinction: labeling fields to match your terminology is fine; breaking a vendor's core product to fit legacy habits is not. Products that reach 85–90% fit out of the box, used as designed, typically outperform heavily customized alternatives long-term.

How to Evaluate HR Technology Vendors

Before selecting or renewing a technology partner, Sackett recommends a simple but underused diligence step: ask to speak with three references —

1. A current customer currently going through implementation (to hear real, present-tense pain points)
2. A power user getting the most value from the platform (to see the ceiling of what's possible)
3. A former customer who churned (to understand where things go wrong — often due to implementation choices, not the product itself)

Any vendor unwilling to provide all three, especially a churned customer, is a red flag.

AI in HR: You're Already Using It

On AI adoption, Sackett's core message is that most HR leaders dramatically underestimate how long they've already been using AI — it's embedded in the everyday tools (office software, mobile devices, HR platforms) they use constantly. His recommendations for HR leaders evaluating AI-enabled vendors:

• Ask vendors directly about their ethical AI statement and roadmap
• Understand whether the vendor is using public or private data to train features
• Stay informed enough to have an intelligent conversation with legal and IT teams, who often over-index on AI risk without recognizing how long it's already been in use

FAQ: Hiring and Retaining Field Talent

Why is retaining field employees harder than retaining office employees?Field roles combine high autonomy with high, often unbounded responsibility — employees are frequently "on call" well outside standard hours, and poor tooling or inflexible policies compound that burden, accelerating burnout and turnover.

Does offering flexible benefits to one field employee legally obligate a company to offer it to all?No. Outside of equal pay for equal roles, there's no legal requirement to offer identical flexibility or benefits to every employee. Individualized accommodations, based on real employee needs, are permissible and often more effective than blanket policies.

How does mobile technology affect field employee retention?Field employees who deal with clunky, non-mobile-first tools for tasks like mileage tracking and expense reporting experience this as unpaid administrative burden. This friction is a documented factor in turnover, especially when competitors offer streamlined, automated alternatives.

What's the best way to build a business case for a new HR technology or benefit?Build it using the finance team's own assumptions about cost-per-hire or cost-of-turnover, rather than presenting an external ROI benchmark. A number the CFO already believes in is more persuasive than an industry statistic.

How should HR leaders vet technology vendors?Ask to speak with a current implementation customer, a power user, and a customer who left. A vendor unwilling to provide references — especially a churned customer — is a warning sign.

Interested in how automated mileage capture and flexible vehicle reimbursement programs can reduce administrative burden and improve retention for your field teams? Reach out to Cardata to learn more.

‍