The household decision is the first one a new database asks you to make, and it is easy to treat it as an afterthought — a filing detail you can fix later if it turns out wrong. It is not a filing detail. Every giving statement, every mailing, every family view on the dashboard reads off the same underlying structure, and restructuring three hundred people after the fact is exactly the kind of chore that makes a volunteer quietly give up on the whole system.
Setting up household records correctly from day one is mostly a matter of holding two ideas at once: a household is a grouping for mail and for a family-level view, and a person is where everything that actually matters — giving, serving, groups, care history — lives. Confuse the two and you end up with a giving statement addressed to nobody in particular, or a serving assignment that got lost because it was attached to a household instead of the person who actually shows up on Sundays.
A household is an address, not a person
Think of the household record as the equivalent of an envelope: it has one address, and it groups the people who share it. It is not where you track anything about a specific individual. Every serving role, every group membership, every pastoral care note, every gift belongs to a person's own profile, one profile per person, with groups, serving, giving, care, and an engagement timeline attached directly to them.
The mistake that causes the most rework later is entering a family as a single blended record — “the Andersons” — instead of four separate people grouped under one household. It looks faster on day one. It falls apart the first time you need to know which Anderson gave which gift, or which teenager is actually enrolled in the youth group. If you are still deciding between the two structures generally, our guide on households versus individuals covers the underlying logic in more depth than this article does.
Decide your household rule before you enter row one
The specific rule matters less than having one, written down, before anyone starts typing. A workable default for a congregation of 60 to 250 people: a household is whoever shares a mailing address and a last name, or whoever the family itself considers a unit, whichever is more useful for your mailings. Write that sentence somewhere visible — a shared note, a whiteboard, the first line of your onboarding doc — and apply it the same way for every family, including the awkward ones.
The awkward ones are where a rule saves you. A blended family with two last names, a college student still on their parents' address but rarely home, a widow who moved in with her daughter last year — each of these will come up in your first afternoon of data entry, and each one takes thirty seconds to decide correctly with a rule and ten minutes to argue about without one.
Common edge cases and a plain answer for each
- Blended or remarried families: group by current address, not by original last name. Two last names in one household is normal and does not need a workaround.
- College students and military deployment: keep them in the family household if mail should still reach that address, and add their own contact details on their personal profile for anything that should reach them directly.
- A single adult living alone: still gets a household, even a household of one. Consistency matters more than the label.
- An elderly parent who moved in with adult children: move them into the new household as soon as the address change is real, and leave a note on their care record if the move itself is pastorally significant.
Enter the household, then build out the people
A practical order: create the household first with its address, then add each person to it, then fill in what belongs to that person specifically — their own phone number if it differs from the household line, their group memberships, whether they are currently serving on a team, and anything pastoral that needs to stay discreet. Resist the urge to enter every historical detail on day one. Get the shape right — correct people, correctly grouped — and let the detail fill in as you go.
This is also where a rough but complete pass beats a slow, perfect one. A church of 150 people is roughly 55 to 65 households once you group by address. Getting all of them entered with the right people in the right household, even with half the phone numbers still blank, puts you in a far better position than having twenty beautifully complete households and the rest still on paper.
What a wrong household costs you later
The cost of an early household mistake rarely shows up right away. It shows up in December, when a year-end giving statement goes out under the wrong name, or on a Sunday morning six months from now, when a greeter cannot find the child of a family that was entered as two unrelated households by mistake. Untangling that later means finding every gift, every group membership, and every serving record tied to the wrong grouping and moving it by hand — exactly the kind of work a volunteer treasurer does not have a free Saturday for.
It is worth being honest about the tradeoff here: getting this right up front takes longer than rushing through a spreadsheet import would. SundayBridge does not import a CSV for you, so every household in the system was typed in by a person who had to make each of these calls consciously. That is slower on day one and it is also why the structure tends to hold up — nobody inherited a stranger's shortcuts.
Keep giving and serving attached to the person, always
One rule is worth repeating on its own, because it is the one that gets violated most often under time pressure: never record a gift, a serving assignment, or a group membership against a household when it actually belongs to one person. A joint checking account does not mean joint giving credit belongs to “the household” as an entity — it belongs to whichever adult the check or online transfer should be attributed to, even if the household later receives one combined mailing. The household groups the mail. The person owns the record.
The same logic applies to serving and groups. If both parents in a household are on the greeting team, that is two serving assignments on two people, not one entry that says “Andersons.” When one of them steps down, you need to be able to remove exactly their assignment without touching their spouse's.
A short setup routine for your first afternoon
If you are starting from a spreadsheet or a paper directory, this order tends to work well for a first session: pull your active member and regular-attender list, sort it loosely by address or last name so families cluster together, then create households one cluster at a time rather than jumping around alphabetically. Enter the household address, add each person, and move to the next cluster. Resist stopping to fix an old typo or chase down a missing phone number mid-session — note it and keep moving, the same way you would during any first-week data entry push.
Once your first batch of households looks right, it is worth reading through our guide to a church directory your team trusts for what a healthy directory looks like once the households themselves are set up correctly, and our database cleanup guide if you are working from records that already have some duplicates or split families baked in.
The five-minute check before you call it done
Before moving on to giving, serving, or groups, spot-check a handful of households against three questions. Does the household address match where mail should actually go? Is every person who lives there listed under it, with no one missing and no one duplicated in a second household by accident? And for anyone who gives or serves, is that activity attached to them personally rather than to the household as a whole? If those three hold for a sample of ten households, the structure underneath the rest of your data is almost certainly sound, and the detail work from here is just filling in what is already correctly shaped.
A household is where the mail goes. A person is where everything else lives. Keep that straight from the first record and the rest of the system holds together on its own.