How to Handle a Delivery Associate Complaint the Right Way
A practical guide for Amazon DSP owners and ops managers on handling DA complaints correctly — from first report to resolution — without the legal and operational risk that comes from getting it wrong.
A mishandled delivery associate complaint doesn't just create HR friction — it creates legal exposure, Amazon scorecard risk, and a culture problem that spreads faster than the original complaint did.
A clear, documented complaint process protects the DSP, protects the DA, and produces a paper trail that matters if the situation escalates — to Amazon, to legal counsel, or beyond.
DSPs that handle complaints consistently and correctly build a culture of trust — which directly affects DA retention, team morale, and long-term operational stability.
The mistake most DSPs make before the complaint is even filed
A delivery associate complaint is one of the highest-risk situations an Amazon DSP can face — not because complaints are uncommon, but because the response window is short and the consequences of getting it wrong compound quickly. However, most DSPs don't fail at the investigation stage. They fail in the critical first hours after a complaint is raised, when the instinct to "handle it informally" overrides the process that would have protected everyone involved.
Informal handling — a quick conversation, a verbal acknowledgment, a promise to look into it — feels like the faster, less confrontational path. In contrast, it almost always creates more risk than it avoids. Without documentation, a complaint that could have been resolved cleanly becomes a he-said-she-said situation. Furthermore, without a consistent process, the DA who filed the complaint has no confidence the issue will be taken seriously, and the DSP has no evidence of good faith if the complaint escalates to Amazon or to legal counsel.
The four ways mishandled complaints create downstream damage
Legal exposure
Undocumented complaints that escalate create employment law liability — particularly for harassment, discrimination, or unsafe working conditions where the law requires a paper trail.
Amazon scorecard risk
Unresolved DA complaints — especially those involving route safety, vehicle condition, or conduct — can surface in Amazon's DSP performance review process and affect station standing.
Team culture damage
DAs talk. A complaint that is dismissed, buried, or handled inconsistently signals to the entire team that raising concerns isn't safe — which suppresses legitimate issues and accelerates turnover.
Repeat incidents
Complaints that aren't properly investigated and resolved don't go away — they resurface. The same issue filed a second time, after evidence of prior knowledge, is significantly harder to defend.
The four most common types of delivery associate complaints
Workplace conduct complaints
Harassment, bullying, or inappropriate behavior from a supervisor, dispatcher, or fellow DA. These carry the highest legal risk and require the most careful, documented handling.
Safety and vehicle complaints
Concerns about vehicle condition, unsafe routes, inadequate equipment, or pressure to drive in unsafe conditions. These overlap with OSHA and Amazon safety compliance requirements.
Pay and scheduling complaints
Disputes over hours worked, pay discrepancies, schedule changes without notice, or perceived unfair treatment in route or shift assignment. Often the easiest to resolve with documentation.
Performance and disciplinary complaints
A DA disputing a written warning, a performance improvement plan, or a disciplinary action. These require clean documentation of the original decision and the process used to reach it.
"A complaint handled correctly — even an uncomfortable one — almost always produces a better outcome than the same complaint handled informally and quickly."
Why the process protects the DSP as much as the DA
The complaint process protects the DSP as much as the DA
A well-documented complaint process is one of the strongest legal and operational protections a DSP has. If a complaint reaches Amazon, an attorney, or a legal proceeding, the question isn't just "what happened" — it's "what did you do when you found out." A clear, documented answer is the difference between a resolved incident and an ongoing liability.
The sections that follow cover the five-step process for handling a delivery associate complaint correctly — from the moment it's raised to the moment it's formally closed. Each step includes what to do, what to document, and what mistakes to avoid along the way. For context on broader DSP operations, see Last Mile Support's DSP back-office services.
The first 48 hours: what to do and what to write down
The first two steps of the complaint process happen within a short window and set the tone for everything that follows. How a DSP receives a delivery associate complaint in the first few hours sends an immediate signal to the DA about whether the process is serious. A dismissive or delayed initial response often transforms a manageable complaint into an escalated one.
Documentation, specifically, is where most DSPs underinvest. As a result, the instinct to keep things simple — a note in a phone, a mental record, a verbal acknowledgment — creates the exact gaps that become problems later. Every delivery associate complaint, regardless of how minor it seems at the time, needs a written record created at the moment it is received.
Step 1 — Receiving the complaint correctly
Acknowledge receipt within 24–48 hours
As soon as a complaint is raised — in person, in writing, or via a third party — acknowledge it to the DA directly. The acknowledgment doesn't need to include any finding or judgment. It simply confirms that the complaint has been received and will be reviewed.
Do not discuss with the subject of the complaint yet
A common mistake is immediately going to the person named in the complaint to "get their side of the story." In contrast, doing this before documentation is complete can contaminate the investigation, tip off the subject, and create retaliation risk for the DA who filed.
Assess whether immediate action is needed
Some complaints require immediate operational response before investigation begins — for example, a safety complaint that requires a vehicle to be pulled from service, or a conduct complaint where continued contact between two DAs creates further risk. Assess this in the first hour.
Step 2 — Documenting the complaint
Create a written complaint record immediately
Whether the DA raises the complaint verbally or in writing, the DSP must create a formal written record at the time of receipt.
Record facts only — no interpretation at this stage
The complaint record should capture what the DA said, not what the manager thinks about it. Interpretations, judgments, and conclusions belong in the investigation summary — not in the initial documentation.
What a complete complaint record should include
What to do and what to avoid in the first 48 hours
"The written record created in the first 48 hours is the most important document in the entire complaint process — because it captures what was said before anyone had time to reconsider, revise, or forget."
With the complaint received and documented, the process moves into the investigation phase — where the facts behind the complaint are gathered, assessed, and used to reach a finding. That process is covered in the next section, along with the specific mistakes DSPs make most often during investigation. For guidance on how Last Mile Support helps DSPs manage HR compliance and back-office operations, visit our DSP services page.
How to investigate a delivery associate complaint without creating new problems
The investigation phase is where most delivery associate complaints are either resolved cleanly or made significantly worse. A thorough, neutral investigation produces a finding that holds up regardless of how the complaint is resolved. In contrast, an investigation that starts with a conclusion and works backward produces exactly the kind of paper trail that creates problems later.
Furthermore, the investigation doesn't need to be lengthy or complex to be effective. In most cases, a well-run DSP complaint investigation takes between three and seven business days. What matters isn't the duration — it's that the right steps are followed in the right order and that everything is documented as the investigation progresses.
The five investigation steps in order
Define the scope before gathering evidence
Before speaking to anyone or pulling any records, write down exactly what the complaint alleges and what questions the investigation needs to answer. A scoped investigation is faster, more defensible, and less likely to create collateral issues by ranging too broadly.
Gather documentary evidence first
Before conducting any interviews, pull every relevant document — route records, delivery scans, vehicle logs, scheduling data, and any written communications related to the complaint. Documentary evidence doesn't change after the fact. Witness accounts sometimes do.
Interview the complainant first, then the subject
Conduct a structured interview with the DA who filed the complaint before speaking to the person named in it. Use open-ended questions and take detailed notes. Then interview the subject using the same structured approach.
Interview any relevant witnesses separately
If other DAs or staff members were present or have relevant information, interview them separately. Keep witness interviews focused on facts — what they observed directly — rather than opinions about the parties involved.
Document every step in real time
Each interview, each document reviewed, and each decision made during the investigation should be recorded as it happens. An investigation summary written from memory is significantly weaker than one built from notes taken throughout the process in real time.
Evidence worth gathering — and how to get it
Route & delivery records
Pull from the Amazon DSP portal — route assignments, delivery scans, timestamps for the relevant period.
Vehicle inspection logs
Physical inspection records, pre-trip checklists, and maintenance history for any vehicle involved.
Written communications
Text messages, emails, and app messages between parties — request screenshots directly from both sides.
Scheduling & pay records
Shift records, clock-in/out data, and pay stubs for the relevant period.
Prior disciplinary records
HR files for both the complainant and the subject — relevant history only, not full employment history.
Witness statements
Written summaries of verbal interviews — reviewed and signed by each witness after the interview.
Amazon scorecard data
Performance metrics from the DSP portal relevant to the complaint period — useful context, rarely decisive.
Training records
Completion records for any relevant training — conduct, safety, or harassment — for the subject of the complaint.
Onboarding documentation
Signed acknowledgments of DSP policies relevant to the complaint — confirms the subject was aware of the rules.
How to define the scope of your investigation
What a properly scoped investigation looks like
Before starting any investigation, write a single sentence that defines what you are investigating and what you need to determine. This becomes the first line of your investigation record.
The five most common investigation mistakes DSPs make
Deciding the outcome before the investigation is complete
Starting with a conclusion and gathering only evidence that supports it produces a finding that doesn't hold up and misses the actual facts of the complaint.
Interviewing the subject before the complainant
Speaking to the person named in the complaint first tips them off before the complainant puts their account on record — and the subject's version can then shape how investigators read the complainant's story.
Letting the investigation drag without updates to the DA
A DA who files a complaint and hears nothing for two weeks assumes it's being buried. Even a brief update — "we're still reviewing, expect to hear from us by [date]" — maintains trust in the process.
Allowing the subject to supervise the complainant during investigation
If the complaint involves a supervisor or dispatcher, that person should not be managing or scheduling the DA who filed the complaint while the investigation is active. This creates retaliation risk regardless of intent.
Skipping documentation because the complaint seems minor
Minor complaints that resurface become major ones — especially when the DSP has no record of having addressed the issue the first time. Every complaint needs a documented investigation and outcome.
What to do when legal exposure is involved
"An investigation that follows the right steps in the right order — even on a complaint that turns out to be unfounded — is one of the strongest protections a DSP has."
If the complaint involves potential legal exposure — harassment, discrimination, a safety incident, or anything that could become a formal claim — consider involving an employment attorney before the investigation is complete rather than after. Early legal guidance is significantly less expensive than retroactive damage control. The EEOC's employer guidance on workplace investigations provides a useful baseline for federal compliance requirements.
With the investigation complete and findings documented, the process moves to the response and resolution phase — communicating the outcome to both parties, taking any corrective action required, and formally closing the complaint with a record that reflects what was decided and why. That is covered in the next section.
Communicating the outcome and closing the complaint correctly
The response and resolution phase turns the investigation's findings into action. A decision goes to both parties, corrective measures follow, and the complaint closes with a documented record. A poorly handled response undoes the credibility that a well-run investigation built.
Both the DA and the subject deserve a clear, direct communication about the outcome. How the DSP delivers that communication often determines whether the complaint truly ends here or resurfaces later.
Four steps to respond and resolve correctly
Reach a clear, documented finding
Before communicating anything to either party, the investigation needs to produce a written finding — substantiated, unsubstantiated, or inconclusive. This becomes the basis for every subsequent decision and communication.
Communicate separately to both parties
The complainant and the subject should receive separate, individual communications about the outcome. Neither communication should include details about what the other party said or what action the DSP took against them.
Apply corrective action where required
If the complaint is substantiated, corrective action must follow — proportional to the finding. Verbal counseling, written warning, retraining, or termination depending on severity. Document every corrective action taken.
Follow up within 30 days
After the complaint closes, check in with the DA who filed it within 30 days to confirm the issue has not recurred and that no retaliation has occurred. Document this follow-up as part of the complaint record.
Matching the finding to the right corrective action
What to say to each party
Complaint closure checklist
"The complaint isn't closed when the investigation ends — it's closed when both parties hear the outcome, corrective action is on file, and a follow-up is on the calendar."
Retaliation risk starts after the complaint closes
The period after resolution is when retaliation risk is highest. A DA who then gets fewer hours, less favorable routes, or increased scrutiny has a retaliation claim — regardless of intent. The 30-day follow-up closes that window. For further guidance see the Department of Labor's retaliation resources.
With the complaint formally closed, the final section covers building this process into standard DSP operations. For support with HR compliance and back-office operations, see how Last Mile Support helps DSPs stay operationally sound.
What a complete complaint process adds up to
recap
The five steps at a glance
Common assumptions worth challenging
Questions DSPs ask most often
Not necessarily — but having one makes the process more defensible. At minimum, document the steps in writing and make sure every manager knows what to do in the first 48 hours.
A withdrawn complaint doesn't automatically close the investigation — for conduct or safety complaints, Amazon or legal compliance may require the DSP to act regardless. Document the withdrawal and consult legal counsel before closing.
Retain complaint records for the DA's employment duration plus three years. For discrimination, harassment, or safety complaints, keep them for at least five years.
If the complaint names the DSP owner, a neutral third party must handle it — an HR consultant, an attorney, or a back-office partner. Self-investigation creates significant legal risk.
The bottom line on complaint handling
Most DSPs never build a formal complaint process until something goes wrong. The ones that build it before anything goes wrong stay operationally stable and protect themselves when situations escalate. The process isn't complicated — but it has to be consistent and documented.