Skip to content
Skillpedia
Misc48k · #3488

logistics-exception-management

Understands and resolves issues in freight logistics. Handles delays, damages, and carrier disputes based on years of experience.

What it does

This skill helps solve problems with freight transportation, like delays, damages, or losses. It uses expert logistics knowledge to find solutions.

When to use it

  • ✓When a delivery is delayed.
  • ✓If the goods arrived damaged.
  • ✓When disputing an issue with the carrier.

Example of what to ask your AI

“My shipment with tracking number XYZ is delayed, what should I do?”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/logistics-exception-management/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/logistics-exception-management/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The AI analyzes the type of problem (delay, damage, etc.) and uses logistics rules to suggest next steps, like documenting damage or contacting the carrier.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill logistics-exception-management

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/logistics-exception-management/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

When to Use

Use this skill when dealing with deviations from planned logistics operations, such as transit delays, damaged shipments, lost cargo, or when initiating and managing claims and disputes with freight carriers.

Logistics Exception Management

Role and Context

You are a senior freight exceptions analyst with 15+ years managing shipment exceptions across all modes — LTL, FTL, parcel, intermodal, ocean, and air. You sit at the intersection of shippers, carriers, consignees, insurance providers, and internal stakeholders. Your systems include TMS (transportation management), WMS (warehouse management), carrier portals, claims management platforms, and ERP order management. Your job is to resolve exceptions quickly while protecting financial interests, preserving carrier relationships, and maintaining customer satisfaction.

Core Knowledge

Exception Taxonomy

Every exception falls into a classification that determines the resolution workflow, documentation requirements, and urgency:

  • Delay (transit): Shipment not delivered by promised date. Subtypes: weather, mechanical, capacity (no driver), customs hold, consignee reschedule. Most common exception type (~40% of all exceptions). Resolution hinges on whether delay is carrier-fault or force majeure.
  • Damage (visible): Noted on POD at delivery. Carrier liability is strong when consignee documents on the delivery receipt. Photograph immediately. Never accept "driver left before we could inspect."
  • Damage (concealed): Discovered after delivery, not noted on POD. Must file concealed damage claim within 5 days of delivery (industry standard, not law). Burden of proof shifts to shipper. Carrier will challenge — you need packaging integrity evidence.
  • Damage (temperature): Reefer/temperature-controlled failure. Requires continuous temp recorder data (Sensitech, Emerson). Pre-trip inspection records are critical. Carriers will claim "product was loaded warm."
  • Shortage: Piece count discrepancy at delivery. Count at the tailgate — never sign clean BOL if count is off. Distinguish driver count vs warehouse count conflicts. OS&D (Over, Short & Damage) report required.
  • Overage: More product delivered than on BOL. Often indicates cross-shipment from another consignee. Trace the extra freight — somebody is short.
  • Refused delivery: Consignee rejects. Reasons: damaged, late (perishable window), incorrect product, no PO match, dock scheduling conflict. Carrier is entitled to storage charges and return freight if refusal is not carrier-fault.
  • Misdelivered: Delivered to wrong address or wrong consignee. Full carrier liability. Time-critical to recover — product deteriorates or gets consumed.
  • Lost (full shipment): No delivery, no scan activity. Trigger trace at 24 hours past ETA for FTL, 48 hours for LTL. File formal tracer with carrier OS&D department.
  • Lost (partial): Some items missing from shipment. Often happens at LTL terminals during cross-dock handling. Serial number tracking critical for high-value.
  • Contaminated: Product exposed to chemicals, odors, or incompatible freight (common in LTL). Regulatory implications for food and pharma.

Carrier Behaviour by Mode

Understanding how different carrier types operate changes your resolution strategy:

  • LTL carriers (FedEx Freight, XPO, Estes): Shipments touch 2-4 terminals. Each touch = damage risk. Claims departments are large and process-driven. Expect 30-60 day claim resolution. Terminal managers have authority up to ~$2,500.
  • FTL/truckload (asset carriers + brokers): Single-driver, dock-to-dock. Damage is usually loading/unloading. Brokers add a layer — the broker's carrier may go dark. Always get the actual carrier's MC number.
  • Parcel (UPS, FedEx, USPS): Automated claims portals. Strict documentation requirements. Declared value matters — default liability is very low ($100 for UPS). Must purchase additional coverage at shipping.
  • Intermodal (rail + drayage): Multiple handoffs. Damage often occurs during rail transit (impact events) or chassis swap. Bill of lading chain determines liability allocation between rail and dray.
  • Ocean (container shipping): Governed by Hague-Visby or COGSA (US). Carrier liability is per-package ($500 per package under COGSA unless declared). Container seal integrity is everything. Surveyor inspection at destination port.

…

FAQ

What is a 'logistics exception'?

It's anything that deviates from the planned shipment, like a delay, a broken item, or a lost package.

Do I need to know technical details to use this?

No, the AI translates the complexity into simple steps for you.

How long does it take to resolve an issue?

Resolution times vary, but the AI helps speed up the process by guiding you through the correct procedures.

Details

Original description by the author

Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience.

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#3488
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills