Donor Householding for Spouses, Families, and Shared Addresses Without Messy Records
Every nonprofit has experienced the issue of two donors sharing the same address but with different names and histories. Now, one of your team members has to decide whether to send one appeal letter or two, and whether to count these two individuals as one household or two donors in the system.
This is donor householding, and how this is handled is more important than most outreach teams understand. When done correctly, it means the outreach remains professional, the database remains orderly, and the relationship with the donor remains solid. When done incorrectly, it leads to mailings being sent twice, greetings that cause donor frustration, and reports that no one can rely on.
This guide walks through the real-world decisions behind donor householding for nonprofits — from shared addresses and married couples to roommates and families who give separately — so your CRM reflects reality rather than creating it.
What Is Donor Householding and Why Does It Matter?
Donor householding is the process of linking two or more donor records in your database that share the same household — typically a shared address — so they can be treated as a single unit for specific purposes like mailings, gift acknowledgment, and reporting.
The objective is not to remove identities. The objective is not to send two separate letters to a married couple. One letter would be better. Householding is a communications strategy and data hygiene technique.
For nonprofits with thousands of donors, inefficient householding leads to donor loss. Studies show a direct correlation between duplicate letters and donor loss. Personalization leads to donor loyalty. Householding is the technique that leads to personalization.
When to Household — and When Not To
The decision to household two records is not always obvious. Understanding when householding helps versus when it creates confusion is the first step toward cleaner donor data.
Household: when sharing a primary residence brings two people closer to a relationship, such as marriage or domestic partnership. If two people in a household choose to donate, a single acknowledgment is best. If they have no reason to be kept separate for program tracking, it makes sense to create a household record.
Don’t create a household record if the two people choose to donate separately. A parent and child are two separate donors, even if they donate from the same residence. Creating a household record would combine the parent’s and child’s separate donation histories. This is also true for siblings, college students, and friends who, though sharing a residence, have separate donating identities.
Householding should improve clear communication between the donor and the organization. If using a household record would combine donors’ identities or donations, then householding should not be done. If unsure, keep the records separate and use relationship tags instead of a household merge.
Shared Addresses and Shared Cards: The Technical Side
Planning field architecture to handle shared addresses in a nonprofit CRM can be tricky. The majority of contemporary donor databases (Salesforce NPSP, Bloomerang, Blackbaud’s Raiser’s Edge, etc.) enable you to create a household record/account that sits above individual contact records. The household record includes the shared address and the total amount given by the household, while the individual records contain each individual’s full history.
Salesforce Nonprofit Success Pack (NPSP)
Salesforce NPSP utilizes a household account model by default. Each contact is associated with a household account, which includes the household’s shared mailing address. Each contact record contains their own personal details, engagement data, and giving history. A household account can track the household’s total giving, enabling household-level reports while preserving individual giving records. Because of this relational model, NPSP remains a top contender for mid- to large-sized nonprofits that need to conduct in-depth data analysis.
Bloomerang
Bloomerang opts for a more visual design. Users can tag a “head of household” in a constituent record and associate a spouse or partner. Each individual retains their transaction history, and when sending out mailings, users can choose to remove the secondary household member from the output. Thus, only one solicitation is sent to that address, and both constituents are retained in the system. Bloomerang’s system design is ideal for small nonprofits that wish to send mailings without managing a sophisticated database.
Blackbaud Raiser’s Edge NXT
What’s unique about Raiser’s Edge NXT is that you can manage address sharing, combined giving, and family salutation formatting at different levels through relationship records and family groupings. You can change family salutation preferences for receipts, envelopes, and email headers, while leaving the relationship records intact.
The shared card question means one spouse used their credit card to make a donation, and that credit card is also used by the other spouse. Once one donation is made using the shared credit card, you need to decide to whom the donation should be assigned — to one spouse or to the household. The recommended best practice is to record the donation for the household or the primary cardholder, and indicate that the payment method was shared. This practice helps prevent a single donation from counting towards the total donations of two individuals.
Greetings, Receipts, and Mailing Lists: Getting the Details Right
Householding in the database is only half the job. The other half is making sure that household grouping surfaces correctly in every donor-facing output — letters, emails, receipts, event invitations, and acknowledgment cards.
The way you format salutations shows how household trust is built or broken. Knowing that John and Mary will each receive a letter or email addressed only to them makes you just another corporate entity to them. The situation is even worse when you send a letter to “Mr. and Mrs. John Smith” when Mary probably has her own last name, and you should know it.
Your CRM should have a system with two versions of a household salutation. One is formal and will be used when receipts need to be printed on paper. The other is an informal version and is used when writing letters or emails. The staff should manually fill these fields when a household is added to the system. These fields should not be left to the system to auto-fill based on logic incapable of deducing what the donor prefers.
Implementing policies for receipt handling is equally critical. When a gift is made from a joint account or designated as a joint gift, the letter of acknowledgment needs to be sent to both recipients. The IRS does not need joint recipients for gifts, but donors prefer to see a tax receipt issued to both when a gift is made jointly. When each spouse makes a gift separately, each needs a receipt for legal purposes and, of equal importance, for personal reasons.
Householding has been a more cost-effective way of suppressing mailing lists. After a household has been established, your mail merge should pull one record per household, suppressing duplicates. This not only saves money on duplicate postage and printing but also prevents your organization from being perceived as wasteful by sending multiple communications to each of them. Most modern CRMs offer a version of this functionality, either as a head-of-household flag or as a deduplication step in mail list output.
Reporting Households Without Losing Granularity
One of the most persistent fears about donor householding is that combining records will destroy reporting accuracy. This fear is valid — but avoidable with the right data architecture.
The solution is to report at two levels simultaneously. Household-level reports answer questions such as, “What is the lifetime value of this household?” or “How many households made gifts above the threshold this fiscal year?” These reports are crucial to identifying potential major gifts, as a couple giving $2,500 each year is actually a $5,000 household and should be treated as such in your development plan.
Individual-level reports answer questions such as, “Who is our most involved individual donor?” or “Who is our most involved contact?” Individual reports will answer questions such as “Who attended the most contact events?” or “Who responded to the email campaigns?”
The ideal system is one that allows you to report at both levels without changing the underlying data structure. If your system forces you to choose between reporting at the household and individual levels, this is a symptom of a poorly constructed data system or one that may not be your optimal solution.
The Nonprofit Technology Network (NTEN) frequently reports on its published benchmarks for both CRM systems and architecture. If your organization is evaluating a new system or reviewing your current data practices, their reports are essential to read.
When you have clear household data layered with individual data, your staff can see the database without reporting distortions, which is helpful both for retaining donors year over year and for reengaging donors whose giving has lapsed.
Conclusion
Donor householding is not a glamorous topic. But it quietly determines whether your nonprofit communicates like an organization that knows its donors, or one that treats them as rows in a spreadsheet. For spouses, families, and shared addresses, the standard is clear: link households thoughtfully, preserve individual records in full, and ensure every donor-facing output — from the receipt to the envelope — reflects a real human relationship.
For nonprofits constructing or reviewing their CRM strategy, the Blackbaud Institute for Philanthropic Impact provides data-informed research on donor behavior. It also provides research on database best practices that offer nonprofits insight into developing householding policies from the ground up.
The organizations that invest in this work retain more donors, raise more money, and spend less time cleaning up database disasters. That is a return worth pursuing.
Frequently Asked Questions
What is the difference between a household record and a contact record in nonprofit CRMs?
A contact record stores information about an individual donor — their name, giving history, communication preferences, and relationship data. A household record sits above individual contacts and groups two or more people at the same address. The household holds shared information, such as the mailing address and combined giving totals, while each contact retains their own complete history. Most modern CRMs support both levels simultaneously.
Should I household donors who give separately but share an address?
Not necessarily. If both individuals give independently and value individual recognition, householding them for communication purposes makes sense — one mailing per address — but their giving records should remain separate. Use a household link for mailing suppression without merging their donation histories. The goal is clean communications, not collapsed data.
How do I handle a donor household where one spouse has passed away?
Remove the deceased individual from active mailing lists and update the household salutation immediately. Do not delete the record — preserve the giving history and relationship data for institutional memory and stewardship purposes. Update the surviving spouse’s record to reflect their new preferred salutation, and review any joint gift designations that may need to be reassigned.
What should I do if a householded couple separates or divorces?
Dissolve the household link as soon as you become aware of the change. Create or restore two fully independent contact records, each with their own current address and communication preferences. Verify with each individual how they prefer to be addressed going forward. This protects both donors’ privacy and keeps your data current.