What could a generated referral handover contain when the receiving team returns it?

A referral administrator prepares REF-7316 for a specialist booking team. The generated referral includes a requested service, a preferred location and supporting administration notes. Its status changes from preparation to submitted when the administrator sends it to the booking queue.

A booking coordinator finds that the required booking authority is absent. The coordinator returns the referral with reason code `AUTHORITY_MISSING`. The referral moves to correction required, and the booking slot remains unallocated. An intake administrator attaches the authority record and resubmits the referral for another review.

A release can contain the original referral, the submission event, the return notice, the added authority record and the resubmission link. Each submission should remain distinguishable so that the correction does not erase the reason the earlier attempt failed.

This teaches recovery from a legitimate receiving-team refusal. A task pack could ask a model to select the corrective action or explain why the returned referral should not be treated as cancelled. A reseller can offer the sequence as an administrative workflow product, with scope confined to referral processing rather than clinical judgement.