How can one late operational task affect several business teams?

A depot coordinator owns delivery confirmation task `TASK-1846` for shipment `SHIP-7312`. The driver has returned, but the signed receipt has not reached the shipment record. The billing team cannot release invoice `INV-2954` until that evidence is attached.

When the task passes its policy deadline, its state changes from awaiting evidence to follow-up required. The operations assistant must contact the depot coordinator through the internal task queue. Sending a payment reminder to the customer would be premature: the invoice has not been released and no payment obligation is late.

The coordinator then reports that the receipt is with the scanning team. Responsibility for retrieving the document changes, while the depot coordinator remains accountable for completing the original task. The assistant must preserve that distinction when recording the handover.

A generated scenario can teach a model to separate a late prerequisite from its downstream commercial consequence. The training signal comes from identifying the blocked dependency, directing follow-up to the person able to remove it and retaining accountability until the evidence arrives.