The pastor cannot visit everyone. Not because they do not want to — most bivocational pastors would visit every hospital room and sit at every kitchen table if the week had more hours in it — but because a congregation of 150 will produce more grief, more surgery, more quiet crisis than one person can carry alone. The math does not work, and pretending it does is how pastors burn out and how the person in room 412 goes three days without a visit.
A lay care team is the fix, but only if it is built with some structure. A list of well-meaning names in a phone is not a team; it is a rumor of help that may or may not show up. This guide is about the difference: how to recruit the right people, give them a real and bounded job, and keep the whole thing running without it becoming another burden on the one person who was already overloaded.
Decide what the team actually does before you recruit anyone
Most lay care teams fail at the definition stage, not the recruiting stage. “Pastoral care” sounds like one job. It is actually several: hospital visits, meal coordination after a surgery or a death, a phone call to someone who has not been at church in a month, a card for a birthday, sitting with someone through a hard diagnosis. Some of those need training and discretion. Some just need a person who shows up with a casserole and does not need to be told twice.
Write down the two or three things your team will do this year, not the ten things a perfect team would eventually do. A church of 80 with no existing team should probably start with hospital and bereavement visits plus meal coordination, and leave the rest for later. Trying to launch a five-function team in month one is how you end up with three volunteers and a document nobody follows.
Recruit for steadiness, not eloquence
The instinct is to recruit whoever is warmest in conversation — the person who is easy to talk to at coffee hour. That is not the same skill as showing up at a hospital at 7 a.m. or sitting in silence with someone who just lost a spouse. What you actually need is steadiness: people who follow through on small commitments, who do not need to be reminded twice, and who can keep something private without it becoming a story by Wednesday.
- Ask the person who already does this informally. Every church has one or two people who already bring meals and make calls without being asked. They are your first recruits — you are just giving their instinct a structure.
- Look past the usual serving roster. Someone who is not gifted at greeting or teaching may be exactly the right person to sit with a grieving widower for an hour. Widen who you consider.
- Recruit in pairs when you can. New visitors are more comfortable shadowing someone the first few times than being handed a name and an address alone.
Set a caseload before someone else sets it for you
Without a stated limit, a lay care team absorbs load until someone quits. A church of 150 with one enthusiastic volunteer will hand that volunteer every hard situation until they are exhausted, simply because asking the reliable person is easier than recruiting a new one. A rough starting ratio is one team member per 15 to 25 people — for 150 people, that is six to ten volunteers, adjusted for how many young families or aging members you actually have.
Decide, out loud, how many active situations one person carries at a time. Two or three is reasonable for someone doing this alongside a job and a family. When a new need comes in and everyone is already at their limit, that is the signal to recruit again — not to quietly overload whoever answers the phone first.
Give every situation an owner and a next step
The single most common failure in lay care is not a lack of compassion. It is diffusion of responsibility — three people know someone is struggling, each assumes someone else is handling it, and nobody actually calls. The fix is unglamorous: every case gets one named owner and a date for the next check-in, written down somewhere everyone on the team can see.
This is the same discipline that keeps a follow-up board from stalling — a name with no owner and no date is a name that quietly ages until someone notices, usually too late. Pastoral care needs the same accountability, just with more discretion around what gets written and who can see it.
Keep the record private, current, and in one place
A care situation should not live in one volunteer's memory, a text thread, and a sticky note on the pastor's desk simultaneously. Somewhere, there needs to be a single record: who is being cared for, who is responsible, what has already happened, and what happens next. It does not need to be elaborate. It does need to survive a volunteer's season ending, a phone getting a new owner, or a pastor going on vacation.
SundayBridge keeps this as a pastoral care case attached to a person's record — comments and history in one discreet place, with full create-edit-delete control, instead of scattered across whoever happened to take the call. The point is not the software; the point is that the record outlives any one person's attention span.
Train for the handoff, not just the visit
Most training conversations focus on what to say at a hospital bedside, which matters, but the more common failure is the handoff: volunteer A visits once, assumes someone will follow up, and nobody does. Spend at least as much time on how a case gets passed — what gets written down, who gets told, and when a situation should be escalated to the pastor rather than handled quietly by the team.
A short, written expectation helps here: after every visit or call, the volunteer adds one line to the record and flags whether the pastor needs to know. That single habit prevents the two failure modes that sink most lay care efforts — the case that dies quietly because nobody wrote anything down, and the case that should have reached the pastor and never did.
Review the team's load every few months, not just when someone complains
Teams drift the same way volunteer schedules drift — quietly, until one person is carrying six situations and another is carrying none. Set a recurring check, even informal, where the team lead looks at who is handling what and rebalances before someone burns out. This is also the moment to notice patterns: if three of your last five cases involved isolated seniors, that is a signal to recruit someone specifically suited to that, not just another generalist.
If your church already tracks who has quietly stopped showing up, that same signal is often the first indicator a care team should be looking at someone, before a crisis makes it obvious.
Start smaller than feels responsible
The temptation is to launch with a full org chart — team lead, hospital visitors, meal coordinators, bereavement callers — before a single visit has happened. Resist it. Two or three steady people doing one job well, with a clear owner-and-date habit and one shared record, will outperform a large team with no structure. Add roles as real need shows up, not in anticipation of need that might.
None of this requires much money or much technology. It requires naming the job clearly, recruiting for steadiness over charisma, and refusing to let any single case exist only in someone's memory. A church that gets those three things right will out-care a much larger congregation with none of them.