Write a serving role too broadly and it sits open for a month. Write it too narrowly and you end up with forty open slots instead of twelve. Both mistakes look like the same symptom — a sign-up sheet nobody is signing — and both get blamed on the same thing: people just are not volunteering like they used to. Often the real problem is smaller and more fixable than that. The role, as written, does not tell anyone what they would actually be agreeing to.
There is a line between vague and narrow, and it is not a matter of taste. You can find it by asking two plain questions about any role before you post it: can someone picture their Sunday from this description, and could more than one person plausibly do it.
Vague roles fail a specific test
“Help with hospitality” asks someone to imagine an entire category of church life and guess which slice of it you mean. Does it involve coffee. Does it involve standing at a door. Does it involve talking to strangers or restocking a cabinet nobody can find. A person reading that role cannot picture their actual Sunday morning, and people rarely commit to a picture they cannot see. So the sign-up sheet sits blank, not because the congregation lacks willing people, but because the description gave them nothing to say yes to.
The fix is not longer language. It is a name that maps to one concrete Sunday task: parking lot greeter, coffee setup, nursery check-in, sound board. Each of those tells a reader exactly where they would stand and roughly what they would do, before they have asked a single follow-up question.
Narrow roles fail a different test
The opposite mistake looks like diligence. A team splits “help with hospitality” into coffee setup, coffee service, coffee cleanup, donut table, and greeting the donut table — five roles where three would do. Each one is easy to picture, which is good. But now there are five slots to fill every week instead of three, and five people to track instead of three, and a much higher chance that any given Sunday has at least one open slot somewhere in that chain.
Narrow roles do not fail to attract volunteers the way vague roles do. People generally can say yes to a specific, small ask. They fail on arithmetic instead. A congregation of 120 with 8 people willing to serve on a rotation can comfortably staff ten broad roles across a month. Split those same duties into twenty-five narrow roles and you have not created more willingness — you have created more gaps for the same willingness to cover, and more chances that one person’s sick Sunday leaves a visible hole.
There is also a quieter cost to over-splitting: whoever schedules the team now has to think about twenty-five things instead of ten every single week. Each extra role is another name to chase, another reminder to send, another gap to notice before Sunday morning arrives. A role list that has grown past what the team actually needs is rarely a sign of a more organized church — more often it is a sign that nobody has gone back and merged the pieces that used to be one job.
The test that actually separates the two
Before posting a role, ask: could a stranger to your church picture their Sunday morning from this description alone. If not, it is too vague — name the actual task.
Then ask a second question: if the usual person calls in sick Saturday night, can you name at least one or two other people who could plausibly step in. If the honest answer is “only one person in the whole church could do that,” the role is too narrow, or it has been defined around one person’s particular habits rather than the task itself. Widen it back out until more than one person fits it.
Both checks point at the same underlying idea: a role description is not documentation, it is an invitation. It has to be specific enough to picture and broad enough that more than one person could say yes to it.
What a right-sized role actually looks like
A role that passes both tests tends to read like a short, plain sentence rather than a job title. Not “usher” and not “hand out bulletin at the second door on the left side only during the 9am service.” Something in between:
- What they do — one sentence a person could act on without asking a follow-up question.
- Roughly how long it takes — arrive fifteen minutes early, done ten minutes after the service ends.
- Who else could do it — if the answer is nobody, the role is not really a role yet. It is one person’s job with a label on it.
That third point is the one most teams skip, and it is the one that determines whether the role survives someone leaving. A role built around what a task requires can be handed to the next willing person. A role built around what one particular volunteer happens to enjoy doing usually cannot be, and it quietly disappears the moment that person steps back.
It helps to write the role from the point of view of the person reading it for the first time, not from the point of view of whoever has always done it. The longtime volunteer already knows which door sticks and which cabinet holds the extra coffee filters. A description written for them, rather than for the next person, is exactly the kind of description that turns into a role only one person can fill.
Watch for roles that grew narrow by accident
Nobody sets out to write twenty-five roles where ten would serve. It happens gradually, one exception at a time. Someone asks to only do the early service. Someone else prefers setup over cleanup. A well-meaning coordinator writes each preference down as its own role so nobody feels boxed in, and eighteen months later the serving list has tripled in length without the congregation growing at all. Each individual split made sense. The sum of them made the schedule fragile.
If you have scheduling volunteers when it is the same ten people every week, this is often the quiet reason the same names cover everything: the role list has grown into more slots than the team can cover, and consolidating a handful of near-duplicate roles frees up real capacity without asking anyone to do more.
Reviewing roles is part of the job, not a one-time setup task
A role that made sense two years ago — back when one specific person needed a specific accommodation — can outlive its reason. Go through the list once or twice a year and ask, for each role, whether it still passes both tests: can a newcomer picture it, and could more than one person fill it. Merge the ones that have drifted too narrow. Split the ones that have stayed too vague to attract anyone. SundayBridge keeps every serving role and who is assigned to it in one place, so this kind of review is a matter of scanning a list rather than reconstructing it from memory or a spreadsheet nobody has opened since spring.
The same review is a good moment to notice which roles keep landing on the same two or three names, which is often the earliest sign of the burnout that shows up later. If a role has quietly become one person’s unpaid part-time job, it is worth reading about building a serving team that does not burn out before that person is the one who disappears.
Roles for one-time events deserve their own version of this
The same tension shows up outside the weekly rotation. A single event — a fall festival, a baptism Sunday, a fundraiser dinner — tempts organizers into either one giant vague ask (“volunteers needed”) or a dozen narrow ones written the week before, when there is no time left to consolidate anything. The same two questions still apply: can someone picture the shift, and could more than one person cover it. If you are building out the volunteer list for an upcoming event, it is worth reading planning a church event without a dozen spreadsheets before the roles get written, not after.
Start with the task, not the title
If you are rewriting your serving roles from scratch, resist the urge to start with a list of titles borrowed from a bigger church’s website. Start with the actual list of tasks a Sunday requires, and let each role be the smallest chunk of that list that a typical volunteer could describe back to you in one sentence. A role that started as a task usually ends up the right size on its own. One that started as a title copied from somewhere else usually needs the two tests above run on it before you post it.