A wedding is one Sunday, or one Saturday afternoon in a fellowship hall with folding chairs, but the record it leaves behind is not a single edit. It is a small sequence: a name, a household, sometimes an address, sometimes a second record that now needs to become part of the first one. Skip a step and the directory tells a story that is three-quarters true — right last name, wrong household, old address still sitting there from a rental she moved out of in June.
None of this is complicated on its own. What makes it easy to get wrong is that the edits arrive at different times, from different people, and nobody is looking at the whole sequence. The pastor hears about the engagement. The check-in volunteer notices the new last name on a name tag. The secretary is the one who eventually has to sit down and make the record match reality. This is the order that actually works.
Start with the name, and get the spelling from her, not the program
The wedding program is not a legal document. It might say “Sarah Whitfield Cole” when the name she actually chose to go by is “Sarah Cole,” middle name dropped, or she is using her maiden name as a middle name and nothing else. The safest way to update the name field is to ask her directly, ideally with a text or a quick conversation, rather than transcribing it off decorations or a bulletin. This matters more than it sounds like it should — a name typed slightly wrong at this stage tends to stay wrong for years, because nobody double-checks a name field that already has something in it.
While you are in the record, decide what to do with the old name. Some churches keep it as a note (“formerly Sarah Whitfield”) so that an old giving envelope or a member from years back who still says “Sarah Whitfield” from the pulpit doesn't confuse the person looking her up. Others just overwrite it. Either is fine. What is not fine is a search for her married name turning up nothing because the old name is still the only one on file.
Then the household — this is the step people skip
A name change is visible. A household change is not, which is exactly why it is the step that gets missed. Before the wedding, she was probably attached to her parents' household, or living alone as her own household of one. After the wedding, she needs to be moved into a household with her new spouse — either merged into a household he already had in the system, or a brand-new household created for the two of them.
This is not cosmetic. Households are what your directory, your giving statements, and your care team lean on to understand who actually lives with whom. If she stays attached to her parents' household, a mailing meant for “the Whitfield family” keeps including a daughter who has not lived there in a year, and a pastoral care note about her new husband's surgery never surfaces next to her name because the system still thinks they are unrelated people.
Household structure is worth understanding on its own if this is the first wedding you have processed since setting up your database — the rules for who belongs to which household are not always obvious, and a marriage is the single most common event that forces the question.
Check whether you now have two records for one person
This is the trickiest part, and it only comes up sometimes. If the new spouse was already in your system before the wedding — visiting for a year, coming to a small group, showing up as a guest a handful of times — you may now have two separate person records that both need to point at the same household: hers, freshly updated, and his, which existed independently before either of you thought to connect them.
The fix is not to delete one and hope the other catches everything. Look at what each record is carrying — giving history, a serving assignment, a pastoral care note, an attendance history — and make sure nothing gets orphaned when you consolidate them into one household. If your church has been keeping loose or duplicate records for a while, this is also a good moment to do a broader pass rather than fixing just this one couple. A general cleanup pass catches the other duplicates that a wedding just happened to expose.
Update the address, and check who else is attached to it
If the couple is moving in together, one of two addresses in your system is now wrong. Update it to the new shared address, and while you are there, check who else was listed at either of the old addresses. It is common for a roommate, a sibling, or a parent to still be tagged to an address that only one person actually lives at anymore. This is a two-minute check, but it is the kind of thing that never gets done unless someone decides, in the moment, to actually look.
If the couple is not moving — she is moving into his existing place, say — you still want to remove her old address rather than leave two current addresses sitting on one person's record. A directory that shows a stale address next to a current one is confusing the first time anyone tries to mail something or drop off a meal after a baby is born.
Decide what belongs in the engagement timeline and what does not
Most church databases keep some kind of running history on a person — when they joined, when they started serving, notable pastoral moments. A wedding is worth a line in that timeline: it is real information, and it helps whoever looks at the record next understand why the household changed shape on a particular date. What does not belong there is a detailed account of the ceremony, the reception, or anything that reads like a social update rather than a membership fact. The timeline is a record, not a scrapbook.
If your church tracks giving carefully and discreetly, this is also the moment a treasurer sometimes wonders whether a married couple should give as one household or keep separate giving identities. That is a pastoral and practical decision each couple can make for themselves — the database will follow whichever choice they land on, once the household is set up correctly.
Who actually does this work
In most small churches, this falls to whoever manages the database — a part-time secretary, a volunteer, sometimes the pastor's spouse. It rarely gets assigned formally, which is part of why it gets delayed. A workable habit is to treat every wedding announcement the same way you would treat a new-guest form: as a trigger for a specific, short checklist, rather than a vague reminder to “update things at some point.” SundayBridge keeps the name, household, and address edits on one profile, so the person doing this work is not hunting across three screens to make one wedding correct in the system.
The checklist itself does not need to be complicated. Name first, from the person directly. Household second, merging or creating as needed. Address third, checked on both sides of the marriage, not just the one that obviously moved. A quick look for duplicate records if the new spouse has any history with the church at all. And a single line in the timeline noting the date, nothing more.
What tends to get missed six months later
The most common failure is not that nobody updates the name — that part is visible and gets done. It is that the household never gets fixed, because nobody realized it was a separate step from the name change. Six months on, someone pulls up the church directory to plan a baby shower or a meal train and finds a household that still says “Sarah Whitfield” living with her parents, married name nowhere in sight, new husband not listed anywhere near her. It is an easy thing to fix in five minutes. It is just as easy to never notice needs fixing at all, which is the actual problem a marriage creates for a database — not that the update is hard, but that half of it is invisible until someone goes looking.