Somebody moved the Christmas card list into a spreadsheet in 2019, and every year since, someone has typed a new address into it a slightly different way. One row says “123 Maple St, Apt 2.” Another says “123 Maple Street #2.” A third just says “Maple St.” They are the same family. The spreadsheet does not know that, and neither does anything you try to build on top of it.
This is not a data-hygiene lecture. It is a practical problem: when your addresses and phone numbers are inconsistent, the things you actually need to do — mail a giving statement, print a directory, call a family whose teenager missed three Sundays — get harder, slower, or quietly wrong. Standardizing the format is boring. It is also one of the few pieces of church admin where an hour of care pays back for years.
What “standardized” means in practice
It does not mean fancy. It means picking one shape for each field and sticking to it:
- Street address on one line, the way the post office would print it — abbreviate the same way every time (St, not Street one week and St. the next).
- City, state, zip as three separate pieces of information, not run together in a street field.
- Phone numbers as ten digits in one consistent pattern, for example 555-201-4478, with no parentheses in some records and none in others.
- One phone per person that you trust is current, rather than three numbers pasted into a notes field with no indication which one still rings.
None of this requires new tools. It requires a rule everyone follows and the discipline to fix a bad entry the moment you notice it, instead of leaving it for “later.”
Where inconsistent formatting actually costs you
The cost is invisible until the moment you need the data to work, and then it is very visible.
Mailings
Year-end giving statements are the clearest case. If a household’s address is on one line in some fields and split oddly in others, the label prints wrong, or the letter comes back, or worse, it goes to the wrong door. A treasurer who has to hand-correct forty addresses before a mailing is spending an evening on a problem that a standard format would have prevented a year earlier.
Exports
Any time you pull a directory or a mailing list out of your system as a CSV, the file is only as clean as what went in. A spreadsheet program cannot tell “123 Maple St” and “123 Maple Street” apart the way a person can. It will treat them as two different addresses, or fail to sort them together, and the export you hand to a print shop or a mail house reflects every inconsistency that has crept in over the years.
Finding people
A search for “555-201” only works if that is how the number is actually stored. If half your entries have dashes, a quarter have dots, and a quarter have nothing, a quick search from the follow-up board or the directory misses records it should have found. The volunteer trying to reach a family before Sunday gives up and calls the wrong number, or none at all.
Duplicate households
Inconsistent addresses are one of the main reasons the same family ends up as two separate entries — one from when they joined, one from when someone re-entered them after a move using slightly different spelling. Once that happens, giving history splits, attendance splits, and nobody notices until year-end statements are wrong. For more on that specific problem, see cleaning up a church database.
Pick the format once, write it down
You do not need a data governance policy. You need one paragraph, taped inside a binder or pinned in a shared doc, that says exactly how an address and a phone number should look. Something like:
- Street on one line, abbreviated the USPS way (St, Ave, Rd, Apt).
- City, state (two letters), zip as separate fields.
- Phone as ten digits with dashes: 555-201-4478.
- If someone gives you a phone number with an area code that does not match local ones, keep it — people move, and the number is still theirs.
Whoever enters new people — a greeter with a clipboard, a volunteer at the connect card table, the secretary typing from a paper form — follows the same rule. New entries stay clean by default, and the backlog of old ones only shrinks, it does not keep growing.
Fix as you touch, not all at once
Trying to fix two hundred records in one weekend is how this project dies. Nobody has a free weekend, and even if they did, a rushed cleanup introduces its own new inconsistencies. The workable version is smaller: every time you open a record for another reason — a new guest follows up, a family calls to update their address, a giving statement bounces — you fix the formatting on that record while you are already in there. It costs thirty seconds instead of a weekend, and it happens whether or not anyone remembers to schedule it.
Set aside a small recurring block — twenty minutes a month is enough — to work through a batch of the records nobody has touched recently. At that pace, a directory of 150–250 people gets meaningfully cleaner within half a year, without ever eating a whole Saturday. If your admin rhythm does not have a slot like this yet, the weekly church admin rhythm guide has a place to put it.
Households make the phone number question sharper
A family of five might share one address but have three different phone numbers — a landline, mom’s cell, a teenager’s cell. Deciding whose number is the household’s “primary” contact, versus which numbers belong to individual people, is really a modeling decision, not a formatting one. Get that decision right first, and the formatting rule is easy to apply consistently. Get it wrong, and you will be reformatting the same numbers again in a year once you realize the structure underneath them was off. The households vs. individuals guide walks through that decision directly.
What good looks like when someone else has to use it
The real test of a standardized directory is not whether it looks tidy to the person who built it. It is whether a volunteer who has never touched the system before can search a phone number, pull an accurate mailing list, or hand a printed directory to a new small group leader and trust every line of it. SundayBridge keeps one profile per person with a CSV export of the directory, so a clean, consistent format on the way in is what makes that export usable on the way out — a spreadsheet with three address styles in it does not become useful just because you exported it. For the fuller picture of what a trustworthy directory looks like day to day, see the church directory your team trusts.
If your directory still lives in a spreadsheet with no shared rules at all, the formatting problem is really a symptom of a bigger one, and it might be worth reading moving your church off spreadsheets before you invest hours standardizing data that is about to move anyway.
The honest limits
No piece of software, SundayBridge included, can look at “123 Maple St” and “123 Maple Street, Apt 2” and know on its own whether those are the same family or two different ones a few doors apart. It cannot know that the landline in someone’s file was disconnected last spring. A consistent format makes the data easier to search, export, and trust — it does not replace the judgment of the person who actually knows the church.
That is the whole case for doing this: not that clean data is virtuous, but that the moment you need it — the mailing, the export, the phone call before Sunday — is exactly the moment inconsistent formatting turns into wasted time. Fix the shape once. Keep it that way as you go. The payoff shows up every single time you touch the directory afterward.