1 June 2026·5 min read

How to onboard new drivers at an Amazon DSP

Onboarding a new driver at an Amazon DSP is never just a paperwork exercise. You are bringing someone into a role where a single missed compliance check can cost you a corrective action, and where a poorly trained first week often turns into a problem driver for months. Most DSP owners get this right eventually — but by trial and error, not by design. This guide lays out a repeatable process so that every new hire arrives at their first wave ready to perform and fully compliant.

Before the first shift: the compliance paperwork that cannot wait

Amazon requires every DA to be cleared through its own background check process before they can deliver. That process takes time, and you cannot control the timeline — but you can make sure everything on your side is sorted before the check comes back, not after.

The minimum you need in place before a new driver's first shift:

Right-to-work verification. You are legally required to check and retain a copy of the documents that prove your driver has the right to work in the UK. This is not optional and does not have a grace period. Do it before they start, not on their first day while they are standing in front of you.
Driving licence check. Check the DVLA record, not just the physical licence. You need to confirm the correct vehicle category (usually B for a standard van), verify there are no disqualifying endorsements, and note the expiry date so you can set a reminder to re-check. Photocopying a licence does not tell you its status.
Insurance notification. Add the new driver to your fleet insurance schedule. If a driver has an accident before they are added, your cover may not apply.
Emergency contact and employment contract. Basic, but often processed in the rush of a busy hiring period. Both need to be signed and filed before the first day.

Set up a standard checklist that your dispatcher or OSM works through for every hire, without exception. If even one item is skipped under pressure, you will eventually face the consequence.

What Amazon checks at station — and what you should prepare for

Your new DA will go through Amazon's own station induction. What that covers varies slightly by station, but you should assume it will include: the Rabbit device setup, the Mentor app, the delivery app walkthrough, and a van safety briefing. Your job is not to duplicate what Amazon covers — it is to brief your driver on everything Amazon does not cover about working for your DSP specifically.

That briefing should cover your expectations on:

Photo on Delivery (POD) compliance. New drivers often understand they need to take photos but do not understand the consequence of missing them. Walk through the POD requirement explicitly and show them what a compliant photo looks like.
Van inspection before every shift. Explain that a daily check-sheet is not a formality — it is how you document pre-existing damage and keep your fleet insurance clean. Make clear that missed inspections have consequences.
What to do when a delivery cannot complete. Many DNR claims and Contact Compliance misses come from drivers who did not know the right procedure for an undeliverable stop. Cover Contact Compliance and how to log exceptions clearly.
Shift start time and what late arrival means for the wave. New drivers often do not realise that being 20 minutes late at the station ripples through to over-stopped routes and incomplete waves.

Setting new drivers up in your systems

Before a new driver's first shift, they need to exist in every system your operation runs through — not just Amazon's. That means:

Adding them to your rota software so they can be scheduled and can see their shifts in advance.
Creating their profile in your performance tracking tool so you can start monitoring their metrics from day one rather than scrambling for data after their first week.
Storing their right-to-work documents, licence details, and licence expiry date in a searchable place — not a filing cabinet and not a folder on someone's laptop.
Setting up a licence re-check reminder. Licence expiry typically comes around 10 years after issue. That is far enough away to feel irrelevant at onboarding, which is exactly why it gets missed.

The first two weeks: building the habits that stick

The first two weeks are when a new driver's habits are formed. The drivers who become consistent performers are almost always the ones who received consistent feedback in their first fortnight — not a one-off induction and then silence until something went wrong.

A simple structure that works:

End of day 1: a brief check-in on how the wave went, any confusion about procedures, any equipment issues. Takes five minutes and catches the problems that will become habits if left unaddressed.
End of week 1: share their actual scorecard metrics with them — POD rate, completion rate, any DNR flags. Make sure they know how to read the numbers and what they mean for their role. Drivers who see their own data early take ownership of it.
End of week 2: a proper one-to-one. What is going well, what needs work, any route or scheduling adjustments needed. By this point you have two weeks of data to work from rather than an impression.

The DSPs with the lowest driver turnover are the ones where new starters feel visible and supported from the beginning. That is not about being soft on performance — it is about being clear about expectations and consistent about feedback.

Where DSPOps fits in

DSPOps centralises the compliance and performance side of driver onboarding. Right-to-work status, licence details, and expiry reminders are stored per driver and surfaced automatically when they are coming due — so nothing gets missed because someone forgot to check a spreadsheet. New drivers appear in the performance dashboard from their first shift, so your OSM can monitor their metrics and run the week-one review with actual numbers rather than impressions.

If you want to see how the onboarding and compliance workflows work inside DSPOps, you can book a 20-minute demo — we will walk through your specific setup and show you what it looks like for your fleet.