Coaching from Netradyne and Mentor events

What Mentor and Netradyne each measure

They measure different things in different ways, which is why a driver can look fine on one and poor on the other.

Read both vendors' pages yourself; they are linked below. Your Amazon program may configure either system in ways their public pages don't describe.

How safety events reach the scorecard

The weekly scorecard's safety columns reflect what these systems recorded during the week, usually as rates per driver rather than raw counts. The legend on your scorecard says which column comes from which system and how each rate is worked out, and it is the definition that counts when you talk to a driver.

Events arrive daily and the scorecard weekly. If you only look at the scorecard, you are coaching a week late on events the driver has half forgotten. Looking at each day's events, even briefly, lets you talk while the route is still fresh.

A weekly coaching routine that fits a station's mornings

Mornings at a station are for getting vans out. Coaching squeezed in before a wave is rushed and usually lands badly. One routine that fits:

1. Each afternoon, someone reviews the day's events for 15 minutes and marks the ones worth a conversation: a seatbelt event, a pattern of hard braking, anything that looks wrong.
2. Conversations happen when drivers return to the station, not before they leave. Keep them short: what the data showed, what the driver says happened, one thing to do differently.
3. When the weekly scorecard arrives, compare it with what you already talked about. Anyone who crosses your written coaching rules and hasn't been spoken to gets a conversation that week.
4. Every Friday, check last week's follow-ups. Did the habit change? Write down what you saw either way.

Recording coaching so it's consistent and fair

Decide your coaching rules before you look at who broke them, and write them down: for example, any seatbelt-off event, or a following distance rate above a level you set. Apply them to everyone. If you skip someone, write down the reason. Two drivers with the same events and different treatment is hard to explain to the crew, and harder to explain later if one of them disputes it.

Write a note for every conversation: the date, what the data showed, what the driver said, what you agreed and when you will check in. Keep coaching apart from discipline. A coaching note isn't a warning, and escalating to a write-up should be a separate, deliberate step with its own record.

When an event looks wrong

Devices make mistakes, and drivers know their routes. When a driver says an event didn't happen the way the system says, take it seriously.

• Ask for the driver's account in their own words and write it down with the date.
• Look at whatever evidence you can: the event's time and location, the route, any video your access allows.
• Use the vendor's own review process where one exists. Neither vendor's public pages we checked describe how their review or appeal process works for DSPs, so ask your Netradyne or eDriving contact, or your Amazon contact, how it works for your account.
• Keep your notes whatever the outcome. If an event is later removed, the coaching record should show that too.

Don't hold an event against a driver in a write-up while it is under review. Coach on the habit if there is one, and wait for the answer on the event.

How SXT Ops handles this today

On the Station plan ($399 per station per month), SXT Ops imports the weekly scorecard and lists people whose standing or metrics cross the coaching rules you set. The default rules are placeholders, not Amazon's tiers. Nothing is created until a person chooses Create coaching item, and each item holds the date you talked, what was said and a follow-up date. Coaching stays separate from write-ups, and drivers don't see coaching items in the driver app.

More on scorecards and coaching, the scorecard metrics guide, or bring one station to the pilot.