The setup
Picture the situation. You've been a delivery contractor for a while. Clean record, consistent routes, no prior damage history to speak of. Then settlement deductions start appearing — one, then another, then more, over the span of weeks or months. The line items just say “Damage Claim — Adjustment.” No incident reports. No photos. No detail on what was supposedly damaged or how the dollar figure was reached.
The instinct most contractors follow first is to call the support line. You explain the situation, you're told the claim is “under review,” and you're promised someone will follow up. Nobody does. You call again. Same script. Weeks pass. The deductions stack up.
The structured approach below is what tends to actually move these claims. The exact dollar figures, timelines, and number of line items will vary by case — what doesn't change is the sequence.
Step 1: Stop calling. Start writing.
The single highest-leverage shift is moving every communication from phone to writing. Phone calls produce no record, and support-line scripts are designed to absorb complaints, not resolve them. From the moment you decide to dispute, every touchpoint goes through email or the in-app written-message channel — saved, dated, screenshotted.
The first written touch is a formal documentation request. Send it to the contractor-support email or written channel for the company. Ask for, for each disputed deduction:
- →The damage report for the incident
- →Any photos taken at delivery or at the customer location
- →Chain-of-custody records showing when damage was identified and by whom
- →The basis for the specific dollar amount being deducted
- →The name of any independent inspector or third party involved
Set a clear deadline — 7 or 10 business days is reasonable. The point isn't to win the argument here; it's to create the documented gap. In our own operating experience, many of these requests are met with partial documentation, late documentation, or no documentation at all. That gap is what your demand letter rests on.
What companies often produce
Typical results from a documentation request on a weakly-supported damage claim. Yours may vary.
Step 2: The demand letter
When the documentation deadline has passed without a substantive response, the next move is a formal demand letter. It lays out the facts plainly:
- →The deductions taken from your settlements (line items, dates, total).
- →The documentation request you formally sent (date).
- →That no substantive documentation was provided within the specified timeframe.
- →The contractual basis: under the deduction-authorization clause of your contractor agreement, deductions require documented substantiation.
- →A formal demand for reversal of the disputed deductions within a specific deadline (10 business days is common).
- →A clear note that failure to respond will result in escalation to formal dispute channels.
Send it via certified email — and where possible, route it to the company's legal department or contractor-resolution team rather than the front-line support desk. Those teams handle demand letters differently than support teams handle tickets.
Use the same process
Generate your demand letter in minutes
ClaimGuard Pro includes the demand letter, documentation request, and evidence checklist used in this walkthrough — customized to your specific situation.
Step 3: What the response often looks like
When a demand letter lands at a team that handles them properly, the response is often a partial offer: reverse some of the disputed amounts immediately, hold others pending “additional review.” The split varies, but partial reversals are common when the company knows their documentation for some line items is thin.
The correct response on your side is to accept the immediate reversal in writing, with an explicit note that it does not settle or waive your dispute over the remaining items. Set a new deadline — another 10 business days is reasonable — for the remaining review. Companies that have moved this far usually resolve the rest within that window or shortly after.
If they don't, the next escalation is a BBB complaint (creates a public record and routes to a different internal team), followed by formal arbitration through the AAA if the amount warrants it. Most contractor agreements include mandatory-arbitration clauses, which means arbitration — not court — is your formal venue.
What makes the difference
Written documentation of everything
Every request, every deadline, every response — documented. By the time a demand letter goes out, the paper trail should be airtight.
Shifted burden of proof
Requesting documentation instead of defending against the claim forces the company to prove their case. If their documentation is incomplete, that incompleteness is the dispute.
Professional language and structure
A demand letter that reads like it came from someone who understands the contract and the escalation path gets handled differently than an emotional support ticket.
Clear, but unspecified, escalation signals
Naming "formal dispute channels" without committing to a specific venue keeps the company guessing — arbitration? state agency? attorney? That ambiguity often motivates resolution.
The lesson
Support phone lines are designed to absorb complaints without resolving them. The structured, written, escalating dispute path described above is what tends to actually move money in this category of dispute. Companies often have weak documentation behind these line items and are essentially betting on the contractor giving up.
We can't guarantee any specific outcome — results depend on your facts, evidence, and the company you're dealing with. What we can say from our own operating experience is: the process matters more than most contractors realize.
For the step-by-step breakdown, see the How to Dispute a Damage Claim guide. For the documents themselves, see the Template Library.
Most of these deductions are disputable.
Use ClaimGuard Pro to build the same documented, professional dispute case described above — without a lawyer. Outcomes depend on your specific facts.