Closed-loop referral
Where referrals break down between organizations
Most organizations can tell you how many referrals they sent last quarter. Far fewer can tell you how many resulted in a service actually delivered. A referral crosses five points before it is complete, four of them break quietly, and most tracking never gets past the second one.
This page walks all five, with a question you can ask about each one to find out which is failing in your own workflow.
Sent is not delivered
Sent is an action your organization took. It is in your system because you did it, it is easy to count, it is easy to report, and it proves effort. Delivered is an outcome a person received. It lives in someone else's system, or in no system at all. It is hard to count, rarely reported, and it is the only one that proves the work mattered.
Every dollar of funding justification, every outcome a board asks about, and every hour of staff time spent chasing confirmations sits in the space between those two words. That space has a shape, and it is not one gap. It is five.
A referral is not complete when it is sent. It is complete when someone can show what was delivered, by whom, and when.
Most tracking starts at point 2 and stops at point 2. The referral was sent. Whether anything reached the person is a separate question that nobody owns.
Need identification
The need is noticed but never recorded in a form another organization can act on.
What it looks like
- A community health worker hears about a utility shutoff during a home visit and handles it informally, by calling someone she knows.
- The need lives in a visit note, a text message, or a person's memory.
- Nobody outside that one conversation ever knows the need existed, including the program that could have met it.
What to do about it
Capture the need at the moment it is identified, in a record more than one person can see, including the needs you cannot meet. The unmet ones feel like failures to log and they are the most valuable data you will ever collect, because they are what justifies the next program, the next partner, and the next grant.
Is this the one in your workflow?
Could you produce a list of every need your staff identified in the last 30 days, and what each one was?
Routing to the right partner
The referral goes somewhere, but not to a person who has agreed to receive it.
What it looks like
- It is emailed to a general inbox, or to a staff member who left in March.
- The sender picks a partner from a printed list nobody has updated in two years.
- Two organizations receive the same referral and each assumes the other is handling it.
What to do about it
For every partner, write down three things: who receives referrals, how long they have to respond, and what comes back when the service is done. That is three sentences, not a contract negotiation. Name a backup recipient for each one, because the single most common cause of a referral disappearing is that one person was out.
Is this the one in your workflow?
For your three most-used partners, can you name the person who receives your referrals and say what happens when that person is out?
Partner acceptance
The referral arrives and is never acknowledged, so nobody owns it.
What it looks like
- Sent on a Friday, opened the following Wednesday, acted on never.
- The partner is at capacity but has no way to say so back up the chain.
- Silence is read as acceptance by the sender and as a decline by the receiver, and both of them are certain they are right.
What to do about it
Require an acknowledgment inside an agreed window, and make silence trigger something rather than mean something. A partner who declines a referral within a day is more useful than one who accepts it and goes quiet for three weeks, because a decline can be re-routed and silence cannot.
Is this the one in your workflow?
How long does it take you to find out that a partner did not pick up a referral, and who tells you?
Service delivery
The partner accepted, and the service still did not reach the person.
What it looks like
- The client could not be reached at the number on the form.
- Eligibility failed at intake and no alternative was offered.
- The program ran out of funds two weeks into the quarter and nobody upstream was told.
What to do about it
A referral that ends without a service should produce a reason, not silence. Reasons are the difference between an anecdote and a pattern. Three months of reasons will tell you which partner has a capacity problem, which intake form is collecting bad phone numbers, and which eligibility rule is quietly excluding the population you built the program for.
Is this the one in your workflow?
When a service is not delivered, does anyone come back to you, or does the referral simply end there?
Delivery confirmation and reporting
The service was delivered and nothing came back to say so.
What it looks like
- The partner knows what happened. Your organization does not. Your funder asks you.
- Confirmation exists as a phone call somebody made once and did not write down.
- Quarterly reporting becomes a reconstruction project instead of a query.
What to do about it
Confirmation has to arrive as part of the partner's own work rather than as a favor to yours, because favors do not survive staff turnover. Underneath that is a language problem worth solving first. The sending organization thinks closed means sent, the receiving partner thinks it means accepted, and the funder means the person got the service. Write the definition down once and hold every partner to it.
Is this the one in your workflow?
To report outcomes for this quarter, would you be querying a record or making phone calls?
Start at the earliest pain point. Not the loudest one.
Reporting is usually where it hurts most, and it is usually not where the problem is. Find the earliest of the five you cannot document, and start there.
The most painful break is almost always downstream of the real one. Reporting feels broken because acceptance was never captured.
Better reporting layered on top of a broken routing step produces confident reporting about the wrong population.
Organizations that try to fix all five at once fix none of them. The five are sequential for a reason.
Find out which one is yours
The Closed-Loop Referral Readiness Checklist turns all five into six questions you can score against whatever you run today, whether that is a platform, a module inside your record system, or a shared spreadsheet. One page, fillable, no sign-up.
Get the readiness checklist
