Warehouse Labor / Damage & Exceptions
What Does a Damage Claim Cost When You Can't Prove What Happened?
Usually more than the claim. A deduction you can't answer costs the amount, the office time spent looking, and the precedent it sets for the next one.
September 20, 2026 · 6 min read
A damage claim costs whatever you cannot answer. Not what happened — what you can still show five weeks later, when the deduction appears on a remittance and somebody in your office starts asking who worked that Tuesday.
That is an uncomfortable way to run a business that is otherwise carefully priced, because a single unanswerable deduction can take more than a job earned.
What one undefended claim actually costs
A customer deducts for damage found on a container your crew stripped last month. The job itself was healthy.
Illustrative example with simulated data. The figures show how the calculation works, not a measured customer result — put your own numbers in their place.
One deduction against one completed job
- Deduction the customer has taken
- $1,850.00
- What the job billed
- $2,240.00
- Net billing if the deduction stands
- $390.00
- Crew payout already paid on the job
- $1,120.00
- Result on a job that made money
- −$730.00
- Office time spent searching for evidence
- 3h
- Precedent set for the next claim
- Unpriced
The labor is unrecoverable — it was paid before the claim existed. That is why a deduction does not reduce a job's margin so much as invert it.
The last line is the one that compounds. A claim settled without documentation teaches everyone involved how the next one will go, and claims are not evenly distributed — they cluster at the accounts that found out it works.
You are not arguing about whether damage occurred. You are arguing about what was recorded at the time.
Why the timing is always against you
Damage is found in seconds and claimed in weeks. Everything that would have settled it cheaply is created at the dock, and almost all of it decays immediately:
- The photos are in a personal camera roll, mixed in with four other jobs from the same day
- The supervisor described it in a text thread that has scrolled past three hundred messages
- The signed receiving paperwork went to the office as a photo of a photo
- The two crew members who were at that door have worked forty jobs since
The evidence was free to capture and expensive to reconstruct.
What proof of work has to establish
A defensible record answers five questions without anybody remembering anything:
- What was found. Photos, video where it helps, and a written description in plain language.
- Which job it belongs to. The customer, the site, the work type, the date — inherited from the job rather than typed onto the evidence.
- When it was recorded. Not when it was emailed to the office. When it was captured.
- Who recorded it. A named person, and whether it came from the field or from the office afterwards.
- Who else was there. The crew assigned to that job and their clocked times, which is what makes a follow-up question answerable at all.
Notice that four of the five are context, not content. A photo on its own proves that a crushed carton exists somewhere. It is the context that makes it evidence.
Where it has to live
On the job. In FOREMAN, photos, documents and video are attached to the Load itself, and the attachment carries who uploaded it, when, whether it came from the field or the office, and a title and description if one was written. Notes are recorded against the same Load with their author. Both show up in the job's activity history alongside the crew assignments, clock-ins and clock-outs from the same shift.
That history is also stable. Removing an attachment archives it rather than erasing it, so the record of what was recorded at the time survives the tidying up — which is exactly the property a claim needs and a shared drive does not have.
A supervisor does this from the floor, on the active job, while standing in front of the problem — the same principle as keeping signed paperwork with the Load, applied to the exception rather than the routine.
Being precise about what this is not
- There is no claims workflow. FOREMAN does not adjudicate deductions, track a dispute through stages or produce a claim pack. It keeps the documentation that a claim is decided with.
- There is no “damage report” object. Attachments are photos, documents or video, with a description. The exception is described in a note, in words, by the person who saw it.
- It is not device tracking. The site on the record is the Location the job belongs to, which the lead checked into. FOREMAN's mobile app collects no device location at all.
- It does not prevent damage. It makes documenting an exception cheap enough that it happens every time, including on the jobs nobody expects to be questioned.
The habit that makes it work
Documentation only defends you if it exists before anyone knows it is needed. The jobs that get claimed are not the ones that felt eventful, so the rule has to be unconditional: exceptions get photographed and described on the job, every time, as part of finishing the work. It is the cheapest insurance in the operation, and the same record is what lets you show a customer what was completed without assembling anything.
Common questions
How should a warehouse labor company document damage?
At the dock, attached to the job it happened on, while the crew is still there. Photos and a short written note of what was found, recorded against that job so the customer, site, date, crew and times around it are already established without anyone having to reconstruct them later.
Why are damage claims hard to dispute weeks later?
Because the evidence decays faster than the claim arrives. Photos sit in a personal camera roll with no job attached, the crew who were there have worked forty jobs since, and the only remaining account of what happened is somebody's memory of a shift five weeks ago.
What makes a photo useful as proof of work?
Context. A photo of a crushed carton proves a crushed carton existed. A photo attached to a specific job, uploaded from the field by a named person at a recorded time, alongside a note describing what was found, establishes when it was found and who found it — which is the part a claim actually turns on.
Does damage documentation stop customers from making claims?
No, and it should not be expected to. Real damage happens and legitimate claims should be settled. What documentation changes is that each claim gets decided on what was recorded rather than on who can be more persistent about it.
See documentation that stays with the job
FOREMAN keeps photos, documents, notes and crew activity on the Load they belong to, captured from the floor as the work finishes. The full capability list covers documentation alongside crews, billing and invoices.