Pathfinders for Hope · Operation Iron Gate North Bay Pilot
What Is the Difference Between Sending a Referral and Confirming a Handoff?
Sending a referral proves one thing: information left your organization. Confirming a handoff proves the receiving organization got it, is responsible for it, and has named the next step or the reason it cannot proceed. A referral can be sent and still go nowhere. A confirmed handoff cannot quietly disappear, because the other side has put its answer on the record.
Sending a referral vs. confirming a handoff
The two are often counted as the same event. They are not. Each one answers a different question.
| Question | Sending a referral | Confirming a handoff |
|---|---|---|
| Who acts? | The sending organization | The receiving organization |
| What it proves | Information was transmitted | The right team has it and owns the next step |
| What it does not prove | That anyone read it, accepted it, or reached the person | That the service was delivered. That is a separate outcome. |
| When it counts as done | When the message leaves | When the receiver records receipt and a next step, or a reason it cannot proceed |
| If nothing comes back | Often nothing happens, and the referral still looks complete | The referral stays open, with an owner, until someone follows up |
Why the difference matters
When a sent referral is counted as a completed one, the gap between them is invisible. A person can be referred, never contacted, and never counted as lost. Reports then describe activity, meaning referrals made, instead of accountability, meaning handoffs that landed. Partners also lose the chance to fix the break, because no one knows where the handoff stopped.
Confirmation makes the break visible the day it happens: a referral that was never acknowledged, a program that was full, a phone number that did not work. Each of those is useful information. None of them shows up if the only record is “sent.”
What a confirmed handoff records
- Receipt: the responsible receiving team acknowledged the referral. An automatic delivery notice is not the same thing.
- A decision: accepted for a next step, or unable to proceed, with the reason.
- A next step and an owner: what happens next, who does it, and when the record will be checked again.
- The outcome, when it is known: what actually happened, supplied by an authorized source. This is a separate fact from receipt.
Is a warm handoff the same as a confirmed handoff?
Not quite. A warm handoff is a live introduction: staff connect the person directly to the next provider instead of handing over a phone number. It improves the odds that the person arrives. A confirmed handoff adds the record: the receiving organization says, on the record, that it has the referral and what happens next. The strongest practice uses both.
Example: sent, but not confirmed
Illustrative example, not a Pathfinders for Hope case: a hospital discharge planner emails a shelter referral on a Friday afternoon. The email is delivered. On Monday, nobody at the hospital knows whether the shelter saw it, and the person has already left. With a confirmed handoff, the shelter’s acknowledgment, or its absence, would have been visible on Friday, with a named person responsible for the next call.
How to move from sending to confirming
- Agree on what “received” means with each partner before live referrals start.
- Ask the receiving side to confirm, not the sender. A second note from the sender is not confirmation.
- Keep a named owner on every referral until a next step or a documented barrier is known.
- Report confirmed handoffs separately from referrals sent, so the gap between them can be seen and fixed.
For a full status vocabulary, see how agencies confirm a referral was received. For the wider model, see what a closed-loop referral is.
Where Operation Iron Gate fits
Operation Iron Gate is the referral-accountability model Pathfinders for Hope is preparing for a pilot in Vallejo and Solano County. It is built on this distinction: a referral is not finished when it is sent. It is finished when the receiving organization confirms it, or when a documented barrier is recorded. It is designed to work alongside each organization’s existing systems, including HMIS. The pilot is in development, public intake is not open, and the projected launch is January 2027.
See your role in the North Bay Pilot.
Source and scope
HUD’s Continuum of Care information provides federal program context for local homelessness response. AHRQ’s care-coordination guidance discusses coordinated referral processes in health care. The distinctions on this page are planning language for organizational discussion. They are not a federal standard, and they are not legal advice.
Frequently asked questions
What is the difference between sending a referral and confirming a handoff?
Sending a referral proves information left the sending organization. Confirming a handoff proves the receiving organization got it, owns it, and has named the next step or a reason it cannot proceed. Only the second tells the sender that the person has not been lost between organizations.
Who should confirm a handoff?
The receiving organization. The sender can prove the referral was transmitted, but it cannot prove what happened after it arrived. Confirmation from the receiving side is an independent record.
Does a confirmed handoff mean the person received a service?
No. Confirmation shows the handoff landed and has a next step. Whether the service happened is a separate outcome that the receiving organization records when it is known.
Prepared by Pathfinders for Hope. Updated September 29, 2026. Resource scope and sources.