To manage field technicians well, set written standards for what a finished job looks like, run a short daily rhythm of morning briefing and end-of-day closeout, judge performance with a small scorecard that separates what the tech controls from what the schedule handed them, and coach in person on ride-alongs. Most technician problems that look like effort problems turn out to be schedule, parts or training problems.
Managing a field technician isn't like managing someone at a desk. You can't watch the work. The tech is alone in a customer's basement making judgment calls about diagnosis, pricing and safety. By the time you hear about a problem, it's usually a callback or a complaint.
That's why field management runs on standards, rhythm and numbers rather than supervision. This guide covers each.
Start with written job standards
You can't hold a tech to a standard that only exists in your head. Before you measure or coach anything, write down what "done right" means for your most common job types.
A useful standard covers:
- Arrival: when to call ahead, what to do if running late, how to introduce yourself
- On site: shoe covers, drop cloths, where to park, what to explain before starting
- Diagnosis: what to check every time, even when the problem seems obvious
- Options: how to present repair choices and prices, if your techs quote on site
- Closeout: what goes in the work order, which photos, what to tell the customer before leaving
Keep each one to a page. Techs won't read a manual, but they will use a checklist. The work order management guide has a closeout standard you can adapt.
Run a short daily rhythm
Field teams drift without a routine. Three touchpoints a day is enough for most companies.
Morning briefing (10 minutes)
Before trucks leave, or on a call if techs start from home. Cover today's unusual jobs, any customers with history, parts that came in, and safety notes. Don't let it become a meeting. Ten minutes, standing up.
Midday check
A quick message or call between the dispatcher and each tech around lunch. Is the day on track? Any jobs running long? Anything that needs a part or a second tech tomorrow? This is where the dispatcher catches problems while there's still time to move afternoon jobs.
End-of-day closeout
Every work order closed out to standard before the tech signs off. Not the next morning, and not at the end of the week. Memory fades fast, and incomplete closeouts cost money in billing and in the next visit.
Build a fair scorecard
Numbers help you manage people you can't see, but only if the numbers measure the tech, not the schedule they were handed. Keep the scorecard to five or six measures.
| Measure | What it shows | Mostly controlled by |
|---|---|---|
| First-time fix rate | Diagnosis skill and preparation | Tech, plus truck stock |
| Callback rate | Quality of the work | Tech |
| Closeout pass rate | Documentation quality | Tech |
| Average ticket | Options presented, upsell | Tech, plus job mix |
| On-time arrival rate | Punctuality | Schedule, more than the tech |
| Jobs per day | Throughput | Schedule and territory, more than the tech |
The last two rows are where managers get it wrong. If a tech is late twice a day, the instinct is to have a talk with the tech. Often, the schedule never gave them enough time to drive between jobs. If one tech does 4 jobs a day and another does 6, check the drive time before you compare them.
Normalize for drive
A simple fix is to compare techs on wrench time, not total paid time.
On-site productivity = jobs completed ÷ on-site hours
On the jobs count, Tech B looks 27% better. On the time they actually had at jobs, they're the same. Tech A's problem is the territory, not the technician. The tools to run this on your crew are the technician utilization calculator and the glossary entries on wrench time and technician productivity.
You can only normalize for drive if drive is visible. On most scheduling boards, a two-hour block includes the drive inside it, so nobody can tell. CrewLink keeps drive time next to the job instead of hiding it inside, which is what makes this kind of comparison possible.
Coach in the field
The scorecard tells you where to look. Coaching happens on site.
Ride-alongs. Spend half a day in the truck with each tech every quarter, more often for new hires. Watch the whole visit: arrival, diagnosis, how options are presented, closeout. Say little during the job. Talk in the truck afterward.
One thing at a time. Pick one behavior to improve per conversation. "Take the equipment label photo every time" is coachable. "Be more professional" is not.
Use the callback review. When a callback happens, review it with the tech within a day or two. Focus on what would have caught it: a missed check, a part that should have been replaced, a test that wasn't run. Treat it as a training gap, not a punishment, or techs will start hiding callbacks.
Pair new techs. A new hire learns faster riding with your best tech for their first weeks than from any manual. See technician onboarding.
Balance the workload
Uneven workload is one of the fastest ways to lose good techs. Your best tech gets the hardest jobs, the emergency calls and the overtime, because they can handle it. Eventually they leave.
Technician workload balancing means watching three things weekly:
- Hours worked per tech, including overtime. See overtime cost.
- Job difficulty mix. Are the same people always getting the long diagnostic calls?
- On-call share. Is the on-call rotation actually rotating?
If one tech is consistently doing more, either pay them for it explicitly or spread it out. Silent overload is how you lose the person you can least afford to lose. The technician retention guide covers the other reasons techs leave.
Pay structures, briefly
How you pay techs shapes behavior. The common structures:
- Hourly: simple, fair for variable work, but no direct reward for productivity
- Hourly plus bonus or commission: rewards average ticket or agreement sales, but can push overselling if not watched
- Flat-rate (piece-rate) pay: pays per task, rewards speed, can punish techs who get bad territories or hard jobs
Whatever you choose, make sure the measure you reward is one the tech actually controls. Paying on jobs per day when the schedule decides jobs per day will feel unfair, because it is. Pay rules involve wage and hour law, which varies by state. Get advice from an employment attorney or payroll professional before changing pay plans.
Tracking and trust
Many companies use GPS or telematics to see where trucks are. Used well, it helps dispatch and answers customer questions. Used as a surveillance tool, it damages trust fast. Tell techs what's tracked and why, and use it to fix schedules rather than to catch people. Rules on employee monitoring vary by state, so check with an employment attorney.
When it's a people problem
Sometimes it really is the technician. Signs that point to the person rather than the system:
- Callback rate stays high after training and ride-alongs
- Closeouts stay incomplete after clear feedback
- Customers complain about behavior, not timing
- Peers on the same territory and job mix perform well
Document the standard, the gap, the coaching and the timeline. Then act. Keeping a tech who doesn't meet the standard tells everyone else the standard is optional.
For the wider system around your techs, see the pillar guide to field service management and the field service workflow guide.
What to take away
- Write a one-page standard for each common job type. You can't manage to a standard that isn't written down.
- Run a short daily rhythm: morning briefing, midday check and closeout before sign-off.
- Keep the scorecard small, and separate what the tech controls from what the schedule handed them.
- Compare techs on jobs per on-site hour, not jobs per day, so territory and drive don't distort the picture.
- Coach on ride-alongs, one behavior at a time, and watch workload so your best people don't burn out.
Common questions
How do you manage field technicians effectively?
Set written job standards, run a short daily routine, track a small set of measures the tech actually controls, and coach in person through ride-alongs and callback reviews. Fix schedule, parts and training problems before treating something as an effort problem.
What KPIs should I track for field technicians?
First-time fix rate, callback rate, closeout quality and average ticket are mostly in the tech's control. On-time arrival and jobs per day depend heavily on the schedule and territory, so normalize them for drive time before comparing technicians.
How do I hold technicians accountable without micromanaging?
Agree on clear standards, measure outcomes instead of minute-by-minute activity, and review the numbers together regularly. Accountability works best when the tech can see the same scorecard you see and knows which measures are theirs.
Why do some technicians complete fewer jobs than others?
Often it's territory and drive time rather than effort. A tech working an outer area may spend twice as long driving. Compare jobs per on-site hour to see whether the gap is the person or the route.
Should I use GPS tracking on my technicians?
Many companies do, mainly for dispatch and customer updates. Be open with techs about what's tracked and why, use it to improve scheduling rather than to catch people out, and check state rules on employee monitoring with an employment attorney.