Skip to main content

Driver timekeeping

Shifts, breaks, odometer capture, and the end-of-shift check — how clock in/out works in the driver app.

Last updated October 20, 2026

Drivers track their working time right in the app, under Timekeeping on the Home screen. Those records flow straight into the office's Payroll pages — no paper timesheets.

The shift flow

  • Start Shift — clock in. The app records the time, the driver's GPS position, and the vehicle's odometer reading.
  • Start Break / End Break — if your company allows breaks, drivers can record breaks during the shift. If a driver forgets to tap End Break and starts driving, dispatch sees Break still open and can end the break for them.
  • End Shift — clock out, again with GPS and odometer. The app shows the total time worked.

The status card reads Not started, Shift Active, On Break, or Shift Complete, with a time grid (Start Shift, Break Start, Break End, End Shift) and a live Worked so far total.

Starting the shift matters beyond payroll: it begins GPS sharing with dispatch, and (when timekeeping is on) the app requires an active shift before stops can be marked.

The end-of-shift check

If trips are still pending when a driver tries to end their shift, the app stops them: an alert lists how many trips are unresolved, with two choices:

  • Back to trips — go finish (or cancel/no-show) the remaining stops. This is the normal path.
  • End shift anyway — after a second confirmation and a reason, the shift ends with pending trips. The override and reason are recorded on the shift for the office to see.

This guard keeps "forgot to mark the last drop-off" from turning into missing completion data on tomorrow's claims.

Your company chooses how strict this is (Settings → Driver app → Trip flow tab → Driver app permissions → When a driver ends their shift with trips still pending): Warn the driver, then allow is the behavior above; Require the office to end the shift removes the driver's End shift anyway — the app tells them to ask dispatch, and dispatch gets a bell alert; Allow without checking skips the check.

Reminders to end the shift

A driver who forgets to clock out leaves an open shift on the office's Payroll pages. Companies can have the app remind them, with a phone notification that says Still clocked in? Reminders are off until an admin turns them on under Settings → Driver app → Shifts & time tab → Shift reminders, and each one is sent once per shift.

  • After the last stop — sent when the driver has nothing left on their schedule for the day, their last stop was completed a set number of minutes ago (5 to 240), and the shift is still running. A driver with a rider on board or a pickup still to come is never reminded.
  • At a set time — sent to any driver still clocked in at a time of day you choose, in company time (up to 11:45 PM). Drivers who clocked in after that time are not reminded.
  • Tell dispatch if there is no clock-out — optional. If a reminded driver is still clocked in an hour later, dispatch gets one bell notification naming the driver, with a link to the Employees page where the open shift can be reviewed.

The reminder is a nudge, not an action: nothing is clocked out automatically by it. Shifts that are never ended are still closed by the overnight auto-close, so a missed reminder never leaves a shift running for days.

When the office needs to step in

A driver can't always fix their own status — they forgot to end a shift, left a break open, or the app refused to end a shift that has been open longer than 16 hours (which happens after an accidental early-morning clock-in). Office staff with dispatch access can Start Shift / End Shift and Start Break / End Break for any driver straight from the Dispatch board, using the two icons beside the driver's name. The punch is recorded exactly as if the driver had tapped it and shows in Settings → Activity log (filter Person to a name) under the staff member's name. See The Dispatch board.

Forms at clock-in and clock-out

Companies can attach forms to the shift boundaries. Under Shift Forms on the Home screen, drivers see their Pre-Shift Forms and Post-Shift Forms with a completed count; after clocking in (or out), any required forms open automatically to fill in. Vehicle inspections are separate and are covered in Inspections and expenses.

Office-side settings

Admins control timekeeping behavior from the web portal:

  • Settings → Driver app → Shifts & time tab → Timekeeping — the Allow breaks toggle. Off means drivers see only Start Shift / End Shift.
  • Settings → Driver app → Shifts & time tab → Shift reminders — the two clock-out reminders (After the last stop and At a set time) and the dispatch escalation described above. All three are off by default.
  • Settings → Driver app → Trip flow tab → Driver app permissions — what happens when a driver ends a shift with pending trips (warn, require the office, or allow).
  • Settings → Driver app → Location & GPS tab → Mobile trip tracking — the Driver location ping interval (10 seconds to 2 minutes; pings stop on clock-out).

Where the records go

Each day's clock-in, break, clock-out, odometer readings, and worked total appear on the Payroll → Today page in the web portal, alongside trips completed and trip hours — see Payroll and expenses. Drivers see today's record in the app; historical review and corrections happen on the office side.

Clock-in windows

Two optional company settings control how early a driver can clock in:

  • Early clock-in window — a fixed number of minutes before the scheduled shift start. A driver clocking in earlier sees a clear "too early" message with the allowed time. Drivers with no schedule for the day are never blocked.
  • Dynamic clock-in — instead of a fixed window, the earliest clock-in is computed per driver: first pickup time, minus the driving time from where their vehicle currently is, minus a small lead buffer you choose. If the vehicle's location is stale or there's no scheduled first pickup, it falls back safely to the fixed window rather than blocking anyone.

Still stuck? The ZeitRide team is one message away.

Contact support