Delivery exceptions: a playbook for evidence, ownership and updates

Read the event before assigning a cause

Keep the original carrier event, its timestamp and time zone beside your plain-language explanation. UPS describes an exception as an unexpected issue that may change the scheduled delivery date. Its guide also distinguishes label creation from the carrier taking possession. These meanings are specific to UPS; check the relevant carrier before applying the same interpretation elsewhere.

For an old or missing scan, inspect the dispatch record, carrier acceptance evidence and any last-mile tracking number. A gap alone does not establish that a parcel is lost. Record what is confirmed and what still needs checking.

Sort cases by the action they need

Use a small set of actionable queues: dispatch evidence missing, carrier investigation, customer information needed, delivery dispute and approved return. Give each queue an escalation rule based on the service and route. Review a missed customer promise or expiring carrier enquiry window before a low-risk informational event.

For address or customs questions, request only the missing information through an appropriate secure channel. Log the carrier case reference and the response deadline. Confirm who is authorized to approve a replacement or refund before offering either.

Write a handoff someone can act on

Every open case should name one accountable owner, the receiving team, the evidence already checked, the next action and the next review time. Include a time zone. A shift change should transfer these details with an explicit acknowledgement from the next owner.

Illustrative example: a parcel has no new event after carrier acceptance. The warehouse coordinator checks the handover receipt; the delivery operations owner opens a carrier enquiry. Support tells the customer: “We are checking the last confirmed handover with the carrier. We will update you by 16:00 UTC tomorrow.” This is a sample process, not a delivery forecast or a JetonTrack case.

Measure exceptions against comparable shipments

Define the shipment cohort, observation window and exception rule before calculating a rate. Count each affected shipment once, even if it generates several events. Separate still-open cases from resolved cases and track case age alongside the final outcome.

Illustrative calculation: 40 distinct shipments have an exception among 1,000 shipments dispatched in one week and observed for 14 days. The exception rate is 40 ÷ 1,000 = 4%. If those shipments generate 65 contacts, that is 65 contacts per 1,000 shipments, a different measure. Compare the same route, service and observation period; a younger cohort can look healthier simply because problems have not appeared yet.

Close the loop with a recorded outcome

Close a case when you have evidence of its outcome and have sent the appropriate customer update. Record delivery confirmation, an approved remedy or the agreed return path. Review recurring causes with fulfillment and support. Keep unknown causes visible instead of assigning blame from an incomplete scan history.

• Preserve the latest carrier evidence and enquiry reference.
• Name the owner, next action and next update time.
• Check that the customer message matches the evidence.
• Record the outcome and include the case in a defined reporting cohort.

Common questions