Pathfinders for Hope · Operation Iron Gate Vallejo Pilot

How Do Agencies Confirm a Homeless Services Referral Was Received?

Agencies confirm a homeless services referral by obtaining an authorized acknowledgment from the receiving organization. A successful transmission is not the same as a human response, an accepted referral, or a delivered service. Keep those milestones separate so the sending team knows what still needs attention.

How can nonprofits confirm that a referral was received and acted on?

Nonprofits can confirm receipt only through an acknowledgment from the authorized receiving team, not through a sent status or delivery notice. They confirm action separately by recording whether the referral is under review, whether contact was attempted, whether the next step was accepted, or whether the organization was unable to proceed and why. Receipt and action are different facts. Both should remain visible until the outcome and next owner are known.

How to confirm a homeless services referral with clear statuses

Use a short status list that partners can interpret consistently. The following is a proposed working vocabulary, not a required reporting standard:

Sent: the sender transmitted the referral using an approved channel.
Received: the destination acknowledged that the referral reached the responsible team.
Under review: the receiver is checking the request, eligibility, or capacity.
Accepted for a next step: the receiver agreed to an assessment, appointment, or other specified action. This does not necessarily mean admission or placement.
Unable to proceed: the receiver supplied an authorized reason or next-step instruction.
Outcome confirmed: an authorized source verified what actually happened. State which outcome rather than writing only “complete.”

Build a receipt check into the handoff

Before sending, confirm the destination, the permitted information, and the receiving team's current process. Ask which channel produces a usable acknowledgment and who handles a missing response. Agree on a response window that reflects the service's hours and urgency; do not assume every partner has round-the-clock staffing.

A proposed receipt record can contain a locally approved reference, the destination team, time sent, time acknowledged, current status, follow-up owner, and next check date. Record only information your organization is authorized to hold. Keep confidential case details out of email subject lines, public forms, analytics, and general-purpose shared notes.

An automated acknowledgment can establish technical delivery. If it does not show that the responsible team can act, leave the referral awaiting review. Avoid converting every email delivery receipt into an accepted referral.

When nobody responds

Use the agreed backup contact, check for a wrong destination or unavailable service, and record the follow-up attempt. If the person wants another option, discuss an authorized alternative instead of silently forwarding the same information to more organizations. An unresolved referral should retain an owner until the agreed next action is completed or the person chooses to stop.

Urgent needs belong in the organization's established urgent-response process, not in an unmonitored referral queue. A referral tracking workflow does not replace emergency response or professional judgment.

Example: received, but not yet accepted

Illustrative example, not a Pathfinders for Hope case: a nonprofit sends a request to a partner intake team. The team acknowledges receipt and asks for an eligibility clarification that the sender is permitted to provide. The record moves to “under review,” with the sender responsible for the clarification. It does not move to “service delivered” simply because the receiver replied.

What evidence confirms each referral status?

To confirm a homeless services referral, connect every status to evidence from an authorized source. A label without a source can create false confidence. The record should show who supplied the update, when it was supplied, and what the update actually proves.

Sent: use a transmission record showing the destination and time. This proves the referral left the sender. It does not prove anyone reviewed it.
Received: use an acknowledgment from the receiving organization or responsible team. An automatic delivery notice may prove technical delivery, but not human review.
Under review: record the receiving role, the date review began, and the next expected update. This prevents a waiting referral from becoming invisible.
Accepted for a next step: record the action the receiver agreed to take, such as an assessment or appointment. Acceptance is not proof that the person arrived or received a service.
Connected: use authorized confirmation that contact or the agreed service step actually occurred. The sender should not assume connection from an appointment offer or a successful transmission.
Unable to proceed: record the reason, the person or role responsible for follow up, and the next authorized option. The referral should not close into silence.

Organizations that confirm a homeless services referral should keep these facts separate because each one answers a different question. Receipt proves the referral arrived. Review proves someone is evaluating it. Acceptance establishes an intended next step. Connection shows that the handoff reached the person. The outcome shows what actually happened.

Use the minimum information needed for the handoff. Do not copy an entire client record into a second tool merely to prove status. The organization that holds the authoritative record should keep control of its data, while the shared referral record contains only the information required to confirm the transfer and manage the next action.

How to use this guide

Test the status definitions with a fictional referral before adopting them. Ask both teams to describe what each label allows them to conclude. If their answers differ, revise the labels before collecting performance numbers.

For the broader workflow, see closed-loop referrals and preventing missed handoffs. For measurement, use the referral outcomes guide.

Referral confirmation checklist for sending organizations

Use this checklist before treating a homeless services referral as complete. It is a planning tool for teams that send referrals. It does not replace the receiving organization’s intake rules, consent requirements, or urgent-response process.

Name the destination. Confirm the specific organization, program, or team expected to receive the referral. A general inbox may be a delivery channel, not the responsible decision-maker.
Confirm permission and minimum information. Share only the information needed for the agreed handoff and only through an authorized channel. Do not use a status workflow to collect more personal information than the receiving team needs.
Record what was sent. Note the date, time, destination, sending role, and locally approved reference. This proves the transmission step. It does not prove review, acceptance, or service.
Set the next check. Identify who will check for acknowledgment and when. The timing should match the organization’s hours, the person’s circumstances, and the urgency of the request.
Separate acknowledgement from outcome. A response can confirm receipt, request clarification, or say the organization cannot proceed. Record the exact status instead of collapsing every reply into “complete.”
Keep an owner until the next action is known. If there is no response, use the agreed follow-up route. If the person chooses another option, document the authorized next step rather than letting the original referral disappear.

What a clear referral record should answer

A referral record should make it possible for an authorized staff member to answer a short set of operational questions without searching through email threads. What was requested? Which organization or team was named? When was it sent? Who acknowledged it? What is the current status? Who owns the next action? When will the record be checked again?

Those questions help a team see the difference between activity and accountability. Sending is activity. Acknowledgment is evidence of receipt. Review is evidence that the receiving side is considering the request. An agreed appointment or assessment is a next step. A confirmed outcome describes what actually happened. Each fact has a different owner and a different level of certainty.

When a team cannot answer one of those questions, it does not mean the person did anything wrong or that a partner failed. It means the handoff still needs a defined next action. The responsible response may be to follow up, correct the destination, wait for the agreed response window, offer another authorized option, or close the record only after the person’s decision and the reason are documented.

Source and scope

AHRQ discusses coordinated referral processes in opioid-use-disorder care. Our status vocabulary and example above are proposed planning tools for organizational discussion, not AHRQ standards or an endorsement. Read AHRQ's care-coordination guidance.

Frequently asked question

Does a delivery receipt prove someone received help?

No. It can show transmission or receipt, but acceptance, an appointment, and actual service delivery require separate authorized confirmation.

What proves that a referral was acted on?

To confirm a homeless services referral was acted on, look for a recorded action. That action may be a review, a contact attempt, an appointment, an acceptance, a denial, or a service outcome. The receiving organization should supply the update. The record should show the date and the next owner. If no action is known, the referral remains unresolved.

Who should confirm the handoff?

The receiving organization should confirm a homeless services referral after it arrives. The sender can prove that the referral was transmitted. The sender cannot prove what happened after it arrived. Confirmation from the receiving side creates an independent record of the handoff.

Confirming receipt is one of five conditions in the wider standard. See what referral accountability requires and what Operation Iron Gate is.

Operation Iron Gate Vallejo Pilot

Pathfinders for Hope is developing the pilot with organizational partners. Public intake is not open, and no service or placement is guaranteed. Discuss the pilot with Pathfinders for Hope or browse the resource hub.

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