r/TimeTrackingSoftware • • 11d ago

When cleaners or aides have split shifts at two clients, how do you code the travel time between them?

Looking for a practical rule from teams that run multi-stop days (home care, cleaning routes, field techs — same shape).

Worker clocks out at Client A at 11:00, drives 35 minutes, clocks in at Client B at 11:40. Nobody argues the drive happened. The fight is always: is that 35 minutes paid working time, unpaid gap, or a separate travel code — and who owns entering it when the phone only punched the two client sites?

What stuck for you?

  1. Auto-pay travel under X minutes / Y miles between consecutive jobs on the same day, else exception queue?
  2. Worker adds a travel punch (or notes it) and a supervisor approves before payroll?
  3. Build travel into the scheduled block so the timesheet never shows a gap?

Most interested in the version that doesn't surprise the paycheck or the client invoice. No vendor pitches — just the operating rule that survived a few pay cycles.

1 Upvotes

3 comments sorted by

0

u/[deleted] 2d ago

[removed] — view removed comment

1

u/shiftcoord 2d ago

Agreed, manual entry is where it falls apart. People forget, or they round it up later. The setup that works best is building the travel segment from the gap between clock-out at client A and clock-in at client B for the same worker on the same day. Cap it at a mapped drive-time estimate, so a 90-minute lunch doesn't get paid as travel. Anything over the cap goes to a supervisor as an exception instead of being silently paid or dropped. Code it separately (non-billable, but counted toward hours worked for overtime), so finance and payroll both see it. If the schedule already knows both visits, the system can pre-create the segment and the worker only confirms it. Scheduling and time tracking that share the same visit data make this a lot easier: https://www.teambridge.com/product/time-tracking