Pathfinders for Hope · Operation Iron Gate Vallejo Pilot

What Is Operation Iron Gate?

Operation Iron Gate is a confirmed handoff referral system operated through the Pathfinders for Hope Vallejo Pilot. It follows a person from the moment a referral is made to a documented outcome, so that the sending organization, the receiving organization, and the person all know what actually happened. It works alongside the systems an organization already uses. It is in development for a Vallejo pilot and is not open to public intake.

The problem Operation Iron Gate was built to address

In most homeless services workflows, a referral is treated as finished the moment it leaves the sending organization. The record says the referral was made. It does not say whether anyone answered, whether the person arrived, or whether the person is now standing outside a closed door with a phone number that no longer works.

That gap is not a paperwork problem. It is the point at which a person stops being anyone's responsibility. Two organizations can both act in good faith, both document their part correctly, and still lose the person between them, because neither one owns the space in the middle.

The central rule of Operation Iron Gate is that a referral being sent is not treated as proof that a connection happened. The outcome has to be known. Until it is known, the referral is open and someone is still accountable for it.

How does Operation Iron Gate improve referral accountability between organizations?

Operation Iron Gate improves referral accountability by creating one visible handoff record between the organization sending the referral and the organization receiving it. The record does not treat sent as complete. It shows whether the referral was acknowledged, who owns the next action, whether the person connected with the service, and why the referral could not proceed when no connection occurred.

The receiving organization confirms receipt
Responsibility transfers between named roles
Receipt, acceptance, connection, and service outcome remain separate
Silence stays visible as unresolved instead of being converted into completion
A referral that does not connect produces a documented reason and a named next action

This creates accountability for the handoff without replacing HMIS, local housing intake and assessment, or the professional judgment of participating organizations.

How Operation Iron Gate works

Operation Iron Gate records a referral as a six-stage sequence rather than a single event. Each stage has to resolve before the record is considered closed.

Referral Made. The sending organization records the destination, the reason, the person's consent, and the named role responsible for the next step.
Referral Received. The receiving organization confirms it has the referral. An unacknowledged referral stays visible instead of disappearing into a sent folder.
Handoff. Responsibility transfers explicitly. Both organizations can see who currently owns the next action, and neither can quietly assume the other has it.
Connection. The record captures whether the person actually reached the service, not whether an appointment was offered.
Documented Outcome. The result is recorded as what it was — connected, declined, ineligible, no capacity, unable to contact, or still unresolved. An unanswered message is never converted into a completed service.
Next Action. If the outcome was not a connection, the record does not end. It routes to a next authorized step so the person does not exit the system by default.

The six operating principles

Six principles govern how the program is designed. They are stated here so an organization can hold the program to them.

Confirmed Handoff. A handoff is complete when the receiving organization confirms it, not when the sender transmits it.
No Dead Ends. A referral that does not connect generates a next action rather than an ending.
Works Alongside Existing HMIS. Operation Iron Gate is designed to sit beside the systems of record an organization already operates, not to replace them.
Organizational Data Sovereignty. Participating organizations keep their own data, can export it, and can leave.
Non-Displacement. Joining is not intended to require an organization to abandon its existing tools, workflows, or funder reporting obligations.
Iron Gate Access Credential. A designed component intended to give a person a usable identity reference when they lack government identification, so that a missing document does not become a locked door.

Who Operation Iron Gate is designed for

Operation Iron Gate is built for organizations, not for individual service seekers. The people it is designed to be used by are the ones who make, receive, coordinate, manage, or oversee referrals:

Executive directors and program directors at homeless services nonprofits
Continuum of Care coordinators and CoC lead agency leadership
City, county, and state human services administrators
Government technology and data leadership
Healthcare and behavioral health administrators managing discharge and community handoffs

If you are looking for services for yourself or someone you are helping right now, Operation Iron Gate is not the right starting point. Public intake is not open. See homeless resources in Vallejo instead.

How Operation Iron Gate differs from an HMIS

A Homeless Management Information System is a system of record. It documents what an organization did, and it exists in large part to satisfy reporting obligations. It answers the question what happened? after the fact, within one organization's boundary.

Operation Iron Gate is scoped to a narrower question and a different moment: did the handoff between two organizations actually complete, and if not, who owns the next step right now? It is designed to hold the space between organizations, which is precisely the space a single organization's system of record cannot see.

The distinction matters for a practical reason. An organization does not have to choose. Operation Iron Gate is designed to work alongside an existing HMIS, and the design intent is that it must not create a second place to type the same client information.

Operation Iron Gate is not a local housing intake and assessment system. It does not assess, prioritize, or rank people for housing, and it is not a replacement for, alternative to, or competitor of a Continuum of Care's local housing intake and assessment process. It runs alongside those systems.

Why Operation Iron Gate was created

The program came out of watching the same failure repeat: a person is referred, everyone involved documents their part correctly, and the person still ends up nowhere. Nobody did anything wrong. The system simply had no owner for the gap.

Pathfinders for Hope was founded to close that gap rather than to add another intake point. The reasoning behind it is set out in the founder's story.

What Operation Iron Gate does not do

Stating the limits plainly is part of the design.

It does not guarantee that a person will be housed, served, or accepted by any organization.
It does not guarantee same-day issuance of any credential unless that has been formally approved for a given deployment.
It does not guarantee that no one is ever lost. It is designed to make it visible when someone is.
It does not replace an HMIS, a local housing intake and assessment system, or an organization's clinical or case management judgment.
It has not produced field results. There are none to report, and none are claimed anywhere on this site.

Current status

Operation Iron Gate is in development. The referral accountability model, the six-stage record, and the operating principles described above are the design specification. They are not a description of a running production system, and the Vallejo pilot has not launched. Pathfinders for Hope is recruiting the first cohort of participating organizations.

Organizations that want to be part of that cohort can review what participation involves.

Frequently asked questions

What is Operation Iron Gate?

How does Operation Iron Gate work?

It records a referral as a six-stage sequence: Referral Made, Referral Received, Handoff, Connection, Documented Outcome, and Next Action. Each stage has to resolve before the record is considered closed, and an outcome that is not a connection routes to a next authorized step instead of ending.

Who is Operation Iron Gate designed for?

It is designed for organizations that make, receive, coordinate, manage, or oversee referrals — nonprofit executive and program directors, Continuum of Care coordinators, city and county human services administrators, government technology leadership, and healthcare and behavioral health administrators. It is not a public intake service.

How is Operation Iron Gate different from HMIS?

An HMIS is a system of record that documents what an organization did, largely for reporting obligations. Operation Iron Gate is scoped to the handoff between organizations and to whether it actually completed. It is designed to work alongside an existing HMIS rather than replace it.

Is Operation Iron Gate a local housing intake and assessment system?

No. It does not assess, prioritize, or rank people for housing, and it is not a replacement for, alternative to, or competitor of a Continuum of Care's local housing intake and assessment process. It is designed to run alongside those systems.

Is Operation Iron Gate available now?

No. Operation Iron Gate is in development and the Vallejo pilot has not launched. Public intake is not open, no field results exist, and none are claimed. Pathfinders for Hope is recruiting the first cohort of participating organizations.

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.