Weplanifyweplanify
30-day free trial

Transport · Logistics · Delivery

Your drivers are everywhere except the office. Time tracking follows them.

A run starts at five in the morning in a car park and ends somewhere else. Span is not time worked, and a route’s cost is not the sum of the salaries.

A warehouse worker in a safety vest adjusting her hard hat.

Today’s schedule

05:00 → 13:00

Morning round

Clock-in recorded

04:57

Geolocation · warehouse

05:00

The departure time nobody witnesses

span ≠ hours

Two different figures, on the same payslip

per route

Real cost, drivers and handling included

Built forFreight transportUrban deliveryLogistics & warehousingStaff transport

What is stuck today

Drivers slip through every tool you have

The unwitnessed departure

The driver says they left at five. No system confirms it.

Span mistaken for work

Twelve hours of span are not twelve hours worked. Yet that is often what gets paid.

Cost per route unknown

You know fuel and tolls. Not labour per run.

The run schedule

Who drives, when, on which route

A run is a shift like any other: assigned, clocked, compared. A 4:30 departure with no driver shows up the day before.

09:41
WeplanifySC
‹›
Runs for the week of 6 Julypublished4 routes · 18 driversPublish
EmployeeMon 6Tue 7Wed 8Thu 9Fri 10Sat 11Sun 12
O. DialloHGV driver · 53 h
05:00Dakar–Thiès
05:00Dakar–Thiès
05:00Dakar–Thiès
05:00Dakar–Thiès
05:00Dakar–Thiès
M. GueyeHGV driver · 46 h
05:30Dakar–Mbour
05:30Dakar–Mbour
Statutory rest
05:30Dakar–Mbour
05:30Dakar–Mbour
A. CisséUrban delivery · 44 h
04:30North Urban
04:30North Urban
04:30North Urban
04:30North Urban
Uncovered
I. FallHGV driver · 50 h
04:45Dakar–Kaolack
04:45Dakar–Kaolack
04:45Dakar–Kaolack
04:45Dakar–Kaolack
04:45Covers A. Cissé
1 alertFriday 10, urban run: no driver assigned to the 4:30 departure. The truck does not leave, and nobody knows before 6.

The runs

Who drives, when, on which route

A run is a shift like any other: assigned, clocked, compared. Clocking in happens on mobile, wherever the driver is.

09:41
WeplanifySC
Runs, 9 JulyDemonstration data
DriverRouteDepartureState
O. DialloDakar–Thiès05:04clocked
M. GueyeDakar–Mbour05:4848 min late
A. CisséNorth Urban–absent
I. FallDakar–Kaolack04:58clocked

A missed departure clock-in shows within the hour, not at the end of the run.

09:41
WeplanifySC
Span and hoursDemonstration data
DriverSpanWorkedBreak
O. Diallo13 h 2010 h 402 h 40
M. Gueye11 h 059 h 151 h 50
I. Fall14 h 1011 h 003 h 10
Average12 h 4510 h 182 h 33

Span and time worked are two separate columns: payroll applies your agreement’s rule, not an approximation.

Payroll and cost per route

What a run actually costs

Clocked hours become payroll; salaries charged to the route become its labour cost.

09:41
WeplanifySC
July payrollDemonstration data
DriverDaysOvertimeNet
O. Diallo26 / 3048 h264 500
M. Gueye24 / 3022 h221 300
I. Fall25 / 3061 h278 900
Net payroll3 946 800

Salary advances, common in this sector, deduct themselves until cleared.

09:41
WeplanifySC
Labour cost per routeDemonstration data
RouteRunsHoursReal cost
Dakar–Thiès48512884 000
Dakar–Mbour36398702 500
North Urban626041 118 000
Total1461 5142 704 500

To match against your revenue per route: the urban run is the most expensive in labour.

Getting started

One route, two weeks

01

Week 1: your routes and runs

Routes, rotations, span and break rules.

02

Week 2: drivers clock in

Mobile clock-in at departure and arrival, wherever they are.

03

Month end: payroll

Actual hours and span kept separate, according to your agreement.

04

Then: cost per route

Labour next to fuel, finally in the same table.

« I was billing my routes without knowing their labour cost. That was the black hole. »

Manager of a transport company (anonymised testimonial)

Take the route that looks the most profitable.

We set up its runs and show you its real labour cost.

Demo on WhatsApp30-day free trialNo card required · onboarding included