Referral Team Coverage: A Handover Plan for Leave and Staff Changes

This proposed operations method covers planned leave, unexpected absence and staff departure. It does not prescribe clinical deadlines or replace the organization's access and escalation procedures.

Separate coverage from headcount

Staffing asks how much capacity the referral team needs. Coverage asks who can perform a particular action when its usual owner is unavailable. A team can have adequate total capacity and still lack access to one person's unresolved work.

For broader planning, see hiring a referral coordinator and the referral coordinator staffing model. This guide focuses on continuity of specific actions.

AHRQ's workflow assessment toolkit addresses administrative workflow around health IT. The handover sheet and readiness questions here are original editorial tools within that scope, not an AHRQ handover standard.

Find open work and record what is uncertain

For planned leave, the coordinator and covering lead review the normal worklist together. For unexpected absence, an authorized manager or delegate rebuilds the list from shared records and approved access. Do not depend on obtaining the absent person's credentials or memory.

Include actions waiting to be performed, requests awaiting replies, callbacks promised, unresolved matching or document issues, and recurring queue-review duties. Check relevant shared inboxes, transmission logs and task views. Record where each item was found and what remains unverified.

Look for work outside the normal queue through approved organizational procedures. If a contact or verbal commitment is not documented, preserve that uncertainty and assign someone to verify it. Do not convert an incomplete recollection into a confirmed promise.

Choose a snapshot time. Any new request, reply or automated action after that time needs an explicit route into the coverage process.

Prepare the handover sheet

Keep the sheet in an approved internal location and use references to the underlying records rather than creating a second patient narrative. The template is one row per open action, because one referral may contain several independently owned actions.

Preserve the original receipt time and any existing commitments. A reassignment should not make old work appear newly received. Keep completed actions distinct from actions with uncertain results so the replacement does not repeat a send simply because its outcome is unclear.

Verify that the replacement can take over

Have the receiving person open the relevant worklist and a representative action. Confirm they can see the context, identify the next step and perform only the actions their role permits. Check whether their current workload can accommodate the assignment and who covers them in turn.

A shared team queue can be a valid receiving point when it has clear duty coverage, action-claim rules and escalation. A mailbox with no defined accountable role is not enough. Record the receiving person or duty lead's acceptance through the supported process.

If acceptance is blocked by access, authority or capacity, keep an accountable covering lead on the action and resolve the gap. Do not silently release the original assignment into an unowned state. For an unexpected absence, use the organization's immediate coverage and escalation process rather than waiting for the absent coordinator to confirm.

For exceptions, transfer what was tried, the last confirmed result and the unresolved question. Share contact context without inventing priority shortcuts or promising a faster clinical response. To inspect open-action ownership and acceptance evidence, book a demo with a synthetic handover.

Track changes while coverage is active

The snapshot starts the handover; it is not the live queue. Define who accepts new referrals, callbacks, later documents and recurring duties during the absence. Reconcile queued automated work before staff repeat the same action.

Keep a change record linked to the action: completed, still open, reassigned, newly discovered or requiring clarification. A new discovery is a prompt to investigate the visibility gap, not proof that one person failed.

Synthetic coverage example

A planned-leave snapshot contains 41 open actions: 30 routine actions, 8 documented exceptions and 3 commitments requiring verification. The receiving coordinator accepts the routine actions after checking access and capacity. The covering lead accepts the exceptions and assigns verification of the three uncertain commitments.

During coverage, a callback arrives for an action missing from the snapshot. The lead records it as newly discovered, establishes its current state and assigns its next action. A later document changes an existing action; that update is recorded against the same action rather than counted as a new referral.

The numbers illustrate 41=30+8+3. They are not a customer result, typical workload or staffing recommendation. The useful output is a current owner and next action, not a perfect-looking original sheet.

Reconcile a return or permanent reassignment

When the original coordinator returns, review the live worklist and change record together. If the person has left permanently, perform the same reconciliation with the successor and accountable lead. Do not assume every item should return to its former owner.

For each remaining action, confirm:

1. The current result and evidence, including any unresolved uncertainty.
2. New documents, contacts or commitments received during coverage.
3. Pending automated actions or retries that could conflict with staff activity.
4. The next authorized action and its existing review or due time.
5. The owner and backup accepting responsibility now.

Keep original and newly discovered actions distinguishable for learning, while maintaining one current operational source of truth. Review gaps in shared records, access and capacity. Set review timing through the organization's process rather than assuming a universal two-day return meeting.

Test coverage readiness before an absence

The Operational AI Evaluation Kit asks for evidence of exception ownership and observable outcomes. Use that approach for a coverage rehearsal, while recognizing that a successful sample does not prove every item is covered.

Use the results to improve everyday records and coverage instructions. A routine shared contact register and current next-action information may be more useful than a longer handover form. Review referral coordination software for broader workflow context.

Bring a synthetic unexpected-absence scenario to a working demo. Ask to see a replacement find, accept and progress the action, including an uncertain prior result and a later callback.

Frequently asked questions

Sources

Sources accessed November 5, 2026.

• AHRQ, Workflow Assessment for Health IT Toolkit.
• Linear Health, Operational AI Evaluation Kit.