Bill has gone by Bill since before most of the church staff were born. His driver's license, his tax return, and the deed to his house all say William. Nobody at church has called him William since 1986. So which one goes in the directory his small group leader pulls up before a hospital visit?
The honest answer is both, in two different fields, used for two different jobs. A church record that only has room for one name will eventually get one of those jobs wrong — either a directory full of formal names nobody recognizes, or a year-end giving statement addressed to a name the IRS has never heard of. The fix is not complicated. It just requires deciding, once, what each name is for.
Two names, two very different audiences
A preferred name is for people. It is what the greeter says at the door, what shows up on a nametag, what a small group leader says when they text to ask how someone is doing. It is chosen by the person, not assigned to them, and it changes whenever they say it should.
A legal name is for institutions. It is what belongs on a year-end giving statement, a background-check form for someone stepping into children's ministry, or a membership roll that might one day be read into a court record or an insurance file. It does not change because someone prefers a nickname. It changes only when a document says it changed: a marriage license, a legal name change, an adoption.
Once you see the split that way, the question of “which name goes on the directory” answers itself: the directory is a people tool, so it shows the preferred name. The paperwork is an institutional tool, so it uses the legal one.
What actually needs the legal name
It is a short list, and it is worth writing down so a volunteer does not have to guess:
- Year-end giving statements, because they represent a tax document.
- Background-check submissions for anyone serving with children or youth.
- A formal membership roll, if the church keeps one that gets referenced legally.
- Anything that will be signed, notarized, or filed outside the church.
Everything else — the directory, the check-in screen, the nametag, the serving schedule, the note a pastor writes after a hospital visit — runs on the preferred name. If you find yourself needing a legal name for a task and it is not on that list, it is worth asking why. Usually the honest answer is habit, not necessity.
The mismatch that actually causes problems
The trouble rarely comes from having two names on file. It comes from having only one, or from having two that nobody bothered to link. A newer volunteer searches the database for “William Carter” because that is the name on a check that just came in, finds nothing, and creates a second record. Now Bill has two profiles: one with thirty years of history and one with a single gift attached to it. Nobody notices for months, because both records look plausible on their own.
This is the same failure mode described in cleaning up a church database, and it is worth treating name mismatches as a subset of that same problem: a record only works if the person entering data can find the right one on the first try, using whatever name is in front of them at the time.
How to set up the two fields so nobody has to remember the rule
The cleanest version of this is not a policy memo, it is a form. A person record should have a spot for a preferred display name that is used everywhere the person is shown — the directory, the serving schedule, the check-in screen — and a separate field, filled in only when it is needed, for the legal name that feeds statements and official paperwork. When the legal name field is empty, whatever process needs it (a giving statement, a background check request) should prompt for it right then, not silently default to the preferred name and create a document with the wrong name on it.
SundayBridge keeps this distinction on the person profile: the name your team sees in the directory and on the serving schedule is the one the person goes by, while giving statements and other official output pull from a separate legal name field so the two never get tangled.
Names that change, and when to act on it
Preferred names change often and for small reasons: a woman starts going by her middle name after a divorce, a teenager who was always “Alex” asks to be called something else, someone anglicizes a name for daily use but keeps the original for anything formal. None of that requires proof. Update it the moment you hear it, the same way you would update a phone number someone gives you at the door.
Legal names should move slower and require more. Wait for the document. A person who says they are getting married next month is not yet the new legal name; a person who mentions in passing that they finally finished a legal name change is, once you have seen the order. This is not bureaucracy for its own sake — it is the difference between a directory that reflects real life and a tax document that gets rejected because the name on it does not match what the government has on file.
Where this connects to the rest of the record
Names are one part of a bigger question: what belongs in a household versus an individual record, and who is the point of contact for each. The logic in households vs. individuals applies here too — a married woman who kept her name professionally but goes by her husband's name socially at church is a preferred-name decision, not a household-structure one, and the two should not be confused. Keep the household model answering “who lives together and gives together” and let the name fields answer “what do we call this person, and what does the government call them.”
The other place this shows up is year-end giving statements, which is usually the one moment a year the legal-name gap gets discovered the hard way — a statement goes out addressed to a name a donor has not used in decades, and the office spends an afternoon fielding the same confused phone call from three different households. Fixing the field in January is a lot cheaper than fixing it in December.
A directory people actually trust
The real test of a directory is whether the person looking someone up recognizes who they are looking at. A directory full of formal names that nobody uses out loud fails that test quietly, one search at a time, until someone stops trusting it and starts keeping their own list on paper. That quiet erosion of trust is the actual cost of getting this wrong — not a single dramatic mistake, but a slow accumulation of small ones. The guide on building a church directory your team trusts covers the rest of what makes a directory usable day to day; name handling is simply the first habit that has to be right for everything after it to hold up.
None of this requires a committee decision or a new policy binder. It requires one field for what people call each other and one field for what the government calls them, used consistently by whoever enters data, and updated on two different clocks — fast for the name people use, slow and documented for the one that goes on paperwork. Bill stays Bill in the directory. William shows up exactly once a year, on a form that needs him to.