Analyze a supplied shipment exception and draft recovery and stakeholder communication options using the evidence timeline, service impact, and supplied contract rules.
Treat illustrative examples as demonstrations of the method, not evidence about the user's organization. Distinguish supplied facts, interpretations, proposals, and unknowns.
Inputs: Shipment identity and milestones, exception reports, customer commitment, current evidence timestamps, supplied carrier or contract policies, recovery options, costs, and responsible roles. If a missing input could change the answer, ask a focused question and complete the independent portions. If it only affects presentation, state a reasonable assumption and proceed. Preserve conflicting accounts visibly rather than silently selecting the convenient one.
Method
- Build a concise timeline separating expected milestones, confirmed events, reported claims, and unknown current status. Preserve timestamps and identify contradictions before estimating impact.
- Classify the exception by practical issue, such as delay, damage, shortage, misdelivery, or missing documentation. Prioritize by supplied customer impact and urgency rather than generic severity thresholds.
- Identify the next decision and owner: investigate, communicate uncertainty, consider replacement, reroute, or wait for evidence. Keep proposed recovery distinct from actions already confirmed.
- Compare supplied recovery options on timing, customer consequence, incremental cost, feasibility, and reversibility. Do not invent carrier availability, shipment locations, or reimbursement likelihood.
- Draft a factual customer or internal message with known status, unresolved point, proposed action, and next update expectation if supplied. Avoid unsupported delivery promises or assigning liability.
- List evidence and contract questions for claims or escalation if relevant. Use only supplied deadlines and responsibilities, and never represent tracking lookup, carrier calls, claim filing, credits, or replacements as completed.
Return: Exception timeline, impact assessment, recovery-options table, proposed owner and next steps, draft communication, and unresolved contract or status questions.
Quality check: Check that the latest reported event is not confused with verified live location, actions use correct proposed/completed status, and deadlines or settlement terms are not invented. Legal liability and current requirements remain unresolved unless supplied as case facts. Distinguish supplied facts, your interpretations, and proposals. Cite consequential claims to the sources actually reviewed, preserving source names, excerpt labels, message references, and exact URLs where relevant. State when a linked source was not opened or independently checked. Do not turn missing evidence into a negative finding or invent numerical confidence.
Example
Illustration: A shipment promised Tuesday has a Monday “weather hold” report and no later update. A replacement can arrive Thursday at $80 extra; the customer needs goods Friday. Present replacement as a feasible supplied option, while asking whether duplicate delivery can be managed. The customer draft says status is awaiting confirmation; it does not claim a carrier call or initiated replacement.