# Time tracking for drivers and couriers

> Time tracking for drivers and couriers: shifts that start at the depot and end elsewhere, waiting time, overnight trips, allowances and payroll exports.

URL: https://timetracking.tech/for/transport
Language: en
Last updated: 2026-10-26

A driver's day rarely ends where it started. It begins at the depot before sunrise. It includes an hour of waiting at a dock. It ends at a customer, a hub or a parking area abroad. Drivers log that day from the cab in TimeTracking. So planning and payroll use real hours, not a trip sheet filled in from memory. Start free for up to 5 users.

## How transport companies use TimeTracking

1. **Start the shift at the depot**: Drivers start the timer in the app when they pick up the vehicle. Or they clock in with a personal PIN at a kiosk tablet in the depot.
2. **Log waiting time and expenses on the road**: Waiting at a dock, loading and other work each go on their own line. Parking, meals and overnight costs go on the same day.
3. **Stop wherever the shift ends**: Drivers close the shift in the app at the last drop, the hub or the overnight stop. No signal? Hours wait on the phone and go out later.
4. **Approve and export**: The planner checks the week against the roster and approves it. Hours, allowances and expenses go to payroll in one export.

## A shift that does not end at the depot

Most time clocks expect people to start and stop in the same building. Drivers don't. In TimeTracking the timer runs on the driver's phone. So the shift can start at the depot in the morning and end at a customer, a cross-dock or a truck stop at night. The timer keeps running when the app is closed or the phone restarts. Entries made without coverage go out as soon as the phone is back online.

Some drivers start and finish at the depot, such as on regional rounds. They can clock in and out at a kiosk tablet in the depot, with a personal 6-digit PIN. No need for their own phone. Both ways end up in the same period, ready for approval.

- Timer that survives app restarts and phone reboots
- Offline queue for routes without coverage
- Kiosk with PIN in the depot
- Shifts across midnight kept as one shift

## Waiting time is working time

An hour waiting for a slot at a distribution centre is part of the working day. Many collective agreements pay it differently from driving. In TimeTracking, drivers log waiting, loading and other work as separate lines. Each line has its own hour type. Each hour type has its own payroll code in the export. So waiting time is paid the way your agreement says.

Waiting time shows per day and per driver. So planners see where it piles up. Then it is easier to raise the issue with a customer. Or to replan a route that keeps running late.

## Overnight trips and allowances

International and long trips often include a night away. A shift from the evening until after midnight stays one shift, with the right totals. Overnight allowances, meals and parking go next to the hours, as expenses or fixed allowances. You approve them together. They go in the same payroll export.

The rule engine works out overtime and shift allowances by the bands you set. It warns planners when a roster leaves too little rest between two shifts.

- Overnight and late shifts across midnight
- Expenses and fixed allowances per day
- Overtime and allowance bands in the rule engine
- Rest-time warnings while planning

## Hours, not tachograph data

TimeTracking logs working time for payroll and planning. It does not read tachograph data. It does not replace the tachograph or your driving-time software. Driving and rest times under EU rules stay where they belong. TimeTracking makes sure the hours you pay are complete and approved. They are exported without retyping.

TimeTracking does not track drivers' location and takes no screenshots. The app logs the hours the driver enters or clocks, nothing more. That keeps the talk with drivers and the works council simple.

## Couriers, part-timers and peak days

Parcel and courier firms rely on part-timers and extra drivers on busy days. Invite new drivers by SMS. They log in with a one-time code and pick one of 20 languages. Post open shifts in the roster, and free drivers can take extra rounds. The planner decides who gets them.

Someone stops working for you? Switch them off. Their hours and exports stay in the history. You only pay for active users.

## Payroll exports: what is live and what is coming

Approved periods are exported in one step. Live today: an SD Worx-format export, CSV, XLSX and JSON exports you set up yourself, and the REST API. Connectors for Loket, Nmbrs and AFAS are coming soon. Exported periods are locked. A late fix becomes a line in the next period.

TimeTracking does not do route planning, fleet management or invoicing. It delivers approved hours to the systems you already use. All from €1 per user per month, with no add-ons.

## Frequently asked questions

### Can a shift start at the depot and end somewhere else?

Yes. The timer runs on the driver's phone. So the shift can end at the last drop or the overnight stop. Drivers who clock in at the depot can use a kiosk there.

### Does TimeTracking read tachograph data?

No. TimeTracking logs working time for payroll and planning. It does not read or replace the tachograph or driving-time software.

### Can waiting time be paid differently from driving?

Yes. Waiting time is its own hour type. It has its own payroll code in the export.

### What happens on routes without mobile coverage?

The timer keeps running offline. Hours wait on the phone and go out automatically when the connection is back.

### Does it track where drivers are?

No. TimeTracking does not build a location trail. It logs the hours drivers clock or enter.

### What does it cost?

Free for up to 5 users. Then €1 per user per month on Core. That includes rosters, expenses, approvals and payroll exports. No add-ons, no seat minimum.
