Operation Iron Gate and your HMIS
Your Homeless Management Information System Cannot Confirm Every Handoff
HMIS records. It can’t confirm arrival.
A confirmed handoff shows whether the receiving organization accepted a referral, explains a denial, or escalates when a person is left waiting. Operation Iron Gate is being built to add that layer alongside your HMIS.
Short answer · Updated 5 Oct 2026
What is HMIS, and what does HMIS stand for?
HMIS stands for Homeless Management Information System. It is the database a local Continuum of Care uses to record who receives homeless services and what help they got, and programs funded by HUD homeless assistance grants must enter data in it.
It documents services, not whether a referral actually reached someone. Operation Iron Gate, which Pathfinders for Hope is developing for a North Bay Pilot, is designed to close that gap.
HMIS and coordinated entry: coordinated entry is the process a Continuum of Care uses to assess people and match them to available homeless assistance programs, in priority order. HMIS is where those assessments and referrals are usually recorded. Neither one confirms that the receiving program accepted the person or that they arrived. See how coordinated entry works in Solano County.
Your HMIS stays
The system of record.
Operation Iron Gate asks one narrow question: did the receiving organization confirm the person arrived? Each organization keeps its own data, policies, and decisions.
In Solano County, Resource Connect Solano enrolls people in HMIS as part of coordinated entry.
The handoff
Your homeless management information system reports it happened. That is not knowing they arrived.
| Stage | Your HMIS records | Operation Iron Gate confirms |
|---|---|---|
| Referral | Referral recorded | Tracked to a named receiver |
| Receipt | Exit reason logged | Confirmed by the receiving organization |
| Arrival | Service entered | Confirmed — or the case reopens |
| Timing | Report generated after the fact | The gap is visible the day it opens |
| Closing | The record closes | The case stays open until arrival is confirmed |
Illustrative.
The first question
Is this more data entry? No.
The system is scoped to the handoff — the moment a person moves from you to someone else. If a field lives in your HMIS, it is not re-collected here.
Stays in your HMIS
- Client demographics
- Program enrollment
- Internal case notes
- Exit reason
Iron Gate confirms three things
- Who received the referral
- Whether the person arrived
- When it was confirmed
No case is lost.A case cannot silently stop, and a case cannot close without an outcome.
The partner session
We bring the map. You tell us where it breaks.
Before anything is signed or built: one working session with your team, your referral route drawn end to end.
Your route, drawn
Where a referral leaves you, who it goes to, and where it stops being visible.
The three fields
Who received it. Whether the person arrived. When it was confirmed.
What stays yours
Your HMIS stays the system of record. Export your data in a standard format any time.
The rules, in writing
Twelve barrier codes. Ten legal-basis codes. Corrections added as records, never edits.
What changes, what doesn’t
Nothing is decommissioned. Your data stays yours.
If your team tracks handoffs on paper or in a spreadsheet because the HMIS can’t, that is the gap this fills. Every time a file is opened, that is recorded.
- Your organization
- The staff working with that person see the full file.
- Everyone else with a login
- No access.
- The public view
- Counts and rates only. No names, ever.
- You, any time
- A full export, in a standard format.
Common questions
Questions directors ask first.
Can referral tracking software work alongside an existing HMIS?
Yes. An HMIS is the system of record. A referral tracking layer covers only the space between organizations: who received a referral, whether the person arrived, and what happens if nobody confirms. It works when the system of record is named and unchanged, the layer collects only fields the HMIS does not hold, and it never becomes a second place to type client data. Using Clarity HMIS in Solano County? See how a confirmed handoff works alongside Clarity HMIS. For the broader model, see closed-loop referrals and referral tracking software for homeless services.
How can agencies track referral status without replacing their system of record?
By tracking the handoff rather than the client. A referral’s status is a fact about an event between two organizations: sent, acknowledged by a named receiver, arrived or not, next action. It does not belong in the client file. Spreadsheets, email threads, and automations record that something was sent; none of them hold a case open until someone confirms an arrival. See how agencies confirm a homeless services referral.
Will our staff have to enter client data twice?
No. The system is scoped to the moment of handoff, not to the intake fields your HMIS already collects.
Our CoC selected our HMIS. Does joining conflict with that?
No. Joining does not change your CoC relationship, your HMIS contract, or your reporting obligations. An HMIS is required infrastructure under HUD’s HMIS Data Standards, and none of that changes.
Will this route our funding through Pathfinders for Hope?
No. Joining does not route your funding through us and does not put your contracts in our name. A confirmed handoff is a number you use in your own reporting.
What if our HMIS already tracks referral outcomes?
Then compare them. If your HMIS reliably produces receiving-side confirmation of arrival, you may not need this. Most do not, which is why the spreadsheet exists. The U.S. Interagency Council on Homelessness treats coordination between providers as a core function, but no HMIS is asked to enforce it across organizations.
How should a referral be closed?
Not because it was sent. A confirmed handoff separates a completed connection from an unverified attempt. The record shows whether the receiving organization accepted, could not accept, could not reach the person, or needs more information, and who owns the next step. It stays visible until there is a documented result or a clear reason to escalate.
What information should a receiving organization see?
Only what that specific handoff needs. The goal is not to copy a person’s full record into another tool. It is to make the referral clear enough to act on, then document the outcome without creating a second case file. Each organization keeps its own records and reporting duties.
What makes outcome reporting useful?
Showing where a handoff succeeds, where it breaks, and why, not just how many referrals were created. Telling an accepted connection from a denial, a missed contact, or an unresolved wait shows which barriers repeat. The standard is simple: no person should disappear between a referral and a result.
The decision
See the whole scope in writing.
Read what joining involves before you decide anything. The system of record stays authoritative while a limited handoff status supports follow-through.
- Pilot status
- Not running yet. Projected launch January 2027.
- Intake by phone
- (707) 205-7588
