Somebody is going to ask, on a Tuesday morning, whether the Petersons still count as members. Or whether the new couple who came to Easter and again two weeks ago has a phone number on file anywhere. Or whose address is current for the mailed newsletter, now that half the church has moved in the last three years. Nobody built the church directory to answer philosophical questions about belonging — it exists so that on an ordinary Tuesday, someone can find an answer without calling four people to ask.
Most small churches did not choose their current system. They inherited a binder, then a spreadsheet somebody built in 2014, then a second spreadsheet nobody merged into the first, and now there are two Petersons and neither one has an accurate phone number. This page is about building something that stays trustworthy: what a record needs, how to structure people into households without losing the individual, what membership actually means as a status, and how to keep the whole thing clean enough that the next person who opens it believes what it says.
What a membership record actually needs to hold
A record earns its place by answering questions someone will actually ask. Name, contact information, household, and a status are the foundation — but a name alone is where most homemade spreadsheets stop, and it is not enough. A useful profile also holds what groups a person is in, whether they serve on a team, a giving history if the church tracks it, any pastoral care history kept discreet, and a timeline of how they have engaged over time. The full list of what belongs and what is optional is worth working through deliberately; see what fields a membership record actually needs for the breakdown. The instinct to add every field you can think of is usually wrong — a record with forty optional fields, most of them blank, is harder to trust than one with twelve that are reliably filled in.
Names deserve their own care. A woman who has gone by Beth for thirty years but whose legal name is Elizabeth should not have her directory listing corrected to the name nobody calls her — the question of which name goes on the directory comes up constantly, and the answer is almost always the name people actually use, with the legal name kept somewhere for the records that need it, like giving statements or a background check. Contact information matters just as much, and it degrades faster than anyone expects. A church of 150 will have a dozen phone numbers change in a given year, and standardizing how addresses and phone numbers get entered in the first place is what keeps a mail merge from bouncing and a phone tree from dialing a number that belongs to someone else now.
One profile per person is the rule underneath all of this, and it is worth stating plainly because it is the rule spreadsheets break first. When someone gets a second row because their name was typed slightly differently at guest check-in, their serving history splits, their giving splits, and nobody trying to look the person up finds the whole picture. The case for why every person should have one profile, not three is really a case for the record being worth consulting at all — a fragmented record is worse than no record, because it looks authoritative while quietly lying.
Households without losing the individual
Grouping people into households solves a real problem: a mailing address that only needs to be entered once, a family picture for a photo directory, and an easy way to see who belongs to whom. But a household is a convenience layer over individual people, not a container that swallows them. The question of how to structure people records around households or individuals comes down to keeping both: the household for the address and the family view, and the individual profile for everything that is actually about that one person — their own groups, their own serving, their own care history.
Kids are the clearest case where this matters. A child’s record should never live only as a line item inside a parent’s profile; it needs its own profile, with its own grade and its own history, linked back to the household it belongs to. That link is what lets a check-in volunteer or a Sunday school teacher confirm who is allowed to pick a child up, and what an emergency contact record actually needs to say is narrower than people expect: a name, a relationship, and a number that will be answered, not a full medical history.
Households also change shape, and the record has to be able to follow without erasing history. Blended families are the most common case that breaks a rigid household model — a child who splits time between two houses, a stepparent who is not the legal guardian, a grandparent raising a grandchild. The honest approach is covered in recording blended families without breaking the household model, and the short version is that the record should reflect the family as it actually is, even when that takes more than one household link to express. The same is true when a couple divorces or marries: the record needs to change without deleting the history that came before it, and neither a maiden name nor a prior address should simply vanish when a household gets updated — a record that quietly overwrites the past has thrown away information someone will eventually need back.
There is one more household question worth deciding on purpose rather than by accident: whose address is the one that gets used when a household has more than one adult who technically lives somewhere else part of the year, or when adult children still live at home but keep their own mailing address. And at some point, usually around the time a household’s oldest child turns eighteen or gets married, the question of when an adult child should get their own member profile comes up on its own. Most churches split them off from the parent household the moment they start giving, serving, or living independently — whichever comes first.
What membership actually means, and who decides
Membership sounds like it should be self-evident, but ask five people at a church of 150 who counts as a member and you will likely get five different answers, some of them contradictory. The underlying question — does a church of that size still need a formal membership roll — is worth answering deliberately rather than letting it drift, because a roll nobody maintains becomes a source of arguments instead of clarity. Some churches decide membership is not worth formalizing at all and simply track everyone who attends; others keep a real distinction because their bylaws, their voting rights, or their denomination requires one.
Where a distinction exists, it has to be recorded somewhere more durable than memory. The difference between an attender and a member in your records is usually a status field with a date attached, not a separate list kept in someone’s head. If your church runs a formal class or track before someone becomes a member, what to track from it is worth deciding up front — attendance, completion date, and whether it feeds directly into a status change. And if your tradition uses a covenant signing as the actual moment of membership, that date deserves its own field rather than being inferred from when someone first shows up on the roll.
Membership status also has to be able to move backward, and this is the part churches are most reluctant to build a process around. Deciding what actually makes a member inactive, and who decides is uncomfortable because it feels like passing judgment on a person, but leaving it undefined does not avoid the judgment — it just means the judgment happens informally, inconsistently, and usually right before an annual meeting when someone finally looks at the numbers. Reviewing that list before the meeting, rather than during it, is a far better moment to do this work — it becomes a routine check instead of a debate. Whether a church should ever formally remove a name from the roll is a governance question more than a software one, but whatever the answer, the record should be able to hold the decision, the date, and who made it.
The people behind that status deserve attention too, not just the label. What to do about members who quietly stopped coming is often more pastoral than administrative — a phone call before a status change, not instead of one. And when someone does come back after months or years away, the record should make that easy to see and act on, restoring their history rather than treating them as a brand-new entry.
Turning a guest into a record someone will actually use
The gap between a paper guest card and a searchable record is where most churches lose people, not because they do not care, but because the card sits in a basket for three weeks before anyone types it in. The questions worth putting on that card in the first place matter more than they seem — ask too much and people leave it blank, ask too little and the follow-up team has nothing to work with. What you should record about that first visit, and what you should deliberately skip, matters just as much: recording everything a guest might ever tell you feels thorough, but it is usually just noise that buries the two or three facts that matter for a follow-up call.
The actual conversion from card to record is a habit, not a feature. Turning a paper guest card into a record someone will use works when one person owns that task every week, the same day, rather than whenever someone gets around to it. Once a guest is in the system, the question becomes how long they stay a guest before someone treats them differently, and what the path from first visit to membership should actually look like on paper, so it does not depend on one staff member remembering who is where in the process. That path is worth writing down once and reusing; see guest to member: the path worth writing down. Not every guest becomes a member, and not every guest comes back at all — the honest thing to do with a guest record for someone who never returned is covered in what to do with a guest record for someone who never came back, and the short version is: keep it, mark it, and stop expecting it to change on its own.
SundayBridge’s follow-up board exists for exactly this handoff: a guest becomes a next step with an owner and a date, and the board ages anything nobody has picked up, so a card does not quietly die in a basket. What it will not do is send the guest anything itself — there is no email or text messaging built in, so the actual outreach is still a phone call or a card someone writes by hand.
Keeping the directory clean enough to trust
A directory degrades the moment it stops being edited, and it degrades fastest in the ways that are hardest to notice: a duplicate created at guest check-in, a phone number that changed and was never updated, two household records that should have merged into one after a wedding. Finding those duplicates before they cause a problem — a follow-up call to the wrong number, a giving statement that only shows half a family’s giving — is covered in how to find duplicate people hiding in your church database, and merging two household records without losing what either one knew is its own careful process worth doing slowly rather than in a rush before a Sunday.
Most of the mess starts small and specific: a name typed two different ways, an address entered as free text instead of structured fields, a household created for someone who already had one. Those small mistakes compound over years into a directory nobody fully trusts, which is why cleanup cannot be a one-time project. A once-a-year pass, timed to something predictable like the start of the school year or the annual meeting, catches what accumulated since the last one. If your database has been neglected for longer than a year, the fix looks different — more like an excavation than a tune-up — and cleaning up a messy church database walks through how to approach that without losing a weekend to it.
None of this holds together without someone actually responsible for it. Deciding who should actually own data entry at a small church matters more than which software you use — a good system with no clear owner ends up exactly where a spreadsheet with no clear owner ends up, which is out of date within a year. SundayBridge cannot import a spreadsheet for you automatically — there is no CSV import — but it will load your existing spreadsheet by hand at no cost, which at least means cleanup starts from a single, correctly structured record instead of a second parallel mess.
Privacy inside a directory everyone can see
A church directory has an odd tension built into it: it exists so people can find each other, and it holds information some of those people would rather not have found. Deciding what member information should never be public, even by accident is a design decision that has to happen before the directory gets printed or shared, not after someone notices their cell number is on a page taped to the church kitchen wall. What actually belongs on a listing is usually smaller than people assume — a name, a household, maybe a phone number people are comfortable sharing, not a full profile’s worth of detail.
Some information needs more protection than a simple omission from a printed page. Background-check results connected to a serving role are sensitive by nature, and keeping them private while still useful to the person who needs to see the alert is its own small discipline. Pastoral notes carry a similar weight, and this is a place where SundayBridge’s limits matter and are worth being direct about: there are no staff roles or permissions in the product, which means one shared login sees everything in the account, including pastoral care notes. If your church keeps genuinely sensitive pastoral history, what one shared login means for who can see pastoral notes is worth reading honestly before you decide what to put in the system at all. Recording a genuinely sensitive family situation without inviting gossip through the record itself follows the same logic: write down only what a caregiver needs to act on, not the whole story.
Every congregation also has someone who does not want to be in the directory at all, and that request deserves a clear, respected answer rather than an awkward workaround — a way to honor it without losing the person from the household and giving records the church still legitimately needs to keep.
Directories, print, and the parts that live outside the database
Not every church wants a digital-only directory, and the choice between a printed directory and a digital one usually comes down to who is looking things up — a congregation with a lot of older members often still wants something they can hold. SundayBridge can export the directory to CSV, which is what makes a printed handbook possible in the first place. A photo directory raises its own question, because most small churches cannot afford to hire a photographer for a single afternoon of headshots — how to build a photo directory without hiring a photographer is a more realistic path for most budgets.
Kids’ records intersect with the directory in ways that are easy to overlook. Every fall, a class roster has to move up a grade, and doing that by hand across dozens of children is tedious enough that churches put it off until it is overdue. Some churches also run a Sunday school roster that never quite matches the membership list, because attendance in a classroom and formal membership are answering two different questions. SundayBridge’s Sunday school module is read-only — classes, teachers, rooms, and enrollment display from records entered elsewhere, so it will not replace a check-in process. If your church does not run a check-in kiosk at all, keeping kids’ records straight has to happen by hand, at a table, with someone who knows the families.
Giving records sit close to the directory too, and the question of whether to track a gift by household or by person deserves the same deliberate answer as the household question in general — most churches track giving at the household level for statements, while still knowing which individual gave.
What good looks like a year from now
A church directory succeeds quietly. Nobody notices a good one; they just find the answer they were looking for, the way they expect to, and go back to whatever they were doing. The signs of a directory that has earned trust are almost boring: the Petersons’ status has a date attached to it and a reason, the guest from Easter either has a follow-up owner or a note explaining why not, the address on file matches the one on the envelope, and nobody in the office is quietly keeping a second spreadsheet because they do not trust the first one.
Getting there is less about picking the right software than about picking a small number of habits and keeping them: one profile per person, a household layer that does not swallow the individual, a membership status with a date, a guest that becomes a record the same week, and a once-a-year look at the whole thing to catch what drifted. SundayBridge’s directory holds one profile per person with groups, serving, giving, care, and an engagement timeline in one place, and it exports to CSV when you need the data somewhere else — but the habits matter more than the tool, and they will outlast whatever software you happen to be using five years from now.