Maria Lopez and David Chen buy a family membership. Their two kids are Chens. At the desk, someone types “Maria Chen” because that seemed close enough, or creates one record called “Maria & David Lopez-Chen.” Six months later the renewal letter goes to a person who doesn’t exist, Maria’s own donation sits on a different record, and nobody can find the family when they search for “Lopez.”
Households with mixed last names are common, and Altru handles them fine as long as you enter people as people and let the household do the grouping. The trouble almost always comes from shortcuts at data entry. Below is the approach that holds up over years of renewals, gifts, and mailings.
The core rule: one constituent record per real person
Every adult (and every child you need to track) gets their own individual constituent record with their own legal or preferred last name. Don’t combine two people into one record, don’t borrow a partner’s last name to make the household “match,” and don’t put a second person’s name in a first name or middle name field.
Why it matters:
- Search works. Staff can find the family by looking up either last name.
- Giving is credited correctly. A gift from Maria lands on Maria, which matters for acknowledgments, tax receipts, and any donor recognition.
- Email and contact details stay accurate. Two adults rarely share one email address, and Altru communications go to the right person.
- Breakups don’t wreck your data. If a household later splits, two clean individual records are easy to separate. A combined record has to be rebuilt by hand.
Grouping them: household plus relationships
Once each person exists, link them. In Altru that generally means two things:
- A relationship between the adults (spouse or partner, using whatever relationship types your organization has set up). This is what tells staff, and your reports, how the two people are connected.
- A household that both belong to, with the children added as household members too. Pick one adult as the primary member, usually whoever handles the membership or whose contact information you want used by default.
Depending on how your database is configured, creating a spouse relationship may offer to create or join a household automatically. If you aren’t sure how your version behaves, try it on a test constituent pair first and check what records were created before training staff on it.
Naming the household
The household name is what shows up in search results and on household-level lists, so pick a convention and use it every time. Common options:
- “Maria Lopez and David Chen Household” — clearest, and searchable by either surname.
- “Lopez/Chen Household” — shorter, still finds both names.
- “Chen Household” — only if the family actually prefers it. Otherwise people searching for Lopez won’t see it.
Whatever you choose, write it in your data entry guide with a couple of examples. Inconsistent household names are one of the main reasons the same family ends up entered twice.
Addressee and salutation: where mixed names show up in print
Most of the visible problems happen on envelopes and letters. Altru lets you store addressee and salutation formats for constituents, and you can usually override the default for a specific person or household. For a mixed-name couple, set them explicitly rather than relying on a format built around a single shared surname:
- Addressee: Ms. Maria Lopez and Mr. David Chen (or without titles, if that’s your house style)
- Salutation: Maria and David
Before a big mailing, pull a query of households where the members have different last names and spot-check the addressee output. Formats that work well for “Mr. and Mrs. Smith” can produce odd results for two surnames, and it’s better to catch that in a query than on 400 printed letters. If you can’t tell which format a mailing or report pulls from, ask Blackbaud support or run a small test export.
Memberships with mixed names
Add each adult to the membership as a member in their own name, and add children as your program allows. That way each person’s name prints correctly on a card, and the desk can look up the membership from either adult’s record. Avoid adding a spouse as a free-text name on the card if your program supports real member records; free text can’t be searched or emailed.
Situations that need a judgment call
Kids with a different last name than one parent
Enter the child under their own last name and add them to the household. If they’re under 18, you probably don’t need much beyond name and birthdate, depending on your privacy policy.
Roommates, adult siblings, grandparents
Ask whether they actually share mail and a membership. If they do, a household works. If one just tagged along on a visit, two separate constituents with no household is cleaner.
Couples who separate
End the relationship, remove one person from the household (or create a new one for them), and update addresses. Because each person had their own record from the start, their giving and visit history stays intact.
A short checklist for staff
- Search for both last names and the email address before creating anyone.
- Create each person with their own name and contact details.
- Add the spouse or partner relationship.
- Put everyone in one household, named by your convention, with a primary member set.
- Check the addressee and salutation, and fix them if they assume one surname.
Quick answers
Should we use a hyphenated name for the household?
Only if the family uses it. A household name like “Lopez/Chen” is a label for staff, not a name anyone carries, so keep the individual records accurate and use the household name for grouping.
We already have combined records. Do we have to fix them all?
Not at once. Fix them as members renew or give, and use a query on constituent names containing “&” or “and” to find the worst cases first.
