How much of the time On Route is covered by the work that was done. Driving is credited at the map's time for each drive the tech actually made, so a zone that's more spread out isn't penalized for being a different shape than someone else's.

For every day in the selected range with route work logged:

• Time earned = each machine visit's standard time (the tech's own average minutes per machine, or the time for that exact job type once Predictive Job-Time is on in App Settings) + the map's drive time for each drive made. A visit under 10 minutes earns only its own minutes.
• Time On Route = the time the tech was clocked in On Route. Every other status — Admin, Training, Break, Other, Lunch, On Call — has nothing to do with the score, nor does a stop added at a plain address (a FedEx drop-off). Logging out early is never held against anyone.

The score for the whole range is (sum of every qualifying day's time earned) ÷ (sum of every qualifying day's time On Route) × 100 — not a day-by-day average, so one unusually short or long day can't swing the whole range.

100% means every minute On Route was covered by the standard time for the work done. A visit that ran longer than its standard, a drive longer than the map's, and time between stops earn nothing, and that is what takes a day below 100%. Finishing jobs faster than their standard takes it above. A day with no route work logged isn't counted at all.

Color bands (red/yellow/green) are admin-configurable in App Settings. A tech with too little history yet to have a reliable personal average uses a reasonable fallback until they build one up.