Referral pipeline

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

One record needs a stable identity

Choose whether the pipeline unit is a person, household, requested service, or referral episode. Keep the raw source event, received time, source organization and person, requested service, original identifiers, and duplicate links.

Merge repeated calls, forms, faxes, and emails only under a documented identity rule. Preserve separate siblings, services, or episodes when they require independent decisions. An inflated pipeline can look like growth while representing duplicated work.

States should describe evidence and action

A practical pipeline may use:

• received and awaiting first review
• contact attempted through an approved channel
• reached and gathering purpose-needed information
• administrative review in progress
• clinical review pending with a qualified professional
• payer or financial route under verification
• access support in progress
• capacity hold or voluntary waitlist
• conditional offer issued
• referred elsewhere, withdrawn, declined, duplicate, or closed

Each state needs an entry rule, exit rule, owner, due date, age, evidence, and escalation path. Avoid a single “pending” bucket.

Decision authority stays outside the funnel score

Operations applies approved administrative criteria. Qualified clinicians decide clinical appropriateness. Payers decide product, network, benefit, and authorization states. Access owners coordinate effective communication and other supports. The person or authorized decision-maker chooses whether to continue.

Software can route tasks and flag conflicts. It should never decide clinical need, legal authority, coverage, or accommodation through a marketing score.

Every open referral needs a next action

Display age by current state and total age since receipt. Record the next action, owner, due date, last contact, preferred channel, and blocker. Use aging bands that match the workflow, then inspect the oldest individual records.

Publish monitored hours and emergency instructions on referral channels. Emergency, mandated-reporting, or protective-service triggers bypass the ordinary queue and follow current policy and law.

Access needs also require early action. Keep language, interpreter, AAC, sensory, mobility, reading, technology, and scheduling supports visible without treating them as adverse qualification facts.

Control referral-source relationships

Maintain a source register with relationship owner, contact, service population, current materials, commitments, value exchanged, review date, and complaint history. Reconcile source naming so “Pediatrics,” “Dr. Lee,” and the clinic's formal name do not create three sources.

The OIG General Compliance Program Guidance is voluntary and nonbinding. It offers a general framework for compliance risk assessment, training, reporting, auditing, and corrective action. Have qualified reviewers assess gifts, sponsorships, consulting, marketing services, discounts, ownership, and other value connected to referrals.

Protect pipeline information

Use role-based access and purpose-specific fields. Keep sensitive clinical, custody, authority, and payer documents in restricted locations instead of copying narratives into a broad sales queue. Define retention, export, vendor, messaging, and deletion controls.

Give referral partners only the status information they are authorized to receive. A referral relationship alone creates no permission to disclose protected or confidential information.

A fictional pipeline snapshot

Oakline ABA, a fictional practice, begins Monday with 36 unique open referrals. Ten await first review, eight are gathering information, six need payer verification, five are on a voluntary capacity waitlist, four have conditional offers, and three await family choice. The states total 36.

During the week, 12 new referrals enter and nine reach a terminal outcome: four conditional offers accepted, three appropriate external referrals, one withdrawal, and one duplicate closure. Ending open work is 36 + 12 - 9 = 39 unique referrals.

The practice reports point-in-time inventory, weekly inflow, terminal outflow, and aging separately. It does not call the 9 terminal outcomes a conversion rate because the week's outflow includes referrals from earlier cohorts.

Measure flow and experience

Useful measures include new unique referrals, age in state, oldest record, first-response timeliness, access actions completed, reviews due and completed, terminal outcomes, reopened records, corrections, and family-rated clarity.

For conversion rates, use locked received-date cohorts with full exposure windows. For workload, use point-in-time inventory and inflow or outflow. Mixing these denominators hides delays.

The SBA market-research guide encourages analysis of demand, location, market size, saturation, and pricing. Pipeline data shows demand reaching this practice under its current channels. It does not count unmet need elsewhere.

Review capacity before promoting volume

Compare referral flow with qualified review capacity, clinician availability, supervision, site, travel, access supports, payer paths, and working capital. Pause or redirect campaigns when the pipeline grows faster than responsible response.

Tell families the current status, likely next step, assumptions, and update date. Honest capacity communication can reduce conversion metrics while improving trust and navigation.