What happens when new information changes the team that should own a request?

Request CASE-0412 reaches a logistics service desk with the message, “The delivery arrived damaged and the driver has gone.” A service agent assigns it to the claims queue and links delivery record DEL-2187.

Before the claims team starts work, a depot coordinator adds a note: the damaged pallet is blocking the receiving entrance, and another vehicle is waiting outside. The request now contains an unresolved site access problem as well as a claim.

The service agent changes the primary owner to the depot operations queue and creates a linked claims follow-up. The case state moves from awaiting claim review to awaiting access clearance. Depot operations can arrange the immediate movement of the pallet; the claims team retains responsibility for assessing the damage afterwards.

Leaving the case solely in claims would delay the team able to restore access. Closing the claim entirely would lose a separate obligation.

A generated task built around this sequence teaches evidence-driven revision: preserve the original issue, recognise the newly actionable dependency and update ownership without erasing unfinished work.