At a church of 80, the pastor did the admin work between sermons, hospital visits, and everything else, because there was no budget for a part-time secretary and no obvious volunteer to ask. Records slipped. A guest’s name got written on a card and never entered anywhere. Giving statements went out three weeks late. None of this was anyone’s fault — there was simply one person doing a job built for two or three.
A volunteer admin team is not a downgrade from a paid secretary. Done well, it is a different shape of the same job, split across people who each own a narrow, defined piece of it. This guide is about how to find those people, what to actually ask of them, and how to keep the whole thing running after the person who built it moves on.
Start by naming the actual jobs, not one big job
“Office volunteer” is not a job description — it is a shrug. Nobody signs up for a shrug. Before you recruit anyone, write down the specific, recurring tasks a paid secretary would have done in a normal week. For most churches of 60 to 250 people, that list is shorter than it feels:
- Entering new guests and updating household records after Sunday.
- Recording contributions and keeping giving records current.
- Building or updating the month’s gatherings calendar.
- Checking the follow-up board for names nobody has picked up.
- Printing or preparing anything for the coming Sunday.
Once the list is broken into pieces, you are no longer looking for one heroic volunteer — you are looking for two or three people, each of whom can say yes to something specific and bounded. That is a much easier ask, and a much easier job to actually do well.
Split the roles by area, not by day
A common mistake is dividing admin work by day of the week — whoever is free on Tuesday does “whatever needs doing.” This sounds flexible but actually makes the job harder, because every volunteer has to hold the whole system in their head. Splitting by area instead means each person becomes genuinely good at one thing:
- People and follow-up. Owns the directory and the follow-up board — entering new guests, updating household information, and checking that every open follow-up has an owner and a date, not just a name sitting unclaimed.
- Giving. Records contributions on a set schedule, watches for anything that looks wrong before it compounds, and is the person who prepares year-end statements in January.
- Calendar and gatherings. Keeps the month’s events current, closes out registrations after they happen, and is the one person who knows what is actually on the calendar three weeks out.
A church of 100 can often run on two of these roles, with one person covering giving and calendar together. A church past 200 usually needs all three, because the volume of guests and gatherings alone fills a person’s week.
Recruit for the outcome, not the task
“We need someone to help with data entry” recruits nobody. “We need someone who makes sure the guest who visited last week doesn’t fall through the cracks” recruits a person who cares about that outcome and is willing to learn the task underneath it. The task is the boring part; the outcome is the reason anyone says yes.
Ask specific people specific things. A general announcement from the front — “we’re looking for office help” — rarely produces a volunteer. A direct ask to someone you have already watched pay attention to detail, framed around one bounded role, usually does. Most small churches already have a retired bookkeeper, a detail-oriented parent, or a former administrative professional sitting in a pew who has simply never been asked.
Give each role a short, written handoff
The single biggest risk to a volunteer admin team is not incompetence — it is memory loss when someone leaves. If the giving volunteer moves across the country and nobody wrote down how the process actually works, the church does not just lose a person, it loses a system.
The fix does not need to be elaborate. A single page per role, updated whenever the process changes, covering:
- What gets done, on what schedule (weekly, after each Sunday, monthly).
- Where the information comes from (attendance cards, offering envelopes, sign-up sheets).
- Who to ask when something looks wrong.
This is the same instinct behind a weekly admin rhythm — the goal is a process that survives whoever is currently running it, not a system that lives entirely in one volunteer’s head.
Set boundaries before you set a schedule
Volunteers burn out from ambiguity as often as from workload. Before anyone starts, agree on what “done” looks like for their role, and just as importantly, what is not their job. The follow-up volunteer is not responsible for making the pastoral visit — only for making sure a name and a date exist so someone else can. The giving volunteer is not responsible for deciding how funds are spent — only for recording what came in accurately and on schedule. Drawing that line early prevents a volunteer from quietly absorbing responsibilities nobody asked them to carry, which is one of the more common paths to resentment and a sudden resignation.
It also helps to agree on what happens when the work does not get done on a given week. Life happens — a volunteer gets sick, travels, or simply runs out of time before Sunday. If the answer is a shrug and a backlog that grows quietly, the job feels heavier every week it slips. If the answer is a known backup person who can cover a single week without taking over the role permanently, the job stays light enough that people are willing to keep doing it. Naming that backup ahead of time, even informally, is cheap insurance against burnout on both sides.
Be honest about the one-login limitation
Most small-church software, including SundayBridge, runs on one login per church rather than separate accounts with different permissions per volunteer. That is a real constraint, not a footnote. If your giving volunteer and your follow-up volunteer share the same login, either of them can technically see the other’s area of the records.
For most volunteer teams of two or three trusted people, this is a workable trade-off — it is the same access a paid part-time secretary would have had anyway. Where it matters is discretion around giving and pastoral care: agree openly, as a team, that seeing something does not mean discussing it, and keep the number of people holding the login as small as the work genuinely requires.
Build in a second set of eyes, especially for giving
A volunteer entering contributions should not also be the only person who ever reviews the totals. Pair the person doing the weekly entry with a treasurer or finance-committee member who checks the running numbers once a month. This is not about distrust — it is about the same reason two people count the offering together. Mistakes caught early are a correction; mistakes caught in December are a scramble.
The same logic applies to the follow-up board. A volunteer who owns it should not be the only person who ever looks at what is aging. A five- minute check-in with a pastor or elder, even monthly, catches the guest whose follow-up quietly stalled for six weeks.
Expect turnover, and plan for it from day one
Volunteer admin roles turn over more than paid positions — people move, get busier, or simply need a season off. Treat this as a certainty rather than a risk you hope to avoid. The handoff document from earlier in this guide is the practical answer, but so is simply not building the whole system around one irreplaceable person.
If you are still assembling your records into a shape a volunteer team can actually maintain, it is worth reading about moving off spreadsheets before you recruit anyone — a volunteer inherits whatever mess or clarity already exists, and starting them on a spreadsheet with three different formats for phone numbers is a fast way to lose them.
What this looks like month to month
A church of 120 with two admin volunteers might run something like this: the people-and-follow-up volunteer spends thirty minutes after each Sunday entering guests and checking the follow-up board, then twenty minutes on a weekday keeping the directory current. The giving volunteer spends an hour a week on entry and, in January, an afternoon preparing year-end statements. Neither role is a part-time job. Both are bounded enough that a volunteer with a full-time job elsewhere can actually sustain them for years, not months.
That sustainability is the real measure of success — not whether the records look perfect the first month, but whether the same two people (or their trained replacements) are still doing this calmly a year later. SundayBridge exists for churches running admin this way: one shared login, straightforward screens a volunteer can learn in an afternoon, and nothing to configure around roles or permissions because there aren’t any to set up.