Understand the general U.S. interstate freight-claim workflow, evidence, federal processing rules, and questions to ask about claims software.
A freight claim is a documented demand for compensation related to cargo loss or damage. A strong process begins when the shipment arrives: record what happened, preserve evidence, notify the appropriate parties, and follow the claim terms and deadlines that apply to the shipment.
At delivery: capture the condition
Before signing, inspect the freight where possible. Note visible damage, shortages, wet packaging, broken seals, or other exceptions on the delivery receipt and take clear photographs of the goods, packaging, labels, and loading condition. If damage is concealed and found later, photograph it before moving or disposing of packaging, and notify the carrier promptly. Keep the bill of lading, delivery receipt, invoice or proof of value, packing list, and relevant correspondence.
Build and submit a complete claim
Identify the shipment and claimant, assert the carrier’s liability for the alleged loss or damage, and state a specified or determinable amount claimed. For covered motor-carrier cargo claims, 49 CFR §370.3 describes the minimum filing requirements. Attach supporting records, but remember that damage notations on a delivery receipt, standing alone, do not constitute a formal claim. The Carmack Amendment addresses carrier liability for covered interstate shipments; see 49 U.S.C. §14706. The governing contract, tariff, shipment mode, and facts can affect the analysis, so confirm the applicable deadline and process rather than relying on a generic calendar.
Send the claim through the carrier’s stated channel and retain proof of receipt. A system should associate correspondence and documents with the shipment, show who submitted each item, and make it easy to follow up when more information is requested.
Track review and resolution
For covered motor-carrier claims, §370.5 addresses acknowledgement, §370.7 addresses investigation, and §370.9 addresses disposition. Track the date received, requests for additional material, responses, offers, denials, and payment. Do not assume a clean receipt makes a later claim impossible or that cargo insurance replaces a claim against the responsible carrier; the applicable coverage and recovery paths differ.
What claims software should demonstrate
- Open a claim directly from a shipment and populate identifiers without losing source records.
- Store photos, receipts, invoices, communications, and version history with access controls.
- Calculate internal reminders from the correct contract or rule and allow a reviewer to verify them.
- Show outstanding evidence, responsible owner, last contact, and next action.
- Export a complete claim file for the carrier, insurer, customer, or counsel.
Ask how the platform handles LTL, truckload, parcel, and international claims, since processes differ. The system can organize evidence and reminders; it cannot guarantee that a carrier will accept or pay a claim.
Compliance and Risk Tools buying guidance
At a glance: Compliance and risk software supports selected workflows such as collecting evidence, tracking review tasks, screening counterparties, recording decisions, and monitoring changes. It does not make an organization compliant or replace legal interpretation. Requirements differ by role, commodity, shipment, jurisdiction, transaction, and contract; separate regulatory duties from voluntary programs and customer terms. OFAC Sanctions List Search; Sanitary Transportation of Human and Animal Food; General Information about the ELD Rule
Common workflows
- Requirement and responsibility mapping: Define the activity, parties, goods, locations, rule or contract, records, responsible owner, and authoritative source before configuring software. Confirm applicability with the agency or qualified counsel where ambiguous. FMCSA Regulations; Part 395—Hours of Service of Drivers
- Screening and human exception review: For sanctions or other list checks, record the query source/date, names and identifiers used, possible match, reviewer decision, and escalation. A similar name is not a match determination; a clear search does not settle other controls. OFAC Sanctions List Search; OFAC
- Evidence, remediation, and audit trail: Demonstrate how evidence is retained, access-controlled, corrected, and retrieved; test a missed record, changed status, and exception. Confirm the system supports—not substitutes for—the applicable program and record rules. Sanitary Transportation of Human and Animal Food; 49 CFR §382.701
Questions to ask providers
- Which specific statutes, regulations, lists, programs, or customer requirements does the proposed workflow address, and for whom?
- What is the underlying source, update cadence, query evidence, and process when a source is stale or unavailable?
- How are false positives, possible matches, overrides, escalation, and final human decisions recorded?
- Can we see retention periods, access roles, data provenance, correction history, audit export, and deletion controls?
- Which tasks are automated versus requiring qualified review, licensed expertise, or separate official submissions?
- What is the complete price and service scope, including list/source licenses, integrations, alert volumes, implementation, and exit/export?
Frequently asked questions
Does compliance software make a company compliant?
No. It can support evidence and workflows, but compliance depends on applicable requirements, accurate data, effective controls, and responsible decisions. FMCSA Regulations
Is every supply-chain compliance requirement a law?
No. Legal requirements, voluntary programs, and customer or contractual requirements have different authority and consequences. Identify the source and responsible party before configuring a workflow. FMCSA Regulations; Customs-Trade Partnership Against Terrorism (CTPAT)
Does an OFAC name-screening alert prove a sanctions match?
No. A potential name match requires review using identifying information and applicable OFAC guidance. Search results alone do not establish identity or resolve all transaction controls. OFAC Sanctions List Search; OFAC
Does a clear screening result prove a shipment is authorized?
No. Screening is one control; classification, destination, end user/end use, licensing, origin, valuation, and other facts may also matter. Consult applicable official guidance and qualified experts. OFAC; Bureau of Industry and Security
Can an ELD platform certify HOS compliance?
A product label does not determine applicability or establish that a carrier's procedures comply. Check the rule, exceptions, exact device status, and carrier responsibilities. General Information about the ELD Rule; Registered ELDs
Does temperature monitoring establish food-transport compliance?
No. FDA's sanitary transportation requirements have defined scope, parties, practices, records, and exceptions; a sensor feature alone does not establish that requirements are met. Sanitary Transportation of Human and Animal Food; 21 CFR Part 1, Subpart O—Sanitary Transportation of Human and Animal Food
What should a compliance platform demo show?
Use a specific obligation and test evidence capture, source date, review, exception escalation, correction, authorization, retention, and audit retrieval. Ask what remains outside the software. OFAC Sanctions List Search; 49 CFR §382.701
Sources (13)
- OFAC Sanctions List Search — U.S. Department of the Treasury, OFAC
- FMCSA Regulations — FMCSA
- Sanitary Transportation of Human and Animal Food — U.S. Food and Drug Administration
- 49 CFR §382.701 — Electronic Code of Federal Regulations
- General Information about the ELD Rule — Federal Motor Carrier Safety Administration
- Part 395—Hours of Service of Drivers — Electronic Code of Federal Regulations
- OFAC — U.S. Department of the Treasury, Office of Foreign Assets Control
- Customs-Trade Partnership Against Terrorism (CTPAT) — U.S. Customs and Border Protection
- Bureau of Industry and Security — U.S. Department of Commerce, Bureau of Industry and Security
- Registered ELDs — Federal Motor Carrier Safety Administration
- 21 CFR Part 1, Subpart O—Sanitary Transportation of Human and Animal Food — Electronic Code of Federal Regulations
- 49 CFR §371.3—Records to Be Kept by Brokers — Electronic Code of Federal Regulations
- Broker and Carrier Fraud and Identity Theft — Federal Motor Carrier Safety Administration