What does a failed handover look like during a delivery exception?

A depot coordinator marks shipment `SHIP-4821` as awaiting redelivery after a failed delivery attempt. The transport team creates case `CASE-0412` for customer service, attaching the driver's delivery note and the current address. The shipment moves from active transport work to customer contact required.

The delivery note says that access requires a booking with the receiving site's facilities team. A separate dispatch comment records a commitment to preserve the original delivery charge. Customer service can arrange a new date, but it cannot authorise that charge treatment.

The receiving agent books another delivery and closes the contact case. The billing team then applies a redelivery fee because the charge commitment never reached its queue. Customer contact succeeded, yet the business obligation was lost between teams.

A generated scenario pack could reproduce these linked records and make the fee appear only after the booking action. It teaches evaluators to look beyond the immediate recipient: some handovers require a second dependent transfer. Success means preserving the commitment, identifying the billing dependency and leaving each outstanding action with an accountable role.