Someone in your congregation gets married and takes a new last name. Someone else finalizes a divorce and goes back to the one they had before. A member legally changes their first name. None of these are rare, and none of them should cost the church anything more than a couple of minutes — but it is easy to handle them in a way that quietly breaks the very history you were trying to protect.
The mistake is treating a name change like a new person instead of an edit to an existing one. Do that, and the giving from January through June sits under “Sarah Combs,” while July onward sits under “Sarah Whitfield,” and nobody notices until the year-end statement comes out short, or the volunteer coordinator can't find the person she scheduled last month.
Edit the person, do not create a new one
The rule is simple to state and easy to forget in the moment: a legal name change is an edit to a field on an existing profile, not a reason to add a second record. The person did not stop being the person who gave, served, and showed up under care last year. Only the name printed at the top of their profile changes. Open the existing record, update the name field, save it, and move on. Everything else attached to that profile — every gift, every serving assignment, every attendance mark, every care case — stays exactly where it was, because it was never tied to the name. It was tied to the person.
Why this trips people up
Most of the time the person telling you about a name change is not the person themselves. It is a spouse mentioning it after service, or a card in the offering with a new name on it that does not match anything in your search box. When a quick search for “Whitfield” returns nothing, the instinct is to add a new person named Whitfield. Search for the old name first. If nothing else fits, ask — a quiet word after service is usually all it takes to confirm you have the right person before you touch anything.
What stays attached, and why it matters
Because a person's giving, serving, groups, and care history all live on one profile in SundayBridge, editing the name field does not disturb any of it. The engagement timeline on that profile still reads top to bottom the way it always did — a gift in March, a serving shift in April, a care note in May — just under the corrected name from here forward. That is the whole benefit of keeping one clean record per person instead of letting old and new identities drift apart. A name is a label. The history belongs to the person underneath it.
This matters most at the two moments people actually check the records: a year-end giving statement that needs to show the full year of contributions under one name, and a follow-up call where a volunteer coordinator needs to see who someone was serving with last month without wondering if they are looking at half a person's story.
A short, ordinary process
- Confirm the person before you touch the field. Search the old name, not the new one, since that is what is already on file.
- Edit the name field on that profile. Do not add a new person, even if the search for the new name comes back empty.
- Check for related profiles. A household entry, a group roster, or a serving assignment printed elsewhere may still show the old name until it is regenerated — that resolves itself the next time those views are pulled.
- Leave the history alone. Past gifts, past attendance, and past care notes do not need to be touched, backdated, or re-labeled. They already happened under the person who is still the same person.
When it is a household name, not just a person's
A marriage often changes more than one field. One spouse's last name changes, and the household label your team uses in conversation — “the Combs family” — may change with it. This is where keeping individuals and households as separate layers earns its keep. You update the individual's name on their own profile. If the household display name needs to follow, that is a second, small edit — not a reason to rebuild the household or move anyone's giving between records. The two layers move independently, which is exactly the point of having them.
Names inside groups, teams, and care cases
A profile does not live in isolation — it shows up as a member inside a group roster, as a volunteer inside a serving team, as the subject of a care case. When you edit the name field on the person's own profile, every one of those places that pulls from the same record updates along with it, the next time it is viewed. You are not hunting down every list the person's name might appear on and fixing each one by hand. That is exactly the value of a directory your team can actually trust — one edit, made once, in the one place that matters, rather than a dozen small fixes scattered across spreadsheets and printed rosters that all have to be remembered separately.
The exception is anything printed on paper before the change. A serving schedule handed out last Sunday still has the old name on it, and that is fine — nobody expects a printout to retroactively update itself. The next time that schedule is generated, it reflects the current record. The gap between an edit and the next printed copy is normal and does not need to be treated as an error.
A quick sanity check after the edit
Once you have made the change, it is worth thirty seconds to confirm nothing split. Pull up the person's profile and scan the engagement timeline: does it still show the full run of history, old and new, in one place? If a gift or a serving shift from before the change seems to be missing, you likely have a second, duplicate profile sitting under the old name somewhere. That is worth catching now, while you still remember why the person's name changed, rather than months later when a report quietly undercounts what they have given.
Where a name change surfaces first
In practice, a name change rarely arrives as an announcement. It shows up sideways: a check comes in with a new signature, a volunteer sign-up sheet has a name your search box does not recognize, or someone mentions offhand that they go by something different now. Whoever notices first is often not the person who manages records, which means the note can sit for a week or two before anyone acts on it. That gap is fine as long as nothing gets entered under the wrong name in the meantime — a gift logged under a name that no longer matches the person's profile is the single most common way a duplicate gets created by accident.
It also helps to think about who else might need to know. A serving team leader printing a schedule, a small group leader with a roster on paper, a greeter who has known someone by their old name for years — none of that needs to change overnight, and none of it should trigger a scramble. The record is the source of truth; the humans around it catch up at their own pace, the way they always do with any personal change.
A word on sensitivity
Not every name change is a happy one. A divorce, a name someone is leaving behind for reasons they would rather not explain, a name tied to a season of their life they are done with — these deserve the same quiet, unremarkable handling as a marriage does. The record does not need a comment explaining why. It needs the new name entered correctly and the old one to stop appearing anywhere a person might see it and have to explain themselves again. Treating the edit as routine, rather than as an event, is itself a kindness.
The habit behind the edit
None of this requires special training or a checklist taped to the monitor. It requires one habit: search before you add. That single habit, applied consistently, is most of what keeps a database from slowly filling with duplicate people who are really the same person wearing a different name. It is a small thing on any single Sunday and a real difference after ten years of Sundays.
If your church is still catching up on a backlog of name changes, address updates, and other small edits that piled up during a busy season, it is often easier to work through them as one pass rather than one at a time — the same discipline covered in cleaning up a church database.