Pathfinders for Hope · Operation Iron Gate Vallejo Pilot

Homeless Services Referral Resource Hub

This homeless services referral resource hub is for organizations that send, receive, or oversee referrals. It brings together practical planning guides on receipt confirmation, follow-up ownership, sensitive information, and outcome reporting. The guides support discussion; they do not establish service availability, legal compliance, or participation in the pilot.

What this homeless services referral resource hub covers

This hub is organized around the questions that appear after one organization sends a person to another. A resource directory can show that an organization exists. It cannot prove that the referral reached the responsible team, that contact occurred, that the service was available, or that somebody still owns the next action.

The guides below explain how organizations can build a referral record that shows:

  • Where the referral was sent and what information the person authorized the partners to share
  • Whether the receiving organization acknowledged the referral
  • Who owns follow up and when the status must be checked again
  • Whether the person connected, could not connect, declined, or remains unresolved
  • Why a referral could not proceed and what authorized next action follows

Together, these guides distinguish referral activity from referral accountability. They are written for cross organizational planning and can be used alongside existing HMIS, clinical records, and local agency workflows.

Choose the question your team needs to answer

Understand the model behind the guides

The guides above are operational. These three explain the model they come from.

A starting point for different organizations

Nonprofits and NGOs: start with the missed-handoff and partnership guides. Hospitals and recovery providers: review follow-up responsibilities alongside your own clinical and admission policies. City, county, and social services teams: start with the tracking and measurement guides. Domestic violence agencies: begin with the sensitive-referral guide and qualified local advice before considering a shared workflow.

These groups have different responsibilities. A common planning resource does not imply identical service models, unrestricted information exchange, or a requirement to use the same software.

Use a guide in a working session

Choose one real workflow problem, but discuss it using fictional or appropriately non-identifying information. Read the relevant guide, agree on the meaning of each status, assign unresolved policy questions to the right people, and decide which small process change to test. Do not put confidential case details into a public resource comment, contact form, or analytics tool.

Use the homeless services referral resource hub with your existing system of record

The homeless services referral resource hub is not a replacement database. Start with the systems, privacy rules, and reporting requirements your organization is already authorized to use. HUD describes an HMIS as the local information system used to collect client level data and data on the provision of housing and services. The guides on this site focus on the narrower handoff between organizations and the unanswered question that follows: what happened after the referral left the sender?

Choose one referral workflow before changing an entire network. Map the moment the referral is sent, the moment the receiving organization acknowledges it, the decision that follows, and the point where responsibility changes hands. Use fictional or properly protected information during planning. Confirm which record remains authoritative and which limited handoff facts may be shared.

Test whether the workflow closes the loop

Ask who is allowed to confirm receipt. Ask who is allowed to mark the referral complete. Ask what happens when nobody responds. Ask whether a denial requires a reason. Ask whether unresolved referrals remain visible. If the answers depend on one staff member remembering to send an email, the workflow is not yet accountable.

AHRQ presents care coordination and referral as a process that requires communication between the referring source and the receiving provider. Its care coordination guidance is written for healthcare settings, not as a universal homeless services standard. It still demonstrates why referral communication must continue after transmission.

Measure outcomes instead of activity

Count referrals sent, but do not mistake that number for proof of connection. Also measure confirmed receipt, time waiting for acknowledgment, connection outcome, unresolved referrals beyond the agreed response window, and the reasons a referral could not proceed. Keep unknown outcomes visible. A clean report that hides unanswered referrals is not a reliable account of what happened.

When evaluating a closed loop referral system, use the buyer criteria in the closed loop referral guide. The strongest test is simple: who confirms completion, and what happens when nobody answers?

Direct answers for referral-accountability questions

These short answers point to the detailed guides in this resource hub. They are planning guidance for organizations. They do not establish a partnership, service availability, or permission to exchange personal information.

What should nonprofits and community service organizations look for in a closed-loop referral system?

Look for separate proof of transmission, receipt, the next agreed action, and the final outcome. The system should keep an unresolved handoff visible with a named owner. A sent status alone is not a closed loop. See the closed-loop referral requirements.

How can organizations know what happened after a referral was made?

The receiving organization must provide an authorized update. Record receipt, review, the next step, connection, an inability to proceed, or an unresolved status as separate facts. This allows a team to see what is known without assuming the person reached help. See what happens after a referral.

What is the difference between sending a referral and confirming a handoff?

Sending proves that the referring organization acted. A confirmed handoff proves that the receiving side acknowledged responsibility or confirmed the agreed connection. The gap between those facts is where referral accountability begins. See the five conditions of referral accountability.

Can referral tracking work alongside an existing HMIS or other system of record?

Yes. A referral workflow can be limited to the handoff facts that organizations need to manage a transfer while each organization retains its authorized client record in its existing system. It is designed to work alongside, not replace, an HMIS or other system of record. See how Operation Iron Gate fits alongside HMIS.

How can organizations track referral status between organizations?

Use a minimum shared handoff record with the destination, authorized information, receipt status, next owner, next check date, and documented outcome. Partners should agree on what each status means before using it with live cases. See the partnership workflow guide.

What is the best closed-loop referral platform for a community-service partnership?

There is no universal best platform. The right choice depends on the organizations’ workflow, consent rules, system-of-record boundaries, receiving-team participation, and ability to keep unresolved handoffs visible. Use the closed-loop referral platform evaluation guide to compare those requirements before selecting a tool.

How to use the homeless services referral resource hub as a working desk

The homeless services referral resource hub is not a directory and it is not a case-management system. Use it to prepare a partner discussion around one real workflow question: what needs to be visible after one organization refers a person to another?

Start with the guide that matches the gap your team can name. Use the homeless services referral resource hub to compare status definitions, identify the next owner, and separate what is known from what is assumed. Then open the linked detailed guide before deciding whether a local policy, privacy review, or partner agreement is needed.

Return to the homeless services referral resource hub when the question changes. It connects the practical guides so a team can move from a missed receipt to the broader handoff model, partnership design, consent boundaries, and outcome review without treating any one page as a promise of service or a replacement for an existing system.

About these resources

The checklists and hypothetical examples are Pathfinders for Hope planning materials, not published pilot results. Refer to editorial standards and sources for scope, attribution, and corrections. Use the partner resource sharing kit to share accurate descriptions without implying a partnership or endorsement.

For the program context, see who Operation Iron Gate is for and the closed-loop referral overview. If you are seeking immediate local help rather than an organizational partnership, visit Get Help for the current status and resource direction.

Prepared by Pathfinders for Hope. Updated September 5, 2026. Resource scope and sources.

Join the Vallejo Pilot

Tell us how your organization can participate. Pathfinders for Hope will review your application and contact you using the information you provide.

Enter your organization’s full name.
Optional.
Select the option that best describes your organization.
Where does your organization primarily serve?
Briefly describe the services, programs, or resources your organization can offer.
How would you like to participate?
Select every role that applies.
Your Name
The primary person we should contact.
Your role within the organization.
We will use this email to respond to your request.
Optional.
Tell us what you want to strengthen, solve, or contribute.