logistics-exception-management

Manage freight exceptions across LTL, FTL, parcel, intermodal, ocean, and air modes.

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Zenobia000/ai-brainstorming --skill logistics-exception-management-zenobia000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logistics-exception-management
Source: https://github.com/Zenobia000/ai-brainstorming/tree/main/.claude/custom-rule%26skill/skills/logistics-exception-management
Command: npx skills add https://github.com/Zenobia000/ai-brainstorming --skill logistics-exception-management-zenobia000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork and administrative burden of managing complex freight exceptions including shipment delays, damage, loss, and carrier disputes, which require specialized domain knowledge of regulations, carrier-specific rules, and cross-stakeholder coordination to resolve without financial loss or damaged customer relationships.

Core Features & Use Cases

  • Exception Classification & Workflow: Automatically categorize exceptions by type (delay, damage, loss, refusal) and severity, then apply mode-specific resolution workflows for LTL, FTL, parcel, intermodal, ocean, and air freight.
  • Claims & Dispute Management: Handle carrier liability disputes, file freight claims in compliance with regulations like the Carmack Amendment, and negotiate settlements to maximize financial recovery.
  • Escalation & Prioritization: Follow tiered escalation protocols and prioritize exceptions based on financial impact, customer tier, and time sensitivity to resolve high-risk issues first.
  • Use Case: A 500-unit LTL shipment arrives with 30% damage, and the carrier claims force majeure. Use this Skill to collect evidence, assess liability, file a claim, and negotiate a settlement while preserving the carrier relationship.

Quick Start

Use the logistics-exception-management skill to handle the delayed LTL shipment with PRO# 12345 for our enterprise client, classify its severity, and draft a proactive customer update with the revised delivery timeline.

Frequently Asked Questions about logistics-exception-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I file a freight claim for damaged LTL shipments under the Carmack Amendment?

Freight exception management involves classifying shipment issues like delays, damage, and loss by severity, then applying mode-specific resolution workflows for LTL, FTL, parcel, intermodal, ocean, and air freight to recover financial losses.

How do I manage freight claims and carrier liability disputes across different shipping modes?

Freight exception management involves classifying shipment issues like delays, damage, and loss by severity, then applying mode-specific resolution workflows for LTL, FTL, parcel, intermodal, ocean, and air freight to recover financial losses.

Can I prioritize shipment delays and freight exceptions based on customer tier?

Yes, you can prioritize shipment delays by following tiered escalation protocols that rank freight exceptions based on financial impact, customer tier, and time sensitivity to resolve high-risk issues first.

What is the best way to resolve carrier disputes when a shipment arrives with 30% damage?

The best way to resolve carrier disputes for damaged freight is to collect delivery evidence, assess liability against force majeure claims, file a compliant freight claim, and negotiate a settlement while preserving the carrier relationship.

Does freight exception management apply to ocean and air freight carrier disputes?

Yes, freight exception management applies to ocean and air freight carrier disputes by executing cross-mode resolution workflows, handling liability negotiations, and tracking carrier performance across all logistics operations.

When do I need to escalate a freight claim for a delayed shipment?

You need to escalate a freight claim for a delayed shipment when tiered escalation protocols indicate high financial impact, high customer tier sensitivity, or critical time sensitivity that requires immediate resolution.