Delivery Exception Report Template: Capture Delays, Damage and Next Actions

A delivery exception report template creates one reliable record when a shipment does not follow plan. It connects the shipment, observed problem, evidence, customer impact, communications, recovery decision and final outcome.

It should not assign liability from incomplete facts. Contract terms, claims, regulated-goods procedures and customer remedies remain with authorized operational, quality, finance and legal owners.

Define exception types and escalation triggers

Publish a simple taxonomy so teams classify events consistently: delay, failed attempt, damage, shortage, overage, wrong item, address issue, documentation failure, temperature excursion, refused delivery or missing proof. Allow “other” with explanation rather than forcing a false category.

Set escalation triggers by customer impact, product sensitivity, safety, contractual commitment and repeated pattern. Name the coordinator and specialist routes. Use the warehouse shift handover checklist when ownership crosses shifts.

Copy this delivery exception report template

DELIVERY EXCEPTION REPORT

Exception ID / opened at / status:
Order / shipment / tracking references:
Customer / destination / contact route:
Carrier / service / planned delivery window:

EXCEPTION
Type / first observed at / observed by:
Confirmed facts:
Unknown or disputed details:
Items, quantities, lots or serials affected:
Customer and operational impact:

EVIDENCE
Tracking events / proof-of-delivery reference:
Photos, scans, labels, temperature or seal records:
Driver, warehouse or customer statements:

RESPONSE
Immediate containment:
Customer update / time / owner:
Recovery options and decision authority:
Action / owner / due time:

RESOLUTION
Delivered, replaced, returned, credited or other outcome:
Approval and system references:
Customer confirmation:
Cause and preventive follow-up:
Closure reviewer / time:

Keep original evidence in its controlled system and link it by reference. Do not expose personal phone numbers, signatures or location data beyond the authorized audience.

Establish the planned delivery baseline

Record the agreed destination, items, quantities, service, delivery window and special handling from the authoritative order and shipment records. Distinguish a customer-requested date from a carrier estimate and a contractual commitment. Capture the baseline before updating it.

Document time zones and local times explicitly. If the plan changed, identify who authorized the change and when it became effective. This prevents a revised estimate from erasing the original exception.

Record facts at first observation

State who observed what, where and when. “Carton crushed on lower-left corner at 10:42 local time” is stronger than “badly damaged.” For shortages, identify ordered, dispatched and received quantities in the same unit. For delays, record the last confirmed event rather than guessing the vehicle’s position.

Capture the condition of outer packaging, inner packaging, seals and labels separately. For a failed attempt, record the verified access condition and contact action without exposing door codes or blaming the recipient. For a wrong-address concern, compare the label, order record and carrier instruction while restricting personal data. Every correction should preserve the original entry, reason, author and timestamp.

Separate fields for confirmed facts, customer statements, carrier statements and unknowns. A status message may be useful evidence, but it may not establish the physical condition or cause. Preserve corrections rather than overwriting the first report silently.

Preserve condition and chain-of-custody evidence

Relevant evidence can include labels, seals, packaging, photographs, scan events, temperature logs, proof of delivery, loading records and signed exception notes. Record device or system timestamps and maintain original files. The quality inspection report template supports a separate technical assessment when damage or conformance needs specialist review.

Do not ask staff or customers to open unsafe packages or handle regulated products simply to improve documentation. Follow safety and product-specific instructions first. Restrict signatures, addresses and contact details to people with a legitimate need.

Assess impact and contain the problem

Assess what is affected now: customer operations, stock availability, product condition, downstream appointments, replacement capacity and documentation. Avoid converting uncertainty into a definitive loss estimate.

Containment may include holding remaining stock, stopping onward distribution, preserving packaging, checking related consignments, securing temperature-sensitive goods or reserving replacement inventory. Each action needs an owner and review time. Containment is temporary; label it clearly so it does not become an indefinite hidden hold.

Communicate without overpromising

Give the customer a concise update: confirmed facts, present impact, action underway, next update time and contact owner. Say what is unknown. Do not promise a delivery time, refund or replacement that the sender or carrier has not authorized.

Document material communications and corrections. Use meeting follow-up principles when several stakeholders agree actions in a call.

Choose and authorize the recovery path

List feasible options such as reattempt, reroute, partial delivery, replacement, collection, return, repair assessment or commercial review. Show customer need, operational feasibility, cost authority and product constraints. The coordinator can organize the decision without assuming authority for credits, disposal or contract interpretation.

Test each option against cut-off times, replacement availability, handling restrictions, customer availability and downstream commitments. If a partial recovery could create a second failure, state that tradeoff. Confirm whether the customer is choosing among approved options or merely expressing a preference. Record any condition attached to acceptance, such as inspection on arrival or return of damaged goods.

Record the selected option, decision owner, time, dependencies and fallback. A decision log template helps when the recovery choice is material or contested. Keep customer preference distinct from the organization’s approved commitment.

Track actions, owners and update times

Use one action list rather than parallel email threads. Each row needs a deliverable, one owner, due time, status and evidence. “Carrier investigating” is not an action; “Carrier operations to confirm depot scan by 15:00 UTC” is.

Include a next-update time even when no resolution is expected. If ownership transfers, record acceptance by the new owner and brief them on facts, commitments and unresolved questions. Do not close because a ticket moved teams.

Determine cause without assigning premature blame

After recovery is stable, review packing, labeling, loading, routing, scan, address, carrier and receiving evidence. Distinguish immediate event, contributing conditions and systemic cause. One delivery can have multiple contributors.

Convert recurring causes into specific controls: revised packaging instruction, address validation, scan checkpoint, carrier review, training or targeted audit. Assign a measure that can show whether the change worked. Do not close a preventive action simply because a document was updated; verify that the process changed where the exception occurred.

Route claims, misconduct, security, safety and contractual questions through their controlled processes. A general exception report should reference those records, not reproduce restricted allegations. Trend review should use comparable definitions and verified data, not anecdotal impressions.

Capture exception calls responsibly

Exception calls can include customer details, addresses, commercial terms and staff statements. Record only when authorized and necessary, with clear notice and agreement where required. Apply purpose limits, access controls, retention and a correction process.

For an authorized logistics call with visible, consented capture, Kuno can help create draft notes, decisions and actions for human review. It does not determine liability, customer remedies or shipment condition. Explore Kuno

Verify names, tracking references, quantities, times and promises against source records before distribution.

Verify resolution and close the report

Close only when the selected recovery outcome is evidenced, customer communication is complete, inventory and order records are reconciled, required approvals are recorded and preventive follow-up has an owner. Keep unresolved claims or quality investigations linked and visible.

Final QA checklist:

• Shipment, order, customer, destination and time zone are unambiguous.
• Original plan and later estimates remain distinct.
• Facts, statements, assumptions and unknowns are labeled.
• Affected items, units, lots and conditions are specific.
• Evidence is preserved with appropriate access.
• Containment and customer updates have named owners.
• Recovery commitments were made by authorized roles.
• Actions include due times and verifiable outputs.
• System, inventory and commercial records are reconciled.
• Closure reflects a verified outcome, not ticket movement.

Create a reviewable exception record from an authorized conversation, then confirm it against operational evidence. Kuno supports consented capture; responsible teams retain control of recovery, claims and closure. See Kuno