The volunteer who has run your church's records for the last three years just told you she is stepping back. Maybe it is a move, a new job, a season of caregiving, or just burnout from being the only one who knows where anything is. Whatever the reason, the records do not stop needing attention the day she leaves — and the next person is not trained yet, might not even be identified yet. That gap, not the departure itself, is where things quietly go stale.
The good news is that the gap is manageable if you plan for it like a bridge rather than a hole. A guest who does not get followed up with for six weeks, a giving entry that never gets recorded, a serving schedule nobody checked before Sunday — none of that has to happen, even with no permanent owner in place yet. Here is what actually needs attention in the gap, and what can honestly wait.
The first week: name what cannot go stale
Not everything decays at the same speed. Some records can sit untouched for a month with no real damage. Others rot within days. In the first week after a volunteer leaves, focus only on the fast kind:
- The follow-up board. A guest who visited two Sundays ago and has no owner assigned is the single most perishable thing in a small church's records. If the board ages past a week or two with nobody picking items up, reassign the open items to someone by name — even the pastor, even temporarily.
- Giving that still needs to be recorded. A stack of checks or an envelope from last Sunday should not sit for three weeks because no one has the habit yet. Someone needs to enter it, even roughly, even if the polish comes later.
- Whatever is on the calendar this month. A gathering with registrations open, or a serving schedule with gaps, needs a human glancing at it weekly. Nothing about a volunteer leaving pauses the Sunday that is three weeks out.
Everything else — a messy field here, a household that needs merging, a report nobody has looked at in months — can wait. Do not let the urgency of the transition convince you that everything is urgent. It is not, and treating it that way is how the person filling in burns out before the real replacement even starts.
The login problem nobody plans for
Most software built for a congregation of this size has one login per church rather than separate staff accounts — there is no concept of restricting what one volunteer can see versus another. That is a real limitation, and it means the handoff is not just about training. It is about a password that lived in one person's head, or her browser's saved passwords, actually getting written down somewhere a second person can find it.
This does not need to be dramatic. It is not a locksmith-changes- the-locks situation. But it is worth doing on purpose, once the departure is clear, rather than discovering three months later that the only person who knew the password has moved across the country and stopped answering emails. Write it down. Tell one other person where it is written down. That is the whole fix.
What the interim person actually needs to know
If there is a gap before a permanent replacement is trained, resist the temptation to hand the interim person a full manual. They do not need to understand every screen. They need three things: where the follow-up board is, how to add a giving entry, and where the calendar lives. That is enough to keep a church of 80 or 150 people from losing anything important for a month or two.
The weekly rhythm matters more here than any feature does. A short, repeatable pass — the same one your last volunteer probably did without thinking about it — is what keeps the gap from turning into a backlog. If that rhythm was never written down, this is the moment to write it down, and a weekly rhythm your records can survive is a reasonable place to start, whether the interim person keeps it forever or hands it to the next volunteer in three months.
An export is not a plan, but it is cheap insurance
Before a departure, it is worth taking two minutes to export a CSV of the directory — names, households, contact information — and saving it somewhere outside the software entirely. This is not because the records are at risk of disappearing. It is a dated snapshot that costs almost nothing and means that even in the strangest handoff, where the departing volunteer is unreachable and the next one has not started, someone can still see who the church is caring for. Treat it like a habit, not a fire drill: export occasionally, whether or not anyone is leaving.
What an export cannot do is replace the record itself — it will not stay current, and it does not carry giving history, serving assignments, or the follow-up notes attached to each person. It is a backup for the worst case, not a working copy for the gap.
Training the replacement without starting from zero
When the next volunteer is finally identified, the temptation is to sit them down and explain everything at once. That rarely sticks. What sticks is showing them one real person's record — a household, their groups, their serving history, the notes attached to them — and letting that be the model for how everything else works. If the directory is a place your team already trusts, the new volunteer is inheriting something coherent rather than a pile of half-finished entries from three different eras of church admin.
If the records were already a little messy before the departure — duplicate people, half-filled fields, contacts nobody has confirmed in years — do not ask the new volunteer to fix that in week one. Cleanup is its own project, best done deliberately rather than as an accidental side effect of onboarding someone new. When the time comes, cleaning up the database is worth doing as a separate, bounded task.
The real fix is a second person, not a better handoff document
Every version of this problem — the gap, the password, the training curve — traces back to the same root cause: one volunteer was the only person who understood how the records worked. That is common in a church of 60 to 250 people, where there is rarely budget for a full-time administrator, but it is worth naming as the thing to fix for next time, not just this time.
It does not take a second full-time volunteer. It takes one other person — a pastor, a board member, a spouse — who runs the weekly rhythm once a quarter as a backup, enough to know where things live if the primary volunteer disappears without warning. SundayBridge keeps the follow-up board, giving, and the calendar in one place precisely so that a backup person can glance at three screens instead of learning five separate systems cold. It will not decide who the backup person is, and it will not run the rhythm for anyone — that part is still a decision a real person has to make, this time and the next time someone leaves.
If your church is still working off spreadsheets and a volunteer departure is what finally forced the question of whether to change that, it is worth reading moving your church off spreadsheets before you decide. A transition is a reasonable moment to fix the system, but it is also a reasonable moment to simply stabilize what you have and revisit the bigger decision once the gap is closed.