Somewhere in your database there is a person who exists twice. Not as a mistake anyone made on purpose — a guest card filled out as “Kathy Lane,” a follow-up entered three weeks later as “Katherine Lane,” and now two records quietly split her attendance, her giving, and the fact that she is on the greeting team between them. Neither record is wrong. Neither one is complete either.
Finding these takes no special tool, just a method and the patience to work through your list once with fresh eyes. Here is a way to do it by hand that catches most of what matters without turning into a weekend project.
Start with a plain alphabetical read
Sort your people list by last name and read it top to bottom, the way you would proofread a page. This sounds too simple to work, but it catches the largest category of duplicates on its own: two entries sitting one line apart, spelled almost the same way. “Jon Reyes” and “John Reyes.” “Steven Park” and “Stephen Park.” Your eye catches these faster than any search box, because it is looking at the shape of the name, not matching exact characters.
Do this pass slowly. Ten minutes on a church of 150 people is usually enough to flag five or six candidates worth a second look.
Then sort by phone number and by email
Names hide duplicates that contact information gives up immediately. Sort the same list by phone number, and two people sharing one number — often a landline entered under both a husband's and a wife's name years ago, or the same cell number typed in twice under a maiden and married name — will sit right next to each other. Repeat the sort by email address. A shared email is one of the strongest signals you will find, since it is far less likely to be a coincidence than a shared last name.
If your list lets you export to a spreadsheet, this is where a CSV export earns its keep: three sorts in a spreadsheet find in minutes what an unsorted screen of names would take an hour to catch by scrolling.
Watch for the specific patterns that cause most duplicates
- Nicknames versus formal names. Bob and Robert, Liz and Elizabeth, Mike and Michael. These are the single most common cause, because two different volunteers, on two different Sundays, each typed the version the person happened to introduce themselves by.
- A name change after marriage. Someone attends single, then reappears under a married name a year later with no one connecting the two records.
- A typo that survived. An extra letter, a swapped vowel, a last name spelled two ways on two different forms.
- A kid who grew into an adult record. A child entered once in a household as a minor, then entered again as their own adult profile when they joined a serving team, with the old entry never retired.
Try a few deliberate near-misses on purpose
Once the obvious pairs are handled, it helps to spend a few minutes testing names you suspect but have not confirmed. Search the last name alone rather than the full name, since a search for “Jonathan Reyes” will not surface “Jon Reyes” even though they are the same person. Search common shortened forms deliberately: if you have a Christopher, search Chris too. If you have a Katherine, search Kathy, Kate, and Katie. This feels slow the first time through, but it is the difference between finding the duplicates that happen to sit next to each other alphabetically and finding the ones that do not.
It is also worth checking address fields where you have them. Two people at the same street address with different last names is sometimes a household you have not connected, and sometimes it is the same person entered once under a maiden name and once under a married one after a move was recorded under the new name but the old record never got flagged. Either way it is worth a look, not a guess.
Check history before you merge, not after
Before combining two records, look at what each one is carrying. Attendance on one, a serving assignment on the other, a giving entry on a third-seeming variant you almost missed. The point of merging is to end up with one record that has all of it — not to pick the tidier-looking entry and lose what the other one held. Keep the record with the deeper history as the one you merge into, and confirm nothing on the losing record gets left behind.
This is also the moment to decide whether you are looking at a true duplicate or a household matter instead — two adults who are genuinely two people, just linked. If that distinction feels blurry, it is worth reading households versus individuals before you start merging, since the wrong call there creates a different kind of mess than the one you are trying to fix.
Work the list once, then build a habit against new ones
A single careful pass through your current records will find most of what is hiding. The harder problem is keeping new duplicates from forming the next time a guest fills out a card under a slightly different spelling of a name already in your system. There is no software trick that replaces a person pausing to check “does this name look familiar” before adding someone new — but a light weekly habit of reviewing new entries catches it early, before a duplicate has three Sundays of history attached to it. That habit fits naturally into a weekly admin rhythm rather than a separate project of its own.
The habit is simple even if nobody writes it down as a policy: whoever enters a new guest or new attender takes five extra seconds to search the last name first, before typing a new profile from scratch. Most duplicates are created in that single moment of not checking, and most of them are prevented in that same moment by checking. It is a smaller ask than it sounds, and far smaller than the alphabetical read-through you would otherwise be doing again in another year.
It also helps to give one person clear ownership of this, even in a small church where most jobs are shared. A record with no one responsible for it tends to accumulate duplicates quietly, because everyone assumes someone else already checked. A record with one named person watching it — even if that is the same volunteer who handles follow-up or serving schedules — tends to stay clean, because the checking is now somebody's job rather than nobody's.
In SundayBridge, each person is one profile carrying their groups, serving, giving, and care history together, so once you find a duplicate, merging it is a single deliberate edit rather than a hunt across separate tabs for attendance here and giving there — but spotting the duplicate in the first place is still the part only a person doing this kind of read-through can do.
Do not let the search discourage you
It is easy to feel discouraged the first time you sit down and find eleven duplicates in a church of 140 people. That number sounds like evidence of neglect, but it is really just the ordinary residue of several years of guest cards, follow-up entries, and well-meaning volunteers each doing their small part without a full view of what was already there. It is not a sign anyone did anything wrong. It is a sign the church has been reaching new people long enough for the records to accumulate the normal wear of that.
Treat the count as a starting number, not a verdict. Merge what you find this week, note anything you are not sure about for a second look, and move on. The list gets shorter every time someone runs this same read-through, and it stays short once the five-second habit of checking before adding becomes normal for whoever handles new people.
Duplicates are a symptom, not the whole problem
If you are finding more than a handful of duplicates, it is worth treating this as one pass in a larger cleanup rather than the whole job. Dead phone numbers, people who left years ago and were never retired, and inconsistent formatting tend to travel together with duplicate names. The full walk-through in cleaning up a messy church database covers those other passes in the order worth doing them.
Whatever you find, the payoff is the same reason any of this is worth the time: a directory the team actually reaches for instead of double-checking, because it has learned the record cannot be trusted. That trust is really what you are cleaning up when you merge Kathy and Katherine back into one person.