Somewhere in every church database sits a field nobody has touched in three years. A “spiritual gifts” dropdown from a class that ended. A middle name column that is blank on 90 percent of profiles. An anniversary date that was accurate for one couple in 2019 and has been wrong ever since they moved. None of it is doing harm, exactly. It is just sitting there, waiting for someone to fill it in, and nobody ever will.
The instinct when you set up a new system is to capture everything you can think of, because surely more information is better. It is not. Every field you add is a quiet promise that someone will keep it current, and at a church of 60 to 250 people, the person making that promise is usually a volunteer with forty-five minutes on a Tuesday night. The honest question is not “could this be useful someday” but “who is going to type this in, and who is going to read it back.” If you cannot answer both halves, leave the field empty and move on.
The test that actually works
Before you add anything to a person’s record, ask two things. First: who looks at this. Not who might look at it, not who could theoretically pull a report on it — who, by name, opens this field and reads it as part of doing their job. Second: what decision changes because of it. If the greeter team lead checks whether a guest has been contacted, that changes whether someone calls them this week. That is a real decision. If a field just describes a person without pointing at an action anyone takes, it is decoration.
This test filters out most of what churches accumulate out of habit. Denominational background, favorite worship style, how they heard about the church — interesting trivia, almost never load-bearing. Whether a guest has an owner and a follow-up date is the opposite: it is the one field standing between a visitor and being forgotten. The gap between those two kinds of information is the whole article.
Worth tracking: anything a next step depends on
Some records earn their upkeep because the church literally cannot function without them being current.
- Who owns the next step with a guest, and by when. A visitor who “someone should probably follow up with” is a visitor nobody follows up with. An assigned owner and a date is the difference between a good intention and a phone call that actually happens.
- Giving records, tied to the right person or household. Wrong here means a wrong year-end statement, and a wrong statement is the one mistake a member notices immediately and remembers for years.
- Background-check status for anyone serving with children. This is not optional bookkeeping; it is the reason a check exists in the first place. A lapsed check that nobody flagged is a real liability, not a data-hygiene nuisance.
- Active pastoral care cases. A hospital visit, a grief situation, a family in crisis — these need to be current because someone is making a decision about who to check on this week, not filing history for later.
- Current serving assignments and group membership. These drive real-world logistics: who shows up to run sound, who is in which small group, who gets the reminder text from a leader.
Notice the pattern: every item on that list has a named person checking it regularly, and a real consequence if it is wrong. That is the bar.
Safe to skip: fields that describe without deciding
The other category is the stuff that feels like it belongs in a “real” database because a spreadsheet from a conference once had a column for it.
- Detailed demographic breakdowns nobody has ever pulled a report on — occupation, employer, alma mater. Pleasant to know, decides nothing.
- A one-time skills or gifts survey that has not been revisited since the class that generated it. If your volunteer coordinator does not open it before recruiting, it is not a record, it is an artifact.
- Formal membership status tracked as a separate class of data, when in practice your staff already knows who is active from groups and serving. Unless your bylaws require a vote and a roll, a groups list usually tells the same story with less upkeep.
- How a guest first heard about the church, tracked in granular detail with no one reviewing it by source. Worth a note if it is genuinely notable; not worth a required dropdown on every single guest.
- Historical attendance at the individual-visit level, beyond what your attendance trend already shows you. The shape of the trend over months is useful. A list of every Sunday any one person did or did not show up rarely changes a decision on its own.
None of these are wrong to know. They are wrong to require, because requiring them turns every new profile into a small piece of unfinished business, and a database full of unfinished business is one your team stops trusting.
Why half-filled fields are worse than no field at all
A field that is blank on 80 percent of records does not read as “optional information.” It reads as a mistake. Someone will eventually notice the gaps and spend an afternoon trying to fill them in, or worse, assume the missing 80 percent means the person does not have that attribute, when really it just means nobody asked. Either way, you have spent effort on a field that never changed a single Sunday.
This is the quiet cost of over-collecting: it is not that extra fields are dangerous, it is that they are boring in a way that erodes trust in everything else. A volunteer who opens a profile expecting stale, half-guessed data will not trust the giving total on that same page either, even though the giving total is accurate. Clutter does not stay contained to the field it lives in. For a longer look at how a database gets into this state in the first place and how to dig back out, see cleaning up a church database and, if you are still working out of spreadsheets entirely, moving a church off spreadsheets.
A short list beats a long one, every time
The churches that keep their records genuinely current are almost never the ones with the most fields. They are the ones with the fewest fields that matter, kept honestly. Ten fields checked weekly beat forty fields checked never. If you are setting up a new system, resist the urge to recreate every column from your old spreadsheet just because it existed. Start with the short list above — owner and date on follow-ups, giving tied to the right household, background-check status, active care, current serving and groups — and add anything else only once a specific person asks for it and commits to keeping it current.
This also matters at the household level. A person and a household are not quite the same unit of record, and getting that distinction wrong early is one of the more common ways churches end up with duplicate, conflicting data. Worth reading before you decide what belongs where: households versus individuals.
Revisit the list once a year, not once a decade
A field that earned its place two years ago can stop earning it. The volunteer coordinator who checked the skills inventory every August may have moved on, and nobody told the database. Once a year — budget season is a natural time — walk the fields you actually have and ask the same two questions again: who looks at this, what decision changes. Archive what fails. You are not deleting history; you are just admitting which parts of it are still working.
SundayBridge keeps this list short on purpose: a profile holds groups, serving, giving, care, and a timeline, and nothing else asks for your attention. There is no blank field waiting to be an accusation. If you are trying to decide what a small church actually needs from a system before you commit to filling one out, it is worth reading how to choose church management software with this same discipline in mind — fewer required fields, not more.
None of this is about being lazy with your records. It is the opposite: it is choosing to be rigorous about a short list instead of vaguely aspirational about a long one. A database that tracks five things perfectly serves a church better than one that tracks fifty things at sixty percent, because the five things are the ones that were going to change someone’s Tuesday afternoon anyway.