Delivery driver scheduling for DSP operators.Plan shifts. Cover routes. Stay compliant.

Rota planning, and where the spreadsheet gives up

Most DSPs start with a spreadsheet, and the spreadsheet is fine until the operation has a second station or a driver who only works Tuesdays and Thursdays. What breaks is not the grid. It is that the grid is accurate on the afternoon someone builds it and wrong by Tuesday morning, and nobody knows which version the drivers are looking at.

The cost shows up in the same three places every time. A route with nobody on it, found on the morning rather than on the Thursday before. A driver who turns up for a shift that was moved on a copy they never saw. And a manager spending the back half of every afternoon on something that is, at heart, arithmetic.

Driver scheduling software earns its place by taking the checking off the person. Building the rota was never the slow part — verifying by eye that every route has someone on it, that nobody has been handed seven days, and that the one driver who cannot do nights has not been given a night, is the slow part.

Next week's rota starts from last week's

Delivery rotas repeat. The same drivers, largely the same days, with the exceptions that make the week interesting — a holiday, a van in the garage, the extra routes the station asked for on Friday. Starting from an empty grid every week is re-typing a decision you already made.

So the week opens as a copy of the last one, and what you spend time on is the difference. Coverage is counted per day as you go, which is the number that actually matters: nine drivers on for eleven routes is a problem you want to meet on Thursday, with options, rather than at 05:40 on Monday with none.

Shifts are morning, afternoon or night, with the hours against them, so the weekly total per driver is visible while you are building rather than after payroll has run. For an Amazon DSP operation that total is not an HR detail — it is the difference between a driver who is available on Saturday and one who is not.

No-shows, swaps and the 05:40 phone call

Every operator has the same morning. A driver is not coming, the routes were allocated last night, and there is about forty minutes to fix it before the station notices. What makes that solvable is not a clever algorithm — it is knowing, without ringing round, who is off today and could be asked, and who is already close to hours you would rather not push.

Swaps between drivers are the quieter version of the same problem. Two drivers agree something in a WhatsApp group at the weekend, the rota never hears about it, and on Wednesday the depot is one short for a reason nobody can reconstruct. A swap recorded against the rota is a swap the person planning Wednesday can actually see.

A van off the road creates the same gap from the other direction, which is why the rota and the fleet records belong in one place: a service booked for Tuesday is a route to re-cover on Tuesday.

A rota nobody has read is not a rota

Publishing is where most scheduling tools stop and where the operational problem starts. A rota pinned to a noticeboard, or posted as an image into a group chat, reaches the people who happen to look. The ones who do not look are the ones you hear about on the morning.

WaveGo sends each driver their own shifts on WhatsApp, in their own language, with a tap to confirm. That matters more in this industry than in most: delivery workforces turn over, and a good share of drivers are not reading English as a first language. Asking someone to install an app, make an account and remember a password, in order to find out what time they start, is a step that quietly does not happen.

The confirmations are the part worth having. A published rota is a plan; a confirmed rota is a forecast. The gap between the two is precisely where a missed route comes from, and it is visible the evening before instead of the morning after.

Hours worked, and what they feed

The rota is also the timesheet, which removes the weekly conversation about whether someone did five days or six. Both sides are looking at the same record of the week, written as the week happened rather than remembered afterwards.

Hours roll up per driver and feed payroll through Sage, Xero and HMRC-ready output. Running a DSP in the UK covers the rest of that ground — Right to Work, DBS, DVLA licence checks — and pricing is five free seats and £10 per seat after that, counted per active user rather than per van.

Questions operators ask about rotas

Is this rota software or scheduling software?

The same thing, under the two names British operators use. A depot in the UK builds a rota; the software category is called driver scheduling. WaveGo does rota planning for delivery drivers: who works which shift, which routes are covered, and who is left over for the morning something goes wrong.

How long does next week's rota take to build?

Minutes, because you start from last week rather than from an empty grid. The part that used to take the afternoon was not the typing — it was checking, by eye, that every route had someone on it and that nobody had been given seven days.

What happens when a driver does not turn up?

You need two things at 05:40 and the rota has both: who is off today and can be asked, and who is already at the hours you do not want to push. Once the replacement is in, the change goes out on WhatsApp to the people it affects rather than to everyone.

Can drivers see their own rota?

Yes, on WhatsApp, in their own language, with a single tap to confirm. There is no app to install and no password to reset at four in the morning, which matters for a workforce that turns over.

Do drivers have to confirm their shifts?

They can, and the confirmation is the useful part. A rota that has been published is a plan; a rota that has been confirmed is a forecast. The gap between the two is where a missed route comes from.

Does the rota feed payroll?

Hours worked roll up from the same rota the week was run on, and feed payroll through Sage, Xero and HMRC-ready output. That also settles the weekly argument about whether someone did five days or six, because both sides are looking at the same record.

What does it cost?

Five seats are free, permanently, then £10 per seat per month. A seat is any active user, whatever their role — not a van, and not a route.