A donor householding report groups related supporters for selected fundraising decisions without merging away their individual identities. It helps a nonprofit answer two questions at once: “How many people have a relationship with us?” and “How many households are we contacting, cultivating, or depending on?”
That distinction matters whenever spouses, partners, family members, or other people at one address appear as separate records. Counting only individuals can overstate audience reach, duplicate mail, split relationship history, and hide total household giving. Counting only households can erase consent differences, separate interests, individual recognition, and the person who actually made each gift.
The right solution is not one permanent household total. It is a reporting layer that preserves person-level records, makes household membership explainable, and switches grain according to the decision.
What is a donor householding report?
A donor householding report shows which individual supporter records are connected to the same household, how confidently that connection is known, and which fundraising activities should use person-level or household-level counts.
Householding is common in nonprofit constituent management. For example, Salesforce describes a household account as a group of contacts who live at the same address and notes that household records support relationship tracking and direct marketing. That is a useful data model, but the reporting rule still belongs to the organization: sharing an address is evidence, not automatic proof that every person should receive one combined message or be treated as one donor.
A practical report should answer five questions:
- Which person records belong to the same confirmed household?
- Which possible relationships still need review?
- Which communications should be combined, personalized separately, or suppressed?
- Which gifts and engagement signals belong to each person, and which analyses should roll them up?
- How do person counts and household counts change the fundraising decision?
The central rule: choose the reporting grain before counting
Reporting grain is the level at which records are counted before they are summarized. A householding report needs at least two grains:
- Person grain: one row per individual supporter. Use it for consent, communication preference, event participation, volunteer activity, relationship ownership, gift attribution, and individual stewardship.
- Household grain: one row per confirmed household. Use it for address-based mail planning, household relationship value, combined cultivation context, and analyses where multiple people act as one giving unit.
Neither grain is universally correct. A year-end mail quantity estimate may need one record per mailable household. An email audience must still respect each person’s usable address and permission. A major-gift briefing may benefit from combined household giving while also showing which household member gave, attended, met with staff, or expressed an interest.
Put the grain in the report title or subtitle. “Active donors by person” and “active donor households” are both honest labels. “Total donors” is ambiguous when householding changes the count.
Use five householding states instead of a yes-or-no flag
A single household ID hides uncertainty. A more useful report gives every relationship one of five mutually exclusive states:
- Confirmed household: the relationship is documented and suitable for the named household-level use.
- Probable household: multiple signals align, but a person or rule owner must confirm the connection before it changes communication or reporting.
- Shared address only: the records share a location, but the organization has no basis to assume a joint relationship.
- Keep separate: the people are related or colocated, but preferences, donor intent, safety, relationship status, or another documented reason requires separate treatment.
- Needs repair: the underlying names, addresses, contact details, relationship fields, or duplicate records are too incomplete or conflicting to decide.
This state model prevents an address match from silently becoming a household merge. It also creates an operating queue: confirm probable relationships, investigate shared-address records only when the use case warrants it, honor keep-separate decisions, and repair incomplete data.
The minimum fields behind the report
Start with fields the organization already maintains. A useful householding dataset usually includes:
- person ID and household ID
- household state and confidence basis
- relationship type, when known and appropriate to store
- preferred name, formal greeting, and household greeting
- primary and alternate addresses with validity status
- email, phone, and mail preferences at the person level
- communication exclusions and keep-separate instructions
- gift ID, credited person, legal donor-of-record field used by the organization, amount, date, campaign, and designation
- soft-credit or recognition relationships when the CRM supports them
- engagement events by person
- relationship owner and last review date
Do not fill missing relationships with guesswork. Names, addresses, emails, and giving patterns can identify candidates for review, but ambiguous matches should remain visible as ambiguous.
Five metrics that make householding operational
1. Confirmed household coverage
Confirmed household coverage = people in confirmed households / household-eligible people
The denominator must match the use case. A planned direct-mail audience, a major-gift portfolio, and all active constituents are different populations.
2. Review rate
Review rate = probable + shared-address-only + needs-repair records / household-eligible people
Break this queue down by reason, owner, potential communication impact, and household value so staff can resolve the most consequential records first.
3. Duplicate-contact exposure
Duplicate-contact exposure = confirmed households receiving more contacts than the communication rule allows / contacted households
Calculate this for a named campaign and channel. Two emails to two consenting people may be correct; two identical mail pieces to a household selected for one-per-household delivery may be an exception.
4. Household revenue concentration
Household revenue concentration = revenue from the top household group / eligible household revenue
Use an organization-defined group, such as the top 10 households or top 5%, and always publish that definition. Compare this with person-level concentration so leadership can see when several donor records represent one relationship unit.
5. Grain variance
Grain variance = person count – confirmed household count
Grain variance is not an error rate. It is context. A large difference tells the reader that donor, audience, or portfolio conclusions may change depending on whether the decision is about people or households.
A worked householding example
Consider an illustrative direct-mail audience with 1,000 eligible person records. After applying the organization’s household rules:
- 720 people belong to 330 confirmed households.
- 120 people are probable household members awaiting review.
- 60 people share an address without enough evidence to household.
- 40 people have documented keep-separate instructions.
- 60 people need data repair.
Confirmed household coverage is 72%: 720 divided by 1,000. The review rate is 24%: the 120 probable, 60 shared-address-only, and 60 needs-repair records divided by 1,000. The keep-separate group is excluded from that review rate because its status is already resolved.
The confirmed group contains 330 households, not 720 mailing units. However, the organization should not simply subtract 390 pieces from the campaign. It must first apply the communication rule, preserve keep-separate instructions, and decide how unresolved records will be treated. The report changes the mailing decision without pretending that every shared address means one relationship.
What the dashboard should show
Build the first view around decisions, not a network diagram. Include:
- person count and confirmed household count side by side
- records in each householding state
- duplicate-contact exposure by campaign and channel
- person-level and household-level revenue, retention, and concentration
- probable, shared-address, and repair queues by owner
- keep-separate exceptions with restricted visibility
- last review date and the rule version used
For campaign operations, add the final quantity after household and channel rules. For development leaders, add combined household giving and recent engagement with the person-level source records still available. For analysts, include a reconciliation that proves every eligible person was assigned to exactly one state.
Four decisions the report should support
A useful donor householding report should end in one of four actions:
- Combine for this use: apply a confirmed household rule to the named mailing, cultivation view, or analysis while preserving person records.
- Review before action: route high-impact probable households or shared-address cases to a named owner.
- Keep separate: preserve distinct communication, recognition, ownership, and reporting treatment.
- Repair first: correct incomplete or conflicting data before the records affect an audience or performance report.
Set a review cadence that matches the risk. A direct-mail audience may need a prelaunch review; a major-gift portfolio may need monthly attention; the full household rules and exceptions may need quarterly governance. Record rule changes in a reporting rules registry so a new matching method does not silently rewrite historical trends.
Common householding mistakes
- Using address as proof: roommates, multigenerational homes, residential facilities, and stale addresses can create false households.
- Merging people instead of relating them: a household view should not remove individual identity, history, or preferences.
- Rolling up every metric: combined household revenue may help cultivation while person-level consent and engagement remain essential.
- Ignoring keep-separate instructions: a resolved exception is a rule to honor, not a defect to clean up.
- Changing historical counts without explanation: report the household rule version and restate prior periods only through an explicit, documented process.
- Optimizing only for mail savings: a smaller mailing quantity is useful only when the resulting treatment is appropriate for the relationship.
Householding also depends on contact quality. Pair this view with a donor contactability report so a combined household does not conceal that one person lacks a usable or permitted channel.
Where ReportWerks fits
Householding becomes difficult when identity, gifts, campaign activity, communication preferences, and relationship ownership live in disconnected exports. ReportWerks is designed to bring marketing, fundraising, and performance data into one reporting system. A householding view can use that connected context to show person and household totals together, keep uncertain relationships visible, and route exceptions to action.
Start with one decision: the next direct-mail audience, a major-gift portfolio review, or a household revenue analysis. Define the grain, assign every eligible record to one state, reconcile the totals, and publish the rule beside the result. That is enough to turn householding from a hidden database setting into a fundraising control the team can understand and use.
Frequently asked questions
Is donor householding the same as merging duplicate records?
No. Deduplication resolves records believed to represent the same person. Householding relates two or more distinct people for selected communication, relationship, or reporting purposes.
Should every person at the same address be placed in one donor household?
No. A shared address can identify a review candidate, but it does not prove a joint relationship or authorize combined treatment. Use documented rules and preserve a shared-address-only state.
Should fundraising revenue be reported by person or household?
Use the grain that matches the question and label it. Person-level revenue preserves who made each gift. Household-level revenue can help with relationship planning and concentration analysis. Important reports often need both.
How often should household records be reviewed?
Review them before decisions that householding can materially change, such as a direct-mail launch or portfolio assignment. Also run a recurring queue for probable households, shared addresses, keep-separate exceptions, and data repairs.
