Should we ask people to opt in before we list them?

Yes, and it does not need to be a form. A line in the bulletin or a sentence from the pulpit — “if you would rather not appear in the printed directory, tell the office and we will leave you off” — is enough for most churches. Keep a note of who opted out somewhere you will actually see it before the next print run, not just in someone’s memory.

What about kids? Do they need their own directory entry?

Most churches list children under the household rather than as their own entries with a photo and contact line. A child’s name, birth year, and grade are usually enough for a Sunday school roster or a class list. Save the fuller profile — allergies, pickup authorization, custody notes — for the people who actually need it, not the general directory.

Is a home address ever appropriate to show?

Rarely, for a general-purpose directory. A neighborhood or general area (useful for small group placement) is usually enough. If your church truly needs full addresses on file — for mailing a physical newsletter, say — keep that on the person’s record for staff use and leave it off anything printed or shared widely.

Should giving history show up anywhere near the directory?

No. Giving is one of the few things in a church database that should have a harder wall around it than anything else, including attendance or group membership. It belongs on the person’s own record, visible to whoever reconciles it, and nowhere near a directory listing, printed or digital, that other members might see.

What if we already published too much and want to walk it back?

Start with the next printing or the next export, not a dramatic announcement. Quietly trim the fields going forward, tell the office team the new standard, and mention it once, briefly, to the congregation as a normal update rather than a confession. Most people will not notice the fields that disappeared; they will notice if you make a bigger deal of it than it needs to be.

What information actually belongs on a directory listing

Every church directory has a moment where someone asks, “should we put that in there?” A cell number. A spouse’s employer. A child’s allergy. The question comes up because nobody wrote down a standard the first time, so each new field gets decided on the spot, by whoever is typing.

A directory listing has one job: help members recognize and reach each other. It is not a full profile, and it is not a place to store everything you happen to know about a household. Once you separate those two things — what the directory shows versus what the record holds — the decisions get much easier.

The directory is for recognition, not record-keeping

A member flipping through the directory (printed or on a screen) is usually trying to do one of a few things: put a face to a name, find a phone number to make a plan, or check which household a new person belongs to. That is a narrow job. It does not require pastoral history, giving totals, or a background-check status. Those things live on the fuller record — the profile the office keeps — not on the page a member sees.

Keeping that distinction in mind resolves most of the edge cases before they turn into a debate. If a field helps a member recognize or reach another member, it is a directory field. If it helps staff care for or manage that person, it belongs on the internal record and stays there.

What earns a spot on the listing

A minimal, sensible directory entry usually holds:

Name — first and last, and a preferred name if it differs from the legal one on file.
Household — who else lives there, so a new member can place a family at a glance.
Photo — optional, but the single field that does the most work for recognition, especially in a church past about eighty people where nobody knows everyone by sight anymore.
A way to reach them — a phone number or email the person has said is fine to share. Not every number on file belongs here; some people give the office a cell number for emergencies only and a different one for the directory.
General area — a neighborhood or part of town, if it is useful for placing someone in a small group or carpool. Not a full street address.

That is close to the whole list. Everything past this point should have a specific reason to be there, not just “we happened to collect it.”

What stays on the record, off the listing

The category that trips up most churches is the information that is genuinely useful to someone on staff, but not to a member browsing the directory. It belongs in the person’s own record and nowhere else:

Giving history. This is the field with the least business appearing near a directory. A church that keeps giving private, always, has an easier time asking people to give honestly.
Pastoral care notes. A case, a comment, a history of what a pastor followed up on — kept discreet, visible to the people handling care, never surfaced next to a phone number.
Background-check status. Relevant to whoever staffs children’s ministry, irrelevant and slightly alarming to a member looking up a friend’s number.
Full home address. Useful for mailing something; not useful for a shared directory most people will eventually lose track of.
Employer, workplace, or income detail. Sometimes volunteered, rarely needed by anyone but the person themselves.

None of this is secret from the church — it is on the record, available to whoever needs it for their role. It is just not on the page every member can flip through.

Ask before you publish, not after

The cheapest fix here happens before printing, not after someone complains. A short opt-out — a line in the bulletin, a note from the front — lets the handful of members who have a reason to stay off the directory (a custody situation, a safety concern, a person who just prefers privacy) say so before their information goes out to eighty families. Asking after the fact means a reprint, an apology, and a member who now trusts the office a little less.

This matters more the bigger the church gets and the more the directory travels — a printed booklet that sits on forty kitchen counters is a very different thing to have gotten wrong than a shared spreadsheet three people glance at.

Photos deserve their own small conversation

A photo does more for a directory than almost any other field, and it is also the field most likely to make someone quietly uncomfortable — a member going through a difficult season, someone in a role where visibility is a real concern, a person who simply does not like how they look in the picture the office happens to have on file. None of that is a reason to skip photos entirely; it is a reason to ask, rather than assume, and to let “no photo” be a normal, unremarked-on choice rather than something a member has to explain.

In practice this is a two-minute conversation the first time someone joins, not a policy document: does this person want a photo in the directory, and if so, whose photo, taken when. Answer it once at intake and the rest of the directory work gets much simpler.

Children get a lighter entry than adults

A child does not need the same directory presence as an adult. Name, birth year or grade, and the household they belong to is usually enough for a class roster or a directory that includes families. The things a Sunday school teacher genuinely needs — allergies, pickup authorization, an emergency contact — belong on the child’s own record, visible to the people running that class, not printed alongside the parents’ phone numbers.

When the directory is digital instead of printed

A lot of what makes this decision easier for a paper directory gets harder once the directory lives in an app or a shared file, because it is easy to add a field “just in case” when there is no page limit forcing restraint. The same standard still applies: if a field helps one member recognize or reach another, it belongs. If it helps staff manage the person, it does not, no matter how easy it would be to add a column for it. A directory your team actually trusts comes from that discipline being applied consistently, not from a longer form.

If your church is exporting a directory as a CSV to hand to a committee or print at a copy shop, the export is the moment to check which columns are actually going out. It is easy to export every field on a person’s profile out of habit and only notice the giving column was included after it has already been handed to someone.

A group leader needs less than the office does

It helps to think through one more audience before you settle the standard: the small group leader or Sunday school teacher who needs a roster, not a directory. Their list is a subset — names, a household grouping, a phone number for the group chat — pulled from the same records, but it does not need to be the full directory any more than the directory needs the group leader’s private notes about who is struggling to make it to group most weeks.

The same restraint applies here as everywhere else in this list. A roster for a small group people actually return to works because the leader can see who is in it and how to reach them, not because they can see everything the church knows about each person. Keep that roster thin, and the directory thin, and the fuller record where it belongs, and nobody ends up holding more information than their role calls for.

A standard, written down once

The point of all this is not a rigid policy binder. It is one short, written standard — the kind that fits in a paragraph — that whoever builds the next directory export can follow without re-litigating each field. SundayBridge keeps a single profile per person with clear boundaries between what is a directory-level field and what belongs to giving, care, or serving, so the export naturally stops at the right line instead of dumping everything on the record.

Write the standard down once, apply it every time you print or export, and the “should we put that in there” question stops coming up as a surprise.

If your current directory grew without anyone deciding much of anything, cleaning up the database is the natural next step once the standard is written down. And if you are still deciding how households and the people in them should relate to each other on the record, households versus individuals is worth reading alongside this one.