A longtime donor calls the development office: “Can you put me and my husband down for the spring lecture?” You already have her constituent record open because you were just thanking her for last month’s gift. The natural thing is to click something on that record and register her. In many Altru setups, that button isn’t there, and staff end up closing the record, going to the event, finding the registration area, and searching for the same person all over again.
This article explains what to expect, the fastest ways to register someone when you start from their record, and how to make the record useful for registration questions even if registration itself happens somewhere else.
Why registration usually starts from the event, not the person
Altru organizes event registration around the event (or the scheduled program, if you sell the event as a ticketed program through daily or advance sales). The event owns the price points, capacity, and registrant list, so the registration workflow begins there and asks you to pick a constituent. The constituent record is mostly where the results show up: revenue, interactions, and in many configurations, the person’s event participation.
Whether your version offers any shortcut from the constituent page into a registration depends on your Altru configuration and how your events are set up. We aren’t going to guess at a menu path. To confirm what your system does, open a test constituent in your sandbox (or a staff record in production) and look at every action available on the record and its tabs. If you don’t see a registration action, ask Blackbaud support whether one exists for your event type before building a workaround.
Three workable ways to do it today
1. Event first, constituent lookup second
This is the standard route and the one to train everyone on. Go to the event, start a registration, and search for the constituent. Two habits make it faster:
- Copy a unique identifier before you leave the record. Lookup ID or email is much safer than a name search, especially for common surnames or households where both spouses share a last name and address.
- Keep the constituent record open in a second browser tab. Altru runs in the browser, so you can register in one tab and still answer the donor’s questions about their giving or membership in the other.
2. Sell it as a ticket with the constituent attached
If the event is set up as a program in advance sales, staff can start an advance sale, select the constituent as the patron, and add tickets. This keeps the purchase tied to the person’s record and is often familiar to front-desk staff who already do this for timed admission. It works best for public programs where “registration” really means “a ticket with a name on it.” It’s a weaker fit for invitation-only events where you track invitees, guests, and responses separately.
3. Log the request, register in a batch
For busy development officers who take registrations during donor calls, a simple pattern works: add an interaction or note on the constituent record (“Requested 2 seats, spring lecture”) and have one person process those requests against the event at the end of the day. A query on that interaction type gives you a clean worklist, and nothing gets lost when the officer is away from their desk.
Make the record answer registration questions
Even if registration starts from the event, staff should be able to look at a person and know whether they’re signed up. A few things help:
- Check where participation appears. Register a test constituent and see what shows on their record afterward. Note the exact tab or section, and put that in your staff guide.
- Add a smart field or query for upcoming registrations. If your team regularly asks “is this person coming to anything?”, a constituent query filtered to future events gives a quick answer and can be shared with the whole office.
- Register guests as real constituents when it matters. If you’ll want to steward a guest later, create or match their record rather than typing a name into a free-text field. It’s more work up front and saves a lot of cleanup.
Watch for duplicates
The biggest risk with the event-first route isn’t the extra clicks. It’s staff who, in a hurry, can’t find the person in the lookup and create a new constituent instead. Now the donor’s event history and giving history live on two records. Before anyone adds a new constituent from inside a registration, have them search by email and by phone, not just name. If your team creates a lot of records this way, run a periodic duplicate review so registrations and gifts end up on the same person.
Quick answers
Can I register a whole household at once from the head of household’s record?
Plan on registering each person (or the primary registrant plus guests) through the event. How household members and guests are linked depends on your event setup, so test it with a real household in your sandbox.
Is it worth asking Blackbaud for a constituent-page shortcut?
It’s worth asking support whether your version already has one. In the meantime, the two-tab habit and copying the lookup ID cover most of the friction.
