Referral Coordinator Job Description, Interview Exercise and Onboarding Plan

Define the job before writing the advertisement

List the referral direction, locations, channels and work queues the role will support. A coordinator receiving referrals for a specialty practice has different responsibilities from one sending referrals from primary care. Use the referral coordination overview to map the work, then remove duties that belong to other roles.

Meet with the person currently doing the work or the staff covering it. Ask what consumes time, which decisions require escalation and what a useful handoff looks like. A job description assembled only from the desired future workflow can mislead applicants and leave the team unprepared.

O*NET's medical administrative occupation profile includes scheduling, records and communication activities. It is useful context, not a complete specification for your referral role. The template below is an original starting point to adapt with your organization.

State what automation currently handles and what it does not. A planned deployment is not an existing capability. If the coordinator must reconcile failed imports or monitor an exception queue, include that work rather than describing automation as the disappearance of administration.

Copyable referral coordinator job description

The following wording can be adapted for a real posting. Replace bracketed fields with factual details before sharing it with candidates.

Job title and reporting relationship

Referral Coordinator, [team or location]. Reports to [role]. Supports [inbound, outbound or both] referrals for [locations and services]. Works [schedule and location arrangement] with coverage provided by [team or backup role].

Role purpose

Maintain an accurate, actionable referral workflow from receipt or creation through the administrative steps assigned to this team. Keep the current status, next action and responsible person clear. Communicate with patients and partner offices using approved procedures, resolve administrative gaps within delegated authority and route clinical or policy questions to the designated responsible staff.

Core responsibilities

• Review incoming referral information using the organization's approved intake checklist, identifying missing or conflicting administrative details.
• Reconcile repeated transmissions with existing referral episodes and escalate uncertain matches rather than merging them without evidence.
• Maintain referral status, next-action dates and documentation in the designated system of record.
• Contact patients and referring or receiving offices through approved channels, respecting recorded preferences and workflow instructions.
• Coordinate scheduling tasks within approved rules and escalate requests that need a decision outside the role's authority.
• Track outstanding administrative requests, document responses and maintain ownership when work is handed to another team.
• Verify that expected documents are received and routed to the appropriate destination without interpreting their clinical content.
• Review assigned exception queues and report repeated process problems to the supervisor with examples.
• Participate in cross-training and keep operating references current when approved workflows change.

Decision authority and escalation

The coordinator may resolve administrative issues within documented procedures. Clinical priority, diagnosis, treatment, medical necessity, coverage interpretation and exceptions to policy belong to authorized staff. The coordinator records the question, supporting context, recipient and next follow-up step. Escalation does not end ownership of the administrative handoff.

Skills and qualifications

Ability to maintain accurate records across interruptions; clear written and spoken communication; careful handling of conflicting information; ability to learn the systems used by the team; and willingness to ask for guidance when a request falls outside approved instructions. Specify any required qualifications that apply to the role. Identify relevant experience as preferred where it can be taught, rather than inserting unsupported requirements copied from another posting.

Tools and working conditions

The team uses [actual EHR], [referral system], [communication tools] and [other required systems]. Current automated tasks include [verified tasks]. Manual duties include [remaining duties]. The role receives [training and support] and uses [documented backup arrangement]. State actual schedule expectations and any required coverage accurately.

Success measures

Success means accurate status records, clear next actions, usable handoffs, timely work under the team's approved operating targets and appropriate escalation. Measures are reviewed with workload, case mix, system availability and quality evidence. Task volume alone is not the performance standard.

Turn responsibilities into an interview scorecard

A posting becomes useful when interviewers can assess its requirements consistently. Choose a few job-related competencies and define what evidence would meet them. Do not score confidence, familiarity with your acronyms or storytelling polish as substitutes for the work.

Use the same core questions for every candidate. Ask for a past example, the person's role, the action taken and what evidence showed the result. Allow relevant examples from other administrative settings when prior healthcare experience is not a genuine requirement.

The patient access manager role provides context for responsibilities that should remain with the supervisor rather than drifting into a coordinator posting.

Run a short synthetic work exercise

Use fictional records with no patient information. Provide the same written workflow instructions and available tools to each candidate. The purpose is to observe how someone handles an administrative task, not to test whether they can guess your unpublished rules.

Hypothetical exercise: the candidate receives four referral records. One is a repeated transmission with a matching order identifier. One has conflicting contact details. One has a patient asking for a different appointment time. One contains a question the provided instructions assign to an authorized clinical reviewer.

Ask the candidate to produce a next-action log, a handoff note and one short patient-facing update. Do not ask them to rank clinical urgency. Give them the approved escalation route for the fourth record and evaluate whether they use it.

An example scoring method assigns zero to two points for each of five competencies in the table: zero for missing or unsupported handling, one for partial handling and two for a clear, documented action. The maximum is ten points. These are proposed interview anchors, not a validated assessment or universal pass score.

Have interviewers score independently before discussing. A candidate who writes “contact details conflict; verify against the designated source before outreach” demonstrates something different from one who simply chooses the newest number. Discuss the evidence behind the score rather than averaging away a serious gap in scope awareness.

Adapt the process with HR so the assessment reflects the role and the support candidates need. Do not use a timed typing competition to evaluate a job whose hardest moments require accuracy and a clear escalation.

Make onboarding a series of observed capabilities

Build the learning plan around the work rather than a calendar alone. A new hire should see a complete example, practice it with support and then demonstrate it independently. Record where assistance remains necessary.

The referral tracking guide supplies a state dictionary for training examples. Keep local configuration and authority rules in the practice's controlled references rather than expecting the article to replace them.

Make trainer time visible in the plan. If every experienced coordinator is already assigned a full queue, training may become a series of interruptions without a reliable feedback window. The turnover-cost ledger helps document that support effort without treating the new hire as a financial burden.

Before independent work, ask the learner to explain what they would do when the reference is unclear or the system is unavailable. Knowing the fallback and backup owner is part of the role, not an optional detail after training ends.

Revisit the role when the workflow changes

After a new intake channel, location or automation step is introduced, inspect which responsibilities moved and which exceptions appeared. Update the job description, operating instructions and performance measures together. Otherwise, the written role can become detached from the actual day.

Keep manual competence where it is needed for fallback or review. An automated step may still require someone who understands what a correct result looks like. Remove obsolete duties when they have disappeared, but do not imply that oversight is effortless.

Use staff input to assess interruptions and workload alongside throughput. The coordinator work-design review can support that conversation. A clear role requires both understandable responsibilities and the resources to perform them.

When you evaluate referral coordination automation, describe the intended division of work in the same terms as the job: inputs, decisions, actions, exceptions and ownership. That makes the hiring and technology plans coherent.

FAQ

Sources

• O*NET: Medical Secretaries and Administrative Assistants, occupational task context. The job template, exercise and scoring anchors above are original proposed tools.