Handing off a task is the easy part. You ask, someone kind says yes, and for a week or two it gets done. The hard part is three months later, when you can't remember if the visitor cards from two Sundays ago ever got entered, or whether the volunteer who used to update the directory is still doing it, or just being too polite to tell you she stopped.
Most small churches don't fail at delegating admin work because volunteers are unwilling. They fail because the handoff has no visible finish line — nothing that shows the task was done, or that it wasn't. What follows is a way to hand off recurring office work so you can actually tell, at a glance, what happened to it.
Delegate the task, not the judgment
The tasks that hand off cleanly are the ones with an obvious right answer: type in the name from this card, print these forty name tags, pull the roster for Sunday's class. There is one correct outcome, and anyone careful can reach it without needing to know the family, the history, or the politics behind it. That is what makes them safe to hand to someone who isn't on staff — the task is mechanical, not judgment-laden.
The tasks that quietly go wrong are the ones with a judgment call buried inside them — deciding whether a visitor counts as a repeat guest or a first-timer, deciding how to phrase a note about a sensitive family situation, deciding whether a giving correction needs a second look. Keep those with someone who has the context to make the call. A volunteer shouldn't have to guess at something you would want to weigh in on yourself, and asking them to guess is unfair to them as much as it is risky for you. When in doubt, hand off the parts of a task that are pure transcription and keep the parts that require knowing the church for yourself, at least until the volunteer has been doing it long enough that you would trust their judgment on the edge cases too.
Write the task down before you hand it off
“Can you enter these when you get a chance” is an instruction that dies with the person who gave it. If you are out sick, or the volunteer forgets, or a new person takes over in six months, nothing written down survives the handoff. It doesn't need to be a manual — three or four lines is usually enough:
- What the task is, in one sentence.
- Where the source material lives (the box of cards, the sign-up sheet).
- What “done” looks like.
- Who to ask if something is unclear.
This is the same instinct behind a good weekly admin rhythm — a task that lives on a fixed day and a written line is a task that survives turnover. One that lives only in your head is not. Writing it down also forces you to notice, before you ever hand it off, whether the task actually is simple enough to delegate. If explaining it takes a full page and three exceptions, that is a sign the task has more judgment buried in it than you realized, and it may need to stay with you a while longer, or be broken into a smaller piece that really is mechanical.
It helps to physically keep these instructions somewhere a volunteer can find them without asking you — a shared folder, a printed sheet in the same box as the visitor cards, a page in whatever system you use for notes. The goal isn't polish. It's that the instructions outlive the conversation where you first explained them, so a new volunteer six months from now can pick up the same task without you having to teach it a second time.
Give every recurring task an owner and a date, not a hope
“Someone should keep the directory updated” is not an assignment; it is a wish. A task only reliably gets done when one named person has it and there is a rhythm to when it happens — weekly, monthly, after every event. If three volunteers are all vaguely responsible for updating addresses, none of them is, and you will find out the hard way when a mailing bounces.
The same logic that makes a follow-up after a big Sunday actually happen — an owner and a date on every next step — applies just as well to office work. A task with a name and a deadline attached to it is a task you can check on later. A task everyone is supposed to remember is a task no one does. This is worth saying plainly because it runs against instinct: asking one specific person feels like putting them on the spot, while asking the group feels generous and low-pressure. In practice it is the opposite. Asking the group diffuses the responsibility so thoroughly that no one feels it land on them, and the task simply doesn't get done. Asking one person, with a clear scope and a real date, is usually the kinder move — it tells them exactly what is expected and when they are done, rather than leaving a vague obligation hanging over everyone indefinitely.
Build in a way to see what got missed
The real risk in delegating isn't that a volunteer will do a task badly. It's that a task will quietly stop getting done and nobody will notice for a season. If the only record of a task's status is in someone's memory or a text thread scrolled past, there is no way to look and see what is overdue — you only find out when something breaks, like a giving statement nobody prepared or a class roster nobody printed.
SundayBridge's follow-up board gives every next step an owner and a date, and it ages anything nobody has picked up — so a task that has gone quiet is visible, not invisible, before it becomes a problem. It won't assign the task for you or nudge the volunteer by text; that conversation is still yours to have.
Decide in advance what “done” means
A surprising amount of friction around delegated tasks comes down to a simple mismatch: the volunteer thinks they finished, and you think they didn't, because neither of you defined the finish line the same way. Entering visitor cards might mean, to you, that every card is in the system with a phone number and an address if one was given. To the volunteer, it might mean every card they could read clearly is entered, and the three with messy handwriting are set aside for later — which sounds reasonable, except now there are three visitors nobody is following up with, and neither of you knows it.
Spell out what “done” looks like when you hand the task off, not after something falls through the cracks. It doesn't need to be elaborate — one sentence usually does it: every card entered, or flagged and set aside if something is missing or unreadable, with the flagged ones brought back to you rather than quietly skipped. That one sentence closes the gap between a task that feels finished and a task that actually is.
Match the task to the trust, not just the availability
The volunteer with the most free time on a Tuesday afternoon is not automatically the right person for every task. Data entry involving people's addresses and giving history calls for someone you already trust with sensitive information, not just someone available. It is worth being slightly slower about who you ask in exchange for not having to worry later about who has seen what.
Worth naming plainly: most small-church software, SundayBridge included, has one login per church and no way to wall off what a volunteer can see once they are in. There is no setting that lets someone update addresses but not view giving history. Until that changes, the safeguard is who you choose, not what the software restricts.
Expect the task to need a new owner eventually
Volunteers move, get busier, or simply lose the thread on a task they once did faithfully. That is not a sign the handoff failed — it is the normal life span of a volunteer role. Build a habit of glancing at recurring tasks once a month rather than assuming silence means everything is fine. A short, kind check-in — is this still workable for you — usually surfaces the truth faster than waiting for something to visibly break, and it keeps the handoff from turning into the kind of quiet mess a database accumulates when nobody is minding a task anymore.
Start with one task, not a reorganization
It is tempting to hand off five tasks at once to finally get the admin load off your desk. Resist it. Pick the single task costing you the most time relative to how simple it is to explain — printing name tags, entering visitor cards — write the three lines it needs, name an owner and a date, and watch how it goes for a month. What you learn from that one handoff — where it breaks, what wasn't clear, how often you have to check on it — will tell you far more about what the next one needs than any amount of planning up front.