A church secretary at a congregation of 150 once told me she had stopped delegating almost anything, not because volunteers were unwilling, but because she had been burned once by a task that looked simple and was not. A well-meaning volunteer had called a grieving family to confirm a funeral date using details that were supposed to stay private. Nobody was careless on purpose. The task was just handed off without anyone asking what it actually required.
Most admin tasks in a church are not that fraught. But they are not all the same, either, and the mistake most offices make is treating them as if they were — either everything gets guarded like the safe combination, or everything gets handed to whoever is standing nearby on a Tuesday afternoon. A better approach sorts tasks along two questions: how much judgment does this take, and how much does the person doing it need to see?
The two questions that actually matter
The good news is that most churches are not actually short on trustworthy people. They are short on a shared, simple way to decide who does what. Once a task is sorted correctly, the decision about who does it tends to make itself — a teenager can print name tags, a retired accountant can reconcile the giving spreadsheet, and the pastor stops being the default answer for everything in between.
Forget job titles for a minute. Two variables decide whether a task is safe to hand off: judgment and access.
Judgment is about whether the task requires reading a situation — deciding what to say to a family in crisis, weighing whether a missed pledge is a paperwork error or something worth a phone call, choosing which of six people should follow up with a first-time guest. Access is about what the person can see while doing it: nothing but a room number, or every household’s giving history for the last three years. A task can be low-judgment and high-access — printing a list of addresses for mailing labels, say — or high-judgment and low-access, like deciding how to word a delicate email with no names attached. Sort a task by both axes before you decide who touches it, and the assignment usually becomes obvious.
Tasks almost anyone can do
These require little judgment and expose little that is sensitive. They are the easiest wins for freeing up a pastor’s or secretary’s week, and most churches underuse them out of habit rather than necessity.
- Setting up chairs, tables, and signage for a scheduled gathering
- Printing bulletins, name tags, or a room-by-room class roster
- Recording attendance counts a teacher hands in on a slip of paper
- Restocking supplies, updating a shared calendar with already-approved dates
- Taking photos at an event for the newsletter or social media
None of these require reading a person’s history or deciding how to handle a hard conversation. If a volunteer makes a mistake here, the fix is usually a reprint, not an apology.
Tasks that need training, not access
A step up: these require some judgment — knowing what to say, noticing when something is off — but do not require deep access to records. A well-trained volunteer can do these as well as staff, sometimes better, because they have time the pastor does not.
- Making a welcome call to a first-time guest, following a simple script
- Confirming details for an upcoming event with a family already on the list
- Checking in on a class roster for who has not shown up in a few weeks
- Coordinating volunteer schedules for a serving team, once the roles are defined
The training here is mostly about tone and boundaries: what to say if a guest asks a question the volunteer cannot answer, what to do if a call turns into something heavier than a welcome. It does not require handing over the giving ledger or the pastoral care file. Our guide on the path from guest to member walks through where these check-ins fit in a longer follow-up rhythm.
Tasks that touch money
Anything involving giving deserves its own tier, separate from “sensitive information” in general, because money carries a different kind of scrutiny — both from the people who gave it and from anyone who might later ask how it was handled. Recording a contribution, correcting an entry, generating a year-end statement: these are not hard tasks technically, but they should go to someone the church has already agreed to trust with financial detail, usually a treasurer or a small, known team, with a second set of eyes on anything unusual. This is less about ability and more about the fact that the congregation needs to know, if asked, exactly who could see what.
It is worth separating two things that get lumped together here: the act of entering a number, and the judgment of what to do when the number looks wrong. A volunteer who is comfortable with spreadsheets can absolutely enter contributions from a batch of envelopes. But if a household’s giving drops to zero for three months, deciding whether that is worth a gentle check-in call is a different kind of decision, and it belongs with whoever already has the pastoral relationship, not whoever happened to be entering data that week. Keep the mechanical task and the judgment call as two separate assignments, even if the same person ends up doing both.
Tasks that stay with staff or a designated leader
A short list, but an important one. Pastoral care notes, anything involving a family crisis, decisions about how to handle a conflict between members — these need someone who holds pastoral authority or has been explicitly given that trust. It is not that volunteers cannot be discreet. It is that the congregation has not agreed, implicitly or otherwise, that a rotating set of helpers should know their hardest moments. Keep this list short and say it out loud to your team, so nobody is guessing where the line is.
One more thing worth naming: this list is not permanent. A volunteer who has handled welcome calls well for a year may be ready for something closer to the care team. A treasurer who is stepping back may need to hand off the mechanical side of giving entry while keeping the judgment calls for a season longer. Treat the sort as a living decision, revisited every few months, rather than a one-time org chart. Churches that never revisit it tend to either overload the same three people forever, or discover too late that access spread further than anyone meant it to.
The shared-login problem
Here is the part most churches skip: however you sort these tasks on paper, your software has to be able to back it up, or the sorting is theoretical. Many small-church tools, SundayBridge included, run on one login per church rather than individual staff accounts with permission levels. That means whoever has the password can see everything in the system — giving history, care notes, the whole directory — regardless of which task you assigned them.
That is not a reason to avoid using the software. It is a reason to be as deliberate about who gets the password as you would be about who gets a key to the office. If a task genuinely only needs a printed roster or a list of room assignments, hand over the printout, not the login. Save login access for the small circle you have already decided can see the whole picture. Our guide on building a directory your team actually trusts covers how to think about who touches the record itself, separate from who touches a task built from it.
A quick test before you hand something off
Before assigning any admin task, ask three questions: does this require reading a situation and deciding how to respond, or just following a clear set of steps? Does doing it require seeing anything the person is not already trusted to see? And if it goes wrong, is the cost a reprint and an apology, or something that damages trust with a family? Low judgment and low access: hand it to anyone willing. High on either axis: keep it with the smaller circle. Most churches find that far more tasks land in the first category than they expected, once they stop assuming “admin work” is one undifferentiated pile. For a broader look at where this fits into a weekly rhythm, see building a weekly church admin rhythm and keeping a serving team from burning out, which both touch on how delegation either relieves or overloads the people doing it.