Transport is unusual. It is one of the few industries where the staff are deliberately not where the business is. The depot is in Tema. The driver is on the Accra to Kumasi road. The conductor is in Aflao. Whatever attendance system you use has to handle the fact that the work is happening, by design, somewhere you can't see.
Most Ghanaian transport operators handle this with phone calls and trust. A driver calls in when they leave Tema. They call again when they arrive in Kumasi. The supervisor writes it down. At month-end, the office assembles the calls into a payroll. Sometimes it works. Often it doesn't, especially when a driver claims a route ran longer than it did, or a conductor's hours don't match the driver's.
This page is about what attendance looks like when it's built for the way transport actually operates, and what changes when the route, the driver and the payroll all reference the same record.
The depot is not the whole company
The classic mistake is to put one clock-in device at the depot and treat that as the attendance system. It works for the depot crew. It fails for everyone who never spends their day at the depot, which is most of the workforce.
The fix is two flows that produce one record. Depot staff clock in at the depot, often on a shared tablet. Drivers and conductors clock in from their personal phones, wherever the route begins. The system reconciles both into one set of timesheets, so payroll doesn't have to.
Route accountability without a tracking device per vehicle
Telematics is great. It is also expensive, hardware-heavy, and slow to roll out across an existing fleet. For most Ghanaian transport operators, the real win comes from much simpler attendance evidence: the driver clocked in at the depot at 5:42am, clocked in again at the Kumasi terminal at 11:18am, and clocked out at 6:04pm.
That is a route, traced by attendance, with no telematics needed. It will not give you live vehicle position, but it will give you something more useful for payroll and disputes: a defensible record of who was working, on which route, for how long.
- Route can be linked to a shift, optional
- Intermediate check-ins for multi-leg routes
- Vehicle assignment recorded alongside the driver
- Per-route hours and labour cost available in reports
Long-haul, overnight and statutory rest
Cross-day shifts are common. A driver leaving Tema at 10pm and arriving in Bolgatanga at 9am has worked an 11-hour shift that crosses midnight. Naive systems either split this into two days or compute the hours wrong. Both end in disputes.
Kuwa records the shift as a single event, computes the hours correctly, and applies your overnight and long-haul allowance rules automatically. Statutory rest periods can be enforced so a driver who hasn't had eight hours off can't be scheduled to drive again.
Driver payroll built on facts, not phone calls
The single biggest source of friction in transport payroll is the driver's hours. The driver says they worked 11 hours. The depot has them down for 9. Without a verified record, the conversation becomes a negotiation, every month, with every driver.
When clock-in is verified at the start of the route and clock-out is verified at the end, the negotiation ends. Either the times are there or they're not. Either the route was completed or it wasn't. Drivers get paid correctly. The depot stops carrying disputes. The owner stops being the final court of appeal for everybody's timesheet.
Six shapes of Ghanaian transport operator
Each has its own attendance shape. The same system handles all of them.
Inter-city passenger transport
Daily routes between Accra and Kumasi. Drivers and conductors clock in at the terminal. Per-route hours feed payroll and per-route labour cost.
Last-mile delivery in Greater Accra
Dozens of riders, sites all over the city. Each delivery has a clock-in at pickup and clock-out at handover. Hours and deliveries reconcile against each other.
Cross-border haulage to Burkina
Multi-day trips. Cross-day shifts handled cleanly. Statutory rest periods enforced. Per-haul payroll roll-up.
Logistics company with central warehouse
Warehouse staff at the depot, drivers on the road. Two clock-in flows, one payroll.
Tro-tro union with shared vehicles
Drivers and mates share vehicles by shift. Vehicle assignment tracked. Shift handover recorded automatically.
Tanker fleet operator
Specialist drivers, certified routes, regulatory hours. Compliance reports for the regulator built from the same attendance data.
What Kuwa puts in place for a transport operator
Kuwa is built for a workforce that is rarely all in one place. Drivers clock in from their phones. Depot staff clock in at the depot. Conductors clock in with the driver. Long-haul shifts handle themselves. Per-route and per-vehicle reporting comes out of the same data that drives payroll.
The end-state is an operation where the depot stops chasing drivers for their hours, the office stops reconstructing routes from phone calls, and the payroll closes on time without anybody arguing about it.
- Mobile clock-in for drivers and conductors, depot clock-in for warehouse and admin
- Shifts linked to routes, vehicles, and routes-and-vehicles together
- Long-haul, overnight and cross-day shift handling
- Statutory rest period enforcement
- Per-route and per-vehicle labour cost reports
- MoMo-ready payroll export in GH₵, allowances included
Browse the full feature list or check pricing in GH₵.
Ready to stop guessing and start managing your workforce properly?
Frequently asked questions
How does it work for drivers who don't return to the depot daily?+
The driver clocks in from their phone at the start of the route, not from a fixed device at the depot. Their location at clock-in is recorded. They clock out when the route is complete. The depot never has to physically see them for the day to be counted.
Can we separate depot staff and on-route staff?+
Yes. Depot crew clock in at the depot (often via a shared tablet). Drivers and conductors clock in from their own phones. The two flows produce one unified attendance record for payroll.
What about long-haul drivers on multi-day trips?+
Long-haul shifts can span multiple days with intermediate rest stops recorded. Statutory rest periods can be enforced. The payroll roll-up handles overnight and cross-day shifts correctly.
Can we tie attendance to specific routes or vehicles?+
Yes. A driver's shift can be linked to a route, a vehicle, or both. This makes per-route labour cost and per-vehicle attendance available for operations, not just for payroll.
How does it handle conductors, mates and casual loaders?+
Each role is configurable. Conductors and mates often share a vehicle with a driver and clock in together. Casual loaders at the depot can be added for the day and roll off cleanly. None of these need separate systems.
Does it work when a driver loses signal en route?+
Yes. Clock-in events are timestamped on the phone and synced when signal returns. The recorded time is the actual clock-in moment, not the moment the data finally uploaded.
More answers in the full Kuwa FAQ or contact the team.
Pay drivers for the hours they actually drove
Transport payroll gets cleaner the moment clock-in stops being a phone call. Start the free trial, get your drivers and depot staff onto one system this week, and feel the difference at the next pay cycle.