Jump to a section
What does housing navigation software need to manage?
Start by separating support for the participant from management of properties, available units, landlords, and specialized housing-program records.
Housing navigation can involve several related jobs. Staff may help someone understand options, coordinate appointments, follow up with a receiving service, or track agreed actions. Another team may recruit landlords, maintain listings, administer assistance, or manage housing inventory. Write down which jobs your organization performs and which system currently owns each one.
HUD Exchange’s housing-search technical assistance distinguishes household support from unit identification and landlord engagement, while noting that some staffing models combine those roles. Use that distinction as a planning prompt. The source concerns Emergency Housing Voucher assistance; it does not establish one national workflow for every housing navigation program.[1]
This guide focuses on evaluating community support workflows and identifying additional requirements. It does not establish eligibility, recommend a housing decision for any person, or promise that software can locate an available unit. Treat referrals, appointments, applications, offers, and move-ins as separate events whose meaning your team must define.
How is navigation software different from HMIS or property software?
Identify the records and reporting responsibilities of each system before deciding whether a new tool can replace any part of the current workflow.
| Job | What to test | Question to resolve |
|---|---|---|
| Participant navigation | Goals, contacts, assignments, referrals, and follow-up | Who owns the participant’s next step? |
| Landlord and unit operations | Listings, availability, landlord relationships, and property details | Does the proposed system actually include these specialized capabilities? |
| Homeless-services information | Required data, local reporting workflows, and approved exchanges | What does the local Homeless Management Information System lead require? |
| Housing assistance administration | Eligibility, payments, inspections, or other program-specific processes | Which agency or system owns each decision and transaction? |
| Property management | Leases, rent, maintenance, and occupancy | Is a separate property system still required? |
The Homeless Management Information System is commonly abbreviated HMIS. HUD’s coordinated entry guide discusses data systems alongside system-level management and information sharing. That makes it important to involve the responsible local system owner when a purchase affects those workflows. A general case-management demonstration is not evidence of compatibility with your local housing data system.[2]
Ask for the precise interface, export, reporting specification, or approval your organization needs. Do not accept “we integrate” without identifying what moves, in which direction, how often, and how errors are resolved. Smores Health’s community services workflows should be evaluated separately from any requirement for HMIS integration, landlord inventory, subsidy administration, or property management. Those capabilities are not established by this guide.
How should you map the housing navigation workflow?
Map the participant’s journey as decisions and completed actions, with an owner and a source for each important update.
| Stage | Staff question | Evidence to inspect |
|---|---|---|
| First contact | What support does the participant want, and how should we contact them? | Preferences and the agreed next action |
| Planning | Which priority will the participant and worker address first? | A specific step with responsibility and a review date |
| Referral or inquiry | Which service was contacted, and for what purpose? | Destination, date, owner, and known response |
| Follow-up | What changed, and what remains unknown? | Dated updates and the information source |
| Handoff | Who continues the work if the original worker is unavailable? | Coverage and access to relevant context |
| Progress review | What happened, and what does the participant want next? | Confirmed facts, participant report, and next decision |
Choose one route through the map and one exception. For example, a participant wants to explore a housing service, the receiving program does not respond, and the assigned worker is absent when follow-up is due. Ask the vendor to show how the covering worker finds the current action without reading every historical note. Then ask how the report represents the unresolved referral.
The map should reflect your program’s actual responsibilities. If your team only helps connect people to services, do not build a purchasing checklist around running rental payments or allocating units. If your team does perform those functions, give them their own requirements and acceptance criteria. This keeps the evaluation focused without hiding essential gaps.
What should you look for in housing referral tracking?
Look for a clear distinction between an inquiry, a referral sent, a response received, and a result that has actually been confirmed.
Ask the vendor to demonstrate an unresolved referral. Where is the next check-in date? Who owns it? What can staff record when the participant chooses another option or the receiving program has a waitlist? A closed record should not automatically become a successful placement in reporting. Your team needs definitions that staff can apply consistently.
Test a fictional participant who explores two options. One receiving service responds, while the other has not. The participant prefers to wait for more information. The record should preserve that choice and the known status of each option. Ask whether the report counts participants, referrals, receiving organizations, or responses. These measures answer different questions.
Use the referral worksheet linked below to prepare a fictional demonstration. Keep operational follow-up separate from decisions made by a housing provider, public agency, or participant. Software can organize evidence about those decisions; a referral status itself does not create an entitlement, approval, or housing placement.
How should participant and household records be evaluated?
Confirm how the system represents the people involved, their relationships, and the information each authorized worker needs to perform the assigned task.
Some housing programs work with individuals, while others use household-level records for specific processes. Write down the unit of service and reporting for your program before viewing software. If a household record is required, ask for a demonstration of that exact structure. Do not assume an individual participant profile can substitute for a household data model.
Use fictional examples to test a change in household composition, a returning participant, and two records that may refer to the same person. Ask how the supported process preserves history and resolves uncertainty. Similar names are not enough to justify merging records. Identify the responsible reviewer for corrections and unclear matches.
Keep contact preferences and relevant context current through your approved process. Test whether a covering worker can find the agreed next action without gaining inappropriate access to unrelated information. The goal is a usable record with clear ownership, not a collection of every detail someone might someday want to know.
How can you verify housing navigation reports?
Test the report against defined measures and a small dataset whose expected results your team already knows.
| Question | Definition to agree |
|---|---|
| How many people received navigation? | Which completed activity qualifies and how repeat contacts are counted |
| How many referrals were made? | Whether the measure counts referral records or unique participants |
| Which referrals need follow-up? | Statuses, next-action dates, and responsibility |
| What progress was reported? | The event, date, evidence source, and remaining uncertainty |
| What remains unknown? | How missing responses and incomplete follow-up are represented |
| What must be submitted elsewhere? | The required format, owner, and accepted submission process |
Include a participant with several contacts, a referral with no response, and a later correction. Ask the vendor to identify each underlying record in the output. Decide which date controls reporting and whether later updates change an earlier period. A chart that cannot be explained against known records is not ready to support your reporting decisions.
Do not treat the number of referrals as the number of people housed. Similarly, a move-in date does not by itself establish sustained housing stability. Choose measures and follow-up periods appropriate to your program and explain their limits. This guide does not claim that Smores Health verifies housing placements independently or submits a particular housing-program report.
What should a housing navigation software demo show?
Use a fictional participant journey to inspect daily work, coverage, reporting, and the specialized requirements that may need another system.
- Describe whether your team provides participant support, landlord engagement, unit management, or a combination.
- Bring one blank referral form and one reporting question.
- Record an agreed housing-related next step and identify the responsible worker.
- Follow an inquiry through a response, a waitlist, or an unknown result.
- Show how another authorized worker continues the open action.
- Inspect how the activity appears in reporting without calling a referral a placement.
- List every required external system and obtain a specific answer about compatibility.
Have the staff who perform the work observe the demonstration. Ask them where they would look next and what information is missing. Give the reporting owner time to check the definitions. Record whether each requirement was demonstrated, proposed as configuration, dependent on another service, or left unresolved.
Smores Health’s community services page describes participant coordination, documentation, staff workflows, and reporting. A walkthrough can help you evaluate those functions for your program. Bring the specialized housing requirements as explicit questions rather than treating the platform’s general capabilities as proof that they are included.[3]
How should housing programs compare software cost?
Compare written quotes for the same users, records, workflows, reports, integrations, and implementation responsibilities.
Ask what drives the recurring charge and what changes as the program grows. Include supervisors, temporary staff, multiple locations, and any proposed partner access. Clarify whether configuration, training, data transfer, support, and additional storage are included. Request a written quote that identifies the included services and any additional charges.
Document the cost of maintaining required systems alongside the new purchase. If staff still enter information into a housing network’s system, include that work in the operating plan. Ask whether any proposed exchange has been demonstrated for the specific systems and fields you need. Do not budget for an assumed integration as though it were already available.
| Category | Question |
|---|---|
| Configuration | Which forms, fields, roles, and reports will be set up? |
| Data migration | Which records, attachments, and relationships can be transferred and checked? |
| Training | Who is trained, on which tasks, and with what follow-up support? |
| Reporting | Which exact outputs are included and which require additional work? |
| Renewal | What terms or costs may change and what notice applies? |
| Exit | What usable exports and assistance are available when you leave? |
Which access and sharing questions belong in the review?
Have your responsible reviewer define who may see, change, export, and share each type of information before configuration is approved.
Map internal roles and external relationships separately. A receiving service may need a narrow referral message rather than access to every note. A covering worker may need current tasks but not the same administrative controls as a director. Ask the vendor to demonstrate those distinctions and identify any limits of the permission model.
Use the local system owner and qualified privacy reviewer to determine applicable requirements. Request current vendor security materials, data-return terms, incident contacts, and the relevant contractual commitments. A statement that a product is secure does not resolve a specific question about a sharing arrangement, export, or record category.
Keep your implementation decisions in writing: which information belongs in the system, which stays elsewhere, who approves access, and what happens when a worker leaves. Do not collect more information simply because a field exists. Evaluate whether the record serves a defined operational purpose and whether the staff responsible can maintain it accurately.
How do you move from evaluation to a practical launch?
Choose a bounded initial workflow, check migrated records, practice exceptions, and assign ownership for configuration and support.
Begin with the workflow that caused you to evaluate software. It may be referral follow-up or coordinating staff coverage. Define the acceptance checks before setup begins, including a known reporting result and a limited-access role. This gives both your team and the vendor a concrete definition of what must work.
Review a small authorized migration sample before moving more records. Check dates, relationships, attachments, and open actions, not just record counts. Identify uncertain duplicates and inconsistent statuses for review. Decide where staff enter new work during transition and how they report a missing or unclear record.
Train staff using fictional cases that include no response, a changed priority, and a covering worker. After launch, review the specific points where staff need extra help. Keep required external reporting processes in place until the responsible owner accepts any change. A software launch should make work understandable to the team, not simply create another place to maintain the same information.
Frequently asked questions
Does housing navigation software replace HMIS?
Do not assume so. Identify the requirements of your local Homeless Management Information System and consult its responsible owner. Confirm any specific interface, export, or reporting capability separately. This guide does not establish Smores Health as an HMIS replacement.
Does Smores Health manage landlords or available units?
This guide does not verify landlord inventory, unit availability, property management, or housing assistance administration. Discuss those requirements explicitly. Evaluate the documented community support workflows separately.
Can we track a referral without knowing its outcome?
Your process should preserve an unknown result, its follow-up owner, and the next action. Test how a proposed system represents uncertainty instead of treating every referral as successful.
How much does housing navigation software cost?
Request a written quote based on users, programs, configuration, migration, training, and required interfaces. Include the cost and staff effort of any systems that must remain in use.
Who should join the demonstration?
Include a frontline navigator, the workflow owner, and the person responsible for reporting. Bring a blank form and a fictional scenario. Ask the local system owner to help define any specialized housing data requirements beforehand.
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.
- 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.
- 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.
- Community services workflows in Smores Health: Smores Health. Discuss the available configuration and specialized requirements in a walkthrough.