All articles
·5 min read

How to reduce Mentor safety events at an Amazon DSP

Mentor safety scores sit quietly next to your Cortex numbers until the week they don't. A cluster of speeding events, a hard-braking spike, or two seatbelt violations in the same wave and suddenly your Safety score is dragging your overall status down — and the DSP down the road is winning routes you used to run.

The good news is that safety events are the most fixable thing on your scorecard. They are behaviours, not skills. Once you show drivers what they did, on which street, at what speed, the numbers move within two weeks. Here is how UK DSP owners we work with actually do it.

What Mentor is actually measuring

Amazon's FICO Safe Driving Score inside the Mentor app blends five behaviours into a single 0–850 score per driver, rolled up into your DSP-level Safety metric on Cortex:

  • Speeding — sustained travel above the posted limit. On UK routes this is almost always the biggest single drag on the score.
  • Harsh braking — deceleration events above Amazon's threshold, usually from tailgating or last-second junction decisions.
  • Harsh acceleration — quick throttle inputs, often from drivers rushing between stops on a tight route.
  • Cornering — lateral G-force events, typically on roundabouts and tight residential turns.
  • Distracted driving — phone handling detected while the van is moving. The single highest-weighted event in the score.

Backup events, seatbelt use, and Sign & Safety violations sit alongside these as separate compliance items — they don't feed the FICO score directly but they do hit your overall Safety status on the DSP scorecard.

Why safety scores drift, even with experienced drivers

The pattern we see is almost universal. A DSP hits Fantastic on safety for a stretch, then a peak wave comes in, routes get longer, one or two drivers start pushing to finish on time — and by Friday the cohort average has dropped ten points. Nobody drove dangerously on purpose. They ran out of buffer.

The other silent driver is unaddressed repeat behaviour. Most DSPs review safety weekly, in a group setting, using cohort averages. Individual drivers with genuinely problematic scores get lost in the average and never see a specific piece of feedback about a specific event.

Speeding — the fastest metric to fix

Speeding events cluster around three things: dual carriageways between drops, downhill sections on residential routes, and drivers running late trying to make the last hour. All three are visible in the event log with street name and speed attached.

  • Pull the last 14 days of speeding events, sort by driver, and identify the top two. In almost every DSP those two names account for 40–60% of all events.
  • Show each driver their own top three streets and the recorded speed against the limit. Specifics move behaviour; generic "please slow down" briefings do not.
  • For drivers running late as the cause, the fix is upstream — an OSM call an hour before wave close to rebalance stops rather than letting the driver push their speed to finish.

Harsh braking and acceleration — coach the anticipation, not the pedal

Harsh braking is a following-distance problem 90% of the time. A driver too close to the vehicle in front has to react rather than anticipate. Show the driver the timestamp and the road, and the conversation writes itself.

Harsh acceleration usually pairs with speeding — the same driver rushing between stops on a route with tight interval times. The two metrics almost always move together, so fixing one lifts both.

Distracted driving — non-negotiable, coach on day one

Distracted driving events are the highest-weighted item in the FICO score and the biggest liability exposure your DSP carries. A single sustained event can drop a driver's individual score by 30–50 points, and repeated events on the same driver are grounds for removal from route.

Two operational habits move this metric:

  • A phone-mount policy that is checked at the van walkaround. The van does not leave the station without the driver's phone in the mount.
  • Any distracted event triggers a same-day conversation. Not a Monday briefing item — a same-day one. Drivers who see the event flagged immediately treat it as serious; drivers who see it three days later treat it as noise.

Backup events and seatbelt violations — the two compliance items DSPs miss

These don't feed FICO but they do feed your DSP-level Safety metric and, more importantly, they surface in Amazon audits. Backup events happen when a driver reverses in a way that triggers the camera — usually reversing off a driveway they should have turned around on. Seatbelt violations happen in the first 30 seconds after the driver hops back in the van at a stop and pulls off without buckling up.

Both are addressable with two lines in the morning briefing: "no reverse-off driveways today" and "belt on before the handbrake comes off." Repetition is what makes them stick.

The two-week feedback rhythm that actually moves the score

DSPs that hold Fantastic on Safety run the same loop:

  • Daily: a two-minute glance at yesterday's Mentor events, sorted by driver. Any driver with a distracted event or three-plus speeding events gets a same-day conversation.
  • Weekly: a one-on-one with the two lowest-scoring drivers, showing them their own events with street names and timestamps.
  • Every fortnight: a leaderboard shared with the whole fleet showing the top five and bottom five FICO scores. Drivers who care about being top of the leaderboard self-correct without a meeting.

The thing that kills this rhythm is data access. If your OSM has to log into Mentor separately for each driver, the loop dies inside a week.

Where DSPOps fits in

DSPOps pulls every driver's Mentor and Cortex data into one dashboard, sorted by driver and by event type. Your OSM opens it, sees the two drivers with distracted-driving events yesterday, and books the five-minute conversation before the next wave. Drivers see their own FICO score and event history inside the driver portal, and the top-of-leaderboard drivers self-correct.

If you want to see what your DSP's safety data looks like inside DSPOps, you can book a 20-minute demo — we'll set up your data live during the call.

Book a demo

Twenty minutes.
Your depot on the screen.

Not a canned walkthrough — we import your drivers, your rota and your Cortex data on the call, so what you're looking at is your own operation. You'd be talking to the person who built it, not a sales team.

Built by a former on-site managerIndependent · UK-built · not affiliated with Amazon

DSPOps was written on the depot floor by someone who ran an Amazon delivery partner's operation day to day — which is why it looks like the job rather than like software.

Book a 20-minute demo

See your DSP live on DSPOps

We'll import your drivers, rota and Cortex data on the call, so you're looking at your own operation — not a canned demo.

No credit card · 14-day free trial · GDPR compliant