Dutybound, by Onnsight · for dedicated driver services
The shift is the record.
A named driver, in a specific car, at a specific place, for a specific stretch of hours. That is what you are paid for, and exactly what gets disputed. That is what you sign off every month, and exactly what gets questioned.
Month end
Tuesday, 06:00 to 22:00. The client says no. Tuesday, 06:00 to 22:00. Nobody can prove it.
Your evidence is a logbook, a photo in a group chat and your driver's word, reconciled a month after the fact against someone who remembers it differently. The evidence is a logbook, a photo in a group chat and the driver's word, reconciled a month after the fact against someone who remembers it differently.
- The logbook
- Handwritten times, corrected in the same pen. Nothing says when the ink went down.
- The photo
- An odometer reading in a group chat. It shows when it arrived, not when or where it was taken.
- The driver's word
- True or not, it is one side of an argument.
05:50 · the basement under the expat's building
The shift starts where the signal ends.
05:50. The car spent the night in the basement car park under the expat's building, and the driver walks down to it. No network, no supervisor. The day ends down here too, at 22:00, with nobody watching either. Here, underground parking is the normal case, not the edge case.
Three usual fixes
Every usual fix needs the thing the basement doesn't have.
Track them, and nothing else
A trail shows where the car went, not that the driver clocked in. And it breaks at the ramp, exactly where the shift starts.
Make them send a photo
It arrives when the signal does, stamped with the time it arrived, not the time it was taken.
Have a supervisor sign
There is nobody there at 05:50 or at 22:00. The signature gets collected at month end, from memory.
06:00 · clock-in
You can only clock in once you're there.
The driver's phone confirms it is beside the car, inside the site boundary, before the shift can start. Attendance stops being something the driver says and becomes something the record observed. It works with no signal at all. As soon as the phone is back in signal, the admin dashboard shows the driver on duty. Or drag the driver to the car.
Outside the site boundary. Clock-in stays closed.
- Outside the site boundary
- Clock-in stays closed. Nothing is recorded.
- Inside the site boundary
- The shift starts, recorded on the phone, with no signal.
06:30 · pickup at the lobby
Nobody has to call to ask where the driver is.
The opening odometer was photographed into the shift before the car left the basement, not sent to a group chat. By the time the expat comes down, the admin dashboard already shows the driver on duty.
07:15 · the client's office
Waiting is part of the shift.
The expat goes in. The car waits in the office car park, and so does the driver, for most of the day. Nothing marks the pickup, the drop or the wait: on the admin dashboard the driver is simply on duty, from clock-in to clock-out. Those hours sit inside the same record that started at 06:00 in the basement, not in a gap someone has to explain at month end.
13:00 · lunch, still on duty
The rest of the day goes into the same record.
Meals and expenses
Claimed against a policy.
Leave
Applied for against a real balance. An approved day is blocked outright.
Service reminders
When the car is due for a service, the reminder reaches the phone the driver already clocks in with, not a sticker nobody reads.
22:00 · back in the basement, and the day as the office sees it
It arrives late, and it arrives whole.
The expat is home, the car is back in its bay, and the driver clocks out beside it, underground again. The second location reading is taken at clock-out. In between, the phone records nothing unless the account has switched on the trail. Either way, the shift waits on the phone until there is signal, and syncs on its own once the driver is back up the ramp. That is when the admin dashboard shows the driver off duty. The app says nothing about it unless something genuinely needs the driver.
- 06:00Clock-in, inside the site boundary
- 06:00–06:25 · 21:50–22:05No reading underground. Shown as a gap, not a guess.
- 06:25–21:50On the move, a reading at regular intervals
- 07:20–20:35Readings in one place: the client's office car park
- 13:00–13:40Readings on foot, at a café
- Nothing recorded between the two
- 22:00Clock-out, back at the bay
Month end, again
Correct it without hiding what you corrected.
The office reviews what came in and fixes what needs fixing, with the driver's original submission still visible underneath. A correction that hides what it corrected is worth little in a dispute. This one is the dispute's answer.
Shift · Tuesday · 06:00 to 22:00
- Clock-in
- 06:00Inside the site boundary
- Opening odometer
- 48,190 kmPhoto in the shift
- Closing odometer
- 48,386 kmCorrected by the coordinator 48,836 kmDriver's original submission, still visible
- Clock-out
- 22:00Location recorded at clock-out
Operations head
Every account, on the same terms. Every site, on the same terms.
Coordinators assign drivers, watch coverage and approve what came in. The operations head moves between client accounts without changing how anything is recorded. Every shift in every row was observed at both ends. Coordinators assign drivers, watch coverage and approve what came in. The operations head moves between sites and departments without changing how anything is recorded. Every shift in every row was observed at both ends.
What it isn't.
- Not ride-hailing. Drivers are assigned for a posting, not a trip.
- Not tracking by default. Location answers "were you here when you said you were?" at clock-in and clock-out. A trail between the two can be switched on, with the driver's consent, for accounts that need the route.
- Not routing.
- No hardware. The driver's own phone is the whole field deployment.
Screens.
Demo data only. Placeholders until real screens are approved.
Driver · clock-in. The same screen outside the site boundary and inside it.
Driver · no signal. The shift keeps recording. Nothing asks the driver about syncing.
Driver · odometer. The reading is photographed into the shift.
Coordinator · review. A correction with the driver's original underneath. See the record above.
Coordinator · shift trail. Optional. The day as a timeline on a map, with gaps where there was no reading. See the trail above.
Operations head · accounts. Coverage across client accounts.
Where it stands.
In production with one client since [month]. A reference call is available on request.
Shifts on record
- Shifts recorded
- 1,200+
- No-signal clock-ins
- 1,000+
- Of those, lost
- 0
- Longest wait to sync
- ~14 hrs
- Corrections kept
- 60+
- Disputes settled
- 20+
Illustrative figures for this draft, standing in for the pilot's real numbers.
Tell us about the shift you couldn't prove.
If you manage a fleet of assigned drivers and already know which shifts turn into arguments, describe one in a paragraph and send it over.