Skip to main content

Scorecards

The weekly Amazon scorecard in the manager app — how it gets in, what the week list and driver detail show, and how to text scorecards to drivers.

A scorecard is the weekly performance report Amazon publishes for your station — a team standing for the week plus a row of numbers for every driver who delivered. VoiceERP keeps every week's scorecard in one place, breaks it out per driver, and lets you send each driver their own numbers. Open it from Performance → Scorecards in the left sidebar.

Getting each week's scorecard in

There are two ways a scorecard lands in the app. If automatic scorecard sync is turned on for your company, a banner at the top of the page tells you so — the app periodically pulls your most recent scorecard for you, and you don't have to do anything. Otherwise you upload it yourself, one week at a time.

The alerts above the list tell you where you stand. When nothing is outstanding you'll see "Your scorecards are up to date." Once last week's scorecard is due, an alert asks you to upload it as soon as Amazon has published it. Past-due weeks are listed under "We're missing your scorecards for the following week(s)," and weeks whose file couldn't be read get their own alert saying they need to be reuploaded.

To upload, find the week's row and press the upload icon under Scorecard PDF — or drag the PDF straight onto that button. It accepts PDF only, and it accepts the real scorecard, not the preview file Amazon publishes earlier in the week: drop a preview and you'll get a "Whoops! Scorecard Preview Detected" dialog. The app also checks the week number in the file name against the row you dropped it on and stops you with "Whoops! Week Mismatch Detected" if they disagree, which is the single most common upload mistake.

After a successful upload you'll see "Scorecard uploaded. Feel free to move away from this page while it processes." The icon becomes a spinner while the file is read, then a green check when it's done. A red error icon means processing failed and the file needs to be uploaded again.

The week list

Each week is a card showing Week N, the week's date range, and the team's overall standing for that week — Fantastic Plus, Fantastic, Great, Fair, or Poor. The Start Date and End Date pickers at the top control which weeks you see; they only allow whole Amazon weeks, and they open on roughly the last ten weeks. That range is your week-over-week view of the station: scroll the list, newest first, and read the standing down the left of every card.

The same row also holds your other weekly files — CDF DPMO CSV, DVIC Report, and an ADP Timecard or Paycom Timecard section depending on your payroll provider. Those uploads stay locked until that week's scorecard has finished processing, because they're matched against the drivers the scorecard named. Replacing a CDF DPMO file later warns you that it may change payouts on your incentives.

A week's driver detail

Once a week's scorecard has processed, its card becomes clickable and opens the detail page for that week. Across the top are the team standings pulled straight from the scorecard: Overall Standing, Safety & Compliance, Quality, Pickup Quality (only when the week's scorecard includes it), and Team.

Below that is the per-driver table. The Driver column stays pinned as you scroll sideways through Score, Delivered, Key Focus Area, FICO Score, the on-road rates (Seat Belt Off Rate, Speeding Event Rate, Distractions Rate, Following Distance Rate, Sign/Signal Violations Rate), and the delivery quality columns — CDF DPMO, CED, DC DPMO, DSB, POD, SWC-CC, SWC-AD, DSB DNR, POD Opps., CC Opps., and PSB. Score is that driver's tier for the week in the same Fantastic-to-Poor wording as the team standing. Columns Amazon didn't include that week are simply left out, and where Amazon reports a rate instead of a defect rate you'll see CDF and DCR in place of CDF DPMO and DC DPMO.

Sending scorecards to drivers

Pinned to the right of the table are the two things you'll actually do with a scorecard. Driver App Usage shows two counters per driver — how many times they've been texted their scorecard for that week, and how many times they've opened it — so you can tell who has genuinely seen their numbers.

Actions has a message icon that texts one driver their scorecard, with a tooltip explaining why it's unavailable when it is (no phone number on file, not yet verified, or not active). When a driver has no number, an add-phone-number icon appears next to it so you can fix that without leaving the page. Above the table, Text All Drivers Their Scorecard does the whole roster at once: a dialog lists the eligible drivers — active, verified, and with a phone number — and lets you trim the list before confirming. The text greets the driver by name and links them to that week's scorecard in the driver app; the first one they ever receive also tells them they can reply in the thread.

Where scorecard numbers go next

Scorecard metrics feed the Overall Score on the Driver Performance page, where you choose which metrics are weighted into each driver's ranking. They also feed incentives, which score drivers against scorecard metrics for the weeks a program covers — so a late scorecard upload holds up both.

Did this answer your question?