Ask a church of 150 people who is in charge of the directory and you will usually get a pause, then a list: the front-desk volunteer updates addresses when someone mentions a move, the small groups coordinator adds new members to her own spreadsheet, the pastor jots a note in his phone after a hospital visit, and the treasurer keeps giving in a separate file nobody else has opened. Five people, five partial pictures, and not one of them owns the whole thing.
This is not a technology problem. It is an org chart problem wearing a technology costume. You can buy the best software available and still end up with five half-updated records, because software does not assign ownership — people do, or they do not, and mostly they do not, because nobody ever asked.
Why "everyone updates it" quietly means no one does
Shared ownership sounds efficient. In practice it produces a specific failure: each person assumes someone else caught the thing they did not. The greeter who heard about a new baby assumes the small groups leader will add it. The small groups leader assumes the greeter already logged it. Neither does, because logging it was never anyone's job in particular — it was everyone's job in general, which functions the same as no one's.
The result is not chaos so much as slow decay. Nothing breaks all at once. The record just gets a little less trustworthy every month, until someone pulls a list for a mailing and finds it is wrong often enough that people stop trusting it, and then stop using it at all.
What a single owner actually does
Naming an owner does not mean one person types every update by hand. It means one person is accountable for the state of the record — the one who notices when a field has gone stale, who decides what counts as a real update versus a rumor, and who actually opens the system on a schedule rather than whenever they happen to remember. Everyone else can still report changes to that person. The difference is that reports land somewhere, instead of evaporating into five different inboxes.
In practice this is often a fifteen-minute task, not a job description. A church of 120 people with a handful of moves, baptisms, and new attendees in a typical month does not need a full-time registrar. It needs one person who treats a short weekly pass over the directory as part of their regular responsibilities, the way a weekly admin rhythm treats it — a fixed slot on the calendar, not an afterthought squeezed in between other tasks.
Picking the right person, not just any person
The owner does not need to be staff, and often should not be — many churches this size do not have paid administrative help at all. What the role needs is presence and attention: someone who is around most Sundays, who already touches the people side of church life (check-in, the welcome table, small groups), and who will treat a wrong phone number as worth fixing rather than someone else's problem. A retired bookkeeper, a parent who is at the building three mornings a week, a deacon who already tracks attendance informally — these are the profiles that tend to work, more than any particular title.
Giving records are worth calling out separately. They carry a confidentiality weight the general directory does not, and the skill set (accuracy with numbers, discretion) often points to a different person entirely — a treasurer or financial secretary rather than whoever runs the welcome table. It is fine, even preferable, to split ownership by data type, as long as each type still has exactly one name on it.
What to do with the other four volunteers
Naming an owner is not the same as telling four people to stop paying attention. The greeter who hears about a move, the small groups leader who notices a new face, the pastor who visits the hospital — they still notice things first, and that noticing is valuable. What changes is where it goes. Instead of each person deciding on their own whether and how to update the record, they report what they saw to the one person whose job is deciding what to do with it.
This is a small habit change with an outsized effect. A short standing note — a text thread, a form, even a sticky pad by the coffee station — that funnels observations to one owner turns five scattered updates into one coherent one. The owner still has to decide what is a real update, which is where a periodic cleanup pass earns its keep, catching the things that slipped through even a well-run process.
What happens when the owner is out
Every real system needs a backup, and this is where a lot of well-intentioned ownership plans quietly break down: the owner goes on a two-week trip, or steps back from the role entirely, and no one else knows where anything is or how it was organized. The fix is not a second full owner — that just recreates the original problem with two people instead of five. It is a named backup who knows the system well enough to cover a Sunday or a vacation, plus a habit of documenting decisions (why a household is grouped a certain way, why someone is marked inactive) so the reasoning does not live only in one person's head.
This matters even more at a handoff. When a data owner moves on for good, the church that has been treating the role as a real job — with a defined scope and a few written notes — hands it off in an afternoon. The church that has been treating it as whatever the last volunteer happened to do starts over from a guess.
What software can and cannot fix here
Software will not assign this role for you, and no amount of feature comparison changes that. What it can do is make the owner's job small enough to actually happen every week. In SundayBridge, each person is one profile — groups, serving, giving, and care history all live under the same record — so the owner is not hunting across five tabs or three spreadsheets to make one update. That does not replace the decision about who owns the role. It just means the fifteen minutes you give them actually cover the whole picture instead of one corner of it.
The churches that get this right are not the ones with the most people watching the data. They are the ones with exactly one person who is supposed to be watching it, and everyone else knowing who that is.
Starting the conversation this week
If your church has no clear owner today, the fix does not require a committee meeting or a new title. It requires one conversation: naming a person, in front of the other four who currently touch the data, and telling them their job going forward is to report what they notice rather than to fix it themselves. Pair that with a directory the whole team can actually trust and you have solved most of what usually gets blamed on the software.