The day you buy church management software is not the day it starts helping anyone. That happens weeks later, on an ordinary Sunday, when the greeter checks a guest in without asking someone else how, and the treasurer pulls a giving report without a phone call to last year's volunteer. Getting from the first login to that ordinary Sunday takes a plan, not just enthusiasm.
This is a week-by-week path for a congregation of 60 to 250 people moving onto new software, written for whoever ends up holding the laptop: a bivocational pastor, a part-time secretary, a volunteer treasurer. It assumes you have already chosen a tool and are past the shopping stage. What follows is how to spend the thirty days between signing up and running a normal Sunday on it.
Before day one: decide who owns this
Pick one person to be accountable for the setup, even if three volunteers help with data entry. Not because anyone else cannot be trusted, but because a shared login and a shared decision leaves no record of who decided that households would be named “The Smith Family” instead of “Smith, Robert & Linda,” and six months later two conventions exist side by side. One owner does not mean one worker. It means one person who can answer “why does it look like this?” without shrugging.
Before you touch the software, write down, on paper or in a shared doc, what your church currently tracks and where: the membership spreadsheet, the giving log in accounting software, the serving schedule in a group text. This list becomes your to-do list for the next four weeks. Nothing on it gets forgotten by accident, because it is written down before you start.
Week one: people and households, nothing else
Resist the urge to explore every screen. Spend week one entering people, organized into households, and nothing else. Every other module in the software points back to a person record, so a clean people list on day seven makes every later week faster, while a rushed one makes every later week harder.
- Start with your most current list. A recent attendance sheet or a directory you trust beats a five-year-old membership roll. You are not trying to be exhaustive yet, only accurate for who is actually part of the church right now.
- Decide households before you enter names. If you are unsure how your software distinguishes a household from an individual, settle that question on day one, not day twenty, when you already have forty records built the other way. This is worth reading up on directly — the difference between households and individuals changes how you enter every single record after it.
- Enter by hand, on purpose. There is no spreadsheet import here to lean on, so plan for someone to type records in directly. This sounds slower than it is: it forces a second look at every name, and typos and duplicate entries get caught as you go instead of imported wholesale.
- Leave gaps visible, not hidden. If you do not know a birthday or an address, leave the field blank rather than guessing. A blank field is an honest to-do. A guessed one is a future correction nobody remembers to make.
By the end of week one, you want a people list that is smaller than your full membership roll but accurate for every name on it. A hundred correct households beat two hundred half-right ones.
Week two: giving history and serving teams
With people in place, week two splits into two tracks that can run at the same time if you have two sets of hands: giving and serving.
For giving, decide up front how far back you will enter history. Going back a full year lets you produce a year-end giving statement that matches what a giver expects, but it is real, unglamorous work, usually a treasurer's evening or two rather than an afternoon. Some churches choose to start giving records fresh from the switch date and keep the old system's statements as the historical record. Either choice is defensible. What is not defensible is leaving the decision unmade and drifting into an inconsistent middle ground where some months are entered and others are not.
For serving teams, this is the week to enter roles and current assignments — who is on the welcome team, who is scheduled for the next few Sundays, and whose background check needs a renewal date attached. Do not try to schedule three months ahead in week two. Get the current rotation right first; the scheduling habit comes later, and it is worth reading about how a small church schedules volunteers without burning out the one person who keeps agreeing to fill gaps.
Week three: groups, gatherings, and the follow-up habit
By week three, the foundational records exist, so this week is about building the habits that keep the system honest going forward rather than entering more raw data.
- Groups. Enter your small groups with their current leaders and rosters. Do not wait for a perfect roster; enter who is there now and let the leader correct it once they see their own group listed.
- The next gathering on your calendar. Rather than back-filling a year of past events, create the next real gathering coming up — a potluck, a class, a service project — and use it to test registrations before a bigger Sunday depends on the process working.
- The follow-up habit. This is the week to start treating every guest as a next step with an owner and a date, not a note in someone's head. A guest who is not followed up with did not fall through a crack in the software; the crack was already there. What changes in week three is that someone is now responsible, by name, with a date attached, and the board makes it visible when nothing has happened after a week.
Week four: your first real Sunday on the system
Week four is not about adding more data. It is about running one ordinary Sunday start to finish on the new system and seeing what breaks. Walk through the actual sequence: guests arrive and get entered as new people, attendance gets recorded, a contribution comes in during the offering and gets logged the same week rather than a month later, and any guest who lingered past the service becomes a follow-up with a name and a date attached before the day ends.
Treat this Sunday as a rehearsal, not a verdict. Something will not go the way you expected — a household gets duplicated, a volunteer cannot find the giving entry screen, someone forgets to log attendance until Tuesday. None of that means the switch failed. It means you now know precisely what the next week's training conversation needs to cover, which is more useful than a guess would have been.
Afterward, look at how the week actually went, not how you hoped it would go. If you are unsure what a healthy attendance pattern looks like this early, it helps to understand how to read attendance against its own history rather than comparing week one on a new system to last year's numbers on the old one — the trend line, not the raw count, is what will matter once you have a few months of data behind you.
What to leave for month two
Some things genuinely do not belong in the first thirty days, and naming them out loud keeps the team from feeling like it failed to finish everything.
Full giving history beyond the last year, a completely populated serving rotation three months out, and every small group roster brought current can all wait. So can exploring every report your software offers — twelve reports is a lot to learn at once, and most churches only pull two or three of them regularly at first. Pick the ones you actually need for a board meeting or a treasurer's update, and let the rest wait until someone asks a question that only a different report can answer.
What should not wait is settling into a repeatable weekly rhythm once the first month is behind you — deciding, as a team, when giving gets entered, when follow-ups get checked, and who does it if the usual person is out. That habit is what keeps the records you built in month one from going stale in month three, and a weekly admin rhythm worth building deliberately, not something that happens on its own once the setup rush is over.
A short checklist for the four weeks
If you want a version of this plan to hand to a volunteer, here is the shape of it in one place:
- Before day one: pick one owner, write down what you currently track and where it lives.
- Week one: enter people and households, accurately, even if incompletely.
- Week two: enter giving history back to a decided date, and current serving assignments.
- Week three: enter groups, create the next real gathering, and start the follow-up habit.
- Week four: run one full Sunday start to finish, and write down what broke.
- Month two: settle into a weekly rhythm instead of a setup sprint.
SundayBridge is built around this exact sequence — people first, then giving and serving, then the habits of follow-up and a weekly rhythm — because that is the order a small church actually needs its records in, not the order a feature list happens to be printed in.