People

A once-a-year cleanup checklist for your church database

One afternoon, five passes, and a directory your team trusts again for another year.

7 min read

Ask AI · in the $19/mo plan

Ask your own records a question. Who visited in the last month, and did anyone follow up?” — answered from the records you already keep. It reads your church and no other, and it can't invent a number.

10 questions a month included · no AI add-on to buy

Most churches do not need a cleanup schedule. They need one afternoon, once a year, where someone sits down with the database and works through it in order. Not a renovation. Not a committee. One person, a checklist, and three or four hours before the coffee gets cold.

The trick is treating it like a checklist and not a mood. Cleanup work has no natural stopping point — you can always find one more phone number to double-check — so the only way to finish is to define the passes in advance and stop when you have done them. Here is the order that works.

Pick a date and put it on the calendar

This sounds obvious and it is the step almost everyone skips. “We should clean up the database sometime” is a sentence that produces nothing. A specific afternoon, named on the calendar, with one person's name attached, produces a cleanup. Late summer or early January both work well — after a season change, before you pull year-end giving statements, while last Sunday's first-time guests are still fresh enough to sort correctly.

Pick a slow week if you can. The point of scheduling this in advance is not ceremony — it is that a task with no deadline competes with everything else that has one, and it always loses. A named afternoon three weeks out beats an open-ended intention that never quite finds its moment. Tell whoever else touches the database that you are doing this, too, so nobody is entering new records mid-cleanup and undoing your work.

It also helps to decide, before you start, what “done” looks like. Not perfect — done. A reasonable definition is: every obvious duplicate merged, everyone inactive for a year or more retired, and the five worst pieces of broken contact information fixed. Anything beyond that is a bonus, not a requirement. Chasing the last percent of tidiness is how a three-hour job becomes a project nobody finishes.

Pass one: hunt the duplicates

Start here because everything downstream depends on it. A duplicate splits one person's history into two thin ones — half their attendance under “Bob Smith,” half under “Robert Smith,” neither telling the whole story. Sort the directory by last name and scan for near-matches: same last name plus a shared phone number or email is almost always the same person entered twice, once by the old system and once by whoever typed it in from memory.

When you find a match, do not delete either record. Pick the one with more history — more attendance, more giving, more notes — and fold the other one's details into it by hand: any phone number, email, or note the thinner record has that the fuller one is missing. Then retire the thinner record rather than erasing it, in case anything was missed. This single pass, done carefully, fixes more than any of the others.

Some duplicates are less obvious than a shared last name. Watch for a maiden name still on file after a marriage, a nickname entered as if it were a separate person — “Bill” and “William” under the same address — and a household where one adult was somehow entered twice under two different email addresses. None of these are hard to fix once you see them. The work is in seeing them, which is why this pass benefits from a person who actually knows the congregation, not just someone comfortable with spreadsheets.

A church of 120 people typically turns up somewhere between two and eight duplicate pairs in a year, mostly from guests who filled out a card twice, or from a name entered by two different volunteers on two different Sundays before anyone checked whether it already existed. That is a normal amount of drift, not a sign anyone did anything wrong. It is simply what happens when more than one person can add a record.

Pass two: retire the people who have moved on

Next, look for people who have not shown up, given, or served in a long stretch — a year is a reasonable line for most churches. The instinct is to delete them and tidy the count. Resist it. Deletion throws away attendance and giving history you may need for tax purposes or for a former member who calls asking about a past statement. Mark them inactive instead. They drop out of your active lists and your attendance numbers stop counting them, but the record survives if they ever walk back in the door, which happens more often than people expect.

Use a plain rule to decide who qualifies, not a feeling. “No attendance, no giving, and no serving record in the last twelve months” is easy to apply consistently and easy to defend if someone asks why a name is missing from the directory count. Without a rule, this pass turns into a series of individual judgment calls about people you may or may not remember well, which is slower and more prone to guilt than it needs to be.

One exception is worth naming: someone in an active pastoral care case should stay visible even if their attendance has dropped, since the point of that record is ongoing care, not activity. Retiring them from the directory count is fine; losing track of the care history is not.

Pass three: fix the contact details you can actually verify

Now work through what is left and fix what you can confirm. A phone number that bounces on a text, an email that bounces back undelivered, an address for a family that moved — these are worth five minutes each because a volunteer will trust the whole directory a little less every time one of them fails. You do not need to verify every field for every person today. Fix what is clearly broken and leave a note on anything you are unsure about, so next year's pass has a head start instead of starting from zero.

A short list beats a long one

If you only have an hour left after the first two passes, prioritize phone numbers over email, and email over mailing address. A wrong phone number gets discovered the next time someone tries to call about a missed follow-up; a wrong mailing address might not surface for a year. Fix the thing that will get used first.

A quick way to find broken phone numbers without calling every one: check for anything with the wrong number of digits, an obviously stale area code for a family you know moved, or a number identical to another household's — often a sign someone copied a neighbor's number by mistake years ago and it was never caught. These are the low-hanging errors, and there are usually more of them than you expect once you go looking on purpose instead of noticing them by accident.

Pass four: check the follow-up board and the groups list

The directory is not the only place drift hides. Walk the follow-up board and close out anything that has clearly already been handled but never got marked done — a guest who is now a regular, a call that was made three months ago. An honest board is worth more than a full one, the same principle covered in the path from guest to member. While you are at it, check your groups for members who quietly stopped attending; a small group roster that still lists someone who left in the spring undersells the group's real size to its own leader.

This is also a good moment to check serving teams, particularly for anyone flagged for a background-check renewal. A yearly cleanup pass is a natural trigger to notice an alert that has been sitting on the dashboard for months, easy to miss during a normal week but obvious once you are already reviewing every list in the system.

Pass five: write down what you found

Before you close the laptop, jot three lines: how many duplicates you merged, how many people you retired, and anything that took longer than expected. This is not for a report nobody reads. It is so that next year's version of you, or whoever inherits the job, knows roughly what to expect and is not surprised by the time it takes. In SundayBridge, each person is one profile carrying their household, groups, and history together, which makes a merge a single deliberate action rather than a hunt across five different screens — but the judgment calls, which Bob is really which, who has truly left, still belong to whoever is running the cleanup.

Keep the next one smaller

The best outcome of an annual cleanup is that next year's is shorter. That only happens if small errors get caught between now and then instead of piling up quietly for twelve months. A light weekly rhythm — five minutes to fix an obvious typo when someone notices one — does more for the health of your directory than any single afternoon can. The annual pass is the safety net; the weekly habit is what keeps you from needing it as badly.

Frequently asked questions

How long should this actually take?
For a church of 60 to 250 people, budget one afternoon — three to four hours. Most of that time goes to pass one, the duplicate hunt, since it requires judgment calls a computer cannot make for you. The remaining passes are faster once the hard thinking is done. If you run out of time, stop after pass three and finish the rest next week.
Do we need to do this every single year, even if nothing looks wrong?
Yes, and especially then. A record that looks clean is often just a record nobody has looked at closely. New duplicates, stale phone numbers, and people who quietly stopped coming accumulate whether or not anyone notices. The annual pass is what keeps small drift from becoming a project nobody wants to touch.
Who on our team should own this?
One person, named in advance, not “whoever has time.” It does not need to be the pastor. A part-time secretary or a volunteer with an afternoon and some patience is enough. What matters is that the task has an owner and a date on the calendar, the same discipline you would use for any follow-up that tends to get dropped.
What is the single most common mistake in a yearly cleanup?
Deleting people instead of retiring them. It feels tidier, but it erases attendance and giving history you may need later, and it makes it look like someone was never part of the church at all. Almost everything you are tempted to delete should instead be marked inactive, with the one exception being true duplicates and test entries.
Should we do this before or after we pull our year-end giving statements?
Before, if you can manage it. A duplicate record splits someone's contributions in two, which means a statement that undercounts what they gave. Running the cleanup first, then generating statements, saves you from issuing a correction later and having to explain the discrepancy to a giver.