logistics-exception-management

Automate freight-exception analysis, escalation, and claims processing across transport modes.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/cescrafli/compyrasion --skill logistics-exception-management-cescrafli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logistics-exception-management
Source: https://github.com/cescrafli/compyrasion/tree/main/skills/logistics-exception-management
Command: npx skills add https://github.com/cescrafli/compyrasion --skill logistics-exception-management-cescrafli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Freight exceptions routinely stall shipments, generate financial risk, and strain carrier relationships due to manual processes and fragmented workflows. This Skill codifies best practices, standardized escalation paths, and evidence-collection templates to accelerate resolution and protect margins.

Core Features & Use Cases

  • Classification framework: categorize exceptions by type (delay, damage, loss, shortage, misdelivery, overage) and severity to determine next steps.
  • End-to-end workflows: guided processes from initial notification through escalation, negotiation, and recovery tracking.
  • Evidence and documentation templates: PODs, photos, inspection reports, and repair/ Replacement quotes, tailored to carrier requirements.
  • Cross-mode applicability: supports LTL, FTL, parcel, intermodal, ocean, and air with mode-specific rules.
  • Escalation and KPIs: tiered escalation, time/dollar thresholds, and performance metrics to drive accountability.

Quick Start

Identify the current exception and initiate the standard escalation and claims workflow to begin resolution.

Frequently Asked Questions about logistics-exception-management

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

FAQPage Schema
How do I automate freight exception analysis and escalation for damaged shipments?

Freight exception management for damaged shipments automates classification by type and severity to trigger tiered escalation. It generates end-to-end claims workflows with evidence documentation templates like photos and inspection reports to accelerate recovery.

What is the best way to manage carrier disputes and OSD claims across different transport modes?

Managing carrier disputes and OSD claims requires cross-mode applicability with mode-specific rules for LTL, FTL, parcel, intermodal, ocean, and air. The process applies taxonomy-based classification to standardize escalation paths and evidence collection tailored to each carrier's requirements.

How does taxonomy-based classification work for logistics exceptions like loss and shortage?

Taxonomy-based classification for logistics exceptions works by categorizing loss, shortage, overage, and misdelivery events by type and severity. This framework determines next steps by applying policy-driven escalation thresholds to route each exception through the correct claims workflow.

Can I process freight claims and track recovery for both LTL and FTL shipments?

You can process freight claims and track recovery for LTL and FTL shipments using guided end-to-end workflows with cross-mode applicability. The system applies mode-specific rules from initial notification through negotiation to drive accountability via performance metrics.

What evidence documentation do I need to resolve freight delays and carrier disputes?

Resolving freight delays and carrier disputes requires evidence documentation including PODs, photos, inspection reports, and repair or replacement quotes. These templates are tailored to specific carrier requirements to support the end-to-end claims workflow and recovery tracking.