How to manage van damage claims at an Amazon DSP

Van damage is one of those operational problems that feels manageable until it isn't. A scrape here, a reversing collision there — and by the end of the month you're looking at an insurance excess that wipes out a week's margin, a fleet insurer asking questions, and a driver who swears the damage was already there. Managing van damage claims properly is not just about saving money. It protects your drivers, keeps your fleet insurer onside, and removes a major source of back-and-forth with Amazon.

Why damage claims spiral without a process

The core problem is the gap between when damage happens and when anyone finds out about it. A driver scrapes a wing mirror at 7am, says nothing, returns the van at 6pm, and the next driver takes it out the following morning without a check. By the time the damage is logged, no one knows who caused it, when it happened, or whether the other party's vehicle was involved. At that point your options are limited and your insurer is paying out on an incomplete picture.

A reliable damage management process closes that gap. It does not require expensive software or lengthy procedures. It requires three things done consistently: a daily walkaround before dispatch, an immediate incident report when damage occurs, and a review before the van goes out again.

The pre-dispatch walkaround is your first line of defence

Every van should be walked around and photographed before it leaves the station — every day, every driver, no exceptions. The photographs matter because they establish a baseline. If damage appears on the van that was not in the morning photos, you know it happened during that driver's shift. If the damage was already there, the photos prove it.

The inspection should cover all four corners, the roof, the rear doors, and the load area. Tyre condition and lights are worth checking while you're there — a blown tyre mid-route is a far worse outcome than a thirty-second check before dispatch. Drivers who are used to the routine complete it in under five minutes.

The key is getting the photos timestamped and linked to the driver. A photo taken on a personal phone and never submitted is useless when the claim lands. The inspection needs to be logged centrally, not stored in a WhatsApp group.

What to do when damage occurs mid-shift

Drivers need a clear, simple process to follow the moment an incident happens — one they have been told about during induction and reminded of regularly. Without a clear process, the instinct is to say nothing and hope for the best. That instinct costs you more than the incident would have.

The process should be:

• Stop and assess. Is anyone hurt? If there is any injury — driver, third party, or pedestrian — call 999 before anything else.
• Photograph everything immediately. The other vehicle, the van, the road position, the surrounding area. Wide shots and close-ups. Before anything moves.
• Exchange details. Name, contact number, vehicle registration, and insurance details for any third party. Do not admit liability and do not apologise — even informally.
• Call the OSM. Not after the shift. Now. Your manager needs to know while the details are fresh and while there is still an option to send another driver if the van is not roadworthy.
• Complete an incident report before the end of shift. Written, signed, and submitted that day.

If the van is damaged but the driver is not sure whether a third party was involved — a car park scrape, a gate catch — the same process applies. Log it, photograph it, report it. Unknown-cause damage handled this way is manageable. Unknown-cause damage discovered a week later is a dispute.

Returning damaged vans and handover checks

The return check is as important as the pre-dispatch check. When a driver returns the van, the outgoing condition photos are compared against the return condition. Any new damage is flagged immediately, recorded against that shift, and the driver signs a record of it.

This does two things. First, it makes the accountability clear — damage is attributed to the right person at the right time rather than becoming a running argument. Second, it signals to drivers that the process is real. If they know the return check happens every day without fail, the pressure to report damage mid-shift rather than hope it goes unnoticed rises significantly.

Managing the insurance claim and keeping costs down

When a claim is inevitable, speed and documentation determine the outcome. Notify your insurer promptly — most commercial fleet policies require notification within 24 to 48 hours even if you are not planning to claim. Late notification is grounds for reducing or refusing a payout, and it draws attention to your process when an auditor looks at your claims history.

Gather everything before you call: the incident report, the pre- and post-shift photos, the driver's statement, the third-party details if applicable, and any dashcam footage. A well-documented claim is settled faster and with less argument over liability. An undocumented claim costs you an excess, sometimes your no-claims bonus, and occasionally the renewal.

Fleet insurers price renewals partly on claims frequency and partly on how well-managed those claims appear. Consistent documentation, prompt reporting, and a clear internal process are evidence that your operation is professionally run. Over time, that evidence is worth money at renewal.

Where DSPOps fits in

DSPOps includes a daily van inspection module that logs timestamped, driver-linked walkaround photos before dispatch and at return — so every shift starts and ends with a documented baseline. When damage appears, you know exactly which shift it happened on, who was driving, and what the van looked like before they left. Incident reports are filed in the same place and attached to the relevant shift record, so when your insurer asks for documentation, it is all in one place.

If you want to see how it works in practice, book a short demo and we will walk through the inspection flow with your fleet size in mind.