Referral coordination defined by Marco Cardenas

What Is No-Dead-End Referral Coordination?

Referral coordination should not stop after a referral is sent. A referral is not a result. A person may get a resource name but never receive help. In many systems, no one notices until it is too late.

A No-Dead-End referral system is a referral coordination model that prevents silent failure. Every referral must reach one of three clear states: confirmed receipt, documented denial, or active escalation. No referral can remain unresolved without a required next action. If a referral is denied, the record must name the rule, policy, funding requirement, or law that applies.

Operation Iron Gate is designed to enforce this referral coordination standard during the Vallejo pilot. It does not replace Coordinated Entry or HMIS. It works alongside those systems to help make sure that what gets referred gets received.

A referral has three possible endings

Referral sent

01Confirmed receiptThe loop closes.

02Documented denialThe applicable basis is recorded.

03No recordThe person is lost, and nobody is told.

When a system records only that a referral was sent, the third outcome can remain invisible.

The rule

What No-Dead-End Referral Coordination Requires

A referral can close through one of two final outcomes: confirmed receipt or documented denial. Until one occurs, the referral must stay active and enter escalation when required.

Silent disappearance is not an allowed outcome.

No-Dead-End is a structural rule, not a feature toggle. It means:

Outcome gates

01Confirmed receiptAllowed

02Documented denialAllowed

03DisappearsBlocked

Confirmed receipt and documented denial are permitted outcomes. Silent disappearance is blocked. An unresolved referral stays active and enters escalation.

A referral cannot sit in an unresolved state indefinitely.

It must move toward confirmed receipt, documented denial, or active escalation.

If a referral stalls past a defined threshold, the system surfaces it.

The next action does not depend on someone requesting it.

Follow-up does not depend only on staff memory.

The workflow keeps the referral visible and records the required next action.

No dead ends. No one gets lost.

The mechanism

What Movement Authority Means

In this referral coordination model, movement authority advances a person’s case to the next required action. That may be another contact, another resource, or escalation. The process does not wait for a manual trigger that may never come.

A record shows what should happen. Movement authority keeps the next action visible, assigned, and time bound until the referral reaches a final outcome. See how each referral status is tracked.

What movement authority does

Day 0Referral sent
WaitingNo confirmation yet
ThresholdThe system surfaces it
Next actionRequired and assigned

The workflow keeps the follow-up requirement visible and assigns the next action.

The denial record

What a Coded Legal Basis for Denial Means

A denial without a recorded reason is not accountable. It becomes a dead end with paperwork.

In Operation Iron Gate, a coded legal basis means each denial must identify the applicable eligibility rule, program policy, funding requirement, or law. The reason is recorded at the time of denial. That creates an auditable record that can be reviewed, challenged, or corrected. It also protects the person and the organization by showing what rule was applied.

A denial with a coded basis

Decision: Denied
Applicable basis: Rule, policy, funding requirement, or law
Recorded: At the moment of denial
Reviewable: Yes. It can be challenged or corrected

Accepted

A denial without one

Decision: Denied
Applicable basis: Empty
Recorded: Nothing to record
Reviewable: No. No basis is available to review

Entry blocked

The design blocks a denial when no applicable basis has been recorded.

The evidence

Why This Matters

Chicago’s Continuum of Care documented a specific referral follow-through problem in its Permanent Supportive Housing process.

All Chicago, the Continuum of Care lead agency, reported that it had no mechanism for tracking how many referrals resulted in a person moving into housing. Working with Harvard Kennedy School’s Government Performance Lab, it ran a twelve-month pilot that changed how referrals were followed through. Clients in the pilot had a referral success rate 33 percentage points higher than the standard pathway and moved into housing 24 days faster. Harvard Kennedy School Government Performance Lab, 22 May 2025.

The Chicago pilot tested process changes, not Operation Iron Gate software. Its results show why active referral follow-through and accountability matter.

Operation Iron Gate is designed to address that same category of gap through tracking, accountability, and required next actions. It is built to work alongside the systems a Continuum of Care already uses, not replace them. See what participating organizations keep control of and confirm.

Chicago’s Continuum of Care · twelve-month pilot

Standard pathwayBaseline

Proactive engagement pilot+33 pts

Referral success rate ran 33 percentage points higher than the standard pathway, and clients moved into housing 24 days faster.

These are All Chicago’s results, not Operation Iron Gate’s. The Vallejo pilot has not launched and has no results to report.

The record

What a Responsible Referral Record Must Show

A no-dead-end process needs more than a sent timestamp. It needs a record people can understand. A supervisor, a partner, or the person seeking help should be able to see what happened without relying on memory, a mailbox, or a verbal update.

A responsible referral record should show

In referral coordination, the record should identify the service requested and the destination chosen. It should show when the handoff was initiated, who made it, and what information the receiving organization needed to act.

01Servicethe service requested and receiving organization
02Originwhen the handoff was initiated and who made it
03Ownershipthe current owner, status, next action, and due date
04Resolutionconfirmed receipt, documented denial, or active escalation
05Basisthe stated reason for a denial when it can be shared

A record that cannot answer all five is a sent message, not a referral record.

A complete record also shows the response.

Confirmed receipt

The receiving organization acknowledges the referral and accepts responsibility for its next step.

Documented denial

The record should capture the stated reason when it can be shared. That may be eligibility, capacity, service area, funding rules, or another documented limitation.

Active escalation

It should show each contact attempt, the partner or role responsible for follow-up, and the decision point that moves the referral forward.

If no response arrives, the record should not simply show that a message was sent. It should name the current owner, the next action, and when that action is due. That makes a stalled handoff visible before it becomes a silent loss.

If a provider declines the referral, the denial needs to be recorded plainly. A clear denial is not a dead end when it triggers a next step. It gives the person and the referring team an honest basis for a different option or an escalation.

The record also needs an escalation trail. That trail makes responsibility specific. It also helps partners identify where their process needs repair without turning a person’s situation into a blame exercise.

Not paperwork

This is not a call for unnecessary paperwork. It is a minimum accountability record for a high-stakes handoff. Documentation should be limited to what partners can lawfully and appropriately share. It should still show whether the referral was received, declined, or actively being resolved.

The Vallejo pilot

Operation Iron Gate is being built for the Vallejo pilot to make those handoff facts visible alongside existing HMIS and Coordinated Entry work. It does not replace those systems.

A referral is only complete when the outcome is known and the next responsibility is clear.

Common questions

Common Questions

What is no-dead-end referral coordination?

No-dead-end referral coordination prevents a referral from silently disappearing. A No-Dead-End referral system allows two final outcomes: confirmed receipt or documented denial. Until one occurs, the referral stays active and enters escalation when required.

What should organizations record after sending a homeless services referral?

Organizations should record whether the receiving organization acknowledged the referral, the current status, contact attempts, the applicable decision or denial basis, and the next action. A responsible record ends in confirmed receipt, documented denial, or active escalation.

What is movement authority in a referral tracking system?

Movement authority is the system rule that advances a case to its next required action, such as another contact, resource, or escalation. It keeps the follow-up visible, assigned, and time bound instead of relying only on staff memory.

What is a coded legal basis for denial?

A coded legal basis for denial is the recorded rule that supports a denial. Depending on the service, that basis may be an eligibility rule, program policy, funding requirement, or law. Recording it makes the decision auditable and reviewable.

Is this the same as the system my Continuum of Care already uses for intake and assessment?

No. The existing Coordinated Entry process and HMIS remain in place. Operation Iron Gate is designed to work alongside them by tracking what happens after a referral is made and whether the receiving organization confirms the handoff.

Why do homeless referrals often fail to connect people to the services they need?

Some systems record that a referral was sent without requiring a confirmed outcome. When follow-up depends entirely on manual action, a stalled referral can remain unresolved without being surfaced.

What is the difference between sending a referral and confirming a handoff?

Sending a referral records that information left one organization. Confirming a handoff records that the receiving organization acknowledged it and the referral reached a known outcome or next action. That is the difference between transmission and accountability.