A household can connect donors without combining them

When two donors share a home, keep each person as an individual contact. Use the household as a relationship and reporting view—not as a substitute donor—and attach each gift, receipt, and communication choice to the person who owns it.

Well-designed donor household records give you a useful shared total without turning “Sam and Priya” into one synthetic person.

Give the person and the household different jobs

A person record answers individual questions: Who made this gift? Which email address belongs to them? What did they ask you to stop sending? Which recurring gift can they manage?

A household view answers shared questions: Which people belong together for this mailing? What is their combined giving for a relationship review? How should a jointly addressed envelope read?

Current nonprofit CRM models make a similar distinction. Microsoft Fundraising and Engagement keeps household members as contacts while adding a primary member, household salutation, and aggregate transaction view. Bloomerang’s current guidance says donations should remain on the record of the individual who made the gift.

The practical rule is simple: the person owns the fact; the household helps you see or act on the relationship.

Do not use a shared address as proof

Two contacts at one address may be partners, adult family members, roommates, or unrelated people in a shared facility. A matching address is a review signal, not permission to merge records or create a household.

Before linking people, confirm the relationship from information your organization already has. Record only what your team needs for a named action. A lean household relationship can usually carry:

• the individual contact IDs;
• the relationship type your team actually uses;
• the shared salutation or mailing label, if requested;
• the person responsible for a joint postal mailing;
• the date the relationship became effective or ended.

Avoid copying personal emails, phone numbers, portal access, or communication preferences onto the household. Those facts can differ even when two people share a kitchen table.

This is also why a household problem should not be solved with a merge. The duplicate-record workflow treats “link” as a separate outcome from “merge” precisely because related people are not duplicate people.

Keep every gift attached to its owner

Suppose Sam and Priya share a household. Sam gives $200 from Sam’s account. Priya has a $25 monthly gift. Your household view may show $500 received across both people after a year, but the underlying records should still show who made each payment.

Do not move both gifts to a “Sam and Priya” contact merely to make the total easy to find. That breaks the line from payment to donor, receipt, recurring schedule, refund, and communication history. It can also make a later address change look like a change of donor identity.

If your system supports household rollups, treat the rollup as a view rather than another gift. If it does not, calculate the household total in a report keyed to the relationship. Do not create a second transaction or an automatic soft credit just to make the number visible. The same guardrail applies in the soft-credit policy: recognition must not turn one received gift into two.

Beacon’s current household guide warns that household records add complexity and recommends keeping donations on the specific person rather than a joint record. That makes a good creation test: if the household will not change a report, mailing, or relationship task, you may not need one.

Choose message ownership before the next appeal

A household can reduce duplicate postal mail without flattening individual communication choices. For Sam and Priya, your team might keep one joint postal salutation while sending email to each person separately. Sam may want fundraising email; Priya may not.

Define the scope before using the household in an audience:

1. Postal mail: Which address and salutation should a joint piece use?
2. Email or SMS: Which individual contact owns the destination and preference?
3. Personal outreach: Which relationship owner should contact which person?
4. Acknowledgment: Which donor record owns the message tied to the gift?

The household should never override a newer person-level instruction. If the relationship view and an individual preference disagree, hold the affected message and resolve the underlying records. The donor communication preference workflow explains how to preserve the channel, purpose, source, and effective time of that instruction.

Test the household with one complicated pair

Do not validate householding with two empty contacts. Use a pair with separate gifts, different email choices, one recurring schedule, and a joint mailing preference.

Then ask four questions:

• Can you open the household total without creating another gift?
• Can you trace each transaction back to one person?
• Can one person change a communication preference without changing the other?
• Can you end the household relationship without erasing either person’s history?

If any answer is no, the household view owns too much. Move the underlying fact back to the individual record, then test again.

Keep the relationship without losing the donor