Measure the work, not just the count.
Jobs completed, days worked, travel and on-site time, response times met, callbacks and ratings for each technician, with a map of where they worked each day.
Why it matters
Counting closed jobs rewards whoever got the easy ones and makes the technicians who take the hard calls look slow.
In practice
- Two crews, two routes. A window cleaning owner sees that one crew spends far more time driving than the other and asks the office to tighten that crew’s routes.
- Callbacks after repairs. An HVAC service manager spots a technician with more callbacks on one job type and schedules a ride-along.
How it works
Recorded from the app
Built from the status changes technicians make: en route, on site, resolved.
Compare fairly
Each technician next to the team average, with their mix of job types.
See the day
A map of the day’s jobs, numbered in order, with the route along streets.
Key features
Team dashboard
Key numbers versus the previous period, a daily chart and a sortable table of technicians.
Per-technician map
Jobs numbered by day, with the street route for any day you pick.
Fair credit
Only work done in the field counts; jobs closed at a desk are left out.
Forgotten taps ignored
Steps longer than eight hours aren’t counted as travel or on-site time.
Hours and job cost
Logged hours and job costs alongside the timing, when you use job costs.
CSV and print
Download the table or print it; also available as a scheduled report.
Common questions
Does it track technicians all day?
No. It uses job status changes and job addresses. Live location sharing is separate and opt-in; see the live map.
What if someone forgets to tap resolved?
Steps longer than eight hours aren’t counted, so one forgotten tap doesn’t skew the numbers.
Who can see it?
Owners, admins and team leads for their own teams.