Robert Allen Sr. and Robert Allen Jr. live at the same address, both carry memberships, and both show up in a household lookup as “Robert Allen.” Your volunteer at the member desk picks one, checks him in, and the visit history now belongs to the wrong person. Nobody did anything careless. The suffix was on the record; it just wasn’t on the screen.
That gap is the whole problem with suffixes in Altru. The field exists and you can fill it in, but whether you actually see it depends on where you’re looking and how your name formats are set up. Here’s how to get suffixes showing in the places where they matter, and how to cope with the screens where they don’t.
Where the suffix lives
On an individual constituent record, the suffix is its own name field alongside title, first, middle, and last name. That’s the right place for it. Entering “Jr.” in the suffix field (rather than typing “Allen Jr.” into the last name) keeps the data clean for sorting, searching, and duplicate checks.
What you see on a given screen, though, is usually a display name built from those parts, not the raw fields. Some views assemble that name with the suffix included and some leave it off. Household views, search results, and summary panels are the places people most often notice the suffix missing.
What you can control
Addressee and salutation formats
For anything that goes out the door (letters, acknowledgments, membership cards, mailing lists), the name comes from addressee and salutation formats. Altru lets administrators configure which name formats are available and which is the default. If your default addressee format doesn’t include the suffix, add or choose one that does, and set it as the default for new records.
Keep in mind that existing constituents keep whatever format was assigned to them. Changing the default won’t rewrite old records, so plan a cleanup for people who already have suffixes (more on that below).
Queries and exports
When you build a constituent query, add the suffix field as its own output column, or use a formatted name output that includes it. If staff rely on a saved query or report to look people up, that’s often the fastest place to make suffixes visible without touching anyone’s daily screens.
Household and on-screen display names
This is the part I can’t promise you can change. Whether the household screen and other built-in views can be configured to show suffixes depends on how that page builds its names, and that isn’t something most organizations can edit. Before you spend time hunting for a setting, test it: add a suffix to a sandbox or test constituent who belongs to a household, then check the household page, constituent search, and the sales screens. If the suffix doesn’t appear and you can’t find a related option, ask Blackbaud support directly whether that display is configurable in your version.
Practical workarounds for the screens you can’t change
- Don’t stuff the suffix into the last name. It’s tempting, and it does make “Allen Jr.” visible everywhere. It also breaks alphabetical sorting, makes searches for “Allen” less reliable, and pollutes every addressee that already appends a suffix (“Robert Allen Jr. Jr.”). Fixing it later is tedious.
- Use the middle name when it differs. If Sr. and Jr. have different middle names or initials, make sure both are filled in. A display that drops the suffix will often still show a middle initial.
- Add an alert or note for same-name households. A short constituent note or attribute like “Father and son share a name; confirm suffix” gives desk staff a reason to slow down.
- Check birth dates or email at the desk. Train staff to confirm one extra detail when a household has two people with the same first and last name. Email address is usually the quickest tiebreaker.
- Watch your duplicate checks. Same name, same address is exactly what duplicate matching looks for. Before merging two “Robert Allen” records, open both and compare suffix, birth date, and email. Merging a father into his son is much harder to undo than to avoid.
Cleaning up records you already have
Start with a query for individuals whose last name ends in common suffix text: “Jr”, “Jr.”, “Sr”, “II”, “III”, “IV”. You’ll get some false hits (a surname that genuinely ends in “ii” for example), so review the list rather than changing it blindly. For each real match, move the suffix into the suffix field, correct the last name, and update the addressee and salutation if they were set before the change.
Then run a second query on the suffix field itself to catch inconsistencies like “Jr” versus “Jr.” and standardize on one. If your suffix field uses a code table, trim it to the values you actually want so new entries stay consistent.
Quick answers
Will a suffix show on printed letters?
Only if the addressee format assigned to that constituent includes it. Check the format, not just the name fields.
Can I make suffixes appear on every screen?
Not reliably through settings you control. Test the specific screens your staff use, and confirm with Blackbaud support before assuming a fix exists.
