Define what counts as delivery proof

A delivery proof is the carrier or recipient record that shows the order reached the agreed place. It may be a scan, a signature, a photo, or a confirmed pickup. The desk should name which forms it accepts before the first parcel moves. A vague standard invites a different answer for every order.

Record the fields that make the proof useful: tracking number, delivery time, recipient location, and the condition noted at handoff. A scan without a location may show the wrong stop. A signature without a name is hard to match. The record should answer who received what and when.

Separate a delivery proof from an internal status. A warehouse note that says shipped is not proof that the customer received the parcel. The desk should not close an order on the strength of its own update. The proof must come from outside the order system.

Agree on what counts as an acceptable substitute when the carrier provides no photo or signature. A carrier confirmation with a timestamp may be enough for a low-value order. A high-value order may need a named recipient. Write the threshold down.

Match the proof to the order before closing

Match the tracking number first, then the delivery address and the order reference. A reused tracking number can attach the wrong proof to a new order. Compare the full record rather than the last four digits. The match should be visible in one view.

Check the delivery time against the promise made to the customer. A parcel delivered after the promised date is a different conversation even when the proof is valid. Record the gap. The desk can then decide whether a customer message is needed.

Confirm the recipient location matches the address on the order. A proof delivered to a neighbor or a front desk may still be correct for the building. Note the difference rather than treating it as a failure. The customer should know where to look.

Close the order only after the match is recorded. A proof in a separate carrier portal is easy to lose when the shift changes. Attach the reference and the key fields to the order. The next reviewer should not have to search again.

Handle a partial or disputed delivery

A partial delivery needs its own status. Some items arrived and others did not, so the order is neither complete nor missing. Record the items received, the items outstanding, and the expected date. Do not close the order on the strength of the first box.

When the customer disputes a delivery, capture their description before defending the carrier. Ask what arrived, when, and where it was left. Compare that account with the proof. The difference often shows whether the issue is location, timing, or theft.

Open a carrier inquiry when the proof conflicts with the customer's account. Give the carrier the tracking number, the delivery scan, and the customer's statement. Set a follow-up date. The desk should not promise a refund before the inquiry returns.

Keep the customer informed with the facts the desk actually has. A short message that names the open inquiry and the next date is better than silence. Do not share internal blame or speculation. The customer needs a path, not a story.

Give the exception one owner and status

Every disputed or missing proof should have one owner at a time. The owner may be the desk specialist, the carrier contact, or the client's fulfillment lead. Write the name and the handoff date. A shared inbox without an owner lets the case drift.

Use a small status set such as matched, awaiting proof, carrier inquiry, partial, and resolved. Each status should have a next action and a time limit. A status that only says open does not tell the team what to do. The queue should sort by the next due action.

Set a decision limit for compensation or reshipment. The desk can prepare the evidence, but a manager should approve money or a replacement. Record the approver and the date. This keeps the specialist out of a promise the business may not keep.

Hand off the case with the proof, the customer statement, and the open question. The next person should not have to rebuild the history from messages. Keep the handoff short and specific. A clean handoff is part of the service.

Review mismatches and carrier patterns

Review mismatches weekly by carrier, route, and proof type. One carrier may have a scanner that records the depot instead of the door. A repeated gap is a process issue, not a single bad parcel. Group the cases before calling the carrier.

Compare the proof rate with the order value and the delivery promise. A low proof rate on high-value orders deserves attention even when the overall number looks fine. Use the comparison to set the sampling rule. Not every order needs the same scrutiny.

Share one corrected case with the desk each month. Explain which field exposed the mismatch and what the specialist did next. A real example teaches the judgment that a checklist cannot fully capture. Remove customer details before sharing.

Retest the match when the carrier or the order system changes. A new portal field can break the tracking match without an error message. Run a known order through the check. Record the result and the date so the control stays visible.

For the next step, compare this workflow with Create a quality sampling plan for a new outsourced lane and Write a customer promise register for outsourced support. For access and oversight, use the authoritative planning reference alongside your own policy.