How do you track housing referrals and follow-up?

What is this housing referral tracker for?

This worksheet organizes staff follow-up on a housing-related connection without treating the referral itself as a completed housing outcome.

Use it when a worker helps a participant explore or contact a receiving service and needs to keep track of the next action. The tracker can support a conversation about current options, an unresolved response, or a change in the participant’s preferences. It is an original Smores Health planning tool, not an official government form.

HUD Exchange’s housing-search guidance recommends individualized planning that clarifies responsibilities and tracks progress. The worksheet applies that broad idea to referral follow-up. The source concerns a specific voucher program; the example fields here are suggested operational prompts rather than mandatory requirements for all housing programs.^[1]

Keep the worksheet in your organization’s approved system. It does not replace required housing data entry, a clinical record, an eligibility assessment, or your program’s information-sharing process. During training, use fictional information and ask a supervisor which fields are useful, unnecessary, or missing for your actual work.

What fields belong in a blank housing referral tracker?

Capture the minimum information needed to understand the participant’s choice, the current result, and who will carry out the next step.

Copy these prompts into your approved form and adapt the language to your service model. Avoid duplicating names, sensitive identifiers, or lengthy histories when a record reference is sufficient. Decide whether the referral is associated with a person, a household, or another approved program record. Do not guess when different systems use different identifiers.

Repeat the receiving-service and follow-up fields when the participant explores several options. Keep the results separate. One responsive service should not make a second unanswered referral look complete. If your system uses a single row per referral, define how staff link it to the relevant participant and preserve updates without overwriting the history.

How should your program define referral statuses?

Use a small set of statuses that describe observable events and keep staff uncertainty visible.

Agree on definitions before using statuses in a report. “Connection confirmed” could mean attending an intake appointment; it should not silently mean housing obtained. If your team needs to report applications, offers, move-ins, or later stability, define those events separately and record their evidence. A status name should not carry several incompatible meanings.

Avoid using a single unsuccessful category for no response, service unavailability, participant choice, and an eligibility decision made elsewhere. These situations call for different follow-up. Keep the reason understandable and respectful. If a receiving agency communicates a decision, record the source and date without implying that your worker made that decision.

How do you use the tracker during everyday work?

Agree on the purpose, make the connection through the approved process, record what actually happened, and assign the next action.

• Discuss the option and the participant’s preferred next step.
• Confirm the receiving service’s contact route using an appropriate current source.
• Follow your organization’s approved process for information sharing.
• Record the completed inquiry or referral with the date and responsible worker.
• Document the response, including when no response is known.
• Agree on follow-up and identify who covers the work during an absence.
• Review the result with the participant and update the next action or closure reason.

Record the actual event rather than the intended result. If a worker left a message, say that a message was left. If a receiving service confirmed an appointment, identify the appointment and how the information was learned. If the participant later reports attending, distinguish that report from direct confirmation by the receiving service.

At the end of the contact, another authorized worker should be able to find the purpose, latest known response, next action, owner, and review date. If they must reconstruct those details from several long notes, consider whether the tracker or workflow needs a clearer current summary. Keep the full history where your approved record process requires it.

What does a completed housing referral log look like?

The fictional example below illustrates an unanswered inquiry, a later response, and a participant’s choice without claiming a housing placement.

Participant B asks a community navigator for help exploring a housing support service. They want to understand the intake process before deciding whether to pursue it. They prefer a telephone call after lunch. The navigator agrees to check the contact route and make an inquiry within the program’s approved information-sharing process.

On October 15, the receiving service responds with instructions for requesting an intake appointment. The covering worker records who provided the information and when. The participant wants to review those instructions before deciding. The worker records that choice and agrees on a later contact. The referral has progressed, but the record still does not show an attended appointment or housing obtained.

If the participant later decides not to pursue the service, close that referral with the actual reason and ask whether another option is wanted. Do not rewrite the earlier entries as though the participant had declined from the beginning. A useful log explains how the decision developed and what, if anything, remains open.

How often should workers follow up on a housing referral?

Set follow-up according to the participant’s preferences, the receiving service’s instructions, the situation, and your program’s established process.

There is no universal follow-up interval in this worksheet. Record the agreed date and the reason when timing matters. If a service provides a response window, identify that source. If circumstances change, update the plan with an explanation rather than allowing an old date to look like a missed obligation indefinitely.

For an unanswered inquiry, consider what the next useful action actually is. It may be checking the approved contact route, asking the participant whether they want another option, or discussing the matter with a supervisor. Repeated identical contacts without a decision about next steps can create activity records without moving the work forward.

Use your organization’s established urgent-response process when immediate safety or service needs arise. Do not rely on a routine tracker review to manage an urgent situation. Keep the worksheet’s role clear: it organizes ordinary referral follow-up and the facts needed for the next authorized worker to continue.

How should a supervisor handle coverage and handoffs?

Identify the new responsible worker, communicate the open action, and confirm that the worker can access the relevant context.

A handoff should answer a small set of questions: what does the participant want, what happened most recently, what is still unknown, what happens next, and when? Include contact preferences and any relevant sharing boundaries. Avoid moving unrelated sensitive details into a handoff message simply because they appear elsewhere in the record.

Ask the covering worker to describe the next action back to the supervisor or through the approved workflow. If the assignment cannot be accepted, identify another owner. A task label that changes without someone understanding the work is not enough to establish continuity. Record the handoff in the appropriate system so the original worker can understand what happened on return.

When several programs serve the participant, clarify who owns this particular referral. One team’s involvement does not automatically transfer responsibility from another. Keep the arrangement visible and resolve duplicate follow-up through the program’s coordination process. The goal is clear responsibility, not more messages.

What belongs in the service note versus the referral tracker?

Use the service note for the work actually performed and the tracker for the current referral result and next action.

A note can describe the completed conversation or coordination activity, the relevant response, and what was agreed. The tracker should make the current status and follow-up easy to find. Keep them consistent, but do not copy an entire narrative into every status update. Repetition can make it harder to identify the latest decision.

If the note reveals new information that changes the next action, update the tracker through the approved process. If the information is uncertain, preserve that uncertainty. Do not record a planned appointment as attended or a future application as submitted. Each event should be represented when it happens and with the appropriate evidence source.

For training, give staff two fictional notes: one with a completed call and one with an unsuccessful attempt. Ask them to update the tracker and explain which fields changed. This exercise can uncover ambiguous status definitions before those ambiguities appear in program reports.

How should staff handle information shared with receiving services?

Use your organization’s approved sharing process and ask the responsible reviewer to resolve uncertainty before information is disclosed.

HUD’s coordinated entry guide addresses information sharing and data privacy as part of system management. That is a reason to coordinate with the responsible local system owner when the referral touches those processes. This worksheet does not determine permission to disclose information or replace a required authorization or agreement.^[2]

Record a reference to the approved sharing decision or process where appropriate. Keep the information sent tied to the purpose of the referral. A question about intake availability may not require the same information as a formal referral. The responsible reviewer should determine the permitted scope for your situation.

Use fictional information in training, product demonstrations, and public examples. Do not put participant details into this webpage or an unsecured copy of the worksheet. If staff need a portable working document, have the organization specify how it is stored, accessed, updated, and returned to the official record.

How can a supervisor report referral activity accurately?

Define what counts, use the appropriate dates, and show unresolved results alongside confirmed events.

Test the report with a few fictional records before relying on it. Include one person with two referrals, one unanswered inquiry, one declined option, and one confirmed appointment. Calculate the expected totals independently. If your system produces a different answer, review the definitions and dates rather than changing records merely to make totals match.

A referral log can show activity and known results. It cannot by itself prove that the program caused housing stability or that every person received the service. Explain the limits when presenting results. A report that names uncertainty is more useful for follow-up than one that hides it behind an apparently complete success rate.

What should a supervisor check before using the tracker?

Check clarity, consistency, participant choice, evidence, responsibility, and the connection between the current record and the underlying work.

• Can another authorized worker identify the next action and its owner?
• Is the status consistent with the recorded event and evidence?
• Are the participant’s preferences and decisions represented accurately?
• Are unknown results preserved instead of guessed?
• Are separate referrals and outcomes kept distinct?
• Does the follow-up date reflect the current plan?
• Is information stored and shared through the approved process?

Review a small sample with staff and discuss disagreements. If two workers choose different statuses for the same fictional event, improve the definition or training. Do not add more categories automatically. A smaller set with clear meanings may be easier to use and report than a long list of overlapping choices.

Decide who owns future changes to the template and how staff will learn about them. Preserve the meaning of earlier records when labels change. If a new definition affects a report, document that change with the reporting owner rather than silently comparing periods that use different rules.

When should you move referral follow-up into software?

Consider software when separate files make it difficult to maintain one current action, clear responsibility, and reliable reporting.

Look for practical problems: conflicting copies, a worker’s private reminder list, unresolved actions during absence, or repeated manual reconstruction at reporting time. Use a fictional example of that problem to evaluate a system. A new tool is worthwhile only if staff can understand how it changes the work and what they will still maintain elsewhere.

Smores Health’s community services overview describes coordination, documentation, staff workflows, and reporting. Bring this blank tracker to a 20-minute walkthrough and ask how your program’s referral process would fit. Confirm configuration, included capabilities, and specialized housing requirements before deciding. The worksheet is not a promise of a preinstalled form or automatic import.^[3]

Frequently asked questions

Sources and product pages

Sources support the specific guidance cited above. Program guidance is not a universal requirement. Product pages describe capabilities to verify against your organization’s needs.

1. Supporting Households Through the Housing Search Process: HUD Exchange. Emergency Housing Voucher technical assistance. Reviewed October 9, 2026. Used for planning context, not as a universal program rule.
2. Coordinated Entry Management and Data Guide: U.S. Department of Housing and Urban Development. Reviewed October 9, 2026. Local system and program requirements still need confirmation.
3. Community services workflows in Smores Health: Smores Health. Discuss the available configuration and specialized requirements in a walkthrough.