Volunteers Are Not a Resource

Every church I know runs on a small number of people who say yes too often. They run the nursery, set up the chairs, count the offering, lead the small group, fix the projector, stay late to lock up. Ask any pastor who they are and you will get a list in under a minute, usually with a pause and a look that says the pastor knows exactly how much those people are carrying.

Most of the software that churches use to organize volunteers was not designed with that look in mind.

Built for staffing

Volunteer scheduling tools were mostly designed by people who think about staffing. That is not a criticism. Staffing is a real problem, and the tools solve it. They see a role, a time and a pool of available names, and their job is to fill every slot. Send the request, collect the yes, send the reminder, mark it filled. In a business with paid shifts, that is exactly right.

In a church it has a side effect nobody intended. The slots that fill fastest are always filled by the same faithful few, because they are the ones who answer. The tool learns, in effect, who is most reliable, and reliability in a volunteer is very often another word for difficulty saying no. So the software gets steadily better at finding the people least able to refuse, and asking them again.

Nothing on the screen looks wrong. Every slot is filled. The dashboard is green. And somewhere in that green is one person serving three Sundays out of four, in two ministries, plus the midweek group, who has not sat through a full service with their own family in a long time.

How it ends

Then one day that person stops coming. Usually not in anger. There is no confrontation and no complaint. They are just empty, and the easiest way to stop being asked is to stop being there. Every pastor I have talked to has a story like this, and almost every one includes the same sentence: we did not see it coming.

They did not see it because nothing showed it. The tools tracked slots, not people. No screen ever said that this one member was carrying a third of the children's ministry, or that their yes rate had been perfect for two years, which should have been a warning and was instead treated as a compliment.

There is a cost beyond the person, too. When one faithful volunteer burns out, the church usually loses more than their hours. It often loses their family's attendance, their giving, their friendships in the congregation, and the quiet example they set for newer members about what it looks like to serve. It also loses the newer members who were never asked, because the system kept going back to the person who always said yes. The slots got filled. The church got smaller in ways no attendance report captures.

And the leaders feel it. A pastor who loses a faithful volunteer to exhaustion does not usually feel relief that the roster still works. They feel that they failed someone they were responsible for, and they often did not have the information that would have let them do otherwise.

The questions we keep asking

I am not going to describe features here. What I can describe is the set of questions I keep asking about anything in SoapBox that touches serving, because I think they are the right questions for any church tool, ours or anyone else's.

Can a leader see who is carrying too much? Not only which slots are empty, but which people are full. The load on a person matters more than the gap in a schedule.

Is no as easy as yes? If declining takes three steps and an explanation while accepting takes one tap, the design is quietly voting for burnout. A volunteer should be able to say not this time without feeling they have let someone down.

Is the reminder an invitation or a nag? There is a difference between helping someone remember a commitment they want to keep and pressuring someone into one they are too tired to refuse. The wording, the frequency and the timing all carry that difference.

Does anyone say thank you, by name? Not an automated message. A person, noticing a person. Software cannot do that part, but it can make sure the leader knows whom to thank.

Is rest treated as faithfulness or as a gap? A volunteer who steps back for a season is not a hole in the roster. They are a member of the church doing something the Bible takes seriously. The tool should make stepping back normal, not conspicuous.

Serving the servers

Underneath all of this is a simple conviction. A volunteer is not a resource to be allocated. They are a member of the congregation, serving. The church exists for them as much as for anyone they serve, and they did not stop being sheep when they started helping with the flock.

I spent decades building software for businesses, and I know how natural it is to borrow a business tool's assumptions without noticing them. A church is not a business with unpaid staff. It is a family where some members carry more than others, sometimes far too much, out of love. The best thing a tool can do for that family is help its leaders see the people doing the carrying, early enough to share the weight.

If you lead a church, try one thing this week. Make a list of the people who never say no. Then go find one of them, thank them by name, and ask, honestly, whether they need a Sunday off. You may find they have been waiting for someone to ask.