A lady in our church had surgery on a Tuesday. I found out about it the following Sunday, from her daughter, standing in the lobby between services. She wasn't upset with me. That's the part that stuck. She just said, "Mom didn't want to bother anybody," like it was settled, like she'd already made her peace with nobody coming.
Every pastor I know has a story like that. The hospital stay you heard about after they were already home. The family that got three casseroles the first week after the funeral and then nothing. The need that came up in a meeting where everybody nodded and everybody figured somebody else had it.
I want to say clearly that none of that happened because our church doesn't care. I've been doing this thirty years and I've never met a church that didn't care. What I've rarely seen is a church that could tell you, with any confidence, that nobody slipped through last month. Those are two different things, and for a long time I had the first one and assumed it covered the second.
What our system actually was
When I finally sat down and got honest about how care worked at our church, the list was short:
- My memory, which by Tuesday afternoon is holding about forty other things.
- Hallway conversations, which only reach the people who happened to be in the hallway.
- A prayer list that got read out loud on Wednesday and then filed.
- Whoever felt prompted to check on somebody that week.
All of those work part of the time. That's what makes this so hard to see. It works often enough to feel like a system, and when it fails it doesn't make a sound. A dropped care need isn't like a bad email address that bounces back at you. It just goes quiet on the other end, and the family waits a while, and then they stop waiting.
Where we were actually losing people
I went back through the misses I knew about and found that almost all of them happened in one of three spots.
The need never got written down anywhere. That surgery I mentioned? People knew. Her small group leader knew. He mentioned it to somebody, who meant to tell me. The information was inside our church the entire time. It just never landed anywhere that was responsible for doing something about it.
Nobody in particular owned it. "Somebody ought to go by and see her" gets said, everybody agrees, and that's usually where it ends. When a need belongs to the whole team it doesn't really belong to anyone.
We ran out of attention before the family ran out of need. When we did respond we were good for about two weeks. Grief doesn't work on a two-week schedule. The call in month three, the card on the anniversary of a death, the check-in after the treatments are over: nobody's memory stretches that far while also running a church. Something has to keep that calendar, and at our church nothing was.
What we do now
None of these seams get fixed by trying harder, because trying harder was already the plan and had been for years. We changed three things.
First, every need goes in one place. Anybody on the care team can add one from their phone in about thirty seconds, from the lobby, in the hospital parking lot, wherever. Getting it written down is now the last part of this that depends on somebody's memory.
Second, it goes to one person by name, right away, with an easy way to say yes or no. If that person can't take it, and often they can't because they're at work or have a sick kid, it moves to the next person on its own and keeps moving until somebody accepts. That one change did more than anything else we tried. I wrote up the night it earned its keep in Four People Missed the Text. The Family Never Knew.
Third, the follow-ups get scheduled the day the need comes in. The meal train, the call in week three, the card in month six. They come back around on their own so nobody has to carry them in their head.
The first eighteen days
We turned this on at the beginning of August. Here's what the log says for the first eighteen days, and I'm giving you the numbers straight rather than the flattering version:
- 24 care needs came in. Surgeries, hospital stays, an ER admission, a few families in hard seasons.
- All 24 were accepted by a real person, by name.
- The median time from a need being entered to somebody accepting it was 28 minutes. The fastest was 12 seconds. The slowest took about two and a half hours and had to work its way through several people on a weeknight before it landed.
- Needs dropped: none.
Eighteen days is not a long time and I'm not going to pretend otherwise. Ask me again at the one-year mark. But I'll say this much: my people did not become more loving in August. They were already loving. What changed is that their love stopped leaking out through three specific holes.
My elders get a one-page summary every Monday now, and the number at the top is how many needs we dropped. If you want the argument for why that number beats everything else we used to count, I made it in The Only Care Metric Worth Reporting to Your Board.
All of this eventually became CarePilot, because after a couple of months other pastors started asking what we were doing. But please hear me on this: the ideas are free. One place for needs, one owner by name, follow-ups with dates on them. If you can build that with index cards and one faithful deacon, then build it with index cards and one faithful deacon. Just build it before the next Tuesday surgery you find out about on Sunday.
Want the system without building it yourself?
CarePilot is the engine described above, running in our church every week. It texts the right volunteer, keeps going until somebody says yes, and reports the number that matters.