Skip to main content

How to Move Your Amazon DSP Scorecard from Great to Fantastic+

A systematic approach to DSP scorecard improvement through daily KPI tracking, structured coaching, dispatch discipline, and pattern elimination.

Back to Blog
Scorecard & StandardsPublished Apr 6, 202513 min read

How to Move Your Amazon DSP Scorecard from Great to Fantastic+

Moving from Great to Fantastic+ takes more than a short-term performance push. It requires consistent scorecard review, real-time visibility, evidence-based coaching, and operational processes that managers can sustain.

Every Amazon DSP owner has seen the pattern. The operation performs well for several weeks, reaches Fantastic+, and then a small number of difficult days brings the rating back down.

This often happens because scorecard improvement is treated as a reaction to declining results rather than a consistent operating process.

Moving from Great to Fantastic+ is not simply about asking drivers and managers to work harder. It requires systems that help teams identify problems earlier, understand what may be contributing to them, document the response, and follow up consistently.

This guide explains the operational disciplines that can help Amazon DSPs improve scorecard performance and sustain stronger results over time.

Key takeaways

  • Moving up takes consistent review, real-time visibility, evidence-based coaching and repeatable processes, not a short-term push.
  • Review the previous day's exceptions before dispatch and reconcile the day's results, rather than waiting for the weekly scorecard.
  • Separate individual issues from systemic ones: a driver-level result can be a symptom of dispatch, scheduling or load-out.
  • Coach from the specific evidence, ask for the driver's perspective, set a clear expectation and document the conversation.
  • Dispatch, scheduling, load-out, attendance, fleet readiness and rescue coordination all shape scorecard results.

Understanding What the Scorecard Measures

The Amazon DSP scorecard is a composite assessment made up of weighted categories. Each category reflects a different part of the DSP's operation, and performance within each category contributes to the overall rating.

Safety and Compliance

Safety and compliance measures include telematics events such as hard braking, speeding, distracted driving, and seatbelt compliance.

These measures help DSPs identify driving behaviors that may require review, coaching, or additional attention. A recurring pattern from one driver can affect broader fleet performance, but every event should still be reviewed in context before conclusions are made.

Delivery Quality

Delivery quality includes measures such as photo-on-delivery compliance, delivery accuracy, and concessions.

Missed photos, incorrect delivery locations, packages marked as delivered but not received, and other delivery exceptions can reduce performance in this category. Reviewing the supporting records helps managers identify the specific behaviors or operating conditions that may be contributing to the result.

Customer Experience

Customer experience includes delivery success, customer-reported issues, and feedback measures.

This category reflects whether customers receive their packages according to Amazon's delivery expectations. Patterns in customer feedback can help managers identify where additional coaching, process review, or route-specific investigation may be needed.

Reliability and Capacity

Reliability and capacity reflect the DSP's ability to staff routes, respond to volume changes, and maintain consistent delivery execution.

Callouts, uncovered routes, returned packages, and other operational disruptions may affect this area. Reviewing attendance, scheduling, rescue activity, and route-completion information together can provide a clearer picture than reviewing any one data source in isolation.

Because Amazon may update scorecard definitions, thresholds, category weighting, and reporting requirements, DSPs should continue referring to the latest official Amazon materials.

Why Short-Term Scorecard Pushes Fail

Many DSPs respond aggressively when a scorecard rating declines. Managers increase coaching, review more footage, monitor routes more closely, and reinforce expectations during dispatch.

These efforts may produce improvement, but the results are often temporary. Once the scorecard begins to recover, the additional attention fades and the same problems return.

Sustainable scorecard improvement requires a repeatable process that continues regardless of the current rating. That process should connect:

  • Weekly scorecard results
  • Driver-level performance information
  • Real-time telematics events
  • Attendance and callout records
  • Route-completion and rescue activity
  • Coaching documentation
  • Follow-up records

The purpose is not to react to every data point. It is to give managers enough organized information to identify what requires attention and decide how to respond.

Build a Consistent Scorecard Review Rhythm

A weekly scorecard is important, but it should not be the first time managers learn about an operational issue. A structured review rhythm helps DSPs identify exceptions earlier and connect them to the weekly result.

Review Previous-Day Exceptions Before Dispatch

Before routes launch, managers should review the most important exceptions from the previous delivery day.

This may include:

  • High-priority safety events
  • Returned packages
  • Delivery-quality exceptions
  • Attendance issues
  • Callouts
  • Rescues
  • Customer escalations
  • Incomplete coaching follow-ups

The review does not need to become a lengthy meeting. Its purpose is to identify which items require immediate attention, which should be included in a coaching conversation, and which need additional investigation.

Use Real-Time Monitoring During Delivery Windows

Waiting until the following day to discover a significant safety event or route problem limits the DSP's ability to respond during the active delivery window.

LMDmax Driver Management Support includes real-time telematics monitoring as a standard platform capability. It surfaces safety events and driver-performance information so authorized DSP managers can review what happened and determine whether a response is needed.

Real-time visibility does not mean reacting to every alert in the same way. The appropriate response depends on the type of event, its severity, the available context, the driver's history, and the DSP's policies.

LMDmax surfaces the information and facilitates client-approved communication. The DSP's authorized managers decide whether coaching or another action is appropriate.

Reconcile the Day's Results

At the end of the delivery day, compare what happened with what was planned.

Review questions may include:

  • Were all assigned routes completed?
  • Were any packages returned?
  • Which routes required rescues?
  • Did any vehicle issues affect delivery execution?
  • Were there callouts or attendance problems?
  • Did any safety or delivery-quality events require follow-up?
  • Were time and attendance records completed correctly?

This daily reconciliation creates the supporting record needed to understand weekly scorecard results.

Conduct a Structured Weekly Review

When the weekly scorecard becomes available, review it alongside the operational records collected throughout the week.

Start by confirming that the correct scorecard and reporting period are being reviewed. Then identify:

  • Categories that improved or declined
  • Recurring driver-level exceptions
  • Changes from the previous reporting period
  • Patterns involving particular routes or operating conditions
  • Open coaching items that require follow-up
  • Areas where additional information is needed

The weekly review should produce a clear list of items for the DSP's management team to evaluate. It should not become a general discussion without assigned follow-up.

Separate Individual Issues From Systemic Problems

When a scorecard measure declines, the easiest response is to identify the driver associated with the event. Sometimes the issue is specific to that driver. In other cases, the driver-level result may be a symptom of a broader operational problem.

Indicators of an Individual Issue

An individual issue may be present when:

  • One driver repeatedly generates similar telematics events
  • One driver has recurring delivery-quality exceptions while others on comparable routes do not
  • A documented expectation has been communicated but the same issue continues
  • The pattern appears across multiple routes or operating conditions

These are reasons for the DSP's manager to review the information and determine whether coaching or another client-directed response is appropriate.

Indicators of a Systemic Issue

A systemic issue may be present when:

  • Multiple drivers struggle on the same route
  • Safety events increase under similar route or weather conditions
  • Returned packages rise when route volume reaches a certain level
  • Delivery problems occur after repeated load-out or scheduling disruptions
  • Rescue activity consistently affects the same routes or operating periods

These patterns may point to scheduling, route assignment, vehicle availability, load-out, staffing, or another operational process.

Data can surface the pattern, but it does not establish the cause automatically. Managers should review the surrounding circumstances before deciding what needs to change.

Use Evidence-Based, Manager-Led Coaching

Coaching connects performance information to the behaviors and expectations managed by the DSP. It is most effective when it is specific, timely, consistent, and documented.

Start With the Available Evidence

Begin with the specific event, metric, footage, or record that prompted the conversation. Avoid broad statements such as "your driving has been poor" or "you need to improve your score."

A more focused conversation identifies what was observed and gives the driver an opportunity to provide context.

Ask for the Driver's Perspective

Performance data does not always explain why an event occurred. Asking the driver what happened may reveal route conditions, traffic, vehicle problems, delivery obstacles, or other relevant circumstances.

The driver's explanation does not replace the available evidence, but it gives the manager additional context for the decision.

Set a Clear Expectation

The DSP's manager should explain the applicable expectation and define what the driver needs to do differently.

The expectation should be based on the DSP's policies, current Amazon program requirements, and the circumstances of the event. It should not be generated automatically by the platform or determined by an external support team.

Document the Conversation

A consistent coaching record may include:

  • The date
  • The manager conducting the conversation
  • The information reviewed
  • The driver's response
  • The expectation communicated
  • The client-directed next step
  • The planned follow-up date

Documentation creates continuity between conversations and helps managers determine whether the relevant performance information changes over time.

Recognize Verified Improvement

Coaching should not focus only on problems. When the available data shows meaningful improvement, managers should acknowledge it.

Recognizing progress reinforces the behavior the DSP wants to sustain and helps establish coaching as a development process rather than a purely punitive one.

Strengthen the Operational Processes Behind the Scorecard

Scorecard performance is influenced by more than driver behavior. Dispatch, scheduling, load-out, attendance, fleet readiness, and rescue coordination can all provide important context for delivery results.

Route and Driver Assignment

Not every driver performs the same way on every route. Historical performance information can help DSP managers evaluate which drivers may be better suited to particular route conditions.

Performance information should support the manager's judgment. The platform should not make assignment decisions automatically without client review.

Load-Out Consistency

A disorganized load-out can create delays throughout the route. Drivers may spend more time locating packages, fall behind expected pace, and require additional support later in the day.

Creating a consistent load-out process and reinforcing it during station operations can reduce avoidable disruption.

Rescue Tracking

Rescues are a normal part of delivery operations, but recurring rescue patterns should be reviewed.

Tracking rescue activity by route, driver, time, and reason helps managers identify where additional review may be needed. The DSP's dispatchers initiate and manage rescue decisions.

Attendance and Callout Visibility

Callouts can affect route coverage, assignments, and the workload placed on the available team.

Reviewing attendance alongside route and rescue records helps managers understand whether staffing disruptions may be contributing to delivery-performance problems.

Respond to Safety Events Consistently

Safety information can change quickly, and a single event should not automatically receive the same response as a recurring pattern.

DSPs should establish a client-approved process that considers:

  • The type and severity of the event
  • Whether the event is isolated or recurring
  • The supporting footage or telematics information
  • The driver's explanation
  • Previous coaching records
  • The DSP's safety and employment policies

Real-time monitoring helps authorized managers see events sooner. It does not replace the manager's responsibility to evaluate the evidence and decide what action is appropriate.

LMDmax

How LMDmax helps you work the scorecard

Improving a scorecard means seeing each driver's pattern, week after week. Driver Management Support organizes weekly scorecard imports, driver-by-driver tracking, safety alerts, attendance and coaching records in one place. Your managers interpret the results, coach, and make every operational and employment decision.

See how it works for Amazon DSPs

How Long Does Scorecard Improvement Take?

Based on LMDmax's operational experience, DSPs that implement consistent KPI review, documented coaching, and stronger dispatch processes may begin to see meaningful scorecard improvement within four to six weeks.

Because the scorecard reflects performance across reporting periods, the full effect of operational changes may take eight to twelve weeks to appear.

The exact timeline depends on:

  • The DSP's starting rating
  • The categories requiring improvement
  • The size and consistency of the performance gap
  • Driver performance
  • Route and operating conditions
  • How consistently the new processes are followed

These timeframes are operational expectations, not guaranteed results. Reaching and sustaining Fantastic+ ultimately depends on the DSP's performance and Amazon's current scorecard requirements.

Frequently Asked Questions

Which scorecard category should a DSP address first?

Begin with the current official scorecard and identify the category creating the largest verified performance gap. Review the supporting driver and operational information before deciding what action to take. There is no single category that every DSP should prioritize first.

Does one driver-level exception mean the driver caused the scorecard issue?

Not necessarily. A driver-level exception is a reason to review the available information. Route conditions, vehicle issues, scheduling changes, staffing disruptions, or other circumstances may be relevant.

How often should managers review scorecard information?

Weekly scorecard results should be reviewed consistently. High-priority safety alerts and operational exceptions may require more immediate review according to the DSP's policies. Attendance, rescues, coaching records, and other supporting information should also be reviewed at an established cadence.

Can real-time monitoring improve scorecard performance?

Real-time monitoring gives managers earlier visibility into safety events and driver-performance information. This can support faster review and more timely client-directed follow-up, but monitoring alone does not guarantee scorecard improvement.

How long does it usually take to move from Great to Fantastic+?

DSPs may begin to see meaningful improvement within four to six weeks after implementing consistent KPI review, documented coaching, and stronger operational processes. The full effect may take eight to twelve weeks to appear across the scorecard's reporting periods. Results vary by operation and are not guaranteed.

Can dispatch planning affect scorecard results?

Dispatch planning can influence the conditions under which drivers perform. Route assignments, staffing coverage, load-out consistency, rescue coordination, and vehicle availability may all provide relevant context for scorecard results.

Does LMDmax coach or discipline drivers?

No. LMDmax can monitor and surface performance information, prepare supporting reports and documentation, and facilitate client-approved communication. The DSP retains exclusive authority to manage, coach, discipline, assign, or separate its drivers.

Should DSPs share scorecard information with drivers?

That is a client decision. Team-level information can help communicate shared performance goals, while individual information is generally better addressed privately through the DSP's coaching process. DSPs should follow their internal policies and applicable requirements when sharing employee-performance information.

Build a Process That Can Be Sustained

Moving from Great to Fantastic+ is not about one intense week of review and coaching. It requires a process that managers can follow consistently:

  • Review current scorecard information
  • Monitor important events in real time
  • Connect scorecard results with supporting operational records
  • Identify individual and systemic patterns
  • Make client-led coaching and management decisions
  • Document the response
  • Follow up on the results

LMDmax provides the visibility, workflows, and managed support that help DSPs maintain this process. The DSP remains in control of every operational and employment decision.

Ready to build a more consistent scorecard process? Book a demo with LMDmax to see how our operations software and managed support help Amazon DSPs turn performance information into consistent, client-led action.

Get Started

See how LMDmax can help your DSP operation

Book a demo and walk through the tools and support services built for your business.

Book a Demo