Somewhere there is a spreadsheet, or a laminated binder, from a much bigger church, listing thirty volunteer roles for a fall festival: parking coordinator, photography lead, balloon-arch team, three separate roles for the bounce house. It gets forwarded around, and a small church of 120 people tries to fill it, and half the roles sit empty on the sign-up sheet while three people quietly do everything else.
Most church events do not fail from having too few roles. They fail from having too many undefined ones, or the wrong ones, while the handful that actually keep the event running go unfilled. A minimum-viable team is shorter than you think, and it scales in a predictable way as your church grows.
What actually breaks without a volunteer there
Before listing roles, it helps to ask what genuinely goes wrong if nobody is assigned to it. Doors that do not get unlocked. Tables that do not get set up before people arrive. Nobody at the door to say hello, so guests walk in and stand there. Nobody at a table to write down a name, so a first-time family leaves without anyone knowing they came. Trash that nobody bags at the end, so the same three families who always stay late are the ones bagging it, again. Every role on the minimum-viable list exists to prevent one of those specific, ordinary failures — not to fill out an org chart.
The six roles almost every event needs
Regardless of whether the event is a potluck for 60 or a fall festival for 300, six roles do the actual work of keeping it running:
- Event lead. One person who knows the whole plan and can answer “where does this go” without checking with anyone else. Not the busiest person on staff — the one who will actually be there two hours early.
- Setup crew. Tables, chairs, signage, whatever the event needs before doors open. Two or three people, not one, because setup always takes longer than the person planning it expects.
- Greeter. Someone whose only job is the first thirty seconds of a guest's experience — eye contact, a welcome, pointing them somewhere. Not the same person staffing a table, if you can help it.
- Check-in or registration table. Whoever gets a name written down, a sticker handed out, or a form signed. This is the role that turns a stranger who showed up into a name somebody can follow up with later.
- Floater. No fixed station. Their job is to notice what is going wrong before the event lead has to — a line backing up, a table running low, a kid who wandered off from their parent.
- Teardown crew. Ideally named separately from setup, even if it is the same people. Setup volunteers are often exhausted and gone by the last hour, and teardown left unassigned tends to fall on whoever is too polite to leave.
Everything past these six is an addition for a specific activity — a craft table, a grill, a photo backdrop — not a structural requirement of the event itself.
Scaling the team to your church's size
The six core roles do not multiply one-for-one with attendance. A church of 60 and a church of 250 need roughly the same lead and floater, but the setup crew, greeters, and check-in table each need another body per fifty or so additional people expected.
Under 75 people
One event lead, two on setup who can also handle teardown, one greeter, one person at check-in, and a floater if you can spare six volunteers total. If you only have five, fold the floater duties into the event lead's job and accept that something small will slip.
75 to 200 people
One lead, three on setup, two greeters at different entry points if there are multiple doors, one or two at check-in depending on how many families arrive in the first fifteen minutes, a dedicated floater, and a separate teardown crew of two or three. That is nine to twelve volunteers, plus anyone running a specific activity.
200 and up
The core roles stay the same shape but need more hands at check-in and greeting specifically, since those are the two jobs most sensitive to a bottleneck at the door. Add a second floater rather than doubling every role — one floater per roughly 150 attendees is a reasonable rule of thumb, since their job is to cover gaps, not staff a fixed post.
Roles to skip until you actually need them
Copying a larger church's volunteer list usually means copying roles that solved a problem you do not have. A parking coordinator makes sense when a lot is genuinely full and cars are circling. It is unnecessary overhead when there are ten open spots and everyone can see them. A dedicated photography role matters for a church trying to build a social-media presence; it is optional for a potluck. Separate roles for every craft-table station sound organized on paper and mean five under-used volunteers standing at empty tables in practice — better to have two people covering three stations and moving between them.
The test worth applying to any role someone suggests adding: what specifically breaks if nobody is assigned to it? If the honest answer is “nothing much,” it belongs on the list of roles to skip, not the sign-up sheet.
A second-order cost of over-listing roles is what it does to recruiting. A sign-up sheet with eighteen slots, half of them vague or unnecessary, reads as chaos to a volunteer deciding whether to say yes. A sheet with six clear roles, each with a real reason to exist, reads as organized — and organized is what actually earns a yes from someone on the fence. Fewer roles, each one obviously necessary, recruits better than a long list padded with jobs nobody will notice went unfilled.
Let one person hold two roles, not three
Small churches are usually short on hands, not short on tasks, so combining roles is often necessary. A greeter can also watch the door for latecomers. A setup lead can also run the floater job once doors open, since setup is finished by then anyway. What does not combine well is check-in with anything else — the moment a line forms, a person juggling two jobs will drop the relational one and keep the transactional one, and check-in is the transactional one. If you are down to four volunteers, protect check-in and greeting as their own jobs and combine everything else.
Recruiting for one event is a different ask than ongoing serving
A single-event ask is easier to say yes to than an ongoing serving commitment, and it is worth treating it that way when you recruit. “Can you run check-in for the fall festival” is a bounded, specific request with a clear end. “Can you join the events team” is vaguer and easier to decline. Ask for the single event first. Some of those one-time volunteers will ask to do it again, and that is how an ongoing team gets built without ever having recruited for one directly — the same pattern described in building a serving team that does not burn out.
Once you have more than a handful of recurring volunteers across several events, the scheduling problem stops being who to ask and becomes who already served last time, which is the subject of scheduling volunteers when it is the same ten people. SundayBridge keeps a record of who served on which team and when, so that question has an answer instead of a guess. It will not tell you who to ask next for a specific event — that judgment call is still yours — but it removes the part where you are trying to remember off the top of your head whether Dana already worked check-in twice this month.
Closing the loop after the event ends
The event does not end when the last chair is stacked. Whoever worked check-in has names of people who showed up for the first time, and those names are worth more than the event itself if nothing happens with them in the following week. Building the actual follow-up habit — who owns calling a first-time guest, and by when — is covered in following up after a big Sunday. The short version: decide who is responsible for those names before the event starts, not after everyone has gone home and the sign-up sheet has been recycled with the coffee cups.
If your event was part of a broader push — a fall festival meant to bring in new families, a Christmas Eve service, a VBS week — the volunteer team for that push is really a subset of the bigger planning question covered in planning a church event. Get the roles right and the rest of the plan has somewhere to land.