Most churches that try to launch a database do it over a single weekend, run out of energy by Saturday afternoon, and quietly go back to the spreadsheet on Monday. The problem usually is not the tool. It is the plan — or the lack of one. Thirty days, broken into four weeks with one goal each, is enough time for a volunteer with a day job to actually finish, and short enough that the project does not drift into next year.
This is a week-by-week plan for getting a small church’s records into working shape: people first, then the front door, then giving and serving, then the habits that keep it all alive. Each week has a single job. Do not start week two’s job in week one just because you have momentum — that is exactly how these projects stall.
Week 1: get the people in, not perfect
The only goal this week is a working list of households. Not a clean one. Not a complete one. A working one. If you are coming from a spreadsheet or a card file, this is the week you sit down — probably more than once — and enter names, in order of who shows up most often.
There is no shortcut here that a small church can afford. SundayBridge does not import a spreadsheet for you; there is no CSV import feature to lean on. What it will do is take your file off your hands and enter it by hand at no charge, which is worth asking for if your list is more than a couple hundred rows. For most congregations of 60 to 250, though, a volunteer typing while watching TV in the evening gets through the regular attenders in a few sittings.
Decide up front whether you are entering households or individuals, because that choice shapes how everything else looks later — giving statements, directory searches, who counts as a family unit at Christmas. Our guide on households vs. individuals walks through the tradeoffs if you have not settled that yet. Whatever you choose, do not stop to fix every typo or missing phone number this week. That is a different job, for a different week.
Week 2: teach the front door
With a working directory in place, week two is about the moment a guest walks in. This is the highest-leverage habit a small church can build, and it is the one most likely to get skipped once the initial excitement of a new system wears off.
The job is simple to describe and easy to let slip: every visitor becomes a follow-up entry with a name attached and a date attached, before the greeter who talked to them goes home and forgets. A follow-up with no owner and no date is not a follow-up. It is a name that will surface again in six months when someone asks “whatever happened to that family that visited in the spring?” and nobody remembers.
Spend this week walking your greeting team through exactly what to do after a conversation with a first-time guest: who enters the name, who gets assigned the follow-up, and how soon. If you want the fuller path from a first visit to an active member, our guide on the guest-to-member path lays out the stages in between. The goal for week two is narrower — just get the habit started, with real owners and real dates, for whoever walks through the door this month.
Week 3: giving and serving catch up
Week three moves to the two areas that carry the most trust and the most liability if they are handled loosely: money and volunteers. Start entering contributions as they come in, rather than trying to backfill a year of history in one sitting. A treasurer recording last Sunday’s offering Monday morning, week after week, builds a giving record that is actually usable when statement season arrives — and it is far less painful than reconstructing twelve months of history from paper slips in December.
At the same time, get your serving teams into the system: who is on the worship team, who runs the nursery, who has a background check on file and when it expires. A church of 120 with 8 people serving in rotating roles does not need a complicated structure — it needs the roster to exist somewhere other than one person’s memory, with alerts on the dashboard when a check is coming due.
This is also the week to note who is carrying too much. If the same three names are on every serving list, that is worth seeing in week three rather than discovering it in a burned-out volunteer’s resignation in March.
Do not treat these two jobs as separate projects handed to separate people with no overlap. The treasurer entering giving and the volunteer coordinator building serving rosters both benefit from looking at the same household record — the person who gives faithfully and the person who serves faithfully are often the same person, and a database that shows both side by side is more honest about who is actually carrying the church than two separate spreadsheets ever were.
Week 4: reports, care, and the habit that outlasts the launch
By week four the directory has weight, follow-up has a rhythm, and giving and serving are current. This last week is about looking at what you have built and deciding how it gets maintained after the 30 days are over.
Spend part of the week in the reports that already exist rather than trying to build new ones — there are twelve across attendance, giving, groups, serving and care, and most churches find two or three that answer the questions leadership actually asks, like which groups have grown quietly or which givers have gone silent. These are read-only views built for checking in on, not screens for adding new records; attendance history and Sunday school rosters work the same way. Reporting is where a database starts paying you back instead of just holding data.
This is also the week to set up pastoral care as its own quiet lane — cases with a comment and a history, kept separate from the general directory, for the situations that need discretion rather than a follow-up owner and a due date.
Before the month closes, decide who owns the ten or fifteen minutes a week this now takes on an ongoing basis. Our guide to the weekly church admin rhythm is built for exactly this handoff moment — the plan that keeps a database alive after the launch excitement fades.
What to deliberately skip in the first 30 days
A plan this short only works if you are equally clear about what you are not doing yet. Do not try to build staff permissions or restrict what a volunteer can see — there is one login per church, and that is not a gap to engineer around in month one. Do not expect the system to send emails or text messages to your congregation; nothing here sends anything on your behalf. Do not plan around online giving or a check-in kiosk for children — giving gets recorded here, not processed, and check-in for kids is not part of what this handles.
None of that is a criticism of your first month’s scope. It is permission to leave those questions for later, rather than letting them stall week one while you research features you do not need yet.
The same discipline applies to groups. Create the groups that already meet — a Tuesday men’s study, a Wednesday youth night, a small group that has been gathering in someone’s living room for years — and attach the leader and the members you already know. Do not spend week one or two trying to invent new groups the database might make possible. Record what is real first. New structure can wait until the basics are steady.
Why a 30 day plan beats a weekend sprint
The churches that stall are usually the ones that tried to do everything at once: enter every person, clean every record, teach every volunteer, and pull every report in a single Saturday. By Sunday afternoon the excitement is gone and the spreadsheet quietly comes back out on Monday because it is familiar, even if it is worse.
Four weeks, one goal each, is slow enough to survive a bivocational pastor’s actual calendar and short enough that it does not become a project that never ends. If you moved off a spreadsheet recently and are looking for the fuller case for why that move is worth the friction, our guide on moving your church off spreadsheets covers the reasoning in more depth. This plan is the practical follow-on: the month it actually takes to make that move stick, in SundayBridge or in whatever your church ends up using.