DSP driver attendance tracking that settles the morning count

Why the whiteboard stops working

With 20 drivers a whiteboard is fine. With 60 across two waves it stops telling you anything useful. You lose the history of who calls out on Mondays, you lose the paper trail behind a termination, and you spend Friday afternoon rebuilding timesheets from memory and text messages.

What a working attendance process looks like

• One board for the day showing scheduled, clocked in, called out and no-show
• Call-outs logged with a reason and a timestamp, not a screenshot
• PTO requests handled in the same place so approved time off never reads as a no-show
• Drivers clocking in from their phone in the yard
• A running history per driver, so coaching conversations are based on a record
• Hours that flow into payroll instead of being retyped

How RouteOps Pro handles it

The attendance board opens on today by default and shows every scheduled driver with their status. Dispatch marks call-outs as they come in; drivers clock in and out from My Day on their phone. PTO lives alongside it, so approved days show as approved instead of missing.

Those same shift records feed the payroll view, which splits regular and overtime hours against each driver's rate and exports a CSV you can hand to your payroll provider. Alerts flag coverage gaps while there is still time to call a rescue.

Start with the data you already have

You do not need to start from an empty roster. Bulk import loads drivers from a spreadsheet, and Amazon A to Z time-punch exports import as shifts, so your existing hours come along with you.