Hiring a field worker doesn’t create a route. It creates payroll, training, and a promise of work you now owe someone. If the route can’t carry that promise, the title is just a nicer label for a future schedule cut.
Call the control point qualified route coverage. It’s the field work that exists in a defined interval, inside a workable service zone, for a person with the required skill, after travel and customer windows have taken their bite. Scheduled headcount isn’t that. A filled vacancy isn’t that either. Both can look tidy right up until your new hire asks why Tuesday vanished again.
Your hiring plan starts with the route that can support a job.
The Requisition
Start with your last 4 to 8 weeks of uncovered work. Record the task, when it occurs, the consequence of delay, recurrence, required skill, and service zone. That’s a requisition: a decision to acquire a defined block of work, not yet a job title.
For field work, daily intervals usually expose the right problem. You may need 15- or 30-minute intervals for a call queue or dispatch surge, and weekly intervals can suit bookkeeping while flattening a service route into fiction. A weekly total can say there are enough labor-hours while windows, travel, and qualified hands collide. Your customer will call it late.
Build your role around one primary outcome, 3 to 6 recurring responsibilities, and 2 to 4 capabilities needed on day one. Those are operating bands, not universal law. The point is to stop combining a technician, dispatcher, estimator, parts runner, and founder’s errand service into one “flexible” opening. Tightly coupled duties belong together. Unrelated shortages don’t become coherent because one payroll line would be convenient.
First remove or automate work that shouldn’t become permanent, then reassign any coherent block, then hire or buy an outside service for what remains. If nobody can answer day-to-day questions or inspect the output, you’re recruiting early. You have a vacancy-shaped feeling, not a role.
The Windshield
The service area belongs in the role promise. A technician’s economic territory isn’t a circle around your shop. It’s the actual route before and after an appointment enters it.
In the corpus’s field example, placing one job adds 16 km to the complete route even though the prior stop is 11.8 km away. The route moves from 62 km to 78 km. That’s why straight-line geography produces so many cheerful staffing plans and so many resentful windshields.
Measure your route through the work it converts into completed jobs:
- Miles and windshield minutes per completed job, including failed access and callbacks.
- Completed jobs per paid route hour, with driving, parking, access, restocking, and window waiting left in the denominator.
- Contribution per truck-day, after parts, field labor, acquisition, subcontractors, payment charges, and warranty allowance have been identified.
The distinction matters because a scheduled 8-hour day with five calls and 150 minutes of travel isn’t the same capacity as five calls clustered into 90 minutes of travel. The second one releases an hour. But it only becomes another ticket if demand, parts, skill, and the remaining appointment windows permit a completion. Route design is a capacity control, not a map decoration.
Separate your recurring routes, emergency dispatch, and project work before you promise a role.
Routes can move a nearby visit to tighten a day. HVAC, plumbing, and electrical faults carry urgency, uncertain duration, parts risk, and after-hours coverage. Replacement work adds estimates, permits, deliveries, and specialized crews. One blended “average route” produces a different calendar every week.
The Promise
Your job packet has to say what the worker will do, who directs it, where and when it happens, what a difficult day contains, and what success looks like after training. An unknown employer has fewer reputational signals, so vague phrases such as “other duties” ask applicants to price the uncertainty themselves.
Put the promise in operating terms before you post: coverage window, service-zone rule, travel basis, scheduled-hour minimum, skill, manager, compensation, first-month deliverables, selection duration, and response timing.
Pay your role against the same occupation, location, industry, and experience level, and BLS publishes wage percentiles as comparison anchors. National averages are not route design.
Use 2 or 3 distinct sourcing channels before scattering the post across ten copies of the same market. A local network, an occupation-specific board, and a general marketplace can each reveal a different failure. Track source through application, qualification, interview, offer, acceptance, start, and the later survivor point. A candidate who withdraws after learning about routine weekend coverage hasn’t disproved the channel. The condition arrived late.
| Field-role promise by service zone | Demand interval | Travel time | Minimum hours | Notice period | Skill requirement | Proficiency date |
|---|---|---|---|---|---|---|
| Compact recurring route | Daily service window; use smaller intervals where peaks need them | Complete route before and after insertion | Committed coverage for the recurring block, not a manufactured full-time total | Publish at least 14 days ahead; freeze the next 7 days except for genuine exceptions | Named task and route qualification | Observable checkpoint tied to task risk |
| Emergency and repair zone | Arrival windows and dispatch intervals | Include driving, parking, access, parts, waiting, callbacks, and return legs | Explicit reserve for urgent work, not hours silently held for demand | State which changes are genuine exceptions and who may make them | Fault type, licence or equipment qualification where required | Safe setup by day 5 can be an illustrative first checkpoint |
| Project and installation territory | Estimate, permit, delivery, and production dates | Include site visits and multi-stage crew movement | Defined project block rather than a weekly average | Publish the actual production commitment, not a hopeful availability range | Specialized crew or trade requirement | Routine work with review by day 20 and independent exceptions by day 60 are illustrative checkpoints |
Those dates aren’t a generic technician curriculum. They’re examples of the right shape: an observable decision or output, a stated supervision level, and a date. “Fully onboarded” is too soft to schedule against.
The Schedule
Total weekly hours are only one setting. Stability also includes notice, variation, consistent days and starts, availability control, shift length, recovery time, and labor held unassigned until demand is known. A schedule posted early but rebuilt every afternoon isn’t stable.
Give 14 days of committed notice, freeze the next 7 days except for genuine exceptions, and keep employer-driven weekly-hour variation below 25% as practical starting settings.
The Department of Labor synthesis treats volatility above 25% across the prior month as one analytical boundary, and separates employer-imposed variability from flexibility the worker chose. That difference matters. A worker taking an extra shift isn’t evidence that a cancellation was harmless.
In a large study of hourly workers at retail and food-service companies, more than 15% had less than 72 hours’ notice, only about a third had at least two weeks, and weekly hours swung 36% between high and low weeks. That sample isn’t an SMB benchmark. It shows that instability has several mechanisms.
Make your reserve capacity explicit: cross-trained owners, voluntary standby workers, or a defined overlap block. Don’t obtain it through routine same-day calls.
Job-site-to-job-site travel during the workday is work time, and covered non-exempt employees receive overtime after 40 hours in a workweek at no less than 1.5 times the regular rate under the federal rule the corpus describes. A route can’t become more productive by making paid travel disappear on the dispatch board.
The Coverage Test
Test each schedule you publish against demand blocks small enough to show the failure. Record required people or labor-hours by skill and location, published assignment, later changes, and attendance.
In the corpus’s seven-day example, 407 scheduled hours become 371 qualified hours because 36 hours lack the required opening or equipment qualification. Apparent coverage of 96.9% becomes 88.3%.
Keep construction and execution separate in your record. Construction covers qualified coverage, excess coverage, consecutive-shift patterns, and first publication date. Execution covers manager edits, worker swaps, call-outs, lateness, no-shows, and actual versus planned hours. Preserve who initiated the change. A voluntary swap and a same-day employer cancellation may each move four hours, but only one tells the worker the promise was provisional.
The Signature of the Loss
Use the signature of the loss. “Nobody wants to work” isn’t a diagnostic category. It’s a way to avoid opening the schedule.
New hire leaves before proficiency → the role promise is broken
Compare actual hours, zone, task mix, manager access, and schedule changes with the packet you published. Measure the cohort from actual start through 30, 90, and 180 days, not from accepted offer.
The rota has names but jobs miss windows → qualified coverage is broken
The schedule ignores travel time, service-area density, required skill, or attendance. Inspect your exposed intervals, not just the weekly total.
Applicants accept then withdraw after the details → disclosure is broken
The coverage window, routine weekend work, travel, compensation basis, or decision authority appeared after the applicant had already evaluated a different job.
Scheduled hours repeatedly fall after a start → demand matching is broken
The position was built from average weekly labor, not from recurring work in compatible zones and intervals. Rebuild your requisition from the last 4 weeks of route demand.
You still answer every exception after training → authority transfer is broken
Access and introductions happened, but decision boundaries, acceptable output, and escalation conditions didn’t. Rework after every independent choice is the evidence.
Departures cluster around one shift, manager, or the first solo route → schedule or transition design is broken
Compare published schedules, later edits, travel conditions, trainer, and task authority before you reach for an economy-wide tenure story.
The First Month
An accepted offer is an administrative event. A start is a workforce event.
A productive start needs your payroll, notices, accounts, keys, equipment, safety instruction, schedule access, a named trainer, and an actual first-week schedule.
For U.S. employees, Form I-9 Section 1 is due no later than the first day. Section 2 is normally due within 3 business days, or on the first day when employment lasts fewer than 3 business days.
Pair your hire with an experienced worker, state which tasks may be performed independently, and name the unfinished-work handoff.
Check in after the first shift, the first full schedule, and the first month. That’s correction of access, training, workload, and schedule expectations — not a vague request for feedback that leaves the worker to solve a broken route alone.
Track retention as start-date cohorts. Published median tenure figures are context, not permission to lose a new technician. The useful question is whether the promised job and the actual route still agree after the worker has had time to see both.
A job title fills a vacancy. A workable route retains a field worker. Scheduled hours show intent. Qualified route coverage shows capacity.
Promise the route before the role. Publish the work before the worker starts. If the coverage can’t survive the calendar, don’t recruit for it.