Freight Claims Recovery: An Owner's Strategy Guide

Your operations team handled 400 shipments last month. Fourteen had documented exceptions: cargo damage, shortages, delays with financial impact. Your team filed claims on six of them. The other eight fell through the cracks. Someone was too busy. The documentation window closed. The amount seemed too small to bother with. Freight claims recovery is the margin protection work that most forwarding companies treat as an afterthought, and the cost adds up fast.

According to CorePiper’s 2026 State of Freight Claims report, roughly half of all eligible freight claims are never filed. Claim volumes have grown 12% year over year since 2024, so the gap between what you’re owed and what you actually recover keeps getting wider.

The Financial Scale of Unfiled Claims

U.S. shippers lose over $50 billion annually to freight damage, shortages, and service failures, according to CorePiper. That figure covers the entire supply chain, not just forwarding. But even a narrow slice hurts at the individual company level.

A mid-size forwarder handling 500 shipments per month with a 3% exception rate sees about 15 exceptions per month. If the average claimable value per exception is $2,000 and you file on only half of them, that’s roughly $15,000 per month left on the table. Over a year, $180,000 in margin that your company earned, your operations team documented, and nobody recovered.

That $180,000 is often more than the fully loaded cost of the ops coordinator who could be managing the claims process. A dedicated claims function usually pays for itself within the first quarter.

This isn’t unique to smaller operators. Larger forwarders with higher volumes face the same filing gaps at a bigger scale. The difference is that well-run operations have built claims recovery into their standard workflow instead of treating it as a side task that gets attention when someone remembers.

Why Do Most Freight Claims Go Unfiled?

The filing gap isn’t laziness. It’s structural. Five patterns explain why eligible claims consistently go unrecovered.

1. No one owns the process. Claims filing sits between operations, finance, and customer service. Ops knows about the damage. Finance handles reconciliation. Customer service manages the client relationship. When nobody has explicit ownership of the claims workflow, exceptions get logged but never pursued.

2. The documentation window closes fast. Most carrier contracts require notice of damage within specific timeframes, often 48 to 72 hours for visible damage and 15 to 30 days for concealed damage. If your team discovers a shortage on Wednesday but doesn’t start the claim until Monday, half the window is already gone. Under the Hague-Visby Rules, the notice period for visible ocean freight damage is just three days from delivery.

3. Small claims get deprioritized. A $500 damage claim doesn’t feel worth two hours of documentation work. But ten $500 claims per month that never get filed add up to $60,000 per year. One claim looks marginal. The total is not.

4. Documentation is scattered. Filing a claim requires the bill of lading, commercial invoice, packing list, inspection report, photographs, and often the original quote or rate confirmation. These documents live in different systems, different inboxes, and sometimes different offices. Assembling the package for a single claim can take a full afternoon.

5. The team lacks claim-filing expertise. Your ops coordinators know how to move cargo. They don’t know how to build legal arguments for carrier liability. Without templates, checklists, or training, each claim becomes a one-off exercise that feels harder than it should.

All five are process problems, not people problems. They have process solutions.

Manual Recovery vs Systematic Recovery

According to CorePiper, companies using manual, ad-hoc claims processes recover 35 to 45% of the value they pursue. Companies with systematic, documented processes recover 70 to 85%.

The gap isn’t mainly about technology. It comes down to three things:

Filing rate. Systematic processes catch every eligible exception because the trigger is built into the shipment workflow. When an exception is logged at the milestone level, it automatically flags for claims review. Manual processes depend on someone remembering to start a claim, so the filing rate drops as operational volume goes up.

Documentation completeness. Incomplete documentation is the single biggest cause of claim denials. Industry data suggests that 35 to 40% of denied claims fail because supporting documents were missing or insufficient. A systematic process that pulls documents from a centralized shipment record eliminates this. A manual process that requires someone to hunt through emails and shared drives does not.

Follow-up discipline. Carriers rarely deny claims outright. They delay. They request additional information. They let the clock run. A claim filed on January 15 that gets a “we need more documentation” response on February 20 will expire if nobody responds by March. Manual processes lose claims to calendar drift. Systematic processes have escalation timers.

The real question isn’t whether to automate claims (that depends on volume and complexity). It’s whether your current process ensures that every eligible exception gets filed, documented completely, and followed through to resolution. If not, you’re operating at the 35% recovery end of the spectrum.

Five Components of an Effective Claims Process

Building a claims recovery process doesn’t require specialized software. It requires clear ownership, defined triggers, and consistent execution.

1. Exception-to-claim trigger. Every operational exception with financial impact should be evaluated for claim eligibility within 24 hours of discovery. Your exception management process needs a branch point: is this exception claimable? If yes, route it to the claims workflow. If no, document why and close it.

2. Claim ownership. One person or team owns claims from filing through resolution. This doesn’t need to be a full-time role at a small forwarder. But it needs to be an explicit responsibility with time allocated for it, not something squeezed in between booking confirmations and customer calls.

3. Document assembly checklist. For each claim type (damage, shortage, delay, overcharge), maintain a checklist of required documents. Your ops team should be building the claim file in real time as they handle the exception, not retroactively assembling it weeks later. The checklist for an ocean cargo damage claim typically includes:

• Bill of lading (HBL and MBL)
• Commercial invoice
• Packing list
• Inspection or survey report with photographs
• Delivery receipt noting the damage
• Original booking confirmation or rate agreement
• Repair estimate or replacement cost documentation

4. Filing timeline tracker. Track the contractual deadline for each open claim. Carriers, modes, and jurisdictions all have different filing windows. The Carriage of Goods by Sea Act gives one year for ocean claims in the U.S. The Montreal Convention gives two years for air cargo claims. But carrier-specific contracts often impose shorter windows. If you’re not tracking these deadlines, you will miss some.

5. Resolution follow-up cadence. Set a 14-day follow-up cycle for every open claim. If the carrier hasn’t responded, escalate. If they’ve requested additional documentation, provide it within 48 hours. From what we’ve seen working with mid-size forwarders, the biggest difference between companies that recover well and those that don’t is follow-up speed. Carriers process claims from the squeaky wheels first.

What Claim Volume Justifies a Dedicated Function?

There’s no magic number, but the economics point to a useful threshold. If your operation generates more than 10 claimable exceptions per month with an average value above $1,500, the annual recovery opportunity exceeds $180,000 at a 100% filing rate. At a more realistic 70% recovery rate, that’s $126,000 per year.

A dedicated claims coordinator at a mid-size forwarder costs $45,000 to $65,000 fully loaded, depending on the market. The role pays for itself at roughly 5 to 7 claimable exceptions per month. Below that threshold, claims responsibility can sit with an existing ops lead who allocates a few hours per week to it. Above it, a dedicated function makes money instead of costing it.

The calculation shifts again when you factor in client relationships. Proactive claims recovery on behalf of your customers sets you apart. A forwarder who files and recovers claims without being asked builds loyalty that a competitor can’t replicate on price alone.

Most owners already have the data to calculate this. Your settlement process captures the gap between expected and actual costs. Your exception logs capture the incidents. The missing piece is connecting those two data sets and acting on the result.

Documentation That Makes or Breaks Your Claim

Every claims professional will tell you the same thing: the quality of your initial filing determines the outcome.

Photograph everything, immediately. Damage claims live and die on photographic evidence taken at the point of discovery. Photos taken three days later, after the container has been destuffed and the cargo moved, carry much less weight. Photograph the container seal before opening, the container interior showing cargo position, and the damaged items from multiple angles before anything is moved.

Match every number. The bill of lading says 450 cartons. The packing list says 448 cartons. The delivery receipt says 445 cartons. Those discrepancies need to be documented and reconciled in the claim filing. If you claim a shortage of 5 cartons but your own documents show conflicting counts, the carrier will use that inconsistency to challenge the claim. This is where strong document management practices pay off downstream.

Quantify the loss precisely. “Approximately $3,000 in damaged goods” is weak. “147 units of SKU X at $18.50 per unit = $2,719.50, per attached commercial invoice line 12” is strong. Carriers look for vague valuations as grounds for reduction. Precise, invoice-backed numbers are harder to dispute.

Include the causal chain. Don’t just document what happened. Document why the carrier is liable. Water damage to cargo in a sealed container with no ventilation damage implies the container wasn’t properly inspected before loading. Crushed cartons in the bottom layer of a container loaded by the carrier’s CFS implies improper stowage. That causal connection between the carrier’s action (or inaction) and the loss is what turns an incident report into a successful claim.

Frequently Asked Questions

What is freight claims recovery?

Freight claims recovery is the process of filing for and collecting compensation from carriers, terminals, or insurers when cargo is damaged, lost, or delayed during transit. It covers the full cycle from exception identification through claim filing, documentation, carrier negotiation, and payment collection. Consistent recovery depends on having a repeatable process rather than filing claims ad-hoc.

How long do you have to file a freight claim?

Filing deadlines vary by transport mode and jurisdiction. For ocean freight under the Carriage of Goods by Sea Act, the statute of limitations is one year from delivery. For air cargo under the Montreal Convention, it is two years. However, notice of damage must typically be given within 3 days for visible damage and 14 days for concealed damage. Individual carrier contracts may impose shorter windows, so always check the terms of your specific agreement.

What percentage of freight claims get denied?

Industry data shows that 35 to 40% of freight claim denials result from incomplete documentation rather than lack of merit. Overall denial rates vary by carrier and mode, but forwarders with systematic documentation processes see much lower denial rates than those filing ad-hoc. The most common reasons for denial are late filing, insufficient evidence of damage, and failure to establish carrier liability.

Who is responsible for filing freight claims: the shipper or the forwarder?

Legally, the party named on the bill of lading as shipper or consignee has standing to file. In practice, forwarders often file on behalf of their clients as part of their service, and doing so is becoming a competitive differentiator. Handling claims proactively reduces client burden and strengthens the business relationship.

What is the difference between a freight claim and a cargo insurance claim?

A freight claim is filed against the carrier based on their liability for loss or damage during transit. A cargo insurance claim is filed against the shipper’s or consignee’s own insurance policy. They are not mutually exclusive. Best practice is to file the carrier claim first (since the carrier bears primary liability under the bill of lading) and pursue the insurance claim if the carrier claim is denied or the recovery is insufficient.

How Tier2 Cargo Supports Claims Tracking

The claims workflow described above connects directly to Tier2 Cargo’s shipment lifecycle. Every shipment in the system carries its full document set, milestone history, and financial record from quote through settlement. When an exception occurs, the documentation needed for a claim is already in one place instead of scattered across inboxes and shared drives.

Tier2 Cargo’s 3-stage profit tracking surfaces the gap between forecast, invoiced, and realized margins on every shipment. When a claim is warranted, the cost variance is already visible. Exception tracking ties operational events to financial outcomes, so your claims team has the data they need without digging for it after the fact.

For forwarders ready to move claims recovery from an ad-hoc task to a managed process, see how Tier2 Cargo structures the shipment lifecycle or book a walkthrough with our team.

In a compressed-rate environment, the forwarders who protect their margins aren’t only the ones negotiating better buy rates or managing surcharges more carefully. They’re the ones who recover what they’re already owed. Every unfiled claim is margin you earned and gave away. The fix isn’t complicated, but the process does need to exist.