Effective cargo claims management remains one of the highest-ROI opportunities for asset-based motor carriers. When Over, Short & Damaged (OS&D) events are captured at the first point of exception with photographic evidence tied to the Bill of Lading (BOL) barcode, carriers dramatically reduce leakage, strengthen subrogation packages, and protect driver settlement integrity.
Strong Tower Consulting has spent more than 18 years helping carriers engineer claims workflows that integrate directly with their existing TMS (Truckmate, McLeod, TMW) and accounting platforms. This playbook details the exact architecture, data model, EDI transaction patterns, and operational discipline required to move from reactive claims handling to proactive, automated recovery.
The Claims Engineering Framework
A mature carrier claims architecture rests on four integrated layers:
- Exception Capture Layer - Mobile photo and barcode annotation at delivery
- OS&D Workflow Engine - Rules-based triage and liability determination
- Subrogation Packaging Engine - Automated generation of claim packages for insurance and shipper recovery
- Financial Reconciliation Layer - Integration with driver settlements, fuel surcharge logic, and detention accounting
Carmack Amendment Liability Limits in Practice
Under the Carmack Amendment (49 USC 14706), motor carriers are generally liable for the actual loss or damage to cargo. However, carriers may establish released-value rates that limit liability when the shipper is given a reasonable opportunity to declare a higher value. Modern claims systems must automatically apply the correct liability ceiling based on the specific rate matrix entry used on the load.
In Truckmate and McLeod environments this is accomplished by storing the released value per hundredweight (or flat maximum) in the carrier rate matrix and surfacing it during the OS&D triage step. Automated checks prevent claims processors from accepting liability above the contracted limit.
| OS&D Event Type | Typical Carrier Liability | Recommended First Action | EDI Impact |
|---|---|---|---|
| Short (OS) | Full invoice value or released rate | Immediate BOL photo + count verification | 214 exception code + 210 adjustment |
| Damaged (D) | Repair cost or depreciated value (less salvage) | High-resolution photos + inspection report | 214 damage code; subrogation package trigger |
| Over (O) | Usually zero unless storage costs incurred | Return to shipper or hold for disposition | 214 status update only |
| Concealed Damage | Limited - must be reported within 15 days | Photographic evidence of packaging | Separate 210 claim filing |
Technical Architecture Components
1. BOL Barcode-Driven Mobile Inspection
Drivers and dock personnel use a mobile application that scans the BOL barcode (typically GS1-128 or proprietary 2D) to pull the load record from the TMS. The app then forces structured exception reporting with mandatory photographs. Metadata (GPS timestamp, driver ID, load number) is embedded directly into the image EXIF and written to a SQL claims repository.
2. SQL Claims Schema Design
A normalized claims schema should include at minimum:
- Claims_Header (ClaimID, LoadID, ProNumber, ClaimType, Status, CarmackLimit)
- Claims_Evidence (EvidenceID, ClaimID, ImagePath, CaptureTimestamp, GPSLat, GPSLong, AnnotateJSON)
- Claims_Subrogation (SubID, ClaimID, InsuranceCarrier, ClaimAmount, RecoveryStatus, RecoveryDate)
- Claims_Settlement_Link (LinkID, ClaimID, DriverSettlementID, AmountDeducted)
3. EDI Transaction Lifecycle for Claims
The architecture must consume and generate specific EDI transactions:
- EDI 204 - Motor Carrier Load Tender (to understand original contract terms)
- EDI 214 - Transportation Carrier Shipment Status Message (exception codes)
- EDI 210 - Freight Invoice (with claim-related adjustments)
Strong Tower recommends a dedicated claims integration service that listens for 214 exception events, triggers workflow rules, and prepares structured subrogation packages for outbound transmission to the shipper's insurance carrier.
4. Automated Subrogation Package Generation
When a claim meets recovery criteria, the system assembles a PDF package containing:
- Annotated BOL images with damage callouts
- Carrier rate confirmation showing liability limit
- Repair estimates or depreciation calculations
- Salvage disposition records
- Proof of timely notification (EDI 214 timestamps)
Integration Points with Core Carrier Systems
The claims engine must maintain real-time synchronization with:
- Driver settlement and escrow modules (deducting proven cargo claims from driver pay)
- Fuel surcharge and accessorial billing logic
- Detention and demurrage accounting to prevent double-dipping
- Insurance policy management systems for aggregate tracking
Measuring Claims Performance
Leading carriers track the following KPIs in near real time:
- OS&D capture rate within 24 hours of delivery (> 94% target)
- Average subrogation recovery percentage (industry average 38%; best practice > 67%)
- Days from exception to subrogation filing (< 9 days target)
- Claims leakage as percentage of freight revenue
Frequently Asked Questions
The released value must be stored as an attribute on every rate in the carrier rate matrix. During OS&D triage the system pulls the specific rate used on that load and caps the claim amount accordingly. This prevents claims staff from inadvertently offering more than the contracted limit and provides clear documentation for subrogation defense.
Use a mobile application that forces the user to scan the BOL barcode first. This associates the photos with the correct load record. Require multiple angles, close-ups of damage, and a photo of the intact seal or packaging when possible. Embed GPS coordinates and timestamp in the image metadata. Store the original files in an immutable repository.
Yes. The architecture is TMS-agnostic at the data layer. We map both Truckmate and McLeod transaction tables into a unified SQL claims schema. EDI 214 and 210 handling is standardized regardless of the source TMS. Strong Tower has delivered identical claims automation playbooks for carriers running each system.
The system must track the 15-day notification window required under Carmack. Automated alerts are generated when a concealed damage notice arrives via EDI or email. The workflow routes these claims to a specialized queue that requires additional documentation proving the damage was not apparent at time of delivery.
Next Steps
Strong Tower Consulting delivers production-ready claims architecture, SQL schema designs, integration specifications, and implementation roadmaps for carriers running Truckmate, McLeod, or TMW. Our independent consulting model ensures you retain complete ownership of the resulting system.
Request a claims process assessment or contact us at 763-244-1373 to discuss your specific OS&D and subrogation recovery objectives.
Strong Tower Consulting, LLC was founded in Minnesota in 2008 by Scott Elliott. In business for more than 18 years. Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership.