Article

Why Your Printed Referral List Is Already Wrong

Dennis Ellis · September 15, 2026

Somewhere in your church office there is a list of agencies. It was accurate the week it was printed. Every week since, it has been getting quietly worse, and nothing on the page says so.

How the decay works

Four things change, and none of them announces itself.

A program ends. A grant funded the utility assistance for two years. Year three, the line item is gone. The agency is still there, still answering, still doing good work, and no longer doing the thing you are sending people for.

Hours move. The pantry goes from three days to one. This is the most common change and the least visible, because the organization’s name, address and phone number are all still correct.

Eligibility narrows. The waitlist gets long, so the agency limits intake to one county, or to households with children, or to people who have not been served in the last twelve months.

The contact leaves. The direct number on your list rang a desk. That person retired and the number now rings a general voicemail that is checked on Fridays.

In all four cases your list looks identical to the day it was right.

Who finds out

Not the church. The person you sent.

They took a bus, or asked for a ride, or used gas they did not have, and arrived to a locked door or a closed program. Then they made a decision about whether to come back to you.

That is the real cost of a stale list, and it is paid entirely by the person who had the least to spare.

The scheduled audit does not solve this

The instinct is to fix it with discipline: review the list every quarter, call every agency, update every row.

Two problems. It is a day of work that nobody owns, so it slips. And even when it happens, it only catches what changed before the audit. The pantry that moves to Wednesdays in week two of the quarter is wrong for ten weeks.

The signal that actually catches it

The church already generates the information. It just throws it away.

Every referral that goes nowhere is a data point about a provider. The number was disconnected. The waitlist was ten weeks. Nobody called back. The program ended in February. Right now that information lives in one volunteer’s head for about a week and then is gone.

Recording it changes what the list is. After a year, you are not holding a directory of agencies in your county. You are holding a list of which agencies in your county actually answer, ranked by evidence your own church collected.

Nobody can sell you that list. It only exists if you wrote things down.

What it takes

Three things, and only the third is software.

  1. Record the referral when you make it. Which provider, for what need, on what day, by whom.
  2. Have a reason to come back to it. A date, a queue, a person whose job includes looking at the ones nobody has answered.
  3. Have somewhere to put the unwelcome answer. Most systems have a field for success. The field that matters here is the one for not served, and the reason why.

In CMinLink, a referral carries a follow-up date and a daily job surfaces the ones that are overdue. Closing a referral requires an outcome — served, partially served, or not served — and the reason list behind it is configurable, so it uses your church’s vocabulary rather than ours.

What comes out the other end is the service-gap report: what your community asked for, and what you had nowhere to send them for.

Common questions

How often should a referral list be checked?
Checking on a schedule is better than not checking, but it is expensive and it still misses things between checks. The cheaper signal is recording what happened to the referrals you already made.
Is a county 211 list enough?
It is a good starting point and it is broader than anything a single church will build. It is also general-purpose, so it will not know which three providers in your county actually answer the phone.