Somebody asks you, quietly, after service: could you take my family out of the directory. Maybe it is a custody situation. Maybe it is a person who left an abusive relationship and does not want an address floating around a printed booklet. Maybe they just do not like being looked up. The reason is theirs to keep, and your job is simple to state and slightly fiddly to execute: honor the request without losing the person.
That last part is where churches get it wrong. In the panic to respect a privacy request, someone deletes the record, and six months later nobody remembers this family gave two hundred dollars in November, or that their teenager is in the youth group roster, or that a pastor was in the middle of a care conversation with them. Opting out of the directory and disappearing from your church's memory are two very different things. Only one of them should happen.
What “the directory” actually means
Before you can honor a request, you need to know what you are actually being asked to change. In most small churches, “the directory” means one of two things: a printed or PDF booklet handed out to members, or a page inside your church software that staff and volunteer leaders can browse. Those are different audiences with different stakes. A person asking to be left out of a booklet that goes home with two hundred families is asking something much bigger than a person asking not to appear on a small group leader's roster.
Get specific with the person if you can. “Do you mean the printed directory, or anywhere at all?” is not an interrogating question — it is the question that lets you actually do what they asked instead of guessing. Most people mean the first one. A smaller number mean the second, and that is fine too, but it changes who on your team needs to know.
Keep the record, change the visibility
The record itself — the person's profile, their groups, their serving roles, their giving history, any care notes — stays exactly where it is. What you are changing is a single attribute: whether this person is included when the directory gets compiled, printed, or exported. Think of it less like deleting a line and more like putting a flag on a page that says do not copy this part.
In SundayBridge, a person's profile is the one place their whole story lives — groups, serving, giving, care, the timeline of what has happened with them over time. Opting out of the directory does not touch any of that. It only means this person is left out the next time you generate or CSV export the directory for members to see. Staff still has the full profile. The congregation-facing list does not.
Households make this a little more delicate
A directory entry is often a household — the Petersons, at 12 Birch Street — but the opt-out request usually comes from one person. Maybe it is the whole family who wants out. Maybe it is one spouse after a separation who does not want their new address linked to the other. Maybe it is a young adult still living at their parents' place who does not want to be listed publicly at all.
Handle the request at the level it was made. If your system treats each person as their own record — even within a shared household — you can mark one person out of the directory without touching their spouse's listing or splitting the family apart in your data. If your system only lets you hide or show a whole household at once, you will end up doing one of two uncomfortable things: honoring more of a request than was asked, or less. Neither is good. This is worth checking before you need it, not during the conversation with the family standing in the lobby. See households vs. individuals for how that modeling choice plays out elsewhere in your data.
Who needs to know, and who does not
A directory opt-out is not a secret from your staff — it is a preference about a specific audience. The pastor following up on a hospital visit still needs the phone number. The volunteer coordinator scheduling this person for the welcome team still needs to reach them. What they do not need is for this family's address to sit in a booklet that gets left in a pew or handed to a new member they have never met.
Where it gets genuinely tricky is your volunteer-facing tools. If a small group leader gets a roster export, or a Sunday school teacher gets a class list, those are directory-adjacent even if nobody calls them “the directory.” Ask the family, plainly: is this about the church-wide list, or about being reachable by the people who serve alongside you. Most people are fine with the second and only want out of the first. Assume nothing; ask once, clearly, and write down the answer somewhere more durable than your memory of the conversation.
Write it down where the next person will see it
The hardest part of an opt-out request is not the technical step — it is that six months from now, someone new is compiling the directory for the fall booklet and has no idea this conversation ever happened. If the preference lives only in your head, or in a text message you deleted, the family will have to make the same uncomfortable ask twice. That second ask stings more than the first.
A note on the person's profile — not a sticky note, not an email you will lose, but something attached to their record — is what keeps this from happening again. It does not need to explain the reason. “Not in printed directory, per their request, [date]” is enough. The point is that the next volunteer who pulls the list sees it without you having to be in the room.
What this looks like at export time
The moment that actually matters is when someone hits export or send to the printer. That is the point where an opt-out either holds or quietly fails. Build a habit — not a whole policy, just a habit — of checking that the list you are about to hand out is the filtered one and not the raw one. It is a thirty-second check that prevents the worst version of this problem: a name appearing in print after someone specifically asked it not to.
If your church still keeps its people list in a spreadsheet, this is exactly the kind of thing that gets missed, because a spreadsheet has no concept of “include in this export, not that one.” Someone has to remember to filter it by hand, every single time. See moving off spreadsheets for what else tends to slip through that same crack.
Being asked twice is the failure state
You will not get this perfect the first time for every family, and that is fine. What you want to avoid is the version where a member who already asked once has to ask again, because the first request evaporated into nobody's notes. That second conversation costs you more trust than the first one earns you back. A directory people trust is one where a quiet request stays honored quietly, indefinitely, without anyone having to remember to remember it. For the broader shape of a directory that holds up under this kind of scrutiny, see the church directory your team trusts, and for the habits that keep the underlying data clean enough that exceptions like this do not get lost, see cleaning up your church database.