The first time someone opens a blank person profile, the temptation is to fill in everything the form allows. Anniversary, allergies, shirt size, spiritual gifts, how they take their coffee. It feels thorough. Three years later it is three hundred records with half the fields empty, nobody sure which blanks mean “doesn't apply” and which mean “we never asked,” and a volunteer spending a Saturday trying to decide whether it is safe to delete any of it.
The better question is not “what could we track” but “what will we actually use.” A field only earns its place on a profile if some person, doing some real job, will look it up. Everything else can wait until the day it is needed — which, for a surprising number of fields, never comes.
This matters more for a small church than it might seem. A congregation of two hundred does not have a data-entry staff. It has a volunteer greeter, a part-time secretary, and whoever is willing to sit down on a Tuesday evening. Every field you decide is “required” is a small tax on that person's time, paid over and over, for every person who ever gets added.
Start from the jobs, not the form
Every field on a person's profile should trace back to something your church actually does. Follow-up needs a phone number and an owner. Giving statements need a mailing address at year-end. The serving schedule needs to know who is on a team. If you can't name the task a field serves, it is decoration, and decoration is what turns into clutter.
This is different from asking what a database could hold. A profile can technically have forty fields. A church of a hundred and fifty people, run by three volunteers with day jobs, cannot keep forty fields current on anyone. The honest constraint is not storage. It is attention.
The fields worth filling in on every person
A short list, and it really is short:
- Name — obviously, but also how they prefer to be addressed if it differs from the legal name on file.
- A way to reach them — phone or email, whichever they actually check. One good contact method beats three stale ones.
- Household — who they live with, so a statement, a card, or a follow-up note goes to the right address and doesn't duplicate. Our guide on households versus individuals goes deeper on where that line actually falls.
- How they arrived — first-time guest, regular attender, member, or transfer. This one field quietly powers follow-up, attendance context, and honest reporting later.
Notice what is missing from that list: birthday, anniversary, occupation, emergency contact, small group history, spiritual gifts inventory. None of those are wrong to have. They are just optional — worth adding the day a real task needs them, not the day the profile is created.
A field, once required, is hard to un-require
There is an asymmetry worth naming. Adding a field later costs almost nothing — you create it, and it sits empty on the older records until someone fills it in as they come up. Removing a required field costs real time, because now someone has to decide what to do with every value that is already sitting in it. Was that occupation field actually used, or was it copied blindly from an old system during setup? Nobody wants to be the one who deletes something that turns out to matter.
That asymmetry is an argument for restraint on the front end. When in doubt, leave a field out rather than add it. You can always create it the week it becomes genuinely useful. You cannot as easily un-create one that a hundred people have half-filled in over three years, because by then removing it looks like deleting data, even when the data was never trustworthy to begin with.
The fields worth leaving blank until asked for
A field that sits empty is not a problem. A field that gets filled in badly, once, and never touched again is. The pattern to watch for is a field that seemed important during setup and then never came up in an actual Sunday. Birthdays are the classic example — genuinely useful if someone owns sending a card, dead weight if nobody does. Anniversary dates, spouse's employer, T-shirt size for the next retreat: all fine to add later, all safe to skip now.
The test is simple. Ask: who looks this up, and how often? If the honest answer is “nobody, yet,” leave it blank. You lose nothing by adding it in six months when a real need shows up. You lose real time re-verifying it if you collect it now and it goes stale before anyone reads it.
Why an empty field beats a guessed one
The instinct to fill every box comes from a good place — it feels like diligence. But a guessed birthday, a phone number copied from an old church directory that's three moves out of date, or an address marked “probably still current” is worse than nothing. It looks like real data. Someone will trust it, act on it, and be wrong.
Blank is a status, and a useful one: it tells the next person to look at the record that nobody has confirmed this yet. That is a true statement. A guess dressed up as an answer is not. If your church is working through an old spreadsheet full of half-filled columns, our guide on cleaning up a church database walks through separating the confirmed from the guessed before you bring it into anything new.
Let the fields grow with the relationship
A first-time guest's profile should be nearly empty on purpose — name, a phone number if they gave one, and who is following up. As someone moves from guest to regular to member, the profile earns more detail because more people are now depending on it: a serving team lead needs to know their availability, a small group leader needs to know which group they're in, whoever prepares statements needs a giving history.
This growing-with-them approach also protects new people from feeling interrogated at the door. Nobody wants to fill out a form with twelve fields the first time they walk in. Ask for what the follow-up actually needs, and let the rest accumulate naturally as the relationship does. A well-kept directory your team trusts is built this way — a little at a time, by the people who actually use it, not all at once by whoever ran the original import.
Set a household rule before you set a field rule
One decision saves more cleanup than any field list: agree, as a team, on where the individual ends and the household begins. Mailing address, giving statements, and last name usually belong at the household level. Phone number, email, serving role, and how someone arrived usually belong to the person. Get that split wrong early and you will spend a future Saturday untangling duplicate addresses and giving records split across two records for the same family.
It is worth deciding this once, in writing, before your team starts entering people rather than working it out record by record as questions come up. A few sentences in a shared document — “the household holds the address, the person holds the phone” — keeps three different volunteers from making three different calls over a year.
Revisit the list once, then leave it alone
Set your required fields once, six months after you have real usage to look at, not on day one when everything is still a guess. Ask the person who answers follow-up calls and the person who prepares statements which fields they actually open. Drop anything neither of them touches. Then stop tinkering — a field list that changes every quarter is its own kind of clutter, and consistency matters more than getting every field theoretically perfect.
If your church is moving off a spreadsheet that has accumulated years of ad hoc columns, this is also the moment to decide which of those columns survive the move and which get left behind. Our guide on moving off spreadsheets covers how to make that call without losing anything you actually need.
What this looks like in practice
Picture a church of a hundred and thirty. A first-time guest walks in on a Sunday and leaves a name and a phone number on a card. That is the entire profile for now — two fields, both filled honestly. The greeter's follow-up note gets attached the same afternoon. A week later, the guest comes back, and someone adds them to a household because their spouse showed up too. A month in, they join a serving team, so a role gets recorded. By the time they are asking about membership, the profile has grown to match the relationship — not because a form demanded it on day one, but because each addition answered a real question someone was actually asking.
Compare that to the alternative: a twelve-field intake form at the door, most of it guessed at or left blank, that nobody revisits once the excitement of a new visitor wears off. The second version looks more thorough on the day it is created. The first version is the one still trustworthy three years later.