StewaraGuidesCare
Care doesn't get dropped by the person who noticed. It gets dropped in the handoff.
Somebody always notices. That is what a church is for. What fails is the twenty seconds in a corridor where one person says they will take it, the other believes them, and neither finds out for six weeks.
Both of you walked away relieved
It happens in a corridor, somewhere between the second service and the parking lot.
Someone stops you. The Parkers were not here again, that is three weeks now, and their daughter said something at youth about her dad. You say the right thing, because you are the sort of person who says the right thing. Then you say the better thing: Steve knows them, Steve should be the one. Steve, can you check on the Parkers?
Steve says yes. Steve means it.
Both of you walk away relieved, and the relief is the whole problem. You have each filed this as handled. One of you is wrong about that, and neither of you is going to find out for six weeks.
Nobody in that corridor did anything wrong. Nobody was lazy and nobody stopped caring. Steve had four more conversations before he reached his car, one of them about a broken thermostat, and by Tuesday the Parkers had turned back into a feeling rather than a task.
Races are lost in the exchange zone
Watch a relay and you will notice something. Nobody ever drops the baton while they are running.
They drop it in the exchange zone. Twenty meters where two runners are both moving, both have a hand on it, and for about a second and a half neither of them is entirely responsible for it. That is the only stretch of the race where the baton can hit the track. Everything either side of it is just running.
Pastoral care has exactly that shape, and churches keep training for the wrong part of it. You are good at the running. Your people notice; somebody always notices. Almost the entire loss happens in the second and a half where care passes from the person who saw it to the person who will do something about it.
Unlike a relay, nobody blows a whistle. The baton hits the track quietly, in a corridor, while two people who like each other are both smiling.
Assigned is a hope, not a status
Every piece of church software has an assign button. What that button does is move a row out of your list and into somebody else's.
Watch your own screen after you press it. The item leaves. Your list gets shorter. The little number goes down. Every signal the interface gives you says the same thing the corridor said: handled.
It is not handled. It has been moved. Those are different words and only one of them is true.
The word assigned is doing an enormous amount of unearned work in most of these tools. It describes a state of a database and gets read as a state of the world, and the gap between those two readings is where a family quietly stops coming.
So ask a plain question of whatever you use now. Three weeks after you assign someone to a staff member, how do you find out whether anything happened? If the honest answer is that you would have to go and look them up, then you will not, because there are forty of them and you do not know which forty.
The four things a handoff has to carry
A handoff that survives contact with a Tuesday carries four things. Most corridors deliver one and a half of them.
- A specific person. Not a queue, not the care team, not whoever picks it up first. A shared queue is a fine home for work nobody owns yet and a terrible home for work somebody promised. Anything addressed to everybody is addressed to nobody.
- Actual words. “Check on the Parkers” is not an instruction, it is a feeling with a surname attached. Whoever receives it has to reconstruct what you meant and will do it badly, because they were not standing where you were standing when you learned it. One sentence of what is really going on is the entire difference between a phone call that helps and a phone call that opens with “so, how are things?”
- A date. Not because a deadline manufactures urgency. Because “soon” has no end and therefore can never be late. A date is not pressure; it is the only thing that turns lateness from a mood into a fact.
- A way back. This is the one almost everyone forgets. The person who handed it off has to learn what happened, and not by asking. If the return leg depends on somebody remembering to chase, you have not built a handoff. You have built a hope with a due date attached.
Do not automate this. Just stop hiding it.
Once a church has felt this a few times, the instinct is to build a machine. Reminders. Escalation after so many days. Automatic reassignment. A nag that fires until somebody clicks something.
Resist that, and not for a squeamish reason. It does not work, and it fails in a particular way that is worth understanding before you buy anything.
The moment software begins chasing a person about a grieving family, the family becomes the thing the software is chasing about. Staff learn the rhythm of a nag inside a fortnight and start clearing rows to make it stop. You have not produced follow-through. You have produced a ticket queue and trained your team to close tickets, which is a genuine skill and the precise opposite of the one you were hoping for.
What actually works is smaller, and slightly boring.
Let the person who handed it off see that it is still out. Show it to them unasked, on a screen they already open, and let it get visibly older. Nobody needs a notification telling them Steve has been carrying the Parkers for eleven days. They need to be able to see that Steve has been carrying the Parkers for eleven days, sitting next to the four other things Steve is carrying.
That turns an accusation into a question, and the question is almost always whether he needs a hand with any of them, which is what you wanted to ask in the first place.
How we do it
How Stewara does it
In Stewara, passing someone to a colleague does not create a second work item. It re-homes the existing one, which is why the shared follow-up queue keeps showing it with a small chip reading “with Jordan Ellis”. The obligation did not leave the church. It moved hands.
The form is called “Pass to someone” and its own description says what it does: “pick a staff member, add a note and a due date — it lands on their Home”. You cannot pass a person to yourself, because you are not in the list. And you cannot send an empty one: the note is required by the server rather than by the form, and the refusal reads “A handoff needs a note.” The placeholder asks the useful question rather than a generic one, which for a man named Marcus is “What does Marcus need?”
Dates are calendar days rather than timestamps. That sounds like a technicality until you have watched a task due today sit in a list marked overdue all day because a server disagreed with a staff member about which day it was. Due the sixteenth means the sixteenth to every person who reads it, and a task due today is not overdue.
At the other end it arrives in a panel called “Passed to you”, which does not exist at all on days when nothing was passed to you. Closing it asks one question, “What happened?”, and that answer travels back to the person who sent it. If it needs to keep moving there is a second button, “Save & pass along”, which closes your leg and opens the next one in a single gesture.
And then the part this whole article is about. The person who sent it has a panel called “Still out”: every baton they passed that has not come back, oldest at the top, with an age that turns amber past five days and red past ten. There are no buttons on those rows. Nothing to click, nothing to nudge with, nothing that fires at anybody. Being visible is the entire feature.
Some smaller decisions follow from the same idea:
Three things it deliberately does not do, and you should hear them here rather than discover them later. Nothing is sent when a handoff lands: no push, no email, no text. It appears on their Home and they find it when they open it, which is the trade this whole article argues for, but it is a trade. There is no accepting or declining, because a handoff is a fact rather than a request. And nothing expires, gets reassigned or bounces back on its own. It sits where you put it and ages in front of you, which is the point, and it is also why the short-list caveat above matters.
- Any staff member can raise a one-line “Flag for the pastor”, because the person who notices is often not the person who can act. A pastor never sees that button, since flagging yourself is not a workflow. Acknowledging one is a single “Got it” with no write-up demanded, because a flag is acknowledged rather than resolved.
- Possession beats permission. Handing someone on is normally a pastor's move, but whoever is currently holding a baton can pass it along for that one person, for an hour after they close their own leg. A greeter can send a first-time guest to the coffee host without an administrator being involved, and without gaining the ability to start a handoff about anybody else.
- The overdue watcher exists, ships switched off, and when a church does turn it on it promotes the original task rather than cloning it. Two rows for one promise is how a follow-up list becomes something people stop reading.
- A handoff carries the note you wrote, the due date and the person's name. It does not carry their care history. Being handed someone is not the same as being given their file.
The short version
If you are trying to fix follow-up, the thing to fix is not the noticing. Your church is already good at that.
- Care is rarely lost by the person who noticed. It is lost in the pass.
- “Assigned” describes your database, not your church. Ask how you find out, three weeks later, whether anything actually happened.
- A handoff needs a specific name, one sentence of what you actually know, a date, and a way for the answer to come back without anyone chasing it.
- Do not buy a nagging machine. Software that chases staff about families teaches them to close tickets.
- Show the sender what is still out and let it age in plain sight. It is a far smaller feature than escalation, and it is the one that works.