Centralized or Local Referral Coordinators? Design the Operating Model
Choose centralized, local or hybrid referral coordination using a task decision worksheet, accepted handoffs and a responsibility map with real coverage.
Design the division of work before choosing tools
Referral coordination involves several administrative actions: receiving a request, gathering required information, routing work, arranging contact and recording its state. Different organizations may assign those actions differently. Document your current process before choosing a new location for the work.
AHRQ's workflow assessment toolkit addresses health IT's effects on administrative and clinical workflows. That supports examining the work around a tool. The task matrix and pilot proposed here are our own editorial methods.
This guide covers responsibility rather than headcount. Use the referral coordinator staffing model for capacity planning and multi-site referral automation evaluation for platform questions.
Compare three designs without assuming a winner
Centralized coordination assigns defined work from several sites to a shared function. The design can aim for pooled coverage and common reporting, but those benefits need actual staffing, usable routing and access to site-specific information. A central queue does not have to mean every worker handles every referral.
Local coordination assigns defined work to a site or department. It can preserve direct access to local contacts and context, while still using shared standards, cross-site backups and common reporting. Local ownership does not inherently mean an isolated spreadsheet or no absence coverage.
Hybrid coordination divides tasks or coverage between shared and local teams. It can address different needs, but adds boundaries to manage. Evaluate the added handoffs against the needs they serve.
For each option, identify the intended benefit and the condition required to obtain it. "Central backup" is only a plan until the backup has the authority, access and capacity to accept the work.
Use the task decision worksheet
Complete the worksheet with the people who perform the work. The examples identify questions, not default owners.
| Task | Knowledge to confirm | Authority or access to confirm | Coverage and handoff question |
|---|---|---|---|
| Receive and identify the request | Channels and local document conventions | Approved worklist and matching process | Who handles unmatched or misrouted items? |
| Check administrative completeness | Current receiving-practice requirements | Permission to request missing information | Who follows up while an item remains incomplete? |
| Route to an approved destination | Organization's established routing instructions | Which role can apply or override them? | Where do ambiguous requests go? |
| Arrange scheduling | Site calendars, constraints and contact process | Scheduling and exception permissions | Can another team cover the same actions? |
| Contact patient or receiving office | Prior contacts and current next action | Approved communication workflow | How are repeated contacts prevented? |
| Track status and documents | Meaning and source of each status | Record updates and document access | Who acts when the state is unknown? |
| Record administrative completion | Agreed endpoint and supporting evidence | Authorized completion or correction | Who covers unresolved or reopened work? |
Add columns for the proposed primary team, backup, retained local work and unresolved evidence. Where a task depends on local knowledge, first ask whether that knowledge can be documented and maintained. Where it depends on authority, ask who holds that authority. A preference list alone does not authorize clinical specialist selection or scheduling overrides.
Do not decide the model by counting "local" and "central" answers. A single required permission or missing backup may constrain the design more than several routine tasks. Inspect the important requirements before comparing convenience.
Make every handoff an accepted transfer
For each change of owner, define the trigger, required context, receiving role, acceptance record and next action. Specify who retains responsibility while acceptance is pending. If a queue is team-owned, identify the on-duty accountable role and the process for claiming individual actions.
Set the review interval and escalation route through the organization's existing process. This article does not define clinical follow-up deadlines. Keep the original request time and prior contact history visible when work moves, so reassignment does not make an old item look new.
Test a handoff when the recipient is absent or cannot act. The alternate path may be another local team, a shared coverage function or a designated lead. Its suitability depends on actual capability, not its position on the organization chart.
Bring the task worksheet and one unresolved handoff to a Linear Health demo to inspect the proposed worklist and assignment evidence.
Turn the decision into a responsibility map
This synthetic example illustrates a possible division for a multi-site practice. It is not a recommended universal arrangement or a customer deployment.
| Administrative task | Primary role | Backup role | Escalation owner | Acceptance evidence |
|---|---|---|---|---|
| Intake within the agreed scope | Shared intake coordinator | Cross-trained intake coordinator | Intake lead | Request accepted in covered queue |
| Apply documented routing instructions | Assigned routing coordinator | Authorized covering coordinator | Designated routing lead | Destination recorded or ambiguity assigned |
| Scheduling within approved rules | Assigned site scheduler | Authorized covering scheduler | Site scheduling lead | Action claimed and result recorded |
| Follow up on unknown status | Assigned follow-up coordinator | Coverage coordinator | Workflow lead | Open request and next check visible |
| Resolve administrative exception | Role authorized for that exception | Designated authorized backup | Accountable operations lead | Decision or remaining question recorded |
| Record agreed completion | Current action owner | Covering action owner | Workflow lead | Endpoint evidence and remaining work |
Review access and capacity for every backup. Include exceptions that require a separate clinical or compliance decision as a handoff to the authorized role, without assigning that judgment to a coordinator through this table.
The Operational AI Evaluation Kit asks for escalation paths and ownership of unresolved work. Apply that evidence question to the responsibility map itself: can the named person find, accept and act on the item?
Pilot the design and inspect retained work
Choose a bounded scope, such as one covered site and referral workflow. Before changing live ownership, rehearse representative synthetic cases: a normal handoff, missing administrative information, an absent recipient and a task that must return to its original team.
For an approved operational pilot, record the included population and what changed. Track referrals entering the scope, accepted handoffs, stalled transfers, repeated actions, unresolved items and the agreed administrative endpoint. Report raw counts and relevant denominators. Keep staff effort and work retained outside the pilot visible.
Review the event histories with both teams. If a handoff stalls, determine whether the issue is access, instructions, authority, capacity or a different cause. Do not infer that all local or central ownership is ineffective from one failure.
Decide whether to retain, adjust or expand the design using the pre-agreed requirements. A clean volume report is insufficient if unresolved work has no owner. Document changes to the responsibility map and verify coverage for the next scope.
Use the evaluation kit for broader vendor evidence questions and the referral coordination software overview for context. Schedule a working review with the map to discuss the specific actions a proposed workflow would support.
Frequently asked questions
Is centralized coordination always more efficient?
Does local ownership mean there is no backup?
What work must stay local?
How does a hybrid avoid gaps between teams?
When should the pilot expand?
Sources
Sources accessed November 6, 2026.
Linear Health publishes educational articles about operational AI for healthcare.