The Drivers Duty Log is a record of every time one of your drivers went on duty or off duty. Find it in the dispatch software at Drivers → Drivers Duty Log (/app/drivers-onduty-log).
What the table shows
- Log ID — the row's own id.
- Driver ID and Name — who changed status. The name is stored on the row at the time it happened, so the log still reads correctly if the driver is later renamed or removed.
- Duty Status — on duty or off duty.
- Date — when the change happened, in your account's time zone.
The table is searchable and sortable, so you can pull one driver's day out of it quickly.
Where the entries come from
Drivers set their own duty status in the Zippykind driver app. Every change writes one row here. There is no way to change a driver's duty status from the dispatch software — it is the driver's switch, and this page is the record of what they did with it. A duty change also fires an on_duty_status webhook if you have webhooks configured, so an external system can react to it. See What are webhooks.
Why duty status matters elsewhere
Duty status is read by several settings, which is what makes this log worth looking at when something did not behave as expected:
- Send Push Notifications Only To On-duty Drivers (General Settings) — decides who gets notified about a new ticket.
- Include Off-duty Drivers (Auto-Assignment) — decides who a ticket can be auto-assigned to.
- Include Offline Drivers (Dashboard Map) — decides who is drawn on the dispatch map.
So "a driver never got the ticket" and "a driver vanished from my map" both have the same first thing to check: was that driver on duty at the time? This page answers it.
Using it for shift review
The duty log tells you when a driver clocked on and off. If you want the delivery work inside those hours instead, the week view of the Schedule Manager shows each driver's first and last ticket of the day and their ticket count, and the Data Exporter can produce a driver performance file over a date range.