Seven better ways to prevent people lost between referrals

Organizations that want to prevent people lost between referrals need a shared definition of what a completed handoff means. The goal is not constant surveillance or unrestricted data sharing. It is a limited, person-respecting process that makes the next authorized action, responsible role, and unresolved barriers visible.

1. Begin with the person’s goal

Explain the proposed destination and next step without promising acceptance or a result. Ask which contact method is appropriate and whether the person wants the referral to proceed. Use the organization’s language-access and accessibility processes. A workflow cannot prevent people lost between referrals if the person does not understand where the information is going or what will happen next.

2. Verify the destination before sending

Check that the organization handles the request type, that the intake route is current, and that basic scope requirements are understood. Separate a public information number from a program’s referral channel. If capacity changes frequently, agree on how the receiver will communicate that status. This check reduces misrouting without treating capacity as guaranteed.

3. Define a receipt response

Partners should agree on a small set of meaningful receipt statuses: received, needs authorized clarification, wrong destination, unable to review, or no response by the cutoff. Receipt is not acceptance, and acceptance is not a completed service. Keeping these states separate helps prevent people lost between referrals while protecting the accuracy of public reporting.

4. Assign an owner and a backup

Give each next action to a role and identify what happens during leave, shift changes, or staff turnover. Use an approved team queue or handover procedure when appropriate. The owner checks the agreed milestone; the owner does not control the person’s choices or guarantee another organization’s action. Managers should test the backup process with fictional examples before relying on it.

5. Set a review point, not a silent deadline

A review date prompts the responsible role to check what is known. It is not proof of failure and should not automatically close the record. Use distinct categories for pending, unknown, unavailable, person declined, and completed as locally defined. Report unresolved volume alongside completion rates so a fast closure process does not hide stalled handoffs.

6. Match the response to the barrier

A wrong address needs a corrected route. Missing authorized information needs clarification. No capacity may require discussion of another option. An unreachable person may require review of the agreed contact plan. Avoid copying a full case file to multiple organizations in the hope that one responds. Follow permission, privacy, and recordkeeping rules for every additional contact.

7. Close with evidence and a next explanation

Record the specific event that was verified, who was authorized to verify it, and the date. “Appointment offered,” “assessment attended,” and “service started” are different outcomes. If the outcome cannot be confirmed, say unknown. If the person declines an option, respect the decision and document only what the organization’s procedures require. Accurate closure is central to efforts to prevent people lost between referrals.

A no-dead-end review table

• Purpose: What exact next contact did the person authorize?
• Destination: Was the current program and route verified?
• Receipt: Did an authorized receiving role acknowledge the request?
• Ownership: Who checks the next step, and who is the backup?
• Timing: What reporting window and review date apply?
• Barrier: What prevented progress, using a neutral category?
• Outcome: What milestone was confirmed, declined, pending, or unknown?
• Next action: What will the participating team do now?

Keep the record as limited as the workflow permits. Decide which system is authoritative, who may access it, how corrections are made, and what information may be shared in aggregate. The Nashville Office of Homeless Services HMIS overview is one official example of how a local community describes its information system. It is context, not a template that every community must copy.

How to review unresolved referrals without blame

Choose a small, authorized sample and ask where the handoff stopped. Was the destination incorrect? Was the reply unclear? Did the person have an accessible contact route? Was capacity unavailable? Did the owner or backup miss the review point? Focus on the system condition and the next improvement. Do not publish identifiable cases or turn the review into a ranking of people or providers.

Track one workflow change at a time when possible. For example, a team might update a referral directory, clarify a receipt status, or improve a shift-change handover. Compare similar cohorts before and after the change, keeping pending and unknown outcomes visible. A difference may justify investigation, but it does not prove causation without an appropriate evaluation.

Local safety and scope boundaries

The process to prevent people lost between referrals must fit local law, privacy requirements, funder rules, service capacity, and organizational policy. HUD’s Continuum of Care program information provides federal program background, while local participating organizations define their operating agreements. No checklist can guarantee acceptance, placement, or housing.

Operation Iron Gate is a pilot under development for organizational partners, not an open public intake service. For an immediate life-threatening emergency, call 911. For local resource navigation, register on GATEHOUSE. These pathways should remain prominent wherever referral-planning content may reach a person seeking urgent help.