It sounds like a technicality: do you store people as individuals, or as families? But it is one of the few data decisions that reaches into almost everything a church does. Get it right and mailings, giving statements, kids records, and pastoral care all fall into place. Get it wrong and you fight the same friction for years.
The rule: individuals, grouped into households
The structure that holds up over time is not one or the other. It is both, layered: every person is their own individual record, and individuals are grouped into a household. The person is where identity and history live — this is Maria, here is her attendance, her serving, her story. The household is the unit most operations run on.
Why does that layering matter so much? Because people move between households over a life. Kids grow up and form their own. Couples marry and merge; some later split. A single blob called “the Nguyen family” can't survive any of those moments without losing someone's history. Individuals-under-a-household can.
What runs on the household
Once you look for it, you see how much church work is household-shaped. You mail one directory entry, not four. A giving statement usually covers a household, even when two spouses both give — the topic of tracking giving in a way that respects the giver. When you picture who is connected and who is drifting, you often think in families. The household is the natural handle for all of it.
What runs on the individual
Other work is stubbornly personal. Attendance is a person's, not a family's — a teenager may be every Sunday while a parent is every other. Serving is a person's. So is the pastoral note about a specific member. Keep these on the individual, and you can still roll them up to the household when it helps.
Handle kids and change deliberately
Children belong to a household and get individual records too, even before they have a phone or an email — because they have attendance, a class, and a birthday that matters. Plan for change from the start: decide how a graduating senior becomes their own household, how a new marriage merges two, how a move splits one. You will not predict every case, but a structure that expects change beats one that assumes everyone stays put.
Model it once, then trust it
The reason to settle this early is that re-sorting a thousand records later is miserable. Decide the shape before a big import, as part of moving off spreadsheets, and it quietly pays off forever after.
SundayBridge is built on exactly this model — people as individuals, gathered into households — so the family view and the person view are the same data seen two ways, and it's the backbone of a directory your team trusts. The model won't make the messy human cases tidy, but it gives them somewhere sensible to live.